module_name.blacklist=yes not working as designed

[Fridtjof Busse]

When booting oneiric Beta 1 via PXE (netboot.tar.gz) with the documented blacklist parameter, in this case "usb.storage.blacklist=yes", the installer fails with "Error while running 'modprobe -v usb-storage'".
This is due to the fact that the blacklist parameter is also passed to the module itself, which doesn't know anything about this parameter.
You can veryify this via dmesg:
usb_storage: Unknown parameter 'blacklist'

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 845561

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Fridtjof Busse (fbusse-deactivatedaccount-deactivatedaccount)]

And how would you like me to run apport in a PXE environment?
Reproducing this is extremly simple btw.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[Lucas Magasweran (lucasrangit)]

Try modprobe.blacklist=module_name to blacklist the loading of the module at boot time. You can still insert it later if you need.