[Bug 844211] New: HW detection fails for BCM43228
https://bugzilla.novell.com/show_bug.cgi?id=844211 https://bugzilla.novell.com/show_bug.cgi?id=844211#c0 Summary: HW detection fails for BCM43228 Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: volker3204@paradise.net.nz QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.34 (KHTML, like Gecko) konqueror/4.10.5 Safari/534.34 openSUSE 12.3 is unable to handle the wireless BCM43228 in a laptop. During installation and by yast there is no reaction. There is also nothing that tells the user the manfacturer and model of the wireless chip so one can start googling. The reason may be that hwinfo fails to detect this chip properly. Contrary to what all instructions say, hwinfo --wlan NEVER PRODUCES ANY OUTPUT. The b43 is too old to handle this chip, and the bcma driver (as suggested perhaps somewhat by grepping the output of hwinfo) is also no good for this chip. The only driver that works is the one in broadcom-wl. hwinfo and yast do not produce anything useable until after this module is loaded, which is no good to the user. Reproducible: Always Steps to Reproduce: 1. Install openSUSE 12.3 on a laptop with BCM43228 wireless chip. 2. 3. Actual Results: User left hung out to dry. Expected Results: User is told what drivers exist for this chip. Adding approximately hwere to get it from would be brilliant. lspci has the only useful info: 02:00.0 Network controller: Broadcom Corporation BCM43228 802.11a/b/g/n -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=844211 https://bugzilla.novell.com/show_bug.cgi?id=844211#c Ye Yuan <yyuan@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |yyuan@suse.com AssignedTo|bnc-team-screening@forge.pr |kernel-maintainers@forge.pr |ovo.novell.com |ovo.novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=844211 https://bugzilla.novell.com/show_bug.cgi?id=844211#c Jeff Mahoney <jeffm@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel-maintainers@forge.pr |jslaby@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=844211 https://bugzilla.novell.com/show_bug.cgi?id=844211#c Jiri Slaby <jslaby@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jslaby@suse.com |machen@suse.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=844211 https://bugzilla.novell.com/show_bug.cgi?id=844211#c1 --- Comment #1 from Matt Chen <machen@suse.com> 2013-10-24 18:14:36 CST --- I see, will have a look. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=844211 https://bugzilla.novell.com/show_bug.cgi?id=844211#c2 Matt Chen <machen@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |volker3204@paradise.net.nz --- Comment #2 from Matt Chen <machen@suse.com> 2013-10-24 20:18:51 CST --- According to the source code, I don't see any related PID and VID for supporting this module. It would just suggest to use "wl" driver from broadcom official site unless there is someone able to contribute the patch to upstream. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=844211 https://bugzilla.novell.com/show_bug.cgi?id=844211#c3 Volker Kuhlmann <volker3204@paradise.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |volker3204@paradise.net.nz --- Comment #3 from Volker Kuhlmann <volker3204@paradise.net.nz> 2013-10-25 12:51:18 NZDT --- The main problem is that both hwinfo and yast produce no useable output whatever for what driver is needed or suggested for this hardware, leaving the user hanging out to dry. As far as I could find out, of the 3 potential drivers for this hardware only the broadcom-wl driver is appropriate for this particular chip, and it does indeed work fine. For yast, the appropriate course of action would be to suggest/offer to install the broadcom-wl package. Note yast MUST name the driver and package in the suggestion, because the repository in which this package is not a default one will probably not already be configured. The packages needed are broadcom-wl-kmp-desktop-5.100.82.112_k3.7.10_1.16-11.6.x86_64 broadcom-wl-5.100.82.112-11.6.x86_64 and are in packman/Essentials. hwinfo should also provide the name of this driver. The biggest problem in this situation is to find the name of the kernel module and package which one is supposed to use, locating them is usually trivial. The laptop switch controls these two devices: lspci 0a:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5761 Gigabit Ethernet PCIe (rev 10) lsusb Bus 002 Device 005: ID 413c:8187 Dell Computer Corp. DW375 Bluetooth Module The wifi chip is a PCI device, not USB, so there is no PID/VID? I can provide more hardware info of course, if needed. Thanks muchly -Volker. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=844211 https://bugzilla.novell.com/show_bug.cgi?id=844211#c Volker Kuhlmann <volker3204@paradise.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|volker3204@paradise.net.nz | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
The main problem is that both hwinfo and yast produce no useable output whatever for what driver is needed or suggested for this hardware, leaving the user hanging out to dry.
As far as I could find out, of the 3 potential drivers for this hardware only the broadcom-wl driver is appropriate for this particular chip, and it does indeed work fine.
For yast, the appropriate course of action would be to suggest/offer to install the broadcom-wl package. Note yast MUST name the driver and package in the suggestion, because the repository in which this package is not a default one will probably not already be configured. The packages needed are
broadcom-wl-kmp-desktop-5.100.82.112_k3.7.10_1.16-11.6.x86_64 broadcom-wl-5.100.82.112-11.6.x86_64
and are in packman/Essentials. Hmm....as I know, packman is still not default or mandatory to be in the openSUSE repository. Some of packages in packman are not open source. I do not
https://bugzilla.novell.com/show_bug.cgi?id=844211 https://bugzilla.novell.com/show_bug.cgi?id=844211#c4 Matt Chen <machen@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |volker3204@paradise.net.nz --- Comment #4 from Matt Chen <machen@suse.com> 2013-12-02 10:08:35 CST --- (In reply to comment #3) think it makes sense to add packaman to update repo as default.
hwinfo should also provide the name of this driver.
The biggest problem in this situation is to find the name of the kernel module and package which one is supposed to use, locating them is usually trivial.
The laptop switch controls these two devices:
lspci 0a:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5761 Gigabit Ethernet PCIe (rev 10) lsusb Bus 002 Device 005: ID 413c:8187 Dell Computer Corp. DW375 Bluetooth Module
The wifi chip is a PCI device, not USB, so there is no PID/VID?
try "lspci -nnk".
I can provide more hardware info of course, if needed.
Thanks muchly -Volker.
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=844211 https://bugzilla.novell.com/show_bug.cgi?id=844211#c5 Volker Kuhlmann <volker3204@paradise.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|volker3204@paradise.net.nz | --- Comment #5 from Volker Kuhlmann <volker3204@paradise.net.nz> 2013-12-02 15:49:00 NZDT --- I realise what the issues around packman are. Note that this bug is not about adding packman to the repo list, it is about abysmal support of any kind for users forced to use this hardware in their laptops (which works robustly btw, once the wl module is installed). Please re-read comment #1 carefully. The problems are: hwinfo --wlan is completely useless. Zero bytes output. I would expect it to tell me that the wl driver suports this chip, even if it does not offer to install the driver. yast is equally useless, and there I definitely would expect better. I noted in previous comments what the Linux options for this broadcom chip are. Essentially, I am expecting yast to tell me the same thing. If it then tells me "sorry no OSS driver that can be automatically installed" fine, no problem, I can start looking. If it tells me "suggested action: install wl kernel module in package broadcom-wl from third-party repo" that would be brilliant. However yast appears to be doing something, while in actual fact it says absoluely nothing and does absolutely nothing - it only pretends to. Addressing this bad user experience is the purpose of this bug report. Yes lspci is the only piece of software that says anything useful at all, however having to search the Internet for chip numbers and Linux drivers is sub-optimal for user-friendly Linux distros! In general, if there is no OSS driver I expect a distro to tell me what proprietory drivers there are, if there are any, and what their names are. I don't expect them to be installed if that is not possible, as in the case of packman. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=844211 https://bugzilla.novell.com/show_bug.cgi?id=844211#c7 Michal Filka <mfilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |locilka@suse.com AssignedTo|mfilka@suse.com |jkosina@suse.com --- Comment #7 from Michal Filka <mfilka@suse.com> 2014-01-09 08:10:21 UTC --- I don't think that yast should contain such piece of information. It is sad that working driver exists and such information is not shared or widely known. However, yast is not intended as a "database of drivers". There are other devices which works only with specific or proprietary hardware. Should yast display such information for all of them? It would make the code really messy and probably hard to maintain. I suggest to document the issue and the solution e.g. in opensuse wiki or in another suitable place. @Lukas: Any opinion or suggestion for suitable doc? @Volker: Thanks for your great job. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=844211 https://bugzilla.novell.com/show_bug.cgi?id=844211#c8 Lukas Ocilka <locilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |locilka@suse.com InfoProvider|locilka@suse.com | --- Comment #8 from Lukas Ocilka <locilka@suse.com> 2014-01-09 08:47:35 UTC --- Michal, I definitely agree that Yast should not contain any hardware-specific information. Yast can't fix issues in other parts of the distro. Especially because this kind of information usually get's obsolete soon and Yast can't find out that it's not relevant anymore. IMO this either belongs to Release Notes https://en.opensuse.org/openSUSE:Release_Notes or to the Hardware Support portal https://en.opensuse.org/Portal:Hardware -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=844211 https://bugzilla.novell.com/show_bug.cgi?id=844211#c9 --- Comment #9 from Volker Kuhlmann <volker3204@paradise.net.nz> 2014-01-09 21:59:07 NZDT --- I agree that yast is not the best place to keep such information. However please be aware that each (forced) user of this chip will neither become nor remain a Linux user. I am able to find the information I need eventually, but it's still a waste of time and I get grumpy about it. For the average laptop Linux user a documentation in some wiki ranks somewhere between 2 out of 10 and might as well not be there. Release notes isn't that good either, unless you are planning on keeping it there for the next umpteen releases. Nobody is going to read the relnotes of the previous oS. In plain, I expect appropriate information to pop up on the screen when I install openSUSE on such a laptop. I don't care where from and how. Anything else is not fit for 2014. Is there a way to make openSUSE suitable for such hardware? Btw with 12.3 the wl kernel module maintains much higher throughput than with 12.1. It has always been rock-solid for me. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com