The kernel is angry!

[Weaseal]

So I am attempting a source upgrade from FreeBSD 6.3 to FreeBSD 7.0-p3, and the world and kernel compiled fine, but when I ran make installkernel:
===> zyd (install)
install -o root -g wheel -m 555 if_zyd.ko /boot/kernel
install -o root -g wheel -m 555 if_zyd.ko.symbols /boot/kernel
kldxref /boot/kernel
kldxref: file isn't dynamically-linked
kldxref: unknown metdata record 0 in file aac.ko.symbols
kldxref: unknown metdata record 0 in file aac.ko.symbols
kldxref: unknown metdata record 0 in file aac.ko.symbols
kldxref: unknown metdata record 0 in file aac.ko.symbols
...
kldxref: unknown metdata record 0 in file wlan_ccmp.ko.symbols
kldxref: unknown metdata record 0 in file wlan_tkip.ko.symbols
kldxref: unknown metdata record 0 in file wlan_tkip.ko.symbols
kldxref: unknown metdata record 0 in file wlan_tkip.ko.symbols
kldxref: unknown metdata record 0 in file wlan_wep.ko.symbols
kldxref: unknown metdata record 0 in file wlan_wep.ko.symbols
kldxref: unknown metdata record 0 in file wlan_wep.ko.symbols
kldxref: unknown metdata record 0 in file wlan_xauth.ko.symbols
kldxref: unknown metdata record 0 in file wlan_xauth.ko.symbols
kldxref: unknown metdata record 0 in file wlan_xauth.ko.symbols
kldxref: unknown metdata record 0 in file if_wpi.ko.symbols
kldxref: unknown metdata record 0 in file if_wpi.ko.symbols
kldxref: unknown metdata record 0 in file if_wpi.ko.symbols
kldxref: unknown metdata record 0 in file if_wpi.ko.symbols
kldxref: unknown metdata record 0 in file if_wpi.ko.symbols
kldxref: unknown metdata record 0 in file wpifw.ko.symbols
kldxref: unknown metdata record 0 in file wpifw.ko.symbols
kldxref: unknown metdata record 0 in file wpifw.ko.symbols
kldxref: unknown metdata record 0 in file xfs.ko.symbols
kldxref: unknown metdata record 0 in file if_xl.ko.symbols
kldxref: unknown metdata record 0 in file if_xl.ko.symbols
kldxref: unknown metdata record 0 in file if_xl.ko.symbols
kldxref: unknown metdata record 0 in file if_xl.ko.symbols
kldxref: unknown metdata record 0 in file if_xl.ko.symbols
kldxref: unknown metdata record 0 in file if_xl.ko.symbols
kldxref: unknown metdata record 0 in file zfs.ko.symbols
kldxref: unknown metdata record 0 in file zfs.ko.symbols
kldxref: unknown metdata record 0 in file zfs.ko.symbols
kldxref: unknown metdata record 0 in file zfs.ko.symbols
kldxref: unknown metdata record 0 in file zlib.ko.symbols
kldxref: unknown metdata record 0 in file zlib.ko.symbols
kldxref: unknown metdata record 0 in file if_zyd.ko.symbols
kldxref: unknown metdata record 0 in file if_zyd.ko.symbols
kldxref: unknown metdata record 0 in file if_zyd.ko.symbols
kldxref: unknown metdata record 0 in file if_zyd.ko.symbolsThere were a lot more of these lines but daemonforums kept saying my message was 'too short' if I posted the whole thing...

Is it okay to continue (reboot) or will this break my system? My machine is far away and I can't fix it for ~3 months if it won't boot.
My kernel config:$ cat RELNKERN7

cpu HAMMER
ident GENERIC

# 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

