You are not logged in.
Hello world! For the first time I can't get a network connection while installing, did everything as usual until giving the pacstrap command it couldn't connect to the servers. The very same livecd worked fine installing on a laptop.
Here's some basic outputs:
ifconfig -a # shows "lo" only
ip link # same here too
lspci # 00:19.0 Intel 82579V
lsmod # e1000e 0
Does that last one mean the driver is lacking and I have bad luck with this specific controller not working on the go? If so, what can I do?
Last edited by lio94 (2015-02-08 21:14:02)
Offline
https://wiki.archlinux.org/index.php/be … uide#Wired
Edit: Welcome to the Arch Forums!
Last edited by frank604 (2015-02-08 22:47:49)
Offline
Thanks.
But what comes to my problem, as I mentioned, it doesn't show that "enpXXX" interface code for my ethernet controller, only loopback thing. Trying ip link set x up or such commands with names as eth0, eth1... don't work either. I have been able to configure wireless and wired networks with minor or no problems before in other computers, but this is a totally new situation.
Offline
Oops. Guess I didn't read it right. What is uname -a and pacman - Qi Linux?
edit: spelling
Last edited by frank604 (2015-02-15 05:23:03)
Offline
Hardblocked maybe? What is the output of
rfkill list all
Crude matter we are not, Luminous beings we are
Offline
rfkill is only for wireless interfaces, and it is only relevant when there is an interface.
Can you post the full entry of the `lscpci -v` output. Which modules are available for the card? EDIT: googling around it seems the e1000e module is the right one for this card. Odd.
Last edited by Trilby (2015-02-09 12:21:41)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
uname -a # Linux archiso 3.18.4-1-ARCH #1 SMP PREEMPT date time x86_64 GNU/Linux
lspci -v # Flags: fast devsel, IRQ 20 \ blah blah \ capabilities: [e0] MSI:Enable- Count=1/1 Maskable- 64bit+ \ kernel modules: e1000e
But lsmod shows a 0 after e1000e. Means what?
Offline
That's normal - it just means no other module requires (depends on) the e1000e module.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
I managed to install a couple times with Evo/Lution installer past months but having some UEFI/BIOS boot problems. It did download the packages fine then but now not Arch nor Evo livecd's can form net connection, so the network interface wasn't dead then at least.
Hard to see what changed after that...
Offline
If it's not working now with the same Evo livecd it used to work under, then it's a hardware problem. If it's a different Evo, then it could be a regression in the module.
But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
Offline
If it's not working now with the same Evo livecd it used to work under, then it's a hardware problem. If it's a different Evo, then it could be a regression in the module.
Not sure if the same physical copy, so it might boot a newer release than then. I'll try with an older release tomorrow. What does this regression mean by the way?
edit: It is indeed a newer release I tried the past weeks. I'll try with this older Evo-CD I just found!
Last edited by lio94 (2015-02-14 18:39:10)
Offline
What does this regression mean by the way?
That there might have been some change in the kernel module that lead to the problem you are facing. A hardware issue seems much more likely to me, though the test with the older Evo disk is the conclusive test.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
It didn't work from the old evocd, but from usb it works fine... don't you say my cd-drive was the issue? Nevertheless I'm happy my NIC isn't broken.
Although now I have another problem. UEFI is disabled from BIOS, syslinux should be properly installed and configured, but it doesn't boot arch. No bootable device or via the usb entering "boot existing os" just flashes and brings the menu back.
Offline