[Solved] Xorg Error: Cannot run in framebuffer mode.

Kepis · 2021-12-15 13:47:18

For whatever reason, I managed somehow to launch xorg server after it was not working, though I didn't touch a thing. But that was just one time and now I am back to the problem specified in the title.
I have no idea, why an ISO like arcolinux has no problem showing gui, but my USB installation cannot. I have checked the drivers, they're the same, I tried downgrading xorg, which was incredible pain due to the dependencies, but nothing worked.
I use linux for around a year, but that was on an old laptop. Now I went for a new laptop (Ideapad 5 Pro) with Ryzen 7 5800H.
amdgpu drivers load correctly, so I can't figure out where the problem could be.
Any help would be appreciated.

Last edited by Kepis (2021-12-18 23:00:53)

V1del · 2021-12-15 13:51:03

Post the actual full error message and a xorg log and

sudo journalctl -b

https://wiki.archlinux.org/title/List_o … n_services

Kepis · 2021-12-15 14:30:09

journalctl -b: https://pastebin.com/zdJx2CvT
xorg log: https://pastebin.com/qbvBB8an

V1del · 2021-12-15 14:53:53

Are you sure that's the correct xorg log? You have nvidia-utils and an nvidia driver and a xorg config referencing the nvidia driver on a system that does not run a nvidia card. Remove the relevant xorg.config snippet at the minimum.

Kepis · 2021-12-15 14:56:25

Yes I am sure, I have a system on a USB that I want to run on anything (which it did, up to now) and even when I uninstalled nvidia, it was the same story

V1del · 2021-12-15 15:10:25

You have a configuration you either created yourself or used nvidia-xrun or optimus-manager or so that does incorrect setup, you need to remove that, and "normally" the first xorg screen would be 0 so the log would be xorg.0.log but this depends on different setup parts, the underlying issue here is simply you have a bogus xorg configuration somewhere in /{etc,usr/share}/X11/xorg.conf.d

Kepis · 2021-12-15 16:40:57

There was literally nothing other than 10-amdgpu.conf a 10-radeon.conf, but never mind, because I spotted once again that the realtek wifi card disconnects after suspending the laptop. Therefore it is unusable so I am returning it.
But thank you for your help anyway.

Last edited by Kepis (2021-12-15 18:08:22)

V1del · 2021-12-15 18:11:42

[   135.534] (==) ServerLayout "Layout0"
[   135.534] (**) |-->Screen "iGPU" (0)
[   135.534] (**) |   |-->Monitor "<default monitor>"
[   135.535] (**) |   |-->Device "iGPU"
[   135.535] (**) |   |-->GPUDevice "dGPU"

is not a logical snippet that would be created by default, whatever file that's in likely contains references to non existing cards. If this worked on your old laptop then this is likely the part that was specific to that laptop. Just something to keep in mind when you switch to a new system and run into the same/similar failure again.

Kepis · 2021-12-15 18:43:04

You misunderstood me.
I wrote at the beginning that it did work on the new laptop too, but it was like a lucky time, because when I restarted X, it suddenly stopped working, even though the previous runs it did work. Basically I just reinstalled all packages, because the system got retarded and I couldn't get it to work in any proper way (errors in all sorts of places). The package reinstall made even a bigger mess I tried to clean up, after which I couldn't get xorg running, aside of one lucky time, when I had just once more reinstalled amdgpu driver. Still, there was no reason for that to be the fix. And so when I restarted the laptop, it stopped working again and I wasn't able to get back to it.

