Hi Jim,
Progress, then :)
> I continue to have some difficulties, though. Even with the renaming
> fixed, the ifup script does not work (with wlan0), and I have to go
> through the ifconfig, iwconfig. dhclient routine.
I use network-manager for managing my wireless connection as I find that it is
more suited to travelling between different wireless networks that I
inevitably do, so I don't have experience with this chip and configuration
through /e/n/interfaces.
I do notice on the debian wiki page for the iwlwifi driver that there is a
config snippet for /e/n/interfaces which includes a pre-up command to make
the wireless card wake up and cause it to do an initial scan or association
or something. That might help with that problem.
http://wiki.debian.org/iwlwifi
Also, check that you have the right names for the device in /e/n/interfaces --
perhaps posting that file along with the output of "ifconfig -a" "iwconfig"
and "ifup wlan0" would be helpful.
> More seriously, the
> link does not survive a suspend-resume cycle (it always did before).
Well, the comment about that config snippet on the debian wiki page says that
such a configuration helps bring the connection back up after a
suspend-to-ram, so that might solve your problem too.
I have also found that blacklisting the module for suspend (how you do so
depends on what suspend wrappers you are using) helps as it then gets removed
just before suspend and reinserted just after resume. I've also found
(sometimes) that doing an extra "modprobe -r iwl3945; modprobe iwl3945" some
time after resume helps. Once again, the suspend scripts usually have some
way of hooking in such calls, perhaps by dropping the script into /etc/init.d
and calling it a "service to be restarted".
But as you said... things will improve on their own with time too :)
Happy hunting.
Stuart
--
Stuart Prescott www.nanoNANOnano.net
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
