| 2007-02-14 13:42:46 |
Thom Pischke |
bug |
|
|
added bug |
| 2007-02-14 16:59:24 |
BHowell |
bcm43xx-fwcutter: status |
Unconfirmed |
Confirmed |
|
| 2007-02-14 16:59:24 |
BHowell |
bcm43xx-fwcutter: statusexplanation |
|
I can confirm the same bug here. Anyone know of any valid 4.x amd64 firmware source out there? |
|
| 2007-02-16 20:57:10 |
jrb114 |
bug |
|
|
added attachment 'crash.txt' (/var/log/syslog) |
| 2007-02-17 00:11:56 |
Brian Murray |
bcm43xx-fwcutter: importance |
Undecided |
Medium |
|
| 2007-02-17 00:11:56 |
Brian Murray |
bcm43xx-fwcutter: statusexplanation |
I can confirm the same bug here. Anyone know of any valid 4.x amd64 firmware source out there? |
|
|
| 2007-02-19 12:53:59 |
magilus |
bcm43xx-fwcutter: status |
Confirmed |
Rejected |
|
| 2007-02-19 12:53:59 |
magilus |
bcm43xx-fwcutter: statusexplanation |
|
In fact, this is no bug in bcm43xx-fwcutter and support has not been dropped for older cards.
The new bcm43xx driver, which went to Feisty, requires a 4.x firmware version.
In order to get one, download the latest bcm43xx-fwcutter from http://developer.berlios.de/project/showfiles.php?group_id=4547 and look at the README. At the bottom, there is a link to a 4.x firmware. Get it and compile the bcm43xx-fwcutter version that you just got (the one in Ubuntu is too old) running make. Then extract the firmware via ./bcm43xx-fwcutter FWFILE and copy the .fw files to /lib/firmware. Reload the bcm43xx module (sudo rmmod bcm43xx && sudo modprobe bcm43xx) and everything should work fine then.
I'll try to get an exception in order to make the recent fwcutter version available in Feisty. |
|
| 2007-02-19 13:53:16 |
magilus |
bug |
|
|
assigned to linux-source-2.6.20 (Ubuntu) |
| 2007-02-19 14:06:45 |
magilus |
linux-source-2.6.20: status |
Unconfirmed |
Confirmed |
|
| 2007-02-19 14:06:45 |
magilus |
linux-source-2.6.20: statusexplanation |
|
|
|
| 2007-02-19 18:56:55 |
R Morrison |
bcm43xx-fwcutter: status |
Rejected |
Confirmed |
|
| 2007-02-19 18:56:55 |
R Morrison |
bcm43xx-fwcutter: statusexplanation |
In fact, this is no bug in bcm43xx-fwcutter and support has not been dropped for older cards.
The new bcm43xx driver, which went to Feisty, requires a 4.x firmware version.
In order to get one, download the latest bcm43xx-fwcutter from http://developer.berlios.de/project/showfiles.php?group_id=4547 and look at the README. At the bottom, there is a link to a 4.x firmware. Get it and compile the bcm43xx-fwcutter version that you just got (the one in Ubuntu is too old) running make. Then extract the firmware via ./bcm43xx-fwcutter FWFILE and copy the .fw files to /lib/firmware. Reload the bcm43xx module (sudo rmmod bcm43xx && sudo modprobe bcm43xx) and everything should work fine then.
I'll try to get an exception in order to make the recent fwcutter version available in Feisty. |
According to Thom the recommendation:In fact, this is no bug in bcm43xx-fwcutter and support has not been dropped for older cards. The new bcm43xx driver, which went to Feisty, requires a 4.x firmware version. In order to get one, download the latest bcm43xx-fwcutter from http://developer.berlios.de/project/showfiles.php?group_id=4547 and look at the README. At the bottom, there is a link to a 4.x firmware. Get it and compile the bcm43xx-fwcutter version that you just got (the one in Ubuntu is too old) running make. Then extract the firmware via ./bcm43xx-fwcutter FWFILE and copy the .fw files to /lib/firmware. Reload the bcm43xx module (sudo rmmod bcm43xx && sudo modprobe bcm43xx) and everything should work fine then. I'll try to get an exception in order to make the recent fwcutter version available in Feisty.
Doesn't seem to fix the issue, back to the drawing board? |
|
| 2007-02-19 19:01:17 |
R Morrison |
bcm43xx-fwcutter: status |
Confirmed |
Rejected |
|
| 2007-02-19 19:01:17 |
R Morrison |
bcm43xx-fwcutter: statusexplanation |
According to Thom the recommendation:In fact, this is no bug in bcm43xx-fwcutter and support has not been dropped for older cards. The new bcm43xx driver, which went to Feisty, requires a 4.x firmware version. In order to get one, download the latest bcm43xx-fwcutter from http://developer.berlios.de/project/showfiles.php?group_id=4547 and look at the README. At the bottom, there is a link to a 4.x firmware. Get it and compile the bcm43xx-fwcutter version that you just got (the one in Ubuntu is too old) running make. Then extract the firmware via ./bcm43xx-fwcutter FWFILE and copy the .fw files to /lib/firmware. Reload the bcm43xx module (sudo rmmod bcm43xx && sudo modprobe bcm43xx) and everything should work fine then. I'll try to get an exception in order to make the recent fwcutter version available in Feisty.
Doesn't seem to fix the issue, back to the drawing board? |
|
|
| 2007-02-19 19:04:04 |
R Morrison |
bcm43xx-fwcutter: status |
Rejected |
Confirmed |
|
| 2007-02-19 19:04:04 |
R Morrison |
bcm43xx-fwcutter: statusexplanation |
|
According to Thom the recommendation:In fact, this is no bug in bcm43xx-fwcutter and support has not been dropped for older cards. The new bcm43xx driver, which went to Feisty, requires a 4.x firmware version. In order to get one, download the latest bcm43xx-fwcutter from http://developer.berlios.de/project/showfiles.php?group_id=4547 and look at the README. At the bottom, there is a link to a 4.x firmware. Get it and compile the bcm43xx-fwcutter version that you just got (the one in Ubuntu is too old) running make. Then extract the firmware via ./bcm43xx-fwcutter FWFILE and copy the .fw files to /lib/firmware. Reload the bcm43xx module (sudo rmmod bcm43xx && sudo modprobe bcm43xx) and everything should work fine then. I'll try to get an exception in order to make the recent fwcutter version available in Feisty.
Doesn't seem to fix the issue, back to the drawing board? |
|
| 2007-02-19 19:52:07 |
magilus |
bcm43xx-fwcutter: status |
Confirmed |
Rejected |
|
| 2007-02-19 19:52:07 |
magilus |
bcm43xx-fwcutter: statusexplanation |
According to Thom the recommendation:In fact, this is no bug in bcm43xx-fwcutter and support has not been dropped for older cards. The new bcm43xx driver, which went to Feisty, requires a 4.x firmware version. In order to get one, download the latest bcm43xx-fwcutter from http://developer.berlios.de/project/showfiles.php?group_id=4547 and look at the README. At the bottom, there is a link to a 4.x firmware. Get it and compile the bcm43xx-fwcutter version that you just got (the one in Ubuntu is too old) running make. Then extract the firmware via ./bcm43xx-fwcutter FWFILE and copy the .fw files to /lib/firmware. Reload the bcm43xx module (sudo rmmod bcm43xx && sudo modprobe bcm43xx) and everything should work fine then. I'll try to get an exception in order to make the recent fwcutter version available in Feisty.
Doesn't seem to fix the issue, back to the drawing board? |
Rejecting the bcm43xx-fwcutter task, as it (WLAN broken) is no bug in bcm43xx-fwcutter. For a newer release which can extract v4 firmwares, see bug 84917. |
|
| 2007-02-21 19:14:38 |
Kevin Kubasik |
bug |
|
|
added attachment 'pciinfo.txt' (lspci output) |
| 2007-02-23 19:05:58 |
magilus |
marked as duplicate |
|
85404 |
|