Also I got other errors from Xorg like 'xf86CloseConsole couldn't reach /dev/tty0' (I have no Idea why it wanted to close the non-existent tty) and when I ran it again, it went back to framebuffer problem...
I think a fresh install would fix that, thought there is no obvious reason to. Despite that, I am too lazy to reinstall it after so much pain and spending the whole day on it, so I resign on this issue. (But I haven't managed to find a way to close this)

Last edited by Kepis (2021-12-15 18:43:39)

seth · 2021-12-15 21:37:13

Doesn't matter.
The failure is likely caused by xorg 1.21 being less tolerant to bogus configs than 1.20 was.

Also

COMMAND=/usr/bin/pacman --sync -- xorg-server

don't do this. You're conducting partial updates what will expose you to potential version incompatibilities.

grep -r iGPU /{etc,usr/share}/X11/xorg.conf*

And run a complete system update to mitigate your previous partial updates

sudo pacman -Syu

Kepis · 2021-12-18 10:18:53

UPDATED: new installation

I have no xorg configuration:

```
$> ls -R /etc/X11
 xinit  xorg.conf.d

/etc/X11/xinit:
 xinitrc  xinitrc.d  xserverrc

/etc/X11/xinit/xinitrc.d:
 40-libcanberra-gtk-module.sh  50-systemd-user.sh

/etc/X11/xorg.conf.d:
 40-libinput.conf
$> ls /usr/share/X11
 app-defaults  locale  Xcms.txt  xkb  xorg.conf.d
$> ls /usr/share/X11/xorg.conf.d
 10-amdgpu.conf  10-quirks.conf  40-libinput.conf
```
Despite that, though I now managed to get Xorg working (I installed nvidia and uninstalled it again), now it often doesn't want to start on the first try after boot, until I press Ctrl+C in the tty and when logging out, whenever it takes any longer than an instant, xauth won't be able to lock my xauthority file.
Here is my current Xorg.1.log:
https://pastebin.com/cr1Hn1R4

I don't understand, why it looks for ati, fbdev and vesa, when I don't have it installed neither is any configuration file in the common folders.
Also, I must point out, once again, downgrading Xorg didn't solve the issue.

Last edited by Kepis (2021-12-18 22:08:32)

seth · 2021-12-18 12:59:05

now it often doesn't want to start on the first try after boot

https://wiki.archlinux.org/title/Kernel … _KMS_start

OK, once again, I have no xorg configuration:

You meant to say that you no longer have them - as is reflected by the updated xorg log…

[     3.544] (==) No Layout section.  Using the first Screen section.
[     3.544] (==) No screen section available. Using defaults.
[     3.544] (**) |-->Screen "Default Screen Section" (0)
[     3.544] (**) |   |-->Monitor "<default monitor>"
[     3.544] (==) No monitor specified for screen "Default Screen Section".

I don't understand, why it looks for ati, fbdev and vesa, when I don't have it installed neither is any configuration file in the common folders.

[ 3.559] (==) Matched amdgpu as autoconfigured driver 0
[ 3.559] (==) Matched ati as autoconfigured driver 1
[ 3.559] (==) Matched modesetting as autoconfigured driver 2
[ 3.559] (==) Matched fbdev as autoconfigured driver 3
[ 3.559] (==) Matched vesa as autoconfigured driver 4

Also, I must point out, once again, downgrading Xorg didn't solve the issue.

Why? Nobody but you has ever brought that up.

Kepis · 2021-12-18 13:23:56

You meant to say that you no longer have them - as is reflected by the updated xorg log…

No, it is not updated, it is a different installation, this is what I get from the system I have newly installed.
I also tried installing all those drivers it was missing and uninstalling them, in hope it would delete the code that tried to get to them, but it did not help.

About the 'autoconfigured' tag, what does that mean I have to do to not load the drivers?

Last edited by Kepis (2021-12-18 13:28:34)

seth · 2021-12-18 13:39:20

"updated" = "new log you posted in #11"
"different installation" = reason why the bogus config is no longer there
"autoconfigured" = the server detected that this driver might match your hardware and tries whether it can be loaded

And you want to check the link I posted in #12 because of your undeterministic success.

Kepis · 2021-12-18 22:12:04

Yes, I did have a look at your link, it certainly helped a lot fixing the randomness of first logins.
I am sorry for being so unintuitive. Also I should have clarified my question more clearly:
If I create an xorg.conf file with the minimal necessary config, will that make Xog stop looking for the other drivers?
I am not sure, whether that actually affects performance, it is purely out of curiosity.

seth · 2021-12-18 22:25:48

If I create an xorg.conf file with the minimal necessary config, will that make Xog stop looking for the other drivers?

Yes.

whether that actually affects performance

Not in a measurable way.

Configuring a specific driver is a common way to end up w/ a non-starting X11 driver because you forgot to remove the config when changing the HW or uninstalling the driver (to use the modesetting one)
The general advice is to keep the server config as lean and flexible as possible.

Arch Linux

#1 2021-12-15 13:47:18

[Solved] Xorg Error: Cannot run in framebuffer mode.

#2 2021-12-15 13:51:03

Re: [Solved] Xorg Error: Cannot run in framebuffer mode.

#3 2021-12-15 14:30:09

Re: [Solved] Xorg Error: Cannot run in framebuffer mode.

#4 2021-12-15 14:53:53

Re: [Solved] Xorg Error: Cannot run in framebuffer mode.

#5 2021-12-15 14:56:25

Re: [Solved] Xorg Error: Cannot run in framebuffer mode.

#6 2021-12-15 15:10:25

Re: [Solved] Xorg Error: Cannot run in framebuffer mode.

#7 2021-12-15 16:40:57

Re: [Solved] Xorg Error: Cannot run in framebuffer mode.

#8 2021-12-15 18:11:42

Re: [Solved] Xorg Error: Cannot run in framebuffer mode.

#9 2021-12-15 18:43:04

Re: [Solved] Xorg Error: Cannot run in framebuffer mode.

#10 2021-12-15 21:37:13

Re: [Solved] Xorg Error: Cannot run in framebuffer mode.

#11 2021-12-18 10:18:53

Re: [Solved] Xorg Error: Cannot run in framebuffer mode.

#12 2021-12-18 12:59:05

Re: [Solved] Xorg Error: Cannot run in framebuffer mode.

#13 2021-12-18 13:23:56

Re: [Solved] Xorg Error: Cannot run in framebuffer mode.

#14 2021-12-18 13:39:20

Re: [Solved] Xorg Error: Cannot run in framebuffer mode.

#15 2021-12-18 22:12:04

Re: [Solved] Xorg Error: Cannot run in framebuffer mode.

#16 2021-12-18 22:25:48

Re: [Solved] Xorg Error: Cannot run in framebuffer mode.

Board footer