You are not logged in.
and i say issue, because its not really a problem. the wireless works. im using an intel 2915 adapater, ipw2200 driver
issue is, when i boot up my system and the knetworkmanager tries to connect, i have to wait for it to fail, and then go in an pick my network that it couldnt connect to automatically, but it connects fine manually after its failed to auto connect
does that make sense to anyone? it takes a while for it to fail the first autoconnect, thats why its posing an issue. arch is supposed to be up and running fast right?
this is a signature
Offline
anyone?
this is a signature
Offline
This might help avoid the delay... loading in background.
http://bbs.archlinux.org/viewtopic.php?id=17723
I also found this in this other thread that might help...
http://bbs.archlinux.org/viewtopic.php?id=8233
Hi Dave,
It's possible that the DHCP request is timing out. By default, the network script calls dhcpcd with a 10-second timeout. You can adjust this by editing /etc/rc.d/network and changing the timeout.
# 60-second timeout /usr/sbin/dhcpcd -t 60 -h $HOSTNAME $1
I'll have some dhcp options in the proper location (/etc/conf.d or rc.conf) soon.
Last edited by stingray (2007-10-05 03:54:42)
Offline
Heh.. three year old quote from apeiro.
He actually did make that change, too - dhcpcd run-time options go in /etc/conf.d/dhcpcd.
Offline
Heh.. three year old quote from apeiro.
3 years? LOL, I had a timing problem with the network about a year ago, and had that thread flaged...
Offline