From: "Alexey Zaytsev" <alexey.zaytsev@gmail.com>
To: "Stefan Lippers-Hollmann" <s.L-H@gmx.de>
Cc: "Michael Buesch" <mb@bu3sch.de>,
"John W. Linville" <linville@tuxdriver.com>,
"Ingo Molnar" <mingo@elte.hu>,
"Alexey Zaytsev" <zaytsev.a@protei.ru>,
"Greg KH" <greg@kroah.com>,
linux-kernel@vger.kernel.org
Subject: Re: bcm43xx regression in 2.6.24 (with patch)
Date: Sat, 1 Mar 2008 02:22:47 +0300 [thread overview]
Message-ID: <f19298770802291522t26055258t363337b74b4969cb@mail.gmail.com> (raw)
In-Reply-To: <200802290012.56654.s.L-H@gmx.de>
On Fri, Feb 29, 2008 at 2:12 AM, Stefan Lippers-Hollmann <s.L-H@gmx.de> wrote:
[...]
> >
> > Btw, when booting the system with the b43 driver, I get a
> > ~30 socond delay after the boot scripts report
> > "Waiting for /dev to be fully populated" and all the modules
> > get loaded. Is this something expected?
>
> That is most likely udev related, which doesn't really like module names
> and default interface names changing for a known MAC address, depending on
> your distribution (the following example assumes debian sid, udev 0.114-2)
> you might have something like /etc/udev/rules.d/z25_persistent-net.rules
> (which lists MAC addresses and the associated persistent interface name),
> removing the corresponding stanza for your Broadcom wireless card (or
> removing the whole file alltogether and letting udev (or rather
> z45_persistent-net-generator.rules) recreate it during the next boot will
> most likely fix it.
>
> This issue is in no way b43 related, it happens with "every" networking
> devices with changing module names (at least for every legacy wireless
> module being replaced by a new mac80211 based driver).
Removing the file helped. Thanks.
>
> Regards
> Stefan Lippers-Hollmann
>
next prev parent reply other threads:[~2008-02-29 23:22 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 11:17 Alexey Zaytsev
2008-02-22 14:13 ` Michael Buesch
2008-02-22 17:51 ` Gabriel C
2008-02-22 17:56 ` Michael Buesch
2008-02-22 22:10 ` Greg KH
2008-02-22 18:10 ` Alexey Zaytsev
2008-02-22 17:48 ` Michael Buesch
2008-02-22 20:06 ` Alexey Zaytsev
2008-02-22 20:12 ` Michael Buesch
2008-02-22 20:38 ` Alexey Zaytsev
2008-02-22 22:12 ` Greg KH
2008-02-22 22:45 ` Alexey Zaytsev
2008-02-23 5:48 ` Michael Buesch
2008-02-23 11:07 ` Ingo Molnar
2008-02-23 11:18 ` Pekka Enberg
2008-02-23 11:24 ` Ingo Molnar
2008-02-23 11:32 ` Alexey Zaytsev
2008-02-23 11:37 ` Pekka Enberg
2008-02-23 11:51 ` Alexey Zaytsev
2008-02-23 11:57 ` Pekka J Enberg
2008-02-23 12:17 ` Alexey Zaytsev
2008-02-23 12:23 ` Pekka Enberg
2008-02-24 14:29 ` Michael Buesch
2008-02-24 16:39 ` Alexey Zaytsev
2008-02-24 17:16 ` Michael Buesch
2008-02-25 6:16 ` Pekka J Enberg
2008-02-25 6:49 ` Greg KH
2008-02-25 6:54 ` Pekka J Enberg
2008-02-25 9:54 ` Michael Buesch
2008-02-25 12:11 ` Pekka Enberg
2008-02-25 12:19 ` Michael Buesch
2008-02-25 12:25 ` Pekka J Enberg
2008-02-25 13:00 ` Alexey Zaytsev
2008-02-25 10:23 ` Alexey Zaytsev
2008-02-25 10:38 ` Michael Buesch
2008-02-25 10:49 ` Xavier Bestel
2008-02-25 10:54 ` Michael Buesch
2008-02-23 16:05 ` Michael Buesch
2008-02-23 16:27 ` Michael Buesch
2008-02-23 16:44 ` Ingo Molnar
2008-02-23 16:50 ` Michael Buesch
2008-02-23 21:32 ` Alexey Zaytsev
2008-02-23 22:20 ` Michael Buesch
2008-02-26 20:20 ` John W. Linville
2008-02-26 21:38 ` Alexey Zaytsev
2008-02-26 22:04 ` Michael Buesch
2008-02-26 22:12 ` Alexey Zaytsev
2008-02-26 22:41 ` Michael Buesch
2008-02-28 22:03 ` Michael Buesch
2008-02-28 22:48 ` Alexey Zaytsev
2008-02-28 23:12 ` Stefan Lippers-Hollmann
2008-02-29 23:22 ` Alexey Zaytsev [this message]
2008-02-28 23:14 ` Michael Buesch
2008-02-26 22:47 ` John W. Linville
2008-02-26 23:12 ` Michael Buesch
2008-02-27 0:23 ` Alexey Zaytsev
2008-02-27 0:27 ` Michael Buesch
2008-02-27 0:32 ` Alexey Zaytsev
2008-02-27 0:43 ` Michael Buesch
2008-02-27 0:53 ` Alexey Zaytsev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f19298770802291522t26055258t363337b74b4969cb@mail.gmail.com \
--to=alexey.zaytsev@gmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=mingo@elte.hu \
--cc=s.L-H@gmx.de \
--cc=zaytsev.a@protei.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®