Bug 239811 - x11-servers/xorg-server 1.18.4 : (EE) Cannot run in frame buffer mode. Please specify busIDs for all framebuffer devices.
Summary: x11-servers/xorg-server 1.18.4 : (EE) Cannot run in frame buffer mode. Please...
Status: Closed Feedback Timeout
Alias: None
Product: Base System
Classification: Unclassified
Component: misc (show other bugs)
Version: 12.0-RELEASE
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-x11 mailing list
Depends on:
Reported: 2019-08-13 00:00 UTC by Jason Mours
Modified: 2019-10-30 18:53 UTC (History)
1 user (show)

See Also:

Xorg.0.log (5.80 KB, text/plain)
2019-08-13 00:10 UTC, Jason Mours
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jason Mours 2019-08-13 00:00:12 UTC
#Found something unknown¿
#Trace went from frame buffer to ¿######¿
#I had to key this in. I have no way to mount outside of beastie. Not authentic. Bad formatting hu-man.

xauth:   file /root/.serverauth.3843 does not exist
xauth:   file /root/.Xauthority does not exist
xauth:   file /root/.Xauthority does not exist

X.Org X Server 1.18.4
Release Date: 2016-07-19
X Protocol Version 11, Revision 0
Build Operating System: FreeBSD 12.0-RELEASE-p5 amd64
Current Operating System: FreeBSD dae.0psi.localdomain 12.0-RELEASE FreeBSD 12.0-RELEASE r341666 GENERIC amd64
Build Date: 16 May 2019  09:00:46AM

Current version of pixman: 0.34.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version.

Markers: (--) probed, (**) from config file, (==) default settings, (++) from command line, (NI) not implemented, (??) unknown.
(==) Log File: "/var/log/Xorg.0.log", Time: Mon Aug 12 18:00:06 2019
(==) Using system config directory "/usr/local/share/X11/xorg.conf.d"
scfb trace: probe start
scfb trace: probe done
Fatal server error:
(EE) Cannot run in frame buffer mode. Please specify busIDs        for all framebuffer devices.
Please consult the The X.Org Foundation support at http://wiki.x.org for help.
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE) Server terminated with error (1). Closing log file.
xinit; giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

# I think ¿######¿ is a paige.
Comment 1 Jason Mours 2019-08-13 00:10:52 UTC
Created attachment 206483 [details]
Comment 2 Jason Mours 2019-08-13 01:33:25 UTC


#a dark shader.
#you don't have to 'dark'....of course, purple. It is to black a green.

#To toaster that cyan would be really neat. 64KiB for the 'i'. This is probably the 'window'.
Comment 3 Jason Mours 2019-08-29 22:43:35 UTC
This is not a 'pci' bus, maybe serial, something. I believe scfb is trying to 'pci' this bus in EFI. 

I still like an EFI RGB dshader. How about xCompositorX? It's in the X. Layers down, Deep.  Wavelengths? Gravity? Toasts? Cyan? Magenta? 128 KiB ... resolution in the microns. That's lab, and more C, bits & extents. Real X.  >IBM< . This is not scfb anymore, which is stretching the EFI and needs looked at. 

This could be real enough to show wayland. It's a '6'. They're far in fabric. More than I can contribute with my uHF TV camera. I think they are way past TV.
Comment 4 Niclas Zeising freebsd_committer 2019-09-24 11:03:59 UTC
I'm not entirely sure what issue you are reporting, can you give more detail? As the error message indicates, when using scfb, which is frambe buffer mode, then you need to specify busID for all framebuffer devices in xorg.conf, scfb cannot detect that on it's own.