[SOLVED] Intel 82566DM Gigabit Network Adapter won't show up as eth0.

ewaller · 2011-07-07 02:09:44

You are correct, your router is using the 192.168.1.xx subdomain. If you are trying a static IP, you will have to be on that subnet.

IMHO, your problem lies with the route command and not having a default gateway. I don't understand the error you are still experiencing after this morning's post and want to work through that issue.

Never-the-less, try it with a static address and see if the same issue remains.

BTW, are the network, wicd, or NetworkManager running ? (look in /run/daemons for lock files bearing the daemon name)

jnl wrote:

Now, type in "route", if one of those start with "default 192.168.0.1", your routes have been updated properly.

Aye, there is the rub.

ScionicSpectre · 2011-07-07 02:20:33

K, so I pkill'd dhcpcd first, then I proceeded to do each of the commands jni wrote latest. I then typed route to see what was on. It output a Destination of 192.168.1.0, Gateway of asterisk (*), and so on (basically like the last post of these results, just with a 1.0 instead of 0.0.

I then issued route del default, even though default didn't really exist it seemed, but just following directions XD. It said SIOCDELRT: No such process.

Then I executed the default gateway command, and pinging 4.4.4.4 says connect: Network is unreachable. I type route and the information comes up just as it was typed next to default, and with route -n it's the same, just with 0.0.0.0 instead of the word default under Destination. Also, ifconfig reports the static IP assigned to it (in case that's important).

Looks like Arch is trying to engage in some sort of sadomasochistic relationship with me.

Last edited by ScionicSpectre (2011-07-07 02:23:57)

ScionicSpectre · 2011-07-07 02:39:20

I don't seem to have a /run folder on my drive. Also, I'm pretty sure I don't even have wicd installed- didn't know you could get it from the 2010 install iso. *scratches head*

