SliTaz Forum

wlan garbage in console

(4 posts) (2 voices)

• Started 11 years ago by Aleksej
• Latest reply from Aleksej
• This topic is not a support question

Tags:

No tags yet.

1. 

   Aleksej
   

   offline

   Coder-hobbyist

   When I switch to pure console (Ctrl+Alt+F1) and log in, I see a repeated "garbage" messages:
   

   cfg80211: Calling CRDA to update world regulatory domain
   cfg80211: Calling CRDA for country: GB

   I see these messages very frequently, maybe once a minute or so. Its very annoying. Messages are writed just in cursor position, over other display stuff.
   When I use Midnight Commander, I can press Ctrl+O twice to redraw screen. But when I'm in lynx or nano, I can't find workaround.

   What I want? Not to see these messages in console. Please, help!

   Additional info.
   dmesg:
   

   . . . . . . . .
   r8169 0000:02:00.0: eth0: link down
   wlan0: authenticate with 54:04:a6:8b:f7:f8 (try 1)
   wlan0: authenticated
   wlan0: associate with 54:04:a6:8b:f7:f8 (try 1)
   wlan0: RX AssocResp from 54:04:a6:8b:f7:f8 (capab=0x411 status=0 aid=2)
   wlan0: associated
   cfg80211: Calling CRDA for country: GB
   padlock: VIA PadLock not detected.
   wlan0: deauthenticated from 54:04:a6:8b:f7:f8 (Reason: 3)
   cfg80211: Calling CRDA to update world regulatory domain
   wlan0: authenticate with 54:04:a6:8b:f7:f8 (try 1)
   wlan0: authenticated
   wlan0: associate with 54:04:a6:8b:f7:f8 (try 1)
   wlan0: RX AssocResp from 54:04:a6:8b:f7:f8 (capab=0x411 status=0 aid=2)
   wlan0: associated
   cfg80211: Calling CRDA for country: GB
   wlan0: deauthenticated from 54:04:a6:8b:f7:f8 (Reason: 3)
   cfg80211: Calling CRDA to update world regulatory domain
   wlan0: authenticate with 54:04:a6:8b:f7:f8 (try 1)
   wlan0: authenticated
   wlan0: associate with 54:04:a6:8b:f7:f8 (try 1)
   wlan0: RX AssocResp from 54:04:a6:8b:f7:f8 (capab=0x411 status=0 aid=2)
   wlan0: associated
   cfg80211: Calling CRDA for country: GB
   . . . . . . . .

   At the same time (I think) when these annoying messages are writed, I can see blinked Network Monitor Applet in LXPanel (beginning with red cross (disconnected?), then two blinks (handshake?), then waiting).

   I live in Ukraine (country code UA). I use wireless router RT-N10 together with my neighbor, he is owner and admin of it.
   Hardinfo says about my wireless thing:

   

   Posted 11 years ago #
2. 

   Aleksej
   

   offline

   Coder-hobbyist

   OK, here is framebuffer screenshot of this nuisance:

   

   Posted 11 years ago #
3. 

   mojo
   

   offline

   Key Master

   This is used to stop kernel messages from bleeding thru boot messages on /etc/init.d/rcS

   # Be quiet
   echo "0 0 0 0" > /proc/sys/kernel/printk

   Posted 11 years ago #
4. 

   Aleksej
   

   offline

   Coder-hobbyist

   Thanks, mojo!

   Now I can't use that Wi-Fi spot for a days. Now I use an Android phone (with GPRS/EDGE connection) as Wi-Fi spot. And its works great (but slow, hehe). Here are latest lines of dmesg, you can see as I disconnected regular spot and connected to Android's:
   

   Adding 1050620k swap on /dev/sda5.  Priority:-1 extents:1 across:1050620k
   r8169 0000:02:00.0: eth0: link down
   wlan0: authenticate with 54:04:a6:8b:f7:f8 (try 1)
   wlan0: authenticated
   wlan0: associate with 54:04:a6:8b:f7:f8 (try 1)
   wlan0: RX AssocResp from 54:04:a6:8b:f7:f8 (capab=0x411 status=0 aid=1)
   wlan0: associated
   cfg80211: Calling CRDA for country: GB
   padlock: VIA PadLock not detected.
   wlan0: deauthenticating from 54:04:a6:8b:f7:f8 by local choice (reason=3)
   cfg80211: Calling CRDA to update world regulatory domain
   r8169 0000:02:00.0: eth0: link down
   wlan0: authenticate with 08:fc:88:c5:df:90 (try 1)
   wlan0: authenticated
   wlan0: associate with 08:fc:88:c5:df:90 (try 1)
   wlan0: RX AssocResp from 08:fc:88:c5:df:90 (capab=0x411 status=0 aid=1)
   wlan0: associated
   cfg80211: Calling CRDA for country: US

   No loops. Maybe, my neighbour, owner of Wi-Fi router, is not a good admin :)
   Or, maybe router incoming cable fixed not well. As he say, here is Modem on the next building, then air cable, then his router. And because of renovation of the nearby building's roof, here is permanent problems with air cable for a days (or weeks), so long.

   Posted 11 years ago #

RSS feed for this topic

Reply

You must log in to post.