Re: kernel versus broadcom wlan
- From: Celejar <celejar@xxxxxxxxx>
- Date: Wed, 30 Jan 2008 07:26:59 -0500
On Wed, 30 Jan 2008 10:21:19 +0100
Florian Kulzer <florian.kulzer+debian@xxxxxxx> 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.
Florian |
Celejar
--
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator
--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
- Follow-Ups:
- Re: kernel versus broadcom wlan
- From: Florian Kulzer
- Re: kernel versus broadcom wlan
- References:
- kernel versus broadcom wlan
- From: wauhugo@xxxxxxxxx
- Re: kernel versus broadcom wlan
- From: Florian Kulzer
- Re: kernel versus broadcom wlan
- From: David Paleino
- Re: kernel versus broadcom wlan
- From: Florian Kulzer
- Re: kernel versus broadcom wlan
- From: wauhugo@xxxxxxxxx
- Re: kernel versus broadcom wlan
- From: Florian Kulzer
- kernel versus broadcom wlan
- Prev by Date: Help with suspend/hibernate in Gnome Power Manager
- Next by Date: Re: Help with suspend/hibernate in Gnome Power Manager
- Previous by thread: Re: kernel versus broadcom wlan
- Next by thread: Re: kernel versus broadcom wlan
- Index(es):
Relevant Pages
|