Bug 743755

Summary: Marvell Yukon Optima 88E8059 - no link detected
Product: [Fedora] Fedora Reporter: Xavier FERAUD <xasoft>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 15CC: dcbw, jklimes
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-07 16:05:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
result of dmesg command
none
file /var/log/messages none

Description Xavier FERAUD 2011-10-05 21:53:25 UTC
Description of problem:
On my laptop SONY VPCEA2S1E with ethernet PCI Card "Marvell Yukon Optima 88E8059" since 2 weeks (date of my last update) the ethernet interface do not work. When I try to activate the interface I have the following message "Définition des informations IP pour eth0. échoué. Aucun lien n'a été trouvé. Vérifier le câble ?" = No link, check the cable ?

Version-Release number of selected component (if applicable):
Fedora 15 - (2.6.40.4-5.fc15.x86_64 #1 SMP Tue Aug 30 14:38:32 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux)

How reproducible:
Install Fedora 15 on Sony laptop VPCEA2S1E
2 week ago, the problem appears on Fedora 14. I have think that the problem will be solved by an update to fedora 15, I have updated to Fedora 15 (using the wlan interface - another network card).
Since fedora 15 installation, no solution to activate Ethernet interface. I have tried all command found in wiki or another blog (ethtool, service NetworkManager star/stop, chkconfig NetworkManager on/off, deactivate NetworkManager, add biosdevname=0 ...)

Steps to Reproduce:
1.With NetworkManager activated and ethernet interface eth0 managed by NetworkManager
[root@dxa4 ~]# service network restart
Restarting network (via systemctl):  Job failed. See system logs and 'systemctl status' for details.
                                                           [ÉCHOUÉ]

2.With NetworkManager activated and ethernet interface eth0 not manager by NetworkManager
2.1 The command "service network restart" provide same result
2.2 [root@dxa4 ~]# ifup eth0

Définition des informations IP pour eth0. échoué. Aucun lien n'a été trouvé. Vérifier le câble ?
3. With NetworkManager deactivated = same result for ifup command as in point 2.2
  
Actual results:
No way to find solution. I have noted that support for this chiset was added with "Bug 585633 - Marvel Yukon 88E8059 NIC not supported" but for me i'm totally blocked and limited to wifi connection, not very secure...

Expected results:
Retreive my ethernet connexion and all benefit (speed and security)

Additional info:
Extract of /var/log/messages when the command service network restart provide error message:
Oct  5 23:47:18 dxa4 NetworkManager[3881]: <warn> connection /org/freedesktop/NetworkManager/Settings/0 failed to activate: (2) Device not managed by NetworkManager or unavailable
Oct  5 23:47:18 dxa4 NetworkManager[3881]: <info> (wlan0): disconnecting for new activation request.
Oct  5 23:47:18 dxa4 NetworkManager[3881]: <info> (wlan0): device state change: activated -> disconnected (reason 'none') [100 30 0]
Oct  5 23:47:18 dxa4 NetworkManager[3881]: <info> (wlan0): deactivating device (reason 'none') [0]
Oct  5 23:47:18 dxa4 NetworkManager[3881]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 3915
Oct  5 23:47:18 dxa4 kernel: [ 2365.304324] cfg80211: Calling CRDA to update world regulatory domain
Oct  5 23:47:18 dxa4 avahi-daemon[994]: Withdrawing address record for 192.168.1.242 on wlan0.
Oct  5 23:47:18 dxa4 avahi-daemon[994]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.242.
Oct  5 23:47:18 dxa4 avahi-daemon[994]: Interface wlan0.IPv4 no longer relevant for mDNS.
Oct  5 23:47:18 dxa4 NetworkManager[3881]: <info> Activation (wlan0) starting connection 'System dwi (wlan0)'
Oct  5 23:47:18 dxa4 NetworkManager[3881]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Oct  5 23:47:18 dxa4 NetworkManager[3881]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Oct  5 23:47:18 dxa4 NetworkManager[3881]: <info> (wlan0): supplicant interface state: completed -> disconnected
Oct  5 23:47:18 dxa4 NetworkManager[3881]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Oct  5 23:47:18 dxa4 dbus: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Oct  5 23:47:18 dxa4 NetworkManager[3881]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Oct  5 23:47:18 dxa4 NetworkManager[3881]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Oct  5 23:47:18 dxa4 NetworkManager[3881]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Oct  5 23:47:18 dxa4 NetworkManager[3881]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Oct  5 23:47:18 dxa4 NetworkManager[3881]: <info> Activation (wlan0/wireless): access point 'System dwi (wlan0)' has security, but secrets are required.
Oct  5 23:47:18 dxa4 NetworkManager[3881]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Oct  5 23:47:18 dxa4 NetworkManager[3881]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Oct  5 23:47:18 dxa4 NetworkManager[3881]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Oct  5 23:47:18 dxa4 NetworkManager[3881]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Oct  5 23:47:18 dxa4 NetworkManager[3881]: <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Oct  5 23:47:18 dxa4 NetworkManager[3881]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Oct  5 23:47:18 dxa4 NetworkManager[3881]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Oct  5 23:47:18 dxa4 NetworkManager[3881]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Oct  5 23:47:18 dxa4 NetworkManager[3881]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Oct  5 23:47:18 dxa4 NetworkManager[3881]: <info> Activation (wlan0/wireless): connection 'System dwi (wlan0)' has security, and secrets exist.  No new secrets needed.
Oct  5 23:47:18 dxa4 NetworkManager[3881]: <info> Config: added 'ssid' value 'dwi'
Oct  5 23:47:18 dxa4 NetworkManager[3881]: <info> Config: added 'scan_ssid' value '1'
Oct  5 23:47:18 dxa4 NetworkManager[3881]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Oct  5 23:47:18 dxa4 NetworkManager[3881]: <info> Config: added 'psk' value '<omitted>'
Oct  5 23:47:18 dxa4 NetworkManager[3881]: <info> Config: added 'proto' value 'WPA RSN'
Oct  5 23:47:18 dxa4 NetworkManager[3881]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Oct  5 23:47:18 dxa4 NetworkManager[3881]: <info> Config: set interface ap_scan to 1
Oct  5 23:47:18 dxa4 dbus: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Oct  5 23:47:18 dxa4 NetworkManager[3881]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Oct  5 23:47:18 dxa4 kernel: [ 2365.380009] cfg80211: World regulatory domain updated:
Oct  5 23:47:18 dxa4 kernel: [ 2365.380014] cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Oct  5 23:47:18 dxa4 kernel: [ 2365.380018] cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Oct  5 23:47:18 dxa4 kernel: [ 2365.380021] cfg80211:     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Oct  5 23:47:18 dxa4 kernel: [ 2365.380024] cfg80211:     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Oct  5 23:47:18 dxa4 kernel: [ 2365.380027] cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Oct  5 23:47:18 dxa4 kernel: [ 2365.380030] cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Oct  5 23:47:19 dxa4 NetworkManager[3881]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Oct  5 23:47:19 dxa4 NetworkManager[3881]: <info> (wlan0): supplicant interface state: authenticating -> associating
Oct  5 23:47:19 dxa4 NetworkManager[3881]: <info> (wlan0): supplicant interface state: associating -> 4-way handshake
Oct  5 23:47:19 dxa4 NetworkManager[3881]: <info> (wlan0): supplicant interface state: 4-way handshake -> group handshake
Oct  5 23:47:19 dxa4 NetworkManager[3881]: <info> (wlan0): supplicant interface state: group handshake -> completed
Oct  5 23:47:19 dxa4 NetworkManager[3881]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'dwi'.
Oct  5 23:47:19 dxa4 NetworkManager[3881]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Oct  5 23:47:19 dxa4 NetworkManager[3881]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Oct  5 23:47:19 dxa4 NetworkManager[3881]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
Oct  5 23:47:19 dxa4 NetworkManager[3881]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Oct  5 23:47:19 dxa4 NetworkManager[3881]: <info> dhclient started with pid 4311
Oct  5 23:47:19 dxa4 NetworkManager[3881]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Oct  5 23:47:19 dxa4 dhclient[4311]: Internet Systems Consortium DHCP Client 4.2.1-P1
Oct  5 23:47:19 dxa4 dhclient[4311]: Copyright 2004-2011 Internet Systems Consortium.
Oct  5 23:47:19 dxa4 dhclient[4311]: All rights reserved.
Oct  5 23:47:19 dxa4 dhclient[4311]: For info, please visit https://www.isc.org/software/dhcp/
Oct  5 23:47:19 dxa4 dhclient[4311]: 
Oct  5 23:47:19 dxa4 NetworkManager[3881]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
Oct  5 23:47:19 dxa4 dhclient[4311]: Listening on LPF/wlan0/78:dd:08:e4:b5:ec
Oct  5 23:47:19 dxa4 dhclient[4311]: Sending on   LPF/wlan0/78:dd:08:e4:b5:ec
Oct  5 23:47:19 dxa4 dhclient[4311]: Sending on   Socket/fallback
Oct  5 23:47:20 dxa4 ntpd[987]: Deleting interface #10 wlan0, 192.168.1.242#123, interface stats: received=8, sent=8, dropped=0, active_time=79 secs
Oct  5 23:47:20 dxa4 ntpd[987]: 194.57.169.1 interface 192.168.1.242 -> (none)
Oct  5 23:47:20 dxa4 ntpd[987]: 88.191.108.178 interface 192.168.1.242 -> (none)
Oct  5 23:47:20 dxa4 ntpd[987]: 213.251.153.35 interface 192.168.1.242 -> (none)
Oct  5 23:47:20 dxa4 ntpd[987]: 193.55.167.2 interface 192.168.1.242 -> (none)
Oct  5 23:47:20 dxa4 ntpd[987]: peers refreshed
Oct  5 23:47:20 dxa4 dhclient[4311]: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Oct  5 23:47:20 dxa4 dhclient[4311]: DHCPACK from 192.168.1.1
Oct  5 23:47:20 dxa4 dhclient[4311]: bound to 192.168.1.242 -- renewal in 18079 seconds.
Oct  5 23:47:20 dxa4 NetworkManager[3881]: <info> (wlan0): DHCPv4 state changed preinit -> reboot
Oct  5 23:47:20 dxa4 NetworkManager[3881]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) scheduled...
Oct  5 23:47:20 dxa4 NetworkManager[3881]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) started...
Oct  5 23:47:20 dxa4 NetworkManager[3881]: <info>   address 192.168.1.242
Oct  5 23:47:20 dxa4 NetworkManager[3881]: <info>   prefix 24 (255.255.255.0)
Oct  5 23:47:20 dxa4 NetworkManager[3881]: <info>   gateway 192.168.1.1
Oct  5 23:47:20 dxa4 NetworkManager[3881]: <info>   hostname 'dxa4'
Oct  5 23:47:20 dxa4 NetworkManager[3881]: <info>   nameserver '192.168.1.1'
Oct  5 23:47:20 dxa4 NetworkManager[3881]: <info>   domain name 'lan'
Oct  5 23:47:20 dxa4 NetworkManager[3881]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
Oct  5 23:47:20 dxa4 NetworkManager[3881]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) complete.
Oct  5 23:47:20 dxa4 NetworkManager[3881]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
Oct  5 23:47:20 dxa4 avahi-daemon[994]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.242.
Oct  5 23:47:20 dxa4 avahi-daemon[994]: New relevant interface wlan0.IPv4 for mDNS.
Oct  5 23:47:20 dxa4 avahi-daemon[994]: Registering new address record for 192.168.1.242 on wlan0.IPv4.
Oct  5 23:47:21 dxa4 NetworkManager[3881]: <info> (wlan0): device state change: ip-config -> activated (reason 'none') [70 100 0]
Oct  5 23:47:21 dxa4 NetworkManager[3881]: <info> Policy set 'System dwi (wlan0)' (wlan0) as default for IPv4 routing and DNS.
Oct  5 23:47:21 dxa4 NetworkManager[3881]: <info> Activation (wlan0) successful, device activated.
Oct  5 23:47:21 dxa4 NetworkManager[3881]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
Oct  5 23:47:21 dxa4 systemd[1]: network.service: control process exited, code=exited status=1
Oct  5 23:47:21 dxa4 systemd[1]: Unit network.service entered failed state.
Oct  5 23:47:22 dxa4 ntpd[987]: Listen normally on 12 wlan0 192.168.1.242 UDP 123
Oct  5 23:47:22 dxa4 ntpd[987]: peers refreshed

