You are not logged in.

#1 2010-06-15 11:00:00

Lockheed
Member
Registered: 2010-03-16
Posts: 1,550

Can't connect to low-channel WIFi networks

The problem is this: laptop cannot connect to wireless networks running on low channels. The lower, the worse the connection.
At channel 1, I cannot even ping local routers. It starts at 400ms and after few retries reaches 50 000ms and then times out indefinitely.

On channel 11 everything works flawlessly.


Before you jump to obvious conclusions, let me exclude  some possibilities:

1. Hardware fault:
- everything works fine under Windows or live CD of Ubuntu 9.10 and 10.04 or RemoteExploit liveCD (I forgot the proper name)

2.Settings problem:
- it first occured on ubuntu 9.04 and after upgrading to 10.04 problem continues
- I just discovered it also happens on freshly installed Arch which has NO settings/home imported from old linux

3. Location, router, overloaded band
- it happens in various countries, various cities, various networks
- it happens even if all wifis are running on 11 and only one on channel 1

4. Drivers
- tried ath5x and madwifi

5. Kernel
- it keeps happening with every kernel since Oct 2009 with every. Before, I did not test it.
- it works on kernel supplied on livecds of Ubuntu 9.10 and 10.04
- it is happening at least since 2.6.31 to 2.6.34

6. Network Manager and WICD
- happens using either of them

So, give it your best shot. I have been trying to find an answer to it on various forums since October last year and yet came up with a solution.

Last edited by Lockheed (2010-06-15 12:23:08)

Offline

#2 2010-06-15 11:07:25

deej
Member
Registered: 2008-02-08
Posts: 395

Re: Can't connect to low-channel WIFi networks

Have you tried turning any powersaving options off ?

Deej

Offline

#3 2010-06-15 11:25:19

eldragon
Member
From: Buenos Aires
Registered: 2008-11-18
Posts: 1,029

Re: Can't connect to low-channel WIFi networks

its definately a bug on the drivers in recent kernels.

try building an older kernel (2.6.31) and see if it works.
if it does.. try 2.6.32, until you find two kernels, a working one and a faulty one.

grab git, and start bisecting till you find the faulty commit. report a bug.

this is a long process, but in the end, everyone benefits wink

Offline

#4 2010-06-15 11:41:35

Lockheed
Member
Registered: 2010-03-16
Posts: 1,550

Re: Can't connect to low-channel WIFi networks

Hey, thanks for writing. That reminded me to exclude kernel versions as well as WICD and NetworkManager.
Another reason to exclude kernel is that on two newest liveCD ubuntu releases, it works just fine.

Last edited by Lockheed (2010-06-15 11:47:54)

Offline

#5 2010-06-15 11:44:03

test1000
Member
Registered: 2005-04-03
Posts: 834

Re: Can't connect to low-channel WIFi networks

It can still be a hw fault that is simply expressed on newer kernels/newer userspace. I used to have a mouse that had a bad cord. On windows the connection would be tested more times and so i almost never had an issue with the mouse there. On linux the connection was only tested now and then(or just in the beggining) and so sometimes the mouse worked and sometimes not.

Perhaps strictly my case is a linux bug. Unless you want your mouse to not work NOW rather than crash completely later, with a harddisk that would probably be the case.

It could also be a problem expressed solely when certain settings are set, so i would try to change a parameter here and there and try different wifi sw. This happens regurarly with alsa for example. You have everything set up + the favorite "hack" to get your mic to work. Then upstream fixes a bug and your mic stops working. Now the fix YOU have to implement is to remove the "hack"...

Issues like these are common in a rolling release distro like Arch. Your issue seem quite specific though so it should be googable?


KISS = "It can scarcely be denied that the supreme goal of all theory is to make the irreducible basic elements as simple and as few as possible without having to surrender the adequate representation of a single datum of experience." - Albert Einstein

Offline

#6 2010-06-15 11:46:37

Lockheed
Member
Registered: 2010-03-16
Posts: 1,550

Re: Can't connect to low-channel WIFi networks

test1000 wrote:

It can still be a hw fault that is simply expressed on newer kernels/newer userspace. I used to have a mouse...

I was talking about Wireless Network, not mouse.
Besides, I don't have any sound system installed on Arch yet.
Besides, it works not only on windows, but live cds of Ubuntu.

Offline

