[SOLVED] xrandr shows unknown monitor, and Xorg -configure fails

whirled_peas · 2024-03-13 17:40:53

Greetings! I love Arch Linux, have been trying it for several years. It does it ALL on the apps. Arch is becoming my fave. This is my first time posting in this forum. Am I in the right area?

After updating one day...I found a blank screen hanging without loading sddm login screen.

After reinstalling sddm, x11 several times, I can now run Plasma in Wayland. Screen resolution is reduced, screen is square. But everything seems to work. I made a new user and logged on through that but the resolutiojn is reduced, icons missing.

If I run X11 for the Mate desktop, my wallpaper has been replaced by a large clock.

if I run X11 for the Plasma desktop, icons are missing. Custom wallpaper not assigned

Plasma Wayland gets me back in a functioning gui with square screen, kdinfo says graphics is using the llvmpipe

libEGL warns that Mesa Loader failed to open simpledrm_dri.so

I have old AMD card but I'm just wanting to use the mesa drivers, I don't need the proprietaries loaded

and yep, pacman -Syu is one of my favorite things to type

I triple boot on this machine and the other distros work so it does not seem to be hardware or cable failure. And Arch worked fine before updating several weeks ago

imho, it's better to fix things and learn rather than wipe and start over

Please tell me what logs to get and I thank you kindly in advance

Last edited by whirled_peas (2024-03-28 13:28:03)

seth · 2024-03-13 18:15:07

That's the SIMPLYDUMB device, enable https://wiki.archlinux.org/title/NVIDIA … de_setting - use the "nvidia_drm.modeset=1" kernel parameter (modprobe.conf won't do!), nvidia_drm.fbdev=1 is currently hit-and miss (might fend off flicker, might cause it)

whirled_peas · 2024-03-13 18:31:25

Thank you for the quick reply Seth. I read something about this before but I was confused because I don't have an Nvidia card. Do I still need this or do I need to black-list it away from my AMD graphics card? Or do I go ahead and load it for the AMD, but choose "nvidia_drm.modeset=0" ?

my card is

product: Oland PRO [Radeon R7 240/340 / Radeon 520]
vendor: Advanced Micro Devices, Inc. [AMD/ATI]

V1del · 2024-03-13 19:00:58

You can do nvidia_drm.modeset=1 ... the parameter's presence is the deciding factor, not whether you actually have the module that it would normally be used for.

seth · 2024-03-13 20:32:16

You can also add "initcall_blacklist=simpledrm_platform_driver_init" to the https://wiki.archlinux.org/title/Kernel_parameters
However, the mesa drivers should™ properly take over from the simplydumb thing anyway - consider https://wiki.archlinux.org/title/Kernel … _KMS_start and w/ the Oland chip in particular, to use https://wiki.archlinux.org/title/AMDGPU … K)_support instead of the radeon driver.

If the issue somehow remains, please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General and your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

whirled_peas · 2024-03-27 16:42:28

Hello again, thanks to you all for the suggestions. I tried passing kernel parameters via GRUB_CMDLINE_LINUX_DEFAULT, within the quotes, even tried the grub-customizer GUI in Plasma. When I tried nvidia_drm.modeset=1 and also radeon.si_support=0 amdgpu.si_support=1 and vice versa. (my GPU is southern islands chip)

When I add those kernel parameters it no longer boots past the blinking cursor and does not reach the logon sddm screen. (f4 start over)

If I remove the added kernel parameters, it then will boot to Plasma or Mate desktop, with the resolution reduced (no screen set up in X11 because Xorg -configure fails)

I will say this is a new monitor since December, has been running fine until updates. The EDID on this monitor shows an extra bit and it covers up the 1st character of the EDID. This probably doesn't help the situation

I have the AMD Oland R7-240 GPU in 2 machines with several different distros and I have never been able to reconfigure X with Xorg -config. It always worked on new installs though, without any special drivers. Popssibly this GPU model is the issue, not friendly. It never Xorg -configure 's correctly, with various monitors attached.

My Xorg logs and boot journal are ready as requested

Please tell me the easiest method of uploading the text. If I understand this correctly, we're not supposed paste the text in the body of the messages, and not supposed to use pastebin directly because of adverts, bots, and such, correct? I have read the wiki about the pastebin and I'm not grasping it.

I just want to use regular vesa driver

Please point me in the right direction and I shall paste the logs

whirled_peas · 2024-03-27 17:23:07

my boot journal below:
my boot journal

I'm currently trying to figure out how to upload my xorg with curl in the same way

