| 2007-09-09 10:47:21 |
Matteo Z |
bug |
|
|
added bug |
| 2007-09-09 10:53:32 |
Matteo Z |
restricted-manager: importance |
Undecided |
Wishlist |
|
| 2007-09-11 20:45:10 |
Martin Böhm |
description |
When user upgrades to a new kernel version, the system will look for firmware files in
/lib/firmware/$(uname -r)
where $(uname -r) is the new kernel version. When user boots with new kernel, r-m will correctly report that bcm43xx firmware is not installed as it is not present in current kernel firmware directory.
Firmware needs to be cutted again.
Restricted-manager should handle this, still this would require:
- to save firmware file wl_apsta.o somewhere for further cutting
- to trigger 'restricted-manager --enable bcm43xx' when needed without user interaction since he already acknowledged to use the restricted firmware
Early win: remove bcm43xx from used list, so that it will be prompted again for being enabled at first boot with new kernel |
When a user upgrades to a new kernel version, the system will not move or rebuild the bcm43xx firmware, which is installed using the Restricted Manager interface. The user should not lose his network connection this way when upgrading a stable system.
|
|
| 2007-09-11 20:45:10 |
Martin Böhm |
title |
bcm43xx: fw needs to be cutted again if user upgrades kernel |
bcm43xx: firmware needs to be cut again if user upgrades kernel |
|
| 2007-09-11 20:54:49 |
Martin Böhm |
bug |
|
|
assigned to linux-restricted-modules-2.6.22 (Ubuntu) |
| 2008-02-04 18:13:27 |
Martin Pitt |
linux-restricted-modules-2.6.22: status |
New |
Invalid |
|
| 2008-02-04 18:14:11 |
Martin Pitt |
bug |
|
|
assigned to jockey (Ubuntu) |
| 2008-02-04 18:14:37 |
Martin Pitt |
restricted-manager: status |
New |
Won't Fix |
|
| 2008-02-18 11:03:34 |
Martin Pitt |
jockey: status |
New |
Fix Released |
|
