Re: udev rule does not assign eth0 to ipw3945 device

[Chris Smith <smitty1elkml@gmail.com>]

Bryan Kadzban <bryan <at> kadzban.is-a-geek.net> writes:
 
> I assume you have the required firmware files, right?
> 
> > #udevinfo <...>
> 
> What about /sys/class/net/*?  (And note that it may not be eth*, it may
> be wifi*/wlan*, or even something different.  Look in /sys/class/net.)
> 
Only thing in there is lo

> > #cat /etc/udev/rules.d/70-persistent-net.rules
> > # This file was automatically generated by the /lib/udev/write_net_rules
> > # program, probably run by the persistent-net-generator.rules rules file.
> > #
> > # You can modify it, as long as you keep each rule on a single line. 
> > KERNEL="0000:0c:00.0",ATTR{class}="0x028000", 
> > ATTR{device}="0x4222", ATTR{vendor}="0x8086",WAIT_FOR_SYSFS, 
> > PROGRAM="/sbin/ipw3945d-start ipw3945d",NAME="eth0"
> 
> Try getting rid of WAIT_FOR_SYSFS.  As far as I know, that option
> requires an argument (the name of the sysfs attribute to wait for); it
> does not cause udev to just "wait for sysfs to be available" or
> something like that.
> 
A further read of man udev confirmed that you are right.

> Another issue might be the KERNEL match; I don't know if that constrains
> the ATTR{...} attributes or not, but it might.  Try ID_PATH if you need
> to match the PCI slot number (of course that will require you to run
> path_id on all network-class devices).
> 
> Also try adding some spaces after the commas -- I don't know if they're
> required or not, but they might be.
> 
> Finally, I am going to guess that the rule was on one line (like the
> comment says it must be), but just in case, it'd be good to double-check
> that.
> 
Further poking based on your suggestions and a read of forums.gentoo.org
suggests that my real heartburn might be that the firmware, which I have sitting
in /lib/firmware, may not in fact be loading.

I don't know if the regulatory daemon just loads the firmware via
sleight-of-hand, or if it is loading and just reporting nothing, or what.
/lib/udev/firmware.sh seems to employ some sysfs entries that I don't see
otherwise, like "loading" and "data".

Curious, and less than thoroughly documented, this whole firmware process...

Thanks for your reply, Bryan. 

Best,
Chris


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel