LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices



Reply
 
Search this Thread
Old 10-14-2010, 05:24 AM   #1
serafimg
Member
 
Registered: Jan 2006
Distribution: Ubuntu 10.10 64-bit
Posts: 60

Rep: Reputation: 15
Exclamation Wired and wireless problems with Fujitsu Siemens Amilo PA 2510 using Ubuntu Linux


Hallo to everybody!
I will share my problem with you...

My laptop is Fujitsu Siemens Amilo PA 2510. I have successfully upgraded to Ubuntu Linux 10.10 64 bit. The general impression is good but I have severe problems with my Internet connections.

My chipset must be atheros ath5k.

When I try to connect wired: I can successfully connect in my home wired connection but the connection is extremely slow. Most of the times I can not even browse to websites, although without loosing the connection.

When I try to connect wireless: Here we have 3 cases:
1. It cannot recognise that I have the wireless activated. As a result, I cannot find any network to connect.
2. It can recognise that the wireless is activated and find possible networks although it cannot connect.
3. It can recognise that the wireless is activated, find possible networks and connect successfully. However, during the time, in can be in 5 minutes or in 2 and 5 hours!, it disconnects and we go back to the previous 2 cases.

It worths to mention that if I do not activate wireless from scratch, before Ubuntu Linux boots the first case is inevitable.

I opened the Log File Viewer and clicked on the syslog section to view the log files in order recognise the problem. Being unexperienced, I couldn't understand the issue. My syslogs are:


When I am connected wired:

ep 27 15:02:19 Serafeim-Linux kernel: [ 8442.620262] [UFW BLOCK] IN=eth0 OUT= MAC=00:03:0d:6d:e0:5d:00:1a:2a:8a:1d:c6:08:00 SRC=94.159.154.242 DST=192.168.2.5 LEN=95 TOS=0x00 PREC=0x00 TTL=114 ID=3455 PROTO=UDP SPT=52461 DPT=6881 LEN=75
Sep 27 15:02:19 Serafeim-Linux kernel: [ 8442.630101] [UFW BLOCK] IN=eth0 OUT= MAC=00:03:0d:6d:e0:5d:00:1a:2a:8a:1d:c6:08:00 SRC=94.159.154.242 DST=192.168.2.5 LEN=58 TOS=0x00 PREC=0x00 TTL=114 ID=3463 PROTO=UDP SPT=52461 DPT=6881 LEN=38
Sep 27 15:02:19 Serafeim-Linux kernel: [ 8442.987652] [UFW BLOCK] IN=eth0 OUT= MAC=00:03:0d:6d:e0:5d:00:1a:2a:8a:1d:c6:08:00 SRC=86.51.125.218 DST=192.168.2.5 LEN=131 TOS=0x00 PREC=0x00 TTL=111 ID=22367 PROTO=UDP SPT=56371 DPT=6881 LEN=111
Sep 27 15:02:24 Serafeim-Linux kernel: [ 8447.342290] [UFW BLOCK] IN=eth0 OUT= MAC=00:03:0d:6d:e0:5d:00:1a:2a:8a:1d:c6:08:00 SRC=94.159.154.242 DST=192.168.2.5 LEN=58 TOS=0x00 PREC=0x00 TTL=114 ID=3911 PROTO=UDP SPT=52461 DPT=6881 LEN=38
Sep 27 15:02:30 Serafeim-Linux kernel: [ 8453.762092] [UFW BLOCK] IN=eth0 OUT= MAC=00:03:0d:6d:e0:5d:00:1a:2a:8a:1d:c6:08:00 SRC=94.159.154.242 DST=192.168.2.5 LEN=58 TOS=0x00 PREC=0x00 TTL=114 ID=4594 PROTO=UDP SPT=52461 DPT=6881 LEN=38
Sep 27 15:02:33 Serafeim-Linux kernel: [ 8456.490203] [UFW BLOCK] IN=eth0 OUT= MAC=00:03:0d:6d:e0:5d:00:1a:2a:8a:1d:c6:08:00 SRC=82.234.11.58 DST=192.168.2.5 LEN=131 TOS=0x00 PREC=0x00 TTL=113 ID=27046 PROTO=UDP SPT=50898 DPT=6881 LEN=111
Sep 27 15:02:48 Serafeim-Linux kernel: [ 8471.377699] [UFW BLOCK] IN=eth0 OUT= MAC=00:03:0d:6d:e0:5d:00:1a:2a:8a:1d:c6:08:00 SRC=88.203.68.116 DST=192.168.2.5 LEN=95 TOS=0x00 PREC=0x00 TTL=115 ID=27287 PROTO=UDP SPT=53010 DPT=6881 LEN=75
Sep 27 15:02:48 Serafeim-Linux kernel: [ 8471.395083] [UFW BLOCK] IN=eth0 OUT= MAC=00:03:0d:6d:e0:5d:00:1a:2a:8a:1d:c6:08:00 SRC=88.203.68.116 DST=192.168.2.5 LEN=58 TOS=0x00 PREC=0x00 TTL=115 ID=27291 PROTO=UDP SPT=53010 DPT=6881 LEN=38
Sep 27 15:02:51 Serafeim-Linux kernel: [ 8474.806261] [UFW BLOCK] IN=eth0 OUT= MAC=00:03:0d:6d:e0:5d:00:1a:2a:8a:1d:c6:08:00 SRC=88.203.68.116 DST=192.168.2.5 LEN=58 TOS=0x00 PREC=0x00 TTL=115 ID=27410 PROTO=UDP SPT=53010 DPT=6881 LEN=38
Sep 27 15:02:58 Serafeim-Linux kernel: [ 8481.527071] [UFW BLOCK] IN=eth0 OUT= MAC=00:03:0d:6d:e0:5d:00:1a:2a:8a:1d:c6:08:00 SRC=109.76.107.45 DST=192.168.2.5 LEN=131 TOS=0x00 PREC=0x00 TTL=115 ID=19735 PROTO=UDP SPT=59553 DPT=6881 LEN=111
Sep 27 15:03:27 Serafeim-Linux kernel: [ 8510.471730] [UFW BLOCK] IN=eth0 OUT= MAC=00:03:0d:6d:e0:5d:00:1a:2a:8a:1d:c6:08:00 SRC=78.149.57.239 DST=192.168.2.5 LEN=131 TOS=0x00 PREC=0x00 TTL=113 ID=5876 PROTO=UDP SPT=27704 DPT=6881 LEN=111
Sep 27 15:03:27 Serafeim-Linux kernel: [ 8510.657447] __ratelimit: 4 callbacks suppressed
Sep 27 15:03:27 Serafeim-Linux kernel: [ 8510.657455] ath5k phy0: gain calibration timeout (2412MHz)
Sep 27 15:03:27 Serafeim-Linux kernel: [ 8511.048003] ath5k phy0: gain calibration timeout (2417MHz)
Sep 27 15:03:28 Serafeim-Linux kernel: [ 8511.434703] ath5k phy0: gain calibration timeout (2422MHz)
Sep 27 15:03:28 Serafeim-Linux kernel: [ 8511.830906] ath5k phy0: gain calibration timeout (2427MHz)
Sep 27 15:03:29 Serafeim-Linux kernel: [ 8512.227138] ath5k phy0: gain calibration timeout (2432MHz)
Sep 27 15:03:29 Serafeim-Linux kernel: [ 8512.616482] ath5k phy0: gain calibration timeout (2437MHz)
Sep 27 15:03:29 Serafeim-Linux kernel: [ 8513.005867] ath5k phy0: gain calibration timeout (2442MHz)
Sep 27 15:03:30 Serafeim-Linux kernel: [ 8513.334324] [UFW BLOCK] IN=eth0 OUT= MAC=00:03:0d:6d:e0:5d:00:1a:2a:8a:1d:c6:08:00 SRC=41.235.70.115 DST=192.168.2.5 LEN=303 TOS=0x00 PREC=0x00 TTL=114 ID=12921 PROTO=UDP SPT=52140 DPT=6881 LEN=283
Sep 27 15:03:30 Serafeim-Linux kernel: [ 8513.394297] ath5k phy0: gain calibration timeout (2447MHz)
Sep 27 15:03:30 Serafeim-Linux kernel: [ 8513.784017] ath5k phy0: gain calibration timeout (2452MHz)
Sep 27 15:03:30 Serafeim-Linux kernel: [ 8514.175883] ath5k phy0: gain calibration timeout (2457MHz)
Sep 27 15:03:42 Serafeim-Linux kernel: [ 8525.317602] [UFW BLOCK] IN=eth0 OUT= MAC=00:03:0d:6d:e0:5d:00:1a:2a:8a:1d:c6:08:00 SRC=188.22.143.148 DST=192.168.2.5 LEN=95 TOS=0x00 PREC=0x00 TTL=116 ID=31282 PROTO=UDP SPT=56783 DPT=6881 LEN=75
Sep 27 15:03:42 Serafeim-Linux kernel: [ 8525.318218] [UFW BLOCK] IN=eth0 OUT= MAC=00:03:0d:6d:e0:5d:00:1a:2a:8a:1d:c6:08:00 SRC=188.22.143.148 DST=192.168.2.5 LEN=58 TOS=0x00 PREC=0x00 TTL=116 ID=31283 PROTO=UDP SPT=56783 DPT=6881 LEN=38


When I am connected wireless and disconnects later on:

Sep 2 16:28:37 Serafeim-Linux kernel: [ 125.564378] ath5k phy0: gain calibration timeout (2412MHz)
Sep 2 16:28:37 Serafeim-Linux kernel: [ 125.972539] ath5k phy0: gain calibration timeout (2417MHz)
Sep 2 16:28:38 Serafeim-Linux kernel: [ 126.362151] ath5k phy0: gain calibration timeout (2422MHz)
Sep 2 16:28:38 Serafeim-Linux kernel: [ 126.754883] ath5k phy0: gain calibration timeout (2427MHz)
Sep 2 16:28:38 Serafeim-Linux kernel: [ 127.144903] ath5k phy0: gain calibration timeout (2432MHz)
Sep 2 16:28:39 Serafeim-Linux kernel: [ 127.534500] ath5k phy0: gain calibration timeout (2437MHz)
Sep 2 16:28:39 Serafeim-Linux kernel: [ 127.935029] ath5k phy0: gain calibration timeout (2442MHz)
Sep 2 16:28:40 Serafeim-Linux kernel: [ 128.321446] ath5k phy0: gain calibration timeout (2447MHz)
Sep 2 16:28:40 Serafeim-Linux kernel: [ 128.714731] ath5k phy0: gain calibration timeout (2452MHz)
Sep 2 16:28:40 Serafeim-Linux kernel: [ 129.114551] ath5k phy0: gain calibration timeout (2457MHz)
Sep 2 16:28:47 Serafeim-Linux kernel: [ 135.835329] __ratelimit: 4 callbacks suppressed
Sep 2 16:28:47 Serafeim-Linux kernel: [ 135.835339] ath5k phy0: gain calibration timeout (2412MHz)
Sep 2 16:28:47 Serafeim-Linux kernel: [ 136.233080] ath5k phy0: gain calibration timeout (2417MHz)
Sep 2 16:28:48 Serafeim-Linux kernel: [ 136.625393] ath5k phy0: gain calibration timeout (2422MHz)
Sep 2 16:28:48 Serafeim-Linux kernel: [ 137.012124] ath5k phy0: gain calibration timeout (2427MHz)
Sep 2 16:28:49 Serafeim-Linux kernel: [ 137.412186] ath5k phy0: gain calibration timeout (2432MHz)
Sep 2 16:28:49 Serafeim-Linux kernel: [ 137.802252] ath5k phy0: gain calibration timeout (2437MHz)
Sep 2 16:28:49 Serafeim-Linux kernel: [ 138.197153] ath5k phy0: gain calibration timeout (2442MHz)
Sep 2 16:28:50 Serafeim-Linux kernel: [ 138.584979] ath5k phy0: gain calibration timeout (2447MHz)
Sep 2 16:28:50 Serafeim-Linux kernel: [ 138.981469] ath5k phy0: gain calibration timeout (2452MHz)
Sep 2 16:28:51 Serafeim-Linux kernel: [ 139.372540] ath5k phy0: gain calibration timeout (2457MHz)
Sep 2 16:28:57 Serafeim-Linux kernel: [ 146.096966] __ratelimit: 4 callbacks suppressed
Sep 2 16:28:57 Serafeim-Linux kernel: [ 146.096976] ath5k phy0: gain calibration timeout (2412MHz)
Sep 2 16:28:58 Serafeim-Linux kernel: [ 146.491479] ath5k phy0: gain calibration timeout (2417MHz)
Sep 2 16:28:58 Serafeim-Linux kernel: [ 146.884331] ath5k phy0: gain calibration timeout (2422MHz)
Sep 2 16:28:59 Serafeim-Linux kernel: [ 147.284862] ath5k phy0: gain calibration timeout (2427MHz)
Sep 2 16:28:59 Serafeim-Linux kernel: [ 147.674367] ath5k phy0: gain calibration timeout (2432MHz)
Sep 2 16:28:59 Serafeim-Linux kernel: [ 148.064312] ath5k phy0: gain calibration timeout (2437MHz)
Sep 2 16:29:00 Serafeim-Linux kernel: [ 148.461692] ath5k phy0: gain calibration timeout (2442MHz)
Sep 2 16:29:00 Serafeim-Linux kernel: [ 148.872555] ath5k phy0: gain calibration timeout (2447MHz)
Sep 2 16:29:00 Serafeim-Linux kernel: [ 149.266952] ath5k phy0: gain calibration timeout (2452MHz)
Sep 2 16:29:01 Serafeim-Linux kernel: [ 149.661545] ath5k phy0: gain calibration timeout (2457MHz)
Sep 2 16:29:08 Serafeim-Linux kernel: [ 156.374341] __ratelimit: 4 callbacks suppressed
Sep 2 16:29:08 Serafeim-Linux kernel: [ 156.374351] ath5k phy0: gain calibration timeout (2412MHz)
Sep 2 16:29:08 Serafeim-Linux kernel: [ 156.774316] ath5k phy0: gain calibration timeout (2417MHz)
Sep 2 16:29:08 Serafeim-Linux kernel: [ 157.184383] ath5k phy0: gain calibration timeout (2422MHz)
Sep 2 16:29:09 Serafeim-Linux kernel: [ 157.581593] ath5k phy0: gain calibration timeout (2427MHz)
Sep 2 16:29:09 Serafeim-Linux kernel: [ 157.984332] ath5k phy0: gain calibration timeout (2432MHz)
Sep 2 16:29:10 Serafeim-Linux kernel: [ 158.384369] ath5k phy0: gain calibration timeout (2437MHz)
Sep 2 16:29:10 Serafeim-Linux kernel: [ 158.783188] ath5k phy0: gain calibration timeout (2442MHz)
Sep 2 16:29:10 Serafeim-Linux kernel: [ 159.184398] ath5k phy0: gain calibration timeout (2447MHz)
Sep 2 16:29:11 Serafeim-Linux kernel: [ 159.581462] ath5k phy0: gain calibration timeout (2452MHz)
Sep 2 16:29:11 Serafeim-Linux kernel: [ 159.984548] ath5k phy0: gain calibration timeout (2457MHz)
Sep 2 16:29:18 Serafeim-Linux kernel: [ 166.731135] __ratelimit: 4 callbacks suppressed
Sep 2 16:29:18 Serafeim-Linux kernel: [ 166.731145] ath5k phy0: gain calibration timeout (2412MHz)
Sep 2 16:29:18 Serafeim-Linux kernel: [ 167.138590] ath5k phy0: gain calibration timeout (2417MHz)
Sep 2 16:29:19 Serafeim-Linux kernel: [ 167.539912] ath5k phy0: gain calibration timeout (2422MHz)
Sep 2 16:29:19 Serafeim-Linux kernel: [ 167.941643] ath5k phy0: gain calibration timeout (2427MHz)
Sep 2 16:29:20 Serafeim-Linux kernel: [ 168.344353] ath5k phy0: gain calibration timeout (2432MHz)
Sep 2 16:29:20 Serafeim-Linux kernel: [ 168.754333] ath5k phy0: gain calibration timeout (2437MHz)
Sep 2 16:29:20 Serafeim-Linux kernel: [ 169.144633] ath5k phy0: gain calibration timeout (2442MHz)
Sep 2 16:29:21 Serafeim-Linux kernel: [ 169.554365] ath5k phy0: gain calibration timeout (2447MHz)
Sep 2 16:29:21 Serafeim-Linux kernel: [ 169.960364] ath5k phy0: gain calibration timeout (2452MHz)
Sep 2 16:29:22 Serafeim-Linux kernel: [ 170.361462] ath5k phy0: gain calibration timeout (2457MHz)
Sep 2 16:29:27 Serafeim-Linux NetworkManager: <info> Activation (wlan0/wireless): association took too long.
Sep 2 16:29:27 Serafeim-Linux NetworkManager: <info> (wlan0): device state change: 5 -> 6 (reason 0)
Sep 2 16:29:27 Serafeim-Linux NetworkManager: <info> Activation (wlan0/wireless): asking for new secrets
Sep 2 16:29:27 Serafeim-Linux NetworkManager: <info> (wlan0): supplicant connection state: scanning -> disconnected


Thank you all in advance! Any idea will be useful and appreciated as Internet connection is frequently used and a strong connection is undoubtedly essential.
 
Old 10-15-2010, 03:38 AM   #2
penguinHugger
LQ Newbie
 
Registered: Aug 2008
Distribution: Ubuntu, EeeOS
Posts: 26

Rep: Reputation: 15
Your having serious wireless problems. It is probably the driver. I have had many problems with Atheros chips. I never could get the ath5k driver to work, maybe try one of the others. Also, it's a big problem then you can get a USB wireless addapter for about $10-15. Until things get fixed.
 
Old 10-15-2010, 04:22 AM   #3
Ziloma
LQ Newbie
 
Registered: Oct 2007
Posts: 5

Rep: Reputation: 0
it looks like you might have a problem with conflicting drivers. I had the same problem with my opensuse 11.1 installation and came to figure out that there was a conflict between the legacy driver and the new one. searched in some forums (drats, I have forgotten the link) and found out which one to blacklist.
otherwise you migh need to use the proprietary drivers through ndiswrapper.
also checkout madwifi, it deals with atheros drivers.
 
Old 10-15-2010, 04:25 AM   #4
penguinHugger
LQ Newbie
 
Registered: Aug 2008
Distribution: Ubuntu, EeeOS
Posts: 26

Rep: Reputation: 15
ath5k is a madwifi driver. Though getting the non open source madwifi driver may help. It is sometimes better.
 
Old 10-16-2010, 06:36 AM   #5
serafimg
Member
 
Registered: Jan 2006
Distribution: Ubuntu 10.10 64-bit
Posts: 60

Original Poster
Rep: Reputation: 15
Ziloma, how can I find out which drivers I have installed and how can I backlist one of them...?

PenguinHugger, how can I remove ath5k and install the madwifi driver?


Thank you all for your replies!
 
Old 10-16-2010, 11:23 AM   #6
penguinHugger
LQ Newbie
 
Registered: Aug 2008
Distribution: Ubuntu, EeeOS
Posts: 26

Rep: Reputation: 15
Go to http://madwifi-project.org/ and download the latest release, then follow the instructions to compile/install.

Google "linux blacklist module" to find out how to keep a module from being loaded by default. You can still load it by hand, but it wont do it on it's own. Also there is a linux specific google search at http://www.google.com/linux
 
Old 10-17-2010, 06:47 AM   #7
Ziloma
LQ Newbie
 
Registered: Oct 2007
Posts: 5

Rep: Reputation: 0
i will second penguinhugger.
 
Old 10-31-2010, 08:52 AM   #8
serafimg
Member
 
Registered: Jan 2006
Distribution: Ubuntu 10.10 64-bit
Posts: 60

Original Poster
Rep: Reputation: 15
I tried both mad-wifi driver and windows driver.
None of them solved the problem.
By using the windows driver I get the following errors, found in the syslog sector of log viewer.

When I am connected wireless:

Oct 21 09:42:58 Serafeim-Linux NetworkManager[1095]: <info> (ath0): supplicant connection state: disconnected -> associated
Oct 21 09:42:58 Serafeim-Linux wpa_supplicant[1124]: CTRL-EVENT-CONNECTED - Connection to 00:24:17:a9:76:1b completed (reauth) [id=0 id_str=]
Oct 21 09:42:58 Serafeim-Linux NetworkManager[1095]: <info> (ath0): supplicant connection state: associated -> completed
Oct 21 09:42:59 Serafeim-Linux wpa_supplicant[1124]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Oct 21 09:42:59 Serafeim-Linux NetworkManager[1095]: <info> (ath0): supplicant connection state: completed -> disconnected
Oct 21 09:42:59 Serafeim-Linux NetworkManager[1095]: <info> (ath0): supplicant connection state: disconnected -> scanning
Oct 21 09:43:02 Serafeim-Linux wpa_supplicant[1124]: Trying to associate with 00:24:17:a9:76:1b (SSID='Thomson429D7D' freq=2462 MHz)
Oct 21 09:43:02 Serafeim-Linux NetworkManager[1095]: <info> (ath0): supplicant connection state: scanning -> associating
Oct 21 09:43:02 Serafeim-Linux wpa_supplicant[1124]: Associated with 00:24:17:a9:76:1b
Oct 21 09:43:02 Serafeim-Linux NetworkManager[1095]: <info> (ath0): supplicant connection state: associating -> associated
Oct 21 09:43:02 Serafeim-Linux wpa_supplicant[1124]: CTRL-EVENT-CONNECTED - Connection to 00:24:17:a9:76:1b completed (reauth) [id=0 id_str=]
Oct 21 09:43:02 Serafeim-Linux NetworkManager[1095]: <info> (ath0): supplicant connection state: associated -> completed
Oct 21 09:43:10 Serafeim-Linux wpa_supplicant[1124]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Oct 21 09:43:10 Serafeim-Linux NetworkManager[1095]: <info> (ath0): supplicant connection state: completed -> disconnected
Oct 21 09:43:10 Serafeim-Linux NetworkManager[1095]: <info> (ath0): supplicant connection state: disconnected -> scanning
Oct 21 09:43:12 Serafeim-Linux wpa_supplicant[1124]: Trying to associate with 00:24:17:a9:76:1b (SSID='Thomson429D7D' freq=2462 MHz)
Oct 21 09:43:12 Serafeim-Linux NetworkManager[1095]: <info> (ath0): supplicant connection state: scanning -> associating
Oct 21 09:43:12 Serafeim-Linux wpa_supplicant[1124]: Associated with 00:24:17:a9:76:1b
Oct 21 09:43:12 Serafeim-Linux NetworkManager[1095]: <info> (ath0): supplicant connection state: associating -> associated
Oct 21 09:43:12 Serafeim-Linux wpa_supplicant[1124]: CTRL-EVENT-CONNECTED - Connection to 00:24:17:a9:76:1b completed (reauth) [id=0 id_str=]
Oct 21 09:43:12 Serafeim-Linux NetworkManager[1095]: <info> (ath0): supplicant connection state: associated -> completed
Oct 21 09:43:31 Serafeim-Linux wpa_supplicant[1124]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Oct 21 09:43:31 Serafeim-Linux NetworkManager[1095]: <info> (ath0): supplicant connection state: completed -> disconnected
Oct 21 09:43:31 Serafeim-Linux NetworkManager[1095]: <info> (ath0): supplicant connection state: disconnected -> scanning
Oct 21 09:43:34 Serafeim-Linux wpa_supplicant[1124]: Trying to associate with 00:24:17:a9:76:1b (SSID='Thomson429D7D' freq=2462 MHz)
Oct 21 09:43:34 Serafeim-Linux NetworkManager[1095]: <info> (ath0): supplicant connection state: scanning -> associating
Oct 21 09:43:34 Serafeim-Linux wpa_supplicant[1124]: Associated with 00:24:17:a9:76:1b
Oct 21 09:43:34 Serafeim-Linux NetworkManager[1095]: <info> (ath0): supplicant connection state: associating -> associated
Oct 21 09:43:34 Serafeim-Linux wpa_supplicant[1124]: CTRL-EVENT-CONNECTED - Connection to 00:24:17:a9:76:1b completed (reauth) [id=0 id_str=]
Oct 21 09:43:34 Serafeim-Linux NetworkManager[1095]: <info> (ath0): supplicant connection state: associated -> completed
Oct 21 09:43:47 Serafeim-Linux rsyslogd: [origin software="rsyslogd" swVersion="4.2.0" x-pid="1055" x-info="http://www.rsyslog.com"] rsyslogd was HUPed, type 'lightweight'.




When I am connected wired:

Oct 20 10:36:07 Serafeim-Linux kernel: [ 83.516319] Clocksource tsc unstable (delta = -93894799 ns)
Oct 20 10:36:21 Serafeim-Linux NetworkManager[1016]: <info> (eth0): carrier now ON (device state 2)
Oct 20 10:36:21 Serafeim-Linux NetworkManager[1016]: <info> (eth0): device state change: 2 -> 3 (reason 40)
Oct 20 10:36:21 Serafeim-Linux NetworkManager[1016]: <info> Activation (eth0) starting connection 'Auto eth0'
Oct 20 10:36:21 Serafeim-Linux NetworkManager[1016]: <info> (eth0): device state change: 3 -> 4 (reason 0)
Oct 20 10:36:21 Serafeim-Linux NetworkManager[1016]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Oct 20 10:36:21 Serafeim-Linux NetworkManager[1016]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Oct 20 10:36:21 Serafeim-Linux NetworkManager[1016]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Oct 20 10:36:21 Serafeim-Linux NetworkManager[1016]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Oct 20 10:36:21 Serafeim-Linux NetworkManager[1016]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Oct 20 10:36:21 Serafeim-Linux NetworkManager[1016]: <info> (eth0): device state change: 4 -> 5 (reason 0)
Oct 20 10:36:21 Serafeim-Linux NetworkManager[1016]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Oct 20 10:36:21 Serafeim-Linux kernel: [ 97.533771] r8169 0000:08:00.0: eth0: link up
Oct 20 10:36:21 Serafeim-Linux kernel: [ 97.534621] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Oct 20 10:36:21 Serafeim-Linux NetworkManager[1016]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Oct 20 10:36:21 Serafeim-Linux NetworkManager[1016]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Oct 20 10:36:21 Serafeim-Linux NetworkManager[1016]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Oct 20 10:36:21 Serafeim-Linux NetworkManager[1016]: <info> (eth0): device state change: 5 -> 7 (reason 0)
Oct 20 10:36:21 Serafeim-Linux NetworkManager[1016]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) scheduled...
Oct 20 10:36:21 Serafeim-Linux NetworkManager[1016]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Oct 20 10:36:21 Serafeim-Linux NetworkManager[1016]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) started...
Oct 20 10:36:21 Serafeim-Linux NetworkManager[1016]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
Oct 20 10:36:21 Serafeim-Linux NetworkManager[1016]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) complete.
Oct 20 10:36:21 Serafeim-Linux NetworkManager[1016]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started...
Oct 20 10:36:21 Serafeim-Linux avahi-daemon[1030]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.2.5.
Oct 20 10:36:21 Serafeim-Linux avahi-daemon[1030]: New relevant interface eth0.IPv4 for mDNS.
Oct 20 10:36:21 Serafeim-Linux avahi-daemon[1030]: Registering new address record for 192.168.2.5 on eth0.IPv4.
Oct 20 10:36:22 Serafeim-Linux NetworkManager[1016]: <info> (eth0): device state change: 7 -> 8 (reason 0)
Oct 20 10:36:22 Serafeim-Linux avahi-daemon[1030]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::203:dff:fe6d:e05d.
Oct 20 10:36:22 Serafeim-Linux avahi-daemon[1030]: New relevant interface eth0.IPv6 for mDNS.
Oct 20 10:36:22 Serafeim-Linux avahi-daemon[1030]: Registering new address record for fe80::203:dff:fe6d:e05d on eth0.*.
Oct 20 10:36:22 Serafeim-Linux NetworkManager[1016]: <info> Policy set 'Auto eth0' (eth0) as default for IPv4 routing and DNS.
Oct 20 10:36:22 Serafeim-Linux NetworkManager[1016]: <info> Activation (eth0) successful, device activated.
Oct 20 10:36:22 Serafeim-Linux NetworkManager[1016]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
Oct 20 10:36:31 Serafeim-Linux kernel: [ 107.571211] eth0: no IPv6 routers present
Oct 20 10:36:33 Serafeim-Linux nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/01ifupdown' exited with error status 1.
Oct 20 10:37:13 Serafeim-Linux ntpdate[2052]: can't find host ntp.ubuntu.com
Oct 20 10:37:13 Serafeim-Linux ntpdate[2052]: no servers can be used, exiting
Oct 20 10:40:03 Serafeim-Linux anacron[1195]: Job `cron.daily' started
Oct 20 10:40:03 Serafeim-Linux anacron[2179]: Updated timestamp for job `cron.daily' to 2010-10-20
Oct 20 10:40:12 Serafeim-Linux kernel: [ 328.981222] r8169 0000:08:00.0: eth0: link down
Oct 20 10:40:12 Serafeim-Linux NetworkManager[1016]: <info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds)
Oct 20 10:40:14 Serafeim-Linux NetworkManager[1016]: <info> (eth0): carrier now ON (device state 8)
Oct 20 10:40:14 Serafeim-Linux kernel: [ 330.906797] r8169 0000:08:00.0: eth0: link up
Oct 20 10:40:22 Serafeim-Linux kernel: [ 338.646707] r8169 0000:08:00.0: eth0: link down
Oct 20 10:40:22 Serafeim-Linux NetworkManager[1016]: <info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds)
Oct 20 10:40:26 Serafeim-Linux NetworkManager[1016]: <info> (eth0): carrier now ON (device state 8)
Oct 20 10:40:26 Serafeim-Linux kernel: [ 342.808253] r8169 0000:08:00.0: eth0: link up
Oct 20 10:42:09 Serafeim-Linux NetworkManager[1016]: <info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds)
Oct 20 10:42:09 Serafeim-Linux kernel: [ 445.738080] r8169 0000:08:00.0: eth0: link down
Oct 20 10:42:11 Serafeim-Linux NetworkManager[1016]: <info> (eth0): carrier now ON (device state 8)
Oct 20 10:42:11 Serafeim-Linux kernel: [ 447.677394] r8169 0000:08:00.0: eth0: link up
Oct 20 10:42:19 Serafeim-Linux kernel: [ 455.402836] r8169 0000:08:00.0: eth0: link down
Oct 20 10:42:19 Serafeim-Linux NetworkManager[1016]: <info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds)
Oct 20 10:42:20 Serafeim-Linux NetworkManager[1016]: <info> (eth0): carrier now ON (device state 8)
Oct 20 10:42:20 Serafeim-Linux kernel: [ 457.177615] r8169 0000:08:00.0: eth0: link up
 
Old 10-31-2010, 01:14 PM   #9
penguinHugger
LQ Newbie
 
Registered: Aug 2008
Distribution: Ubuntu, EeeOS
Posts: 26

Rep: Reputation: 15
Here's the bug on launchpad:

https://bugs.launchpad.net/ubuntu/+s...ger/+bug/37821
 
  


Reply

Tags
atheros, laptop, ubuntu, wired, wireless


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Wireless Fujitsu Siemens Amilo 1650 dzcharles Debian 3 03-25-2010 12:43 PM
Installing wireless on Fujitsu-Siemens Amilo Pro remipham Linux - Laptop and Netbook 1 08-12-2008 03:00 PM
Ubuntu/kubuntu on Fujitsu-Siemens Amilo M7440 LeoKhan Linux - Laptop and Netbook 7 08-30-2005 11:25 AM
Linux with Fujitsu-Siemens Amilo D8830 nbsinner Linux - Laptop and Netbook 8 03-12-2005 05:48 PM
News: Fujitsu Siemens Amilo and Linux Impaler Linux - Laptop and Netbook 3 04-04-2004 12:08 PM


All times are GMT -5. The time now is 08:20 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration