[SOLVED] xrandr - simpledrm issues

RedArcher · 2024-12-01 07:21:19

I might have a similar issue.

This xrandr command, which is in my i3 config file, does not work, and the resolution of the display appears to be of 1024x768.

exec xrandr --output HDMI-0 --mode 1920x1080 --rate 60

This is the new output of xrandr.

$ xrandr
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 4096 x 4096
None-1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1024x768      60.00*+

$ xrandr --output HDMI-0 --mode 1920x1080 --rate 60
warning: output HDMI-0 not found; ignoring

$ xrandr --output None-1 --mode 1920x1080 --rate 60
xrandr: cannot find mode 1920x1080

I have also updated package nvidia-535xx-utils to version 535.216.01-3.

Last edited by RedArcher (2024-12-03 15:08:18)

seth · 2024-12-01 07:53:24

Most likely unrelated, this smells as if the simplydumb device gets into the way.
Please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General

RedArcher · 2024-12-01 09:17:21

$ cat .local/share/xorg/Xorg.0.log  | curl -F 'file=@-' 0x0.st
http://0x0.st/XR5J.txt

seth · 2024-12-01 11:49:02

[    26.574] (II) Platform probe for /sys/devices/pci0000:00/0000:00:03.1/0000:1c:00.0/simple-framebuffer.0/drm/card0
[    26.861] (II) modeset(0): Refusing to try glamor on llvmpipe
[    26.863] (II) modeset(0): glamor initialization failed
[    26.863] (II) modeset(0): ShadowFB: preferred NO, enabled NO
[    26.863] (II) modeset(0): Output None-1 has no monitor section
[    26.863] (II) modeset(0): EDID for output None-1
[    26.863] (II) modeset(0): Printing probed modes for output None-1
[    26.863] (II) modeset(0): Modeline "1024x768"x60.0   47.19  1024 1024 1024 1024  768 768 768 768 (46.1 kHz eP)
[    26.872] (II) IGLX: Loaded and initialized swrast
[    26.872] (II) GLX: Initialized DRISWRAST GL provider for screen 0

Tada.

Apparently the "nvidia_drm.modeset=1" hack was removed from the 6.12 kernels. /grrr
Add "initcall_blacklist=simpledrm_platform_driver_init" to the https://wiki.archlinux.org/title/Kernel_parameters

RedArcher · 2024-12-01 12:35:34

# grub-mkconfig -o /boot/grub/grub.cfg
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux.img
Found fallback initrd image(s) in /boot:  amd-ucode.img initramfs-linux-fallback.img
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

Restarting machine...

1. The screen tends to have a purple or pink colour.
2. The screen gets blanked (black) for a secind or two, sometimes).

Problem persists, even after removing nvidia_drm.modeset=1.

$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-linux root=UUID=80f8e3f3-51ff-4a07-a8c6-62a9a416466b rw loglevel=3 quiet

$ xrandr
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 4096 x 4096
None-1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1024x768      60.00*+

Xorg

$ cat .local/share/xorg/Xorg.0.log  | curl -F 'file=@-' 0x0.st
http://0x0.st/XR7A.txt

If the issue of corrupted kernel space has been solved, then I would want to switch back to the non-proprietary driver nouveau.

Last edited by RedArcher (2024-12-01 12:52:55)

seth · 2024-12-01 18:38:32

http://0x0.st/XR7A.txt

[    49.400] (==) Log file: "/home/admin/.local/share/xorg/Xorg.0.log", Time: Sun Dec  1 14:38:10 2024
[    49.400] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=80f8e3f3-51ff-4a07-a8c6-62a9a416466b rw loglevel=3 quiet
[    49.408] (II) Platform probe for /sys/devices/pci0000:00/0000:00:03.1/0000:1c:00.0/simple-framebuffer.0/drm/card0

"initcall_blacklist=simpledrm_platform_driver_init" is not in the kernel parameters, the simplydumb device acts up.
nvidia_drm.modeset=1 is meanwhile default anyway but I'd just keep it there in case the hack returns.

In doubt use the LTS kernel (though "initcall_blacklist=simpledrm_platform_driver_init" should absolutely work)

RedArcher · 2024-12-02 08:53:10

Applying this configuration has caused to Linux to stuck at boot, and after a minute the machine fans were halted.

