You are not logged in.
I built a new box in July. As a motherboard I chose an Asus p8z77-v and I'm having this problem with a clean install:
Most of the time when turning on the computer, I cannot connect to the network (even after setting the network config), and when I type "dhcpcd eth0" a message along the lines of interface eth0 not available appears.
I've have noticed however, that if I push the reboot button as soon as the computer turns on and beeps I don't have the problem.
I have had this problem not only with Arch, but with Xubuntu and Crunchbang (On the other hand the wireless adapter always works, regardless of ethernet)
Another thing I noticed when pressing DEL to go into the bios utility, is that most of the time when having trouble with ethernet I can see IBA GE SLOT as a boot option, which never appears when ethernet can be used without trouble. I think this might be related.
If it helps, I'm using EFI, and the ethernet interface is supposed to be Intel Gigabit ethernet.
Any suggestions?
Offline
Ok guys, I've got an update on this.
First, I was completely mistaken, there appears not to be an ethernet interface available when the Intel Boot Agent does not start, that means when turning the computer on from being completely off.
However, if restarting it, then the Intel agent appears on the screen (even before loading the system) and everything works as it is supposed to work.
Please, point me anywhere, as I can't seem to find anything closely related on the internet.
EDIT: If this goes in networking rather than hardware please help me moving it there, maybe it will get more views in that section
Last edited by theodorleopold (2012-10-24 02:35:49)
Offline
I use that same board (I think...at least very similar) and have not had that problem. Have you tried a firmware flash? Mine originally came with a February firmware and flashed it to one from early June.
Also Arch seems to like eth1 better than eth0 for me.
Not sure how much this helps but thought I'd throw it out.
Offline
I think this is relevant for the "eth0 vs. eth1" thing: there is a known "parallel start" issue between the network drivers and udev which can cause weirdness between eth0 and eth1.
Also see https://wiki.archlinux.org/index.php/Co … ng_Network, scroll down to the "Persistent device names" section, which explains the problem and https://wiki.archlinux.org/index.php/Ud … ork_device on how to have a solid workaround.
Offline
I'll check that in just a bit. On the other hand I noticed that by PXE OPROM in the mobo settings the Intel boot agent started from the beginning and not just when rebooting, however, it didn't solve the issue. My new guess is that the issue is not IBA related.
I'm not completely sure if it is an eth0 vs eth1 issue, as loading Xubuntu (which automatically connects to the networks) doesn't solve it. If I reboot it automatically connects to the wired network, if turning on for the first time it shows a "no wired network available" ,and instead offers to connect to the available wireless networks.
I used to have the first firmware (probably dating back to february or march) but updated to a more recent one and yesterday got the most recent firmware available through Asus, but the issue persisted.
Offline