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
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
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
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
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-
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
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+
7 matches
Mail list logo
