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#10362 - blacklist new firewire-core
Attached to Project:
Arch Linux
Opened by Ingo (smove) - Monday, 05 May 2008, 17:45 GMT
Last edited by Thomas Bächler (brain0) - Monday, 05 May 2008, 21:56 GMT
Opened by Ingo (smove) - Monday, 05 May 2008, 17:45 GMT
Last edited by Thomas Bächler (brain0) - Monday, 05 May 2008, 21:56 GMT
|
DetailsDescription:
Since i upgraded my system to a new kernel-package i am unable to use my firewire-card. I have researched a lot and came to the conclusion, that the new kernel uses the new "juju"-ieee1394 stack instead of the old one. The only solution to make it work again is to blacklist the firewire-ohci and firewire-sbp2 modules in /etc/modprobe.conf. I don´t know if it´s a good decision to use the new firewire-core. Refering to http://wiki.linux1394.org/JujuMigration#head-d85e38e688c6424c37741239c8c6b1857ee71b93 it seems to be not a good idea to use the new stack yet because of its experimental state. Additional info: i added following file: /etc/modprobe.d/juju_firewire_blacklist: blacklist firewire-ohci blacklist firewire-sbp2 |
This task depends upon