> -----Original Message----- > From: Bruce Ferrell [mailto:bferr...@baywinds.org] > Sent: Sunday, March 03, 2013 9:49 AM > To: e1000-devel@lists.sourceforge.net > Subject: [E1000-devel] 82574L Gig E Adapter not recognized by OpenSUSE kernel > 3.8.0-28-desktop > > Any suggestions folks? Do I have a bad card? > > I've now rolled back to OpenSUSE 3.4.28-2.20-desktop and ethtool still says > the > card's not there: > > modprobe e1000e debug=16 > > dmesg > [ 2360.580696] e1000e: Intel(R) PRO/1000 Network Driver - 2.2.14-NAPI > [ 2360.580698] e1000e: Copyright(c) 1999 - 2012 Intel Corporation. > [ 2360.580721] e1000e 0000:07:00.0: Disabling ASPM L0s L1 > [ 2360.580882] e1000e 0000:07:00.0: Interrupt Throttling Rate (ints/sec) set > to dynamic conservative mode > [ 2360.581467] e1000e 0000:07:00.0: irq 59 for MSI/MSI-X > [ 2360.581470] e1000e 0000:07:00.0: irq 60 for MSI/MSI-X > [ 2360.581473]e1000e 0000:07:00.0: irq 61 for MSI/MSI-X > [ 2360.682071] e1000e 0000:07:00.0: eth1: (PCI Express:2.5GT/s:Width x1) > 68:05:ca:12:90:dd > [ 2360.682073] e1000e 0000:07:00.0: eth1: Intel(R) PRO/1000 Network > Connection > [ 2360.682097] e1000e 0000:07:00.0: eth1: MAC: 4, PHY: 8, PBA No: E46981-008 > [ 2360.843419] ADDRCONF(NETDEV_UP): eth1: link is not ready > [ 2360.843423] device eth1 entered promiscuous mode > > > [..] > eth1 Link encap:Ethernet HWaddr 68:05:CA:12:90:DD > inet addr:xxx.xxx.xxx.xxx Bcast:xxx.xxx.xxx.xxx > Mask:255.255.255.240 > 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 txqueuelen:1000 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > Interrupt:16 Memory:f7ac0000-f7ae0000 > > > ethtool eth1 > Settings for eth1: > Cannot get device settings: No such device Cannot get wake-on-lan settings: No > such device Cannot get message level: No such device Cannot get link status: > No > such device No data available [..]
Hello, Sorry you having trouble with our parts. There seems to have been some changes with this kernel version to the runtime power management system that is affecting the parts supported in this driver. We have other reports and we are trying to find a resolution. In the meantime, as a workaround you can disable runtime power management in the kernel config. Another way to do that, which may or may not be available to you is to change the contents of a file in the sysfs file system using the <busdevfunc> of your device: /sys/devices/pci0000:00/0000:07:00.0/power/control file, <busdevfunc> in this case is the <0000:07:00.0> listed in the output you sent. However its, possible that file does not exist for this device on your system. If it does exist echo "on" to that file. If it does not, then only the kernel config is an option. Let me know if the workaround helps at all. Thanks, Carolyn Carolyn Wyborny Linux Development Networking Division Intel Corporation ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