seth · 2024-03-27 17:29:05

You can just "cat" it into the curl command.

None of those parameters is present and neither amdgpu nor radeon are loaded and you're running on the simpledrm device in software mode.

modprobe -c | grep -v alias | grep -E '(amdgpu|radeon)'

Btw, disable dhcpcd, it runs against NetworkManager

whirled_peas · 2024-03-27 17:42:17

Here are the logs below, just curled them:

boot journal

xorg.0.log

whirled_peas · 2024-03-27 17:54:12

Seth, I stopped the dhcpcd and removed the symlink.

Then I ran the modprobe command as instructed, without error.

Also, please note I was able to message a link to my Xorg.0.log, in this thread, message #9.

I'm leaving this machine on for now, waiting for you to see my xorg log until I reboot. I don't want to goof this up

seth · 2024-03-27 18:13:45

[   474.044] (++) Using config file: "/root/xorg.conf.new"

Remove that, don't try to run X11 as root.

modprobe wasn't supposed to post errors but also not empty - apparently you're not blacklisting the modules either?

modinfo amdgpu radeon
lsmod
sudo modprobe -v radeon

whirled_peas · 2024-03-27 20:39:30

Thank you Seth, I know to avoid startx as root. I've been using SDDM and the logoin screen as a normal user with sudo so I rarely input "startx" anymore, I usually let SDDM do that for me.

I'm not aware that I'm blacklisting anything. I know some linux basics, that's about it. Should I be blacklisting something?

I ran your last 3 commands from recovery mode. When I ran "sudo modprobe -v radeon" it increased my screen size, Plasma with Wayland composting is now full screen, higher resolution. But plasma with X11 stops loading at a blank screen.

seth · 2024-03-27 21:47:46

We don't know why the radeon module isn't loading for you but it very much sounds like it's blacklisted - what was the actual output of the earlier "modprobe -c" grep?
Wrt plasma on X11, please post an udpated xorg log.

whirled_peas · 2024-03-27 22:39:11

I apologize, I must be going blind....I missed it earlier when input

modprobe -c grep, etc now produces:

blacklist radeon
blacklist amdgpu

please tell me how I un-blacklist them

I will get you the new xorg log after attempting Plasma X11. If it freezes again, I reboot to Plasma Wayland afterwards, to get the xorg log

seth · 2024-03-27 22:43:02

https://wiki.archlinux.org/title/Kernel … acklisting
Likely some file in /etc/modprobe.d/ - you also may have to regenerate the initramfs after removing that.

whirled_peas · 2024-03-27 23:17:47

okay, I will look in the /etc/modprobe.d/ directory for something that says blacklist and regen the initramfs afterwards

meanwhile, here is my new xorg log after attempting to load the Plasma in X11 (froze black screen without cursor)

xorg.0.log for 2nd try

whirled_peas · 2024-03-28 00:08:21

You were correct, I had an AMD blacklist, and it has been deleted. I'm sorry I missed that earlier.

I just ran these commands:

1. deleted old preset for an lqx kernel that is no longer installed

2. sudo mkinitcpio -P linux

3. sudo pacman -Syu

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

5, rebooted

6. tried to logon Plasma X11. still freezes

7. tried Plasma X11 with a new user for grins, and it worked. Yay! Perhaps I have a permission problem

