An error with e1000e causes permanent freeze

bulbik · 2026-04-15 20:19:22

So im kinda new to arch i have been using other distros for some time but i tried installing arch rn and i ran into a problem with e1000e. I have Intel 1219-V adapter which causes arch to freeze during the boot when it gets to the internet. Currently using my phone and a usb to get internet connection. Is there anyway to fix it? I even updated the BIOS and the situation stayed the same. Atp i just dont know what to do.

seth · 2026-04-15 21:24:11

causes arch to freeze during the boot when it gets to the internet

Does the boot eventually continue? Do you experience freezes when trying to establish a connection over that NIC after the boot?
Generally we'll need to see some data on the situation .

sudo journalctl -b | curl -s -H "Accept: application/json, */*" --upload-file - 'https://paste.c-net.org/'

will upload the system journal to c-net.org and hand you a link to share.

bulbik · 2026-04-15 21:27:56

seth https://paste.c-net.org/GiantsCahoots this is the link i got and also it just freezes completely. No matter what i tried to do or update it simply doesnt work. Im not sure about all the stuff the stuff you are saying so please sorry for me being a noob Also i would like to mention im on USB Modem rn so im not sure that e1000e is shown in the report

Last edited by bulbik (2026-04-15 21:28:32)

seth · 2026-04-15 21:34:52

pcie_aspm=off e1000e.SmartPowerDownEnable=0 modprobe.blacklist=e1000e

Does "modprobe e1000e" alone cause the freeze?
Do you get this w/ the LTS kernel?
Try to disable systemd-networkd (so the module loads but the link not used)

If this freezes during the boot, what are the last messages?

bulbik · 2026-04-15 21:41:35

seth wrote:

Does "modprobe e1000e" alone cause the freeze?
Do you get this w/ the LTS kernel?
Try to disable systemd-networkd (so the module loads but the link not used)
If this freezes during the boot, what are the last messages?

So the modprobe e1000e causes the freeze automatically. I installed lts and it doenst work. Can u give me a guide to disable systemd-netword? I will try this and if it doesn't work i will reboot without it all and send u a screenshot with logs.

seth · 2026-04-15 21:44:32

https://wiki.archlinux.org/title/System … mctl_usage

systemctl disable --now systemd-networkd

bulbik · 2026-04-15 22:01:29

seth wrote:

https://wiki.archlinux.org/title/System … mctl_usage
systemctl disable --now systemd-networkd

.
So unfortunately that didnt work either. I will upload the last screenshot however i doubt there is anything useful since it autloagged after loading in the soundcard. Screenshot: https://prnt.sc/8k4up_3Foy_Z
I had loglevel 7 turned on

Last edited by bulbik (2026-04-15 22:02:56)

seth · 2026-04-16 06:13:07

1f.3 is a Cannon Lake PCH cAVS on the same bus and that acts up, too.

Apr 15 16:08:52 bulba kernel: snd_hda_intel 0000:00:1f.3: enabling device (0000 -> 0002)
Apr 15 16:08:52 bulba kernel: snd_hda_intel 0000:00:1f.3: Unknown capability 0
Apr 15 16:08:52 bulba kernel: snd_hda_intel 0000:01:00.1: enabling device (0000 -> 0002)
Apr 15 16:08:52 bulba kernel: snd_hda_intel 0000:01:00.1: Force to non-snoop mode
Apr 15 16:08:52 bulba kernel: snd_hda_intel 0000:01:00.1: bound 0000:01:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
Apr 15 16:08:52 bulba kernel: snd_hda_intel 0000:00:1f.3: CORB reset timeout#1, CORBRP = 0
Apr 15 16:08:52 bulba kernel: snd_hda_intel 0000:00:1f.3: no codecs found!

Install https://archlinux.org/packages/extra/x8 … -firmware/, see whether the sound chip behaves better and whether its problems spilled over to the ethernet chip

bulbik · 2026-04-17 18:23:11

seth wrote:

1f.3 is a Cannon Lake PCH cAVS on the same bus and that acts up, too.

