Wired and wireless problems with Fujitsu Siemens Amilo PA 2510 using Ubuntu Linux
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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:
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.
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.
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.
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
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
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.