#7 2010-06-15 12:00:51

kazuo
Member
From: São Paulo/Brazil
Registered: 2008-03-18
Posts: 413
Website

Re: Can't connect to low-channel WIFi networks

Lockheed wrote:
test1000 wrote:

It can still be a hw fault that is simply expressed on newer kernels/newer userspace. I used to have a mouse...

I was talking about Wireless Network, not mouse.
Besides, I don't have any sound system installed on Arch yet.
Besides, it works not only on windows, but live cds of Ubuntu.

Huhaha you are very dumb (we already know that from the topic title). You know what a 'example' is?

If works on ubuntu and not on Arch, can be a kernel fault, go and do a git bisect. Not kernel, another component go and do a regression test on the component.

Ubuntu use 2.6.32, Arch use 2.6.33.4, so when you discarded kernel you basically says that nothing happened between 2.6.32 and 2.6.33.4... you need to prove your point...

Offline

#8 2010-06-15 12:03:03

hokasch
Member
Registered: 2007-09-23
Posts: 1,461

Re: Can't connect to low-channel WIFi networks

As you experience the bug with an installed Ubuntu, but not from the live environment, you should imho concentrate on the possible differences - boot parameters, updates pulled in with the install etc.
Similarly, is the bug present from Arch Live CD?

P.S.: not sure if it makes any difference, but check the wireless country region code thing as well.
Second Edit: I hope you tested this the only reliable way before jumping conclusions, e.g. same router, once with low channel, once with high channel, once with the install and live cd for both settings.

Last edited by hokasch (2010-06-15 12:16:22)

Offline

#9 2010-06-15 12:18:47

.:B:.
Forum Fellow
Registered: 2006-11-26
Posts: 5,819
Website

Re: Can't connect to low-channel WIFi networks

While your title might be an eyecatcher, it's hardly informative and even derogatory.

I'd like to ask you to change it to something more descriptive smile.

Lockheed wrote:

Another reason to exclude kernel is that on two newest liveCD ubuntu releases, it works just fine.

Arch kernel != Ubuntu kernel. Simple as that. If you say yourself that most Arch kernels you tried up till now don't work, then how do you exclude the kernel? hmm

kazuo: we can do without the insults, keep it polite.


Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy

Offline

#10 2010-06-15 12:19:20

Lockheed
Member
Registered: 2010-03-16
Posts: 1,550

Re: Can't connect to low-channel WIFi networks

The only Arch cd that boots on my laptop is the one form May '10. Is it a live cd? Cause it looks more as an install cd.
I am not sure if there's a point in comparing live ubuntu with installed ubuntu since the problem occurs also in Arch booted with defaults.

kazuo, my reply to your first line is redundant since you already did such a good job in maligning your image.
In ubuntu, I am using 2.6.34 and nothing changed since 2.6.31.10 (not sure about before that).

Last edited by Lockheed (2010-06-15 12:21:12)

Offline

#11 2010-06-15 12:20:22

Lockheed
Member
Registered: 2010-03-16
Posts: 1,550

Re: Can't connect to low-channel WIFi networks

.:B:. wrote:

While your title might be an eyecatcher, it's hardly informative and even derogatory.

I'd like to ask you to change it to something more descriptive smile.

You are quite right. I picked that one because my previous topics rendered no replies for months.

Last edited by Lockheed (2010-06-15 12:21:28)

Offline

#12 2010-06-15 12:25:43

hokasch
Member
Registered: 2007-09-23
Posts: 1,461

Re: Can't connect to low-channel WIFi networks

I am not sure if there's a point in comparing live ubuntu with installed ubuntu since the problem occurs also in Arch booted with defaults.

It is your best shot - you have one case where it works, one where it doesn't, you like to find out why, find the differences - logcial, no?
AFAIK arch install images provide a live environment for a long time now. If you miss something, configure network (ethernet if you must) and install with pacman, but all the wirelesss tools needed should be included.

Offline

#13 2010-06-15 12:28:22

.:B:.
Forum Fellow
Registered: 2006-11-26
Posts: 5,819
Website

Re: Can't connect to low-channel WIFi networks

I know the feeling wink. You can always bump your topic 24h later to keep it in the lists, if that helps.

Thanks for adapting the title smile.


Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy

Offline

#14 2010-06-15 13:15:24

Lockheed
Member
Registered: 2010-03-16
Posts: 1,550