options SCHED_ULE # 4BSD scheduler
options PREEMPTION # Enable kernel thread preemption
options INET # InterNETworking
options INET6 # IPv6 communications protocols
options SCTP # Stream Control Transmission Protocol
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 UFS_GJOURNAL # Enable gjournal-based UFS journaling
options MD_ROOT # MD is a potential root device
options NFSCLIENT # Network Filesystem Client
options NFSSERVER # Network Filesystem Server
options NFS_ROOT # NFS usable as /, requires NFSCLIENT
options NTFS # NT File System
options MSDOSFS # MSDOS Filesystem
options CD9660 # ISO 9660 Filesystem
options PROCFS # Process filesystem (requires PSEUDOFS)
options PSEUDOFS # Pseudo-filesystem framework
options GEOM_PART_GPT # GUID Partition Tables.
options GEOM_LABEL # Provides labelization
options COMPAT_43TTY # BSD 4.3 TTY compat [KEEP THIS!]
options COMPAT_IA32 # Compatible with i386 binaries
#options COMPAT_FREEBSD4 # Compatible with FreeBSD4
#options COMPAT_FREEBSD5 # Compatible with FreeBSD5
options COMPAT_FREEBSD6 # Compatible with FreeBSD6
options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI
options KTRACE # ktrace(1) support
options SYSVSHM # SYSV-style shared memory
options SYSVMSG # SYSV-style message queues
options SYSVSEM # SYSV-style semaphores
options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions
options KBD_INSTALL_CDEV # install a CDEV entry in /dev
options ADAPTIVE_GIANT # Giant mutex is adaptive.
options STOP_NMI # Stop CPUS using NMI instead of IPI
options AUDIT # Security event auditing

# Make an SMP-capable kernel by default
#options SMP # Symmetric MultiProcessor Kernel

# CPU frequency control
device cpufreq

# Bus support.
device acpi
device pci

# Floppy drives
device fdc

# ATA and ATAPI devices
device ata
device atadisk # ATA disk drives
device ataraid # ATA RAID 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 ahc # AHA2940 and onboard AIC7xxx devices
#options AHC_REG_PRETTY_PRINT # Print register bitfields in debug
# output. Adds ~128k to driver.
#device ahd # AHA39320/29320 and onboard AIC79xx devices
#options AHD_REG_PRETTY_PRINT # Print register bitfields in debug
# output. Adds ~215k to driver.
#device amd # AMD 53C974 (Tekram DC-390(T))
#device hptiop # Highpoint RocketRaid 3xxx series
#device isp # Qlogic family
#device ispfw # Firmware for QLogic HBAs- normally a module
#device mpt # LSI-Logic MPT-Fusion
#device ncr # NCR/Symbios Logic
#device sym # NCR/Symbios Logic (newer chipsets + those of `ncr')
#device trm # Tekram DC395U/UW/F DC315U adapters

#device adv # Advansys SCSI adapters
#device adw # Advansys wide SCSI adapters
#device aic # Adaptec 15[012]x SCSI adapters, AIC-6[23]60.
#device bt # Buslogic/Mylex MultiMaster SCSI adapters


# SCSI peripherals
device scbus # SCSI bus (required for SCSI)
#device ch # SCSI media changers
device da # Direct Access (disks)
#device sa # Sequential Access (tape etc)
#device cd # CD
device pass # Passthrough device (direct SCSI access)
#device ses # SCSI Environmental Services (and SAF-TE)

# RAID controllers interfaced to the SCSI subsystem
#device amr # AMI MegaRAID
#device arcmsr # Areca SATA II RAID
#device ciss # Compaq Smart RAID 5*
#device dpt # DPT Smartcache III, IV - See NOTES for options
#device hptmv # Highpoint RocketRAID 182x
#device hptrr # Highpoint RocketRAID 17xx, 22xx, 23xx, 25xx
#device iir # Intel Integrated RAID
#device ips # IBM (Adaptec) ServeRAID
#device mly # Mylex AcceleRAID/eXtremeRAID
#device twa # 3ware 9000 series PATA/SATA RAID

# RAID controllers
#device aac # Adaptec FSA RAID
#device aacp # SCSI passthrough for aac (requires CAM)
#device ida # Compaq Smart RAID
#device mfi # LSI MegaRAID SAS
#device mlx # Mylex DAC960 family
#XXX pointer/int warnings
#device pst # Promise Supertrak SX6000
#device twe # 3ware ATA RAID

# atkbdc0 controls both the keyboard and the PS/2 mouse
device atkbdc # AT keyboard controller
device atkbd # AT keyboard
device psm # PS/2 mouse

device kbdmux # keyboard multiplexer

device vga # VGA video card driver

device splash # Splash screen and screen saver support

# syscons is the default console driver, resembling an SCO console
device sc

device agp # support several AGP chipsets

# PCCARD (PCMCIA) support
# PCMCIA and cardbus bridge support
#device cbb # cardbus (yenta) bridge
#device pccard # PC Card (16-bit) bus
#device cardbus # CardBus (32-bit) bus

