Dell Latitude E6410 - No ethernet, no wireless (strange)

[stevea]

Yes. The kernel was walking the PCi bus and found the registers page for the device, but couldn't access the PCI bus memory.

You should always report "lspci -nnk" since we really need the chip endor numbers. Also look/verify that ALL devices on PCI are recognized (no "UNKNOWN" devices). Ii interpret you output as indicating the enet is a [8086:10ea] device id.

The e1000e is verified as the correct driver for that ID.

It appears this is a known problem that appeared somewhere between the 2.6.32 and 2.6.34 kernel where the power management allows the chip to shutdown before the probe is complete. The correction involved several files and it was signed off for kernel inclusion around June 10.

Which version of the Fedora kernel are you running when this occurs ?
Update to the latest and if it still occurs you'll need to install an older kernel or build the newest.

--

update
put in the kernel July 30, so it seems to appear in 2.6.36-rc4 kernel.
http://git.kernel.org/?p=linux/kerne...3f11e2ea253d52

[Zaraphrax]

According to uname -a:

Linux hubble.mydomain.removed 2.6.34.6-54.fc13.x86_64

That's the latest, no?

[Zaraphrax]

Ok thank you to all that responded. I now have sucessfully fixed my ethernet problem.

I install this kernel and all is well. However it breaks the nVidia drivers which is something I now have to fix, but at least I'll have ethernet when I do. Thanks a bunch.

[kuade]

Hi, I wish that I knew a little bit more about linux, all this stuff is pretty advanced for me. If you are all still willing to help me out that would be great. Thanks

[Jesse@titanium ~]$ lsmod | sort
acpi_cpufreq            6453  1 
bluetooth              72139  10 hidp,rfcomm,sco,bnep,l2cap,btusb
bnep                   11757  2 
bridge                 37420  0 
btusb                  12104  4 
cpufreq_ondemand        6732  4 
crc_itu_t               1215  1 firewire_core
dcdbas                  6360  0 
dell_wmi                2499  0 
drm                   133962  2 i915,drm_kms_helper
drm_kms_helper         21663  1 i915
e1000e                102355  0 
fat                    36677  1 vfat
firewire_core          35642  1 firewire_ohci

[root@titanium ~]# lspci -v
00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02)
	Subsystem: Dell Device 040a
	Flags: bus master, fast devsel, latency 0
	Capabilities: [e0] Vendor Specific Information: Len=0c <?>
	Kernel driver in use: agpgart-intel

00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit Network Connection (rev 05)
	Subsystem: Dell Device 040a
	Flags: fast devsel, IRQ 20
	Memory at f6900000 (32-bit, non-prefetchable) [size=128K]
	Memory at f6980000 (32-bit, non-prefetchable) [size=4K]
	I/O ports at 7040 [size=32]
	Capabilities: [c8] Power Management version 2
	Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [e0] PCI Advanced Features
	Kernel modules: e1000e

02:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g LP-PHY (rev 01)
	Subsystem: Dell Device 0010
	Flags: bus master, fast devsel, latency 0, IRQ 11
	Memory at f4100000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [40] Power Management version 3
	Capabilities: [58] Vendor Specific Information: Len=78 <?>
	Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [d0] Express Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [13c] Virtual Channel
	Capabilities: [160] Device Serial Number 00-00-00-ff-ff-89-78-e4
	Capabilities: [16c] Power Budgeting <?>

[Jesse@titanium ~]$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: pan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN 
    link/ether 9a:0a:56:ad:0a:e3 brd ff:ff:ff:ff:ff:ff
[Jesse@titanium ~]$

[root@titanium ~]# dmesg | grep e1000e
e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k2
e1000e: Copyright (c) 1999 - 2009 Intel Corporation.
e1000e 0000:00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
e1000e 0000:00:19.0: setting latency timer to 64
e1000e 0000:00:19.0: irq 30 for MSI/MSI-X
e1000e 0000:00:19.0: PCI INT A disabled
e1000e: probe of 0000:00:19.0 failed with error -2
[root@titanium ~]#

In the Network configuration tool it auto loads the 3com ethernet as pan0 and I cannot edit it. I tried deleting it, then adding a new device so I can access the drop down list but my driver is not listed and I cannot select pan0 as my second option.

[stoat]

Originally Posted by kuade

If you are all still willing to help me out that would be great.

Well, I wasn't sure who you were talking to there, but I am willing anyway. First, even though you said in post #3 that you have the same computer as Zaraphrax, you sure don't have the same wireless adapter. Zaraphrax has an Intel 6300 which is supported by a driver module and firmware that comes with Fedora. But you have a Broadcom wireless chipset that requires you to install a driver. The best idea to try for that IMO is the Broadcom 802.11 STA Linux driver (aka broadcom-wl). If you want to proceed with that, and since your wired NIC is not working yet (I think), you will need to download some driver files on another computer (or in Windows if you are dual booting) and manually install them. To start, you need to identify the current kernel (uname -r). After you return and post that information, I or someone will tell you which files to download and where to get them and how to install them. That will get the wireless going.

Next, that wired NIC of yours has resulted in the kernel loading the e1000e driver module. I trust the kernel to know what it's doing related to that, so you probably can eventully get that going, too. But I don't know what you or Zaraphrax need to do about that. Maybe somebody else knows.

That pan0 thing is usually a bluetooth device.

[stevea]

Originally Posted by kuade

Hi, I wish that I knew a little bit more about linux, all this stuff is pretty advanced for me..