Comment 1 Xavier FERAUD 2011-10-06 06:17:07 UTC
I have forget some precision:
This laptop have multiboot.
The same ethernet works fine when I boot it on Windows Seven.

Comment 2 Jirka Klimes 2011-10-06 11:43:02 UTC
Well, it appears there's a problem with the ethernet driver. Please provide the following information:
1) lspci -vnn | grep -A 15 Marvell
2) ifconfig -a
3) /var/log/messages file
4) output of dmesg command

Comment 3 Xavier FERAUD 2011-10-07 08:46:35 UTC
Thanks for your help.

[root@dxa4 ~]# lspci -vnn | grep -A 15 Marvell
04:00.0 Ethernet controller [0200]: Marvell Technology Group Ltd. Yukon Optima 88E8059 [PCIe Gigabit Ethernet Controller with AVB] [11ab:4381] (rev 11)
	Subsystem: Sony Corporation Device [104d:9071]
	Flags: bus master, fast devsel, latency 0, IRQ 43
	Memory at f2220000 (64-bit, non-prefetchable) [size=16K]
	I/O ports at a000 [size=256]
	Expansion ROM at f2200000 [disabled] [size=128K]
	Capabilities: [48] Power Management version 3
	Capabilities: [5c] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [c0] Express Legacy Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [130] Device Serial Number 49-09-5f-ff-ff-49-42-54
	Kernel driver in use: sky2
	Kernel modules: sky2

3f:00.0 Host bridge [0600]: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers [8086:2c62] (rev 02)
	Subsystem: Sony Corporation Device [104d:9071]

[root@dxa4 ~]# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 54:42:49:5F:09:49  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interruption:18 

lo        Link encap:Boucle locale  
          inet adr:127.0.0.1  Masque:255.0.0.0
          adr inet6: ::1/128 Scope:Hôte
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:510 errors:0 dropped:0 overruns:0 frame:0
          TX packets:510 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:0 
          RX bytes:41748 (40.7 KiB)  TX bytes:41748 (40.7 KiB)

wlan0     Link encap:Ethernet  HWaddr 78:DD:08:E4:B5:EC  
          inet adr:192.168.1.242  Bcast:192.168.1.255  Masque:255.255.255.0
          adr inet6: fe80::7add:8ff:fee4:b5ec/64 Scope:Lien
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:12717 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12339 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:1000 
          RX bytes:12385048 (11.8 MiB)  TX bytes:5672823 (5.4 MiB)

Other informations are in attachments

Comment 4 Xavier FERAUD 2011-10-07 08:47:27 UTC
Created attachment 526845 [details]
result of dmesg  command

Comment 5 Xavier FERAUD 2011-10-07 08:48:39 UTC
Created attachment 526846 [details]
file /var/log/messages

Comment 6 Jirka Klimes 2011-10-18 08:56:01 UTC
Oct  7 10:05:43 dxa4 NetworkManager[972]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
Oct  7 10:05:43 dxa4 NetworkManager[972]:    ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-p8p1 ... 
Oct  7 10:05:43 dxa4 NetworkManager[972]:    ifcfg-rh:     read connection 'System p8p1'
Oct  7 10:05:43 dxa4 NetworkManager[972]:    ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-lo ... 
Oct  7 10:05:43 dxa4 NetworkManager[972]:    ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-wlan0 ... 
Oct  7 10:05:43 dxa4 NetworkManager[972]:    ifcfg-rh:     read connection 'System dwi (wlan0)'
Oct  7 10:05:43 dxa4 NetworkManager[972]:    ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-eth0 ... 
Oct  7 10:05:43 dxa4 NetworkManager[972]:    ifcfg-rh:     read connection 'System eth0'
Oct  7 10:05:43 dxa4 NetworkManager[972]:    ifcfg-rh: Ignoring connection 'System eth0' and its device due to NM_CONTROLLED/BRIDGE/VLAN.