# Serial (COM) ports
#device sio # 8250, 16[45]50 based serial ports
#device uart # Generic UART driver

# Parallel port
#device ppc
#device ppbus # Parallel port bus (required)
#device lpt # Printer
#device plip # TCP/IP over parallel
#device ppi # Parallel port interface device
#device vpo # Requires scbus and da

# If you've got a "dumb" serial or parallel PCI card that is
# supported by the puc(4) glue driver, uncomment the following
# line to enable it (connects to sio, uart and/or ppc drivers):
#device puc

# PCI Ethernet NICs.
#device de # DEC/Intel DC21x4x (``Tulip'')
#device em # Intel PRO/1000 adapter Gigabit Ethernet Card
#device ixgb # Intel PRO/10GbE Ethernet Card
#device le # AMD Am7900 LANCE and Am79C9xx PCnet
#device txp # 3Com 3cR990 (``Typhoon'')
#device vx # 3Com 3c590, 3c595 (``Vortex'')

# PCI Ethernet NICs that use the common MII bus controller code.
# NOTE: Be sure to keep the 'device miibus' line in order to use these NICs!
device miibus # MII bus support
#device bce # Broadcom BCM5706/BCM5708 Gigabit Ethernet
#device bfe # Broadcom BCM440x 10/100 Ethernet
#device bge # Broadcom BCM570xx Gigabit Ethernet
device dc # DEC/Intel 21143 and various workalikes
#device fxp # Intel EtherExpress PRO/100B (82557, 82558)
#device lge # Level 1 LXT1001 gigabit Ethernet
#device msk # Marvell/SysKonnect Yukon II Gigabit Ethernet
#device nfe # nVidia nForce MCP on-board Ethernet
#device nge # NatSemi DP83820 gigabit Ethernet
#device nve # nVidia nForce MCP on-board Ethernet Networking
#device pcn # AMD Am79C97x PCI 10/100 (precedence over 'le')
device re # RealTek 8139C+/8169/8169S/8110S
#device rl # RealTek 8129/8139
#device sf # Adaptec AIC-6915 (``Starfire'')
#device sis # Silicon Integrated Systems SiS 900/SiS 7016
#device sk # SysKonnect SK-984x & SK-982x gigabit Ethernet
#device ste # Sundance ST201 (D-Link DFE-550TX)
#device ti # Alteon Networks Tigon I/II gigabit Ethernet
#device tl # Texas Instruments ThunderLAN
#device tx # SMC EtherPower II (83c170 ``EPIC'')
#device vge # VIA VT612x gigabit Ethernet
#device vr # VIA Rhine, Rhine II
#device wb # Winbond W89C840F
#device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'')

# ISA Ethernet NICs. pccard NICs included.
#device cs # Crystal Semiconductor CS89x0 NIC
# 'device ed' requires 'device miibus'
#device ed # NE[12]000, SMC Ultra, 3c503, DS8390 cards
#device ex # Intel EtherExpress Pro/10 and Pro/10+
#device ep # Etherlink III based cards
#device fe # Fujitsu MB8696x based cards
#device sn # SMC's 9000 series of Ethernet chips
#device xe # Xircom pccard Ethernet

# Wireless NIC cards
#device wlan # 802.11 support
#device wlan_wep # 802.11 WEP support
#device wlan_ccmp # 802.11 CCMP support
#device wlan_tkip # 802.11 TKIP support
#device wlan_amrr # AMRR transmit rate control algorithm
#device wlan_scan_ap # 802.11 AP mode scanning
#device wlan_scan_sta # 802.11 STA mode scanning
#device an # Aironet 4500/4800 802.11 wireless NICs.
#device ath # Atheros pci/cardbus NIC's
#device ath_hal # Atheros HAL (Hardware Access Layer)
#device ath_rate_sample # SampleRate tx rate control for ath
#device awi # BayStack 660 and others
#device ral # Ralink Technology RT2500 wireless NICs.
#device wi # WaveLAN/Intersil/Symbol 802.11 wireless NICs.

# Pseudo devices.
device loop # Network loopback
device random # Entropy device
device ether # Ethernet support
device sl # Kernel SLIP
device ppp # Kernel PPP
device tun # Packet tunnel.
device pty # Pseudo-ttys (telnet etc)
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
device uhci # UHCI PCI->USB interface
device ohci # OHCI PCI->USB interface
device ehci # EHCI PCI->USB interface (USB 2.0)
device usb # USB Bus (required)
device udbp # USB Double Bulk Pipe devices
device ugen # Generic
device uhid # "Human Interface Devices"
device ukbd # Keyboard
device ulpt # Printer
device umass # Disks/Mass storage - Requires scbus and da
device ums # Mouse
#device ural # Ralink Technology RT2500USB wireless NICs
#device urio # Diamond Rio 500 MP3 player
#device uscanner # Scanners
# 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

# FireWire support
#device firewire # FireWire bus code
#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

# I forgot what this is for but I added it so I must need it...
options NETGRAPH # for udbp (USB double-pipe driver)

# These are for OpenVPN
device tap # virtual ethernet device

[killasmurf86]

Dude you configured kernel wrong from start :)
wtf is this:

cpu HAMMER
ident GENERIC


it should be (i assume you have x86 system):

machine i386
cpu I686_CPU
ident MyPcWhateverYouCalllIt

If you have older than Pentium machine, use I586_CPU or I486_CPU

And Save your config as MyPcWhateverYouCalllIt

cd to /usr/src and:

make kernel KERNCONF=MyPcWhateverYouCallIt

and then reboot (with luck it would work fine)

In case you are afraid that your kernel might not boot
just compile GENERIC kernel


http://www2.lv.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html
http://www2.lv.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-custom-kernel.html


P.S. Nice topic name :)

[Weaseal]

This is an amd64 machine. I noticed that my old 6.x kernel had such a 'machine amd64' line but the GENERIC /usr/src/sys/amd64/conf/GENERIC had no such line so I figured it had been knocked out for 7.x. Are you sure that is valid for 7.x?

[killasmurf86]

Oh, I think it's ok, cause it's separate architecture
currently i can't tell much about it, cause i'm on win machine....

Try it
but then use
make buildkernel KERNCONF=.....
make installkernel KERNCONF=.....

If it fails use machine i386

Note that you have to do this in /usr/src/sys/amd64/conf/
or for 2nd chouse /usr/src/sys/i386/conf/
(i'm guessing, i never configured kernel for other than i386, but i think it's right)

[Weaseal]

Yes, that is precisely how I compiled it.
Any other ideas?

[killasmurf86]

Yes, that is precisely how I compiled it.
Any other ideas?

did you already fixed what i posted in 1st post?

also show me 1st few lines of generic amd64 kernel

[Weaseal]

No I didn't add any 'machine' lines, I figured adding things that didn't exist in the GENERIC kernel would be a bad idea. Right now I'm recompiling with GENERIC just to have something.

Here's its config:$ cat /usr/src/sys/amd64/conf/GENERIC
#
# GENERIC -- Generic kernel configuration file for FreeBSD/amd64
#
# 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/amd64/conf/GENERIC,v 1.484.2.2.2.1 2008/02/06 03:24:28 scottl Exp $

cpu HAMMER
ident GENERIC

# 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

options SCHED_4BSD # 4BSD scheduler
options PREEMPTION # Enable kernel thread preemption
options INET # InterNETworking
options INET6 # IPv6 communications protocols
options SCTP # Stream Control Transmission Protocol
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 UFS_GJOURNAL # Enable gjournal-based UFS journaling
options MD_ROOT # MD is a potential root device
options NFSCLIENT # Network Filesystem Client
options NFSSERVER # Network Filesystem Server
options NFS_ROOT # NFS usable as /, requires NFSCLIENT
options NTFS # NT File System
options MSDOSFS # MSDOS Filesystem
options CD9660 # ISO 9660 Filesystem
options PROCFS # Process filesystem (requires PSEUDOFS)
options PSEUDOFS # Pseudo-filesystem framework
options GEOM_PART_GPT # GUID Partition Tables.
options GEOM_LABEL # Provides labelization
options COMPAT_43TTY # BSD 4.3 TTY compat [KEEP THIS!]
options COMPAT_IA32 # Compatible with i386 binaries
options COMPAT_FREEBSD4 # Compatible with FreeBSD4
options COMPAT_FREEBSD5 # Compatible with FreeBSD5
options COMPAT_FREEBSD6 # Compatible with FreeBSD6
options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI
options KTRACE # ktrace(1) support
options SYSVSHM # SYSV-style shared memory
options SYSVMSG # SYSV-style message queues
options SYSVSEM # SYSV-style semaphores
options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions
options KBD_INSTALL_CDEV # install a CDEV entry in /dev
options ADAPTIVE_GIANT # Giant mutex is adaptive.
options STOP_NMI # Stop CPUS using NMI instead of IPI
options AUDIT # Security event auditing

# Make an SMP-capable kernel by default
options SMP # Symmetric MultiProcessor Kernel

# CPU frequency control
device cpufreq

# Bus support.
device acpi
device pci

# Floppy drives
device fdc

# ATA and ATAPI devices
device ata
device atadisk # ATA disk drives
device ataraid # ATA RAID 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 ahc # AHA2940 and onboard AIC7xxx devices
options AHC_REG_PRETTY_PRINT # Print register bitfields in debug
# output. Adds ~128k to driver.
device ahd # AHA39320/29320 and onboard AIC79xx devices
options AHD_REG_PRETTY_PRINT # Print register bitfields in debug
# output. Adds ~215k to driver.
device amd # AMD 53C974 (Tekram DC-390(T))
device hptiop # Highpoint RocketRaid 3xxx series
device isp # Qlogic family
#device ispfw # Firmware for QLogic HBAs- normally a module
device mpt # LSI-Logic MPT-Fusion
#device ncr # NCR/Symbios Logic
device sym # NCR/Symbios Logic (newer chipsets + those of `ncr')
device trm # Tekram DC395U/UW/F DC315U adapters

device adv # Advansys SCSI adapters
device adw # Advansys wide SCSI adapters
device aic # Adaptec 15[012]x SCSI adapters, AIC-6[23]60.
device bt # Buslogic/Mylex MultiMaster SCSI adapters


# SCSI peripherals
device scbus # SCSI bus (required for SCSI)
device ch # SCSI media changers
device da # Direct Access (disks)
device sa # Sequential Access (tape etc)
device cd # CD
device pass # Passthrough device (direct SCSI access)
device ses # SCSI Environmental Services (and SAF-TE)

# RAID controllers interfaced to the SCSI subsystem
device amr # AMI MegaRAID
device arcmsr # Areca SATA II RAID
device ciss # Compaq Smart RAID 5*
device dpt # DPT Smartcache III, IV - See NOTES for options
device hptmv # Highpoint RocketRAID 182x
device hptrr # Highpoint RocketRAID 17xx, 22xx, 23xx, 25xx
device iir # Intel Integrated RAID
device ips # IBM (Adaptec) ServeRAID
device mly # Mylex AcceleRAID/eXtremeRAID
device twa # 3ware 9000 series PATA/SATA RAID

# RAID controllers
device aac # Adaptec FSA RAID
device aacp # SCSI passthrough for aac (requires CAM)
device ida # Compaq Smart RAID
device mfi # LSI MegaRAID SAS
device mlx # Mylex DAC960 family
#XXX pointer/int warnings
#device pst # Promise Supertrak SX6000
device twe # 3ware ATA RAID

# atkbdc0 controls both the keyboard and the PS/2 mouse
device atkbdc # AT keyboard controller
device atkbd # AT keyboard
device psm # PS/2 mouse

device kbdmux # keyboard multiplexer

device vga # VGA video card driver

device splash # Splash screen and screen saver support

# syscons is the default console driver, resembling an SCO console
device sc

device agp # support several AGP chipsets

# PCCARD (PCMCIA) support
# PCMCIA and cardbus bridge support
device cbb # cardbus (yenta) bridge
device pccard # PC Card (16-bit) bus
device cardbus # CardBus (32-bit) bus

# Serial (COM) ports
device sio # 8250, 16[45]50 based serial ports
device uart # Generic UART driver

# Parallel port
device ppc
device ppbus # Parallel port bus (required)
device lpt # Printer
device plip # TCP/IP over parallel
device ppi # Parallel port interface device
#device vpo # Requires scbus and da

# If you've got a "dumb" serial or parallel PCI card that is
# supported by the puc(4) glue driver, uncomment the following
# line to enable it (connects to sio, uart and/or ppc drivers):
#device puc

# PCI Ethernet NICs.
device de # DEC/Intel DC21x4x (``Tulip'')
device em # Intel PRO/1000 adapter Gigabit Ethernet Card
device ixgb # Intel PRO/10GbE Ethernet Card
device le # AMD Am7900 LANCE and Am79C9xx PCnet
device txp # 3Com 3cR990 (``Typhoon'')
device vx # 3Com 3c590, 3c595 (``Vortex'')

# PCI Ethernet NICs that use the common MII bus controller code.
# NOTE: Be sure to keep the 'device miibus' line in order to use these NICs!
device miibus # MII bus support
device bce # Broadcom BCM5706/BCM5708 Gigabit Ethernet
device bfe # Broadcom BCM440x 10/100 Ethernet
device bge # Broadcom BCM570xx Gigabit Ethernet
device dc # DEC/Intel 21143 and various workalikes
device fxp # Intel EtherExpress PRO/100B (82557, 82558)
device lge # Level 1 LXT1001 gigabit Ethernet
device msk # Marvell/SysKonnect Yukon II Gigabit Ethernet
device nfe # nVidia nForce MCP on-board Ethernet
device nge # NatSemi DP83820 gigabit Ethernet
#device nve # nVidia nForce MCP on-board Ethernet Networking
device pcn # AMD Am79C97x PCI 10/100 (precedence over 'le')
device re # RealTek 8139C+/8169/8169S/8110S
device rl # RealTek 8129/8139
device sf # Adaptec AIC-6915 (``Starfire'')
device sis # Silicon Integrated Systems SiS 900/SiS 7016
device sk # SysKonnect SK-984x & SK-982x gigabit Ethernet
device ste # Sundance ST201 (D-Link DFE-550TX)
device ti # Alteon Networks Tigon I/II gigabit Ethernet
device tl # Texas Instruments ThunderLAN
device tx # SMC EtherPower II (83c170 ``EPIC'')
device vge # VIA VT612x gigabit Ethernet
device vr # VIA Rhine, Rhine II
device wb # Winbond W89C840F
device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'')

# ISA Ethernet NICs. pccard NICs included.
device cs # Crystal Semiconductor CS89x0 NIC
# 'device ed' requires 'device miibus'
device ed # NE[12]000, SMC Ultra, 3c503, DS8390 cards
device ex # Intel EtherExpress Pro/10 and Pro/10+
device ep # Etherlink III based cards
device fe # Fujitsu MB8696x based cards
device sn # SMC's 9000 series of Ethernet chips
device xe # Xircom pccard Ethernet

# Wireless NIC cards
device wlan # 802.11 support
device wlan_wep # 802.11 WEP support
device wlan_ccmp # 802.11 CCMP support
device wlan_tkip # 802.11 TKIP support
device wlan_amrr # AMRR transmit rate control algorithm
device wlan_scan_ap # 802.11 AP mode scanning
device wlan_scan_sta # 802.11 STA mode scanning
device an # Aironet 4500/4800 802.11 wireless NICs.
device ath # Atheros pci/cardbus NIC's
device ath_hal # Atheros HAL (Hardware Access Layer)
device ath_rate_sample # SampleRate tx rate control for ath
device awi # BayStack 660 and others
device ral # Ralink Technology RT2500 wireless NICs.
device wi # WaveLAN/Intersil/Symbol 802.11 wireless NICs.

# Pseudo devices.
device loop # Network loopback
device random # Entropy device
device ether # Ethernet support
device sl # Kernel SLIP
device ppp # Kernel PPP
device tun # Packet tunnel.
device pty # Pseudo-ttys (telnet etc)
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
device uhci # UHCI PCI->USB interface
device ohci # OHCI PCI->USB interface
device ehci # EHCI PCI->USB interface (USB 2.0)
device usb # USB Bus (required)
#device udbp # USB Double Bulk Pipe devices
device ugen # Generic
device uhid # "Human Interface Devices"
device ukbd # Keyboard
device ulpt # Printer
device umass # Disks/Mass storage - Requires scbus and da
device ums # Mouse
device ural # Ralink Technology RT2500USB wireless NICs
device urio # Diamond Rio 500 MP3 player
device uscanner # Scanners
# 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

# FireWire support
device firewire # FireWire bus code
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

[killasmurf86]

OK that is fine. :)
So did you managed to compile generic?

For custom kernel just change ident to something and save it with same filename (you probably know this)


Also you might want to

# cd /usr/src/sys/amd64/conf/
# make LINT