OP has a pretty advanced problem The problem is specific to the e1000e and the r8169 drivers for hardware that supports PCI power management (pretty new).

The only reason that 2.6.35 koji kernel works is *probably* b/c Fedora team has a habit of backporting later kernel changes as patches. 2.6.36-rc4 seems to be the earliest vanilla kernel with the fix.

-S

[Zaraphrax]

Originally Posted by stevea

OP has a pretty advanced problem The problem is specific to the e1000e and the r8169 drivers for hardware that supports PCI power management (pretty new).

The only reason that 2.6.35 koji kernel works is *probably* b/c Fedora team has a habit of backporting later kernel changes as patches. 2.6.36-rc4 seems to be the earliest vanilla kernel with the fix.

-S

The odd thing now though, is even when I boot up with the original kernel, the wired NIC now works. Even when powering off the machine and removing the power, it comes up just fine under the original kernel. *shrugs*

[stevea]

Originally Posted by Zaraphrax

The odd thing now though, is even when I boot up with the original kernel, the wired NIC now works. Even when powering off the machine and removing the power, it comes up just fine under the original kernel. *shrugs*

OK - that's very odd. All I can think is that a bios setting has disabled the PM or else the timing has changed a little and ...

[Zaraphrax]

Originally Posted by stevea

OK - that's very odd. All I can think is that a bios setting has disabled the PM or else the timing has changed a little and ...

I initially thought it was because when I booted the new kernel (and simply warm restarted back to the old kernel) it'd brought the adaptor up. But even shutting the machine down, unplugging the cable and removing the power from the system, then booting the original kernel brings it up just fine. I have no idea what's going on, but at least now as long as it keeps working I don't have to mess with nVidia drivers. :P

---------- Post added at 09:33 PM CDT ---------- Previous post was at 08:32 PM CDT ----------

Ok, apparently I was wrong. I just booted my machine into Windows, and then back into Fedora (original kernel) and no ethernet. I haven't fixed my nVidia drivers on the new kernel yet (any guides or advice on how to do that would be appreciated as I'm a bit lost as to what I need to actually do to get them working), but for the time being I'm happily on WiFi.

[stoat]

I don't know about Windows 7 or your NIC, but in XP I can go into the Device Manager and disable Windows' power management of the Intel NIC in my Thinkpad. I think I have read posts where people did that for such things as this going on here. I know that I have read posts where rebooting from Windows into Fedora (without shutting down) has resulted in a network card being disabled.

[kuade]

stoat,

Thank you for the assistance. uname -r reveals:
2.6.33.3-85.fc13.i686.PAE

Is it easy to update the kernel? The only reason I ask is because I am trying to teach myself Linux, but you all know better than I do.

[stoat]

Originally Posted by kuade

02:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g LP-PHY (rev 01)

Originally Posted by kuade

uname -r reveals:
2.6.33.3-85.fc13.i686.PAE

I guess that means that your wired NIC connection is not yet working. Then you can download the following three files from RPM Fusion in Windows or another computer, transfer them to the Fedora filesystem, and manually install them...

broadcom-wl-5.60.48.36-1.fc13.noarch.rpm
kmod-wl-PAE-5.60.48.36-1.fc13.5.i686.rpm
kmod-wl-2.6.33.3-85.fc13.i686.PAE-5.60.48.36-1.fc13.5.i686.rpm

To manually install them, open a terminal, change directories in the terminal to the directory with the three files, and install them all at once in the same command like this...

su
rpm -ivh *.rpm

Ignore or agree to GPG key warnings for now. Then reboot and check the NetworkManager panel applet icon for available networks (left-click the icon) and connect.

If all of that worked, then you must then install the RPM Fusion non-free repo before updating the system. Otherwise, the kernel will be updated but not the broadcom-wl stuff and there will be no wireless in the new kernel. Go here to learn how to install the RPM Fusion repos (go ahead and install Free and Nonfree)...

http://rpmfusion.org/Configuration

[kuade]

stoat, thanks for the info. I installed the three *.rpm and my wifi card is now recognized but the intel NIC is not present. Unfortunatly my wifi is giving me an error when I try to activate it.

Error org.freedesktop.NetworkManagerSettings.InternalErr or: unable to get the connection D-Bus path
Error org.freedesktop.NetworkManagerSettings.InternalErr or: unable to get the connection D-Bus path
Error for wireless request "Set Encode" (8B2A) :
SET failed on device eth1 ; Invalid argument.

Determining IP information for eth1... failed.

[stoat]

Originally Posted by kuade

Unfortunatly my wifi is giving me an error when I try to activate it.

I'm not really sure what you mean by that. Sorry. Actually, you don't need to do anything like that. After installing the kmods, you only need to reboot and look for available networks in the NetworkManager panel applet icon. That's it.

If you have opened the old Network Configuration utility (aka and started with system-config-network), don't do that. If you entered stuff in there, undo it. You can even delete any wireless interfaces in that. Reboot. Check the NetworkManager panel applet icon for networks.

Another sometimes helpful thing is to disable the network service. True, NetworkManager needs it. But NetworkManager will start the network service later when it needs it. Having network disabled in services sometimes avoids IP address errors during booting before the interface is ready. It won't hurt to try it...

su
chkconfig network off
reboot

If nothing above helped, then return and describe in more detail what you are doing to attempt a connection and what you are observing when it doesn't happen.

[kuade]

stoat,

That did it

 chkconfig network off

as soon as I did that the applet popped right up and my wifi and NIC work.

Thank you for the help, it looks like everything is working! close this thread as SOLVED