Black screen

fyohs · December 10, 2023, 4:39pm

Hello,

Something strange happened with my PC.

I wanted to copy files from my GrapheneOS, I did use the same pendrive as usually. I did format it on GrapheneOS, then copy file’s. After that just connect to my PC. QubesOS was already running. When I connect pendrive I got many notification about system discontent USB device’s.

Keyboard and muse got discontent by system. I don’t know why, I don’t understand. I pulled out pendrive but nothing changed. Without choice I turned off my PC by power bottom. Then started the machine again. Now it does not boot to the system. Only black screen.

Computer is restarting by itself the only option I have it is picture: blue screen I can choice system. I don’t know what to do?
Can it be fixed?

I did not change anything in BIOS.

apparatus · December 10, 2023, 6:38pm

When you have the boot-screen (“Qubes, with Xen hypervisor”)

hit e to edit the config
locate the quiet keyword on the kernel-line and remove it
Press Ctrl+x to boot in verbose mode

Check the errors that you’ll see on the screen and try to search them on forum/github issues.

fyohs · December 11, 2023, 6:46am

Like those? Is this what I should check?

apparatus · December 11, 2023, 6:57am

Yes, then search for messages and you’ll find this issue:

github.com/QubesOS/qubes-issues

Kernel panic with Xen 4.8.3-7

opened 08:41AM - 21 May 18 UTC

closed 04:10AM - 29 Nov 18 UTC

AlmightyLaxz

T: bug C: kernel P: major

### Qubes OS version:  R4.0 ### Affected component(s): Xen --- ### Steps to reproduce the behavior:  `sudo qubes-dom0-update` Reboot when finished ### Expected behavior: Qubes OS boots successfully ### Actual behavior: Kernel panic right after booting from GRUB When booting: ``` Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) CPU: 3 PID: 1 Comm: swapper/0 Not tainted 4.14.35-1.pvops.qubes.x86_64 #1 Hardware name: *name* Call Trace: dump_stack+0x5c/0x85 panic+0xe4/0x252 mount_block_root+0x358/0x522 ? do_early_param+0x19e/0x19e prepare_namespace+0x27d/0x2da ? do_early_param+0x19e/0x19e kernel_init_feeable+0x2ea/0x32f ? rest_init+0xb0/0xb0 kernel_init+0xa/0xfc ret_from_fork+0x35/0x40 Kernel Offset: Disabled ``` ### General notes: Booting is successful when selecting `Qubes, with Xen 4.8.3 and Linux 4.14.18-1.pvops.qubes.x86_64` from GRUB boot menu, but `Qubes, with Xen 4.8.3 and Linux 4.14.35-1.pvops.qubes.x86_64` results in kernel panic. I noticed in the GRUB configurations for each that the new 4.14.35-1 option is missing two lines that are present in the 4.14.18-1 menu option: ``` echo 'Loading initial ramdisk ...' module --nounzip /initramfs-4.14.18-1.pvops.qubes.x86_64.img ``` Looking in the /boot folder there is no initramfs image for 4.14.35-1, only for 4.14.18.1, but there is a vmlinuz file for each which looks like the problem. I am not yet familiar with kernel updates or what has gone wrong here so help would be appreciated. Packages altered during dom0 update (from `sudo dnf history info`): ``` Upgraded qubes-gui-dom0-4.0.7-1.fc25.x86_64 @anaconda/rawhide Upgrade 4.0.8-1.fc25.x86_64 @qubes-dom0-cached Upgraded python3-xen-2001:4.8.3-3.fc25.x86_64 @anaconda/rawhide Upgrade 2001:4.8.3-7.fc25.x86_64 @qubes-dom0-cached Upgraded xen-2001:4.8.3-3.fc25.x86_64 @anaconda/rawhide Upgrade 2001:4.8.3-7.fc25.x86_64 @qubes-dom0-cached Upgraded xen-hvm-2001:4.8.3-3.fc25.x86_64 @anaconda/rawhide Upgrade 2001:4.8.3-7.fc25.x86_64 @qubes-dom0-cached Upgraded xen-hypervisor-2001:4.8.3-3.fc25.x86_64 @anaconda/rawhide Upgrade 2001:4.8.3-7.fc25.x86_64 @qubes-dom0-cached Upgraded xen-libs-2001:4.8.3-3.fc25.x86_64 @anaconda/rawhide Upgrade 2001:4.8.3-7.fc25.x86_64 @qubes-dom0-cached Upgraded xen-licenses-2001:4.8.3-3.fc25.x86_64 @anaconda/rawhide Upgrade 2001:4.8.3-7.fc25.x86_64 @qubes-dom0-cached Upgraded xen-runtime-2001:4.8.3-3.fc25.x86_64 @anaconda/rawhide Upgrade 2001:4.8.3-7.fc25.x86_64 @qubes-dom0-cached ``` --- ### Related issues:

And possible fix to boot older kernel (or chroot from LiveCD) and regenerate grub config and initramfs.