Re: NetworkManager doesn't work on eth0 anymore

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Marko Vojinovic píše v St 11. 03. 2009 v 18:59 +0100:
> After the latest updates:
> 
> Mar 10 14:10:11 Updated: 1:NetworkManager-glib-0.7.0.99-1.fc10.x86_64
> Mar 10 14:10:17 Updated: 1:NetworkManager-0.7.0.99-1.fc10.x86_64
> Mar 10 14:10:56 Updated: 1:NetworkManager-gnome-0.7.0.99-1.fc10.x86_64
> Mar 10 14:11:01 Updated: 1:NetworkManager-openvpn-0.7.0.99-1.fc10.x86_64
> Mar 10 14:11:05 Updated: 1:NetworkManager-vpnc-0.7.0.99-1.fc10.x86_64
> 
> NetworkManager stopped connecting via eth0. Wireless still works, wired
> worked before the updates, as "auto eth0" or something like that. Now
> there is no such option, and everything regarding eth0 in the
> configuration gui is greyed out.
> 
> When I plug in the network cable, /var/log/messages says that famous
> cryptic message that NM changed state from 2 to 3 and such, and that's it.
> No activity regarding dhcp or other usual stuff.
> 
> If I setup system-config-network to turn off "conntroled by NM" switch for
> eth0 and do a service network restart, the wired network starts to work
> correctly, so it is not a hardware problem.
> 
> My lspci -v says:
> 04:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8055 PCI-E
> Gigabit Ethernet Controller (rev 14)
>         Subsystem: Fujitsu Siemens Computers Device 110f
>         Flags: bus master, fast devsel, latency 0, IRQ 17
>         Memory at f8000000 (64-bit, non-prefetchable) [size=16K]
>         I/O ports at 3000 [size=256]
>         [virtual] Expansion ROM at f2000000 [disabled] [size=128K]
>         Capabilities: [48] Power Management version 3
>         Capabilities: [50] Vital Product Data <?>
>         Capabilities: [5c] Message Signalled Interrupts: Mask- 64bit+
> Count=1/1 Enable-
>         Capabilities: [e0] Express Legacy Endpoint, MSI 00
>         Capabilities: [100] Advanced Error Reporting
>                 UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt-
> RxOF- MalfTLP- ECRC- UnsupReq- ACSVoil-
>                 UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt-
> RxOF- MalfTLP- ECRC- UnsupReq- ACSVoil-
>                 UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt-
> RxOF+ MalfTLP+ ECRC- UnsupReq- ACSVoil-
>                 CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout-
> NonFatalErr+
>                 CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout-
> NonFatalErr+
>                 AERCap: First Error Pointer: 1f, GenCap- CGenEn- ChkCap-
> ChkEn-
>         Kernel driver in use: sky2
>         Kernel modules: sky2
> 
> Does anybody know the cause of the problem and a possible fix/workaround?
> Up to now NM worked flawlessly on my laptop for both wired and wireless
> and I find it more convenient than the old network service, but...

It is known problem, yum update (from today) fix it.

Pavel
-- 
Pavel Lisy <pali@xxxxxxxx>
T-MAPY spol. s r.o.

-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux