Fatal server error: (EE) cannot run in framebuffer mode. Please specif

casual · 2017-01-28 13:57:17

I did a long overdue update the other day after maybe 4-6 months of not updating (sudo pacman -Syu) and restarted this morning only to find this error when I try to log in to an account that runs startx (then goes back to the login prompt):

Fatal server error: (EE) cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices (EE) (EE)

I checked /var/log/Xorg.0.log, as it suggested and I see the same error and a bunch of data I don't know the relevance of. I had to add the '-f' flag to get the pacman update to run as one of the updates required it, and I wonder if it didn't change my video libraries from like AMD to Nvidia. I see some GeForce mentions in the Xorg.0.log file, which I don't think I was using any Geforce libraries before the update.

Any help would be greatly appreciated.

Last edited by casual (2017-01-28 14:07:53)

Trilby · 2017-01-28 14:39:34

casual wrote:

I see the same error and a bunch of data I don't know the relevance of.

We can't possibly know the relevance either unless you show them to us.
https://bbs.archlinux.org/viewtopic.php?id=57855

casual wrote:

I had to add the '-f' flag to get the pacman update to run as one of the updates required it

You forced the entire upgrade instead of reading the news. There's no telling what damage forcing the entire system update could do.

WorMzy · 2017-01-28 16:21:53

Trilby wrote:

casual wrote:
I had to add the '-f' flag to get the pacman update to run as one of the updates required it
You forced the entire upgrade instead of reading the news. There's no telling what damage forcing the entire system update could do.

Also, the -f option was removed from pacman over five years ago. What spinoff are you running?

casual · 2017-01-29 14:28:20

I just did a fresh install and I'm getting the exact same error so this must be unrelated to how I updated it. This is what's in /var/log/Xorg.0.log: https://ptpb.pw/3e04

Last edited by casual (2017-01-29 14:32:37)

Trilby · 2017-01-29 14:34:36

So now the original error is not there. But as you've nuked the system and started from scratch there's no way the original problem can be solved.

The reason it failed this time is that you did not follow all steps to install Xorg. You do not have a video driver.

casual · 2017-01-29 14:41:07

Seems like a huge coincidence that I get the exact same error on a fresh install, and I do have a video driver, nvidia-304xx.

casual · 2017-01-29 14:44:10

Nvm, you're right, the error is different.

casual · 2017-01-29 14:45:42

Honestly I would have tried to fix the original error but the way you responded I figured I bricked my system. My bad.

Trilby · 2017-01-29 14:46:47

(edit original post removed as it was cross posted with the above revisions).

Please note that you can edit your post rather than creating several new posts in sequence.

Are you sure the driver you have installed is the right one? What is your graphics hardware? Do you have the libgl package installed too? Do you need/have an xorg conf file for your nvidia driver?

Whatever happened before, the current problem is that your graphics driver is not properly installed or configured.

casual · 2017-01-29 15:00:47

I'm sure I have the driver the arch wiki suggested, which is for GF6000/7000 series. I have nvidia-304xx-libgl installed.

casual · 2017-01-29 15:12:37

I just tried running 'X -configure' and got this error: https://ptpb.pw/nEEs

loqs · 2017-01-29 15:13:24

If you have nvidia-304xx see https://bugs.archlinux.org/task/52734

seth · 2017-01-29 15:15:38

"pacman -Q | grep nvidia", installing libgl is NOT enough. You also need to install nvidia-304xx

casual · 2017-01-29 15:39:23

Do I have to recompile the sources after I change the line? And where are the sources stored? I don't have 'locate' setup.

loqs · 2017-01-29 15:49:35

Patching_in_ABS#Applying_patches also from there the linked page covering ABS and from there the pages on makepkg and PKGBUILD.
It can be confusing the first time you attempt to build a package from source / apply a patch. If you still have issues applying the patch after having read the above please post the commands you have used and the PKGBUILD after you have modified it.

casual · 2017-01-29 19:32:04

lol... I can't even untar the damn thing. I'm afraid this is beyond me at the moment. Maybe I'm not cut out for Arch. Thanks for all the help though.

Last edited by casual (2017-01-29 19:32:53)

casual · 2017-01-30 16:55:08

Decided to give this another shot. I'm confused, why don't I have /var/abs like the wiki is saying which stores all my PKGBUILDs?

loqs · 2017-01-30 17:24:57

https://bugs.archlinux.org/task/52734

Closed by Laurent Carlier (lordheavy)
Monday, 30 January 2017, 10:01 GMT
Reason for closing: Fixed
Additional comments about closing: nvidia-304xx-304.134-5

Is it not fixed with the version 5 release for you?
On the other point /var/abs will not be created until you run abs for the first time for instance

$ sudo abs extra/nvidia-304xx

Then copy the directory to somewhere belonging to the normal user to work on

$ cp -r /var/abs/extra/nvidia-304xx .
$ cd nvidia-304xx

You would apply the changes to PKGBUILD here

$ makepkg

Build the package

casual · 2017-01-30 18:19:16

Version 5 fixed it, thanks guys.

@loqs: so pacman doesnt use the abs system? Where does it store the PKGBUILDs then?

mrunion · 2017-01-30 18:24:57

Don't confuse the pacman cache: https://wiki.archlinux.org/index.php/Pa … kage_cache

with the ABS build system: https://wiki.archlinux.org/index.php/Arch_Build_System

Arch Linux

#1 2017-01-28 13:57:17

Fatal server error: (EE) cannot run in framebuffer mode. Please specif

#2 2017-01-28 14:39:34

Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif

#3 2017-01-28 16:21:53

Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif

#4 2017-01-29 14:28:20

Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif

#5 2017-01-29 14:34:36

Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif

#6 2017-01-29 14:41:07

Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif

#7 2017-01-29 14:44:10

Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif

#8 2017-01-29 14:45:42

Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif

#9 2017-01-29 14:46:47

Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif

#10 2017-01-29 15:00:47

Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif

#11 2017-01-29 15:12:37

Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif

#12 2017-01-29 15:13:24

Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif

#13 2017-01-29 15:15:38

Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif

#14 2017-01-29 15:39:23

Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif

#15 2017-01-29 15:49:35

Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif

#16 2017-01-29 19:32:04

Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif

#17 2017-01-30 16:55:08

Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif

#18 2017-01-30 17:24:57

Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif

#19 2017-01-30 18:19:16

Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif

#20 2017-01-30 18:24:57

Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif

Board footer