The only way I would be able to run the setup assistant is from the live environment since the install is not booting to the desktop. Are you suggesting that I chroot into the newly installed OS and use the live setup assistant to install the nVidia drivers before doing the reboot?
Iâm not sure whether this would be of help here since the systems donât boot at all.
Itâs really weird, like @BluishHumility I installed the dr460nized ISO on a spare notebook and didnât have any of the issues other people face.
Further troubleshooting steps might be increasing the log level in GRUB, which might give hints about what went is going on:
I have checked with CachyOS, EndeavourOS, ArcoLinux using their latest ISOâs and theyâre all fine. Now that said it looks like the testing ISOâs donât like my monitor, the video card seems to be fine. the below is from my installed Garuda for the monitor and video card. Iâm going to go into the zen ISO and do a garudainxi and add it to this post. Maybe that will give use some idea about whats going on there.
Mine was a rolling upgrade of Dr460nized on the old Lenovo x250 work-horse (Scandinavian version with Estonian âSun Type 6/7â keyboard) so not an install from scratch.
In general things work but having serious but not urgent problems:
kwin_wayland appears to be the culprit blocking ProtonVPN GUI from successfully opening a secure working network connection. My work-around for this is to use the PVPN CLI which reportedly is not well-maintained anymore. I am more concerned about why wayland needs to be a true or pseudo man-in-the-middle of my personal computing network affairs. See interesting github posts about this problem.
getting my virtual keyboards working (previously used Ibus m17n and trying to get it back) and now have to start from scratch and choose correctly between fcitx, fcitx5, and Ibus and try to get something to show up in the system settings. (Garuda Assistant settings manager attempts return journal errors of missing files but Octopi and Pamac show files as installed so conflicts presumably are blocking anything from loading other than the main installed keyboard with no virtual keyboards loading). Kwin_wayland is also appearing (via Conky) active in this and pipewire also appears to be interacting in the process). Kden issued notifications about the keyboard issue but trying to resolve it did not work although I have not had much spare time to work on it properly other than to confirm the so-called missing packages were installed.
These issues are not as dire a priority as the black screen issue, but I am wondering there will ever be a way for Dr460nized to allow users to choose between Xorg and Wayland since I will never need a dual boot or Vine vm on this laptop. Or another Garuda OS other than Dr460nizedâŠ
I realized I didnât change the word âsummaryâ to the name of the ISO when I posted this (it was getting lateâŠthis was actually the last machine I did last night even though it is posted earlier in the list).
I clicked took a peek at the inxi to see which one it was, but waitâŠ
Oops! I think I must have installed an older ISO by accident.
So I reinstalled on this same machine with garuda-dr460nized-linux-zen-240319.iso, and now:
Loading Linux linux-zen ...
Loading initial ramdisk ...
error: you need to load the kernel first.
Press any key to continue..._
Bingo!
This leads me to my first theory:
It seems possible the issue is related to AMD CPUs.
Try to install the iso from 240319 and try to partition the hdd manual. Then i try to give the partition a label like GarudaKDE2_sys for example. If i do that, the installer fails by the partition generation before the install starts. I try also differnt namings, and sometimes the label was shown in uppercase letters.
Try it with the iso from 231029 and get the same error. Maybe its not a garuda problem⊠and itâs no problem, because i can give the partitions a label after the installation. But maybe it can be fixed in the future to improve the installation if some idiots like me try to do the naming during the installation.
Confirm also the installation of the new garuda iso wonât boot after install, so itâs fine that this was not my fault
I have also an AMD CPU with Nvidia 2080.
and the following must be said : I do a lot of distro hopping to find my personal best distro with your KDE edition. The garuda tools are genius to use and do the maintenance of the system so easy. Great work !!!
It was more of a general question, for anyone. I guess what Iâm saying isâŠI have no idea either.
The fact that removing amd-ucode seemed to allow the boot makes me think there is a bug or something wrong with the version of amd-ucode itself, however if that were the case I would expect to see reports of issues elsewhere, in other distros for example so I am not so sure.
The more I read about AMD ucode, the less I understand it I think.
Seems to be set up as the separate initramfs from what information I have seen on this thread, at least with @buccaneer78 's case (two .img files using the GRUB method from what I can see from the Arch Wiki). I am assuming its like that to be independent of using dracut just in case the user wants to change to mkinitcpio.
As to why it is working without additional microcode, the provided motherboard firmware could be doing the heavy lifting, or there is microcode baked into whatever kernel is used. Actually⊠the more I think about it⊠As to why it isnât working until the /@/boot/amd-ucode.img is removed, there can be multiple early loading microcode methods going on just for the AMD side (if it still stands true that only AMD CPU users are effected with the new ISOs). I say this because as @dr460nf1r3 's link ( [bug #64475] grub failed to initrd /boot/amd-ucode.img in btrfs partitio ) mentions that a user had an issue with duplicates of /boot/amd-ucode.img
Edit: wrote this as Blushish was writing more . Maybe it is more of a version issue if the git one works without issue.