Re: kernel versus broadcom wlan
On Wed, Jan 30, 2008 at 07:26:59 -0500, Celejar wrote:
> On Wed, 30 Jan 2008 10:21:19 +0100 Florian Kulzer wrote:
>
> [snip]
>
> > The problem with the broadcom chip appears to be that the firmware is
> > not present at the first boot of a Debian system, so only the master
> > device is detected and added to z25_persistent-net.rules. This seems
> > somehow to block correct name assignment for the "real" (usable) device
> > (later, when the firmware has been installed).
> >
> > The bugzilla links suggest that you can simply delete or rename the
> > persistent-net.rules file and reboot. With the firmware present udev
> > obviously creates the rules for the two interfaces at once and
> > correctly.
>
> I had this problem; I was also told to reboot, but I believe
> that simply commenting out the rule(s) in persistent-net.rules and then
> doing 'udevtrigger' is sufficient to generate a correct rewrite of the
> rules.
Ah, good point. I just tried this and there is indeed no need to reboot.
However, I found that udevtrigger increments the interface numbers as
long as the old rules are only commented out, i.e. my present eth0
interface would have become eth1 on the next reboot. (I guess the same
would have happened had I rebooted directly instead of running
udevtrigger manually.) It seems to be better to delete the old rules or
to (re)move the entire persistent-net-rules file.
--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |
Reply to: