Ubuntu
jockey package

Jockey-kde does not properly install b43 firmware

Bug #207928 reported by TheGZeus on 2008-03-27

Affects		Status	Importance	Assigned to	Milestone
	jockey (Ubuntu)	Fix Released	Undecided	Martin Pitt

Bug Description

backtrace:
WARNING: unbind/rebind for device ssb0:0 on driver /sys/module/b43/drivers/ssb:b43 failed
Traceback (most recent call last):
File "/usr/lib/python2.5/site-packages/jockey/handlers.py", line 396, in rebind
open(os.path.join(driver_path, 'unbind'), 'w').write(device)
IOError: [Errno 13] Permission denied: '/sys/module/b43/drivers/ssb:b43/unbind'

Looks like a small permissions problem, and things are infinitely better than 2 days ago.
Not unhappy with the progress. Keep up the good work!

Revision history for this message

Martin Pitt (pitti) wrote on 2008-03-31:

I suppose this was run with admin privileges.

If the b43 driver does not support this (weird, it worked with other hardware), then jockey needs to intercept this and trigger the "reboot required" notification instead.

Thanks, Martin

Changed in jockey:
status:	New → Confirmed

Revision history for this message

Martin Pitt (pitti) wrote on 2008-04-01:

Ah, this is just debug output, jockey does not actually crash due to that. It just means that rebinding b43 does not work (which is unfortunate, and a kernel bug, since that worked fine with bcm43xx). So I'll fix it to trigger the "reboot required" notification.

Changed in jockey:
assignee:	nobody → pitti
status:	Confirmed → Fix Committed

Revision history for this message

TheGZeus (gzeusmants) wrote on 2008-04-01:

uh, oh.

I've rebooted a few times since this and I still have no wireless.

Is that a b43 bug?

Revision history for this message

Martin Pitt (pitti) wrote on 2008-04-01:

Forgot to mention in the changelog, but the notification is fixed here:

jockey (0.3.3-0ubuntu2) hardy; urgency=low

  * Merge to upstream trunk to pick up a few bug fixes:
    - nvidia.py: Add AddARGBGLXVisuals option to Screen section for
      nvidia-glx. (LP: #154596)
    - nvidia.py: Do not advertise as enabling composite if driver is already
      loaded (i. e. installed manually). (LP: #202802)
    - fglrx.py: Do not suggest installing fglrx if using the radeon X.org
      driver, since that already supports composite (LP: #207957)
    - jockey/ui.py: Change --update-db to print an error message instead of
      exception (LP: #209594)

-- Martin Pitt <email address hidden> Tue, 01 Apr 2008 20:40:50 +0200

Changed in jockey:
status:	Fix Committed → Fix Released

Revision history for this message

Martin Pitt (pitti) wrote on 2008-04-01:

> I've rebooted a few times since this and I still have no wireless.
> Is that a b43 bug?

It's most probably either:

* bug 197819 (failure to install the firmware properly): I don't have a Broadcom wifi, thus it is difficult for me to track down where in the process the b43-fwcutter package does not download/install the firmware properly when being installed through jockey and synaptic

* bug 182716 (b43 driver not working on all devices where bcm43xx worked): kernel bug

The two are relatively easy to differentiate by checking the installed firmware and dmesg.

If you find anything, I'd be infinitely grateful! :-)

Thanks, Martin

Revision history for this message

TheGZeus (gzeusmants) wrote on 2008-04-01:

demesg b43 Edit (86.7 KiB, text/plain)

Here's the dmesg output:

Revision history for this message

Martin Pitt (pitti) wrote on 2008-04-01:

TheGZeus, ah, it does seem to be a firmware installation problem, thus most likely a duplicate of bug 197819. Let's continue the discussion there. Thank you!