Re: Can't connect to low-channel WIFi networks

hokasch wrote:

It is your best shot - you have one case where it works, one where it doesn't, you like to find out why, find the differences - logcial, no?
AFAIK arch install images provide a live environment for a long time now. If you miss something, configure network (ethernet if you must) and install with pacman, but all the wirelesss tools needed should be included.

The problem is, this ubuntu has been so heavily customised, tracking back all the changes is virtually impossible. If anything, it would be more doable to compare livecd ubuntu with installed Arch.

As for Arch liveCD, tell me if my reasoning is wrong - bare Arch installed directly from the cd has the issue, ergo - the cd will have it as well. At least the latest one. As I said, I am unable to boot previous releases.

.:B:. wrote:

I know the feeling . You can always bump your topic 24h later to keep it in the lists, if that helps.

Yes, I was doing it for months, as well. Didn't help.

Last edited by Lockheed (2010-06-15 13:15:44)

Offline

#15 2010-06-15 13:51:47

hokasch
Member
Registered: 2007-09-23
Posts: 1,461

Re: Can't connect to low-channel WIFi networks

The problem is, this ubuntu has been so heavily customised, tracking back all the changes is virtually impossible. If anything, it would be more doable to compare livecd ubuntu with installed Arch.

I got the impression it works from the live cd, but not from a fresh ubuntu install - if you suspect the bug was introduced on Ubuntu through later tinkering/updating and would not be present on a fresh 10.04 install, this may indeed not be a good angle.
Still you can easily check for kernel boot parameters to rule out one more thing, or do a test install with 10.04 to see if that works compared to the heavily customised/updated 10.04 you got. If it does, chances are a package updated after the install broke it, and you can easily find out which one it is.

As for Arch liveCD, tell me if my reasoning is wrong - bare Arch installed directly from the cd has the issue, ergo - the cd will have it as well.

It should of course, yes.

Offline

#16 2010-06-15 13:59:49

Vamp898
Member
Registered: 2009-01-03
Posts: 1,032
Website

Re: Can't connect to low-channel WIFi networks

and dont forget to tail -f /var/log/${messages,everything}.log

Offline

#17 2010-06-16 14:52:52

Lockheed
Member
Registered: 2010-03-16
Posts: 1,550

Re: Can't connect to low-channel WIFi networks

Vamp898 wrote:

and dont forget to tail -f /var/log/${messages,everything}.log

I am getting

~$ tail -f /var/log/${messages,everything}.log
tail: cannot open `/var/log/.log' for reading: No such file or directory
tail: no files remaining

But if instead of this I use this: tail -f /var/log/*.log I am getting some results.

Offline

#18 2010-06-16 21:34:10

Lockheed
Member
Registered: 2010-03-16
Posts: 1,550

Re: Can't connect to low-channel WIFi networks

Here is logs taken few seconds after "connecting" to a low-channel wifi network:

$ tail -f /var/log/*.log
==> /var/log/AlsaUpgradeRev-1.0.21-4-121109-20.39.log <==
./drivers/opl3/snd-opl3-lib.ko
./drivers/opl3/snd-opl3-synth.ko
./drivers/pcsp/snd-pcsp.ko
./drivers/snd-virmidi.ko
./drivers/snd-mtpav.ko
./drivers/snd-aloop.ko
./drivers/vx/snd-vx-lib.ko
./drivers/snd-serial-u16550.ko
./drivers/snd-dummy.ko
chmod: cannot access `/dev/midi': No such file or directory

==> /var/log/AlsaUpgradeRev-1.0.21-4-121109-21.50.log <==
./drivers/opl3/snd-opl3-lib.ko
./drivers/opl3/snd-opl3-synth.ko
./drivers/pcsp/snd-pcsp.ko
./drivers/snd-virmidi.ko
./drivers/snd-mtpav.ko
./drivers/snd-aloop.ko
./drivers/vx/snd-vx-lib.ko
./drivers/snd-serial-u16550.ko
./drivers/snd-dummy.ko
chmod: cannot access `/dev/midi': No such file or directory

==> /var/log/AlsaUpgradeRev-1.17-060109-23.04.log <==

-------------------------------------------------------------
-  Installation successfully finished!
-------------------------------------------------------------


-------------------------------------------------------------
-  Your new ALSA version will be loaded after the next reboot...
-------------------------------------------------------------


==> /var/log/auth.log <==
Jun 16 21:24:04 Beyond2000 sudo:     juha : TTY=pts/0 ; PWD=/home/juha ; USER=root ; COMMAND=/usr/bin/apt-get install opera*
Jun 16 21:25:58 Beyond2000 sudo:     juha : TTY=unknown ; PWD=/home/juha ; USER=root ; COMMAND=/usr/sbin/synaptic
Jun 16 21:27:21 Beyond2000 sudo:     juha : TTY=pts/0 ; PWD=/home/juha ; USER=root ; COMMAND=/usr/bin/apt-key add -
Jun 16 21:27:24 Beyond2000 sudo:     juha : TTY=pts/0 ; PWD=/home/juha ; USER=root ; COMMAND=/usr/bin/apt-get install debian-archive-keyring
Jun 16 21:27:39 Beyond2000 sudo:     juha : TTY=pts/0 ; PWD=/home/juha ; USER=root ; COMMAND=/usr/bin/apt-get install debian-archive-keyring
Jun 16 21:28:58 Beyond2000 sudo:     juha : TTY=pts/0 ; PWD=/home/juha ; USER=root ; COMMAND=/usr/bin/apt-get update
Jun 16 21:29:08 Beyond2000 sudo:     juha : TTY=pts/0 ; PWD=/home/juha ; USER=root ; COMMAND=/usr/bin/apt-get install opera
Jun 16 22:15:01 Beyond2000 CRON[24643]: pam_unix(cron:session): session opened for user juha by (uid=0)
Jun 16 22:17:02 Beyond2000 CRON[25074]: pam_unix(cron:session): session opened for user root by (uid=0)
Jun 16 22:17:02 Beyond2000 CRON[25074]: pam_unix(cron:session): session closed for user root

==> /var/log/boot.log <==
Error connecting to ftp: Couldn't resolve host 'gavbiz.co.uk'
mountall: mount /media/d/wwws/gavbiz_online [3221] terminated with status 1
Invalidating stale software suspend images... done.
 * Setting sensors limits                                                [ OK ] 
 * Starting system log daemon...                                                acpid: starting up with proc fs

init: apport pre-start process (3314) terminated with status 1
init: apport post-stop process (3345) terminated with status 1
                                                                         [ OK ]
 * Starting kernel log daemon...                                         [ OK ] 

==> /var/log/bootstrap.log <==
Setting up libio-string-perl (1.08-2) ...
Setting up libclass-accessor-perl (0.31-2) ...
Setting up libtimedate-perl (1.1600-9) ...
Setting up tasksel (2.73ubuntu18) ...

Setting up libparse-debianchangelog-perl (1.1.1-2ubuntu1) ...
Setting up ubuntu-minimal (1.140) ...
Processing triggers for libc6 ...
ldconfig deferred processing now taking place
Processing triggers for initramfs-tools ...

==> /var/log/checkbox.log <==

==> /var/log/daemon.log <==
Jun 16 21:07:45 Beyond2000 cpupowerd[32291]: WARNING: This program could cause damage to your Hardware! 
Jun 16 21:07:46 Beyond2000 cpupowerd[32292]: CPU frequency should be 1600 MHz, but is 800 MHz. Frequency changing failed! 
Jun 16 21:07:46 Beyond2000 cpupowerd[32292]: Change cpu step failed! 
Jun 16 21:28:59 Beyond2000 ntpd[3829]: synchronized to 130.149.17.21, stratum 1
Jun 16 21:28:59 Beyond2000 ntpd[3829]: kernel time sync status change 6001
Jun 16 21:31:00 Beyond2000 ntpd[3829]: synchronized to 130.88.202.49, stratum 2
Jun 16 21:31:00 Beyond2000 ntpd[3829]: kernel time sync status change 2001
Jun 16 21:47:28 Beyond2000 ntpd[3829]: synchronized to 130.149.17.21, stratum 1
Jun 16 22:09:01 Beyond2000 ntpd[3829]: synchronized to 193.62.22.98, stratum 1
Jun 16 22:28:39 Beyond2000 ntpd[3829]: sendto(213.222.193.35) (fd=18): Invalid argument

==> /var/log/dpkg.log <==
2010-06-16 21:30:13 status unpacked opera 10.10.4742.gcc4.qt3
2010-06-16 21:30:13 status half-configured opera 10.10.4742.gcc4.qt3
2010-06-16 21:30:22 update-alternatives: run with --install /usr/bin/x-www-browser x-www-browser /usr/bin/opera 90 --slave /usr/share/man/man1/x-www-browser.1.gz x-www-browser.1.gz /usr/share/man/man1/opera.1.gz
2010-06-16 21:30:22 update-alternatives: link group x-www-browser updated to point to /usr/bin/opera
2010-06-16 21:30:24 status installed opera 10.10.4742.gcc4.qt3
2010-06-16 21:30:24 status triggers-pending menu 2.1.43ubuntu1
2010-06-16 21:30:24 status triggers-awaited menu 2.1.43ubuntu1
2010-06-16 21:30:24 trigproc menu 2.1.43ubuntu1 2.1.43ubuntu1
2010-06-16 21:30:24 status half-configured menu 2.1.43ubuntu1
2010-06-16 21:30:26 status installed menu 2.1.43ubuntu1

==> /var/log/fontconfig.log <==
/usr/share/fonts/truetype/ttf-symbol-replacement/symbol-replacement.ttf: skipping, existing cache is valid: 1 fonts, 0 dirs
/usr/share/fonts/truetype/unfonts: skipping, existing cache is valid: 4 fonts, 0 dirs
/usr/share/fonts/truetype/unifont: skipping, existing cache is valid: 1 fonts, 0 dirs
/usr/share/fonts/type1: skipping, existing cache is valid: 0 fonts, 1 dirs
/usr/share/fonts/type1/gsfonts: skipping, existing cache is valid: 35 fonts, 0 dirs
/usr/X11R6/lib/X11/fonts: skipping, no such directory
/usr/local/share/fonts: skipping, existing cache is valid: 0 fonts, 0 dirs
/usr/share/texmf/fonts/type1/public/lm: skipping, existing cache is valid: 92 fonts, 0 dirs
/var/cache/fontconfig: cleaning cache directory
fc-cache: succeeded
tail: cannot open `/var/log/hibernate.log' for reading: Permission denied