$ cat /etc/default/grub
# GRUB boot loader configuration

GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Arch"
#GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet nvidia_drm.modeset=1"
GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet"
GRUB_CMDLINE_LINUX="initcall_blacklist=simpledrm_platform_driver_init"
#GRUB_CMDLINE_LINUX="nvidia_drm.modeset=1"
#GRUB_CMDLINE_LINUX="initcall_blacklist=simpledrm_platform_driver_init"

I will try again with this line

GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet initcall_blacklist=simpledrm_platform_driver_init"

Adding "initcall_blacklist=simpledrm_platform_driver_init" as follows also stucks at boot.

GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet initcall_blacklist=simpledrm_platform_driver_init"

Last edited by RedArcher (2024-12-02 09:21:13)

seth · 2024-12-02 09:34:12

https://gitlab.archlinux.org/archlinux/ … /issues/94

Remove the quiet parameter and also see whether you can log in blindly

In doubt use the LTS kernel (though "initcall_blacklist=simpledrm_platform_driver_init" should™ absolutely work)

RedArcher · 2024-12-02 13:19:52

Same lower resolution and purple colour scheme for

$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-linux root=UUID=80f8e3f3-51ff-4a07-a8c6-62a9a416466b rw loglevel=3

Pardon.

What do you mean by "blindly"?
How can the LTS kernel be enabled?
I did try "initcall_blacklist=simpledrm_platform_driver_init", and it did not work.

Last edited by RedArcher (2024-12-02 14:31:37)

seth · 2024-12-02 16:08:18

Same lower resolution and purple colour scheme for

Removing the quiet parameter was meant "along initcall_blacklist=simpledrm_platform_driver_init" to maybe get *some* output.
Blindly means you're entering your login and start the display server w/o any visual feedback, just trusting your fingers to not typo.

You just install linux-lts and nvidia-lts and add it to your bootloader config (in doubt grub-mkconfig will pick it up)
You can then select it at the bootloader and avoid the 6.12 regressions for the moment.

RedArcher · 2024-12-02 16:41:21

I have just added "initcall_blacklist=simpledrm_platform_driver_init" and it has produced the same result.

The system was stuck at

loading linux linux...
loading initial ramdisk...

And the line that should be at the top "Loading 'Arch Linux'" was missing.

I shall wait for a fix or install package "vulkan-nouveau".

anti4r. Was your problem solved?

seth · 2024-12-02 16:50:15

And the line that should be at the top "Loading 'Arch Linux'" was missing.

W/ the kms switch, yes - the question is whether the system still boots, but doesn't update the framebuffer anymore until you start X11 or wayland and have them take over.

=> Install the LTS kernel and wait for 6.12 to be fixed (if ever…)

anti4r's problem is completely unrelated to yours and Lone_Wolf should probably split off the tail starting at #6

RedArcher · 2024-12-02 17:01:14

Once packages linux-lts and nvidia-lts are installed, are there any special parameters to add to grub, or reloading it would soffice.

I suppose that package r8168-lts would also need to be installed.

By "reloading", I mean to this command.

grub-mkconfig -o /boot/grub/grub.cfg

Last edited by RedArcher (2024-12-02 17:12:11)

seth · 2024-12-02 17:13:29

Nope, grub-mkconfig should™ pick up the kernels automatically - make sure you didn't forget to mount any boot partition and maybe inspect the generated grub.cfg for the lts kernel presence.

RedArcher · 2024-12-02 17:47:19

A lesson learned.

I have made a couple of backup files of the generated file "/boot/grub/grub.cfg",

I will install packages linux-lts and nvidia-lts and run the command grub-mkconfig.

I have a problem.

# pacman -S nvidia-lts
resolving dependencies...
looking for conflicting packages...
:: nvidia-utils-565.57.01-2 and nvidia-535xx-utils-535.216.01-3 are in conflict (nvidia-libgl). Remove nvidia-535xx-utils? [y/N] y
:: nvidia-lts-1:565.57.01-6 and nvidia-535xx-dkms-535.216.01-3 are in conflict (NVIDIA-MODULE). Remove nvidia-535xx-dkms? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: unable to satisfy dependency 'egl-gbm' required by nvidia-utils

Last edited by RedArcher (2024-12-02 17:48:41)

seth · 2024-12-02 17:53:53

Oh, don't install nvidia-lts but the linux-lts-headers, dkms will build you the 535xx drivers and afaiu they also don't build against 6.12: https://aur.archlinux.org/packages/nvid … nt-1000467 so there's your problem.

RedArcher · 2024-12-02 18:10:35

Errors.

# pacman -S linux-lts-headers
resolving dependencies...
looking for conflicting packages...

Packages (1) linux-lts-headers-6.6.63-1

Total Download Size:    24.64 MiB
Total Installed Size:  124.39 MiB

:: Proceed with installation? [Y/n] 
:: Retrieving packages...
 linux-lts-header...    24.6 MiB   527 KiB/s 00:48 [#############] 100%
(1/1) checking keys in keyring                     [#############] 100%
(1/1) checking package integrity                   [#############] 100%
(1/1) loading package files                        [#############] 100%
(1/1) checking for file conflicts                  [#############] 100%
(1/1) checking available disk space                [#############] 100%
:: Processing package changes...
(1/1) installing linux-lts-headers                 [#############] 100%
:: Running post-transaction hooks...
(1/4) Arming ConditionNeedsUpdate...
(2/4) Updating module dependencies...
(3/4) Install DKMS modules
==> ERROR: Missing 6.6.63-1-lts kernel modules tree for module v4l2loopback/0.13.2.
==> ERROR: Missing 6.6.63-1-lts kernel modules tree for module nvidia/535.216.01.
==> ERROR: Missing 6.6.63-1-lts kernel modules tree for module binder/1.
(4/4) Refreshing py3status arch_updates module...

Package "linux-lts" is not yet installed.

# pacman -S linux-lts
resolving dependencies...
looking for conflicting packages...

Packages (1) linux-lts-6.6.63-1

Total Download Size:   128.40 MiB
Total Installed Size:  128.59 MiB

:: Proceed with installation? [Y/n]

Please. Kindly instruct me what actions do to. I refrain from interpreting matters on my own for fear of doing tasks falsly.

Last edited by RedArcher (2024-12-02 18:13:10)

Scimmia · 2024-12-02 18:12:06

What good are the headers for a kernel you don't have installed? Partial update, I'm guessing?

Last edited by Scimmia (2024-12-02 18:13:14)

RedArcher · 2024-12-02 18:13:55

I have figured that pacman would handle that.

I will install package "linux-lts".

Is this fine? (notice the error and warning)

# pacman -S linux-lts-headers
warning: linux-lts-headers-6.6.63-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) linux-lts-headers-6.6.63-1

Total Installed Size:  124.39 MiB
Net Upgrade Size:        0.00 MiB

:: Proceed with installation? [Y/n] 
(1/1) checking keys in keyring                     [#############] 100%
(1/1) checking package integrity                   [#############] 100%
(1/1) loading package files                        [#############] 100%
(1/1) checking for file conflicts                  [#############] 100%
(1/1) checking available disk space                [#############] 100%
:: Running pre-transaction hooks...
(1/1) Remove upgraded DKMS modules
==> dkms remove --no-depmod nvidia/535.216.01 -k 6.6.63-1-lts
==> dkms remove --no-depmod v4l2loopback/0.13.2 -k 6.6.63-1-lts
:: Processing package changes...
(1/1) reinstalling linux-lts-headers               [#############] 100%
:: Running post-transaction hooks...
(1/4) Arming ConditionNeedsUpdate...
(2/4) Updating module dependencies...
(3/4) Install DKMS modules
==> dkms install --no-depmod v4l2loopback/0.13.2 -k 6.6.63-1-lts
==> dkms install --no-depmod nvidia/535.216.01 -k 6.6.63-1-lts
==> dkms install --no-depmod binder/1 -k 6.6.63-1-lts

Error! Bad return status for module build on kernel: 6.6.63-1-lts (x86_64)
Consult /var/lib/dkms/binder/1/build/make.log for more information.
==> WARNING: `dkms install --no-depmod binder/1 -k 6.6.63-1-lts' exited 10
==> depmod 6.6.63-1-lts
(4/4) Refreshing py3status arch_updates module...

Shall I execute the command?

grub-mkconfig -o /boot/grub/grub.cfg

Last edited by RedArcher (2024-12-02 19:35:55)

seth · 2024-12-02 20:53:47

One of these failed to build: https://aur.archlinux.org/packages/bind … x-dkms-git
Check

dkms status

- you want to see something like

nvidia/535.216.01, 6.6.63-1-lts, x86_64: installed

RedArcher · 2024-12-03 02:26:16

$ dkms status
binder/1: added
nvidia/535.216.01, 6.12.1-arch1-1, x86_64: installed
nvidia/535.216.01, 6.6.63-1-lts, x86_64: installed
v4l2loopback/0.13.2, 6.12.1-arch1-1, x86_64: installed
v4l2loopback/0.13.2, 6.6.63-1-lts, x86_64: installed

Shall I install "binder_linux-dkms-git" or execute command?

grub-mkconfig -o /boot/grub/grub.cfg

And then restart the machine

Last edited by RedArcher (2024-12-03 02:41:46)

seth · 2024-12-03 05:08:54

You don't have the binder module installed for any kernel atm, so I assume that's just residual of a failed attempt and you can ignore those errors.
You've the nvidia module installed for the LTS kernel, so check the mount status of your boot partition, recreate grub.cfg, take a look at it and if it looks fine *to you*, jump feet ahead into the reboot.
(I want you to make this judgement. If you screw up, we'll work out of that, but you cannot just ask for permission for every little thing. At some point you've to put on your big boy pants, fire up your brain, estimate the situation the best you can, take a deep breath and then act accordingly)

RedArcher · 2024-12-03 07:26:07

I want you to make this judgement. If you screw up, we'll work out of that,

Thank you.

but you cannot just ask for permission for every little thing.

I understand. And I agree.

Because this might be a crucial moment, and because I still have an accessible environment to execute actions, if you would require me, I have kept the machine working, while it is still convenient.

At some point you've to put on your big boy pants, fire up your brain, estimate the situation the best you can, take a deep breath and then act accordingly

I have laughed from joy and because it is funny too!

Thank you so much for that laugh, and I appreciate your attitude towards me, specifically that quoted statement. And thank you for a good start of a day!

I wish that I would ever receive such attitude from my mother and father.

I will reload the configuration, restart the machine, and hope to convey a good report.

This is interesting. It appears that there are now additional menu entries to boot with the LTS kernel; that is, it appears as I might be able to choose the kernel to utilize, directly from GRUB.

# diff /boot/grub/grub.cfg /boot/grub/grub.cfg_clear.bak
97,98c97,98
<       echo    'Loading Linux linux-lts ...'
<       linux   /vmlinuz-linux-lts root=UUID=80f8e3f3-51ff-4a07-a8c6-62a9a416466b rw  loglevel=3 nvidia_drm.modeset=1
---
>       echo    'Loading Linux linux ...'
>       linux   /vmlinuz-linux root=UUID=80f8e3f3-51ff-4a07-a8c6-62a9a416466b rw  loglevel=3 nvidia_drm.modeset=1
100c100
<       initrd  /amd-ucode.img /initramfs-linux-lts.img
---
>       initrd  /amd-ucode.img /initramfs-linux.img
103,126d102
<       menuentry 'Arch Linux, with Linux linux-lts' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-lts-advanced-80f8e3f3-51ff-4a07-a8c6-62a9a416466b' {
<               load_video
<               set gfxpayload=keep
<               insmod gzio
<               insmod part_gpt
<               insmod ext2
<               search --no-floppy --fs-uuid --set=root f94b4d87-14e2-4bf3-947b-c742161820b8
<               echo    'Loading Linux linux-lts ...'
<               linux   /vmlinuz-linux-lts root=UUID=80f8e3f3-51ff-4a07-a8c6-62a9a416466b rw  loglevel=3 nvidia_drm.modeset=1
<               echo    'Loading initial ramdisk ...'
<               initrd  /amd-ucode.img /initramfs-linux-lts.img
<       }
<       menuentry 'Arch Linux, with Linux linux-lts (fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-lts-fallback-80f8e3f3-51ff-4a07-a8c6-62a9a416466b' {
<               load_video
<               set gfxpayload=keep
<               insmod gzio
<               insmod part_gpt
<               insmod ext2
<               search --no-floppy --fs-uuid --set=root f94b4d87-14e2-4bf3-947b-c742161820b8
<               echo    'Loading Linux linux-lts ...'
<               linux   /vmlinuz-linux-lts root=UUID=80f8e3f3-51ff-4a07-a8c6-62a9a416466b rw  loglevel=3 nvidia_drm.modeset=1
<               echo    'Loading initial ramdisk ...'
<               initrd  /amd-ucode.img /initramfs-linux-lts-fallback.img
<       }

No. No new menu entries as I was hoping for.

It would be nice to select which kernel to choose.

Yet, everything is back to normal.

Liferea, sway, i3, Fluxbox, Falkon, I2P, qBitTorrent, Tribler, Gajim, MPC-Qt, rofi and everything fun is managed!

$ uname -a
Linux workstation 6.6.63-1-lts #1 SMP PREEMPT_DYNAMIC Fri, 22 Nov 2024 15:39:56 +0000 x86_64 GNU/Linux

$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-linux-lts root=UUID=80f8e3f3-51ff-4a07-a8c6-62a9a416466b rw loglevel=3 nvidia_drm.modeset=1

Thank you!

My issue has been solved!

Last edited by RedArcher (2024-12-03 07:46:12)

Lone_Wolf · 2024-12-03 10:26:24

Split off from https://bbs.archlinux.org/viewtopic.php?id=301399

RedArcher, if you are satisifed with the outcome please prepend [Solved] to the thread title (edit first post)

seth · 2024-12-03 15:00:44

No. No new menu entries as I was hoping for.
It would be nice to select which kernel to choose.

Please post the entire new grub.cfg and "ls /boot" - you certainly *added* the LTS kernel and didn't remove anything else, but it also looks like some previous entry was changed from the main to the LTS kernel.

Arch Linux

#1 2024-12-01 07:21:19

[SOLVED] xrandr - simpledrm issues

#2 2024-12-01 07:53:24

Re: [SOLVED] xrandr - simpledrm issues

#3 2024-12-01 09:17:21

Re: [SOLVED] xrandr - simpledrm issues

#4 2024-12-01 11:49:02

Re: [SOLVED] xrandr - simpledrm issues

#5 2024-12-01 12:35:34

Re: [SOLVED] xrandr - simpledrm issues

#6 2024-12-01 18:38:32

Re: [SOLVED] xrandr - simpledrm issues

#7 2024-12-02 08:53:10

Re: [SOLVED] xrandr - simpledrm issues

#8 2024-12-02 09:34:12

Re: [SOLVED] xrandr - simpledrm issues

#9 2024-12-02 13:19:52

Re: [SOLVED] xrandr - simpledrm issues

#10 2024-12-02 16:08:18

Re: [SOLVED] xrandr - simpledrm issues

#11 2024-12-02 16:41:21

Re: [SOLVED] xrandr - simpledrm issues

#12 2024-12-02 16:50:15

Re: [SOLVED] xrandr - simpledrm issues

#13 2024-12-02 17:01:14

Re: [SOLVED] xrandr - simpledrm issues

#14 2024-12-02 17:13:29

Re: [SOLVED] xrandr - simpledrm issues

#15 2024-12-02 17:47:19

Re: [SOLVED] xrandr - simpledrm issues

#16 2024-12-02 17:53:53

Re: [SOLVED] xrandr - simpledrm issues

#17 2024-12-02 18:10:35

Re: [SOLVED] xrandr - simpledrm issues

#18 2024-12-02 18:12:06

Re: [SOLVED] xrandr - simpledrm issues

#19 2024-12-02 18:13:55

Re: [SOLVED] xrandr - simpledrm issues

#20 2024-12-02 20:53:47

Re: [SOLVED] xrandr - simpledrm issues

#21 2024-12-03 02:26:16

Re: [SOLVED] xrandr - simpledrm issues

#22 2024-12-03 05:08:54

Re: [SOLVED] xrandr - simpledrm issues

#23 2024-12-03 07:26:07

Re: [SOLVED] xrandr - simpledrm issues

#24 2024-12-03 10:26:24

Re: [SOLVED] xrandr - simpledrm issues

#25 2024-12-03 15:00:44

Re: [SOLVED] xrandr - simpledrm issues

Board footer