Thank you for filling in the blanks here, you guys. It's been very helpful so far- I'm sure we're narrowing things down quite a bit. Also, I should note that Kubuntu uses the same e1000e driver module as does Arch, so it probably isn't an issue there unless the version in Arch is super-old or has a serious bug even after updating to 2.6.39 (I did reinstall from scratch however, so I'm not on that kernel at the moment, just to be clear). I'll keep looking around at my files and making comparisons in the meantime.

I can already see myself facepalming over how obvious the solution is in the near future.

Last edited by ScionicSpectre (2011-07-07 02:40:56)

jni · 2011-07-07 02:44:26

Indeed ewaller, it sounds more like a route issue. The DHCP seems to half work and "network unreachable" it means linux doesn't know what to do with a packet... so it doesn't even have a gateway to send it to or anything.

This could be stupid... but do you have another wire to try it with? If so, change the wire between your PC and your router... just in case.

PS: sorry for the late reply... i kept pressing F5... duh, it was on a second page.

Last edited by jni (2011-07-07 02:49:26)

ScionicSpectre · 2011-07-07 03:04:40

Well, redid the whole static IP routine with a new cable, and no changes. I figured it wouldn't, since I'm rebooting to the LiveUSB on the same machine as the Arch installation (it starts pretty fast, so it's no biggy).

I just don't know enough about networking on Linux to figure out a reason why dhcp won't just cram an IP into the interface by itself, especially when it did briefly at one point. It seemed entirely random. Another odd thing- my friend has the exact same computer (they're twins) with the same components and everything, and when we installed Arch at his house with the netinstall CD, the network did download and install all the packages, but had the same problem after installation as I'm having here (so we just went with Ubuntu as his place while I tried to figure it out on mine at home :\).

So it's pretty obvious the issue is all in the networking configuration, and it may even have something to do with my router, but the router works with plenty of wireless and wired computers in this house. So Arch has some sort of lack of automation with this specific card that's making it full of hate. I can plug the exact same cord into my older Arch box without so much as a peep about anything network related.

Sorry for the rant- I'm sure that was all pretty irrelevant. I'm just hoping to find some information on a variety of things I could try to do to get it working with dhcp, or otherwise. I guess I might as well review the man pages of ifconfig and dhcpcd (and the module options for e1000e, since that could be different between Debian and Arch).

If you guys have anymore 'this could be stupid, but...' ideas, it'd be great to hear them, since they might lead to a solution at this point. Of course, I don't expect you to dispel a wiki's worth of possible networking configurations here if you know about them, since this isn't the place, but I feel kinda' powerlessly unknowledgeable at the moment. Thank you so much for your free time this evening, though- respond at your leisure, I know none of this is directly your responsibility (unless you're a developer *shakes fist*).

ewaller · 2011-07-07 03:08:13

Sanity check: Can you ping 192.168.1.1 ?

ScionicSpectre · 2011-07-07 03:25:43

You see, the sad part isn't that I didn't think of trying that before. It's that I did and forgot to mention it, or realize its significance at the time (I thought I had the wrong driver loaded back then).

It outputs connect: Network is unreachable when I try to ping it. Now I'm wondering what could possibly be standing in the way, if not some module options or something. It's 'insane'.

Last edited by ScionicSpectre (2011-07-07 03:27:24)

jni · 2011-07-07 03:47:00

it really is a route problem... i'm just way too tired to think of something i guess (i missed the .1 subnet, forgot to change page, etc... lol)

Here is the output on my computer... it should look something like that, changing 192.168.0 to 192.168.1 obviously.

You could also try to unload/reload your NIC driver, and look in dmesg for strange stuff.

my ifconfig

eth0      Link encap:Ethernet  HWaddr 00:24:8C:62:4F:2B  
          inet addr:192.168.0.100  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::224:8cff:fe62:4f2b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:374724 errors:0 dropped:0 overruns:0 frame:0
          TX packets:180865 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:371430277 (354.2 Mb)  TX bytes:18187887 (17.3 Mb)
          Interrupt:44

my route

└% route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         192.168.0.1     0.0.0.0         UG    202    0        0 eth0
192.168.0.0     *               255.255.255.0   U     202    0        0 eth0

(if your genmask is 255.255.255.0, it should work too)

unless you did some changes, it shouldn't be a problem... but is you iptable empty? (all policy ACCEPT or logical rules).

Here is the config you should have in /etc/rc.conf

old way

eth0="dhcp"
INTERFACES=(eth0)

gateway="default gw 192.168.0.1"
ROUTES=(!gateway)

New way

interface=eth0
address=
netmask=
gateway=

Also, make sure you have a hostname set (command to check this is... suspense... 'hostname' ). Does it output something? Otherwise, set it in rc.conf (this should not be an issue... but at this point, i'm just throw stupid ideas in the air, see what comes down lol)

can you ping 127.0.0.1 ?

From another computer (or from the router, if you have some cool routers), can you ping your net-deprivated PC? i.e. if you used 192.168.1.100 for this arch rig, try "ping 192.168.1.100" from 192.168.1.101

Make sure you have no conflicts on ur network when you use static IPs. If 2 PC have the same IP, it'll give weird results like that (check iPhones, android phones, iPod touch, etc etc). Or just use something ridiculous like 192.168.1.167

What is your router? Did you make custom configs to it? Did you change default subnet or anything?

Doing "traceroute 4.4.4.4" or "traceroute 192.168.1.1", does it hop to the gateway? It should say "network unreachable too" or just hang... but who knows

EDIT : one more... if you do "ifconfig -a", do you have other interfaces? other than eth0 and lo

Alright, this is as much as my brain can do for the day lol i often have genius ideas in the shower tho, so we'll see about that tomorrow morning

Good luck with that, i'll try to read this again and reply tomorrow morning, if you haven't found it yet.

PS : i too am sure we'll be having a round of facepalms when we figure this out...

Last edited by jni (2011-07-07 03:48:41)

ScionicSpectre · 2011-07-07 04:12:57

Well, I certainly do have a hostname, and my rc.conf still uses the 'old way', and I'll probably leave it that way until I update unless it's necessary to change it (will it work with the old Arch?). I definitely can ping 127.0.0.1, and it seems to communicate at a constant rate. Unfortunately, I can't access any of the other computers in this place at the moment, but I tried a high, improbable number just to be sure my HTC EVO wasn't interfering, since it's using WiFi at the moment.

My router configuration is vanilla aside from WPA security and an exception to allow RDP connections in Port Forwarding from a while back. Also, only have ethernet 0 and loopback in ifconfig's output. Thank you for the suggestions- I hope some of that information is helpful.

jni · 2011-07-07 12:12:49

Aight, i really can't think of anything else... even tho i am sure we are just missing the obvious here.

Let's tackle this from the beginning again.

Make sure your router IP is 192.168.1.1 ... it could be 192.168.1.254, i've seen some like that.
Next, make sure it doesn't use funky subnets... i.e. check another device, their ip should be something similar to 192.168.1.100. If it looks like 192.168.1.2... that could be your router only using subject 192.168.1.2 through 192.168.1.99

Try either dhcp or static ips, and see if your ifconfig -a and route -n shows about the same as mine.

If after double checking all of that it still fails, let's more to more obscur solutions.

If you run "route -Ceen", you'll see every routed connections. Produce some net activity, pings, opening firefox, etc. Does it output anything? If so, it might be a huge output... post a sample here please.

Next is hardware problems.

what does "dmesg | grep -A5 -B5 eth0" say? Can you post that here please?

Can you also post "cat /proc/interrupts" and "cat /proc/ioports" please? It'll show any hardware conflict (this would actually make sense... since your "twin" computers both don't work).

If it's a pci card, add the output of "lspci", if it's a usb card use "lsusb" instead.

What is your driver again? I think you said you knew it. And what's your kernel (uname -a) ?

I know most of these ideas are far fetched and some make no sense... but it's all i can think of, next thing on the list is i buy a plane ticket to wherever you are and check it out on my own lol

Your problem is giving me sleep issues lol but it's enough for this morning, time to go to work. You should have a few mins worth of work to gather all these info

Last edited by jni (2011-07-07 12:25:49)

ewaller · 2011-07-07 14:45:37

jni wrote:

what does "dmesg | grep -A5 -B5 eth0" say? Can you post that here please?
Can you also post "cat /proc/interrupts" and "cat /proc/ioports" please? It'll show any hardware conflict (this would actually make sense... since your "twin" computers both don't work).

Those are definitely the next place to start looking. Although, itis a bit like opening Pandora's box.

ScionicSpectre · 2011-07-07 17:38:57

The spectre's networking issues are haunting you at night. D: Lol.

The IP of the router is definitely 192.168.1.1. Every computer in the house, including the one Arch is having issues with, has the same subnet mask and default gateway (255.255.255.0 and 192.168.1.1). The only major difference seems to be that my Kubuntu partition and those other computers have a DNS suffix from my ISP (hsd1.ut.comcast.net) and nameservers 68.87.85.102 and 68.87.69.150, while my Arch box has nothing there (its resolv.conf is totally empty, except for the time I entered some nameservers suggested by jni a while back).

Also, all the IPs on these computers are in the 100, 101, 102 range. Nothing excessive, no crazy subnets. If it weren't for Arch, you'd think things were perfectly normal. XD

I tried to get an address through dhcpcd again and it failed (I have no idea how I ever got one in the first place). With a static IP and default gateway specified, and after trying to ping a few things, route -Ceen displayed absolutely nothing but the category headings.

Dmesg output.

ppdev: user-space parallel port driver
lp0: using parport0 (interrupt-driven).
tpm_tis 00:0b: 1.2 TPM (device-id 0xB, rev-id 16)
input: HP WMI hotkeys as /devices/virtual/input/input4
[drm] Initialized drm 1.1.0 20060810
0000:00:19.0: eth0: (PCI Express:2.5GB/s:Width x1) 00:0f:fe:6c:15:be
0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
0000:00:19.0: eth0: MAC: 6, PHY: 6, PBA No: 1002ff-0ff
ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 20 (level, low) -> IRQ 20
ehci_hcd 0000:00:1d.7: setting latency timer to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2
ehci_hcd 0000:00:1d.7: debug port 1
--
generic-usb 0003:413C:2006.0002: input,hidraw1: USB HID v1.10 Keyboard [Dell Dell USB Keyboard Hub] on usb-0000:00:1d.0-2.1/input0
input: Dell Dell USB Keyboard Hub as /devices/pci0000:00/0000:00:1d.0/usb5/5-2/5-2.1/5-2.1:1.1/input/input8
generic-usb 0003:413C:2006.0003: input,hidraw2: USB HID v1.10 Device [Dell Dell USB Keyboard Hub] on usb-0000:00:1d.0-2.1/input1
e1000e 0000:00:19.0: irq 25 for MSI/MSI-X
e1000e 0000:00:19.0: irq 25 for MSI/MSI-X
e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
0000:00:19.0: eth0: 10/100 speed: disabling TSO
0000:00:19.0: eth0: changing MTU from 1500 to 576
0000:00:19.0: eth0: changing MTU from 576 to 1500
e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
0000:00:19.0: eth0: 10/100 speed: disabling TSO
0000:00:19.0: eth0: changing MTU from 1500 to 576
0000:00:19.0: eth0: changing MTU from 576 to 1500
e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
0000:00:19.0: eth0: 10/100 speed: disabling TSO
0000:00:19.0: eth0: changing MTU from 1500 to 576
0000:00:19.0: eth0: changing MTU from 576 to 1500
e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
0000:00:19.0: eth0: 10/100 speed: disabling TSO
0000:00:19.0: eth0: changing MTU from 1500 to 576
0000:00:19.0: eth0: changing MTU from 576 to 1500
e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
0000:00:19.0: eth0: 10/100 speed: disabling TSO
0000:00:19.0: eth0: changing MTU from 1500 to 576
0000:00:19.0: eth0: changing MTU from 576 to 1500
e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
0000:00:19.0: eth0: 10/100 speed: disabling TSO
0000:00:19.0: eth0: changing MTU from 1500 to 576
0000:00:19.0: eth0: changing MTU from 576 to 1500
e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
0000:00:19.0: eth0: 10/100 speed: disabling TSO
usb 5-1: USB disconnect, address 2
usb 5-1: new low speed USB device using uhci_hcd and address 5
input: PIXART USB OPTICAL MOUSE as /devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.0/input/input9
generic-usb 0003:093A:2510.0004: input,hidraw0: USB HID v1.11 Mouse [PIXART USB OPTICAL MOUSE] on usb-0000:00:1d.0-1/input0
usb 5-1: USB disconnect, address 5
usb 5-1: new low speed USB device using uhci_hcd and address 6
input: PIXART USB OPTICAL MOUSE as /devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.0/input/input10
generic-usb 0003:093A:2510.0005: input,hidraw0: USB HID v1.11 Mouse [PIXART USB OPTICAL MOUSE] on usb-0000:00:1d.0-1/input0
e1000e 0000:00:19.0: irq 25 for MSI/MSI-X
e1000e 0000:00:19.0: irq 25 for MSI/MSI-X
e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
0000:00:19.0: eth0: 10/100 speed: disabling TSO
usb 5-1: USB disconnect, address 6
usb 5-1: new low speed USB device using uhci_hcd and address 7
input: PIXART USB OPTICAL MOUSE as /devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.0/input/input11
generic-usb 0003:093A:2510.0006: input,hidraw0: USB HID v1.11 Mouse [PIXART USB OPTICAL MOUSE] on usb-0000:00:1d.0-1/input0
usb 5-1: USB disconnect, address 7

Interrupts output.

           CPU0       CPU1       
  0:         50          0   IO-APIC-edge      timer
  1:          2          0   IO-APIC-edge      i8042
  6:          3          0   IO-APIC-edge      floppy
  7:          0          0   IO-APIC-edge      parport0
  8:        161          0   IO-APIC-edge      rtc0
  9:          0          0   IO-APIC-fasteoi   acpi
 12:          4          0   IO-APIC-edge      i8042
 14:       1668          0   IO-APIC-edge      ata_piix
 15:         90          0   IO-APIC-edge      ata_piix
 20:       1183          0   IO-APIC-fasteoi   ehci_hcd:usb2, uhci_hcd:usb3, uhci_hcd:usb5
 21:          0          0   IO-APIC-fasteoi   uhci_hcd:usb4, uhci_hcd:usb6
 22:          0          0   IO-APIC-fasteoi   ehci_hcd:usb1
 25:         76          0   PCI-MSI-edge      eth0
 26:        140          0   PCI-MSI-edge      hda_intel
 27:          1          0   PCI-MSI-edge      i915
NMI:          0          0   Non-maskable interrupts
LOC:       3590       5479   Local timer interrupts
SPU:          0          0   Spurious interrupts
PMI:          0          0   Performance monitoring interrupts
PND:          0          0   Performance pending work
RES:        283        173   Rescheduling interrupts
CAL:          7         24   Function call interrupts
TLB:        162        163   TLB shootdowns
TRM:          0          0   Thermal event interrupts
THR:          0          0   Threshold APIC interrupts
MCE:          0          0   Machine check exceptions
MCP:          2          2   Machine check polls
ERR:          1
MIS:          0

Ioports output.

0000-001f : dma1
0020-0021 : pic1
0040-0043 : timer0
0050-0053 : timer1
0060-0060 : keyboard
0064-0064 : keyboard
0070-0071 : rtc0
0080-008f : dma page reg
00a0-00a1 : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : 0000:00:1f.2
  0170-0177 : ata_piix
01f0-01f7 : 0000:00:1f.2
  01f0-01f7 : ata_piix
0376-0376 : 0000:00:1f.2
  0376-0376 : ata_piix
0378-037a : parport0
03c0-03df : vga+
03f2-03f2 : floppy
03f4-03f5 : floppy
03f6-03f6 : 0000:00:1f.2
  03f6-03f6 : ata_piix
03f7-03f7 : floppy
03f8-03ff : serial
0400-041f : pnp 00:0e
0420-043f : pnp 00:0e
0440-045f : pnp 00:0e
0460-047f : pnp 00:0e
  0460-0461 : ACPI PM1b_CNT_BLK
0480-048f : pnp 00:0e
04d0-04d1 : pnp 00:0f
0778-077a : parport0
0cf8-0cff : PCI conf1
1000-101f : 0000:00:19.0
1020-103f : 0000:00:1a.0
  1020-103f : uhci_hcd
1040-105f : 0000:00:1a.1
  1040-105f : uhci_hcd
1060-107f : 0000:00:1d.0
  1060-107f : uhci_hcd
1080-109f : 0000:00:1d.1
  1080-109f : uhci_hcd
10e0-10ef : 0000:00:1f.2
  10e0-10ef : ata_piix
10f0-10ff : 0000:00:1f.2
  10f0-10ff : ata_piix
1100-1107 : 0000:00:02.0
2000-2fff : PCI Bus 0000:20
f800-f87f : 0000:00:1f.0
  f800-f803 : ACPI PM1a_EVT_BLK
  f804-f805 : ACPI PM1a_CNT_BLK
  f808-f80b : ACPI PM_TMR
  f810-f815 : ACPI CPU throttle
  f828-f82f : ACPI GPE0_BLK
  f830-f833 : iTCO_wdt
  f860-f87f : iTCO_wdt
fa00-fa3f : 0000:00:1f.0
  fa00-fa3f : pnp 00:0e
fc00-fc7f : pnp 00:0e
fc80-fcff : pnp 00:0e
fe00-fe7f : pnp 00:0e
fe80-feff : pnp 00:0e

The lspci line for my card (this is where I got the information for the title of my post).

00:19.0 Ethernet controller: Intel Corporation 82566DM Gigabit Network Connection (rev 02)

And lsmod shows that e1000e is there, and it's the only module related to my card that I can successfully rmmod, so I assume it's the only one active. This is also the module used in my Kubuntu installation, although I don't know how to check their versions to see if they're the same (I assume they're in the kernel, so if the version should have been the problem, the update I made to 2.6.39 on my earlier attempt should have fixed things). There were issues with these conflicting back in the 2.6.25 series of kernels, but I assume that's long over now, as my Arch is using 2.6.33 (the default for the latest ISO on the download page). At least, that's what uname -a says.

I see a lot of MTU changing up there. I did find a post somewhere on the forums suggesting to set the MTU to 1492 (or something like that) a while back and tried that, but it didn't change anything, static IP or otherwise. Also, MTU is 1500 on my Kubuntu box and it's working perfectly. So I'm really at a loss. I'm 'this' close to resetting my router to factory defaults just to see if it helps. Let me know if this is too much output to have in the forums, and I can offload the text to another website like pastebin.

EDIT: My router is a Linksys WRT54GS2, according to the router page. It's round and black and shiny. D:

Last edited by ScionicSpectre (2011-07-07 17:46:11)

MoonSwan · 2011-07-07 19:09:04

Out of curiousity, are you actually using any of the "iw(xxx)" drivers? You might need to check that with pacman doing a "pacman -Qs iw". I mention this because I do recall seeing there are some intel specific drivers and firmwares needed during installation for Intel NICs.

I'm stabbing at anything in the dark here partly because I have the same issue on my netbook. Until the last week it has been problem free where networking is concerned. But in the last week I must have re-installed and re-done as much as I can to get it to connect to my LAN/router. Very frustrating.

{Edit} Ok stupid question time but have you ever typed this in at a prompt: modprobe e1000

That should load the correct driver for your Nic. If you've never tried that, you might want to look at the output of "lspci|grep -i net" or "... grep -i intel"

I hope this helps.

Last edited by MoonSwan (2011-07-07 19:12:42)

ScionicSpectre · 2011-07-07 20:14:22

I had indeed attempted to use e1000 as a last resort throughout all of this troubleshooting (rmmod e1000e, modprobe e1000, retry). But it never really worked and e1000e is what's working on my Kubuntu partition. Also, the e is for PCIe, and this driver has been favored over e1000 since kernel 2.6.25 or so from what I've read, as e1000 is in a 'stable maintenance mode'. At least, that's all the information I could gather from Intel and other related sites.

I will of course take a look at the firmware issue you're referring to, since Ubuntu's notorious for including things like this in their patched kernel whereas Arch is notorious for having the fewest modifications necessary.

UPDATE: pacman -Qs iw returns nothing, but I'm on a desktop with no wireless (I assumed wireless is what that refers to).

Last edited by ScionicSpectre (2011-07-07 21:50:40)

ScionicSpectre · 2011-07-08 07:05:18

I just popped in an Ubuntu Maverick LiveCD a minute ago to look at something in the old Firefox, and it turns out Maverick actually has the same issue. So it may indeed be a kernel issue, and I don't expect there to be a great deal of difference between the default network settings in successive releases. It may well be some small tweak to some setting that's allowing it to work.

I'm starting to think that getting it working with this kernel version is going to be a dead end. Feel free to make any extra suggestions you might have based on the output information above. I think I'm going to reinstall Arch from a newer (unsupported) ISO, otherwise. And if that doesn't work, I'll just keep a broken Arch around (hopefully not indefinitely, after I file a bug).

ewaller · 2011-07-08 14:35:43

How do you feel about compiling a kernel? It is not that tough with a little guidance.

ScionicSpectre · 2011-07-08 16:30:13

I don't really like the idea of recompiling the kernel often, but my guess is that this bug will be taken care of in the near future. I think I know enough about Linux not to be alienated by the experience, and it might be fun. XD

I just need to know any extra packages I might need to compile the kernel and a few pointers on what's most important to my situation (ie. how compiling the kernel could actually help me solve the problem). I assume the wiki should be a good enough guide otherwise?

EDIT: It should also be noted that Fedora, OpenSUSE, and Ubuntu (the distributions the ethernet works with) use NetworkManager by default, not network or netcfg. Also, I tried a Live Arch (CTK Arch), and it failed to work, but it uses wicd. I might just try installing NetworkManager offline to see what happens.

Last edited by ScionicSpectre (2011-07-08 21:30:52)

ScionicSpectre · 2011-07-08 23:33:14

It's fixed!

All I had to do was install NetworkManager (I did it offline instead of chrooting, which required about an hour in dependency hell on the Arch Rollback Machine), and now it works with nothing more than following the instructions on the wiki and installing dhclient. In fact, dhclient may be the entire reason this whole thing works, now- I don't have the tenacity to go back and check, but if anyone else runs into this problem in the future, save yourself some trouble and just get dhclient to see if it works.

Thank you so much for your help, guys. If it weren't for you I wouldn't have caught onto any of this; I also learned quite a bit about Linux's networking stack. Although the solution was not ideal, and it explained little about why dhcpcd and the network daemon weren't working, we made it. If anyone who's been helping me troubleshoot wants more information I'll be glad to give it. Thank you again.

Last edited by ScionicSpectre (2011-07-08 23:33:54)

skottish · 2011-07-09 03:43:26

I had a network card in the past that simply would not work with dhcpcd but did with dhclient. I've also read a number of threads throughout the years from people with the same problem. I've brought this up before, but I really think that both dhcpcd and dhclient need to be in core. Unfortunately, I was too far removed from my own experience when the idea occured to me to form a useful feature request.

ScionicSpectre · 2011-07-09 03:51:56

I've indeed found much debate over the superiority of dhclient or dhcpcd. They seem to do much the same thing, and I think its their similarity of features and usefulness that keeps anything other than dhcpcd from breaking into the core ISO. If we let alternative utilities like that in, a lot of people would want to add more and more unnecessary stuff to the CD, surely.

But from what I see, for some people dhclient has become a necessity just to get things up and running. It'd be silly not to include it if this continues without a fix from dhcpcd. I may get around to making a request after testing my hardware more strongly in the future.

MoonSwan · 2011-07-09 21:02:23

Glad you solved it . Could you post a link to the specific wiki page(s) you used? I am in a similar boat and I'll take all the help I can get.

ScionicSpectre · 2011-07-11 00:32:34

NetworkManager and ARM (click ARM search). I suggest just getting dhclient and looking at its documentation before getting the fifteen or so distinct packages required for NetworkManager combined with it.

Arch Linux

#26 2011-07-07 02:09:44

Re: [SOLVED] Intel 82566DM Gigabit Network Adapter won't show up as eth0.

#27 2011-07-07 02:20:33

Re: [SOLVED] Intel 82566DM Gigabit Network Adapter won't show up as eth0.

#28 2011-07-07 02:39:20

Re: [SOLVED] Intel 82566DM Gigabit Network Adapter won't show up as eth0.

#29 2011-07-07 02:44:26

Re: [SOLVED] Intel 82566DM Gigabit Network Adapter won't show up as eth0.

#30 2011-07-07 03:04:40

Re: [SOLVED] Intel 82566DM Gigabit Network Adapter won't show up as eth0.

#31 2011-07-07 03:08:13

Re: [SOLVED] Intel 82566DM Gigabit Network Adapter won't show up as eth0.

#32 2011-07-07 03:25:43

Re: [SOLVED] Intel 82566DM Gigabit Network Adapter won't show up as eth0.

#33 2011-07-07 03:47:00

Re: [SOLVED] Intel 82566DM Gigabit Network Adapter won't show up as eth0.

#34 2011-07-07 04:12:57

Re: [SOLVED] Intel 82566DM Gigabit Network Adapter won't show up as eth0.

#35 2011-07-07 12:12:49

Re: [SOLVED] Intel 82566DM Gigabit Network Adapter won't show up as eth0.

#36 2011-07-07 14:45:37

Re: [SOLVED] Intel 82566DM Gigabit Network Adapter won't show up as eth0.

#37 2011-07-07 17:38:57

Re: [SOLVED] Intel 82566DM Gigabit Network Adapter won't show up as eth0.

#38 2011-07-07 19:09:04

Re: [SOLVED] Intel 82566DM Gigabit Network Adapter won't show up as eth0.

#39 2011-07-07 20:14:22

Re: [SOLVED] Intel 82566DM Gigabit Network Adapter won't show up as eth0.

#40 2011-07-08 07:05:18

Re: [SOLVED] Intel 82566DM Gigabit Network Adapter won't show up as eth0.

#41 2011-07-08 14:35:43

Re: [SOLVED] Intel 82566DM Gigabit Network Adapter won't show up as eth0.

#42 2011-07-08 16:30:13

Re: [SOLVED] Intel 82566DM Gigabit Network Adapter won't show up as eth0.

#43 2011-07-08 23:33:14

Re: [SOLVED] Intel 82566DM Gigabit Network Adapter won't show up as eth0.

#44 2011-07-09 03:43:26

Re: [SOLVED] Intel 82566DM Gigabit Network Adapter won't show up as eth0.

#45 2011-07-09 03:51:56

Re: [SOLVED] Intel 82566DM Gigabit Network Adapter won't show up as eth0.

#46 2011-07-09 21:02:23

Re: [SOLVED] Intel 82566DM Gigabit Network Adapter won't show up as eth0.

#47 2011-07-11 00:32:34

Re: [SOLVED] Intel 82566DM Gigabit Network Adapter won't show up as eth0.

Board footer