|
Quote:
|
Didn't have to wait for too long, as it happened again...
|
Quote:
|
Here it is: http://pastebin.com/m7a7bc2e3
Could be of any more help to have the messages I find as soon as I find the network down? I mean, before a reboot... |
You can see your self:
[ 35.763086] wlan0: direct probe to AP 00:17:33:9b:de:85 try 1 [ 35.769861] wlan0: direct probe to AP 00:17:33:9b:de:85 try 1 [ 35.769880] wlan0 direct probe responded [ 35.769883] wlan0: authenticate with AP 00:17:33:9b:de:85 [ 35.772923] wlan0: authenticated [ 35.772928] wlan0: associate with AP 00:17:33:9b:de:85 [ 35.775303] wlan0: RX AssocResp from 00:17:33:9b:de:85 (capab=0x401 status=0 aid=1) [ 35.775308] wlan0: associated [ 35.795743] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 46.008045] wlan0: no IPv6 routers present [ 163.644011] CE: hpet increasing min_delta_ns to 15000 nsec [ 172.089068] CE: hpet increasing min_delta_ns to 22500 nsec [ 1003.401446] CE: hpet increasing min_delta_ns to 33750 nsec Your wireless adapter was associated and didn't lost connection any more. How about to consider possibility to change NetworkManager to WICD for example. May be it helps somehow? |
Hi again
Try the following command as root, when you machine can no longer connect to your ISP: # iwlist wlan0 scan if you get no joy and your wifi card hasn't gotten too hot and still appears to be functional - I don't if it has any led lights that indicate it is transmitting and or receiving then it appears to me that your ISP ap (access point) has dropped you rather than your machine, your wifi card or your ubuntu os dropping the connection at your end. Luckily, I have an old acer tablet lapop running XP that I can crank up to check if there is a signal in the air when I get dropped because the signal becomes too weak. When I was trying karmic this resulted in my machine trying to scan for the strongest signal in town and then trying to connect - unsuccessfully - using my static ip settings. Very boring. Hopefully you are back online shortly. Cheers |
nimnull, I already switched to wicd after the first reply in this thread.
Besides, the output of dmesg you see is *after* the reboot. What you point out is probably the result of my wifi card connecting to the ap after rebooting the machine. I can't really understand those timestamps (those between brackets are timestamps, right?), so I cannot say for sure, but that seems very likely to me. minrich, already tried that, the laptop doesn't find any wireless network. I mean, I live in an apartment block and at any time of the day I can scan at least five or six other networks, my neighbor's. Actually, when my network goes down, my laptop doesn't get disconnected: wicd says I'm still connected but the power of the signal has dropped to -256 dbm, with no other network to be found. I tried to disconnect manually and rescan for available networks but nothing came up. That is, until I reboot. I can say everything is fine on the part of my ap and isp since I can connect my phone. Sadly I don't have another computer to run any deeper test. It looks to me that it's a hardware related problem. Of course it shouldn't be a faulty wireless card since under windows everything ran fine. It must be the kernel or drivers or firmware or whatever messing with my wifi card in some way. Anyway, thanks for your time so far. Should you ever come up with some other idea, please let me know. |
Ok.
If you use WICD it is good, because it has its own log. So, please, reboot your comp, connect to wireless, and use it. When wireless disconnects, do not reboot, save 2 log files: /var/log/daemon.log and one for WICD in /var/log/wicd/wicd.log (copy them to somewhere, but keep the original). When reboot, and post them through http://pastebin.com. Thanks |
Johnnie.it
I have been pondering your intermittent wireless problem, and wondered if it has something to do with the rfkill module and your wireless card. The first thing I would do is see if rfkill is loaded: lsmod | grep rfkill if it is you might want to read the following bug report which emanated on intrepid and your wifi card: (not that I understand it completely!) https://bugs.launchpad.net/ubuntu/+s...er/+bug/269264 seems you are not alone. |
Hi guys, there's some news.
it happened again and, so i grabbed a copy of those two files. daemon.log --- http://pastebin.com/m3f3233a1 wicd.log --- http://pastebin.com/m55028928 disconnection must have happened just a little before 3:00 am. When I found out, I opened wicd, hit "refresh" a couple of times, and nothing. So I disconnected from that "ghost" wifi network and hit refresh again - nothing yet. Besides, I found out that wicd logs my password in PLAIN TEXT during handshakes!!! That's insane!!! And I can read the log file without having admin privileges!!! minrich: johnnie@johnnie-xps:~$ lsmod | grep rfkill johnnie@johnnie-xps:~$ I suppose everything's fine on that side...? |
Nice logs. Thanks.
Everything was good, look: 2009/11/07 17:26:27 :: bound to 192.168.1.99 -- renewal in 41657 seconds. 2009/11/07 17:26:27 :: DHCP connection successful 2009/11/07 17:26:27 :: Connecting thread exiting. 2009/11/07 17:26:27 :: IP Address is: 192.168.1.99 2009/11/07 17:26:31 :: Sending connection attempt result Success After 41657 seconds, dhcp start over: 2009/11/08 02:42:14 :: --------------------------- 2009/11/08 02:42:14 :: wicd initializing... 2009/11/08 02:42:14 :: --------------------------- ... and wicd was connected 2009/11/08 02:42:36 :: bound to 192.168.1.99 -- renewal in 32753 seconds. 2009/11/08 02:42:36 :: DHCP connection successful 2009/11/08 02:42:36 :: Connecting thread exiting. 2009/11/08 02:42:36 :: IP Address is: 192.168.1.99 2009/11/08 02:42:37 :: Sending connection attempt result Success. But after that something happened. First and most strange thing, that there is no any log for /var/log/daemon.log - nothing until Nov 18 12:45:37 Second, WICD start connects after 1 hour 2009/11/08 03:15:53 :: --------------------------- 2009/11/08 03:15:53 :: wicd initializing... 2009/11/08 03:15:53 :: --------------------------- And it successfully connected: 2009/11/08 03:16:16 :: bound to 192.168.1.99 -- renewal in 36964 seconds. 2009/11/08 03:16:16 :: DHCP connection successful 2009/11/08 03:16:16 :: Connecting thread exiting. 2009/11/08 03:16:16 :: IP Address is: 192.168.1.99 2009/11/08 03:16:20 :: Sending connection attempt result Success. But 30 minutes later, there is no networks 2009/11/08 03:47:27 :: scanning start 2009/11/08 03:47:27 :: ifconfig wlan0 up 2009/11/08 03:47:28 :: iwlist wlan0 scan 2009/11/08 03:47:28 :: scanning done 2009/11/08 03:47:28 :: found 0 networks: The question is what happened after 03:47, and why WICD start over? 2009/11/08 03:49:12 :: --------------------------- 2009/11/08 03:49:12 :: wicd initializing... 2009/11/08 03:49:12 :: --------------------------- 2009/11/08 03:49:12 :: wicd is version 1.6.1 426 ... 2009/11/08 03:49:35 :: Sending connection attempt result Success Yes, WICD keeps you password unencrypted, but you can disable log. |
Quote:
But I didn't do them myself, the merit goes all to linux :) Quote:
Quote:
That usually happens because of this very problem, less often for other reasons, like sometimes blueman or pulseaudio going crazy :) I almost never shut down... But shouldn't you be looking at most recent entries? Like: Code:
2009/11/19 03:06:09 :: scanning startAnyway, that's the problem. How can I further troubleshoot it? |
Just my 2 cents
but are you sure the problem is linux? If you have a router, do you see anything in the logs? |
Look your self:
Nov 17 02:43:51 localhost blueman-mechanism: Exiting Nov 18 12:45:37 localhost bluetoothd[1581]: link_key_request (sba=00:1F:3A:E0:B8:51, dba=00:1D:82:02:E1:F0) Nothing between Nov 17 02:43:51 and Nov 18 12:45:37. So you just reboot. OK Lets do next step. In preferences of the WICD there is option "Debug Log". Please enable it. But log will be very long, and we do not interesting to see all of it. So when next time your comp. lose connection, cat a part of the log since last successful connection (Sending connection attempt result Success.). And of course delete all passwords. I can explain why I an asking, because 2009/11/08 03:16:20 :: Sending connection attempt result Success 2009/11/08 03:47:27 :: found window_width in configuration 530 2009/11/08 03:47:27 :: found window_height in configuration 470 2009/11/08 03:47:27 :: scanning start 2009/11/08 03:47:27 :: ifconfig wlan0 up 2009/11/08 03:47:28 :: iwlist wlan0 scan 2009/11/08 03:47:28 :: scanning done 2009/11/08 03:47:28 :: found 0 networks 2009/11/13 20:01:52 :: Sending connection attempt result Success 2009/11/15 14:48:37 :: found window_width in configuration 530 2009/11/15 14:48:37 :: found window_height in configuration 470 2009/11/15 14:48:38 :: scanning start 2009/11/15 14:48:38 :: ifconfig wlan0 up 2009/11/15 14:48:38 :: iwlist wlan0 scan 2009/11/15 14:48:38 :: scanning done 2009/11/15 14:48:38 :: found 0 networks: 2009/11/15 14:55:14 :: Sending connection attempt result Success 2009/11/15 15:00:09 :: found window_width in configuration 530 2009/11/15 15:00:09 :: found window_height in configuration 470 2009/11/15 15:00:10 :: scanning start 2009/11/15 15:00:10 :: ifconfig wlan0 up 2009/11/15 15:00:10 :: iwlist wlan0 scan 2009/11/15 15:00:11 :: Forced disconnect on 2009/11/15 15:00:11 :: /sbin/dhclient -r wlan0 2009/11/15 15:00:11 :: ifconfig wlan0 0.0.0.0 2009/11/15 15:00:11 :: /sbin/ip route flush dev wlan0 2009/11/15 15:00:11 :: ifconfig wlan0 down 2009/11/15 15:00:11 :: ifconfig wlan0 up 2009/11/15 15:00:11 :: scanning done 2009/11/15 15:00:11 :: found 0 networks: No one knows what was between (for ex.): 2009/11/08 03:16:20 - 2009/11/08 03:47:27 2009/11/13 20:01:52 - 2009/11/15 14:48:37 2009/11/15 14:55:14 - 2009/11/15 15:00:09 |
Quote:
Correct me, if I am wrong. |
| All times are GMT -5. The time now is 05:21 PM. |