Thrown into ROOTFS with no usb control.

[RealMrCactus]

Before reporting an issue, please check for relevant keywords in the issues search bar, including closed issues. The solution to your issue might be there already !

Describe the bug

• Which OS do you encounter the bug on? Arch Linux
• A clear and concise description of what the bug is. Thrown into ROOTFS with no control over it i have to turn my PSU off to turn my system off and the normal Linux kernel also has been effected as my identical displays now show one as normal and the other at 640x480 labeled as NVIDIA
• Attach the contents of your logs folder by drag & dropping each file into this message. Special note for Arch users: please run makepkg [args] | tee shell-output.log for more logging! customization.cfg.txt prepare.log.txt system-info.txt

Let me know if you would like me to do the more logging.

[RealMrCactus]

The display issue was unrelated.

[AdelKS]

Hey, can you also attach the file shell-output.log (just append a .txt to it and you can drag and drop it here). I am suspecting either modprobed-db or a mkinitcpio configuration issue (or are you using dracut ? )

[RealMrCactus]

I'm using mkinitcpio when I get home in like 6 hours I can give you the stuff you requested

[RealMrCactus]

Sorry about not getting back I've been busy but could my issue possibly be that I'm using an Nvidia GPU and I'm supposed to have a package before installing? Because all I did after it compile as far as I'm aware was run mkinitcpio -P and add the entries to limine

[Tk-Glitch]

You need a dkms nvidia package so the module is rebuilt against your custom kernel(s). The prebuilt distro-provided nvidia non-dkms package is built against the distro-provided kernel and thus not compatible with any other kernel. We are offering a nvidia package https://github.com/Frogging-Family/nvidia-all which defaults to dkms, but the Arch package https://archlinux.org/packages/extra/x86_64/nvidia-dkms/ will work just fine as well. If you already have the dkms package installed, then something needs fixing on our end :D

[RealMrCactus]

You need a dkms nvidia package so the module is rebuilt against your custom kernel(s). The prebuilt distro-provided nvidia non-dkms package is built against the distro-provided kernel and thus not compatible with any other kernel. We are offering a nvidia package https://github.com/Frogging-Family/nvidia-all which defaults to dkms, but the Arch package https://archlinux.org/packages/extra/x86_64/nvidia-dkms/ will work just fine as well. If you already have the dkms package installed, then something needs fixing on our end :D

I do not I will try nvidia-dkms and see how it goes if it works I will close the thread if not I'll inform

[RealMrCactus]

Yeah dkms did not work

[RealMrCactus]

Mind you the normal arch kernel works so uhhh yeah after compiling I just mkinitcpio -P (after grabbing dkms of course)

[Tk-Glitch]

This looks like missing filesystem driver to me. Using the diet config or modprobed-db?

[RealMrCactus]

This looks like missing filesystem driver to me. Using the diet config or modprobed-db?

Uhhh I dunno all I do is makepkg -si and then mkinitcpio -P

[RealMrCactus]

Also the normal kernel works so?

[RealMrCactus]

Hello?

[Tk-Glitch]

Please check that thread and see if it's the same issue: https://bbs.archlinux.org/viewtopic.php?id=237066 I didn't think much about that early hook warning of yours initially, but it's most definitely abnormal. The file should be there on Arch's kernel.

We have zero reproduction case of your issue at this point. To be fair it doesn't make much sense for our package to be the culprit here considering you're using the default defconfig (which is Arch's) along with next to no customization. So the issue is more likely related to your setup, and that warning tends to solidify that theory. Also, which bootloader are you using?

[RealMrCactus]

Please check that thread and see if it's the same issue: https://bbs.archlinux.org/viewtopic.php?id=237066 I didn't think much about that early hook warning of yours initially, but it's most definitely abnormal. The file should be there on Arch's kernel.

We have zero reproduction case of your issue at this point. To be fair it doesn't make much sense for our package to be the culprit here considering you're using the default defconfig (which is Arch's) along with next to no customization. So the issue is more likely related to your setup, and that warning tends to solidify that theory. Also, which bootloader are you using?

My bad for late reply I'll check out the page you sent later today and I'm using limine

[RealMrCactus]

so i think i found my issue

[RealMrCactus]

well im unsure as id like to recompile the kernel but bore isnt avail for 6.9.3 and i cant try the version im currently on 6.9.1

[RealMrCactus]

was the issue im just dumb lol