Could you send me the output of /usr/sbin/ethtool -e eth0 That may allow me to restore my still-broken e1000e ...
Karsten Keil (of SuSE) has been helping me restore my Ethernet device. We thought we had an image that worked (I was able to use eth0 for a few hours), but alas after a reboot it is broken again/still. An image from a working T400 would be helpful.
On Thu, 2008-11-13 at 22:06 -0800, Per Bothner wrote:
Could you send me the output of /usr/sbin/ethtool -e eth0 That may allow me to restore my still-broken e1000e ...
Karsten Keil (of SuSE) has been helping me restore my Ethernet device. We thought we had an image that worked (I was able to use eth0 for a few hours), but alas after a reboot it is broken again/still. An image from a working T400 would be helpful.
Here ya go...! Running F10 on a T400 with both WiFi and Ethernet working...
Cheers,
Chris
-- ================================== By all means marry; If you get a good wife, you'll be happy. If you get a bad one, you'll become a philosopher.
--Socrates
Christopher A. Williams wrote:
On Thu, 2008-11-13 at 22:06 -0800, Per Bothner wrote:
Could you send me the output of /usr/sbin/ethtool -e eth0 That may allow me to restore my still-broken e1000e ...
Karsten Keil (of SuSE) has been helping me restore my Ethernet device. We thought we had an image that worked (I was able to use eth0 for a few hours), but alas after a reboot it is broken again/still. An image from a working T400 would be helpful.
Here ya go...! Running F10 on a T400 with both WiFi and Ethernet working...
Thanks! I edited the MAC address (the first 6 bytes), and installed this image (using e1000e_nvm on Karsten's recovery CD), and rebooted.
There were a few diffs from the dump that Karsten had me try; let's hope those make the difference.
So far so good, but of course it's only been running less than an hour.
The recovered device shows up as eth1 rather than eth0. That's a slight blemish. Perhaps this is left-over from when I used a USB Ethernet device and that got installed as eth0? Some configuration file defines that as eth0?
On Friday 14 November 2008 06:53:53 Per Bothner wrote:
The recovered device shows up as eth1 rather than eth0. That's a slight blemish. Perhaps this is left-over from when I used a USB Ethernet device and that got installed as eth0? Some configuration file defines that as eth0?
Interesting. My eth0 also shows up as eth1, apparently renamed by udev - and no obvious reason.
Configured devices: l0 eth0 wlan0 Currently active devices: lo eth1 wmaster0 wlan0
Something odd going on here.
Anne
On Fri, 2008-11-14 at 07:08 +0000, Anne Wilson wrote:
On Friday 14 November 2008 06:53:53 Per Bothner wrote:
The recovered device shows up as eth1 rather than eth0. That's a slight blemish. Perhaps this is left-over from when I used a USB Ethernet device and that got installed as eth0? Some configuration file defines that as eth0?
Interesting. My eth0 also shows up as eth1, apparently renamed by udev - and no obvious reason.
Configured devices: l0 eth0 wlan0 Currently active devices: lo eth1 wmaster0 wlan0
Something odd going on here.
Indeed...! After plugging in a network cable (I usually run on my wireless connection at home) my laptop - which generated the output file used - shows:
Active: eth0 Inactive: pan0 Active: wlan0
Everything looks like you would expect. Not sure what could be going on with your systems. For the record, my T400 is model 2765-T6U. Could that have something to do with it?
Cheers,
Chris
-- ================================== By all means marry; If you get a good wife, you'll be happy. If you get a bad one, you'll become a philosopher.
--Socrates
On Fri, Nov 14, 2008 at 07:08:03AM +0000, Anne Wilson wrote:
On Friday 14 November 2008 06:53:53 Per Bothner wrote:
The recovered device shows up as eth1 rather than eth0. That's a slight blemish. Perhaps this is left-over from when I used a USB Ethernet device and that got installed as eth0? Some configuration file defines that as eth0?
Interesting. My eth0 also shows up as eth1, apparently renamed by udev - and no obvious reason.
Configured devices: l0 eth0 wlan0 Currently active devices: lo eth1 wmaster0 wlan0
Something odd going on here.
I think that is "persistent udev naming rules" which tries to keep the eth name the same for every boot despite additional interfaces coming/going, e.g. usb or other hotplugged devices.
You can find the mapping of ethernet address to device name here and change it if you want:
/etc/udev/rules.d/70-persistent-net.rules
Also, make sure your ifcfg-ethX files have matching HWADDR= lines. e.g. ifcfg-eth0 should save DEVICE=eth0 and HWADDR= that matches the ATTR{address} from the persistent-net.rules above.
Chuck Anderson wrote:
I think that is "persistent udev naming rules" which tries to keep the eth name the same for every boot despite additional interfaces coming/going, e.g. usb or other hotplugged devices.
You can find the mapping of ethernet address to device name here and change it if you want:
/etc/udev/rules.d/70-persistent-net.rules
That was it: I removed from that file two lines referring to eth0 and eth1, and after reboot my Ethernet comes up as eth0. Thanks!
Also, make sure your ifcfg-ethX files have matching HWADDR= lines. e.g. ifcfg-eth0 should save DEVICE=eth0 and HWADDR= that matches the ATTR{address} from the persistent-net.rules above.
There are no fcfg-ethX files in /etc.
Per Bothner wrote:
Chuck Anderson wrote:
I think that is "persistent udev naming rules" which tries to keep the eth name the same for every boot despite additional interfaces coming/going, e.g. usb or other hotplugged devices.
You can find the mapping of ethernet address to device name here and change it if you want:
/etc/udev/rules.d/70-persistent-net.rules
That was it: I removed from that file two lines referring to eth0 and eth1, and after reboot my Ethernet comes up as eth0. Thanks!
Also, make sure your ifcfg-ethX files have matching HWADDR= lines. e.g. ifcfg-eth0 should save DEVICE=eth0 and HWADDR= that matches the ATTR{address} from the persistent-net.rules above.
There are no fcfg-ethX files in /etc.
The full path to those is /etc/sysconfig/network-scripts/ifcfg-ethX. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer ricks@nerd.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - ----------------------------------------------------------------------
Rick Stevens wrote:
Per Bothner wrote:
There are no fcfg-ethX files in /etc.
The full path to those is /etc/sysconfig/network-scripts/ifcfg-ethX.
I thought "There are no fcfg-ethX files in /etc." was pretty clear ...
$ sudo find /etc -name 'ifcfg-*' /etc/sysconfig/network-scripts/ifcfg-lo $
On Fri, Nov 14, 2008 at 11:22:27AM -0800, Per Bothner wrote:
Rick Stevens wrote:
Per Bothner wrote:
There are no fcfg-ethX files in /etc.
The full path to those is /etc/sysconfig/network-scripts/ifcfg-ethX.
I thought "There are no fcfg-ethX files in /etc." was pretty clear ...
$ sudo find /etc -name 'ifcfg-*' /etc/sysconfig/network-scripts/ifcfg-lo $
Ah, if you don't have any then I would assume NetworkManager just auto-creates configuration for them. Maybe that is the difference between "Auto Ethernet" and "System eth0" that shows up for me in the drop-down list?
Chuck Anderson wrote:
On Fri, Nov 14, 2008 at 11:22:27AM -0800, Per Bothner wrote:
Rick Stevens wrote:
Per Bothner wrote:
There are no fcfg-ethX files in /etc.
The full path to those is /etc/sysconfig/network-scripts/ifcfg-ethX.
I thought "There are no fcfg-ethX files in /etc." was pretty clear ...
$ sudo find /etc -name 'ifcfg-*' /etc/sysconfig/network-scripts/ifcfg-lo $
Ah, if you don't have any then I would assume NetworkManager just auto-creates configuration for them. Maybe that is the difference between "Auto Ethernet" and "System eth0" that shows up for me in the drop-down list?
Hm. Probably. That distinction has been annoying/confusing ...
I now just get "Auto eth0" under "Wired Network".
On Fri, 2008-11-14 at 23:16 -0500, Chuck Anderson wrote:
Ah, if you don't have any then I would assume NetworkManager just auto-creates configuration for them. Maybe that is the difference between "Auto Ethernet" and "System eth0" that shows up for me in the drop-down list?
That's exactly the difference. "System" means config file on the system, likely shared between all users, but auto or other connections you create may be specific to your user, and are typically stored in your gconf.
-
Anne Wilson -
Christopher A Williams -
Chuck Anderson -
Jesse Keating -
Per Bothner -
Rick Stevens