According to logs, NM doesn't manage your ethernet card, because it is said thus in /etc/sysconfig/network-scripts/ifcfg-eth0. The file probably contains NM_CONTROLLED=no or something.

Please paste here these files:
/etc/sysconfig/network-scripts/ifcfg-p8p1
/etc/sysconfig/network-scripts/ifcfg-eth0

Solution for your problem:
Set NM_CONTROLLED to "yes", or maybe just remove /etc/sysconfig/network-scripts/ifcfg-eth0  (/etc/sysconfig/network-scripts/ifcfg-p8p1 is sufficient for configuration).

Tip:
You can check status of the devices by 'nmcli dev' and active connection via 'nmcli con status'. Also nm-tool shows valuable information about devices.

Comment 7 Jirka Klimes 2011-10-18 09:03:16 UTC
Not relating to the ethernet problem, I've encountered in the logs several issues of your system:
1) dmesg says
 22.204841] systemd[1]: /usr appears to be on a different file system than /. This is not supported anymore. Some things will probably break (sometimes even silently) in mysterious ways. Consult http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken for more information.

2) there is a radeon driver crash
Oct  4 20:51:38 dxa4 kernel: [30486.234805] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec
Oct  4 20:51:38 dxa4 kernel: [30486.234812] ------------[ cut here ]------------
Oct  4 20:51:38 dxa4 kernel: [30486.234873] WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:267 radeon_fence_wait+0x296/0x33d [radeon]()
Oct  4 20:51:38 dxa4 kernel: [30486.234879] Hardware name: VPCEA2S1E
Oct  4 20:51:38 dxa4 kernel: [30486.234883] GPU lockup (waiting for 0x000F48DF last fence id 0x000F48D8)
Oct  4 20:51:38 dxa4 kernel: [30486.234887] Modules linked in: tcp_lp rfcomm btusb fuse ppdev parport_pc lp parport sunrpc cpufreq_ondemand bnep acpi_cpufreq mperf bluetooth ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack snd_hda_codec_hdmi microcode snd_hda_codec_realtek arc4 uvcvideo videodev media v4l2_compat_ioctl32 joydev snd_hda_intel snd_hda_codec ath9k snd_hwdep snd_seq snd_seq_device iTCO_wdt snd_pcm mac80211 ath9k_common ath9k_hw i2c_i801 ath iTCO_vendor_support sky2 cfg80211 snd_timer snd soundcore snd_page_alloc sony_laptop rfkill ipv6 xts gf128mul dm_crypt sdhci_pci sdhci mmc_core video radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core [last unloaded: scsi_wait_scan]
Oct  4 20:51:38 dxa4 kernel: [30486.234949] Pid: 1330, comm: Xorg Not tainted 2.6.40.4-5.fc15.x86_64 #1
Oct  4 20:51:38 dxa4 kernel: [30486.234952] Call Trace:
Oct  4 20:51:38 dxa4 kernel: [30486.234962]  [<ffffffff81054c8e>] warn_slowpath_common+0x83/0x9b
Oct  4 20:51:38 dxa4 kernel: [30486.234966]  [<ffffffff81054d49>] warn_slowpath_fmt+0x46/0x48
Oct  4 20:51:38 dxa4 kernel: [30486.234988]  [<ffffffffa00bee3d>] ? r600_gpu_is_lockup+0xbd/0xc6 [radeon]
Oct  4 20:51:38 dxa4 kernel: [30486.235004]  [<ffffffffa0098dcd>] radeon_fence_wait+0x296/0x33d [radeon]
Oct  4 20:51:38 dxa4 kernel: [30486.235009]  [<ffffffff81070566>] ? remove_wait_queue+0x3a/0x3a
Oct  4 20:51:38 dxa4 kernel: [30486.235025]  [<ffffffffa00993c1>] radeon_sync_obj_wait+0x11/0x13 [radeon]
Oct  4 20:51:38 dxa4 kernel: [30486.235033]  [<ffffffffa0060642>] ttm_bo_wait+0xbf/0x17a [ttm]
Oct  4 20:51:38 dxa4 kernel: [30486.235039]  [<ffffffffa0061075>] ? ttm_bo_list_ref_sub+0x29/0x2b [ttm]
Oct  4 20:51:38 dxa4 kernel: [30486.235058]  [<ffffffffa00a9dcb>] radeon_bo_wait+0x7b/0x9f [radeon]
Oct  4 20:51:38 dxa4 kernel: [30486.235078]  [<ffffffffa00aa32d>] radeon_gem_wait_idle_ioctl+0x3d/0x70 [radeon]
Oct  4 20:51:38 dxa4 kernel: [30486.235090]  [<ffffffffa00157f7>] drm_ioctl+0x29e/0x37b [drm]
Oct  4 20:51:38 dxa4 kernel: [30486.235109]  [<ffffffffa00aa2f0>] ? radeon_gem_busy_ioctl+0x86/0x86 [radeon]
Oct  4 20:51:38 dxa4 kernel: [30486.235114]  [<ffffffff811f649c>] ? inode_has_perm+0x32/0x34
Oct  4 20:51:38 dxa4 kernel: [30486.235117]  [<ffffffff811f6545>] ? file_has_perm+0xa7/0xc9
Oct  4 20:51:38 dxa4 kernel: [30486.235121]  [<ffffffff81134f0a>] do_vfs_ioctl+0x460/0x4a1
Oct  4 20:51:38 dxa4 kernel: [30486.235124]  [<ffffffff81134fa1>] sys_ioctl+0x56/0x79
Oct  4 20:51:38 dxa4 kernel: [30486.235129]  [<ffffffff8148e842>] system_call_fastpath+0x16/0x1b
Oct  4 20:51:38 dxa4 kernel: [30486.235132] ---[ end trace f13de336a5805a7a ]---

3) there are problems with gdm
Oct  4 20:54:28 dxa4 gdm-simple-greeter[1579]: Gtk-WARNING: gtkwidget.c:6796: widget not within a GtkWindow
Oct  4 20:54:28 dxa4 gdm-simple-greeter[1579]: Gtk-WARNING: gtk_widget_size_allocate(): attempt to allocate widget with width -47 and height -47
Oct  4 20:54:28 dxa4 gdm-simple-greeter[1579]: Gtk-CRITICAL: gtk_widget_get_mapped: assertion `GTK_IS_WIDGET (widget)' failed
Oct  4 20:54:28 dxa4 gdm-simple-greeter[1579]: GLib-GObject-WARNING: invalid (NULL) pointer instance
Oct  4 20:54:28 dxa4 gdm-simple-greeter[1579]: GLib-GObject-CRITICAL: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
Oct  4 20:54:28 dxa4 gdm-simple-greeter[1579]: Gtk-CRITICAL: gtk_widget_get_mapped: assertion `GTK_IS_WIDGET (widget)' failed
Oct  4 20:54:28 dxa4 gdm-simple-greeter[1579]: GLib-GObject-WARNING: invalid (NULL) pointer instance
Oct  4 20:54:28 dxa4 gdm-simple-greeter[1579]: GLib-GObject-CRITICAL: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

Consider updating your system to fix those problems.

Comment 8 Xavier FERAUD 2011-10-18 20:22:22 UTC
(In reply to comment #6)
> Oct  7 10:05:43 dxa4 NetworkManager[972]: <info> Loaded plugin keyfile: (c)
> 2007 - 2010 Red Hat, Inc.  To report bugs please use the NetworkManager mailing
> list.
> Oct  7 10:05:43 dxa4 NetworkManager[972]:    ifcfg-rh: parsing
> /etc/sysconfig/network-scripts/ifcfg-p8p1 ... 
> Oct  7 10:05:43 dxa4 NetworkManager[972]:    ifcfg-rh:     read connection
> 'System p8p1'
> Oct  7 10:05:43 dxa4 NetworkManager[972]:    ifcfg-rh: parsing
> /etc/sysconfig/network-scripts/ifcfg-lo ... 
> Oct  7 10:05:43 dxa4 NetworkManager[972]:    ifcfg-rh: parsing
> /etc/sysconfig/network-scripts/ifcfg-wlan0 ... 
> Oct  7 10:05:43 dxa4 NetworkManager[972]:    ifcfg-rh:     read connection
> 'System dwi (wlan0)'
> Oct  7 10:05:43 dxa4 NetworkManager[972]:    ifcfg-rh: parsing
> /etc/sysconfig/network-scripts/ifcfg-eth0 ... 
> Oct  7 10:05:43 dxa4 NetworkManager[972]:    ifcfg-rh:     read connection
> 'System eth0'
> Oct  7 10:05:43 dxa4 NetworkManager[972]:    ifcfg-rh: Ignoring connection
> 'System eth0' and its device due to NM_CONTROLLED/BRIDGE/VLAN.
> 
> According to logs, NM doesn't manage your ethernet card, because it is said
> thus in /etc/sysconfig/network-scripts/ifcfg-eth0. The file probably contains
> NM_CONTROLLED=no or something.
> 
> Please paste here these files:
> /etc/sysconfig/network-scripts/ifcfg-p8p1
DEVICE=p8p1
ONBOOT=yes
NM_CONTROLLED=yes
TYPE=Ethernet
BOOTPROTO=dhcp
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
NAME="System p8p1"
UUID=d848fc00-d599-ef06-78c8-608a5e6fa354
HWADDR=54:42:49:5f:09:49
PEERDNS=yes
PEERROUTES=yes
USERCTL=no

> /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
ONBOOT=yes
NM_CONTROLLED=yes
TYPE=Ethernet
BOOTPROTO=dhcp
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
NAME="System eth0"
UUID=d848fc00-d599-ef06-78c8-608a5e6fa354
HWADDR=54:42:49:5f:09:49
PEERDNS=yes
PEERROUTES=yes
USERCTL=no

I have chnaged NM_CONTROLLED value from "no" to "yes"

> 
> Solution for your problem:
> Set NM_CONTROLLED to "yes", or maybe just remove
> /etc/sysconfig/network-scripts/ifcfg-eth0 
> (/etc/sysconfig/network-scripts/ifcfg-p8p1 is sufficient for configuration).
> 
> Tip:
> You can check status of the devices by 'nmcli dev' and active connection via
> 'nmcli con status'. Also nm-tool shows valuable information about devices.

Comment 9 Xavier FERAUD 2011-10-18 21:02:40 UTC
I not sure that to remove ifcfg-eth0 file because I have added option "biosdevname=0" in kernel option in Grub.

I have tried command "nmcli con" that gives following result
[xavier@dxa4 dxa4]$ nmcli con
NOM                       UUID                                   TYPE              TIMESTAMP-REAL                    
System dwi (wlan0)        113f1f4e-535e-c25b-8849-2c6f770a6501   802-11-wireless   mar. 18 oct. 2011 22:21:53 CEST   
System p8p1               d848fc00-d599-ef06-78c8-608a5e6fa354   802-3-ethernet    jamais                            
System eth0               d848fc00-d599-ef06-78c8-608a5e6fa354   802-3-ethernet    jamais                            

and command "nmcli con up id "System eth0"" gives following result
Erreur: L'activation de la connexion a échoué: Device not managed by NetworkManager or unavailable

and wired interface is always seen as unpluged in Network Manager GUI

Comment 10 Jirka Klimes 2011-10-19 08:29:13 UTC
(In reply to comment #8)
> > /etc/sysconfig/network-scripts/ifcfg-eth0
> DEVICE=eth0
> ONBOOT=yes
> NM_CONTROLLED=yes
> TYPE=Ethernet
> BOOTPROTO=dhcp
> DEFROUTE=yes
> IPV4_FAILURE_FATAL=yes
> IPV6INIT=no
> NAME="System eth0"
> UUID=d848fc00-d599-ef06-78c8-608a5e6fa354
> HWADDR=54:42:49:5f:09:49
> PEERDNS=yes
> PEERROUTES=yes
> USERCTL=no
> 
> I have chnaged NM_CONTROLLED value from "no" to "yes"
> 
Did you really changed it on your disk, or just in this post?
If you edited the file and save, NM would re-read it and start managing eth0.

In case you still have a problem, please restart NM and grab logs (/var/log/messages) of the start-up. They should start with "NetworkManager (version XXX) is starting..."

> I have tried command "nmcli con" that gives following result
'nmcli con' is equal to 'nmcli con list' and only shows configured connections, i.e. static profiles.
Active connections can be listed via 'nmcli con status'. However, until the device is unmanaged, no active connection will be on the device.

Comment 11 Xavier FERAUD 2011-10-19 21:00:32 UTC
I really changed it on the disk in the file !
The result of the command "service Network Manager restart" in /var/log/messsages is :
Oct 19 22:37:33 dxa4 NetworkManager[3288]: <info> NetworkManager (version 0.9.1.90-3.git20110927.fc15) is starting...
Oct 19 22:37:33 dxa4 NetworkManager[3288]: <info> Read config file /etc/NetworkManager/NetworkManager.conf
Oct 19 22:37:33 dxa4 NetworkManager[3288]: <info> VPN: loaded org.freedesktop.NetworkManager.vpnc
Oct 19 22:37:33 dxa4 NetworkManager[3288]: <info> VPN: loaded org.freedesktop.NetworkManager.pptp
Oct 19 22:37:33 dxa4 NetworkManager[3288]: <info> VPN: loaded org.freedesktop.NetworkManager.openvpn
Oct 19 22:37:33 dxa4 NetworkManager[3288]: <info> VPN: loaded org.freedesktop.NetworkManager.openconnect
Oct 19 22:37:33 dxa4 NetworkManager[3288]:    ifcfg-rh: Acquired D-Bus service com.redhat.ifcfgrh1
Oct 19 22:37:33 dxa4 NetworkManager[3288]: <info> Loaded plugin ifcfg-rh: (c) 2007 - 2010 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
Oct 19 22:37:33 dxa4 NetworkManager[3288]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
Oct 19 22:37:33 dxa4 NetworkManager[3288]:    ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-p8p1 ... 
Oct 19 22:37:33 dxa4 NetworkManager[3288]:    ifcfg-rh:     read connection 'System p8p1'
Oct 19 22:37:33 dxa4 NetworkManager[3288]:    ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-lo ... 
Oct 19 22:37:33 dxa4 NetworkManager[3288]:    ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-wlan0 ... 
Oct 19 22:37:33 dxa4 NetworkManager[3288]:    ifcfg-rh:     read connection 'System dwi (wlan0)'
Oct 19 22:37:33 dxa4 NetworkManager[3288]:    ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-eth0 ... 
Oct 19 22:37:33 dxa4 NetworkManager[3288]:    ifcfg-rh:     read connection 'System eth0'
Oct 19 22:37:33 dxa4 NetworkManager[3288]: <info> modem-manager is now available
Oct 19 22:37:33 dxa4 NetworkManager[3288]: <info> monitoring kernel firmware directory '/lib/firmware'.
Oct 19 22:37:33 dxa4 NetworkManager[3288]: <info> found WiFi radio killswitch rfkill0 (at /sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:02/SNY5001:00/rfkill/rfkill0) (driver Sony Notebook Control Driver)
Oct 19 22:37:33 dxa4 NetworkManager[3288]: <info> found WiFi radio killswitch rfkill3 (at /sys/devices/pci0000:00/0000:00:1c.0/0000:02:00.0/ieee80211/phy0/rfkill3) (driver (unknown))
Oct 19 22:37:33 dxa4 NetworkManager[3288]: <info> WiFi enabled by radio killswitch; enabled by state file
Oct 19 22:37:33 dxa4 NetworkManager[3288]: <info> WWAN enabled by radio killswitch; enabled by state file
Oct 19 22:37:33 dxa4 NetworkManager[3288]: <info> WiMAX enabled by radio killswitch; enabled by state file
Oct 19 22:37:33 dxa4 NetworkManager[3288]: <info> Networking is enabled by state file
Oct 19 22:37:33 dxa4 NetworkManager[3288]: <info> (wlan0): driver supports SSID scans (scan_capa 0x01).
Oct 19 22:37:33 dxa4 NetworkManager[3288]: <info> (wlan0): new 802.11 WiFi device (driver: 'ath9k' ifindex: 3)
Oct 19 22:37:33 dxa4 NetworkManager[3288]: <info> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/0
Oct 19 22:37:33 dxa4 NetworkManager[3288]: <info> (wlan0): now managed
Oct 19 22:37:33 dxa4 NetworkManager[3288]: <info> (wlan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Oct 19 22:37:33 dxa4 NetworkManager[3288]: <info> (wlan0): bringing up device.
Oct 19 22:37:33 dxa4 NetworkManager[3288]: <info> (wlan0): preparing device.
Oct 19 22:37:33 dxa4 NetworkManager[3288]: <info> (wlan0): deactivating device (reason 'managed') [2]
Oct 19 22:37:33 dxa4 kernel: [ 6839.715661] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Oct 19 22:37:33 dxa4 NetworkManager[3288]: <info> (eth0): carrier is OFF
Oct 19 22:37:33 dxa4 NetworkManager[3288]: <info> (eth0): new Ethernet device (driver: 'sky2' ifindex: 2)
Oct 19 22:37:33 dxa4 NetworkManager[3288]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/1
Oct 19 22:37:33 dxa4 NetworkManager[3288]: <info> (eth0): now managed
Oct 19 22:37:33 dxa4 NetworkManager[3288]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Oct 19 22:37:33 dxa4 NetworkManager[3288]: <info> (eth0): bringing up device.
Oct 19 22:37:33 dxa4 kernel: [ 6839.721405] sky2 0000:04:00.0: eth0: enabling interface
Oct 19 22:37:33 dxa4 kernel: [ 6839.721943] ADDRCONF(NETDEV_UP): eth0: link is not ready
Oct 19 22:37:33 dxa4 NetworkManager[3288]: <info> (eth0): preparing device.
Oct 19 22:37:33 dxa4 NetworkManager[3288]: <info> (eth0): deactivating device (reason 'managed') [2]
Oct 19 22:37:33 dxa4 NetworkManager[3288]: <warn> bluez error getting default adapter: No such adapter
Oct 19 22:37:33 dxa4 NetworkManager[3288]: <info> (wlan0): supplicant interface state: starting -> ready
Oct 19 22:37:33 dxa4 NetworkManager[3288]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Oct 19 22:37:33 dxa4 NetworkManager[3288]: <info> (wlan0): supplicant interface state: ready -> inactive
Oct 19 22:37:35 dxa4 ntpd[949]: Deleting interface #9 wlan0, fe80::7add:8ff:fee4:b5ec#123, interface stats: received=0, sent=0, dropped=0, active_time=130 secs
Oct 19 22:37:35 dxa4 ntpd[949]: Deleting interface #8 wlan0, 192.168.1.242#123, interface stats: received=28, sent=28, dropped=0, active_time=130 secs
Oct 19 22:37:35 dxa4 ntpd[949]: 91.121.201.31 interface 192.168.1.242 -> (none)
Oct 19 22:37:35 dxa4 ntpd[949]: 188.165.51.29 interface 192.168.1.242 -> (none)
Oct 19 22:37:35 dxa4 ntpd[949]: 193.55.167.1 interface 192.168.1.242 -> (none)
Oct 19 22:37:35 dxa4 ntpd[949]: 88.191.73.241 interface 192.168.1.242 -> (none)
Oct 19 22:37:35 dxa4 ntpd[949]: peers refreshed
Oct 19 22:37:35 dxa4 NetworkManager[3288]: <info> Auto-activating connection 'System dwi (wlan0)'.
Oct 19 22:37:35 dxa4 NetworkManager[3288]: <info> Activation (wlan0) starting connection 'System dwi (wlan0)'
Oct 19 22:37:35 dxa4 NetworkManager[3288]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Oct 19 22:37:35 dxa4 NetworkManager[3288]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Oct 19 22:37:35 dxa4 NetworkManager[3288]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Oct 19 22:37:35 dxa4 NetworkManager[3288]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Oct 19 22:37:35 dxa4 NetworkManager[3288]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Oct 19 22:37:35 dxa4 NetworkManager[3288]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Oct 19 22:37:35 dxa4 NetworkManager[3288]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Oct 19 22:37:35 dxa4 NetworkManager[3288]: <info> Activation (wlan0/wireless): connection 'System dwi (wlan0)' has security, and secrets exist.  No new secrets needed.
Oct 19 22:37:35 dxa4 NetworkManager[3288]: <info> Config: added 'ssid' value 'dwi'
Oct 19 22:37:35 dxa4 NetworkManager[3288]: <info> Config: added 'scan_ssid' value '1'
Oct 19 22:37:35 dxa4 NetworkManager[3288]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Oct 19 22:37:35 dxa4 NetworkManager[3288]: <info> Config: added 'psk' value '<omitted>'
Oct 19 22:37:35 dxa4 NetworkManager[3288]: <info> Config: added 'proto' value 'WPA RSN'
Oct 19 22:37:35 dxa4 NetworkManager[3288]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Oct 19 22:37:35 dxa4 NetworkManager[3288]: <info> Config: set interface ap_scan to 1
Oct 19 22:37:35 dxa4 NetworkManager[3288]: <info> (wlan0): supplicant interface state: inactive -> scanning
Oct 19 22:37:36 dxa4 NetworkManager[3288]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Oct 19 22:37:36 dxa4 NetworkManager[3288]: <info> (wlan0): supplicant interface state: authenticating -> associating
Oct 19 22:37:36 dxa4 kernel: [ 6842.382313] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Oct 19 22:37:36 dxa4 NetworkManager[3288]: <info> (wlan0): supplicant interface state: associating -> 4-way handshake
Oct 19 22:37:36 dxa4 NetworkManager[3288]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed
Oct 19 22:37:36 dxa4 NetworkManager[3288]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'dwi'.
Oct 19 22:37:36 dxa4 NetworkManager[3288]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Oct 19 22:37:36 dxa4 NetworkManager[3288]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Oct 19 22:37:36 dxa4 NetworkManager[3288]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
Oct 19 22:37:36 dxa4 NetworkManager[3288]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Oct 19 22:37:36 dxa4 NetworkManager[3288]: <info> dhclient started with pid 3290
Oct 19 22:37:36 dxa4 NetworkManager[3288]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Oct 19 22:37:36 dxa4 dhclient[3290]: Internet Systems Consortium DHCP Client 4.2.1-P1
Oct 19 22:37:36 dxa4 dhclient[3290]: Copyright 2004-2011 Internet Systems Consortium.
Oct 19 22:37:36 dxa4 dhclient[3290]: All rights reserved.
Oct 19 22:37:36 dxa4 dhclient[3290]: For info, please visit https://www.isc.org/software/dhcp/
Oct 19 22:37:36 dxa4 dhclient[3290]: 
Oct 19 22:37:36 dxa4 dhclient[3290]: Listening on LPF/wlan0/78:dd:08:e4:b5:ec
Oct 19 22:37:36 dxa4 dhclient[3290]: Sending on   LPF/wlan0/78:dd:08:e4:b5:ec
Oct 19 22:37:36 dxa4 dhclient[3290]: Sending on   Socket/fallback
Oct 19 22:37:36 dxa4 NetworkManager[3288]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
Oct 19 22:37:36 dxa4 dhclient[3290]: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Oct 19 22:37:36 dxa4 dhclient[3290]: DHCPACK from 192.168.1.1
Oct 19 22:37:36 dxa4 dhclient[3290]: bound to 192.168.1.242 -- renewal in 17874 seconds.
Oct 19 22:37:36 dxa4 NetworkManager[3288]: <info> (wlan0): DHCPv4 state changed preinit -> reboot
Oct 19 22:37:36 dxa4 NetworkManager[3288]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) scheduled...
Oct 19 22:37:36 dxa4 NetworkManager[3288]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) started...
Oct 19 22:37:36 dxa4 NetworkManager[3288]: <info>   address 192.168.1.242
Oct 19 22:37:36 dxa4 NetworkManager[3288]: <info>   prefix 24 (255.255.255.0)
Oct 19 22:37:36 dxa4 NetworkManager[3288]: <info>   gateway 192.168.1.1
Oct 19 22:37:36 dxa4 NetworkManager[3288]: <info>   hostname 'dxa4'
Oct 19 22:37:36 dxa4 NetworkManager[3288]: <info>   nameserver '192.168.1.1'
Oct 19 22:37:36 dxa4 NetworkManager[3288]: <info>   domain name 'lan'
Oct 19 22:37:36 dxa4 NetworkManager[3288]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
Oct 19 22:37:36 dxa4 NetworkManager[3288]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) complete.
Oct 19 22:37:36 dxa4 NetworkManager[3288]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
Oct 19 22:37:36 dxa4 avahi-daemon[954]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.242.
Oct 19 22:37:36 dxa4 avahi-daemon[954]: New relevant interface wlan0.IPv4 for mDNS.
Oct 19 22:37:36 dxa4 avahi-daemon[954]: Registering new address record for 192.168.1.242 on wlan0.IPv4.
Oct 19 22:37:37 dxa4 NetworkManager[3288]: <info> (wlan0): device state change: ip-config -> activated (reason 'none') [70 100 0]
Oct 19 22:37:37 dxa4 NetworkManager[3288]: <info> Policy set 'System dwi (wlan0)' (wlan0) as default for IPv4 routing and DNS.
Oct 19 22:37:37 dxa4 NetworkManager[3288]: <info> Activation (wlan0) successful, device activated.
Oct 19 22:37:37 dxa4 NetworkManager[3288]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
Oct 19 22:37:37 dxa4 avahi-daemon[954]: Registering new address record for fe80::7add:8ff:fee4:b5ec on wlan0.*.
Oct 19 22:37:37 dxa4 systemd[1]: PID 3258 read from file /var/run/sendmail.pid does not exist. Your service or init script might be broken.
Oct 19 22:37:39 dxa4 ntpd[949]: Listen normally on 10 wlan0 192.168.1.242 UDP 123
Oct 19 22:37:39 dxa4 ntpd[949]: Listen normally on 11 wlan0 fe80::7add:8ff:fee4:b5ec UDP 123
Oct 19 22:37:39 dxa4 ntpd[949]: peers refreshed

I have tested a new time with the Ms Windows boot and I confirm that the network card and Ethernet link works fine.

Comment 12 Fedora End Of Life 2012-08-07 16:05:40 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping