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

Zaraphrax · #1 16th September 2010, 02:13 PM

Hi all,

I've just installed Fedora 13 x86_64 on my Dell Latitude E6410. This laptop has Intel 82577LM Ethernet and Intel 6300 WiFi. Both of which work fine under Windows and Linux Mint. However on Fedora, I can't get either of them to work. Flicking the wireless switch on doesn't bring up the wireless light, and cycling the Ethernet cable does nothing at all. I've also tried using ifconfig, however it tells me no adaptors are installed. It is my understanding that both of these should work out of the box (I installed via a netinstall, so perhaps I've removed a package I shouldn't have?). Any help would be greatly appreciated, and apologies for my limited Linux experience.

stoat · #2 17th September 2010, 01:35 AM

I don't have an Intel wireless adapter (wish I did, though), but Fedora has several Intel wireless driver modules and firmware packages. And it's sort of rare to have to do anything for an Ethernet card to work. I would boot into Mint and get it to tell you what drivers its using for those hardware items and what firmware is installed. Then you easily can find out if they are built-in or available for Fedora. Another thing worth checking in Fedora for the wireless is the status of rfkill. You probably can install that from your DVD. See the help or man page for the simple syntax for listing current states of devices and unblocking them.

Some things to do in Mint for information...

Code:

lspci -k
lsmod | sort
dpkg -l *firmware*

kuade · #3 17th September 2010, 02:15 AM

Zara,
sorry for the worthless post but I have the same laptop and FC13. I have posted this question on linuxquestions.org so if I find out anything I will be sure to let you know. I will edit this post as soon as I can get some good/helpful information. Unfortunatly I am still very new to Linux and you might find a solution first

Zaraphrax · #4 17th September 2010, 02:38 AM

Quote:

Originally Posted by stoat

I don't have an Intel wireless adapter (wish I did, though), but Fedora has several Intel wireless driver modules and firmware packages. And it's sort of rare to have to do anything for an Ethernet card to work. I would boot into Mint and get it to tell you what drivers its using for those hardware items and what firmware is installed. Then you easily can find out if they are built-in or available for Fedora. Another thing worth checking in Fedora for the wireless is the status of rfkill. You probably can install that from your DVD. See the help or man page for the simple syntax for listing current states of devices and unblocking them.

Some things to do in Mint for information...

Code:

lspci -k
lsmod | sort
dpkg -l *firmware*

Thanks for the info. I should've been more specific in that it has worked with Mint before, I now don't have Mint installed (I've picked up and moved t Fedora). EDIT: I have read online that the ethernet card uses the e1000e driver.

Quote:

Originally Posted by kuade

Zara,
sorry for the worthless post but I have the same laptop and FC13. I have posted this question on linuxquestions.org so if I find out anything I will be sure to let you know. I will edit this post as soon as I can get some good/helpful information. Unfortunatly I am still very new to Linux and you might find a solution first

Many thanks.

stoat · #5 17th September 2010, 03:36 AM

Quote:

Originally Posted by Zaraphrax

EDIT: I have read online that the ethernet card uses the e1000e driver.

That doesn't surprise me. Like I said before, IMO, it's kinda rare for an Ethernet card not to work in Fedora. That e1000e driver module is included with Fedora kernels. The kernel is usually good about loading the right module for detected hardware. You can check for the module in the output of this...

Code:

lsmod | sort

If it's there, then start looking for some other reason for it not to work. Maybe even silly things like cabling or router or modem things.

I did some reading around, too, and that wireless adapter likely uses the iwlagn driver module which also is included with Fedora kernels. See if it's being loaded (the lsmod output again). But it needs firmware. I can't be sure since I already confessed that I don't own a card with that chipset, but I would be tempted to install the iwl6000-firmware package. It's a harmless and reversible thing to try. If you get the Ethernet going, then you easily can install the wireless firmware with yum. Otherwise, you can install it from your DVD. It may already be installed. You can check for that this way...

Code:

rpm -qa | grep firmware

If the driver module and the firmware were already installed (very possible if the card was on when Fedora was installed), then start looking for things that can disable a wireless card such as on-off switches, hotkeys and software switches, BIOS settings, and rfkill.

Zaraphrax · #6 17th September 2010, 03:48 AM

e1000e is installed according to that. I haven't moved the machine at all, and it's been working as I've been using Windows to browse the web whilst trying to get this sorted out.

The firmware and driver package are both installed. However, the odd thing is, last night turning the wireless on wouldn't do a damn thing. Just now I threw the switch, and this post is now coming to you from Fedora via my wireless connection. Weird, weird, weird.

EDIT: Not only that, LSCPI detects the wired NIC correctly and that it is using the e1000e drivers. What the heck is this thing doing?

stoat · #7 17th September 2010, 04:00 AM

Maybe it's a NetworkManager thing. Maybe set one or the other to "Connect automatically". See that by right-clicking the NetworkManager panel applet icon, "Edit Connections...", Wired tab or Wireless tab, "Edit". While you're in there, set both to "Available to all users".

Zaraphrax · #8 17th September 2010, 04:07 AM

Quote:

Originally Posted by stoat

Maybe it's a NetworkManager thing. Maybe set one or the other to "Connect automatically". See that by right-clicking the NetworkManager panel applet icon, "Edit Connections...", Wired tab or Wireless tab, "Edit". While you're in there, set both to "Available to all users".

Both are set to connect automatically & enabled for all users. No dice. Wireless still works, but wired doesn't even recognise it's plugged in.

stoat · #9 17th September 2010, 04:21 AM

Okay. Try unchecking "Enable Wireless" in the NetworkManager panel applet (right-click the panel icon). Then left-click the applet and click "System eth0" or whatever it says for you. The icon should do the swirling green dots thing and connect. The icon will change from signal bars to look like two monitors (but without the red X for disconnected). You will be connected via the NIC. To go back to wireless, right-click the icon and check "Enable Wireless" again. Left-click again and choose the wireless network. It works like that here. Play around with that stuff.

P.S.: Actually, you may not need to uncheck "Enable Wireless". If you are connected to the router by wire, try just left-clicking the applet icon and choose "System eth0". And vice versa for wireless. It may work like that, too. I've already put my cable away. You can figure it out for all of us. I rarely (never, actually) am connected by both methods at the same time, so I don't really know the tiny details of it all.

Zaraphrax · #10 17th September 2010, 04:30 AM

Quote:

Originally Posted by stoat

Okay. Try unchecking "Enable Wireless" in the panel applet (right-click). Then left-click the applet and click "System eth0" or whatever it says for you. The icon should do the swirling green dots thing and connect. The icon will look like two monitors (but without the red X for disconnected). You will be connected via the NIC. To go back to wireless, right-click the icon and check "Enable Wireless" again. Left-click again and choose the wireless network. It works like that here. Play around with that stuff.

P.S.: Actually, you may not need to uncheck "Enable Wireless". If you are connected to the router by wire, try just left-clicking the applet icon and choose "System eth0". And vice versa for wireless. It may work like that, too. I've already put my cable away. You can figure it out for all of us. I rarely (never, actually) am connected by both methods at the same time, so I don't really know the tiny details of it all.

System eth0 doesn't show up in the list, even with wireless disabled.

Arimus · #11 17th September 2010, 10:15 AM

From a terminal window what does ip link report (example below is for my U100, wireless is disabled currently)

Code:

[root@u100-fc13 ~]# 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: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
    link/ether 00:24:21:f6:e9:c9 brd ff:ff:ff:ff:ff:ff
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state DORMANT qlen 1000
    link/ether 00:24:21:c9:7f:a0 brd ff:ff:ff:ff:ff:ff
4: pan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN 
    link/ether c6:ee:e2:2a:c6:ac brd ff:ff:ff:ff:ff:ff
11: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 3
    link/ppp

When you do lspci -v does it report the driver in use and the kernel module loaded ?

Might be an idea to post the output from both lsmod and lspci -v for the relevant bits...

Zaraphrax · #12 17th September 2010, 10:27 AM

Hi there,

ip link gives this (I'm currently sitting here with the wireless ON)

Code:

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: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether 00:24:d7:23:f0:88 brd ff:ff:ff:ff:ff:ff
3: pan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN 
    link/ether 52:3c:ad:7d:0c:15 brd ff:ff:ff:ff:ff:ff

lspci -v gives (trimmed just for the networking hardware):

Code:

00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit Network Connection (rev 05)
	Subsystem: Dell Device 040a
	Flags: fast devsel, IRQ 20
	Memory at e9600000 (32-bit, non-prefetchable) [size=128K]
	Memory at e9680000 (32-bit, non-prefetchable) [size=4K]
	I/O ports at 8040 [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

03:00.0 Network controller: Intel Corporation Centrino Ultimate-N 6300 (rev 35)
	Subsystem: Intel Corporation Centrino Ultimate-N 6300 3x3 AGN
	Flags: bus master, fast devsel, latency 0, IRQ 30
	Memory at e6e00000 (64-bit, non-prefetchable) [size=8K]
	Capabilities: [c8] Power Management version 3
	Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [e0] Express Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Device Serial Number 00-24-d7-ff-ff-23-f0-88
	Kernel driver in use: iwlagn
	Kernel modules: iwlagn

And lsmod gives:

Code:

Module                  Size  Used by
vfat                    8512  0 
fat                    44892  1 vfat
ppp_deflate             3988  0 
ppp_async               6860  0 
crc_ccitt               1557  1 ppp_async
ppp_generic            21701  2 ppp_deflate,ppp_async
slhc                    4843  1 ppp_generic
option                 15685  0 
usb_wwan               10264  1 option
usbserial              33093  2 option,usb_wwan
usb_storage            45368  2 
fuse                   57233  10 
rfcomm                 66944  4 
deflate                 1969  0 
zlib_deflate           18943  2 ppp_deflate,deflate
ctr                     3797  0 
camellia               18244  0 
sco                    16845  2 
bridge                 64064  0 
cast5                  16096  0 
stp                     1943  1 bridge
llc                     4733  2 bridge,stp
rmd160                  7968  0 
bnep                   15449  2 
l2cap                  46390  16 rfcomm,bnep
crypto_null             2862  0 
ccm                     7720  0 
serpent                18349  0 
blowfish                8242  0 
twofish_x86_64          5231  0 
twofish_common         14430  1 twofish_x86_64
xcbc                    2631  0 
cbc                     2929  0 
sha256_generic         10143  0 
sha512_generic          4756  0 
des_generic            16391  0 
aes_x86_64              7742  0 
aes_generic            27084  1 aes_x86_64
ah6                     5612  0 
ah4                     4947  0 
esp6                    4911  0 
esp4                    5178  0 
xfrm4_mode_beet         2027  0 
xfrm4_tunnel            1939  0 
tunnel4                 2595  1 xfrm4_tunnel
xfrm4_mode_tunnel       1864  0 
xfrm4_mode_transport     1439  0 
xfrm6_mode_transport     1503  0 
xfrm6_mode_ro           1292  0 
xfrm6_mode_beet         1898  0 
xfrm6_mode_tunnel       1784  0 
ipcomp                  1999  0 
ipcomp6                 2032  0 
xfrm_ipcomp             4174  2 ipcomp,ipcomp6
xfrm6_tunnel            4008  1 ipcomp6
tunnel6                 2462  1 xfrm6_tunnel
af_key                 26462  0 
sunrpc                198573  1 
cpufreq_ondemand        8764  4 
acpi_cpufreq            7693  1 
freq_table              3955  2 cpufreq_ondemand,acpi_cpufreq
ip6t_REJECT             4111  2 
nf_conntrack_ipv6      17856  2 
ip6table_filter         1671  1 
ip6_tables             17580  1 ip6table_filter
ipv6                  275768  53 ah6,esp6,xfrm6_mode_beet,xfrm6_mode_tunnel,ipcomp6,xfrm6_tunnel,tunnel6,ip6t_REJECT,nf_conntrack_ipv6
uinput                  7455  0 
snd_hda_codec_nvhdmi    12797  4 
snd_hda_codec_idt      55832  1 
snd_hda_intel          23960  2 
snd_hda_codec          85624  3 snd_hda_codec_nvhdmi,snd_hda_codec_idt,snd_hda_intel
snd_hwdep               6454  1 snd_hda_codec
snd_seq                53005  0 
snd_seq_device          6159  1 snd_seq
snd_pcm                80324  2 snd_hda_intel,snd_hda_codec
nvidia              11080195  41 
arc4                    1433  2 
snd_timer              19882  2 snd_seq,snd_pcm
ecb                     2087  2 
snd                    62929  13 snd_hda_codec_nvhdmi,snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_seq,snd_seq_device,snd_pcm,snd_timer
ppdev                   8326  0 
parport_pc             21225  0 
dell_wmi                3059  0 
uvcvideo               54628  0 
videodev               35667  1 uvcvideo
iwlagn                152556  0 
iwlcore               233826  1 iwlagn
e1000e                120377  0 
iTCO_wdt               11200  0 
wmi                     6888  1 dell_wmi
sdhci_pci               7238  0 
v4l1_compat            12930  2 uvcvideo,videodev
sdhci                  17806  1 sdhci_pci
v4l2_compat_ioctl32    10021  1 videodev
mmc_core               62351  1 sdhci
soundcore               6390  1 snd
btusb                  15388  2 
dcdbas                  8388  0 
i2c_i801               10270  0 
parport                31449  2 ppdev,parport_pc
iTCO_vendor_support     2555  1 iTCO_wdt
microcode              18282  0 
mac80211              220214  2 iwlagn,iwlcore
bluetooth              89796  9 rfcomm,sco,bnep,l2cap,btusb
cfg80211              134041  3 iwlagn,iwlcore,mac80211
snd_page_alloc          7437  2 snd_hda_intel,snd_pcm
rfkill                 17218  4 bluetooth,cfg80211
joydev                  9771  0 
i2c_core               25709  3 nvidia,videodev,i2c_i801
firewire_ohci          20544  0 
firewire_core          44982  1 firewire_ohci
crc_itu_t               1547  1 firewire_core
video                  21629  0 
output                  2221  1 video

Hopefully that's what you're after....

Thanks.

Arimus · #13 17th September 2010, 11:35 AM

The ethernet card lspci output looks odd; should have a kernel driver in use line matching the kernel module (least it does on the ethernet systems I';ve got to hand) - also would have expected device serial number lines.

Try dmesg | grep e1000e to see what's reported during boot up regarding your ethernet controller (might need to play with the search string)

Zaraphrax · #14 17th September 2010, 11:56 AM

Quote:

Originally Posted by Arimus

The ethernet card lspci output looks odd; should have a kernel driver in use line matching the kernel module (least it does on the ethernet systems I';ve got to hand) - also would have expected device serial number lines.

Try dmesg | grep e1000e to see what's reported during boot up regarding your ethernet controller (might need to play with the search string)

Code:

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

Does this make any sense to you?

Arimus · #15 17th September 2010, 01:43 PM

Well it tells us why the ethernet interface isn't present... the module is failing to load.

I've seen plenty of references for -3 being returned (due to irq assignements etc) but not -2... going to see if I can see what -2 actually means....