Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#7900 - ipw3945 and hibernate-script, unloading module
Attached to Project:
Arch Linux
Opened by Martin (dante) - Monday, 27 August 2007, 10:37 GMT
Last edited by Thomas Bächler (brain0) - Tuesday, 28 August 2007, 09:33 GMT
Opened by Martin (dante) - Monday, 27 August 2007, 10:37 GMT
Last edited by Thomas Bächler (brain0) - Tuesday, 28 August 2007, 09:33 GMT
|
DetailsWhen using hibernate-script, I get this message:
sudo hibernate -n Passwort: :: Saving ALSA Levels [BUSY] [DONE] Some modules failed to unload: [permanent] hibernate: Aborting suspend due to errors in ModulesUnloadBlacklist (use --force to override). :: Restoring ALSA Levels [BUSY] [DONE] The problem is the ipw3945 module, which is new in "/etc/hibernate/blacklisted-modules". Unloading ipw3945 gives this message: sudo rmmod ipw3945 Passwort: ERROR: Module ipw3945 is in use by [permanent] Additional info: * hibernate-script-1.96-2 * ipw3945 1.2.1-6 |
This task depends upon
Comment by Jan de Groot (JGC) -
Monday, 27 August 2007, 17:24 GMT
You can't unload ipw3945 without also stopping the ipw3945 daemon. BTW: you don't need to unload this driver to go to suspend/hibernate.
Comment by Martin (dante) -
Monday, 27 August 2007, 21:53 GMT
But why is the ipw3945 module in "/etc/hibernate/blacklisted-modules" for the hibernate-script-1.96 release? Removing ipw3945 from "/etc/hibernate/blacklisted-modules" let the system hibernate as before.
Comment by Thomas Bächler (brain0) -
Tuesday, 28 August 2007, 09:33 GMT
When you don't blacklist ipw3945, it sometimes won't work properly after resume. If you use RestartDaemons ipw3945d in common.conf, you will be able to blacklist. Removing the module from the blacklist may work or may not work, that is for you to decide, I had problems in the past.