Prev: Compiling 2.6.32.9 on Slackware 13
Next: No rootdisks/ in 13. Help me a bit here.
From: phunehehe on 26 Feb 2010 11:53
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,
From: Douglas Mayne on 26 Feb 2010 11:57
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
From: phunehehe on 27 Feb 2010 06:13
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 :(
Phu
From: Thomas Overgaard on 27 Feb 2010 08:01

phunehehe(a)gmail.com wrote :

> So the wicd thing is included in the slackware CD?

Wicd isn't installed by default, You'll find it the /extra directory.
--
Thomas O.

This area is designed to become quite warm during normal operation.
From: Douglas Mayne on 27 Feb 2010 08:07
On Sat, 27 Feb 2010 03:13:04 -0800, phunehehe 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?
It is not part of the "base" install. It is in the group extra:
http://mirrors.xmission.com/slackware/slackware-13.0/extra/wicd

>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?).

The command line version is wicd-curses. (This assumes that the "base"
package l/urwid-0.9.8.4-i486-1.txz is installed. Your user name must
also be present in the group "netdev". The daemon /etc/rc.d/rc.wicd must
be made executable, and then executed, etc. Check the file,
extra/wicd/README.SLACKWARE)

> 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
>
If your user is in the "netdev" group, then you can dynamically connect
to any visible/available wireless network by simply browsing the list of
available networks. That is a handy feature, especially for laptops
connecting at a variety of locations: house, coffee shop, hotel, library,
office, etc. It makes it very easy! Here is a screenshot from a netbook
with wicd running:
http://www.xmission.com/~ddmayne/misc/ss.2010-02-22.02.png

The "tray" icon is immediately to the right of the battery icon (battery
is reading red/low). The wireless strength on the wicd icon is showing
about 7/8ths, or "very good" reception.

These types of tray indicators are essential for laptops, IMO. YMMV. It's
hard to try to convince someone to use GNU/Linux without some modern
tools to aid ease of use. When these tools are present, it places OS
competitors on a more or less equal footing.

--
Douglas Mayne
 |  Next  |  Last
Pages: 1 2 3
Prev: Compiling 2.6.32.9 on Slackware 13
Next: No rootdisks/ in 13. Help me a bit here.