LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)
-   -   Fedora 16 Wired connection problem (https://www.linuxquestions.org/questions/linux-networking-3/fedora-16-wired-connection-problem-948406/)

antares7 06-04-2012 04:25 AM

Fedora 16 Wired connection problem
 
Helo LQ,

I have strange problem with my Fedora. The setup is Fedora 16 x64, KDE 4.7.4. My Network Manager displays the wired interface (p1p1) as 'cable unplugged'.

Sometimes I manage to connect by physically unplugging/plugging back on the lottery principle. I tried rebooting into Windows 7 - there is no problem with the connection. If I connect to different internal network - I have no problem, just the particular network, which has more complex routes embedded into it.

Code:

ip a l |grep -A1 p1p1
2: p1p1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
    link/ether f0:de:f1:a2:30:c3 brd ff:ff:ff:ff:ff:ff

ifup p1p1
Error: Connection activation failed: Device not managed by NetworkManager or unavailable

Here's some log outputs:
Code:

dmesg | grep Net
[  25.679675] NetworkManager[942]: NetworkManager[942]: <info> NetworkManager (version 0.9.2-1.fc16) is starting...
[  25.679680] NetworkManager[942]: NetworkManager[942]: <info> Read config file /etc/NetworkManager/NetworkManager.conf

Code:

dmesg | grep -A3 -B3 p1p1
[  22.723774] r8169 0000:02:00.0: irq 42 for MSI/MSI-X
[  22.724005] r8169 0000:02:00.0: eth0: RTL8168e/8111e at 0xffffc900050ee000, f0:de:f1:a2:30:c3, XID 0c200000 IRQ 42
[  22.724010] r8169 0000:02:00.0: eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[  22.746303] udevd[485]: renamed network interface eth0 to p1p1
[  22.775197] RPC: Registered named UNIX socket transport module.
[  22.775201] RPC: Registered udp transport module.
[  22.775202] RPC: Registered tcp transport module.
--
[  26.492384] Bluetooth: RFCOMM TTY layer initialized
[  26.492389] Bluetooth: RFCOMM socket layer initialized
[  26.492391] Bluetooth: RFCOMM ver 1.11
[  26.652983] r8169 0000:02:00.0: p1p1: link down
[  26.653001] r8169 0000:02:00.0: p1p1: link down
[  26.653378] ADDRCONF(NETDEV_UP): p1p1: link is not ready
[  26.655832] iwlwifi 0000:08:00.0: L1 Enabled; Disabling L0S
[  26.716620] iwlwifi 0000:08:00.0: L1 Enabled; Disabling L0S
[  26.777544] ADDRCONF(NETDEV_UP): wlan0: link is not ready
--
[  609.251127] cfg80211:  (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2300 mBm)
[  609.251129] cfg80211:  (5250000 KHz - 5290000 KHz @ 40000 KHz), (N/A, 2300 mBm)
[  609.251131] cfg80211:  (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 3000 mBm)
[  638.956632] r8169 0000:02:00.0: p1p1: link down
[  638.957030] ADDRCONF(NETDEV_UP): p1p1: link is not ready
[  639.891648] iwlwifi 0000:08:00.0: L1 Enabled; Disabling L0S
[  639.974813] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  642.208617] wlan0: authenticate with 54:75:d0:e3:a9:e9 (try 1)

output from /var/log/messages
Code:

Jun  4 10:55:40 antares-nb NetworkManager[932]:    ifcfg-rh: removed /etc/sysconfig/network-scripts/ifcfg-p1p1.
Jun  4 10:55:40 antares-nb NetworkManager[932]: NetworkManager[932]:    ifcfg-rh: removed /etc/sysconfig/network-scripts/ifcfg-p1p1.
Jun  4 10:55:40 antares-nb NetworkManager[932]:    ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-p1p1 ...
Jun  4 10:55:40 antares-nb NetworkManager[932]: NetworkManager[932]:    ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-p1p1 ...
Jun  4 10:55:40 antares-nb NetworkManager[932]:    ifcfg-rh:    read connection 'System p1p1'
Jun  4 10:55:40 antares-nb NetworkManager[932]: NetworkManager[932]:    ifcfg-rh:    read connection 'System p1p1'
----------
Jun  4 11:00:59 antares-nb NetworkManager[932]: <warn> connection /org/freedesktop/NetworkManager/Settings/6 failed to activate: (2) Device not managed by NetworkMan
ager or unavailable
Jun  4 11:00:59 antares-nb NetworkManager[932]: NetworkManager[932]: <warn> connection /org/freedesktop/NetworkManager/Settings/6 failed to activate: (2) Device not
managed by NetworkManager or unavailable
Jun  4 11:01:12 antares-nb NetworkManager[932]: <warn> connection /org/freedesktop/NetworkManager/Settings/6 failed to activate: (2) Device not managed by NetworkMan
ager or unavailable
Jun  4 11:01:12 antares-nb NetworkManager[932]: NetworkManager[932]: <warn> connection /org/freedesktop/NetworkManager/Settings/6 failed to activate: (2) Device not
managed by NetworkManager or unavailable
Jun  4 11:01:53 antares-nb NetworkManager[932]: NetworkManager[932]:    ifcfg-rh: updating /etc/sysconfig/network-scripts/ifcfg-p1p1
Jun  4 11:01:53 antares-nb NetworkManager[932]:    ifcfg-rh: updating /etc/sysconfig/network-scripts/ifcfg-p1p1
--------
Jun  4 11:13:27 antares-nb NetworkManager[942]: <info> (p1p1): carrier is OFF
Jun  4 11:13:27 antares-nb NetworkManager[942]: NetworkManager[942]: <info> (p1p1): carrier is OFF
Jun  4 11:13:27 antares-nb NetworkManager[942]: <info> (p1p1): new Ethernet device (driver: 'r8169' ifindex: 2)
Jun  4 11:13:27 antares-nb NetworkManager[942]: NetworkManager[942]: <info> (p1p1): new Ethernet device (driver: 'r8169' ifindex: 2)
Jun  4 11:13:27 antares-nb NetworkManager[942]: <info> (p1p1): exported as /org/freedesktop/NetworkManager/Devices/0
Jun  4 11:13:27 antares-nb NetworkManager[942]: NetworkManager[942]: <info> (p1p1): exported as /org/freedesktop/NetworkManager/Devices/0
Jun  4 11:13:27 antares-nb NetworkManager[942]: <info> (p1p1): now managed
Jun  4 11:13:27 antares-nb NetworkManager[942]: <info> (p1p1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Jun  4 11:13:27 antares-nb NetworkManager[942]: <info> (p1p1): bringing up device.
Jun  4 11:13:27 antares-nb NetworkManager[942]: NetworkManager[942]: <info> (p1p1): now managed
Jun  4 11:13:27 antares-nb NetworkManager[942]: NetworkManager[942]: <info> (p1p1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Jun  4 11:13:27 antares-nb NetworkManager[942]: NetworkManager[942]: <info> (p1p1): bringing up device.
----
Jun  4 11:23:10 antares-nb NetworkManager[942]: <info> disable requested (sleeping: no  enabled: yes)
Jun  4 11:23:10 antares-nb NetworkManager[942]: <info> sleeping or disabling...
Jun  4 11:23:10 antares-nb NetworkManager[942]: <info> (p1p1): now unmanaged
Jun  4 11:23:10 antares-nb NetworkManager[942]: NetworkManager[942]: <info> disable requested (sleeping: no  enabled: yes)
Jun  4 11:23:10 antares-nb NetworkManager[942]: NetworkManager[942]: <info> sleeping or disabling...
Jun  4 11:23:10 antares-nb NetworkManager[942]: NetworkManager[942]: <info> (p1p1): now unmanaged
Jun  4 11:23:10 antares-nb NetworkManager[942]: <info> (p1p1): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37]
Jun  4 11:23:10 antares-nb NetworkManager[942]: NetworkManager[942]: <info> (p1p1): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37]
Jun  4 11:23:10 antares-nb NetworkManager[942]: <info> (p1p1): cleaning up...
Jun  4 11:23:10 antares-nb NetworkManager[942]: NetworkManager[942]: <info> (p1p1): cleaning up...
Jun  4 11:23:10 antares-nb NetworkManager[942]: <info> (p1p1): taking down device.
Jun  4 11:23:10 antares-nb NetworkManager[942]: NetworkManager[942]: <info> (p1p1): taking down device.
----
Jun  4 11:23:40 antares-nb NetworkManager[942]: <info> (p1p1): now managed
Jun  4 11:23:40 antares-nb NetworkManager[942]: NetworkManager[942]: <info> (p1p1): now managed
Jun  4 11:23:40 antares-nb NetworkManager[942]: <info> (p1p1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Jun  4 11:23:40 antares-nb NetworkManager[942]: NetworkManager[942]: <info> (p1p1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Jun  4 11:23:40 antares-nb NetworkManager[942]: <info> (p1p1): bringing up device.
Jun  4 11:23:40 antares-nb NetworkManager[942]: NetworkManager[942]: <info> (p1p1): bringing up device.
Jun  4 11:23:40 antares-nb NetworkManager[942]: <info> (p1p1): preparing device.
Jun  4 11:23:40 antares-nb NetworkManager[942]: <info> (p1p1): deactivating device (reason 'managed') [2]
Jun  4 11:23:40 antares-nb NetworkManager[942]: NetworkManager[942]: <info> (p1p1): preparing device.
Jun  4 11:23:40 antares-nb NetworkManager[942]: NetworkManager[942]: <info> (p1p1): deactivating device (reason 'managed') [2]
Jun  4 11:23:40 antares-nb kernel: [  638.956632] r8169 0000:02:00.0: p1p1: link down
Jun  4 11:23:40 antares-nb kernel: [  638.957030] ADDRCONF(NETDEV_UP): p1p1: link is not ready

Code:

lspci |grep -i net
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
08:00.0 Network controller: Intel Corporation Centrino Wireless-N 1000

Code:

cat /etc/sysconfig/network-scripts/ifcfg-p1p1
DEVICE="p1p1"
NAME="System p1p1"
BOOTPROTO=dhcp
ONBOOT="yes"
NM_CONTROLLED="yes"
TYPE=Ethernet
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
UUID=46e26279-f69b-daf5-1b79-d03677b7178d
PEERDNS=yes
PEERROUTES=yes
USERS=antares

I suspect that there could be a conflict between the KDE network manager, and the linux's. The WiFi is working fine. But the wired network interface is displayed incorrectly "unplugged".

I would be grateful if you can point me at things I need to investigate or any help provided. Tell me if I need to post other log/configuration outputs.

Thank you in advance!

Didier Spaier 06-05-2012 02:18 PM

I would try to do a manual connection, using "ifconfig <iface name> up" to bring up the interface if it doesn't show in "ifconfig" output, then an DHCP client to do the connection (I use dhcpcd on Slackware but maybe it's not available on Fedora; then try another one like dhclient).
The "route" command will tell you if that worked or not.

nini09 06-05-2012 02:20 PM

It look like your NIC card has problem. Replacing it with another one and test again.

antares7 06-07-2012 05:23 AM

Sorry for the late reply.

I was not able to change the NIC, because it is a laptop. Trying to work with the interface with ifup, ifdown was not possible, it showed me error message "device not controlled by NetworkManager or unavailable" (or something similar).

I was able to fix the problem. It seems for some reason my Fedora had enabled r8169 module in modprobe. I downloaded and installed the correct drivers from the Realtek website. Although - after restart the old modules were again enabled, so I had to put r8169 in the /etc/modprobe.d/blacklist.conf . After this I installed the drivers again, following the instructions in the README file.

I hope this helps someone else. The topic can be considered as solved now.


All times are GMT -5. The time now is 03:47 AM.