FS#8679 - Error in ipw3945d PKGBUILD
Attached to Project:
Arch Linux
Opened by Jakub Schmidtke (tanis) - Saturday, 17 November 2007, 17:35 GMT
Last edited by Thomas Bächler (brain0) - Friday, 05 December 2008, 12:58 GMT
Opened by Jakub Schmidtke (tanis) - Saturday, 17 November 2007, 17:35 GMT
Last edited by Thomas Bächler (brain0) - Friday, 05 December 2008, 12:58 GMT
|
Details
Description:
The newest ipw3945d package (from testing, I have no idea if previous versions did the same) after installation prints this message: AUTOMATIC DAEMON LOADING VIA MODPROBE ==> To do this, you typically place the following two lines into your ==> /etc/modprobe.conf: ==> echo install ipw3945 /sbin/modprobe --ignore-install ipw3945 ; ==> sleep 0.5 ; /sbin/ipw3945d --quiet >> /etc/modprobe.conf ==> ==> echo remove ipw3945 /sbin/ipw3945d --kill ; ==> /sbin/modprobe -r --ignore-remove ipw3945 >> /etc/modprobe.conf I think it should tell the user to do: echo "install ipw3945 /sbin/modprobe --ignore-install ipw3945 ; sleep 0.5 ; /sbin/ipw3945d --quiet" >> /etc/modprobe.conf echo "remove ipw3945 /sbin/ipw3945d --kill ; /sbin/modprobe -r --ignore-remove ipw3945" >> /etc/modprobe.conf (With " ", and no '==>' - which could overwrite /sbin/modprobe) |
This task depends upon
Closed by Thomas Bächler (brain0)
Friday, 05 December 2008, 12:58 GMT
Reason for closing: None
Additional comments about closing: The package is no longer part of Archlinux.
Friday, 05 December 2008, 12:58 GMT
Reason for closing: None
Additional comments about closing: The package is no longer part of Archlinux.
Comment by Greg (dolby) - Sunday, 04
May 2008, 18:37 GMT
Comment by eliott (cactus) -
Thursday, 08 May 2008, 06:45 GMT
Comment by Greg (dolby) - Saturday,
10 May 2008, 10:23 GMT
Comment by Gavin Bisesi (Daenyth) -
Wednesday, 04 June 2008, 18:15 GMT
Comment by Jakub Schmidtke (tanis) -
Sunday, 15 June 2008, 16:04 GMT
oh sorry about the closure request, i looked at ipw3945 instead of
ipw3945d
Is this still an issue then?
yes the message appears to be still present
What about the iwlwifi module?
iwlwifi doesn't use separate daemon, and has no separate package,
so this bug is not relevant.