Re: Issue with kernel building
On Thu, 23 Aug 2012 17:23:59 +0100, Jamie Paul Griffin wrote: > [ Lowell Gilbert wrote on Thu 23.Aug'12 at 10:28:47 -0400 ] > > > Jamie Paul Griffin writes: > > > > > [ Lowell Gilbert wrote on Thu 23.Aug'12 at 9:23:14 -0400 ] > > > > > >> antonin tessier writes: > > >> > > >> > I have a problem when I try to build my own kernel. I had never > > >> > got such a one; here is my kernel configuration file and the > > >> > building errors that it makes. > > > > > >> Or just stay with GENERIC; most consumer PCs have no real reason to need > > >> a customized kernel. > > > > > > I agree. It boots quickly and it isn't really necessary for the majority > > > of users. I can be useful to learn the procedure, etc. but didn't use the > > > correct command anyway: > > > > > > make buildkernel KERNCONF=KERNELCONFIG > > >^^^ > > > > "make kernel" is equivalent to "make buildkernel installkernel". > > Ah, I didn't know that. I just stick to the Handbook info but it's good > to learn other options. Cheers. Have a look at the comment header of /usr/src/Makefile -- it contaons lots of "compressed information" about how to deal with source installs. Also worth reading: "man make.conf" and "man src.conf". -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Issue with kernel building
[ Lowell Gilbert wrote on Thu 23.Aug'12 at 10:28:47 -0400 ] > Jamie Paul Griffin writes: > > > [ Lowell Gilbert wrote on Thu 23.Aug'12 at 9:23:14 -0400 ] > > > >> antonin tessier writes: > >> > >> > I have a problem when I try to build my own kernel. I had never > >> > got such a one; here is my kernel configuration file and the > >> > building errors that it makes. > > > >> Or just stay with GENERIC; most consumer PCs have no real reason to need > >> a customized kernel. > > > > I agree. It boots quickly and it isn't really necessary for the majority of > > users. I can be useful to learn the procedure, etc. but didn't use the > > correct command anyway: > > > > make buildkernel KERNCONF=KERNELCONFIG > >^^^ > > "make kernel" is equivalent to "make buildkernel installkernel". Ah, I didn't know that. I just stick to the Handbook info but it's good to learn other options. Cheers. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Issue with kernel building
Jamie Paul Griffin writes: > [ Lowell Gilbert wrote on Thu 23.Aug'12 at 9:23:14 -0400 ] > >> antonin tessier writes: >> >> > I have a problem when I try to build my own kernel. I had never >> > got such a one; here is my kernel configuration file and the >> > building errors that it makes. > >> Or just stay with GENERIC; most consumer PCs have no real reason to need >> a customized kernel. > > I agree. It boots quickly and it isn't really necessary for the majority of > users. I can be useful to learn the procedure, etc. but didn't use the > correct command anyway: > > make buildkernel KERNCONF=KERNELCONFIG >^^^ "make kernel" is equivalent to "make buildkernel installkernel". ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Issue with kernel building
[ Lowell Gilbert wrote on Thu 23.Aug'12 at 9:23:14 -0400 ] > antonin tessier writes: > > > I have a problem when I try to build my own kernel. I had never got such a > > one; here is my kernel configuration file and the building errors that it > > makes. > Or just stay with GENERIC; most consumer PCs have no real reason to need > a customized kernel. I agree. It boots quickly and it isn't really necessary for the majority of users. I can be useful to learn the procedure, etc. but didn't use the correct command anyway: make buildkernel KERNCONF=KERNELCONFIG ^^^ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Issue with kernel building
antonin tessier writes: > I have a problem when I try to build my own kernel. I had never got such a > one; here is my kernel configuration file and the building errors that it > makes. You left out some devices that are required by other devices in your configuration. for a start, it looks like "man 4 ral" would tell you about a few of them for the ral device. A better way to assemble a kernel configuration would be to start with GENERIC and only change a few items at a time. That way, if it fails to build, you have a narrower idea of where to look for the problem. Or just stay with GENERIC; most consumer PCs have no real reason to need a customized kernel. Good luck. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Issue with kernel building
Hi, I have a problem when I try to build my own kernel. I had never got such a one; here is my kernel configuration file and the building errors that it makes. "#device tun # Packet tunnel. device pty # BSD-style compatibility pseudo ttys device md # Memory "disks" device gif # IPv6 and IPv4 tunneling device faith # IPv6-to-IPv4 relaying (translation) #device firmware# firmware assist module # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! # Note that 'bpf' is required for DHCP. device bpf # Berkeley packet filter # USB support options USB_DEBUG # enable debug msgs device uhci# UHCI PCI->USB interface device ohci# OHCI PCI->USB interface device ehci# EHCI PCI->USB interface (USB 2.0) #device xhci# XHCI PCI->USB interface (USB 3.0) device usb # USB Bus (required) #device udbp# USB Double Bulk Pipe devices (needs netgraph) device uhid# "Human Interface Devices" #device ukbd# Keyboard #device ulpt# Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse #device urio# Diamond Rio 500 MP3 player # USB Serial devices #device u3g # USB-based 3G modems (Option, Huawei, Sierra) #device uark# Technologies ARK3116 based serial adapters #device ubsa# Belkin F5U103 and compatible serial adapters #device uftdi # For FTDI usb serial adapters #device uipaq # Some WinCE based devices #device uplcom # Prolific PL-2303 serial adapters #device uslcom # SI Labs CP2101/CP2102 serial adapters #device uvisor # Visor and Palm devices #device uvscom # USB serial support for DDI pocket's PHS # USB Ethernet, requires miibus #device aue # ADMtek USB Ethernet #device axe # ASIX Electronics USB Ethernet #device cdce# Generic USB over Ethernet #device cue # CATC USB Ethernet #device kue # Kawasaki LSI USB Ethernet #device rue # RealTek RTL8150 USB Ethernet #device udav# Davicom DM9601E USB # USB Wireless #device rum # Ralink Technology RT2501USB wireless NICs #device run # Ralink Technology RT2700/RT2800/RT3000 NICs. #device uath# Atheros AR5523 wireless NICs #device upgt# Conexant/Intersil PrismGT wireless NICs. #device ural# Ralink Technology RT2500USB wireless NICs device urtw# Realtek RTL8187B/L wireless NICs #device zyd # ZyDAS zd1211/zd1211b wireless NICs # FireWire support #device firewire# FireWire bus code # sbp(4) works for some systems but causes boot failure on others #device sbp # SCSI over FireWire (Requires scbus and da) #device fwe # Ethernet over FireWire (non-standard!) #device fwip# IP over FireWire (RFC 2734,3146) #device dcons # Dumb console driver #device dcons_crom # Configuration ROM for dcons # Sound support device sound # Generic sound driver (required) #device snd_cmi # CMedia CMI8338/CMI8738 #device snd_csa # Crystal Semiconductor CS461x/428x #device snd_emu10kx # Creative SoundBlaster Live! and Audigy #device snd_es137x # Ensoniq AudioPCI ES137x device snd_hda # Intel High Definition Audio device snd_ich # Intel, NVidia and other ICH AC'97 Audio #device snd_uaudio # USB Audio device snd_via8233 # VIA VT8233x Audio" "# make kernel KERNCONF=GOLLUM MAKE=make sh /usr/src/sys/conf/newvers.sh GOLLUM cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -march=native -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror vers.c linking kernel.debug rt2560.o: In function `rt2560_ioctl'
Re: Issue with kernel building
On Mon, 20 Aug 2012 09:46:30 -0400, Robert Huff wrote: > > Polytropon writes: > > > > Very good point! I'd clear the /usr/src/obj directory as pointed out, > > > then build a generic kenel, install it and boot from it. Then you > > > know you've got a working kernel to fall back on. > > > > You could then make a copy of that kernel, e. g. from its initial > > installation location /boot/kernel to /boot/kernel.GENERIC. > > Before doing this, make sure you have enough space on /. On my > -CURRENT system, /boot/kernel uses ~300 mb and /boot/modules another > 35; I created / with 2 gb in part so it could hold multiple kernels. > Running out of space on / is a Really Bad Idea(tm). Excellent advice. I'd like to add "man src.conf" and maybe tweaking /etc/make.conf to adjust kernel and world builds for the case that more control over what should be built and installed is desired, such as omitting debug symbols, the exclusion of certain modules and so on. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Issue with kernel building
Polytropon writes: > > Very good point! I'd clear the /usr/src/obj directory as pointed out, > > then build a generic kenel, install it and boot from it. Then you > > know you've got a working kernel to fall back on. > > You could then make a copy of that kernel, e. g. from its initial > installation location /boot/kernel to /boot/kernel.GENERIC. Before doing this, make sure you have enough space on /. On my -CURRENT system, /boot/kernel uses ~300 mb and /boot/modules another 35; I created / with 2 gb in part so it could hold multiple kernels. Running out of space on / is a Really Bad Idea(tm). Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Issue with kernel building
On Mon, 20 Aug 2012 14:13:44 +0100, Jamie Paul Griffin wrote: > == Michael Powell wrote on Sun 19.Aug'12 at 19:43:14 -0400 == > > > Keep in mind whenever you install a new kernel your present kernel (and its > > matching modules) get moved to kernel.old. What this means is that the > > GENERIC you have with a base install will be moved to kernel.old and can be > > used in the event the new kernel won't boot. Realize this: after the next > > rebuild process this kernel.old will be replaced _again_. In which case > > you > > might now have 2 broken kernels with not an easy way to recover. > > Very good point! I'd clear the /usr/src/obj directory as pointed out, > then build a generic kenel, install it and boot from it. Then you > know you've got a working kernel to fall back on. You could then make a copy of that kernel, e. g. from its initial installation location /boot/kernel to /boot/kernel.GENERIC. If you continue building a custom kernel, /boot/kernel will be overwritten. In worst case, you can unload your custom kernel at the loader prompt, load kernel.GENERIC instead and boot the system with that definitely working kernel. > At that point rebuild your custom kernel with correct commands > as pointed out in the previous response by Michael; i.e. > `make buildkernel KERNCONF=MYKERNEL` ... etc. Again, I may point to The FreeBSD Handbook, the section regarding building world and kernel, as well as the instructions in the comment header of /usr/src/Makefile. Following those advices should be easy and provide you with a procedure that reliably works. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Issue with kernel building
== Jerry wrote on Mon 20.Aug'12 at 8:11:17 -0400 == > I inquired several years ago about the possibility of changing the > renaming format into something like: "kernel_##_YY-MM-DD.old". The "##" > would be incremented with each successive build on a given day. I > thought it would alleviate just the sort of problem you are referring > to and would make it easier to revert to a specific kernel if required. > I never received even a single response so I guess it was not a well > received concept. I think it's a valid and idiot-proof suggestion; however, the handbook information regarding building custom kernels is pretty clear. The steps are not difficult to understand if you ask me. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Issue with kernel building
== Michael Powell wrote on Sun 19.Aug'12 at 19:43:14 -0400 == > Keep in mind whenever you install a new kernel your present kernel (and its > matching modules) get moved to kernel.old. What this means is that the > GENERIC you have with a base install will be moved to kernel.old and can be > used in the event the new kernel won't boot. Realize this: after the next > rebuild process this kernel.old will be replaced _again_. In which case you > might now have 2 broken kernels with not an easy way to recover. Very good point! I'd clear the /usr/src/obj directory as pointed out, then build a generic kenel, install it and boot from it. Then you know you've got a working kernel to fall back on. At that point rebuild your custom kernel with correct commands as pointed out in the previous response by Michael; i.e. `make buildkernel KERNCONF=MYKERNEL` ... etc. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Issue with kernel building
On Sun, 19 Aug 2012 19:43:14 -0400
Michael Powell articulated:
{snip}
> Keep in mind whenever you install a new kernel your present kernel
> (and its matching modules) get moved to kernel.old. What this means
> is that the GENERIC you have with a base install will be moved to
> kernel.old and can be used in the event the new kernel won't boot.
> Realize this: after the next rebuild process this kernel.old will be
> replaced _again_. In which case you might now have 2 broken kernels
> with not an easy way to recover.
I inquired several years ago about the possibility of changing the
renaming format into something like: "kernel_##_YY-MM-DD.old". The "##"
would be incremented with each successive build on a given day. I
thought it would alleviate just the sort of problem you are referring
to and would make it easier to revert to a specific kernel if required.
I never received even a single response so I guess it was not a well
received concept.
--
Jerry ♔
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__
“I believe if life gives you lemons make lemonade… then find someone
that life gave vodka to and have a party.”
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Issue with kernel building
antonin tessier wrote: > > Hi, > > I have a problem when I try to build my own kernel. I had never got such a > one; here is my kernel configuration file and the building errors that it > makes. > [snip] > > "# make kernel KERNCONF=GOLLUM > > MAKE=make sh /usr/src/sys/conf/newvers.sh GOLLUM > > Stop in /usr/obj/usr/src/sys/GOLLUM. " I have snipped out content for brevity; rather let's focus on evidence of incorrect procedure on your part. While there still exists 2 ways of accomplishing this, the so-called "new" method is standard. An example of how to do this can be found contained within a commented out section in the beginning of /usr/src/Makefile. While this information is on how to completely rebuild/update the entire system from source, the commands to build and install a new kernel are present. Please note the following: make buildkernel KERNCONF=somekernelfilename make installkernel KERNCONF=somekernelfilename You are on almost the right track but you are referencing above incorrect paths to this kernel config process. For an i386 box/install your kernel config file would be located in /usr/src/sys/i386/conf and for a 64-bit amd64 install this location is /usr/src/sys/amd64/conf. The best way to begin with customising a kernel is to simply copy the GENERIC config you will find in the conf directory mentioned (whichever is your box - i386 or amd64) to something like, for example, GOLLUM. Then cd to /usr/src and perform the above described commands. Hints: Prior to attempting to rebuild again cd to /usr/obj and delete anything under /usr/obj. There will exist here content left over from the previous failed attempt. Keep in mind whenever you install a new kernel your present kernel (and its matching modules) get moved to kernel.old. What this means is that the GENERIC you have with a base install will be moved to kernel.old and can be used in the event the new kernel won't boot. Realize this: after the next rebuild process this kernel.old will be replaced _again_. In which case you might now have 2 broken kernels with not an easy way to recover. This is just some generic stuff to try and get you back on track. I would recommend an extended reading of the Handbook, as all of these instructions are present there. Hope this halps. :-) -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Issue with kernel building
Hi, I have a problem when I try to build my own kernel. I had never got such a one; here is my kernel configuration file and the building errors that it makes. "#device tun # Packet tunnel. device pty # BSD-style compatibility pseudo ttys device md # Memory "disks" device gif # IPv6 and IPv4 tunneling device faith # IPv6-to-IPv4 relaying (translation) #device firmware# firmware assist module # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! # Note that 'bpf' is required for DHCP. device bpf # Berkeley packet filter # USB support options USB_DEBUG # enable debug msgs device uhci# UHCI PCI->USB interface device ohci# OHCI PCI->USB interface device ehci# EHCI PCI->USB interface (USB 2.0) #device xhci# XHCI PCI->USB interface (USB 3.0) device usb # USB Bus (required) #device udbp# USB Double Bulk Pipe devices (needs netgraph) device uhid# "Human Interface Devices" #device ukbd# Keyboard #device ulpt# Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse #device urio# Diamond Rio 500 MP3 player # USB Serial devices #device u3g # USB-based 3G modems (Option, Huawei, Sierra) #device uark# Technologies ARK3116 based serial adapters #device ubsa# Belkin F5U103 and compatible serial adapters #device uftdi # For FTDI usb serial adapters #device uipaq # Some WinCE based devices #device uplcom # Prolific PL-2303 serial adapters #device uslcom # SI Labs CP2101/CP2102 serial adapters #device uvisor # Visor and Palm devices #device uvscom # USB serial support for DDI pocket's PHS # USB Ethernet, requires miibus #device aue # ADMtek USB Ethernet #device axe # ASIX Electronics USB Ethernet #device cdce# Generic USB over Ethernet #device cue # CATC USB Ethernet #device kue # Kawasaki LSI USB Ethernet #device rue # RealTek RTL8150 USB Ethernet #device udav# Davicom DM9601E USB # USB Wireless #device rum # Ralink Technology RT2501USB wireless NICs #device run # Ralink Technology RT2700/RT2800/RT3000 NICs. #device uath# Atheros AR5523 wireless NICs #device upgt# Conexant/Intersil PrismGT wireless NICs. #device ural# Ralink Technology RT2500USB wireless NICs device urtw# Realtek RTL8187B/L wireless NICs #device zyd # ZyDAS zd1211/zd1211b wireless NICs # FireWire support #device firewire# FireWire bus code # sbp(4) works for some systems but causes boot failure on others #device sbp # SCSI over FireWire (Requires scbus and da) #device fwe # Ethernet over FireWire (non-standard!) #device fwip# IP over FireWire (RFC 2734,3146) #device dcons # Dumb console driver #device dcons_crom # Configuration ROM for dcons # Sound support device sound # Generic sound driver (required) #device snd_cmi # CMedia CMI8338/CMI8738 #device snd_csa # Crystal Semiconductor CS461x/428x #device snd_emu10kx # Creative SoundBlaster Live! and Audigy #device snd_es137x # Ensoniq AudioPCI ES137x device snd_hda # Intel High Definition Audio device snd_ich # Intel, NVidia and other ICH AC'97 Audio #device snd_uaudio # USB Audio device snd_via8233 # VIA VT8233x Audio" "# make kernel KERNCONF=GOLLUM MAKE=make sh /usr/src/sys/conf/newvers.sh GOLLUM cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -march=native -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror vers.c linking kernel.debug rt2560.o: In function `rt2560_ioctl': /u
Re: error with kernel building
At 02:11 PM 1/4/2006, Nguyen Danh Hieu wrote: Could someone tell me what's wrong with my configuration plz here are erros with command "make" You have the wlan device commented out but the ural devices requires it. You also have the da device commented out, but there are other devices that require it that are still included. -Glenn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
error with kernel building
Could someone tell me what's wrong with my configuration plz here are erros with command "make" linking kernel.debug if_ural.o(.text+0x3bb): In function `ural_attach': ../../../dev/usb/if_ural.c:458: undefined reference to `ieee80211_ieee2mhz' if_ural.o(.text+0x3ef):../../../dev/usb/if_ural.c:463: undefined reference to `ieee80211_ieee2mhz' if_ural.o(.text+0x427):../../../dev/usb/if_ural.c:468: undefined reference to `ieee80211_ieee2mhz' if_ural.o(.text+0x4bb):../../../dev/usb/if_ural.c:480: undefined reference to `ieee80211_ieee2mhz' if_ural.o(.text+0x4e2):../../../dev/usb/if_ural.c:487: undefined reference to `ieee80211_ifattach' if_ural.o(.text+0x513):../../../dev/usb/if_ural.c:493: undefined reference to `ieee80211_media_status' if_ural.o(.text+0x51e):../../../dev/usb/if_ural.c:493: undefined reference to `ieee80211_media_init' if_ural.o(.text+0x580):../../../dev/usb/if_ural.c:507: undefined reference to `ieee80211_announce' if_ural.o(.text+0x628): In function `ural_detach': ../../../dev/usb/if_ural.c:535: undefined reference to `ieee80211_ifdetach' if_ural.o(.text+0x73a): In function `ural_free_tx_list': ../../../dev/usb/if_ural.c:595: undefined reference to `ieee80211_free_node' if_ural.o(.text+0x8f2): In function `ural_media_change': ../../../dev/usb/if_ural.c:673: undefined reference to `ieee80211_media_change' if_ural.o(.text+0x9a8): In function `ural_next_scan': ../../../dev/usb/if_ural.c:699: undefined reference to `ieee80211_next_scan' if_ural.o(.text+0xb13): In function `ural_task': ../../../dev/usb/if_ural.c:756: undefined reference to `ieee80211_beacon_alloc' if_ural.o(.text+0xc73): In function `ural_txeof': ../../../dev/usb/if_ural.c:826: undefined reference to `ieee80211_free_node' if_ural.o(.text+0xd99): In function `ural_rxeof': ../../../dev/usb/if_ural.c:890: undefined reference to `ieee80211_find_rxnode' if_ural.o(.text+0xdaf):../../../dev/usb/if_ural.c:893: undefined reference to `ieee80211_input' if_ural.o(.text+0xdb7):../../../dev/usb/if_ural.c:896: undefined reference to `ieee80211_free_node' if_ural.o(.text+0x1360): In function `ural_tx_data': ../../../dev/usb/if_ural.c:1218: undefined reference to `ieee80211_crypto_encap' if_ural.o(.text+0x1858): In function `ural_start': ../../../dev/usb/if_ural.c:1321: undefined reference to `ieee80211_find_txnode' if_ural.o(.text+0x1890):../../../dev/usb/if_ural.c:1328: undefined reference to `ieee80211_encap' if_ural.o(.text+0x189f):../../../dev/usb/if_ural.c:1330: undefined reference to `ieee80211_free_node' if_ural.o(.text+0x18d7):../../../dev/usb/if_ural.c:1338: undefined reference to `ieee80211_free_node' if_ural.o(.text+0x19c4): In function `ural_watchdog': ../../../dev/usb/if_ural.c:1370: undefined reference to `ieee80211_watchdog' if_ural.o(.text+0x1ad2): In function `ural_ioctl': ../../../dev/usb/if_ural.c:1417: undefined reference to `ieee80211_ioctl' if_ural.o(.text+0x1f58): In function `ural_set_chan': ../../../dev/usb/if_ural.c:1606: undefined reference to `ieee80211_chan2ieee' *** Error code 1 Stop in /usr/src/sys/i386/compile/mykernel and here is my configuration # # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ../../conf/NOTES and NOTES files. # If you are in doubt as to the purpose or necessity of a line, check first # in NOTES. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.429.2.3.2.1 2005/10/28 19:22:41 jhb Exp $ machine i386 #cpuI486_CPU #cpuI586_CPU cpu I686_CPU ident mykernel # To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" # Default places to look for devices. makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols #optionsSCHED_ULE # ULE scheduler options SCHED_4BSD # 4BSD scheduler options PREEMPTION # Enable kernel thread preemption options INET# InterNETworking options INET6 # IPv6 communications protocols options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options MD_ROOT # MD is a potential root device #optionsNFSCLIENT # Network
Re: kernel-building error
On Fri, 8 Aug 2003 09:49:08 -0700 Kent Stewart <[EMAIL PROTECTED]> wrote: |On Friday 08 August 2003 07:10 am, mess-mate wrote: |> Hi, |> An error occurs when building my kernel :( |> What does this mean ?? : | |That you deleted options without reading what is required. Read the |requirements for umass in the USB section and reactivate the required |pieces. | |Kent | |> |> linking kernel |> umass.o: In function `umass_cam_attach_sim': |> umass.o(.text+0x17c7): undefined reference to `cam_simq_alloc' |> umass.o(.text+0x1818): undefined reference to `cam_sim_alloc' |> umass.o(.text+0x1827): undefined reference to `cam_simq_free' |> umass.o(.text+0x1847): undefined reference to `xpt_bus_register' |> umass.o: In function `umass_cam_rescan_callback': |> umass.o(.text+0x1883): undefined reference to `xpt_free_path' |> umass.o: In function `umass_cam_rescan': |> umass.o(.text+0x18f5): undefined reference to `xpt_periph' |> umass.o(.text+0x1904): undefined reference to `xpt_create_path' |> umass.o(.text+0x1920): undefined reference to `xpt_setup_ccb' |> umass.o(.text+0x193d): undefined reference to `xpt_action' |> umass.o: In function `umass_cam_detach_sim': |> umass.o(.text+0x1a2c): undefined reference to `xpt_bus_deregister' |> umass.o(.text+0x1a48): undefined reference to `cam_sim_free' |> umass.o: In function `umass_cam_action': |> umass.o(.text+0x1ebd): undefined reference to `xpt_done' |> umass.o: In function `umass_cam_cb': |> umass.o(.text+0x202b): undefined reference to `xpt_done' |> umass.o: In function `umass_cam_sense_cb': |> umass.o(.text+0x2191): undefined reference to `xpt_done' |> umass.o: In function `umass_cam_quirk_cb': |> umass.o(.text+0x21bb): undefined reference to `xpt_done' |> *** Error code 1 |> |> Thanks for your help. |> mess-mate |> Thanks for your help. Problem semi-solved. Disabled 'umass' in the kernel and all goes well. I don't know whar the requirements are for 'umass', what's this beast ?? mess-mate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kernel-building error
Thanks Marc. Next time I'll read the config file better. A+ mess-mate On Fri, 8 Aug 2003 14:59:46 -0700 Mark Woodson <[EMAIL PROTECTED]> wrote: |On Friday 08 August 2003 12:47 pm, mess-mate wrote: |> |> umass.o: In function `umass_cam_quirk_cb': |> |> umass.o(.text+0x21bb): undefined reference to `xpt_done' |> |> *** Error code 1 |> |> |> |> Thanks for your help. |> |> mess-mate |> |> Thanks for your help. |> Problem semi-solved. Disabled 'umass' in the kernel and all |> goes well. |> I don't know whar the requirements are for 'umass', what's |> this beast ?? | |umass is USB mass storage (a usb hard drive). | |The requirements for umass are: scbus and da (scsi bus and scsi direct |access) as the line states in the kernel config file |device umass # Disks/Mass storage - Requires scbus and da | |The requirements for a device or option are listed in the config file. |generally. | |-Mark | |___ |[EMAIL PROTECTED] mailing list |http://lists.freebsd.org/mailman/listinfo/freebsd-questions |To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kernel-building error
On Fri, Aug 08, 2003 at 09:47:49PM +0200, mess-mate wrote: > |That you deleted options without reading what is required. Read the > |requirements for umass in the USB section and reactivate the required > |pieces. > | > |Kent > Thanks for your help. > Problem semi-solved. Disabled 'umass' in the kernel and all > goes well. > I don't know whar the requirements are for 'umass', what's > this beast ?? As Kent said, read the comments next to the umass entry. Kris pgp0.pgp Description: PGP signature
Re: kernel-building error
On Friday 08 August 2003 07:10 am, mess-mate wrote: > Hi, > An error occurs when building my kernel :( > What does this mean ?? : That you deleted options without reading what is required. Read the requirements for umass in the USB section and reactivate the required pieces. Kent > > linking kernel > umass.o: In function `umass_cam_attach_sim': > umass.o(.text+0x17c7): undefined reference to `cam_simq_alloc' > umass.o(.text+0x1818): undefined reference to `cam_sim_alloc' > umass.o(.text+0x1827): undefined reference to `cam_simq_free' > umass.o(.text+0x1847): undefined reference to `xpt_bus_register' > umass.o: In function `umass_cam_rescan_callback': > umass.o(.text+0x1883): undefined reference to `xpt_free_path' > umass.o: In function `umass_cam_rescan': > umass.o(.text+0x18f5): undefined reference to `xpt_periph' > umass.o(.text+0x1904): undefined reference to `xpt_create_path' > umass.o(.text+0x1920): undefined reference to `xpt_setup_ccb' > umass.o(.text+0x193d): undefined reference to `xpt_action' > umass.o: In function `umass_cam_detach_sim': > umass.o(.text+0x1a2c): undefined reference to `xpt_bus_deregister' > umass.o(.text+0x1a48): undefined reference to `cam_sim_free' > umass.o: In function `umass_cam_action': > umass.o(.text+0x1ebd): undefined reference to `xpt_done' > umass.o: In function `umass_cam_cb': > umass.o(.text+0x202b): undefined reference to `xpt_done' > umass.o: In function `umass_cam_sense_cb': > umass.o(.text+0x2191): undefined reference to `xpt_done' > umass.o: In function `umass_cam_quirk_cb': > umass.o(.text+0x21bb): undefined reference to `xpt_done' > *** Error code 1 > > Thanks for your help. > mess-mate > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kernel-building error
On Friday 08 August 2003 12:47 pm, mess-mate wrote: > |> umass.o: In function `umass_cam_quirk_cb': > |> umass.o(.text+0x21bb): undefined reference to `xpt_done' > |> *** Error code 1 > |> > |> Thanks for your help. > |> mess-mate > > Thanks for your help. > Problem semi-solved. Disabled 'umass' in the kernel and all > goes well. > I don't know whar the requirements are for 'umass', what's > this beast ?? umass is USB mass storage (a usb hard drive). The requirements for umass are: scbus and da (scsi bus and scsi direct access) as the line states in the kernel config file device umass # Disks/Mass storage - Requires scbus and da The requirements for a device or option are listed in the config file. generally. -Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
kernel-building error
Hi, An error occurs when building my kernel :( What does this mean ?? : linking kernel umass.o: In function `umass_cam_attach_sim': umass.o(.text+0x17c7): undefined reference to `cam_simq_alloc' umass.o(.text+0x1818): undefined reference to `cam_sim_alloc' umass.o(.text+0x1827): undefined reference to `cam_simq_free' umass.o(.text+0x1847): undefined reference to `xpt_bus_register' umass.o: In function `umass_cam_rescan_callback': umass.o(.text+0x1883): undefined reference to `xpt_free_path' umass.o: In function `umass_cam_rescan': umass.o(.text+0x18f5): undefined reference to `xpt_periph' umass.o(.text+0x1904): undefined reference to `xpt_create_path' umass.o(.text+0x1920): undefined reference to `xpt_setup_ccb' umass.o(.text+0x193d): undefined reference to `xpt_action' umass.o: In function `umass_cam_detach_sim': umass.o(.text+0x1a2c): undefined reference to `xpt_bus_deregister' umass.o(.text+0x1a48): undefined reference to `cam_sim_free' umass.o: In function `umass_cam_action': umass.o(.text+0x1ebd): undefined reference to `xpt_done' umass.o: In function `umass_cam_cb': umass.o(.text+0x202b): undefined reference to `xpt_done' umass.o: In function `umass_cam_sense_cb': umass.o(.text+0x2191): undefined reference to `xpt_done' umass.o: In function `umass_cam_quirk_cb': umass.o(.text+0x21bb): undefined reference to `xpt_done' *** Error code 1 Thanks for your help. mess-mate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Kernel building
Try: # cd /usr/src # make buildkernel KERNCONF=YOURKERNEL # make installkernel KERNCONF=YOURKERNEL - Original Message - From: "Paul &" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, June 22, 2003 8:31 PM Subject: Kernel building > I'm trying to build a custom kernel that I can eventually include a device > for a (built in the mother board) sound controller. > > I tried several time and added back some devices which I think I don't need > just to see if the kernel will make, however, it doesn't. > > I followed the directions in the handbook > # /usr/sbin/config MYKERNEL > # cd ../../compile/MYKERNEL > # make depend > # make (fails here with Error code 1) > > I'm running FreeBSD 4.8-RELEASE > > I'm attaching MYKERNEL with hopes someone can help. > > Thanks > Paul Calabrese > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Kernel building
On Sun, Jun 22, 2003 at 07:31:54PM -0400, Paul & wrote: > I'm trying to build a custom kernel that I can eventually include a device > for a (built in the mother board) sound controller. > > I tried several time and added back some devices which I think I don't need > just to see if the kernel will make, however, it doesn't. > > I followed the directions in the handbook > # /usr/sbin/config MYKERNEL > # cd ../../compile/MYKERNEL > # make depend > # make (fails here with Error code 1) > > I'm running FreeBSD 4.8-RELEASE > > I'm attaching MYKERNEL with hopes someone can help. You forgot to include the error. Kris pgp0.pgp Description: PGP signature
Kernel building
I'm trying to build a custom kernel that I can eventually include a device for a (built in the mother board) sound controller. I tried several time and added back some devices which I think I don't need just to see if the kernel will make, however, it doesn't. I followed the directions in the handbook # /usr/sbin/config MYKERNEL # cd ../../compile/MYKERNEL # make depend # make (fails here with Error code 1) I'm running FreeBSD 4.8-RELEASE I'm attaching MYKERNEL with hopes someone can help. Thanks Paul Calabrese # # MYKERNEL - kernel configuration file for FreeBSD/i386 with sound added # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # #http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $FreeBSD: src/sys/i386/conf/MYKERNEL 1.246.2.51.2.2 2003/03/25 23:35:15 jhb Exp $ machine i386 cpu I686_CPU ident MYKERNEL maxusers0 makeoptions DEBUG=-g#Build kernel with gdb(1) debug symbols #optionsMATH_EMULATE#Support for x87 emulation options INET#InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT#FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options UFS_DIRHASH #Improve performance on big directories options MFS #Memory Filesystem options MD_ROOT #MD is a potential root device options NFS #Network Filesystem #optionsNFS_ROOT#NFS usable as root device, NFS required options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root, CD9660 required options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] #optionsSCSI_DELAY=15000#Delay (in ms) before probing SCSI options UCONSOLE#Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B#Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM#Rate limit bad replies options KBD_INSTALL_CDEV# install a CDEV entry in /dev options AHC_REG_PRETTY_PRINT# Print register bitfields in debug # output. Adds ~128k to driver. options AHD_REG_PRETTY_PRINT# Print register bitfields in debug # output. Adds ~215k to driver. # To make an SMP kernel, the next two are needed #optionsSMP # Symmetric MultiProcessor Kernel #optionsAPIC_IO # Symmetric (APIC) I/O # To support HyperThreading, HTT is needed in addition to SMP and APIC_IO #optionsHTT # HyperThreading Technology device isa device eisa device pci # Floppy drives device fdc0at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 #device fd1 at fdc0 drive 1 # # If you have a Toshiba Libretto with its Y-E Data PCMCIA floppy, # don't use the above line for fdc0 but the following one: #device fdc0 # ATA and ATAPI devices device ata0at isa? port IO_WD1 irq 14 device ata1at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering # SCSI Controllers #device ahb # EISA AHA1742 family #device ahc # AHA2940 and
Re: Kernel Building
On Sun, Nov 03, 2002 at 11:03:17PM -0600, Ryan Sommers wrote: > I'm assuming it's possible to build a kernel for a different computer > then it's compiled on as long as they are the same architecture. How do > I go about compiling my kernel for my laptop on my desktop? First I > don't think the laptop could hold the source and more importantly I > think the 850 box will compile it faster then the 200mhz laptop. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/small-lan.html First make sure that /etc/make.conf settings are compatible with both machines --- pay particular attention to the CPUTYPE variable. Copy the /etc/make.conf file to both machines. Copy the kernel config for your laptop into /usr/src/sys/i386/conf on the build machine. To build a kernel for the laptop, log into the build machine and just: cd /usr/src make buildkernel KERNCONF=LAPTOP then NFS mount the /usr/src and /usr/obj directories on the laptop, and (while logged into the laptop) run: make installkernel KERNCONF=LAPTOP You'll want to do likewise with buildworld and installworld so the kernel and userland are in synch on both machines, obviously. As a convenience, on the build machine you can set KERNCONF to a list of kernel configs. All will be built, but the first one is assumed to be the build machine's own config. It's quite handy to add the correct KERNCONF setting to /etc/make.conf on each machine. eg. KERNCONF = BUILDBOX LAPTOP on the build box, and KERNCONF = LAPTOP on the laptop. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Kernel Building
I'm assuming it's possible to build a kernel for a different computer then it's compiled on as long as they are the same architecture. How do I go about compiling my kernel for my laptop on my desktop? First I don't think the laptop could hold the source and more importantly I think the 850 box will compile it faster then the 200mhz laptop. -- Ryan "leadZERO" Sommers Gamer's Impact President [EMAIL PROTECTED] ICQ: 1019590 AIM/MSN: leadZERO -= http://www.gamersimpact.com =- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
