Re: [gentoo-user] Re: udev upgrade and non-working eth0

[Mick <michaelkintzios@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 2699 bytes --]

On Wednesday 29 November 2006 17:33, Richard Fish wrote:
> On 11/27/06, Mrugesh Karnik <mrugeshkarnik@gmail.com> wrote:
> > On Tuesday 28 November 2006 07:31, Richard Fish wrote:
> > > > can see a 75-persistent-net-generator.rules file in there..
> > >
> > > Hmm, not sure how I got a 70-persistent-net.rules.  There is some
> > > interaction between that and 75-persistent-net-generator.rules (and
> > > the /lib/udev/write_net_rules script), but I'm a bit too tired to
> > > figure it out ATM.  It looks like 70-... should be created by the
> > > write_net_rules script...
> >
> > RULES_FILE='/etc/udev/rules.d/70-persistent-net.rules'
> >
> > That's the first line of write_net_rules.
>
> Right.  I just wasn't able to figure out why you didn't already have
> this file created, nor why my laptop had it but not my desktop.
>
> So the story is that 75-persistent-net-generator.rules will call the
> script when ethernet devices are added, and it is up to the
> write_net_rules script to generate 70-persistent-net.rules.  The
> problem is that when udev starts very early in the boot process, your
> root filesystem may still be mounted read-only, preventing this file
> from being created.
>
> This worked on my laptop, because I added module aliases to prevent
> udev from coldplugging the ipw3945 driver, since it requires a daemon
> to be running in order to work and that required /var to be mounted.
> The module is loaded later in the boot process, after all of the
> filesystems are mounted read-write, and that allowed udev to create
> the rules file for me, but only for that adapter.
>
> The upshot of this is this: by far the easiest way to solve the
> net-naming problem is to run
>
> /lib/udev/write_net_rules all_interfaces
>
> This will generate the rules for all interfaces, and then you can just
> edit the file to change the names as you like.  So I guess I'll know
> that for the next person that asks. :-P

Not sure if/how it is related to the OP, but this is what was created in 
my /etc/udev/rules.d/70-persistent-net.rules:
=====================================
# USB device 0x050d:0x7050 (rt2500usb)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:11:50:18:55:3f", 
ATTRS{type}=="1", NAME="wlan0"
=====================================

However, if I boot with the USB WiFi adaptor plugged in it, the device is not 
being detected.  If I plug it in after the system has booted then there is no 
problem.  The USB devices are 'udev-plugged' relatively late in the boot 
process, well after udevd has started.  Therefore I cannot understand why 
this adaptor is not being detected.  Any ideas?
-- 
Regards,
Mick

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]