Re: [gentoo-user] MAJOR udev problem, PLEASE help
Hello Trenton, Ok it's been a month since this thread but... I found myself too oftenly in front of unsolved archived threads. Did you recompile your kernel with udev support ? I had a similar problem with a PCMCIA ethernet card while turning my system to udev. I recompiled my kernel with the same options and adding udev support and it worked smoothly (even had a shorter boot time :-) ) Check Code Listing 2.2 in : http://www.gentoo.org/doc/en/udev-guide.xml # # General setup --- # [*] Support for hot-pluggable devices # # File systems --- # Pseudo filesystems --- # [*] /proc file system support # [*] Virtual memory file system support (former shm fs) # Trenton Adams wrote: I have an ethernet controller that worked until I updated my udev to the latest version. Regards, -- Redouane BOUMGHAR Physics, Remote Sensing and Digital Imagery Engineer --- The biggest mountain can fear the slow man. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] MAJOR udev problem, PLEASE help
Yes, everything worked just fine. It indeed switched my ethernet to a different interface (eth1). Not a problem. On 6/11/07, Redouane Boumghar [EMAIL PROTECTED] wrote: Hello Trenton, Ok it's been a month since this thread but... I found myself too oftenly in front of unsolved archived threads. Did you recompile your kernel with udev support ? I had a similar problem with a PCMCIA ethernet card while turning my system to udev. I recompiled my kernel with the same options and adding udev support and it worked smoothly (even had a shorter boot time :-) ) Check Code Listing 2.2 in : http://www.gentoo.org/doc/en/udev-guide.xml # # General setup --- # [*] Support for hot-pluggable devices # # File systems --- # Pseudo filesystems --- # [*] /proc file system support # [*] Virtual memory file system support (former shm fs) # Trenton Adams wrote: I have an ethernet controller that worked until I updated my udev to the latest version. Regards, -- Redouane BOUMGHAR Physics, Remote Sensing and Digital Imagery Engineer --- The biggest mountain can fear the slow man. -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] MAJOR udev problem, PLEASE help
This is giving me some problems on a laptop - I have a 70-persistent-net rules file which attempts to pin eth0 to the ethernet interface, and eth1 to the wireless interface. This works fine on a cold boot or hibernate to disk (sus2) - without it the allocation wanders between the interfaces at will (this also occurs on a number of multi-interface servers I have - a real pain!) Recently however, if I attempt to echo mem /sys/power/state (aka instant stop/start!!) it resumes with one of the interfaces having a name of ethx_renam and of course no network. Is it possible to: a. fix so it worked as previously - i.e., resumed on the same interface in working condition or b. able to rename the interface so I can script a fix to run after resume. and is it a bug (so I will bugzilla it) or is it a feature :( BillK On Mon, 2007-06-11 at 17:20 -0600, Trenton Adams wrote: Yes, everything worked just fine. It indeed switched my ethernet to a different interface (eth1). Not a problem. On 6/11/07, Redouane Boumghar [EMAIL PROTECTED] wrote: Hello Trenton, Ok it's been a month since this thread but... I found myself too oftenly in front of unsolved archived threads. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] MAJOR udev problem, PLEASE help
Sorry for not replying earlier. Yes, I found it to be a fireware ethernet. Why udev would put that first makes no sense. I found another email on the list where someone had the same problem. Thanks. On 5/2/07, Neil Bothwick [EMAIL PROTECTED] wrote: On Wed, 2 May 2007 21:43:13 -0600, Trenton Adams wrote: I have an ethernet controller that worked until I updated my udev to the latest version. It shows up as follows from ifconfig eth0 Link encap:UNSPEC HWaddr 00-11-D8-00-00-7D-66-26-00-00-00-00-00-00-00-00 inet addr:192.168.20.2 Bcast:192.168.20.255 I don't understand what is happening. It sets my IP just fine, but the MAC address is WEIRD and there's no link. That MAC address looks like it could be a Firewire ethernet interface. Does ifconfig -a show your correct MAC address on another interface? If so, it is probably your persistent net rules messing things up, but if you don't use Firewire for ethernet, it's probably easiest to disable the eth1394 module. -- Neil Bothwick Drive not ready: (R)etry (G)o to Impulse (C)all Engineering -- [EMAIL PROTECTED] mailing list
[gentoo-user] MAJOR udev problem, PLEASE help
I have an ethernet controller that worked until I updated my udev to the latest version. 00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a1) Subsystem: ASUSTeK Computer Inc. Unknown device 8141 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 (250ns min, 5000ns max) Interrupt: pin A routed to IRQ 16 Region 0: Memory at febd7000 (32-bit, non-prefetchable) [size=4K] Region 1: I/O ports at d080 [size=8] Capabilities: [44] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- It shows up as follows from ifconfig eth0 Link encap:UNSPEC HWaddr 00-11-D8-00-00-7D-66-26-00-00-00-00-00-00-00-00 inet addr:192.168.20.2 Bcast:192.168.20.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:14 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:504 (504.0 b) I have kernel 2.6.18-r4 from gentoo-sources I don't understand what is happening. It sets my IP just fine, but the MAC address is WEIRD and there's no link. The link light is on. I can ping my IP, but my gateway IP returns with destination host unreachable. Any help would be appreciated. Thanks. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] MAJOR udev problem, PLEASE help
On Wed, 2 May 2007 21:43:13 -0600, Trenton Adams wrote: I have an ethernet controller that worked until I updated my udev to the latest version. It shows up as follows from ifconfig eth0 Link encap:UNSPEC HWaddr 00-11-D8-00-00-7D-66-26-00-00-00-00-00-00-00-00 inet addr:192.168.20.2 Bcast:192.168.20.255 I don't understand what is happening. It sets my IP just fine, but the MAC address is WEIRD and there's no link. That MAC address looks like it could be a Firewire ethernet interface. Does ifconfig -a show your correct MAC address on another interface? If so, it is probably your persistent net rules messing things up, but if you don't use Firewire for ethernet, it's probably easiest to disable the eth1394 module. -- Neil Bothwick Drive not ready: (R)etry (G)o to Impulse (C)all Engineering signature.asc Description: PGP signature
Re: [gentoo-user] MAJOR udev problem, PLEASE help
On Thursday 03 May 2007, Trenton Adams wrote: I have an ethernet controller that worked until I updated my udev to the latest version. 00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a1) Subsystem: ASUSTeK Computer Inc. Unknown device 8141 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 (250ns min, 5000ns max) Interrupt: pin A routed to IRQ 16 Region 0: Memory at febd7000 (32-bit, non-prefetchable) [size=4K] Region 1: I/O ports at d080 [size=8] Capabilities: [44] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- It shows up as follows from ifconfig eth0 Link encap:UNSPEC HWaddr Methinks that looks like some kind of firewire voodoo interface. The Link encap should be ethernet, like this: eth0 Link encap:Ethernet HWaddr 00:11:2F:28:94:AF inet addr:xxx.xxx.xx.xx Bcast:xxx.xxx.xx.xx Mask:255.255.255.240 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:18809418 errors:0 dropped:0 overruns:0 frame:0 TX packets:16750561 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1252875785 (1194.8 Mb) TX bytes:1941196921 (1851.2 Mb) Interrupt:10 Does ifconfig show any other interfaces? Are you running ~arch or plain arch? If the latter, I think udev-110 has defaulted to blacklisting the offending module precisely because of problems with the interfaces getting juggled about. -- /PA -- [EMAIL PROTECTED] mailing list
