Can someone tell me what this means;
From /var/log/boot.msg
eth0 configuration: eth-id-00:0b:db:97:5d:66 eth0 (DHCP) . . . modprobe: FATAL: Error inserting hw_random (/lib/modules/2.6.4-54.5-default/kernel/drivers/char/hw_random.ko): Input/output error . . <notice>pidofproc: dhcpcd 2201 IP/Netmask: 10.0.208.36 / 255.255.240.0 ('sha-linux') and from /var/log/message May 18 20:08:10 sha-linux kernel: eth0: no IPv6 routers present This is a Broadcom 4400 10/100BaseT Ethernet in Dell Inspiron 8500. Art
Hi, On Wednesday 19 May 2004 05:36, Art Fore wrote:
Can someone tell me what this means;
From /var/log/boot.msg
eth0 configuration: eth-id-00:0b:db:97:5d:66 eth0 (DHCP) . . . modprobe: FATAL: Error inserting hw_random (/lib/modules/2.6.4-54.5-default/kernel/drivers/char/hw_random.ko): Input/output error
. . <notice>pidofproc: dhcpcd 2201 IP/Netmask: 10.0.208.36 / 255.255.240.0 ('sha-linux')
and from /var/log/message
May 18 20:08:10 sha-linux kernel: eth0: no IPv6 routers present
This is a Broadcom 4400 10/100BaseT Ethernet in Dell Inspiron 8500.
That's not a eth0 problem. In fact, from those messages it appears that eth0 is set up just fine (with DHCP). What irritates you is the "FATAL: Error inserting hw_random" message in between. For some reason a module called hw_random is trying to get loaded but this fails (doesn't match your hardware). It's not critical, though. Only irritating. If you want to get rid of that message, you can blacklist the hw_random module in /etc/hotplug/blacklist Greetings from Bremen hartmut
What is the actual reason/use for that hw_random module mentioned down below ?? Johan Onsdag 19 maj 2004 08:04 skrev Hartmut Meyer:
Hi,
On Wednesday 19 May 2004 05:36, Art Fore wrote:
Can someone tell me what this means;
From /var/log/boot.msg
eth0 configuration: eth-id-00:0b:db:97:5d:66 eth0 (DHCP) . . . modprobe: FATAL: Error inserting hw_random (/lib/modules/2.6.4-54.5-default/kernel/drivers/char/hw_random.ko ): Input/output error
. . <notice>pidofproc: dhcpcd 2201 IP/Netmask: 10.0.208.36 / 255.255.240.0 ('sha-linux')
and from /var/log/message
May 18 20:08:10 sha-linux kernel: eth0: no IPv6 routers present
This is a Broadcom 4400 10/100BaseT Ethernet in Dell Inspiron 8500.
That's not a eth0 problem. In fact, from those messages it appears that eth0 is set up just fine (with DHCP).
What irritates you is the "FATAL: Error inserting hw_random" message in between. For some reason a module called hw_random is trying to get loaded but this fails (doesn't match your hardware). It's not critical, though. Only irritating.
If you want to get rid of that message, you can blacklist the hw_random module in /etc/hotplug/blacklist
Greetings from Bremen hartmut
On Wednesday 19 May 2004 19.57, Hartmut Meyer wrote:
Hi,
On Wednesday 19 May 2004 10:45, Johan wrote:
What is the actual reason/use for that hw_random module mentioned down below ??
I don't know.
/usr/src/linux/Documentation/hw_random.txt The hw_random device driver is software that makes use of a special hardware feature on your CPU or motherboard, a Random Number Generator (RNG).
I found I couldn't use the e100_speed_duplex module parameter under SuSE 9.1 with my Intel NIC. A recent posting on this list reported the same problem and a solution - the ethtool utility. Indeed I found that the following commands got the NIC talking: ethtool -s eth0 autoneg off duplex full rmmod e100; modprobe e100 sometimes it seems necessary to reload the kernel module twice before the network starts working properly. I have found that this needs to be run every time the computer is rebooted. I could put these commands in the boot.local but that could delay/prevent the startup of other services. Also, this doesn't solve the problem of network based installations, where these settings need to be activated prior to installing the operating system. Any ideas? -- Simon Oliver
Onsdag 19 maj 2004 17:03 skrev Simon Oliver:
I found I couldn't use the e100_speed_duplex module parameter under SuSE 9.1 with my Intel NIC.
A recent posting on this list reported the same problem and a solution - the ethtool utility. Indeed I found that the following commands got the NIC talking:
It was me who did that posting on that issue ...... it would be nice to know what motherboard and chipsset plus which controller-chip is used for the lan
ethtool -s eth0 autoneg off duplex full rmmod e100; modprobe e100
Did try out you suggested fix. please watch the result below B2:/home/b2 # rmmod e1000; modprobe e1000 B2:/home/b2 # ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised auto-negotiation: Yes Speed: Unknown! (65535) Duplex: Unknown! (255) Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: umbg Wake-on: g Current message level: 0x00000007 (7) Link detected: no As you can see
sometimes it seems necessary to reload the kernel module twice before the network starts working properly.
I have found that this needs to be run every time the computer is rebooted. I could put these commands in the boot.local but that could delay/prevent the startup of other services.
Also, this doesn't solve the problem of network based installations, where these settings need to be activated prior to installing the operating system.
Any ideas?
-- Simon Oliver
Johan wrote
It was me who did that posting on that issue ......
it would be nice to know what motherboard and chipset plus which controller-chip is used for the lan
Supermicro 370SSM Intel8215 based, with PCI 8255x Ethernet Pro 100 NIC (offboard).
ethtool -s eth0 autoneg off duplex full rmmod e100; modprobe e100
Did try out you suggested fix. please watch the result below
B2:/home/b2 # rmmod e1000; modprobe e1000 B2:/home/b2 # ethtool eth0
I'm using an e100 not an e1000. As I said, ethtool did work for me. But, I found that not only was it necessary to reload the e100.o module, I also had to do this a couple of times or put a sleep in between the unload and reload: ethtool -s eth0 autoneg off duplex full modprobe -r e100; sleep 2; modprobe e100 Here's the output: Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Advertised auto-negotiation: No Speed: 100Mb/s Duplex: Full Port: MII PHYAD: 1 Transceiver: internal Auto-negotiation: off Supports Wake-on: d Wake-on: d Current message level: 0x00000007 (7) Link detected: yes So I've got it working, once booted but not during boot. I could edit the init.d scripts and insert the ethtool command as required but these could easily get replaced by a YaST update. I could use boot.local but that gets run too late! Regards -- Simon Oliver
Fredag 21 maj 2004 11:48 skrev Simon Oliver:
Johan wrote
It was me who did that posting on that issue ......
it would be nice to know what motherboard and chipset plus which controller-chip is used for the lan
Supermicro 370SSM Intel8215 based, with PCI 8255x Ethernet Pro 100 NIC (offboard).
ethtool -s eth0 autoneg off duplex full rmmod e100; modprobe e100
Did try out you suggested fix. please watch the result below
B2:/home/b2 # rmmod e1000; modprobe e1000 B2:/home/b2 # ethtool eth0
I'm using an e100 not an e1000.
As I said, ethtool did work for me. But, I found that not only was it necessary to reload the e100.o module, I also had to do this a couple of times or put a sleep in between the unload and reload:
ethtool -s eth0 autoneg off duplex full modprobe -r e100; sleep 2; modprobe e100
Here's the output:
Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Advertised auto-negotiation: No Speed: 100Mb/s Duplex: Full Port: MII PHYAD: 1 Transceiver: internal Auto-negotiation: off Supports Wake-on: d Wake-on: d Current message level: 0x00000007 (7) Link detected: yes
So I've got it working, once booted but not during boot.
I could edit the init.d scripts and insert the ethtool command as required but these could easily get replaced by a YaST update.
I could use boot.local but that gets run too late!
Regards
-- Simon Oliver
Thanx for that little tip (hope it helps me) couse 10Mbit traffic on my NFS is a bore :-/ I'll have a close look at that "sucker" ;-) and let it sleep a little before kicking it again :-) But having read the documents on the matter in the kernel I suspect that for full functionality I have to wait for a fresh driver that supports the latest and greates (chip-wize). My controllerchip is not mentioned as of yet ... but I have started a conversation with some Intel developers and they're trying to recreate the problem (with same motherboard (ASUS P4C800E-Deluxe) Johan
participants (5)
-
Anders Johansson -
Art Fore -
Hartmut Meyer -
Johan -
Simon Oliver