Re: Intel Dual PRO/1000 Nic - Setup of shared code failed
On Jun 12, 2008, at 4:03 PM, Robert Huff wrote: Christopher Sean Hilton writes: I just got an Intel Dual gigabit nic that I planned to use with FreeBSD 7-STABLE. I'm using this on FreeBSD 7.0-CURRENT #1: Sat Apr 19 23:17:00 EDT 2008 i386 with no problems. Sounds cool. I had one going in an older laptop as early as 5.x-STABLE I'm pretty sure it's strongly supported by FreeBSD. Did you have to do anything special to get it going? -- Chris Chris Hilton tildeChris -- http://myblog.vindaloo.com email -- chris/at/vindaloo/ dot/com .~ ~ .--.~ ~.--.~~.--.~~.--.~~.--.~~.--.~~.--.~~.--.~~.--.~~.--.~~.--.~~.--.~~. I'm on the outside looking inside, What do I see? Much confusion, disillution, all around me. -- Ian McDonald / Peter Sinfield ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Intel Dual PRO/1000 Nic - Setup of shared code failed
Christopher Sean Hilton writes: I just got an Intel Dual gigabit nic that I planned to use with FreeBSD 7-STABLE. I'm using this on FreeBSD 7.0-CURRENT #1: Sat Apr 19 23:17:00 EDT 2008 i386 with no problems. Sounds cool. I had one going in an older laptop as early as 5.x-STABLE I'm pretty sure it's strongly supported by FreeBSD. Actually, the code is cotributed/maintained by Intel. Did you have to do anything special to get it going? huff@ more /boot/loader.conf | grep _em if_em_load=YES Your mileage may vary. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Intel Dual PRO/1000 Nic - Setup of shared code failed
On Jun 12, 2008, at 4:43 PM, Robert Huff wrote: Christopher Sean Hilton writes: I just got an Intel Dual gigabit nic that I planned to use with FreeBSD 7-STABLE. I'm using this on FreeBSD 7.0-CURRENT #1: Sat Apr 19 23:17:00 EDT 2008 i386 with no problems. Sounds cool. I had one going in an older laptop as early as 5.x- STABLE I'm pretty sure it's strongly supported by FreeBSD. Actually, the code is cotributed/maintained by Intel. Did you have to do anything special to get it going? huff@ more /boot/loader.conf | grep _em if_em_load=YES Your mileage may vary. Yeah, my first instinct was to assume that the em driver isn't in the GENERIC kernel to so I did this: # kldload -v if_em Which promptly fired back a bunch of errors about duplicate symbols. At that time I figured that the em module is already loaded into the GENERIC kernel. This was confirmed by doing: # grep '^device.*em' /usr/src/sys/i386/conf/GENERIC device mly # Mylex AcceleRAID/eXtremeRAID device em # Intel PRO/1000 adapter Gigabit Ethernet Card device nge # NatSemi DP83820 gigabit Ethernet ... I can try that later but given that the em driver is already in the kernel I don't expect it to bear fruit. However, can you do a kldstat on your machine with the em card? It will tell me if there is some firmware module or something that I'm missing. -- Chris P.S. In digging around on Google I found kern/117926 in the Bug tracking system. Chris Hilton e: chris|at|vindaloo| dot|com The pattern juggler lifts his hand; The orchestra begin. As slowly turns the grinding wheel in the court of the crimson king. -- Ian McDonald / Peter Sinfield ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Intel Dual PRO/1000 Nic - Setup of shared code failed
Christopher Sean Hilton writes: I can try that later but given that the em driver is already in the kernel I don't expect it to bear fruit. However, can you do a kldstat on your machine with the em card? It will tell me if there is some firmware module or something that I'm missing. huff@ kldstat Id Refs AddressSize Name 1 47 0xc040 4b9868 kernel (/boot/kernel/kernel) 22 0xc08ba000 29820linux.ko (/boot/kernel/linux.ko) 31 0xc08e4000 2839cif_em.ko (/boot/kernel/if_em.ko) 41 0xc090d000 24b4 accf_http.ko (/boot/kernel/accf_http.ko) 51 0xc091 6a808acpi.ko (/boot/kernel/acpi.ko) 61 0xc4e76000 7000 linprocfs.ko (/boot/kernel/linprocfs.ko) 71 0xc5207000 1f000nfsserver.ko (/boot/kernel/nfsserver.ko) 81 0xc5239000 a000 nfslockd.ko (/boot/kernel/nfslockd.ko) 91 0xc5244000 f000 krpc.ko (/boot/kernel/krpc.ko) P.S. In digging around on Google I found kern/117926 in the Bug tracking system. That machine has a ASUS P4B motherboard. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Intel Dual PRO/1000 Nic - Setup of shared code failed
On Jun 12, 2008, at 6:38 PM, Robert Huff wrote: Christopher Sean Hilton writes: I can try that later but given that the em driver is already in the kernel I don't expect it to bear fruit. However, can you do a kldstat on your machine with the em card? It will tell me if there is some firmware module or something that I'm missing. huff@ kldstat Id Refs AddressSize Name 1 47 0xc040 4b9868 kernel (/boot/kernel/kernel) 22 0xc08ba000 29820linux.ko (/boot/kernel/linux.ko) 31 0xc08e4000 2839cif_em.ko (/boot/kernel/if_em.ko) 41 0xc090d000 24b4 accf_http.ko (/boot/kernel/accf_http.ko) 51 0xc091 6a808acpi.ko (/boot/kernel/acpi.ko) 61 0xc4e76000 7000 linprocfs.ko (/boot/kernel/linprocfs.ko) 71 0xc5207000 1f000nfsserver.ko (/boot/kernel/nfsserver.ko) 81 0xc5239000 a000 nfslockd.ko (/boot/kernel/nfslockd.ko) 91 0xc5244000 f000 krpc.ko (/boot/kernel/krpc.ko) P.S. In digging around on Google I found kern/117926 in the Bug tracking system. That machine has a ASUS P4B motherboard. Doesn't look like there's a firmware module though. Thanks -- Chris Chris Hilton e: chris|at|vindaloo| dot|com The pattern juggler lifts his hand; The orchestra begin. As slowly turns the grinding wheel in the court of the crimson king. -- Ian McDonald / Peter Sinfield ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
