You are not logged in.
I did a normal "pacman -Syu" after a long time of not updating. Now the system freezes at random places at boot.
e.g. "Starting Flush Journal to Persistent Storage", or after mounting /temp
After Probing EDD, I get:
ata1: COMRESET failed (errno=-16)
I don't know if I had this before the update, turning off what appears to me to be ata1 in bios doesn't seem to change anything.
Booting in rescue mode is giving me the same behavior, only emergency mode works.
In emergency mode "journalctl -xb" is empty, running fsck on all disks doesn't seem to help and says they are clean.
dmesg doesn't seem to give me anything interesting either.
I think it might be because of that kernel package split, I didn't install any of those firmwares and I don't know if I need any or how to check this.
I'm a bit lost here, it seems I cannot easily use network in the emergency mode, to maybe install some things.
Any ideas on how to proceed? Or any useful guides, what one can do in such a situation?
Last edited by ziustag (2022-05-04 05:59:29)
Offline
Linux-firmware has been split - not the kernel. These are your additional options depending on your hardware (get more info with 'lspci'):
core/linux-firmware-bnx2x 20220411.705f19a-1
Firmware files for Linux - bnx2x / Firmware for Broadcom NetXtreme II 10Gb ethernet adapters
core/linux-firmware-liquidio 20220411.705f19a-1
Firmware files for Linux - liquidio / Firmware for Cavium LiquidIO server adapters
core/linux-firmware-marvell 20220411.705f19a-1
Firmware files for Linux - marvell / Firmware for Marvell devices
core/linux-firmware-mellanox 20220411.705f19a-1
Firmware files for Linux - mellanox / Firmware for Mellanox Spectrum switches
core/linux-firmware-nfp 20220411.705f19a-1
Firmware files for Linux - nfp / Firmware for Netronome Flow Processors
core/linux-firmware-qcom 20220411.705f19a-1
Firmware files for Linux - qcom / Firmware for Qualcomm SoCs
core/linux-firmware-qlogic 20220411.705f19a-1
Firmware files for Linux - qlogic / Firmware for QLogic devicesLast edited by dogknowsnx (2022-04-30 13:07:02)
thanks for the clarification, I don't seem to have any of those devices (judging by lspci).
It's a simple system, just a bunch of onboard Intel stuff and some Realtek ethernet.
So I suppose it's something else?
But I'm still mostly lost and confused, I don't know how to further analyze the problem, if I don't see a proper error message.
The system just keeps hanging while booting.
Offline
Intel is covered by 'linux-firmware', but apparently your system was working without it before the update.
Anyhow, you can use your installation medium to chroot into your system and try the update again and install additional firmware/packages [EDIT], or 'linux-lts' (you didn't mention when you last updated your system) - I'd recommend checking your top mirror first to make sure it is fully synced.
Last edited by dogknowsnx (2022-04-30 13:50:35)
Ok thanks for the help, turned out it was something completely different:
Apparently the nvidia GTX 650 is no longer supported in the standard nvidia driver and I had to fall back to driver 470XX provided by the AUR.
I think the reason it got stuck at random places was, that I also have an onboard GPU that was still enabled :S
After installing all the linux-firmware thingies and trying linux-lts I got desperate and went through the bios to see if I can disable some unneeded things.
As soon as I turned off the onboard GPU I could see the warning about the GPU driver.
I'm not really sure why I didn't see any of this in the logs, or why the system got stuck at some random place during boot.
But I think the system tried to default back to the onboard GPU and somehow got stuck there, probably at random places because systemd starts things in parallel.
Offline
Glad that you were able to sort it out, reporting about it AND marking the thread. (Not so happy about not even mentioning nvidia at all in the first place
)
Last edited by dogknowsnx (2022-05-04 09:59:35)