My mind…that´s the prob… this board have one m.2 nvme pcie and one m.2 sata slot.
But your current inxi tells me no nvme is connected, only 1x sata + 1x usb. (or i’m blind)
That tells me only something about the controller and the size but nothing if it’s a m.2 sata or m.2 nvme pcie
I´m a little bit confused about it, what you like to do. An os doesn’t care whether the boot disk is an nvme or sata/hdd/usb. What matters is how I configure the uefi bios and which os should boot first or which boot manager (grub/refind..etc) is the master.
You have “only” delete the nvme or real connected to your first nvme slot ?
If you real connected to the first slot… pls reverse and next time read the docu from your motherboard, before.
If you have the os default installed, before all drives deleted (nvme +sata), of course you have current only your sata hardware. Then use partitionmanager → format the unallocated drive with /exfat/ext4/btrfs, mountpoint to what you like/need → apply → you can use the drive. (mount the drive or make a reboot, of course)
Let me summarize the whole thing briefly: a 2.5” 240GB Crucial BX200 SATA SSD is installed, with Windows and Garuda as dual boot. As soon as the OP installs the 1TB CUSU PCIe Gen4 M.2 NVMe, neither the installed Garuda Linux nor the Garuda live.iso boots (Failed to start Journal Service). Windows boots perfectly, recognizes the NVMe and a short error scan shows no problems with the NVMe.
Possibly the kernel has a problem with the NVMe (machine-id bug, missing/wrong/failed nvme-modul or whatever). Try this:
Remove the NVMe, boot Garuda and install the linux-lts kernel and the linux-lts-headers. Then shut down the computer, reinstall the NVMe and boot Garuda with the Linux LTS kernel (you can select `linux-lts in the grub menu).
Optionally, you can also try to boot the Garuda XFCE live.iso with the pre-installed LTS kernel when the NVMe is installed: garuda-xfce-linux-lts-250308.iso.
perhaps this
check pls inside bios if you can change pci express bandwith for the m.2 slots. Advanced bios, if possible, default is auto, switch to Pcie X4 mode, save, test again.
Hmm..if.. only
what nepti wrote in his post
Test the xfce live.iso or install the lts kernel.
If this also fails..sorry no idea..then. Only one (for myself) ..this “cusu” nvme.. i read about this the first time and about the motherboard…the same.
Perhaps bios update but from where ?
This is an m.2 nvme drive connected to a nvme slot on my motherboard.
Also I can ensure that the nvme is connected via an m.2 nvme slot and not an m.2 sata slot
We have covered this topic before, but I would like to repeat my advice:
Do you have the possibility to install the NVMe on another mainboard and boot a Linux live.iso as a test, for example on a friend’s computer? That way we could find out whether the NVMe is preventing Linux from booting or whether the QIYIDA E5-A99 mainboard/BIOS is the cause.
I just tried xfce and received the error <PCIe Bus Error: severity=Correctable. Type=physical layer. (Receiver>
What is after reciever is cut off by my monitor
Great, that’s the first useful hint. This indicates that either the BIOS or the controller of the NVMe has not implemented the PCIe protocol correctly. The linux kernel tries to implement this specification exactly, while windows doesn’t really care - that’s why windows boots with the NVMe but Linux does not.
Remove the NVMe again, boot your installed Garuda, open the “Garuda Boot Options” and add the kernel parameter pcie_aspm=off. Then test whether Garuda boots with the NVMe installed - if not, try the following kernel parameters (first individually, then you can also combine them for testing): pcie_port_pm=off and pci=noaer.
If no one has already mentioned it already, you might want to check if the drive that is preventing booting properly has up to date firmware installed on it.
You also might want to test out the linux-mainline kernel as it has the most support for the newest hardware.
thank you all so much for the effort to help me out. Adding pcie_asp=off did end up working which while I am extremely happy to find a solution I find it funny that I did end up trying this solution a while back but in my bios but I think I must have forgotten to save changes as it didn’t end up working
Again thanks to everyone who helped out I really appreciate it