Your message dated Wed, 20 Jan 2010 11:49:45 +0400
with message-id <201001201149.45235.clac...@easter-eggs.com>
and subject line Re: Bug#565812: The build wl.ko dont works with a bcm4312
card. With the broadcom-sta-common_5.10.91.9.3-2_all - Version it works fine
has caused the Debian Bug report #565812,
regarding The build wl.ko dont works with a bcm4312 card. With the
broadcom-sta-common_5.10.91.9.3-2_all - Version it works fine
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
565812: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565812
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: broadcom-sta
Version: broadcom-sta-common_5.10.91.9.3-3_all
Severity: grave
Justification: renders package unusable
The build wl-module dont works with a bcm4312 card. The interface is not found.
The problem exists since upgrading from broadcom-sta-common_5.10.91.9.3-2_all
to broadcom-sta-common_5.10.91.9.3-2_all.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-3.slh.3-sidux-amd64 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Hi,
> Ok, after removing the directory, rebuilding the kernelmodule and
> updating the initrd it works.
>
> The ssb-Module seems to be the Problem: I looked first on the "normal"
> system (with the downgraded version) if it was loaded, and there it was
> not. In the second system on an external disk with the newer Version of
> broadcom-sta-... it was loaded - sorry about the wrong information.
Yes it is, both modules are in conlict when accessing the bus.
> I have no Idea what exactly was the Problem. I think you know better how
> it works in detail and what could be happend, so the exact steps I made:
>
> - System with older version runnig, wlan OK.
> - Updated of the newer version of broadcom-sta-common, build the module,
> reboot, it stopped working
> - downgraded to old version of the package, build the module, it worked
> (with the same initrd!), also after reboot.
> - steps you described me -> OK
>
> On the second system:
>
> - System with older version runnig, wlan OK.
> - Updated of the newer version of broadcom-sta-common, build the module,
> no update of initrd, reboot, it stopped working
> - downgraded to old version of the package, build the module, it worked
> (with the same initrd!), also after reboot.
> - updated, it stopped working (same initrd).
> - ssb was loaded (why now?).
> - removing ssb - nothing
> - remove wl and load it again: interface exists, but no scanning possible
> - reboot, ssb loaded
> - update initrd, reboot
> - OK
As I said, initrd file has to be rebuilt just after a fresh install of -3
because ssb module is now blacklisted instead of unloaded.
See:
* http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=545388
* https://bugs.launchpad.net/ubuntu/+source/linux/+bug/227158
* http://ubuntuforums.org/showthread.php?t=794600
Closing the bug.
Regards,
--
Cyril Lacoux
--- End Message ---