Apr 15 16:08:52 bulba kernel: snd_hda_intel 0000:00:1f.3: enabling device (0000 -> 0002)
Apr 15 16:08:52 bulba kernel: snd_hda_intel 0000:00:1f.3: Unknown capability 0
Apr 15 16:08:52 bulba kernel: snd_hda_intel 0000:01:00.1: enabling device (0000 -> 0002)
Apr 15 16:08:52 bulba kernel: snd_hda_intel 0000:01:00.1: Force to non-snoop mode
Apr 15 16:08:52 bulba kernel: snd_hda_intel 0000:01:00.1: bound 0000:01:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
Apr 15 16:08:52 bulba kernel: snd_hda_intel 0000:00:1f.3: CORB reset timeout#1, CORBRP = 0
Apr 15 16:08:52 bulba kernel: snd_hda_intel 0000:00:1f.3: no codecs found!

Install https://archlinux.org/packages/extra/x8 … -firmware/, see whether the sound chip behaves better and whether its problems spilled over to the ethernet chip

So i tried both lts and normal linux with this however it lagged at the exact same spot. Its an issue with the ethernet chip exactly because when i blacklist it it turns on. Idk if i can trust chatgpt and claude but they tell me that its a highly popular problem with my exact ethernet chip 1219-V. Idk if i installed the lts correctly because im still a newbie at all this

seth · 2026-04-17 21:41:26

Intel 1219-V isn't exactly a new chip and "system just completely freezes" isn't a typical failure either and LLMs will happily and confidently assert any nonsense.
Are the snd_hda_intel errors gone w/ the sof-firmware installed?

Please post a journal for a LTS boot w/ sof-firmware installed.

bulbik · 2026-04-17 21:46:55

So i will try to reinstall the arch completely and redo everything cuz i messed up while trying to fix everything using AI. Is there any way we could contact each other in something like discord so i could show u what exactly happens during the boot and the logs? I think it would be a way faster communication rather than replying to each other without much understanding

seth · 2026-04-17 22:12:54

Looking at a screen that stops updating will hardly tell anything.
My main concern (b/c of the issues w/ the audio chip) is that there's an issue w/ the bus that gets exposed when talking to the ethernet chip at the other end - we want to rule that out.
Can you btw. use the ethernet chip w/ eg. https://grml.org ?

bulbik · 2026-04-17 22:16:16

seth wrote:

Looking at a screen that stops updating will hardly tell anything.
My main concern (b/c of the issues w/ the audio chip) is that there's an issue w/ the bus that gets exposed when talking to the ethernet chip at the other end - we want to rule that out.
Can you btw. use the ethernet chip w/ eg. https://grml.org ?

I mean as i said i just wanted to use discord so u could explain some stuff while i would do it since im kind of noob because most of my life i was using either windows or user friendly linux distributives like fedora or ubuntu. Thats why, if you dont mind and have free time of course, to proceed in discord for example so i could follow ur instructions and u would rule out stuff so we could fix my problem way quicker. If not lets just proceed here and i will follow your lead with instructions and ruling out stuff. Also i would like to mention that with ai i tried running e1000e later than usual and it would freeze completely at the moment of its run if that gives u any helpful info. Also i have some screenshots of logs after the "freeze boot" that i managed to get through rescue mode i can show u if that would be any help

Last edited by bulbik (2026-04-17 22:24:05)

Arch Linux

#1 2026-04-15 20:19:22

An error with e1000e causes permanent freeze

#2 2026-04-15 21:24:11

Re: An error with e1000e causes permanent freeze

#3 2026-04-15 21:27:56

Re: An error with e1000e causes permanent freeze

#4 2026-04-15 21:34:52

Re: An error with e1000e causes permanent freeze

#5 2026-04-15 21:41:35

Re: An error with e1000e causes permanent freeze

#6 2026-04-15 21:44:32

Re: An error with e1000e causes permanent freeze

#7 2026-04-15 22:01:29

Re: An error with e1000e causes permanent freeze

#8 2026-04-16 06:13:07

Re: An error with e1000e causes permanent freeze

#9 2026-04-17 18:23:11

Re: An error with e1000e causes permanent freeze

#10 2026-04-17 21:41:26

Re: An error with e1000e causes permanent freeze

#11 2026-04-17 21:46:55

Re: An error with e1000e causes permanent freeze

#12 2026-04-17 22:12:54

Re: An error with e1000e causes permanent freeze

#13 2026-04-17 22:16:16

Re: An error with e1000e causes permanent freeze

Board footer