You are not logged in.
You don't need to do anything with the module, just add "nvidia_drm.modeset=1" to the https://wiki.archlinux.org/title/Kernel_parameters
You could also use "initcall_blacklist=simpledrm_platform_driver_init", the only point is to prevent the simpledrm module from loading.
Offline
I have added the following via GRUB:
$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-linux root=UUID=80f8e3f3-51ff-4a07-a8c6-62a9a416466b rw loglevel=3 quiet nvidia_drm.modeset=1
Problem persists.
Offline
I have followed the GRUB instructions and then executed "# grub-mkconfig -o /boot/grub/grub.cfg" and now the display indicates "No Signal".
Unfotunately, the CPU does not support display, so I am relied on the GPU for display.
SSH does not work because it appears - from LAN (using "arp-scan") that even the system does not even load.
I have attempted to boot Live USB images to attempt to solve this issue and both (completely different distributions) stuck shortly after selecting an option from each GRUB screen,
I do not understand what could block the machine from booting Live images.
---
The distro SystemRescue is working!
Thunar does not list the devices, though they are detected via command "lsblk".
I need to undo the recent change I have made.
---
It appears that "/boot/grub/grub.cfg" - which is mounted as "/root/Mounter/boot/grub/grub.cfg" - does not exist
What should I do to restore GRUB to its previous state?
Last edited by RedArcher2 (2024-05-09 14:16:10)
Offline
Deleted
Last edited by RedArcher2 (2024-05-09 13:37:10)
Offline
Deleted
Last edited by RedArcher2 (2024-05-09 13:37:19)
Offline
You probably forgot to mount the boot Partition.
The system Not working w/o the simpledrm device is a huge Red flag, but you probably still can Boot it to the rescue or Multi-User.target (2nd Link belo) in doubt along "nomodeset"
Then please Post a Journal fromnone of the failed Boots w/o the Simpledrm device.
Offline
Yes. You are correct.
It exists, on another partition
Yet, when I ttempt to execute "# grub-mkconfig -o /root/Mounter/boot/grub/grub.cfg" I get this error:
/usr/bin/grub-probe: error: failed to get canonical path of `airootfs`.
Manual removal of "nvidia_drm.modeset=1" did not work either.
I do not know what to do now.
---
The system Not working w/o the simpledrm device is a huge Red flag,
Why "red flag"?
but you probably still can Boot it to the rescue or Multi-User.target (2nd Link belo) in doubt along "nomodeset"
From an externnal live medium or directly from Archlinux?
As I noted, upon loading GRUB, the screen - possibly - gets blanked (i.e. no signal).
Then please Post a Journal fromnone of the failed Boots w/o the Simpledrm device.
Where can I find that file, when I use an external live medium to browse Archlinux?
Last edited by RedArcher2 (2024-05-09 13:38:11)
Offline
Deleted
Last edited by RedArcher2 (2024-05-09 13:37:40)
Offline
Don't Run grub-cfg from random other distros, IT might be an incopatible older Version.
What so you mean by "Manual removal doesn't Work"?
You could also edit the commandline at the bootloader (Press "e" to edit the entry)
Offline
I mean, manual edit of file boot/grub/grub.cfg
I can not utilize GRUB and therefore I can not edit the commandline at the bootloader because the screen gets blanked.
I am reading V1del instructions at https://bbs.archlinux.org/viewtopic.php?id=280246
---
I use System Rescue https://www.system-rescue.org/Download/ at the moment
---
I have mounted the root partition and executed command grub-mkconfig from arch-chroot https://wiki.archlinux.org/title/Chroot … rch-chroot and then manually copied the grub.cfg to the desired directory.
Restarting...
---
It did not work. Still no signal.
How foolish I was for not making a backup of grub.cfg
What should I do?
---
Then please Post a Journal fromnone of the failed Boots w/o the Simpledrm device.
# mount /dev/nvme0n1p3 /tmp/root
# arch-chroot /tmp/root/
# journalctl -b
-- No entries -
What is "Simpledrm device"?
---
Is this information helpful?
[root@sysrescue ~]# arch-chroot /tmp/root/
[root@sysrescue /]# pacman -Syu
(10/22) Install DKMS modules
==> dkms install --no-depmod binder/1 -k 6.8.9-arch1-2
Error! Bad return status for module build on kernel: 6.8.9-arch1-2 (x86_64)
Consult /var/lib/dkms/binder/1/build/make.log for more information.
==> WARNING: `dkms install --no-depmod binder/1 -k 6.8.9-arch1-2' exited 10
==> dkms install --no-depmod nvidia/535.171.04 -k 6.8.9-arch1-2
==> dkms install --no-depmod v4l2loopback/0.13.1 -k 6.8.9-arch1-2
==> depmod 6.8.9-arch1-2
(11/22) Updating linux initcpios...
---
I intend to attempt this https://bbs.archlinux.org/viewtopic.php?id=280246
---
Now GRUB appear to work.
There is only command prompt
grub >
with explanatory text above it, having a minimal BASH-like line editing, instead of the TUI.
Last edited by RedArcher2 (2024-05-09 13:17:47)
Offline
Deleted
Last edited by RedArcher2 (2024-05-09 13:18:22)
Offline
Deleted
Last edited by RedArcher2 (2024-05-09 13:18:29)
Offline
Deleted
Last edited by RedArcher2 (2024-05-09 13:18:37)
Offline
Deleted
Last edited by RedArcher2 (2024-05-09 13:18:42)
Offline
Deleted
Last edited by RedArcher2 (2024-05-09 13:18:47)
Offline
Deleted
Last edited by RedArcher2 (2024-05-09 13:19:00)
Offline
Deleted
Last edited by RedArcher2 (2024-05-09 13:18:53)
Offline
Please don't bump. Edit you previous post if nobody has responded.
The problem wasn't the grub.cfg nor the simpledrm device but likely still https://archlinux.org/news/grub-bootloa … ibilities/
From https://bbs.archlinux.org/viewtopic.php … 0#p2170230 did you check that /dev/nvme0n1p1 is actually the ESP?
[root@sysrescue /]# mount /dev/nvme0n1p2 /boot/grub/
This is very most likely wrong, you probably wanted to mount that into /boot because now grub was installed/configured into /dev/nvme0n1p3
=> umount /boot/grub, clear the /boot mountpoint (the directory on /dev/nvme0n1p3) and mount /dev/nvme0n1p2 into /boot
Then
grub-install --target=x86_64-efi --efi-directory=/efi --bootloader-id=GRUB
grub-mkconfig -o /boot/grub/grub.cfg
Offline
Pardon. I will join the posts.
[root@sysrescue /]# grub-mkconfig -o /boot/grub/grub.cfg
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-linux-zen
Found linux image: /boot/vmlinuz-linux
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
done
Offline
This is from the chroot w/ the correct partitions mounted into place?
There's nothing critical in that output, try to boot the system.
Offline
This is from the chroot w/ the correct partitions mounted into place?
Yes, as you instructed.
Yet, I did not erase (i.e. "clear") the data from directory /boot/ of partition /dev/nvme0n1p3
EDIT: I have erased (backed up) directory /boot/ of partition /dev/nvme0n1p3 and the result appears to be the same.
1. GRUB works.
2. Afterwards, the display is stuck with:
Loading Linux linux-zen ...
_
---
My boot partition appears to be out of order:
[root@sysrescue /]# mount /dev/nvme0n1p2 /boot/
[root@sysrescue /]# ls /boot/
fonts grubenv lost+found vmlinuz-linux x86_64-efi
grub locale themes vmlinuz-linux-zen
[root@sysrescue /]# ls /boot/grub
fonts grub.cfg.bak grub.cfg.nvidia.bak locale themes
grub.cfg grub.cfg.bak2 grubenv log_from_console.txt x86_64-efi
Please ignore the .bak files.
Notice that
- Directory /boot/fonts/ is the same as /boot/grub/fonts/
- Directory /boot/locale/ is the same as /boot/grub/locale/
- Directory /boot/themes/ is the same as /boot/grub/themes/
- Directory /boot/x86_64-efi/ is the same as /boot/grub/x86_64-efi/
- File /boot/grubenv is the same as /boot/grub/grubenv
What should I do with these files?
vmlinuz-linux
vmlinuz-linux-zen
Last edited by RedArcher2 (2024-05-09 13:50:14)
Offline
Leave them where they are, you've at some point installed grub into a configuration where the boot partition was mounted as /boot/grub
You can remove /boot/{fonts,locale,themes,grubenv} but it currently just wastes space.
From the chroo, w/ the /boot partition mounted, re-install linux-zen.
In doubt try to boot only the multi-user.target along "nomodeset" and in any event remove the "quiet" parameter (you should now be able to edit the kernel commandline from grub?)
Offline
Greetings once again!
I have cleared the directory /boot/ and then executed these commands:
# mount /dev/nvme0n1p1 /efi/
# mount /dev/nvme0n1p2 /boot/
# pacman -S linux
# grub-install --target=x86_64-efi --efi-directory=/efi --bootloader-id=GRUB
# grub-mkconfig -o /boot/grub/grub.cfg
Result:
$ ls /boot/
grub
initramfs-linux-fallback.img
initramfs-linux.img
lost+found
vmlinuz-linux
Now, Arch Linux boots again!
---
The WebKit GTK+ HTML problem under X11 remains.
$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-linux root=UUID=80f8e3f3-51ff-4a07-a8c6-62a9a416466b rw loglevel=3 quiet nvidia_drm.modeset=1
---
Concerning a past comment of yours:
Generally speaking, the nvidida binary drivers will outperform nouveau (and probably not cause these kind of GL errors) - the export in your bashrc means right now you're rendering everything on the CPU.
Could this be that my CPU is utilized to render graphics when using "LIBGL_ALWAYS_SOFTWARE=1" even though my CPU does not support graphics when the HDMI cable is connected to it instead of to the GPU?
Last edited by RedArcher (2024-05-09 14:55:32)
Offline
At least you can boot again (not the zen kernel, currently, though)
\o/
For recap:
You ran an nvidia GP108 on nouveau and the modesetting driver, webkit doesn't render on X11 but rendering in software through "LIBGL_ALWAYS_SOFTWARE=1" works.
We tried to use the binary nvidia driver but that somehow failed and in https://bbs.archlinux.org/viewtopic.php … 7#p2168817 you ran on the simpledrm device.
After all the noise:
dkms status
lspci -k
and please post the current Xorg log, https://wiki.archlinux.org/title/Xorg#General
Offline
I have installed "linux-zen" too, in order to restore the files - and also regenerated GRUB config file - and GRUB still works!
Yet, starting xinit or wlr fail.
Image: https://i.kalli.st/KAD9d.jpeg
dkms status
binder/1: added
nvidia/535.171.04, 6.8.9-arch1-2, x86_64: installed
v4l2loopback/0.13.1, 6.8.9-arch1-2, x86_64: installed
lspci -k
cat Xorg.0.log
Last edited by RedArcher2 (2024-05-09 15:52:26)
Offline