This is great, finally gettting somewhere after struggling for several weeks on my own (and looks like I had messed some things up trying. I should have came here first

So please help me restore my old user permissions for graphics- or should I just delete the user and associated files, and create the account again?

"Xorg -configure :0" still fails, says wrong number of screens

(I just saw your last post, thank you, and i will try the kernel parameters)

Last edited by whirled_peas (2024-03-28 09:53:48)

seth · 2024-03-28 07:48:54

https://wiki.archlinux.org/title/Mkinit … generation

sudo mkinitcpio -P

Your xorg log looks promising

[ 10086.124] (II) modeset(0): glamor X acceleration enabled on OLAND (radeonsi, , LLVM 17.0.6, DRM 2.50, 6.8.1-arch1-1)

So unblacklist amdgpu and try "radeon.si_support=0 amdgpu.si_support=1"

whirled_peas · 2024-03-28 10:43:01

I added the radeon.si_support=0 amdgpu.si_support=1 kernel parameter in etc default grub and it loads properly (thanks!) because in Kinfo center it now shows "AMD Radeon Graphics" Before the kernel paramters were added it displayed "AMD Oland Graphics"

My newly made user account boots Plasma X11 full width, full resolution. Awesome.

My orignal user account now boots Plasma X11 but in a small screen with the wrong aspect ratio, squished.

I'm now going to add my new user account to the wheel group to get sudo there and then try Xorg -configure :0 again

whirled_peas · 2024-03-28 12:12:15

My new user account boots Plasma in both X11 and Wayand with full screen

I tried the "Xorg -configure :0" with the new user account, still doesn't work. I'm convinced that issue is related to this graphics card. Because it Xorg has never configured, for any of my distros, on 2 seperate machines, both with the same adapter. Maybe that's not important....the screen and mouse and keyboard works. So maybe the X11 is okay like it is? Without manual configuration?

My only question remaining is why is my original user account is booting Plasma X11 with a squished display, and booting Plasma Wayland in full screen.

V1del · 2024-03-28 12:16:40

X is always ok without manual configuration and actually runnin Xorg -configure is very much untested and not actually necessary anymore.

There are special cases where you might want to add a configuration snippet, but this should be a controlled and intended action not plastering the auto config over it.

For your original user, if it's only based on the user you likely have a broken kscreen config, try removing ~/.local/share/kscreen and relogin

Last edited by V1del (2024-03-28 12:17:18)

whirled_peas · 2024-03-28 13:15:17

Such great help! Y'all are much appreciated.

And I learned several things. I was happy we conquered this- as I said earlier I've distro hopped much on PC's and RPI's and Arch is the best, the AUR is awesome too

Do I mark this solved somehow, or to you do that?

seth · 2024-03-28 13:18:46

Mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Arch Linux

#1 2024-03-13 17:40:53

[SOLVED] xrandr shows unknown monitor, and Xorg -configure fails

#2 2024-03-13 18:15:07

Re: [SOLVED] xrandr shows unknown monitor, and Xorg -configure fails

#3 2024-03-13 18:31:25

Re: [SOLVED] xrandr shows unknown monitor, and Xorg -configure fails

#4 2024-03-13 19:00:58

Re: [SOLVED] xrandr shows unknown monitor, and Xorg -configure fails

#5 2024-03-13 20:32:16

Re: [SOLVED] xrandr shows unknown monitor, and Xorg -configure fails

#6 2024-03-27 16:42:28

Re: [SOLVED] xrandr shows unknown monitor, and Xorg -configure fails

#7 2024-03-27 17:23:07

Re: [SOLVED] xrandr shows unknown monitor, and Xorg -configure fails

#8 2024-03-27 17:29:05

Re: [SOLVED] xrandr shows unknown monitor, and Xorg -configure fails

#9 2024-03-27 17:42:17

Re: [SOLVED] xrandr shows unknown monitor, and Xorg -configure fails

#10 2024-03-27 17:54:12

Re: [SOLVED] xrandr shows unknown monitor, and Xorg -configure fails

#11 2024-03-27 18:13:45

Re: [SOLVED] xrandr shows unknown monitor, and Xorg -configure fails

#12 2024-03-27 20:39:30

Re: [SOLVED] xrandr shows unknown monitor, and Xorg -configure fails

#13 2024-03-27 21:47:46

Re: [SOLVED] xrandr shows unknown monitor, and Xorg -configure fails

#14 2024-03-27 22:39:11

Re: [SOLVED] xrandr shows unknown monitor, and Xorg -configure fails

#15 2024-03-27 22:43:02

Re: [SOLVED] xrandr shows unknown monitor, and Xorg -configure fails

#16 2024-03-27 23:17:47

Re: [SOLVED] xrandr shows unknown monitor, and Xorg -configure fails

#17 2024-03-28 00:08:21

Re: [SOLVED] xrandr shows unknown monitor, and Xorg -configure fails

#18 2024-03-28 07:48:54

Re: [SOLVED] xrandr shows unknown monitor, and Xorg -configure fails

#19 2024-03-28 10:43:01

Re: [SOLVED] xrandr shows unknown monitor, and Xorg -configure fails

#20 2024-03-28 12:12:15

Re: [SOLVED] xrandr shows unknown monitor, and Xorg -configure fails

#21 2024-03-28 12:16:40

Re: [SOLVED] xrandr shows unknown monitor, and Xorg -configure fails

#22 2024-03-28 13:15:17

Re: [SOLVED] xrandr shows unknown monitor, and Xorg -configure fails

#23 2024-03-28 13:18:46

Re: [SOLVED] xrandr shows unknown monitor, and Xorg -configure fails

Board footer