loqs wrote:Please try my suggestion from post #18
I did try LTS already but it was not working either. Or do you mean this specific LTS?
That specific one which predates the last kernel you could boot.
]]>[2019-08-22 16:43] [ALPM] warning: /etc/default/grub installed as /etc/default/grub.pacnew
[2019-08-22 16:43] [ALPM] upgraded grub (2:2.02-8 -> 2:2.04-2)
Remember that /boot/grub/grub.cfg has to be re-generated after any change to /etc/default/grub or files in /etc/grub.d/.
Have you tried that ?
]]>I just wanted to tell you this problem is solved by switching to systemd-boot from grub. systemd-boot can load the ramdisk.
So is this a grub bug or what? I mean if I should file a bug report or alike.
regards and thanks for your time
]]>Please try my suggestion from post #18
I did try LTS already but it was not working either. Or do you mean this specific LTS?
]]>If you remove the nvidia modules from mkinitcpio.conf, regenerate the initrds does that have any effect?
no effect still stuck on initramdisk
]]>What is the contents of mkinitcpio.conf (if no nvidia modules are added to the initrd then that can not be the cause of the issue)
MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm)
BINARIES=()
FILES=()
HOOKS=(base udev autodetect modconf block filesystems keyboard fsck)
Tried "acpi=off"?
yeah did nothing neither
well I am now updated except of linux linux-headers nvidia nvidia-utils which are version of may first in the official repos. that is and linux 5.0.10.arch1-1 and nvidia 418.56-10.
You think there might be a bug in either the kernel or nvidia?
]]>adding
debug ignore_loglevel
did generate no further output still stuck on initramfs. I did update the system by ignoring linux linux-headers nvidia nvidia-utils by now, so in these packages must be the problem
any ideas?
]]>]]>
If you didn't use any helper scripts (dunno what arch-chroot actually does) you'll have to re-source your /etc/profile and your shell rc in order to apply the configuration of the chroot target.
However (I missed the failure singularity) if the good-locale initramfs (upgrade) doesn't work but the bad-locale (downgrade) does, it's safe to say that the locale error is not the cause of your troubles.
This is the case:/ Upgrade boot fails downgrade everything works
hm this drives me nuts
]]>