Restrict Drivers Manager installs firmwares only in the current-version kernel directory

[All Yours]

Binary package hint: bcm43xx-fwcutter

I am on Gutsy in Dell Inspiron 1501. I have been testing it. It has been great. It has improved hardware supports, such as bcm43xx firmware that can be installed via Restricted Drivers Manager.

A couple of days ago, the kernel of Gutsy has been upgraded. My wireless lan of chipset is based on bcm43xx did not work. I found that the firmwares installed via the Restricted Drivers Manager was placed in the previous firmware directory only.

It annoyed me because I had to connect my lap to the main hub 'with wire' again and to active the Restricted Drivers Manager again.

I suggest that the Restricted Drivers Manager should install the firmwares(not drivers) into "/lib/firmware" NOT "/lib/firmware/`uname -r`".
It will let me avoid to install the firmwares again or copy the firmware from the previous firmware directory.

Respect

[Sandip Bhattacharya (sandipb)]

I can confirm this. Putting it in "/lib/firmware/`uname -r`" breaks wireless after kernel upgradation. I have switched back to ndiswrapper till this is resolved. This is a major bug in using Restricted Drivers Manager for bcm43xx drivers.

[Matteo Z (matteozandi)]

Thanks for taking the time to report this bug, I'm marking it as duplicate of #138400.