Page 1 of 1

[SOLVED] Mageia1 (64-bit) network problem

PostPosted: Jan 22nd, '12, 10:47
by dude67
I'm experiencing a weird problem I've never encountered before. I'm having a hard time connecting to my home network (wired LAN) and naturally to the internet. The connection is erratic at best. I sometimes cannot connect at all for minutes, but mostly it's just on-and-off connection. It's like 2 to 10 seconds connection on and then it's off again for a similar (or longer) period of time.

First of all, this is my first 64-bit linux desktop. I installed it from a downloaded Mageia1 64-bit DVD and have since installed sources and updated the system. The PC is a dual boot with Win7 pro. Within Win7 the connection works like charm - no problem. All other wired and wireless connections in my network work fine - it's just this one system that doesn't seem to work.

The LAN module is integrated to the motherboard and the model is ASUS P8-Z68-M Pro.

I have two Zyxel ADSL/LAN/WLAN gateways (P-661HNU and P-661HN) and I've tried them both (only one at a time operating in my network). The results are the same with both of them. I've also disabled firewall and MAC filters within Zyxel, but no help.

I've also tried with both automatic (DHCP) or fixed IP configuration.

I don't know, but I would rule out hw-failure as it's working without problems in my Win7 Pro installation.

Here's copy of my ping tests (.254 is my gateway and .9 is the problem PC's fixed IP):
Code: Select all
    $ ping 192.168.254.254
    PING 192.168.254.254 (192.168.254.254) 56(84) bytes of data.
    From 192.168.254.9 icmp_seq=1 Destination Host Unreachable
    From 192.168.254.9 icmp_seq=2 Destination Host Unreachable
    From 192.168.254.9 icmp_seq=3 Destination Host Unreachable
    From 192.168.254.9 icmp_seq=4 Destination Host Unreachable
    64 bytes from 192.168.254.254: icmp_req=7 ttl=254 time=10.6 ms
    64 bytes from 192.168.254.254: icmp_req=8 ttl=254 time=1.41 ms
    64 bytes from 192.168.254.254: icmp_req=9 ttl=254 time=1.33 ms
    64 bytes from 192.168.254.254: icmp_req=10 ttl=254 time=1.34 ms
    64 bytes from 192.168.254.254: icmp_req=11 ttl=254 time=1.49 ms
    64 bytes from 192.168.254.254: icmp_req=12 ttl=254 time=1.31 ms
    64 bytes from 192.168.254.254: icmp_req=13 ttl=254 time=1.33 ms
    64 bytes from 192.168.254.254: icmp_req=14 ttl=254 time=1.33 ms
    64 bytes from 192.168.254.254: icmp_req=15 ttl=254 time=1.36 ms
    64 bytes from 192.168.254.254: icmp_req=16 ttl=254 time=1.34 ms
    ^C
    --- 192.168.254.254 ping statistics ---
    16 packets transmitted, 10 received, +4 errors, 37% packet loss, time 15012ms
    rtt min/avg/max/mdev = 1.310/2.287/10.602/2.772 ms, pipe 3

    $ ping 192.168.254.254
    PING 192.168.254.254 (192.168.254.254) 56(84) bytes of data.
    64 bytes from 192.168.254.254: icmp_req=5 ttl=254 time=1.93 ms
    64 bytes from 192.168.254.254: icmp_req=6 ttl=254 time=2.61 ms
    64 bytes from 192.168.254.254: icmp_req=7 ttl=254 time=1.52 ms
    64 bytes from 192.168.254.254: icmp_req=8 ttl=254 time=1.37 ms
    64 bytes from 192.168.254.254: icmp_req=9 ttl=254 time=1.31 ms
    64 bytes from 192.168.254.254: icmp_req=10 ttl=254 time=1.41 ms
    64 bytes from 192.168.254.254: icmp_req=11 ttl=254 time=1.30 ms
    64 bytes from 192.168.254.254: icmp_req=12 ttl=254 time=1.35 ms
    64 bytes from 192.168.254.254: icmp_req=13 ttl=254 time=1.39 ms
    64 bytes from 192.168.254.254: icmp_req=14 ttl=254 time=1.46 ms
    64 bytes from 192.168.254.254: icmp_req=16 ttl=254 time=1.35 ms
    64 bytes from 192.168.254.254: icmp_req=17 ttl=254 time=1.34 ms
    64 bytes from 192.168.254.254: icmp_req=19 ttl=254 time=1.34 ms
    ^C
    --- 192.168.254.254 ping statistics ---
    20 packets transmitted, 13 received, 35% packet loss, time 19016ms
    rtt min/avg/max/mdev = 1.302/1.518/2.614/0.354 ms


    $ ping 192.168.254.254
    PING 192.168.254.254 (192.168.254.254) 56(84) bytes of data.
    64 bytes from 192.168.254.254: icmp_req=10 ttl=254 time=1.34 ms
    64 bytes from 192.168.254.254: icmp_req=11 ttl=254 time=1.39 ms
    64 bytes from 192.168.254.254: icmp_req=12 ttl=254 time=1.36 ms
    64 bytes from 192.168.254.254: icmp_req=13 ttl=254 time=1.38 ms
    64 bytes from 192.168.254.254: icmp_req=14 ttl=254 time=1.49 ms
    ^C
    --- 192.168.254.254 ping statistics ---
    14 packets transmitted, 5 received, 64% packet loss, time 13004ms
    rtt min/avg/max/mdev = 1.342/1.395/1.492/0.061 ms


Any help is greatly appreciated! :)

Re: Mageia1 (64-bit) network problem

PostPosted: Jan 22nd, '12, 11:27
by CaptSilver
Are you using a PPOE and if so, which machine is doing the connection?

Have you tried changing cables, if that is an option?

Finally, turn off and unplug your computer to reset the integrated LAN on your computer. I would suggest 5 minutes. All I know it has something to do with resetting WOL that sometimes works.

Re: Mageia1 (64-bit) network problem

PostPosted: Jan 22nd, '12, 11:30
by CaptSilver
Also, may seem simple... but make sure you do NOT have an IP conflict. That would do it.

Re: Mageia1 (64-bit) network problem

PostPosted: Jan 22nd, '12, 12:15
by dude67
CaptSilver wrote:Are you using a PPOE and if so, which machine is doing the connection?

Have you tried changing cables, if that is an option?

Finally, turn off and unplug your computer to reset the integrated LAN on your computer. I would suggest 5 minutes. All I know it has something to do with resetting WOL that sometimes works.

I've changed the cable also, but as I said everything works like charm under Win7 Pro (64-bit). So that's not it. And I'm not using Wake-On-Lan (at least not to my knowledge).

I always turn this PC off for the night (i.e. several hours at a time) and I've changed the PC between Win7 and Mageia several times during the day (thus turning it off quite often).
CaptSilver wrote:Also, may seem simple... but make sure you do NOT have an IP conflict. That would do it.

Thanks CaptSilver, but no, that's not the case. I keep a list of all IPs in my home network. And as I said, I've also tried it with automatic IP configuration (DHCP enabled also in the Zyxel boxes).

Re: Mageia1 (64-bit) network problem

PostPosted: Jan 22nd, '12, 14:47
by martinw
If, as root, you run
Code: Select all
tail -f /var/log/messages

in a terminal window, are there any helpful (or unhelpful!) messages relating to the network connection as the connection comes and goes?

Re: Mageia1 (64-bit) network problem

PostPosted: Jan 22nd, '12, 16:54
by dude67
OK, this is how shows up in /var/log/messages file. At this same time I tried pinging (a bit further down the ping messages)
Code: Select all
# tail -f /var/log/messages
Jan 22 16:44:40 localhost kernel: ctnetlink v0.93: registering with nfnetlink.
Jan 22 16:44:40 localhost kernel: ipt_CLUSTERIP: ClusterIP Version 0.8 loaded successfully
Jan 22 16:44:41 localhost kernel: ip_set: protocol 6
Jan 22 16:44:41 localhost kernel: xt_time: kernel timezone is +0200
Jan 22 16:44:41 localhost kernel: u32 classifier
Jan 22 16:44:41 localhost kernel:    Actions configured
Jan 22 16:44:41 localhost logger: Shorewall started
Jan 22 16:45:28 localhost kernel: r8169 0000:03:00.0: eth0: link up
Jan 22 16:45:44 localhost kernel: r8169 0000:03:00.0: eth0: link up
Jan 22 16:45:54 localhost kernel: r8169 0000:03:00.0: eth0: link up
Jan 22 16:46:53 localhost kernel: r8169 0000:03:00.0: eth0: link up
Jan 22 16:47:34 localhost mgaapplet[3168]: trying distributions list from https://releases.mageia.org/api/a/x86_64?product=Default&version=1&mgaonline_version=2.77.29
Jan 22 16:47:34 localhost mgaapplet[3168]: Computing new updates...
Jan 22 16:47:34 localhost mgaapplet[3168]: running: urpmi.update --update
Jan 22 16:48:16 localhost kernel: r8169 0000:03:00.0: eth0: link up
Jan 22 16:48:23 localhost kernel: r8169 0000:03:00.0: eth0: link up
Jan 22 16:48:25 localhost kernel: r8169 0000:03:00.0: eth0: link up
Jan 22 16:48:27 localhost kernel: r8169 0000:03:00.0: eth0: link up
Jan 22 16:48:28 localhost kernel: r8169 0000:03:00.0: eth0: link up
Jan 22 16:48:31 localhost kernel: r8169 0000:03:00.0: eth0: link up
Jan 22 16:48:34 localhost mgaapplet[3168]: updating inactive backport media Core Backports (distrib7), Core Backports Testing (distrib9), Nonfree Backports (distrib17), Nonfree Backports Testing (distrib19), Tainted Backports Testing (distrib29), Core 32bit Backports (distrib37), Core 32bit Backports Testing (distrib39)
Jan 22 16:48:34 localhost mgaapplet[3168]: running: urpmi.update Core Backports (distrib7)
Jan 22 16:48:35 localhost mgaapplet[3168]: running: urpmi.update Core Backports Testing (distrib9)
Jan 22 16:49:15 localhost kernel: r8169 0000:03:00.0: eth0: link up
Jan 22 16:49:25 localhost kernel: r8169 0000:03:00.0: eth0: link up


Code: Select all
$ ping 192.168.254.254                                                                                                     
PING 192.168.254.254 (192.168.254.254) 56(84) bytes of data.                                                                               
From 192.168.254.9 icmp_seq=1 Destination Host Unreachable
From 192.168.254.9 icmp_seq=2 Destination Host Unreachable
From 192.168.254.9 icmp_seq=5 Destination Host Unreachable
64 bytes from 192.168.254.254: icmp_req=6 ttl=254 time=2.48 ms
64 bytes from 192.168.254.254: icmp_req=7 ttl=254 time=1.33 ms
64 bytes from 192.168.254.254: icmp_req=8 ttl=254 time=1.39 ms
64 bytes from 192.168.254.254: icmp_req=9 ttl=254 time=1.35 ms
64 bytes from 192.168.254.254: icmp_req=10 ttl=254 time=1.39 ms
64 bytes from 192.168.254.254: icmp_req=15 ttl=254 time=1.43 ms
64 bytes from 192.168.254.254: icmp_req=16 ttl=254 time=1.37 ms
64 bytes from 192.168.254.254: icmp_req=17 ttl=254 time=1.30 ms
64 bytes from 192.168.254.254: icmp_req=41 ttl=254 time=1.49 ms
64 bytes from 192.168.254.254: icmp_req=42 ttl=254 time=1.30 ms
64 bytes from 192.168.254.254: icmp_req=43 ttl=254 time=1.32 ms
64 bytes from 192.168.254.254: icmp_req=69 ttl=254 time=499 ms
64 bytes from 192.168.254.254: icmp_req=70 ttl=254 time=1.36 ms
64 bytes from 192.168.254.254: icmp_req=71 ttl=254 time=1.39 ms
64 bytes from 192.168.254.254: icmp_req=72 ttl=254 time=1.34 ms
64 bytes from 192.168.254.254: icmp_req=73 ttl=254 time=1.34 ms
64 bytes from 192.168.254.254: icmp_req=74 ttl=254 time=1.36 ms
64 bytes from 192.168.254.254: icmp_req=75 ttl=254 time=1.33 ms
64 bytes from 192.168.254.254: icmp_req=76 ttl=254 time=1.48 ms
64 bytes from 192.168.254.254: icmp_req=77 ttl=254 time=1.30 ms
64 bytes from 192.168.254.254: icmp_req=78 ttl=254 time=1.31 ms
64 bytes from 192.168.254.254: icmp_req=81 ttl=254 time=1.39 ms
64 bytes from 192.168.254.254: icmp_req=82 ttl=254 time=1.32 ms
64 bytes from 192.168.254.254: icmp_req=83 ttl=254 time=1.34 ms
64 bytes from 192.168.254.254: icmp_req=84 ttl=254 time=1.31 ms
64 bytes from 192.168.254.254: icmp_req=85 ttl=254 time=1.36 ms
64 bytes from 192.168.254.254: icmp_req=86 ttl=254 time=1.33 ms
64 bytes from 192.168.254.254: icmp_req=87 ttl=254 time=1.40 ms
64 bytes from 192.168.254.254: icmp_req=88 ttl=254 time=1.32 ms
64 bytes from 192.168.254.254: icmp_req=89 ttl=254 time=1.39 ms
64 bytes from 192.168.254.254: icmp_req=90 ttl=254 time=1.39 ms
64 bytes from 192.168.254.254: icmp_req=91 ttl=254 time=1.39 ms
64 bytes from 192.168.254.254: icmp_req=92 ttl=254 time=1.33 ms
64 bytes from 192.168.254.254: icmp_req=93 ttl=254 time=1.44 ms
64 bytes from 192.168.254.254: icmp_req=94 ttl=254 time=1.34 ms
From 192.168.254.9 icmp_seq=121 Destination Host Unreachable
From 192.168.254.9 icmp_seq=122 Destination Host Unreachable
From 192.168.254.9 icmp_seq=123 Destination Host Unreachable
From 192.168.254.9 icmp_seq=125 Destination Host Unreachable
From 192.168.254.9 icmp_seq=126 Destination Host Unreachable
From 192.168.254.9 icmp_seq=127 Destination Host Unreachable
From 192.168.254.9 icmp_seq=129 Destination Host Unreachable
From 192.168.254.9 icmp_seq=130 Destination Host Unreachable
From 192.168.254.9 icmp_seq=131 Destination Host Unreachable
From 192.168.254.9 icmp_seq=132 Destination Host Unreachable
From 192.168.254.9 icmp_seq=133 Destination Host Unreachable
From 192.168.254.9 icmp_seq=134 Destination Host Unreachable
From 192.168.254.9 icmp_seq=136 Destination Host Unreachable
From 192.168.254.9 icmp_seq=137 Destination Host Unreachable
From 192.168.254.9 icmp_seq=138 Destination Host Unreachable
From 192.168.254.9 icmp_seq=140 Destination Host Unreachable
From 192.168.254.9 icmp_seq=141 Destination Host Unreachable
From 192.168.254.9 icmp_seq=142 Destination Host Unreachable
From 192.168.254.9 icmp_seq=144 Destination Host Unreachable
From 192.168.254.9 icmp_seq=145 Destination Host Unreachable
From 192.168.254.9 icmp_seq=146 Destination Host Unreachable
64 bytes from 192.168.254.254: icmp_req=147 ttl=254 time=2008 ms
64 bytes from 192.168.254.254: icmp_req=148 ttl=254 time=1008 ms
64 bytes from 192.168.254.254: icmp_req=149 ttl=254 time=8.70 ms
64 bytes from 192.168.254.254: icmp_req=150 ttl=254 time=1.47 ms
64 bytes from 192.168.254.254: icmp_req=151 ttl=254 time=1.40 ms
64 bytes from 192.168.254.254: icmp_req=152 ttl=254 time=1.40 ms
64 bytes from 192.168.254.254: icmp_req=153 ttl=254 time=1.42 ms
64 bytes from 192.168.254.254: icmp_req=154 ttl=254 time=1.31 ms
64 bytes from 192.168.254.254: icmp_req=155 ttl=254 time=1.34 ms
64 bytes from 192.168.254.254: icmp_req=156 ttl=254 time=1.40 ms
64 bytes from 192.168.254.254: icmp_req=157 ttl=254 time=1.40 ms
64 bytes from 192.168.254.254: icmp_req=158 ttl=254 time=1.39 ms
64 bytes from 192.168.254.254: icmp_req=159 ttl=254 time=1.37 ms
64 bytes from 192.168.254.254: icmp_req=160 ttl=254 time=1.34 ms
64 bytes from 192.168.254.254: icmp_req=161 ttl=254 time=1.38 ms
64 bytes from 192.168.254.254: icmp_req=162 ttl=254 time=1.44 ms
64 bytes from 192.168.254.254: icmp_req=163 ttl=254 time=1.52 ms
64 bytes from 192.168.254.254: icmp_req=164 ttl=254 time=1.30 ms
64 bytes from 192.168.254.254: icmp_req=165 ttl=254 time=1.33 ms
64 bytes from 192.168.254.254: icmp_req=166 ttl=254 time=1.32 ms
64 bytes from 192.168.254.254: icmp_req=167 ttl=254 time=1.34 ms
64 bytes from 192.168.254.254: icmp_req=168 ttl=254 time=1.33 ms
64 bytes from 192.168.254.254: icmp_req=169 ttl=254 time=1.32 ms
64 bytes from 192.168.254.254: icmp_req=170 ttl=254 time=1.30 ms
64 bytes from 192.168.254.254: icmp_req=171 ttl=254 time=1.34 ms
64 bytes from 192.168.254.254: icmp_req=172 ttl=254 time=1.51 ms
64 bytes from 192.168.254.254: icmp_req=173 ttl=254 time=1.37 ms
64 bytes from 192.168.254.254: icmp_req=174 ttl=254 time=1.35 ms
64 bytes from 192.168.254.254: icmp_req=175 ttl=254 time=1.42 ms
64 bytes from 192.168.254.254: icmp_req=176 ttl=254 time=1.38 ms
64 bytes from 192.168.254.254: icmp_req=177 ttl=254 time=1.39 ms
64 bytes from 192.168.254.254: icmp_req=178 ttl=254 time=1.37 ms
64 bytes from 192.168.254.254: icmp_req=179 ttl=254 time=1.47 ms
64 bytes from 192.168.254.254: icmp_req=180 ttl=254 time=1.39 ms
64 bytes from 192.168.254.254: icmp_req=181 ttl=254 time=1.39 ms
64 bytes from 192.168.254.254: icmp_req=182 ttl=254 time=1.42 ms
64 bytes from 192.168.254.254: icmp_req=183 ttl=254 time=1.36 ms
64 bytes from 192.168.254.254: icmp_req=184 ttl=254 time=1.35 ms
64 bytes from 192.168.254.254: icmp_req=185 ttl=254 time=1.40 ms
64 bytes from 192.168.254.254: icmp_req=186 ttl=254 time=1.45 ms
64 bytes from 192.168.254.254: icmp_req=187 ttl=254 time=1.41 ms
64 bytes from 192.168.254.254: icmp_req=188 ttl=254 time=1.30 ms
64 bytes from 192.168.254.254: icmp_req=189 ttl=254 time=1.38 ms
64 bytes from 192.168.254.254: icmp_req=190 ttl=254 time=1.33 ms
64 bytes from 192.168.254.254: icmp_req=191 ttl=254 time=1.38 ms
64 bytes from 192.168.254.254: icmp_req=192 ttl=254 time=1.40 ms
64 bytes from 192.168.254.254: icmp_req=193 ttl=254 time=1.46 ms
64 bytes from 192.168.254.254: icmp_req=194 ttl=254 time=1.33 ms
64 bytes from 192.168.254.254: icmp_req=195 ttl=254 time=1.37 ms
64 bytes from 192.168.254.254: icmp_req=196 ttl=254 time=1.39 ms
64 bytes from 192.168.254.254: icmp_req=197 ttl=254 time=1.31 ms
^C
--- 192.168.254.254 ping statistics ---
203 packets transmitted, 86 received, +24 errors, 57% packet loss, time 202111ms
rtt min/avg/max/mdev = 1.304/42.313/2008.417/244.626 ms, pipe 3

