[SUSPENDED] No network interface after cold boot

phollox · 2014-08-16 22:10:16

I have a weird issue with my NIC. The network interface eno1 is missing after cold boot, and only a reboot will fix it. My mother board is an Intel DH67BL. I upgraded the BIOS to the latest version, but it did not help.

$ uname -r

3.16.1-1-ARCH

After the cold boot, with the network down, I get these outputs for the network

# lspci -vvv

00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network Connection (rev 05)
	Subsystem: Intel Corporation Device 2002
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 20
	Region 0: Memory at fe500000 (32-bit, non-prefetchable) [size=128K]
	Region 1: Memory at fe528000 (32-bit, non-prefetchable) [size=4K]
	Region 2: I/O ports at f080 [size=32]
	Capabilities: [c8] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME-
	Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
		Address: 00000000feeff00c  Data: 41a2
	Capabilities: [e0] PCI Advanced Features
		AFCap: TP+ FLR+
		AFCtrl: FLR-
		AFStatus: TP-
	Kernel modules: e1000e

$ dmesg | grep e1000e

[    7.362167] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
[    7.362169] e1000e: Copyright(c) 1999 - 2014 Intel Corporation.
[    7.362284] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[    7.362300] e1000e 0000:00:19.0: irq 52 for MSI/MSI-X
[    8.378156] e1000e: probe of 0000:00:19.0 failed with error -3

When the network is up, after the reboot, these are the outputs

# lspci -vvv

00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network Connection (rev 05)
	Subsystem: Intel Corporation Device 2002
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 53
	Region 0: Memory at fe500000 (32-bit, non-prefetchable) [size=128K]
	Region 1: Memory at fe528000 (32-bit, non-prefetchable) [size=4K]
	Region 2: I/O ports at f080 [size=32]
	Capabilities: [c8] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME-
	Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
		Address: 00000000feeff00c  Data: 41e2
	Capabilities: [e0] PCI Advanced Features
		AFCap: TP+ FLR+
		AFCtrl: FLR-
		AFStatus: TP-
	Kernel driver in use: e1000e
	Kernel modules: e1000e

$ dmesg | grep e1000e

[    7.612032] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
[    7.612034] e1000e: Copyright(c) 1999 - 2014 Intel Corporation.
[    7.612156] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[    7.612171] e1000e 0000:00:19.0: irq 53 for MSI/MSI-X
[    7.879202] e1000e 0000:00:19.0 eth0: registered PHC clock
[    7.879207] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 0x:x0:0x:x0:0x:x0 (<==modified)
[    7.879209] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[    7.879261] e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: FFFFFF-0FF
[   13.572973] e1000e 0000:00:19.0: irq 53 for MSI/MSI-X
[   13.675606] e1000e 0000:00:19.0: irq 53 for MSI/MSI-X
[   15.218190] e1000e: eno1 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
[   15.218197] e1000e 0000:00:19.0 eno1: 10/100 speed: disabling TSO

I don't know how to get the meaning of the error -3 message when the module is probed.

Thanks,

Last edited by phollox (2015-01-09 01:06:41)

wtx · 2014-08-17 09:32:25

As far as I know "-3" status means "No such process", but probably this info doesn't help you much.

Could you post 'cat /proc/interrupts' in both cases?

Last edited by wtx (2014-08-17 10:05:14)

phollox · 2014-08-17 15:14:47

Thanks for your answer. Certainly, the "No such process" isn't very informative. These are the outputs you asked for.

After cold boot (no network)

$ cat /proc/interrupts

           CPU0       CPU1       CPU2       CPU3       CPU4       CPU5       CPU6       CPU7       
  0:         16          0          0          0          0          0          0          0   IO-APIC-edge      timer
  1:          3          0          0          0          0          0          0          0   IO-APIC-edge      i8042
  8:          1          0          0          0          0          0          0          0   IO-APIC-edge      rtc0
  9:          3          0          0          0          0          0          0          0   IO-APIC-fasteoi   acpi
 12:          4          0          0          0          0          0          0          0   IO-APIC-edge      i8042
 16:       3181          0          0          0          0          0          0          0   IO-APIC-fasteoi   ehci_hcd:usb1
 18:          0          0          0          0          0          0          0          0   IO-APIC-fasteoi   i801_smbus
 23:       4955          0          0          0          0          0          0          0   IO-APIC-fasteoi   ehci_hcd:usb4
 40:          0          0          0          0          0          0          0          0   PCI-MSI-edge      PCIe PME
 41:          0          0          0          0          0          0          0          0   PCI-MSI-edge      PCIe PME
 42:        214          0          0          0          0          0          0          0   PCI-MSI-edge      i915
 43:          1          0          0          0          0          0          0          0   PCI-MSI-edge      xhci_hcd
 44:          0          0          0          0          0          0          0          0   PCI-MSI-edge      xhci_hcd
 45:          0          0          0          0          0          0          0          0   PCI-MSI-edge      xhci_hcd
 46:          0          0          0          0          0          0          0          0   PCI-MSI-edge      xhci_hcd
 47:          0          0          0          0          0          0          0          0   PCI-MSI-edge      xhci_hcd
 48:          0          0          0          0          0          0          0          0   PCI-MSI-edge      xhci_hcd
 49:          0          0          0          0          0          0          0          0   PCI-MSI-edge      xhci_hcd
 50:          0          0          0          0          0          0          0          0   PCI-MSI-edge      xhci_hcd
 51:      56381          0          0          0          0          0          0          0   PCI-MSI-edge      ahci
 52:      18336          0          0          0          0          0          0          0   PCI-MSI-edge      snd_hda_intel
NMI:          0          0          0          0          0          0          0          0   Non-maskable interrupts
LOC:      24590      19851      18651      18656      10066       8630       9151      10526   Local timer interrupts
SPU:          0          0          0          0          0          0          0          0   Spurious interrupts
PMI:          0          0          0          0          0          0          0          0   Performance monitoring interrupts
IWI:          0          0          0          1          1          1          1          1   IRQ work interrupts
RTR:          5          0          0          0          0          0          0          0   APIC ICR read retries
RES:       1210       1882       1118        788        278        260        278        434   Rescheduling interrupts
CAL:        753        811        787        783        881        860        828        823   Function call interrupts
TLB:        105         21        155          9        102         28        145        198   TLB shootdowns
TRM:          0          0          0          0          0          0          0          0   Thermal event interrupts
THR:          0          0          0          0          0          0          0          0   Threshold APIC interrupts
MCE:          0          0          0          0          0          0          0          0   Machine check exceptions
MCP:          3          3          3          3          3          3          3          3   Machine check polls
THR:          0          0          0          0          0          0          0          0   Hypervisor callback interrupts
ERR:          0
MIS:          0

After reboot (network up)

$ cat /proc/interrupts

           CPU0       CPU1       CPU2       CPU3       CPU4       CPU5       CPU6       CPU7       
  0:         16          0          0          0          0          0          0          0   IO-APIC-edge      timer
  1:          3          0          0          0          0          0          0          0   IO-APIC-edge      i8042
  8:          1          0          0          0          0          0          0          0   IO-APIC-edge      rtc0
  9:          3          0          0          0          0          0          0          0   IO-APIC-fasteoi   acpi
 12:          4          0          0          0          0          0          0          0   IO-APIC-edge      i8042
 16:        385          0          0          0          0          0          0          0   IO-APIC-fasteoi   ehci_hcd:usb3
 18:          0          0          0          0          0          0          0          0   IO-APIC-fasteoi   i801_smbus
 23:       2149          0          0          0          0          0          0          0   IO-APIC-fasteoi   ehci_hcd:usb4
 40:          0          0          0          0          0          0          0          0   PCI-MSI-edge      PCIe PME
 41:          0          0          0          0          0          0          0          0   PCI-MSI-edge      PCIe PME
 42:        246          0          0          0          0          0          0          0   PCI-MSI-edge      i915
 43:          1          0          0          0          0          0          0          0   PCI-MSI-edge      xhci_hcd
 44:          0          0          0          0          0          0          0          0   PCI-MSI-edge      xhci_hcd
 45:          0          0          0          0          0          0          0          0   PCI-MSI-edge      xhci_hcd
 46:          0          0          0          0          0          0          0          0   PCI-MSI-edge      xhci_hcd
 47:          0          0          0          0          0          0          0          0   PCI-MSI-edge      xhci_hcd
 48:          0          0          0          0          0          0          0          0   PCI-MSI-edge      xhci_hcd
 49:          0          0          0          0          0          0          0          0   PCI-MSI-edge      xhci_hcd
 50:          0          0          0          0          0          0          0          0   PCI-MSI-edge      xhci_hcd
 51:      11456          0          0          0          0          0          0          0   PCI-MSI-edge      ahci
 52:        217          0          0          0          0          0          0          0   PCI-MSI-edge      eno1
 53:       7348          0          0          0          0          0          0          0   PCI-MSI-edge      snd_hda_intel
NMI:          0          0          0          0          0          0          0          0   Non-maskable interrupts
LOC:       5344       3407       3395       3209        677       1144        792        883   Local timer interrupts
SPU:          0          0          0          0          0          0          0          0   Spurious interrupts
PMI:          0          0          0          0          0          0          0          0   Performance monitoring interrupts
IWI:          0          1          1          0          1          1          1          1   IRQ work interrupts
RTR:          6          0          0          0          0          0          0          0   APIC ICR read retries
RES:        291        180        105         90         35         51         39        161   Rescheduling interrupts
CAL:        761        844        820        828        869        801        853        774   Function call interrupts
TLB:         30          8         16        192         14         18          9         19   TLB shootdowns
TRM:          0          0          0          0          0          0          0          0   Thermal event interrupts
THR:          0          0          0          0          0          0          0          0   Threshold APIC interrupts
MCE:          0          0          0          0          0          0          0          0   Machine check exceptions
MCP:          2          2          2          2          2          2          2          2   Machine check polls
THR:          0          0          0          0          0          0          0          0   Hypervisor callback interrupts
ERR:          0
MIS:          0

I also checked the power control and the output is on in both cases

$ cat /sys/bus/pci/devices/0000\:00\:19.0/power/control 
on

Thanks again,

EDIT: I just realized that the IRQ assigned to the network interface in this case was 52, while in my first post was 53.

$ dmesg | grep e1000e

[    7.370277] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
[    7.370278] e1000e: Copyright(c) 1999 - 2014 Intel Corporation.
[    7.370392] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[    7.370408] e1000e 0000:00:19.0: irq 52 for MSI/MSI-X
[    7.637644] e1000e 0000:00:19.0 eth0: registered PHC clock
[    7.637646] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 0x:x0:0x:x0:0x:x0 (<==modified)
[    7.637655] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[    7.637703] e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: FFFFFF-0FF
[   14.120756] e1000e 0000:00:19.0: irq 52 for MSI/MSI-X
[   14.224062] e1000e 0000:00:19.0: irq 52 for MSI/MSI-X
[   15.826677] e1000e: eno1 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
[   15.826684] e1000e 0000:00:19.0 eno1: 10/100 speed: disabling TSO

Also, the IRQ assigned to the eno1 is assigned to the sound card when the network is down after cold boot. This issue is fairly new, after a recent update. Probably related with the kernel module or with udev. Is it possible to assign the IRQ in a fixed manner? Thanks

Last edited by phollox (2014-08-18 13:08:48)

wtx · 2014-08-18 05:46:49

I would try to temporarily disable sound card in your system (in BIOS) and try to cold start the system.
Or - the second possibility - to compile "snd_hda_intel" as a module but e1000e compiled into the kernel. I mean you can try to enforce loading e1000e driver *before* snd_hda_intel, because there may be some problem with sharing interrupts in e1000e driver.

Hm... I don't know how to enforce assigning particular IRQ to pci(e) device.

Lone_Wolf · 2014-08-18 10:03:15

wtx wrote:

I would try to temporarily disable sound card in your system (in BIOS) and try to cold start the system.
Or - the second possibility - to compile "snd_hda_intel" as a module but e1000e compiled into the kernel. I mean you can try to enforce loading e1000e driver *before* snd_hda_intel, because there may be some problem with sharing interrupts in e1000e driver.
Hm... I don't know how to enforce assigning particular IRQ to pci(e) device.

Adding e1000e in the MODULES= line in mkinitcpio.conf, would be an easier way to make sure e1000e is loaded before snd_hda_intel .

phollox · 2014-08-18 13:08:16

Thank you both. I added e1000e to the MODULES= line in mkinitcpio.conf, as suggested, and generated the new image. It certainly help to attempt to load the e1000e before, but still, I'm getting an error -3

$ dmesg | grep e1000e

[    0.934736] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
[    0.934737] e1000e: Copyright(c) 1999 - 2014 Intel Corporation.
[    0.934871] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[    0.934888] e1000e 0000:00:19.0: irq 43 for MSI/MSI-X
[    1.956975] e1000e: probe of 0000:00:19.0 failed with error -3

With the network up

$ dmesg | grep e1000e

[    0.944218] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
[    0.944220] e1000e: Copyright(c) 1999 - 2014 Intel Corporation.
[    0.944377] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[    0.944398] e1000e 0000:00:19.0: irq 43 for MSI/MSI-X
[    1.211893] e1000e 0000:00:19.0 eth0: registered PHC clock
[    1.211897] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 0x:x0:0x:x0:0x:x0 (<==modified)
[    1.211898] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[    1.211948] e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: FFFFFF-0FF
[   13.701730] e1000e 0000:00:19.0: irq 43 for MSI/MSI-X
[   13.804952] e1000e 0000:00:19.0: irq 43 for MSI/MSI-X
[   15.327456] e1000e: eno1 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
[   15.327462] e1000e 0000:00:19.0 eno1: 10/100 speed: disabling TSO

Thus, it is loading e1000e module before snd_hda_intel, and it works, except when it comes from cold boot. I don't know why it is done for a eth0 interface. I never have one with that name. It has always been eno1.

It seems like some sort of BIOS feature, like powering off the LAN module for x amount of seconds after power up. There are a few power related features in my BIOS, but none of them is related with the network adapter, just with the processor, the memory, the CPU fan, etc.

On the other hand, with the exception of the recent update, I haven't modified my BIOS in ages. This issue appeared after an update, not sure of which package.

I also have the i915 module on my MODULES= line, so I could disable some power saving options (the screen was going blank during netflix playback). It's being loaded before e1000e, but some options have changed and a few parameters are currently non valid. But they are always invalid. Not sure how the cold boot could affect this.

I will temporarily remove the i915 from my MODULES line, and disable the sound in my BIOS. I'll keep you posted

EDIT: Neither removing i915 from the MODULES line nor disabling the sound in BIOS have any effect. Still the same issue

Last edited by phollox (2014-08-18 14:20:23)

R00KIE · 2014-08-18 17:04:54

Give the LTS kernel a try, if it works then most probably it is some kind of regression. To be really sure you could downgrade the kernel to the previous version and try that too.

phollox · 2014-08-18 17:14:30

Thanks R00KIE, I'll downgrade the kernel as soon as I can, and post the results. If it works, should I fill some sort of form to the kernel devs? Like a bug report? Or simple avoid the kernel upgrades in the pacman.conf?

Last edited by phollox (2014-08-18 17:15:07)

phollox · 2014-08-19 05:19:46

I downgraded the kernel, from 3.16.1-1-x86_64 to 3.12.1-3-x86_64. Same issue. This is my first kernel downgrade. I only ran

$ sudo pacman -u /var/cache/pacman/pkg/linux-3.12.1-3-x86_64.pkg.tar.xz

and pacman did not complained about dependencies. However, should I also downgrade any other packages?

Thanks

R00KIE · 2014-08-19 08:10:06

If it used to work with kernel 3.12 and now it doesn't then I would suspect a hardware problem (or some bios interference). If pacman didn't complain and you did a reboot after installing the kernel then it should be ok.

I find it strange that your lcpci output doesn't have any Ethernet controller, I get two, one for the wired card and another one for wireless card, but let someone else chime in and say something about it.

On another note, you did a big jump, you could have tried kernel 3.15 since you said it was working until very recently.

phollox · 2014-08-19 11:23:22

This is a desktop, so no wireless. ifconfig gives me normally eno1 and lo. But after cold boot, it only gives lo.

After downgrading to the 3.12 kernel, I did a reboot, checked with uname -r that the kernel was actually that one, and the network worked just fine. Then shutdown, and power up again, and the issue appeared.

I lost the track of time during these last few weeks (writing thesis). So, I'm not really sure when it appeared. It was actually another user of the computer who reported the problem. I tried to fix it upgrading to 3.16, but didn't work, and I really don't remember how many times I upgraded since it started. That's why I went with the oldest kernel available in my cache.

What baffles me is that I don't understand what's the difference between a cold boot and reboot, at least for linux. That's why it seems like a BIOS related problem, but there's nothing there, at least to my knowledge. A hardware failure should be more random, I think, and since the issue appeared, the network is always down after power up and always works after reboot. I also tried leaving the GRUB menu for a couple of minutes, to see if the LAN module of the motherboard have some sort of delay, but didn't help.

I wrote an email to the Intel guys, linking to this post, to see if they shed any light on this. I know that in some cases, after unplugging the computer, the BIOS behaves different, like the Fast Boot optimization is disabled. My BIOS was locked with this Fast Boot feature enabled. That's why I know I haven't changed it in ages, and to access the BIOS menu, I have to either open the box and remove the battery or, after reading about Intel Fast Boot, simply unplug the computer to disable it and access the menu.

phollox · 2014-08-19 11:45:49

Ok, I went into the BIOS menu directly after power up, to triple check if there was any power option that could help. Changed some stuff, just to try (activate network boot, wake on LAN), saved the changed and exit. The boot cycle went normally and then I did have network. I shutdown, power up again without getting into BIOS, and no network.

Next logical step: get into the BIOS menu after power up, and exit it discarding any changes. No network.

Finally, getting into BIOS menu after power up, save the configuration WITHOUT actually making any change. I did have network.

So, it seems like the LAN module is only fully available at the second power cycle of the motherboard. When no changes in BIOS are made, the GRUB appears directly, but when the BIOS config is saved, even without changes, it does the full cycle, flashing the Intel logo again.

My last test of the day is reboot the computer after power up in the GRUB console. After that, Linux started with network. Thus, it seems that there is some sort of hardware conflict in the BIOS, or my machine is cursed. Either way, I'm out of ideas.

Thanks

Lone_Wolf · 2014-08-19 12:51:48

phollox, that does very much sound like a firmware issue .

Are you able to disable "Fast Boot" , if so does it stick and change anything ?

R00KIE · 2014-08-19 14:00:50

Just a guess, how old is that motherboard? Might it be that the cmos battery is weak and causing problems?

phollox · 2014-08-19 14:40:50

Lone_Wolf: yes, I disable Fast Boot. The BIOS configurations remain after power down. I'll try unplugging the machine, to test.

R00KIE: my MB is around two years old. The CMOS battery issues, to my understanding, usually appear with the system date, or the system not booting because it can't identify the Hard Drive. But tzdata and the auto options in the BIOS correct that in simple cases (I only have one hard drive. Yes, shame, I know). I'll payore attention to this, but as I said to Lone_Wolf, the BIOS seems to hold the configuration without issues

EDIT: the BIOS configuration holds after unplugo the machine. Also the time is correct. And all the Network boot options I put there to test if they have any effect are still there. Is there any other way to test the CMOS battery? A magic command that tells me the % of charge? Anyway, I guess is awesome that we established, almost without doubt, that the problem is not Arch related, but you guys are still answering my post. Thanks for your interest. I hope the Intel guys I forwarded this thread read it soon. My wife keeps telling me that I broke the computer with this "Linux" thing, and I really need to show her she's wrong, at least with that particular issue. Please Intel guys, help me win this battle :-)

Last edited by phollox (2014-08-19 14:58:33)

R00KIE · 2014-08-19 16:07:31