and check if....
you might find some useful info (options, without description)


Also show me your /etc/make.conf

[Weaseal]

The kernel is still building (slow machine, 1 processor, 1 core).$ cat /etc/make.conf
CFLAGS=-O2 -pipe
COPTFLAGS=-O2 -pipe
CPUTYPE?=athlon64

#buildworld stuff
NO_BLUETOOTH=true
NO_GAMES=true
NO_I4B=true
NO_PROFILE=true
# added by use.perl 2007-12-22 16:10:34
PERL_VER=5.8.8
PERL_VERSION=5.8.8

[killasmurf86]

Comment out

CFLAGS=-O2 -pipe
COPTFLAGS=-O2 -pipe

They will break things...
there are more of them by default then you typed.
No need to reenter default values

this might actually solve the problem

[Carpetsmoker]

It would seem that this is harmless:
http://lists.freebsd.org/pipermail/cvs-all/2005-October/142330.html

Assuming you don't need debug symbols, you can remove ``makeoptions DEBUG=-g'', which would make the warnings go away (And speed up builds a bit too).

This is an amd64 machine. I noticed that my old 6.x kernel had such a 'machine amd64' line but the GENERIC /usr/src/sys/amd64/conf/GENERIC had no such line so I figured it had been knocked out for 7.x. Are you sure that is valid for 7.x?

The ``machine xyz'' line is no longer needed in FreeBSD 7, using ``cpu xyz'' is enough.

Comment out

CFLAGS=-O2 -pipe
COPTFLAGS=-O2 -pipe

They will break things...

No, this won't do any good, the default CFLAGS are ``-fno-strict-aliasing -O2 -pipe''

In addition, CFLAGS is not used for kernel builds anyway.

[phoenix]

Dude you configured kernel wrong from start :)
wtf is this:

cpu HAMMER
ident GENERIC


No, no, no, no, no. If he does that, he will have a useless system. If you've never used a 64-bit install of FreeBSD, then don't give advice. Those are the correct lines for an amd64 system.

[phoenix]

This is an amd64 machine. I noticed that my old 6.x kernel had such a 'machine amd64' line but the GENERIC /usr/src/sys/amd64/conf/GENERIC had no such line so I figured it had been knocked out for 7.x. Are you sure that is valid for 7.x?

All kernels pull in the DEFAULTS file. The machine type is set in that file, along with a few other things.

[phoenix]

So I am attempting a source upgrade from FreeBSD 6.3 to FreeBSD 7.0-p3, and the world and kernel compiled fine, but when I ran make installkernel:

When doing upgrades across major versions, it's always a good idea to compile and install GENERIC. Get things installed and working, then compile a custom kernel.

Also, you can use KODIR=/boot/testkernel on the installkernel command to install the kernel to a separate directory. Then you can use the nextboot command to test boot that kernel. If it doesn't work, a reboot will use the previously working kernel.

My kernel config:$ cat RELNKERN7

cpu HAMMER
ident GENERIC


The ident line has to match the name of the kernel config file.

[TerryP]

"Hammer"m I believe was a code word or a project name used by AMD when developing the chips we nore would call 'amd64' based.



Like phoenix has said, it's usually a good idea to test with the GENERIC kernel and usually a bloody good idea to have a copy handy just in case! You can always use make.conf to control what kernels are built and installed by default,



KERNCONF=VIPER GENERIC




Will build me my custom kernel"VIPER" and the FreeBSD generic kernel during a buildkernel, then I can override KERNCONF to install the right kernel when the time comes. The first in the list is the default to be installed if you don't override KERNCONF when calling make.

[Weaseal]

make installworld for a GENERIC kernel, after being built with an empty make.conf (aside from CPUTYPE?=athlon64) results in the exact same errors.

Any other suggestions?

[Weaseal]

When doing upgrades across major versions, it's always a good idea to compile and install GENERIC. Get things installed and working, then compile a custom kernel.

Also, you can use KODIR=/boot/testkernel on the installkernel command to install the kernel to a separate directory. Then you can use the nextboot command to test boot that kernel. If it doesn't work, a reboot will use the previously working kernel.
Sweet! Thanks phoenix. I tried nextboot with the GENERIC 7 kernel that spit out all the errors and all seems well.

[Weaseal]

Update: While running the GENERIC 7 kernel, I was able to install the custom 7 kernel without the errors appearing.