I'm actually having this same problem. I installed via the text-only disc, ran "sudo apt-get update", then "sudo apt-get install bcm43xx- fwcutter". After retrieving and unpacking the package, here's what it spit back at me:
Setting up bcm43xx-fwcutter (1:006-1) ... --05:40:37-- http://boredklink.googlepages.com/wl_apsta.o => `wl_apsta.o' Resolving boredklink.googlepages.com... 72.14.203.118 Connecting to boredklink.googlepages.com|72.14.203.118|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 756 [text/html] 100%[===================================>] 756 --.--K/s 05:40:37 (41.62 MB/s) - `wl_apsta.o' saved [756/756] Sorry, the input file is either wrong or not supported by bcm43xx-fwcutter. This file has an unknown MD5sum a58843b5ee79d015adf8c54178186487. dpkg: error processing bcm43xx-fwcutter (--configure): subprocess post-installation script returned error exit status 255 Errors were encountered while processing: bcm43xx-fwcutter E: Sub-process /usr/bin/dpkg returned an error code (1) $ I reinstalled Feisty, got the same error message, completely removed bcm43xx-fwcutter (and the firmware file it placed in /tmp) and then installed the package again and it went through fine. (I've since reinstalled Gutsy) So it appears the place the script is getting the firmware from isn't all that reliable, perhaps? -- bcm43xx-fwcutter required by restricted-manager, but isn't included https://bugs.launchpad.net/bugs/124304 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