I mentioned the cmos battery because one of my machines had a mostly dead cmos battery and the only symptom would be that the time would not move forward when the machine was unplugged from the wall socket (actually turned off the power with the button in the power supply). Every setting and even the last time before the machine was unplugged would be kept, just time would not move forward.

The only sure way I know of testing the cmos battery is taking it out and measuring the voltage, whatever the bios may report about the battery voltage may be wrong. I mentioned it because it's better to eliminate the simple problems before trying to hunt the complicated ones and it's easy to forget about this little simple thing.

phollox · 2014-08-19 17:17:35

Got you. It's my HTPC. Opening the box means moving the TV cabinet, which also translates in realizing how much dust is there, and that would lead to a cleaning frenzy. That's why I was postponing it. But it also gives me the excuse for getting a multimeter. At the hardware store, when my wife asks why do I need new tools, I will quote you, but as an Expert, not as a R00KIE.

phollox · 2015-01-08 08:05:44

I haven't been able to test the battery of the MB. Been quite busy (something that start with "T" and ends with "hesis"). However, it bothers me that the issue is still open in the forums. I'll mark it as closed, for the moment. When I solve it (if I solve it), I'll post whatever I did here. Thanks

jasonwryan · 2015-01-08 08:55:56

Please don't use [Closed], it denotes a locked thread; use [Resolved] or [Suspended]...

phollox · 2015-01-09 01:07:33

jasonwryan wrote:

Please don't use [Closed], it denotes a locked thread; use [Resolved] or [Suspended]...

Thanks for the advice. Changed

wadapad · 2016-12-16 17:59:42

Good day, friends! I got same issue with my Dell Latitude e6430. Is there any solution yet? Thanks in advance.

WorMzy · 2016-12-17 16:09:42

OP hasn't been seen on the forums for almost two years. It's safe to assume they gave up on getting this to work on Arch.

https://wiki.archlinux.org/index.php/Co … bumping.22

Closing.

Arch Linux

#1 2014-08-16 22:10:16

[SUSPENDED] No network interface after cold boot

#2 2014-08-17 09:32:25

Re: [SUSPENDED] No network interface after cold boot

#3 2014-08-17 15:14:47

Re: [SUSPENDED] No network interface after cold boot

#4 2014-08-18 05:46:49

Re: [SUSPENDED] No network interface after cold boot

#5 2014-08-18 10:03:15

Re: [SUSPENDED] No network interface after cold boot

#6 2014-08-18 13:08:16

Re: [SUSPENDED] No network interface after cold boot

#7 2014-08-18 17:04:54

Re: [SUSPENDED] No network interface after cold boot

#8 2014-08-18 17:14:30

Re: [SUSPENDED] No network interface after cold boot

#9 2014-08-19 05:19:46

Re: [SUSPENDED] No network interface after cold boot

#10 2014-08-19 08:10:06

Re: [SUSPENDED] No network interface after cold boot

#11 2014-08-19 11:23:22

Re: [SUSPENDED] No network interface after cold boot

#12 2014-08-19 11:45:49

Re: [SUSPENDED] No network interface after cold boot

#13 2014-08-19 12:51:48

Re: [SUSPENDED] No network interface after cold boot

#14 2014-08-19 14:00:50

Re: [SUSPENDED] No network interface after cold boot

#15 2014-08-19 14:40:50

Re: [SUSPENDED] No network interface after cold boot

#16 2014-08-19 16:07:31

Re: [SUSPENDED] No network interface after cold boot

#17 2014-08-19 17:17:35

Re: [SUSPENDED] No network interface after cold boot

#18 2015-01-08 08:05:44

Re: [SUSPENDED] No network interface after cold boot

#19 2015-01-08 08:55:56

Re: [SUSPENDED] No network interface after cold boot

#20 2015-01-09 01:07:33

Re: [SUSPENDED] No network interface after cold boot

#21 2016-12-16 17:59:42

Re: [SUSPENDED] No network interface after cold boot

#22 2016-12-17 16:09:42

Re: [SUSPENDED] No network interface after cold boot

Board footer