On Tue, 2006-07-04 at 19:35 +0200, Marco d'Itri wrote:
> On Jul 04, Andreas Beckmann <[EMAIL PROTECTED]> wrote:
> 
> > # ignore interfaces without a driver link
> > DRIVER!="?*", GOTO="persistent_net_generator_end"
> > 
> > If I comment out this line, z25_persistent-net.rules is generated on
> > boot (if it was missing), so the test seems to be too limiting.
> Too bad, because it's needed.
> 
> > > Unless you can point me to an actual bug, then the explanation of
> > > this behaviour is that your network card(s) do not support generation of
> > > persistent rules, older versions of udev lacked some checks which were
> > > added later.
> > 
> > Are the following network cards too old?
> > # PCI device 14e4:4401 (b44) (onboard)
> > # PCI device 10ec:8139 (8139too) (PCI card)
> No, and unless you added the drivers name in the comment you reported
> it means that the driver symlinks exist because the script has found them.
> Kay, do you have any idea about why DRIVER!="?*" is not working as
> expected?

The device itself does not have a DRIVER value set. We need to select a
parent device with BUS to match against DRIVER, but unfortunately there
are pci devices in the higher chain which don't have a driver value, so
  BUS=="?*", DRIVER!="?*"
will not work. I see currently no easy solution other than using
PHYSDEVDRIVER, until we know how to solve that.

> > I attach a copy of /sys/class/net/eth* as described in #368845.
> > Kernel 2.6.16-2-k7 (2.6.16-15), there are no 'driver' symlinks.
> They are in the device/ directory.

Care to provide:
  udevinfo -a -p /class/net/eth0

That should print all the DRIVER= values, just to check if that is
correct.

Thanks,
Kay



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to