startxfce4 not working

joe213

I am following this video tutorail on how to set up DragonFlyBSD.

https://www.youtube.com/watch?v=tPSP_9cNgOc&list=PLt69ZO6X8Hs2qcwYpmNnKyYWM_pum2LT3&index=20&t=113s

The only thing I have done differently was that I installed this on VirtualBox, I did install slim slim-themes however I did not add it via /etc/rc.config "slim_enable='YES" I did not add that at all, and I added an extra line, moused_enable="YES" and I logged in as root user.
For some reason when I typed startxfce4, I got this error message.

exec: xinit: not found

So I installed xinit pkg install xinit.

and when I tried to run startxfce4 again and I get this error message.

(EE) no screens found(EE)

What do I do from here to fix this issue?

Jay

joe213 please read this.. https://www.dragonflybsd.org/docs/how_to_get_to_the_desktop/

Jay

joe213 you will need dbus and hald also installed.. I will suggest adding

exec startxfce4

To ~/.xinitrc

And do startx

joe213

Jay

Jay exec startxfce4

To ~/.xinitrc

I did do that as well.

dbus is already installed and hald does not exist

I did do startx and again I get the same error.

Jay

joe213 did you configure xorg as shown in documentation above I shared ?

joe213

Jay Ok so DragonflyBSD mentions that if startx does not work, refer to FreeBSD 5.4

https://www.freebsd.org/doc/handbook/x-config.html

So over here, I tried the first command and i got this error.

rename /etc/X11/xorg.conf to /root/xorg.conf.etc: no such file or directory.

If I ran this OS on actual hardware, would it work fine?

Jay

joe213 why aren't you following dragonflybsd documentation I shared you? It shows how to configure xorg ?

joe213

Jay Cause on the site itself it said if startx is failing to load, then refer to FreeBSD and in my case startx did fail to load so I did follow its instructions.

joe213

Jay This is weird, I again installed xorg and now it works????

atayozcan

joe213 I think you were missing kld_list="/boot/modules/i915kms.ko" in your rc.conf which enables the use of Intel drivers causing this issue.