Re: Mageia1 (64-bit) network problem

PostPosted: Jan 22nd, '12, 16:58
by dude67
OK, this is how shows up in /var/log/messages file. At this same time I tried pinging (a bit further down the ping messages)
Code: Select all
# tail -f /var/log/messages
Jan 22 16:44:40 localhost kernel: ctnetlink v0.93: registering with nfnetlink.
Jan 22 16:44:40 localhost kernel: ipt_CLUSTERIP: ClusterIP Version 0.8 loaded successfully
Jan 22 16:44:41 localhost kernel: ip_set: protocol 6
Jan 22 16:44:41 localhost kernel: xt_time: kernel timezone is +0200
Jan 22 16:44:41 localhost kernel: u32 classifier
Jan 22 16:44:41 localhost kernel:    Actions configured
Jan 22 16:44:41 localhost logger: Shorewall started
Jan 22 16:45:28 localhost kernel: r8169 0000:03:00.0: eth0: link up
Jan 22 16:45:44 localhost kernel: r8169 0000:03:00.0: eth0: link up
Jan 22 16:45:54 localhost kernel: r8169 0000:03:00.0: eth0: link up
Jan 22 16:46:53 localhost kernel: r8169 0000:03:00.0: eth0: link up
Jan 22 16:47:34 localhost mgaapplet[3168]: trying distributions list from https://releases.mageia.org/api/a/x86_64?product=Default&version=1&mgaonline_version=2.77.29
Jan 22 16:47:34 localhost mgaapplet[3168]: Computing new updates...
Jan 22 16:47:34 localhost mgaapplet[3168]: running: urpmi.update --update
Jan 22 16:48:16 localhost kernel: r8169 0000:03:00.0: eth0: link up
Jan 22 16:48:23 localhost kernel: r8169 0000:03:00.0: eth0: link up
Jan 22 16:48:25 localhost kernel: r8169 0000:03:00.0: eth0: link up
Jan 22 16:48:27 localhost kernel: r8169 0000:03:00.0: eth0: link up
Jan 22 16:48:28 localhost kernel: r8169 0000:03:00.0: eth0: link up
Jan 22 16:48:31 localhost kernel: r8169 0000:03:00.0: eth0: link up
Jan 22 16:48:34 localhost mgaapplet[3168]: updating inactive backport media Core Backports (distrib7), Core Backports Testing (distrib9), Nonfree Backports (distrib17), Nonfree Backports Testing (distrib19), Tainted Backports Testing (distrib29), Core 32bit Backports (distrib37), Core 32bit Backports Testing (distrib39)
Jan 22 16:48:34 localhost mgaapplet[3168]: running: urpmi.update Core Backports (distrib7)
Jan 22 16:48:35 localhost mgaapplet[3168]: running: urpmi.update Core Backports Testing (distrib9)
Jan 22 16:49:15 localhost kernel: r8169 0000:03:00.0: eth0: link up
Jan 22 16:49:25 localhost kernel: r8169 0000:03:00.0: eth0: link up


Code: Select all
$ ping 192.168.254.254                                                                                                     
PING 192.168.254.254 (192.168.254.254) 56(84) bytes of data.                                                                               
From 192.168.254.9 icmp_seq=1 Destination Host Unreachable
From 192.168.254.9 icmp_seq=2 Destination Host Unreachable
From 192.168.254.9 icmp_seq=5 Destination Host Unreachable
64 bytes from 192.168.254.254: icmp_req=6 ttl=254 time=2.48 ms
64 bytes from 192.168.254.254: icmp_req=7 ttl=254 time=1.33 ms
64 bytes from 192.168.254.254: icmp_req=8 ttl=254 time=1.39 ms
64 bytes from 192.168.254.254: icmp_req=9 ttl=254 time=1.35 ms
64 bytes from 192.168.254.254: icmp_req=10 ttl=254 time=1.39 ms
64 bytes from 192.168.254.254: icmp_req=15 ttl=254 time=1.43 ms
64 bytes from 192.168.254.254: icmp_req=16 ttl=254 time=1.37 ms
64 bytes from 192.168.254.254: icmp_req=17 ttl=254 time=1.30 ms
64 bytes from 192.168.254.254: icmp_req=41 ttl=254 time=1.49 ms
64 bytes from 192.168.254.254: icmp_req=42 ttl=254 time=1.30 ms
64 bytes from 192.168.254.254: icmp_req=43 ttl=254 time=1.32 ms
64 bytes from 192.168.254.254: icmp_req=69 ttl=254 time=499 ms
64 bytes from 192.168.254.254: icmp_req=70 ttl=254 time=1.36 ms
64 bytes from 192.168.254.254: icmp_req=71 ttl=254 time=1.39 ms
64 bytes from 192.168.254.254: icmp_req=72 ttl=254 time=1.34 ms
64 bytes from 192.168.254.254: icmp_req=73 ttl=254 time=1.34 ms
64 bytes from 192.168.254.254: icmp_req=74 ttl=254 time=1.36 ms
64 bytes from 192.168.254.254: icmp_req=75 ttl=254 time=1.33 ms
64 bytes from 192.168.254.254: icmp_req=76 ttl=254 time=1.48 ms
64 bytes from 192.168.254.254: icmp_req=77 ttl=254 time=1.30 ms
64 bytes from 192.168.254.254: icmp_req=78 ttl=254 time=1.31 ms
64 bytes from 192.168.254.254: icmp_req=81 ttl=254 time=1.39 ms
64 bytes from 192.168.254.254: icmp_req=82 ttl=254 time=1.32 ms
64 bytes from 192.168.254.254: icmp_req=83 ttl=254 time=1.34 ms
64 bytes from 192.168.254.254: icmp_req=84 ttl=254 time=1.31 ms
64 bytes from 192.168.254.254: icmp_req=85 ttl=254 time=1.36 ms
64 bytes from 192.168.254.254: icmp_req=86 ttl=254 time=1.33 ms
64 bytes from 192.168.254.254: icmp_req=87 ttl=254 time=1.40 ms
64 bytes from 192.168.254.254: icmp_req=88 ttl=254 time=1.32 ms
64 bytes from 192.168.254.254: icmp_req=89 ttl=254 time=1.39 ms
64 bytes from 192.168.254.254: icmp_req=90 ttl=254 time=1.39 ms
64 bytes from 192.168.254.254: icmp_req=91 ttl=254 time=1.39 ms
64 bytes from 192.168.254.254: icmp_req=92 ttl=254 time=1.33 ms
64 bytes from 192.168.254.254: icmp_req=93 ttl=254 time=1.44 ms
64 bytes from 192.168.254.254: icmp_req=94 ttl=254 time=1.34 ms
From 192.168.254.9 icmp_seq=121 Destination Host Unreachable
From 192.168.254.9 icmp_seq=122 Destination Host Unreachable
From 192.168.254.9 icmp_seq=123 Destination Host Unreachable
From 192.168.254.9 icmp_seq=125 Destination Host Unreachable
From 192.168.254.9 icmp_seq=126 Destination Host Unreachable
From 192.168.254.9 icmp_seq=127 Destination Host Unreachable
From 192.168.254.9 icmp_seq=129 Destination Host Unreachable
From 192.168.254.9 icmp_seq=130 Destination Host Unreachable
From 192.168.254.9 icmp_seq=131 Destination Host Unreachable
From 192.168.254.9 icmp_seq=132 Destination Host Unreachable
From 192.168.254.9 icmp_seq=133 Destination Host Unreachable
From 192.168.254.9 icmp_seq=134 Destination Host Unreachable
From 192.168.254.9 icmp_seq=136 Destination Host Unreachable
From 192.168.254.9 icmp_seq=137 Destination Host Unreachable
From 192.168.254.9 icmp_seq=138 Destination Host Unreachable
From 192.168.254.9 icmp_seq=140 Destination Host Unreachable
From 192.168.254.9 icmp_seq=141 Destination Host Unreachable
From 192.168.254.9 icmp_seq=142 Destination Host Unreachable
From 192.168.254.9 icmp_seq=144 Destination Host Unreachable
From 192.168.254.9 icmp_seq=145 Destination Host Unreachable
From 192.168.254.9 icmp_seq=146 Destination Host Unreachable
64 bytes from 192.168.254.254: icmp_req=147 ttl=254 time=2008 ms
64 bytes from 192.168.254.254: icmp_req=148 ttl=254 time=1008 ms
64 bytes from 192.168.254.254: icmp_req=149 ttl=254 time=8.70 ms
64 bytes from 192.168.254.254: icmp_req=150 ttl=254 time=1.47 ms
64 bytes from 192.168.254.254: icmp_req=151 ttl=254 time=1.40 ms
64 bytes from 192.168.254.254: icmp_req=152 ttl=254 time=1.40 ms
64 bytes from 192.168.254.254: icmp_req=153 ttl=254 time=1.42 ms
64 bytes from 192.168.254.254: icmp_req=154 ttl=254 time=1.31 ms
64 bytes from 192.168.254.254: icmp_req=155 ttl=254 time=1.34 ms
64 bytes from 192.168.254.254: icmp_req=156 ttl=254 time=1.40 ms
64 bytes from 192.168.254.254: icmp_req=157 ttl=254 time=1.40 ms
64 bytes from 192.168.254.254: icmp_req=158 ttl=254 time=1.39 ms
64 bytes from 192.168.254.254: icmp_req=159 ttl=254 time=1.37 ms
64 bytes from 192.168.254.254: icmp_req=160 ttl=254 time=1.34 ms
64 bytes from 192.168.254.254: icmp_req=161 ttl=254 time=1.38 ms
64 bytes from 192.168.254.254: icmp_req=162 ttl=254 time=1.44 ms
64 bytes from 192.168.254.254: icmp_req=163 ttl=254 time=1.52 ms
64 bytes from 192.168.254.254: icmp_req=164 ttl=254 time=1.30 ms
64 bytes from 192.168.254.254: icmp_req=165 ttl=254 time=1.33 ms
64 bytes from 192.168.254.254: icmp_req=166 ttl=254 time=1.32 ms
64 bytes from 192.168.254.254: icmp_req=167 ttl=254 time=1.34 ms
64 bytes from 192.168.254.254: icmp_req=168 ttl=254 time=1.33 ms
64 bytes from 192.168.254.254: icmp_req=169 ttl=254 time=1.32 ms
64 bytes from 192.168.254.254: icmp_req=170 ttl=254 time=1.30 ms
64 bytes from 192.168.254.254: icmp_req=171 ttl=254 time=1.34 ms
64 bytes from 192.168.254.254: icmp_req=172 ttl=254 time=1.51 ms
64 bytes from 192.168.254.254: icmp_req=173 ttl=254 time=1.37 ms
64 bytes from 192.168.254.254: icmp_req=174 ttl=254 time=1.35 ms
64 bytes from 192.168.254.254: icmp_req=175 ttl=254 time=1.42 ms
64 bytes from 192.168.254.254: icmp_req=176 ttl=254 time=1.38 ms
64 bytes from 192.168.254.254: icmp_req=177 ttl=254 time=1.39 ms
64 bytes from 192.168.254.254: icmp_req=178 ttl=254 time=1.37 ms
64 bytes from 192.168.254.254: icmp_req=179 ttl=254 time=1.47 ms
64 bytes from 192.168.254.254: icmp_req=180 ttl=254 time=1.39 ms
64 bytes from 192.168.254.254: icmp_req=181 ttl=254 time=1.39 ms
64 bytes from 192.168.254.254: icmp_req=182 ttl=254 time=1.42 ms
64 bytes from 192.168.254.254: icmp_req=183 ttl=254 time=1.36 ms
64 bytes from 192.168.254.254: icmp_req=184 ttl=254 time=1.35 ms
64 bytes from 192.168.254.254: icmp_req=185 ttl=254 time=1.40 ms
64 bytes from 192.168.254.254: icmp_req=186 ttl=254 time=1.45 ms
64 bytes from 192.168.254.254: icmp_req=187 ttl=254 time=1.41 ms
64 bytes from 192.168.254.254: icmp_req=188 ttl=254 time=1.30 ms
64 bytes from 192.168.254.254: icmp_req=189 ttl=254 time=1.38 ms
64 bytes from 192.168.254.254: icmp_req=190 ttl=254 time=1.33 ms
64 bytes from 192.168.254.254: icmp_req=191 ttl=254 time=1.38 ms
64 bytes from 192.168.254.254: icmp_req=192 ttl=254 time=1.40 ms
64 bytes from 192.168.254.254: icmp_req=193 ttl=254 time=1.46 ms
64 bytes from 192.168.254.254: icmp_req=194 ttl=254 time=1.33 ms
64 bytes from 192.168.254.254: icmp_req=195 ttl=254 time=1.37 ms
64 bytes from 192.168.254.254: icmp_req=196 ttl=254 time=1.39 ms
64 bytes from 192.168.254.254: icmp_req=197 ttl=254 time=1.31 ms
^C
--- 192.168.254.254 ping statistics ---
203 packets transmitted, 86 received, +24 errors, 57% packet loss, time 202111ms
rtt min/avg/max/mdev = 1.304/42.313/2008.417/244.626 ms, pipe 3

Re: Mageia1 (64-bit) network problem

PostPosted: Jan 22nd, '12, 17:39
by dude67
Every once in a while I see this in the /var/log/messages file (I left it running).
Code: Select all
Jan 22 17:09:16 localhost kernel: r8169 0000:03:00.0: eth0: link up
Jan 22 17:10:01 localhost kernel: CIFS VFS: Server 192.168.254.100 has not responded in 300 seconds. Reconnecting...
Jan 22 17:10:01 localhost kernel: CIFS VFS: Server 192.168.254.100 has not responded in 300 seconds. Reconnecting...
Jan 22 17:10:06 localhost kernel: r8169 0000:03:00.0: eth0: link up


- EDIT - This .100 is one of my mounted network storage that the system is trying to connect.

Re: Mageia1 (64-bit) network problem

PostPosted: Jan 22nd, '12, 21:28
by martinw
Google found this http://forums.gentoo.org/viewtopic-t-885238-start-0.html which looks a bit like your problem. Can you post the output of
Code: Select all
lspci -nn | grep -i eth

(again run in a terminal as root), which should identify exactly which ethernet device you have.

Re: Mageia1 (64-bit) network problem

PostPosted: Jan 22nd, '12, 21:39
by CaptSilver
You can also try booting with pci=noacpi in grub to check to see if some sort of power saving mode is causing it.

Re: Mageia1 (64-bit) network problem

PostPosted: Jan 22nd, '12, 22:29
by dude67
OK, thanks martinw and CaptSilver. I'll check these tomorrow and post back.

Re: Mageia1 (64-bit) network problem

PostPosted: Jan 23rd, '12, 05:41
by dude67
Here it is.
Code: Select all
# lspci -nn | grep -i eth
03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 06)

Re: Mageia1 (64-bit) network problem

PostPosted: Jan 23rd, '12, 07:50
by dude67
I had a look at the instructions on the Gentoo and further on Ubuntu forums, but the solution seems quite tricky. First of all, I would need to build the new kernel driver, and I don't know if I know how to do that. Then if I manage to do that, I would have to do that every time the kernel is updated. And that would be real pain in the behind...

Maybe I should just go ahead and by me a new NIC. The problem is that I have only one PCI slot left in the motherboard. Then I would not have any room for any other cards left.

Re: Mageia1 (64-bit) network problem

PostPosted: Jan 23rd, '12, 17:27
by dude67
OK, managed to get the network to work properly. Now my problem is that it's not automatically loaded. How can I get that loaded automatically?

What did I do?
I downloaded the package from Realtek's pages:
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false#2
I removed the old package as instructed in ubutu forum:
Code: Select all
-> rmmod r8169
-> mv /lib/modules/`uname -r`/kernel/drivers/net/r8169.ko ~/r8169.ko.backup

Then I unpacked the files on my desktop:
Code: Select all
$ bzip2 -d r8168-8.009.00.tar.bz2
$ tar -xf r8168-8.009.00.tar
$ cd r8168-8.009.00

And as per the Readme file in the package, I ran the autorun file:
Code: Select all
# ./autorun.sh

Check old driver and unload it.
Build the module and install
DEPMOD 2.6.38.8-desktop-9.mga
load module r8168
Completed.


And that works like a charm. At least until I reboot the system and I will have to run that autorun again.
How can I make the module to run automatically?

Re: Mageia1 (64-bit) network problem

PostPosted: Jan 23rd, '12, 19:00
by ozky
You need to add it to file /etc/rc.d/rc.local.
Code: Select all
/path/to/myshell.sh

and boot your system and it will load it automatical on every boot.

Re: Mageia1 (64-bit) network problem

PostPosted: Jan 23rd, '12, 19:12
by ozky
You may need to set that script to executable first i think command it is
firs su root and that command
Code: Select all
chmod +x autorun.sh

Re: Mageia1 (64-bit) network problem

PostPosted: Jan 23rd, '12, 19:59
by dude67
Thanks ozky! That worked. :)

I had the Realtek package untarred to ~/Programmes/ -directory
Here's what I added to /etc/rc.d/rc.local file:
Code: Select all
cd /home/dude67/Programmes/r8168-8.027.00/
./autorun.sh