==> /var/log/jockey.log <==

==> /var/log/kern.log <==
Jun 16 22:28:18 Beyond2000 kernel: wlan0: deauthenticated from 00:12:17:4a:10:ae (Reason: 7)
Jun 16 22:28:19 Beyond2000 kernel: eth0: no link during initialization.
Jun 16 22:28:34 Beyond2000 kernel: eth0: no link during initialization.
Jun 16 22:28:37 Beyond2000 kernel: wlan0: direct probe to AP 00:12:17:4a:10:ae (try 1)
Jun 16 22:28:38 Beyond2000 kernel: wlan0: direct probe responded
Jun 16 22:28:38 Beyond2000 kernel: wlan0: authenticate with AP 00:12:17:4a:10:ae (try 1)
Jun 16 22:28:38 Beyond2000 kernel: wlan0: authenticated
Jun 16 22:28:38 Beyond2000 kernel: wlan0: associate with AP 00:12:17:4a:10:ae (try 1)
Jun 16 22:28:38 Beyond2000 kernel: wlan0: RX AssocResp from 00:12:17:4a:10:ae (capab=0x431 status=0 aid=3)
Jun 16 22:28:38 Beyond2000 kernel: wlan0: associated

==> /var/log/lpr.log <==

==> /var/log/mail.log <==

==> /var/log/MountManager.log <==

==> /var/log/nvidia-installer.log <==
-> Running runtime sanity check:
-> done.
-> Runtime sanity check passed.
-> Would you like to run the nvidia-xconfig utility to automatically update you
   r X configuration file so that the NVIDIA X driver will be used when you res
   tart X?  Any pre-existing X configuration file will be backed up. (Answer: Y
   es)
-> Your X configuration file has been successfully updated.  Installation of
   the NVIDIA Accelerated Graphics Driver for Linux-x86_64 (version: 195.36.24)
   is now complete.

==> /var/log/pacman.log <==
[2010-05-07 22:00] synchronizing package lists

==> /var/log/pm-powersave.log <==
sudo: /etc/init.d/preload: command not found

ERROR: The control display is undefined; please run `nvidia-settings
       --help` for usage information.


ERROR: The control display is undefined; please run `nvidia-settings
       --help` for usage information.

Returned exit code 1.

==> /var/log/pm-suspend.log <==
/usr/lib/pm-utils/sleep.d/91wicd resume suspend:success.
/usr/lib/pm-utils/sleep.d/90clock resume suspend:not applicable.
/usr/lib/pm-utils/sleep.d/75modules resume suspend:success.
/usr/lib/pm-utils/sleep.d/55NetworkManager resume suspend:not applicable.
/usr/lib/pm-utils/sleep.d/49bluetooth resume suspend:not applicable.
/etc/pm/sleep.d/10_unattended-upgrades-hibernate resume suspend:success.
/etc/pm/sleep.d/10_grub-common resume suspend:success.
/usr/lib/pm-utils/sleep.d/00powersave resume suspend:success.
/usr/lib/pm-utils/sleep.d/00logging resume suspend:success.
/usr/lib/pm-utils/sleep.d/000kernel-change resume suspend:success.

==> /var/log/pycentral.log <==
2010-05-27 13:52:21 2 pycentral cleanup-pkgprepare-updates: found 3 dangling symlinks
2010-05-27 13:52:21 2 pycentral cleanup-pkgprepare-updates: checking for links owned by packages (this may take some time)
2010-05-27 13:52:30 2 pycentral cleanup-pkgprepare-updates: removed %d dangling symlinks not owned by any package
2010-05-27 14:20:10 3 pycentral pkginstall: error byte-compiling files (1)
2010-05-27 14:26:27 3 pycentral pkginstall: error byte-compiling files (1)
2010-05-27 14:29:13 3 pycentral pkginstall: error byte-compiling files (1)
2010-05-27 14:34:08 3 pycentral pkginstall: error byte-compiling files (1)

==> /var/log/soundon.log <==
crw-rw-rw- 1 root root 251,  2 Jun 16 17:47 /dev/mixer
lrwxrwxrwx 1 root root      26 Jun 16 17:47 /dev/mixer0 -> /dev/oss/oss_hdaudio0/mix0
crw-rw-rw- 1 root root 250,  3 Jun 16 17:47 /dev/oss/oss_hdaudio0/mix0
crw-rw-rw- 1 root root 250,  4 Jun 16 17:47 /dev/oss/oss_hdaudio0/pcm0
crw-rw-rw- 1 root root 250,  6 Jun 16 17:47 /dev/oss/oss_hdaudio0/pcm1
crw-rw-rw- 1 root root 250, 10 Jun 16 17:47 /dev/oss/oss_hdaudio0/pcmin0
crw-rw-rw- 1 root root 250, 12 Jun 16 17:47 /dev/oss/oss_hdaudio0/pcmin1
crw-rw-rw- 1 root root 250,  8 Jun 16 17:47 /dev/oss/oss_hdaudio0/spdout0

Loading mixer settings from /usr/lib/oss/etc/mixer.save

==> /var/log/user.log <==

==> /var/log/vbox-install.log <==
vboxnetadp.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/2.6.33.5-colombo/updates/dkms/

depmod....

DKMS: install Completed.

==> /var/log/wpa_supplicant.log <==

==> /var/log/Xorg.0.log <==
(**) Logitech USB RECEIVER: Device: "/dev/input/event8"
(II) Logitech USB RECEIVER: Found 20 mouse buttons
(II) Logitech USB RECEIVER: Found scroll wheel(s)
(II) Logitech USB RECEIVER: Found relative axes
(II) Logitech USB RECEIVER: Found x and y relative axes
(II) Logitech USB RECEIVER: Configuring as mouse
(**) Logitech USB RECEIVER: YAxisMapping: buttons 4 and 5
(**) Logitech USB RECEIVER: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Logitech USB RECEIVER" (type: MOUSE)
(II) Logitech USB RECEIVER: initialized for relative axes.

==> /var/log/Xorg.1.log <==

Fatal server error:
no screens found

Please consult the The X.Org Foundation support 
     at http://wiki.x.org
 for help. 
Please also check the log file at "/var/log/Xorg.1.log" for additional information.

 ddxSigGiveUp: Closing log

==> /var/log/Xorg.2.log <==

Fatal server error:
no screens found

Please consult the The X.Org Foundation support 
     at http://wiki.x.org
 for help. 
Please also check the log file at "/var/log/Xorg.2.log" for additional information.

 ddxSigGiveUp: Closing log

