Booting a Slackware laptop previouly connected to a wifi essid

jayhel · 01-17-2007, 08:56 PM

Hi!

When I boot Slackware on a laptop that was previouly configured to connect on a wifi network in a new location, it hangs when it comes to the dhcp resolution since it can't find the ESSID it was connected to previously.
I tried any combination of keys to override and complete the boot sequence: nothing works.
I have to boot with another kernel that does not support wifi (vmlinux from the distro), comment dhcp=yes in rc.inet1.conf and then reboot again.

What a pain!

Is there something more efficient I could do?

MS3FGX · 01-17-2007, 09:03 PM

It probably isn't actually hanging. The default DHCP timeout in Slackware is an overly-long 1 minute, so if it can't connect to the AP, it is going to sit there for 60 seconds doing nothing, which is probably what is happening.

The easiest way to remedy this, and something I do on every Slackware install, is to edit the timeout value in rc.inet1.