I'll dive into it right now .... gotta get something to eat first before my brain crash ....... BBL Johan Torsdag 20 maj 2004 13:38 skrev Daniel Thivierge:
I miss most of the posting for this, if it was mention before, just delete it. Also, this was done on Enterprise 8 version of SuSE (we don't have 9.1 yet).
Anyway, here it is........
Look in to the file: /proc/net/PRO_LAN_Adapters/eth0/LoadParameters/e100_speed_duplex.de f you should see the different values you can assign to the driver.
In the file below you should have your default value the driver is using: /proc/net/PRO_LAN_Adapters/eth0/LoadParameters/e100_speed_duplex.va l
In the etc/modules.conf add the options line (if 4 is what you want from the def file): alias eth0 e100 options e100 e100_speed_duplex=4
This is how the server is setup to run with Full Duplex 100 by default.
|---------+----------------------------> | | | Johan | | |
| | | | | 20/05/2004 05:21 | | |---------+----------------------------> | ---------------------------------------------------------------- -------------------------------------------------------------|
| To: suse-linux-e@suse.com | | | cc: | | | Subject: Re: [SLE] e100 speed duplex under 9.1 | | |
---------------------------------------------------------------- -------------------------------------------------------------|
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
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com