==> /var/log/Xorg.3.log <==

Fatal server error:
no screens found

Please consult the The X.Org Foundation support 
     at http://wiki.x.org
 for help. 
Please also check the log file at "/var/log/Xorg.3.log" for additional information.

 ddxSigGiveUp: Closing log

==> /var/log/Xorg.4.log <==

Fatal server error:
no screens found

Please consult the The X.Org Foundation support 
     at http://wiki.x.org
 for help. 
Please also check the log file at "/var/log/Xorg.4.log" for additional information.

 ddxSigGiveUp: Closing log

==> /var/log/Xorg.5.log <==

Fatal server error:
no screens found

Please consult the The X.Org Foundation support 
     at http://wiki.x.org
 for help. 
Please also check the log file at "/var/log/Xorg.5.log" for additional information.

 ddxSigGiveUp: Closing log

==> /var/log/Xorg.99.log <==

==> /var/log/Xorg.failsafe.log <==
(II) UnloadModule: "evdev"
(II) Sleep Button: Close
(II) UnloadModule: "evdev"
(II) Power Button: Close
(II) UnloadModule: "evdev"
(II) Video Bus: Close
(II) UnloadModule: "evdev"
(II) Power Button: Close
(II) UnloadModule: "evdev"
 ddxSigGiveUp: Closing log

And pings from this period:

$ ping 192.168.7.1
PING 192.168.7.1 (192.168.7.1) 56(84) bytes of data.
64 bytes from 192.168.7.1: icmp_seq=1 ttl=64 time=19771 ms
64 bytes from 192.168.7.1: icmp_seq=2 ttl=64 time=18858 ms
64 bytes from 192.168.7.1: icmp_seq=3 ttl=64 time=18246 ms
64 bytes from 192.168.7.1: icmp_seq=4 ttl=64 time=17504 ms
64 bytes from 192.168.7.1: icmp_seq=5 ttl=64 time=16551 ms
64 bytes from 192.168.7.1: icmp_seq=6 ttl=64 time=15644 ms
64 bytes from 192.168.7.1: icmp_seq=7 ttl=64 time=14686 ms
64 bytes from 192.168.7.1: icmp_seq=8 ttl=64 time=13711 ms
64 bytes from 192.168.7.1: icmp_seq=9 ttl=64 time=12738 ms
64 bytes from 192.168.7.1: icmp_seq=10 ttl=64 time=11752 ms
64 bytes from 192.168.7.1: icmp_seq=11 ttl=64 time=5711 ms
64 bytes from 192.168.7.1: icmp_seq=12 ttl=64 time=5449 ms
64 bytes from 192.168.7.1: icmp_seq=13 ttl=64 time=5149 ms
64 bytes from 192.168.7.1: icmp_seq=14 ttl=64 time=4819 ms
64 bytes from 192.168.7.1: icmp_seq=15 ttl=64 time=4512 ms
64 bytes from 192.168.7.1: icmp_seq=16 ttl=64 time=5000 ms
64 bytes from 192.168.7.1: icmp_seq=17 ttl=64 time=4755 ms
64 bytes from 192.168.7.1: icmp_seq=18 ttl=64 time=4454 ms
64 bytes from 192.168.7.1: icmp_seq=19 ttl=64 time=4318 ms
64 bytes from 192.168.7.1: icmp_seq=20 ttl=64 time=4071 ms
64 bytes from 192.168.7.1: icmp_seq=21 ttl=64 time=4123 ms
64 bytes from 192.168.7.1: icmp_seq=22 ttl=64 time=4081 ms
64 bytes from 192.168.7.1: icmp_seq=23 ttl=64 time=3344 ms
64 bytes from 192.168.7.1: icmp_seq=24 ttl=64 time=2759 ms
64 bytes from 192.168.7.1: icmp_seq=25 ttl=64 time=2488 ms
64 bytes from 192.168.7.1: icmp_seq=26 ttl=64 time=2042 ms
64 bytes from 192.168.7.1: icmp_seq=27 ttl=64 time=1381 ms
64 bytes from 192.168.7.1: icmp_seq=28 ttl=64 time=1773 ms
64 bytes from 192.168.7.1: icmp_seq=29 ttl=64 time=1651 ms
64 bytes from 192.168.7.1: icmp_seq=30 ttl=64 time=1772 ms
64 bytes from 192.168.7.1: icmp_seq=31 ttl=64 time=1520 ms
64 bytes from 192.168.7.1: icmp_seq=32 ttl=64 time=759 ms
64 bytes from 192.168.7.1: icmp_seq=33 ttl=64 time=42.4 ms
64 bytes from 192.168.7.1: icmp_seq=34 ttl=64 time=71.3 ms
64 bytes from 192.168.7.1: icmp_seq=35 ttl=64 time=397 ms
64 bytes from 192.168.7.1: icmp_seq=36 ttl=64 time=6.13 ms
64 bytes from 192.168.7.1: icmp_seq=37 ttl=64 time=1.47 ms
64 bytes from 192.168.7.1: icmp_seq=38 ttl=64 time=571 ms
64 bytes from 192.168.7.1: icmp_seq=39 ttl=64 time=250 ms
64 bytes from 192.168.7.1: icmp_seq=40 ttl=64 time=97.9 ms
64 bytes from 192.168.7.1: icmp_seq=41 ttl=64 time=17.3 ms
64 bytes from 192.168.7.1: icmp_seq=42 ttl=64 time=8.66 ms
64 bytes from 192.168.7.1: icmp_seq=43 ttl=64 time=794 ms
64 bytes from 192.168.7.1: icmp_seq=44 ttl=64 time=630 ms
64 bytes from 192.168.7.1: icmp_seq=45 ttl=64 time=590 ms
64 bytes from 192.168.7.1: icmp_seq=46 ttl=64 time=337 ms
64 bytes from 192.168.7.1: icmp_seq=47 ttl=64 time=1.68 ms
64 bytes from 192.168.7.1: icmp_seq=48 ttl=64 time=179 ms
64 bytes from 192.168.7.1: icmp_seq=49 ttl=64 time=456 ms
64 bytes from 192.168.7.1: icmp_seq=50 ttl=64 time=13.7 ms
64 bytes from 192.168.7.1: icmp_seq=51 ttl=64 time=78.8 ms
64 bytes from 192.168.7.1: icmp_seq=52 ttl=64 time=1031 ms
64 bytes from 192.168.7.1: icmp_seq=53 ttl=64 time=652 ms
64 bytes from 192.168.7.1: icmp_seq=54 ttl=64 time=1020 ms
64 bytes from 192.168.7.1: icmp_seq=55 ttl=64 time=1352 ms
64 bytes from 192.168.7.1: icmp_seq=56 ttl=64 time=3012 ms
64 bytes from 192.168.7.1: icmp_seq=57 ttl=64 time=3448 ms
64 bytes from 192.168.7.1: icmp_seq=58 ttl=64 time=3881 ms
64 bytes from 192.168.7.1: icmp_seq=59 ttl=64 time=3139 ms
64 bytes from 192.168.7.1: icmp_seq=60 ttl=64 time=2364 ms
64 bytes from 192.168.7.1: icmp_seq=61 ttl=64 time=1733 ms
64 bytes from 192.168.7.1: icmp_seq=62 ttl=64 time=1670 ms

It is remarkable it actually kept pinging. Every other time it just timed out after several retries and I wasn't even able to access router's config page.

Here is pings after going back to channel 11:

64 bytes from 192.168.7.1: icmp_seq=84 ttl=64 time=2.02 ms
64 bytes from 192.168.7.1: icmp_seq=85 ttl=64 time=5.14 ms
64 bytes from 192.168.7.1: icmp_seq=86 ttl=64 time=3.24 ms
64 bytes from 192.168.7.1: icmp_seq=87 ttl=64 time=2.02 ms
64 bytes from 192.168.7.1: icmp_seq=88 ttl=64 time=1.41 ms
64 bytes from 192.168.7.1: icmp_seq=89 ttl=64 time=9.08 ms
64 bytes from 192.168.7.1: icmp_seq=90 ttl=64 time=58.4 ms
64 bytes from 192.168.7.1: icmp_seq=91 ttl=64 time=14.1 ms
64 bytes from 192.168.7.1: icmp_seq=92 ttl=64 time=1.23 ms
64 bytes from 192.168.7.1: icmp_seq=93 ttl=64 time=28.8 ms
64 bytes from 192.168.7.1: icmp_seq=94 ttl=64 time=1.40 ms

Offline

Board footer

Powered by FluxBB