On Mar 22, Kurt Roeckx <[EMAIL PROTECTED]> wrote: > I assumed that either you or upstream has some expierence with dealing > with such situation. I assume the kernel breaks things once in a while. > I have no idea if there are any workarounds for simular problems. Yes, but the report was confusing. People can't assume that I know about every broken version of every wifi driver around... I do not understand if removing the old rules and reloading the modules fixed the problem or not. Also, what changed exactly from the kernel side? And where did the eth3 name came from?
> My first idea was that if the b43 driver is loaded and the MAC adddress
> matches that the 'ATTRS{type}="1"' gets added automaticly if it's not
> present.
Automatically modifying exising rules is hard.
> Alternativly udev should know that (for the b43 driver) it should only
> attemp to rename it if the type is 1.
It does:
if [ $basename = "ath" -o $basename = "wlan" ]; then
match="$match, ATTR{type}==\"1\"" # do not match the wifi* interfaces
fi
--
ciao,
Marco
signature.asc
Description: Digital signature
