Fedora Linux Support Community & Resources Center
  #1  
Old 26th April 2012, 07:50 PM
AndyPen Offline
Registered User
 
Join Date: Jul 2010
Posts: 5
linuxsafari
ne2k-pci cable unplugged could't get carrier state

Since doing a yum update to NetworkManager 0.9.4 I can't connect to a wired network. I believe NetworkManager reports couldn't get carrier state and then does not try to start networking. Previously NetworkManager would report driver ne2k-pci does not support carrier detection and go on to bring up the device. If I could get networking going I could post some logs.

I tried a yum downgrade on NetworkManager but that failed as there is no networking.

---------- Post added at 07:50 PM ---------- Previous post was at 05:07 PM ----------

A temporary fix is as follows:
sudo kill <pid_of_NetworkManager>
sudo dhclient <network_adapter_e.g. p5p1>
Reply With Quote
  #2  
Old 26th April 2012, 08:50 PM
stevea Online
Registered User
 
Join Date: Apr 2006
Location: Ohio, USA
Posts: 8,562
linuxfirefox
Re: ne2k-pci cable unplugged could't get carrier state

If your workaround actually works then *maybe* the ne2k doesn't have it's carrier detect up in time after boot.

Does it work if you just restart NM service or manually tell NM to connect ?
You may want to use mii-diag and mii-tool to dump or watch the carrier state.
__________________
None are more hopelessly enslaved than those who falsely believe they are free.
Johann Wolfgang von Goethe
Reply With Quote
  #3  
Old 26th April 2012, 09:39 PM
AndyPen Offline
Registered User
 
Join Date: Jul 2010
Posts: 5
linuxchrome
Re: ne2k-pci cable unplugged could't get carrier state

I don't think it is the ne2k not bringing up it's carrier in time because it has always worked fine in F16 until the latest update to NetworkManager (NetworkManager-0.9.4-2.git20120403.fc16.i686). I also understand that NM should detect networks becoming available so if I physically unplug the network cable and then plug it back in, NM should detect this and bring networking up, it doesn't. Also looking at some log files from before the update, NM would report "Apr 22 13:09:18 trinity NetworkManager[830]: <info> (p5p1): driver 'ne2k-pci' does not support carrier detection." but then go on to bring up networking. After the upgrade to the latest version it says:
Apr 26 19:21:57 trinity NetworkManager[842]: <warn> (p5p1): couldn't get carrier state: (-1) unknown
Apr 26 19:21:57 trinity NetworkManager[842]: <info> (p5p1): carrier now OFF (device state 20, deferring action for 4 seconds)
Apr 26 19:21:57 trinity NetworkManager[842]: <info> (p5p1): preparing device.
Apr 26 19:21:57 trinity NetworkManager[842]: <info> (p5p1): deactivating device (reason 'managed') [2]

I have filed a bug (816719) in the hope that the behaviour will be reverted to the previous version of NM. I have not downgraded NM in case extra info is required (and I can get networking going now - although a bit mandrolic). If you would like specific information, let me know.
Reply With Quote
Reply

Tags
cable, carrier, couldt, ne2kpci, state, unplugged

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

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 On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Cable unplugged when fedora 16 boots up chansanle Servers & Networking 3 6th April 2012 02:01 PM
F16: Wired Connection showing " Cable Unplugged error" rrampage Servers & Networking 3 2nd April 2012 05:21 AM
cable unplugged on first boot Martin Sebor Servers & Networking 4 24th March 2012 04:12 PM
unplugged cable message (plugged cable!) verzuiul Servers & Networking 3 2nd September 2007 06:12 PM


Current GMT-time: 04:05 (Friday, 25-04-2014)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat