Re: wireless quits every few hours [SOLVED]
On Sat, Sep 18, 2010 at 11:30 AM, Kamaraju S Kusumanchi raju.mailingli...@gmail.com wrote: John wrote: I wonder why the linux driver for one of the oldest standard wifi cards (Cisco aironet) doesn't work properly, but Windows does. Don't see that too often. John If there is room for experimentation, I'd install a newer kernel and see if the problem goes away. I think I'll pass on that, since Squeeze will come along one of these days. When I started this thread, my wireless on Linux crashed so often it was unbearable! After this thread, and people had given me good ideas, it ran for days! Go figger. ANYWAY, it finally crashed again. I can now confirm, after a crash I can fix my wireless networking without a reboot, like this: r...@thinkpad:/home/john# modprobe -r airo r...@thinkpad:/home/john# modprobe -a airo r...@thinkpad:/home/john# /etc/init.d/networking start My thanks to everybody for the great advice. John -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktin-mhqd39bhzk-0p-blqw=4q58èfnejs7m...@mail.gmail.com
Re: wireless quits every few hours
On Vi, 17 sep 10, 16:30:06, John wrote: Hardware: IBM T30 laptop with internal Cisco Airo type of wireless card. In other words, support is built into the kernel. Please post the relevant line from 'lspci' So, question 1, what happens during reboot, that doesn't happen during ifdown/ ifup Loading the module ;) Or, putting it another way, what can I type from the command line to do the same network restart as if I was rebooting. Remove and reinsert the module. This works for me with iwlagn (on recent firmware versions the wireless can disconnect under heavy loads, it works fine otherwise) Regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
wireless quits every few hours
On Sat, Sep 18, 2010 at 2:30 AM, Andrei Popescu andreimpope...@gmail.com wrote: Please post the relevant line from 'lspci' At the moment, it's still working, but here's the line from lspci: 02:02.0 Network controller: AIRONET Wireless Communications Cisco Aironet Wireless 802.11b -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlkti=ymspcdqug5uz_=ohhrh64znht2=sdkjh2n...@mail.gmail.com
Re: wireless quits every few hours
On Sat, Sep 18, 2010 at 3:25 AM, John nesre...@gmail.com wrote: On Sat, Sep 18, 2010 at 2:30 AM, Andrei Popescu andreimpope...@gmail.com wrote: Please post the relevant line from 'lspci' At the moment, it's still working, but here's the line from lspci: 02:02.0 Network controller: AIRONET Wireless Communications Cisco Aironet Wireless 802.11b Ok, Andrei, I finally get it now. I just removed the module called airo from the kernel (networking died), and replaced it, and did the networking start thing and, indeed, the networking came back to life. If that works when I run into the random network death, I can quickly revive things. Thanks. I wonder why the linux driver for one of the oldest standard wifi cards (Cisco aironet) doesn't work properly, but Windows does. Don't see that too often. John -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktikzsnp0omvm1_jwqzqpgkffnnpa81yimyckh...@mail.gmail.com
Re: wireless quits every few hours
On Sat September 18 2010, John wrote: Ok, Andrei, I finally get it now. I just removed the module called airo from the kernel (networking died), and replaced it, and did the networking start thing and, indeed, the networking came back to life. I have had a similar problem in the past.. but I'm not aware of how to load/unload these modules. Could you explain exactly what you did?? If that works when I run into the random network death, I can quickly revive things. Thanks. thanks -- Paul Cartwright Registered Linux user # 367800 Registered Ubuntu User #12459 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201009180633.32735.deb...@pcartwright.com
Re: wireless quits every few hours
On Sat, Sep 18, 2010 at 6:33 AM, Paul Cartwright deb...@pcartwright.com wrote: On Sat September 18 2010, John wrote: Ok, Andrei, I finally get it now. I just removed the module called airo from the kernel (networking died), and replaced it, and did the networking start thing and, indeed, the networking came back to life. I have had a similar problem in the past.. but I'm not aware of how to load/unload these modules. Could you explain exactly what you did?? Sure. I figured out what the module is called by doing: lsmod For my wireless card, the module is called airo Remove the module, add the module back, and (re)start the network: modprobe -r airo modprobe -a airo /etc/init.d/networking start I'm on another machine right now so I'm going by memory; let me know if that doesn't work. John -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktikn3u9smzl-xn0s+nj+dsap6ybu1vfdveqx-...@mail.gmail.com
Re: wireless quits every few hours
On Sat September 18 2010, John wrote: Sure. I figured out what the module is called by doing: lsmod For my wireless card, the module is called airo Remove the module, add the module back, and (re)start the network: modprobe -r airo modprobe -a airo /etc/init.d/networking start that sounds about right, thanks! -- Paul Cartwright Registered Linux user # 367800 Registered Ubuntu User #12459 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201009180939.27980.deb...@pcartwright.com
Re: wireless quits every few hours
John wrote: I wonder why the linux driver for one of the oldest standard wifi cards (Cisco aironet) doesn't work properly, but Windows does. Don't see that too often. John If there is room for experimentation, I'd install a newer kernel and see if the problem goes away. -- Kamaraju S Kusumanchi http://malayamaarutham.blogspot.com/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/i72lua$he...@dough.gmane.org
wireless quits every few hours
I writing this on Windows XP (yuck) because rebooting my linux system every few hours is driving me crazy. On Windows, it will run for days. So I think hardware is probably not the problem. Hardware: IBM T30 laptop with internal Cisco Airo type of wireless card. In other words, support is built into the kernel. O/S is Mepis 8, which is Debian Lenny, more or less. Encryption is WEP What happens is that wireless will die randomly after a few hours. Mepis has a nice network wizard, but using it to restart the network won't fix things. ifdown eth1 followed by ifup eth1 won't fix it either. I must reboot the machine, but that works every time. So, question 1, what happens during reboot, that doesn't happen during ifdown/ ifup Or, putting it another way, what can I type from the command line to do the same network restart as if I was rebooting. If I can get that far, I can start worrying about what is actually causing the problem, but I would like to be able to restart without rebooting. Any hints? Thanks. John -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktimc8gpaomsx7ont2giype7x1mwpvafk9yu-x...@mail.gmail.com
Re: wireless quits every few hours
John wrote: Or, putting it another way, what can I type from the command line to do the same network restart as if I was rebooting. After doing the ifup thing, run the following command (as root) and see if it helps. # /etc/init.d/networking restart -- Kamaraju S Kusumanchi http://malayamaarutham.blogspot.com/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/i71102$e7...@dough.gmane.org
Re: wireless quits every few hours
On Fri, Sep 17, 2010 at 8:26 PM, Kamaraju S Kusumanchi raju.mailingli...@gmail.com wrote: John wrote: Or, putting it another way, what can I type from the command line to do the same network restart as if I was rebooting. After doing the ifup thing, run the following command (as root) and see if it helps. # /etc/init.d/networking restart Ok, I can confirm when I boot up and things are working, ifdown eth1 shuts wireless, ifup1 starts up, and the /etc/init.d/networking restart does restart Ok, more clues. I say that it restarts because the network monitor popup shows and does the ding thing. But I _think_ in fact, the network was killed by trying to restart. I saved the terminal output and rebooted. Here's what it said: Error for wireless request Set Bit Rate (8B20) : SET failed on device eth1 ; Invalid argument. * Starting portmap daemon... * Already running. ...done. * Starting NFS common utilities ...done. r...@thinkpad:/home/john# /etc/init.d/networking restart * Reconfiguring network interfaces... Error for wireless request Set Bit Rate (8B20) : SET failed on device eth1 ; Invalid argument. * Starting portmap daemon... * Already running. ...done. * Starting NFS common utilities ...done. THEREFORE, one might guess, during reboot it does NOT try to set bit rate with the bad argument, but on a CL restart, it does try to set bit rate and that's what makes it fail. If so, which startup file needs the surgery? Or am I totally on the wrong track? John -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktincnmut6hwqkl_b-cwkg9u6-po=n9+ga35pc...@mail.gmail.com
Re: wireless quits every few hours
On Fri, Sep 17, 2010 at 9:22 PM, John nesre...@gmail.com wrote: On Fri, Sep 17, 2010 at 8:26 PM, Kamaraju S Kusumanchi raju.mailingli...@gmail.com wrote: John wrote: Or, putting it another way, what can I type from the command line to do the same network restart as if I was rebooting. After doing the ifup thing, run the following command (as root) and see if it helps. # /etc/init.d/networking restart Ok, I can confirm when I boot up and things are working, ifdown eth1 shuts wireless, ifup1 starts up, and the /etc/init.d/networking restart does restart Ok, more clues. I say that it restarts because the network monitor popup shows and does the ding thing. But I _think_ in fact, the network was killed by trying to restart. I saved the terminal output and rebooted. Here's what it said: Error for wireless request Set Bit Rate (8B20) : SET failed on device eth1 ; Invalid argument. * Starting portmap daemon... * Already running. ...done. * Starting NFS common utilities ...done. r...@thinkpad:/home/john# /etc/init.d/networking restart * Reconfiguring network interfaces... Error for wireless request Set Bit Rate (8B20) : SET failed on device eth1 ; Invalid argument. * Starting portmap daemon... * Already running. ...done. * Starting NFS common utilities ...done. THEREFORE, one might guess, during reboot it does NOT try to set bit rate with the bad argument, but on a CL restart, it does try to set bit rate and that's what makes it fail. If so, which startup file needs the surgery? Or am I totally on the wrong track? John Ok, forget about all of that. I can ifdown and ifup and networking restart and even networking force-reload, and I always get that error message BUT the network always starts up instantly. I guess the failure I had above was just a coincidence. I think it will actually have to wait until it crashes by itself. John -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktinwajeqgnx1xhtjdjmjp_w78cgaf3o9+fwvf...@mail.gmail.com
