RE: FW: module_register
No. All devices are compiled in. dmesg output ed0: NE2000 PCI Ethernet (RealTek 8029) port 0xc000-0xc01f irq 12 at device 2.0 on pci1 ed0: address 00:c0:df:a4:05:43, type NE2000 (16 bit) wb0: Winbond W89C840F 10/100BaseTX port 0xc400-0xc47f mem 0xd500-0xd57f irq 11 at device 5.0 on pci1 wb0: Ethernet address: 00:10:61:b0:78:47 miibus0: MII bus on wb0 amphy0: Am79C873 10/100 media interface on miibus0 amphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto And here messages log Aug 10 12:41:28 server /kernel: Doing initial network setup: Aug 10 12:41:28 server /kernel: hostname Aug 10 12:41:28 server /kernel: ipmon Aug 10 12:41:28 server /kernel: ipfilter Aug 10 12:41:28 server /kernel: ipnat Aug 10 12:41:28 server /kernel: 0 entries flushed from NAT table Aug 10 12:41:28 server /kernel: 0 entries flushed from NAT list Aug 10 12:41:28 server /kernel: . Aug 10 12:41:28 server /kernel: module_register: module miibus/ukphy already exists! Aug 10 12:41:28 server /kernel: linker_file_sysinit miibus.ko failed to register! 17 Aug 10 12:41:28 server /kernel: module_register: module pci/ed already exists! Aug 10 12:41:28 server /kernel: linker_file_sysinit if_ed.ko failed to register! 17 Aug 10 12:41:28 server /kernel: ed0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 Aug 10 12:41:28 server /kernel: inet 159.148.36.226 netmask 0xfff8 broadcast 159.148.36.231 Aug 10 12:41:28 server /kernel: ether 00:c0:df:a4:05:43 Aug 10 12:41:28 server /kernel: wb0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 Aug 10 12:41:28 server /kernel: inet 192.168.0.1 netmask 0xff00 broadcast 192.168.0.255 Aug 10 12:41:28 server /kernel: ether 00:10:61:b0:78:47 Aug 10 12:41:28 server /kernel: media: Ethernet autoselect (none) Aug 10 12:41:28 server /kernel: status: no carrier -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Fleck Sent: Monday, August 11, 2003 3:43 PM To: Andris Cc: 'Doug White'; [EMAIL PROTECTED] Subject: RE: FW: module_register On Mon, 11 Aug 2003, Andris wrote: I already have compile options 'device ed', and I can't find where rc scripts try to load module. Or it is ifconfig problem? is it in your /boot/loader.conf ? That's where my loadable kernel modules are listed. -- David Fleck [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FW: module_register
On Mon, 11 Aug 2003, Andris wrote: I already have compile options 'device ed', and I can't find where rc scripts try to load module. Or it is ifconfig problem? is it in your /boot/loader.conf ? That's where my loadable kernel modules are listed. -- David Fleck [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FW: module_register
On Mon, 11 Aug 2003, Andris wrote: No. All devices are compiled in. Can you mail me your kernel config, privately please? Thanks! dmesg output ed0: NE2000 PCI Ethernet (RealTek 8029) port 0xc000-0xc01f irq 12 at device 2.0 on pci1 ed0: address 00:c0:df:a4:05:43, type NE2000 (16 bit) wb0: Winbond W89C840F 10/100BaseTX port 0xc400-0xc47f mem 0xd500-0xd57f irq 11 at device 5.0 on pci1 wb0: Ethernet address: 00:10:61:b0:78:47 miibus0: MII bus on wb0 amphy0: Am79C873 10/100 media interface on miibus0 amphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto And here messages log Aug 10 12:41:28 server /kernel: Doing initial network setup: Aug 10 12:41:28 server /kernel: hostname Aug 10 12:41:28 server /kernel: ipmon Aug 10 12:41:28 server /kernel: ipfilter Aug 10 12:41:28 server /kernel: ipnat Aug 10 12:41:28 server /kernel: 0 entries flushed from NAT table Aug 10 12:41:28 server /kernel: 0 entries flushed from NAT list Aug 10 12:41:28 server /kernel: . Aug 10 12:41:28 server /kernel: module_register: module miibus/ukphy already exists! Aug 10 12:41:28 server /kernel: linker_file_sysinit miibus.ko failed to register! 17 Aug 10 12:41:28 server /kernel: module_register: module pci/ed already exists! Aug 10 12:41:28 server /kernel: linker_file_sysinit if_ed.ko failed to register! 17 Aug 10 12:41:28 server /kernel: ed0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 Aug 10 12:41:28 server /kernel: inet 159.148.36.226 netmask 0xfff8 broadcast 159.148.36.231 Aug 10 12:41:28 server /kernel: ether 00:c0:df:a4:05:43 Aug 10 12:41:28 server /kernel: wb0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 Aug 10 12:41:28 server /kernel: inet 192.168.0.1 netmask 0xff00 broadcast 192.168.0.255 Aug 10 12:41:28 server /kernel: ether 00:10:61:b0:78:47 Aug 10 12:41:28 server /kernel: media: Ethernet autoselect (none) Aug 10 12:41:28 server /kernel: status: no carrier -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Fleck Sent: Monday, August 11, 2003 3:43 PM To: Andris Cc: 'Doug White'; [EMAIL PROTECTED] Subject: RE: FW: module_register On Mon, 11 Aug 2003, Andris wrote: I already have compile options 'device ed', and I can't find where rc scripts try to load module. Or it is ifconfig problem? is it in your /boot/loader.conf ? That's where my loadable kernel modules are listed. -- David Fleck [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FW: module_register
I already have compile options 'device ed', and I can't find where rc scripts try to load module. Or it is ifconfig problem? -Original Message- From: Doug White [mailto:[EMAIL PROTECTED] Sent: Monday, August 11, 2003 10:47 AM To: Andris Cc: [EMAIL PROTECTED] Subject: Re: FW: module_register On Mon, 11 Aug 2003, Andris wrote: Hello! I have the same problem, whats up? This is normal -- you already have the miibus device compiled into your kernel for another ethernet device and the ed driver depends on the miibus module since it needs it. Error 17 means the necessary code is already loaded. If the message bothers you, either: 1. recompile your kernel, adding 'device ed' so you don't have to load the module in the first place. or 2. recompile your kernel, removing 'device miibus' and all ethernet devices that depend on it. Then when ed loads it will also successfully load miibus. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
