Prev: Compiling 2.6.32.9 on Slackware 13
Next: No rootdisks/ in 13. Help me a bit here.
From: Jim Diamond on 3 Mar 2010 09:55
On 2010-02-27 at 07:13 AST, phunehehe <phunehehe(a)gmail.com> wrote:
> On Feb 26, 11:57�pm, Douglas Mayne <inva...(a)invalid.com> wrote:
>> On Fri, 26 Feb 2010 08:53:39 -0800, phunehehe wrote:
>> > Hallo,
>> > I managed to set up wifi for my laptop and everything is working fine.
>> > However, every time I let the computer go to sleep and wake it up, it
>> > just cannot connect anymore. I tried `sudo /etc/rc.d/rc.inet1 stop` then
>> > `sudo /etc/rc.d/inet1 wlan0_start` but it doesn't do the trick. Now I
>> > need to shutdown, instead of sleep, so that I can connect (everything
>> > turns out OK after a reboot). So, how can I possibly restart the whole
>> > networking thing, so that I don't have to reboot my computer?
>> > Thanks,
>>
>> I use wicd to manage wireless connections. I have it set to require
>> manual reconnection after resume from suspend/hibernate, but it may also
>> have an automatic mode. Check out wicd, from the extra package group.
>>
>> --
>> Douglas Mayne
>
> Hi Douglas,
> So the wicd thing is included in the slackware CD? I wonder why it
> doesn't recognize the command when I type "wicd" in a terminal (I
> installed a full version of slackware so it should be there, right?).
> I will try to install wicd if I must, but it's still nice if I can get
> the thing restart through the command line. Well I don't need an
> automatic mode, but my wifi just doesn't reconnect :(

When I first started using wicd, I was very happy with how well it
worked (except wicd-client rolls over and dies in certain
circumstances related to the use of stalonetray, but that's a
different issue).

To make it reconnect for me after a resume, I put
/usr/lib*/wicd/autoconnect.py >$TTY 2>&1 &
in /etc/acpi/acpi_handler.sh (where TTY is a terminal device I set earlier)
and that was working fine as well.

However, recently it has been sporadically failing to connect after I
resume from a S2R. Looking in /var/log/wicd/wicd.log, it complains
about not being able to ping my router after it does the
wpa_supplicant, iwconfig, ifconfig, route and DNS stuff. Bringing up
the GUI and getting it to attempt another connection fails as
miserably. This is quite repeatable.

Interestingly, if I enter the same commands in a terminal, everything
works fine. This suggested to me (and others) that the ping'ing to
verify AP association was happening too quickly. I d/l'ed and
installed wicd 1.7.0, where the ping is tried 10 times with 1 second
sleeps between tries, and that has the same issues.

So in summary, if anyone else has seen this problem and figured out a
robust solution, please share.

And to the OP: if you try wicd and you get this problem, you could try
looking in /var/log/wicd/wicd.log, see the commands it tries, and type
them (as root) in a terminal, and see if that gets you connected.

Cheers.
Jim
From: phunehehe on 4 Mar 2010 00:40
On Mar 3, 4:41 pm, Eef Hartman <E.J.M.Hart...(a)tudelft.nl> wrote:
> phunehehe <phuneh...(a)gmail.com> wrote:
> > On Feb 26, 11:57 pm, Douglas Mayne <inva...(a)invalid.com> wrote:
> > So the wicd thing is included in the slackware CD? I wonder why it
> > doesn't recognize the command when I type "wicd" in a terminal (I
> > installed a full version of slackware so it should be there, right?).
>
> A "full" install is: everything in the "slackware" tree.
> As wicd is in the "extra" one, it MUST be installed by hand, too many
> packages in "extra" conflict with those in "slackware" (or even each
> other) for to auto-install them.
>
> This is the contents (subdirs only) of "extra" in 13.0, it should be
> in the DVD image too:
> aspell-word-lists       08/14/2009      12:00:00 AM
> bash-completion         07/16/2009      12:00:00 AM
> bittornado              05/07/2009      12:00:00 AM
> bittorrent              05/07/2009      12:00:00 AM
> blackbox-0.70.1         05/07/2009      12:00:00 AM
> brltty                  08/21/2009      12:00:00 AM
> btmgr-3.7               05/07/2009      12:00:00 AM
> checkinstall            06/30/2007      12:00:00 AM
> dip-3.3.7p              05/07/2009      12:00:00 AM
> emacspeak               05/07/2009      12:00:00 AM
> emacspeak-ss-1.9.1      05/07/2009      12:00:00 AM
> grub                    05/07/2009      12:00:00 AM
> inn                     05/07/2009      12:00:00 AM
> jdk-6                   08/14/2009      12:00:00 AM
> kde3-compat             06/19/2009      12:00:00 AM
> linux-2.6.29.6-nosmp-sdk 08/18/2009     12:00:00 AM
> mpg123                  05/07/2009      12:00:00 AM
> mplayerplug-in          08/21/2009      12:00:00 AM
> slacktrack              07/18/2009      12:00:00 AM
> source                  08/26/2009      12:00:00 AM
> tightvnc                06/16/2009      12:00:00 AM
> wicd                    08/26/2009      12:00:00 AM
> xf86-video-intel-alternate 08/26/2009   12:00:00 AM
>
> > I will try to install wicd if I must, but it's still nice if I can get
> > the thing restart through the command line. Well I don't need an
> > automatic mode, but my wifi just doesn't reconnect :(
> > Phu
>
> --
> *******************************************************************
> **  Eef Hartman, Delft University of Technology, dept. SSC/ICT   **
> **  e-mail: E.J.M.Hart...(a)tudelft.nl - phone: +31-15-278 82525   **
> *******************************************************************

Yay cool, thanks for the explanation, much clearer now. I'll see to
wicd.
From: phunehehe on 4 Mar 2010 00:49
On Mar 1, 6:13 am, news10p...(a)moo.uklinux.net wrote:
> phunehehe <phuneh...(a)gmail.com> wrote:
> > Hallo,
> > I managed to set up wifi for my laptop and everything is working fine.
> > However, every time I let the computer go to sleep and wake it up, it
> > just cannot connect anymore. I tried `sudo /etc/rc.d/rc.inet1 stop`
> > then `sudo /etc/rc.d/inet1 wlan0_start` but it doesn't do the trick.
> > Now I need to shutdown, instead of sleep, so that I can connect
> > (everything turns out OK after a reboot).
> > So, how can I possibly restart the whole networking thing, so that I
> > don't have to reboot my computer?
>
> I had something similar on my laptop that I "fixed" by a rmmod/modprobe
> sequence on the affected modules after coming out of suspend.  I have
> no idea wehther it was the best solution, but it worked, and never
> bothered to look further.
>
> (A S12.1 system with a newer kernel to get the ipw2200 drivers)
>
> #Paul

Hi Paul,
I think this just what I need, but how do you actually do it? I've
never used modprobe before.
Can you give me the commands?
Thanks
From: phunehehe on 4 Mar 2010 00:59
On Mar 4, 12:49 pm, phunehehe <phuneh...(a)gmail.com> wrote:
> On Mar 1, 6:13 am, news10p...(a)moo.uklinux.net wrote:
>
>
>
>
>
> > phunehehe <phuneh...(a)gmail.com> wrote:
> > > Hallo,
> > > I managed to set up wifi for my laptop and everything is working fine..
> > > However, every time I let the computer go to sleep and wake it up, it
> > > just cannot connect anymore. I tried `sudo /etc/rc.d/rc.inet1 stop`
> > > then `sudo /etc/rc.d/inet1 wlan0_start` but it doesn't do the trick.
> > > Now I need to shutdown, instead of sleep, so that I can connect
> > > (everything turns out OK after a reboot).
> > > So, how can I possibly restart the whole networking thing, so that I
> > > don't have to reboot my computer?
>
> > I had something similar on my laptop that I "fixed" by a rmmod/modprobe
> > sequence on the affected modules after coming out of suspend.  I have
> > no idea wehther it was the best solution, but it worked, and never
> > bothered to look further.
>
> > (A S12.1 system with a newer kernel to get the ipw2200 drivers)
>
> > #Paul
>
> Hi Paul,
> I think this just what I need, but how do you actually do it? I've
> never used modprobe before.
> Can you give me the commands?
> Thanks

Ah I figured it out
# modprobe -vr ath9k
# modprobe -v ath9k
Thanks
From: Joost Kremers on 4 Mar 2010 05:42
phunehehe wrote:
> Ah I figured it out
> # modprobe -vr ath9k
> # modprobe -v ath9k

probably a better way is to create/edit the file /etc/pm/config.d/modules with
the following line:

SUSPEND_MODULES="ath9k"

see /usr/doc/pm-utils-<blah>/README.Slackware. the modules mentioned in
SUSPEND_MODULES are automatically removed before suspend and reloaded again
after a resume.


--
Joost Kremers joostkremers(a)yahoo.com
Selbst in die Unterwelt dringt durch Spalten Licht
EN:SiS(9)
First  |  Prev  | 
Pages: 1 2 3
Prev: Compiling 2.6.32.9 on Slackware 13
Next: No rootdisks/ in 13. Help me a bit here.