You are not logged in.
Pages: 1
Hi All,
I just got an update to ipw3945d-1.7.22-2 and since the update, my wireless won't start at boot anymore.
When I then manually enter iwconfig eth2 yadayadayada, ifconfig eth2 up and dhcpd eth2 it works fine.
Any ideas?
thx,
Leon..
Offline
Will test and take a look on this.
Are you sure your rc.conf and conf.d/wireless have eth2 entered? so the device didn't change?
Maybe a completely different problem, got also a 1945d card on my notebook, but i can't test right now at work... some hours maybe.
Ability is nothing without opportunity.
Offline
Will test and take a look on this.
Are you sure your rc.conf and conf.d/wireless have eth2 entered? so the device didn't change?
Maybe a completely different problem, got also a 1945d card on my notebook, but i can't test right now at work... some hours maybe.
yup, the only change to my system was the update..
Offline
see post below... was wrong information
Ability is nothing without opportunity.
Offline
i have a different kind of problem but also with an ipw3945d driver. when i want to connect to internet with wifi-radar, kernel spits some information out on vc/1 listing all loaded modules and some more information. and then i cant run any program and i need to restart. if i run wifi-radar daemon at startup it writes the same message and everything stops loading. i'll try to retype what it is written on vc/1.
oh and i noticed that after using ethernet cable connection i have 600MB (out of 1024MB) more free ram . . . Before it was always almost full (at least after firefox was started)
EDIT: and the key (fn+F2) doesn't work to turn on the wireless but just to shut down
Offline
Well... located the problem.
The error i posted above is wrong.
The device is not ready on boot time, it seems as if the driver needs too long to initialize the ressource.
The driver loads - indeed it does. but the network isn't ready this time. the boot progress goes on, and the device is not there yet.
Some secs later, it is there.
I tried some scripts on load of ipw3945, using /sbin/ipw3945d --isrunning, in a until loop. The daemon says it's running - sure, the daemon runs, but it would take longer.
I simply think the driver / daemon needs a load on time to boot up.
simply doing
/sbin/ipw3945d --isrunning
if [ $? -eq 0 ]; then
echo "daemon running.."
fi
says it's running. 0 is the status for running in the daemon.
WORKAROUND
I simply set the sleep in the /etc/rc.d/ipw3945d up to 10 secs from 1 sec... isn't nice but works.
I'll file a bug report at ipw, i'd appreciate a function to check if the ressource is allocated or not.
I contacted James Ketrenos at intel, and filed a bug report to the ipw3945 project, maybe he knows a solution, it's a well known problem of this driver.
// STi
Ability is nothing without opportunity.
Offline
Pages: 1