You are not logged in.
- Topics: Active | Unanswered
#1 2008-03-01 22:58:53
- TB2
- Member
- Registered: 2005-09-06
- Posts: 25
ipw3945 only working when modprobing manually / not on startup
The last kernel update broke my wireless.
When booting, the ipw3945d daemon will tell me "ERROR: Could not find Intel PRO/Wireless 3945ABG Network Connection". After it finishes booting, I can rmmod the ipw3945 module and modprobe it again. Starting the daemon after that works flawlessly. Even if I try to start the daemon manually after the booting sequence, I'll get that error. I first need to rmod and modprobe ipw3945 for it to work. So...:
[21:32:40 | shapeshifter@Tachycineta ~]$ sudo /etc/rc.d/ipw3945d start
:: Starting IPW3945d [BUSY]
2008-03-01 21:32:47: ERROR: Could not find Intel PRO/Wireless 3945ABG Network Connection
[DONE]
[21:32:48 | shapeshifter@Tachycineta ~]$ sudo rmmod ipw3945
[21:32:50 | shapeshifter@Tachycineta ~]$ sudo modprobe ipw3945
[21:32:53 | shapeshifter@Tachycineta ~]$ sudo /etc/rc.d/ipw3945d start
:: Starting IPW3945d [DONE]
[21:32:57 | shapeshifter@Tachycineta ~]$
And I have no idea why it only works when modprobing manually.
Anyone?
Last edited by TB2 (2008-03-01 23:05:33)
Offline
#2 2008-03-03 14:43:30
- zenlord
- Member
- From: Belgium
- Registered: 2006-05-24
- Posts: 1,222
- Website
Re: ipw3945 only working when modprobing manually / not on startup
Have you tried iwl3945? It's another driver which will superseed the ipw3945. Works great here in combination with the latest updates and netcfg2 to connect to a wireless LAN.
Zl.
Offline
#3 2008-03-03 22:29:56
- mcmillan
- Member
- Registered: 2006-04-06
- Posts: 737
Re: ipw3945 only working when modprobing manually / not on startup
How are you loading the module on boot? Is it specifically listed in the module array or are you relying on autoloading. I think I remember autoload wasn't working when I used ipw3945.
Other than that I can also recommend using iwl3945, I've been using it since starting to use 2.6.24 kernel and it's been working fine.
Offline
#4 2008-03-03 23:34:02
- uastasi
- Member
- From: Salento - Italy
- Registered: 2007-11-27
- Posts: 247
Re: ipw3945 only working when modprobing manually / not on startup
Check that ipw9345d is loaded before network in DAEMONS' section of /etc/rc.conf .
Other than that I can also recommend using iwl3945, I've been using it since starting to use 2.6.24 kernel and it's been working fine.
Not for me. It doesn't work properly for me because it often deassociates from access point. I'd like to use it in order to avoid ipw394d loading, but IMHO it's not ready yet.
Offline
#5 2008-03-04 08:59:41
- zenlord
- Member
- From: Belgium
- Registered: 2006-05-24
- Posts: 1,222
- Website
Re: ipw3945 only working when modprobing manually / not on startup
using iwl3945
Not for me. It doesn't work properly for me because it often deassociates from access point. I'd like to use it in order to avoid ipw394d loading, but IMHO it's not ready yet.
Are you sure it's driver-related? I have never heard anyone complain about deassociating wireless networks unless they were using networkmanager or wicd or something like that. In the various threads about netcfg2 I have never seen anyone with this problem.
Zl.
Offline
#6 2008-03-04 13:09:02
- ibendiben
- Member
- Registered: 2007-10-10
- Posts: 519
Re: ipw3945 only working when modprobing manually / not on startup
With the new kernel (.24) iwl3945 seems to work fine for me too, where before I could only use ipw3945...
I'd suggest you remove everything ipw3945 related, and try with iwl3945 once more... (update kernel)
Offline
#7 2008-03-04 14:56:50
- jonkristian
- Member
- From: Norway
- Registered: 2007-03-09
- Posts: 101
- Website
Re: ipw3945 only working when modprobing manually / not on startup
With the new kernel (.24) iwl3945 seems to work fine for me too, where before I could only use ipw3945...
I'd suggest you remove everything ipw3945 related, and try with iwl3945 once more... (update kernel)
For me, I have to do a iwlist scan before it works, i am using network-profiles and menu option in rc.conf
PROCRASTINATION
is like masturbation...it's good in the beginning, but in the end, you realize
you've just fkd yourself
Offline
#8 2008-03-04 17:21:53
- zenlord
- Member
- From: Belgium
- Registered: 2006-05-24
- Posts: 1,222
- Website
Re: ipw3945 only working when modprobing manually / not on startup
For me, I have to do a iwlist scan before it works, i am using network-profiles and menu option in rc.conf
Are you using netcfg2 v2.0.0.6 or an older version? IIRC this was a problem with the previous version.
And what do you mean with 'the menu option'?
Zl.
Last edited by zenlord (2008-03-04 17:23:47)
Offline
#9 2008-03-13 20:10:01
- uastasi
- Member
- From: Salento - Italy
- Registered: 2007-11-27
- Posts: 247
Re: ipw3945 only working when modprobing manually / not on startup
Are you sure it's driver-related? I have never heard anyone complain about deassociating wireless networks unless they were using networkmanager or wicd or something like that. In the various threads about netcfg2 I have never seen anyone with this problem.
Zl.
I don't know if it's driver-related, but it could be power-related: iwl3945 isn't able to retrieve my ap essid everytime, since on the other hand ipw3945 is able to do, with the laptop in the SAME position.
Last edited by uastasi (2008-03-13 20:10:18)
Offline
#10 2008-03-19 12:24:25
- uastasi
- Member
- From: Salento - Italy
- Registered: 2007-11-27
- Posts: 247
Re: ipw3945 only working when modprobing manually / not on startup
It seems that someone has my same problem, this is the bug -> http://bughost.org/bugzilla/show_bug.cg … le&id=1579
Offline