X server does not want to start after installing dwm

Michael Warren · 2026-01-11T20:16:06+0000

Hello everybody !
I'm not entirely a noob to freebsd as It was my os of choice back when i managed a virtual private server.

Before i compiled dwm the x server was starting just fine... I tested moving the xterm for a bit then rebooted back to a tty to further configure dwm.
After finishing that up i created ~.xinitrc with just exec dwm and then i ran startx and this is what i got :

Code:

warren@:~/tmp % startx
xauth:  file /home/warren/.serverauth.4836 does not exist
xauth: (stdin):1:  bad display name ":0" in "add" command
xauth: (argv):1:  bad display name ":0" in "list" command
xauth: (stdin):1:  bad display name ":0" in "add" command
xauth: (argv):1:  bad display name "/unix:0" in "list" command
xauth: (stdin):1:  bad display name "/unix:0" in "add" command

/usr/local/libexec/Xorg.wrap: Only console users are allowed to run the X server
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
xauth: (argv):1:  bad display name "/unix:0" in "remove" command
xauth: (argv):1:  bad display name ":0" in "remove" command
warren@:~/tmp % exit

Code:

warren@:~/tmp % groups
operator video warren
i tried to add my account to console but it said console group does not exist so i'm confused  not sure what is  xorg rambling about

Errors loged in /var/log/Xorg.0.log

Code:

(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  5352.726] (EE) Failed to load module "intel" (module does not exist, 0)
[  5352.775] (EE)
[  5352.775] (EE) Cannot run in framebuffer mode. Please specify busIDs        for all framebuffer devices
[  5352.775] (EE)
[  5352.775] (EE)
[  5352.775] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[  5352.775] (EE)
[  5352.792] (EE) Server terminated with error (1). Closing log file.

My graphic cards

Code:

vgapci1@pci0:0:2:0:    class=0x030000 rev=0x01 hdr=0x00 vendor=0x8086 device=0x9a68 subvendor=0x1043 subdevice=0x13fc
    vendor     = 'Intel Corporation'
    device     = 'TigerLake-H GT1 [UHD Graphics]'
    class      = display
--
vgapci0@pci0:1:0:0:    class=0x030000 rev=0xa1 hdr=0x00 vendor=0x10de device=0x25a2 subvendor=0x1043 subdevice=0x13fc
    vendor     = 'NVIDIA Corporation'
    device     = 'GA107M [GeForce RTX 3050 Mobile]'
    class      = display
#i chose to only the intel kernel module to avoid dealing with nvidia

Loaded modules

Code:

warren@:~/tmp %kldstat
Id Refs Address                Size Name
 1  103 0xffffffff80200000  1f4daa0 kernel
 2    1 0xffffffff83200000   210318 i915kms.ko
 3    2 0xffffffff83411000    8a190 drm.ko
 4    1 0xffffffff831f9000     22b8 iic.ko
 5    2 0xffffffff8349c000     4120 linuxkpi_video.ko
 6    3 0xffffffff834a1000     7358 dmabuf.ko
 7    3 0xffffffff831fc000     3378 lindebugfs.ko
 8    1 0xffffffff834a9000     b480 ttm.ko
 9    1 0xffffffff834b5000     3390 acpi_wmi.ko
10    1 0xffffffff834b9000     21e8 hcons.ko
11    3 0xffffffff834bc000     30a8 hidmap.ko
12    1 0xffffffff834c0000     21e8 hms.ko
13    1 0xffffffff834c3000     21e8 hsctrl.ko
14    1 0xffffffff834c6000     4250 ichsmb.ko
15    1 0xffffffff834cb000     2178 smbus.ko
16    1 0xffffffff834ce000     6210 ig4.ko
17    1 0xffffffff834d5000    14958 fusefs.ko
18    1 0xffffffff834ea000     4d84 geom_uzip.ko
19    1 0xffffffff834ef000     3218 iichid.ko
20    1 0xffffffff834f3000     3355 hmt.ko
21    1 0xffffffff834f7000     22cc hconf.ko
22    1 0xffffffff834fa000     2a80 mac_ntpd.ko
23    1 0xffffffff834fd000     33c0 if_urndis.ko
24    1 0xffffffff83501000     31d0 uether.ko
25    1 0xffffffff83505000     2140 msdosfs_iconv.ko
26    1 0xffffffff83508000     4810 libiconv.ko

after figuring [ 5352.726] (EE) Failed to load module "intel" (module does not exist, 0) I installed the intel driver but that didn't fix the problem and honestly burnt out now.

marq · 2026-01-11T22:48:38+0000

Michael Warren said:
Hello everybody !
I'm not entirely a noob to freebsd as It was my os of choice back when i managed a virtual private server.

Before i compiled dwm the x server was starting just fine... I tested moving the xterm for a bit then rebooted back to a tty to further configure dwm.
After finishing that up i created ~.xinitrc with just exec dwm and then i ran startx and this is what i got :

Code:

warren@:~/tmp % startx xauth: file /home/warren/.serverauth.4836 does not exist xauth: (stdin):1: bad display name ":0" in "add" command xauth: (argv):1: bad display name ":0" in "list" command xauth: (stdin):1: bad display name ":0" in "add" command xauth: (argv):1: bad display name "/unix:0" in "list" command xauth: (stdin):1: bad display name "/unix:0" in "add" command /usr/local/libexec/Xorg.wrap: Only console users are allowed to run the X server xinit: giving up xinit: unable to connect to X server: Connection refused xinit: server error xauth: (argv):1: bad display name "/unix:0" in "remove" command xauth: (argv):1: bad display name ":0" in "remove" command warren@:~/tmp % exit

Code:

warren@:~/tmp % groups operator video warren i tried to add my account to console but it said console group does not exist so i'm confused not sure what is xorg rambling about [...] [HIGHLIGHT]Loaded modules [/HIGHLIGHT] [code] warren@:~/tmp %kldstat Id Refs Address Size Name 2 1 0xffffffff83200000 210318 i915kms.ko 3 2 0xffffffff83411000 8a190 drm.ko

after figuring [ 5352.726] (EE) Failed to load module "intel" (module does not exist, 0) i installed the intel driver but that didn't fix the problem and honestly burnt out now.

I'll take a stab/guess at this, but YMMV:

It looks like you have the accelerated Intel modesetting driver already loaded, so I think Xorg should automatically find and use it, if you have no xorg.conf overrides anywhere.
IIRC, the "intel" driver is the old/unaccelerated driver. Hmmm, do you have any explicit Xorg config directives in /etc/X11/xorg.conf or /usr/local/etc/X11/xorg.conf or /usr/local/etc/X11/xorg.conf.d/*? If so, overrides in any of those locations could be trying to load "intel" when it's probably not needed.
If your desktop environment normally starts before you login, that might explain why you're seeing different behavior when you instead run startx and get the error "Only console users are allowed to run the X server". Running startx is different than if your desktop environment starts the X server, and you login through a running X session.
You are in the video and operator groups, which I believe are the only groups you should need to have proper access to video hardware, at least I have a personal system where I'm in those groups, and I'm able to run startx without getting that error message.
Your X server logs were helpful, thank you for posting those.
It looks like the crux of your issue is that the Xorg.wrap executable doesn't think you have one of the necessary permissions (though it doesn't say exactly which), so one option is to follow the Xorg.wrap(1) manual page, which says that you could create /usr/local/etc/X11/Xwrapper.config, possibly with a line that contains:
Code:
```
allowed_users = myusername
```
specifically to allow Xorg.wrap to permit myusername to start Xorg. (FWIW, I don't think this should be required, at least I've never had to do that, and I normally use startx on my X systems)
If you created $HOME/.xinitrc with just one line that did exec dwm, keep in-mind that the X startup will run your .xinitrc file instead of the system-default one (/usr/local/etc/X11/xinit/xinitrc) -- that file does some initialization that you might now be skipping by running only dwm.

Hope something here helps..

Michael Warren · 2026-01-12T01:15:12+0000

marq said:
do you have any explicit Xorg config directives in /etc/X11/xorg.conf or /usr/local/etc/X11/xorg.conf or /usr/local/etc/X11/xorg.conf.d/*? If so, overrides in any of those locations could be trying to load "intel" when it's probably not needed.

Negative on all 3.

if your desktop environment normally starts before you login, that might explain why you're seeing different behavior when you instead run startx and get the error "Only console users are allowed to run the X server". Running startx is different than if your desktop environment starts the X server, and you login through a running X session.

i removed ~.xinitrc and rebooted then ran startx and unfortunately saw the same old errors.

marq said:
It looks like the crux of your issue is that the Xorg.wrap executable doesn't think you have one of the necessary permissions

Yea totally agree ,i don't even have Xorg.wrap installed to begin with so.... this can be either the problem or just irrelevant maybe there is a chance my system does not use wrapping policies and permissions are handled differently ??
Thank for trying to help me anyways. Now i'm thinking about installing the nvidia kernel module and the proprietary driver and giving xorg a last try, If it will still show erros i will switch to wayland and dwl instead.