You are not logged in.

#1 2020-01-11 18:18:50

Flupsi
Member
Registered: 2020-01-11
Posts: 3

[SOLVED] Any boot medium hangs at 'triggering uevents'

I had a working installation with Efistub loading the kernel directly. This worked fine until recently. I honestly don't know what I did that caused the error.

Since yesterday, the system won't boot:
- Uefi boot entries are visible, but when I select them from the Bios Menu, I am thrown back into the Bios after a second.
- The Archiso boot medium now hangs at udev, then the screen turns off. The very same usb drive worked before yesterday, so I assume it must be the hardware that has a problem.

I tried these things:

(1) updated the Bios
-No change-

(2) tried different kernel parameters with the archiso usb medium, following https://bbs.archlinux.org/viewtopic.php?id=151259.
Each time, it hangs. These are the three last lines on my screen, in each case:

  with the default kernel parameters:

running early hook [archiso_pxe_nbd]
running hook [udev]
Triggering uevents...

  loglevel=7

nouveau 0000...DRM: using COPY for buffer copies
ata1: SATA link down (SStates 0 SControl 300)
ata9: SATA link down (SStates 0 SControl 300)

  iommu=off loglevel=7 libata.ata_probe_timeout=2

scsi host6: ahci
scsi host7: ahci
ata1: SATA max UDMA/133 abar m131072@0xf6780000 port 0xf6780100 i

(3) I removed my hard drive (nvme) and my USB Wifi stick so that the only attached devices are the graphics card (nvidi gtx1600), the keyboard/trackball combo (PS2 port), and the boot medium (USB3). I tried the following kernel parameters, and these were the last 3 lines before the screen would go black:

  iommu=off loglevel=7 libata.ata_probe_timeout=2

scsi host8: ahci
ata9: SATA max UDMA/133 abar m4096@0xf68C000) port 0xf6808100 irq 42
xhci_hcd 000:01:00.0: hcc params 0x0200cf81hci version 0x110 qu

  debug ignore_loglevel

scsi host1: ahci
scsi host2: ahci
xhci_hcd 0000:01:00.0: xHCI Host Controller

(4) What can I do now? As you see, I'm not familiar enough with the boot process to find the problem source.

Last edited by Flupsi (2020-01-13 09:19:42)

Offline

#2 2020-01-12 12:20:16

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 7,637

Re: [SOLVED] Any boot medium hangs at 'triggering uevents'

nouveau 0000...DRM: using COPY for buffer copies

Looks like you have an nvidia videocard, try blacklisting the nouveau kernelmodule .

https://wiki.archlinux.org/index.php/Ke … and_line_2


Multi-init booting with apg Openrc and systemd coexisting
Automounting : not needed, i prefer pmount
Aur helpers : makepkg + my own local repo === rarely need them

Offline

#3 2020-01-12 16:04:53

Flupsi
Member
Registered: 2020-01-11
Posts: 3

Re: [SOLVED] Any boot medium hangs at 'triggering uevents'

Cool, module_blacklist=nouveau made the archiso boot again :-) Thank you!
I'll now add that kernel parameter to the boot entry of my installation and check if it's going to boot.

Offline

#4 2020-01-13 09:16:04

Flupsi
Member
Registered: 2020-01-11
Posts: 3

Re: [SOLVED] Any boot medium hangs at 'triggering uevents'

Update: neither efibootmgr (via arch-chroot) nor bcfg (via Uefi-shell) did create bootable entries this time, even with module_blacklist=nouveau. Then I found the reason: a lot of libs in /usr/lib were corrupted. I tried to repair them but even simple tools like ls were broken so I decided to salvage my files and reinstall arch.

This is how the catastrophe was caused: I had started a system upgrade while a video was running. Then, the nvidia driver caused the system to freeze. I pressed the power button to down the computer as pacman was still running. This broke my installation. Well, lesson learned ;-) Next time, I'll not run the system upgrade in X.

Offline

Board footer

Powered by FluxBB