[SOLVED] FreeBSD 13 - xorg server will not load any desktop except for fluxbox
*BSDThis forum is for the discussion of all BSD variants.
FreeBSD, OpenBSD, NetBSD, etc.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
FreeBSD 13 - xorg server will not load any desktop except for fluxbox
Hello
Prior to freebsd 13, I was able to install and get any desktop manager to load.
I tried xfce4, kde5, mate and ratpoison. Neither will load from the xorg server. All I get is a black screen. No icons or anything but a mouse pointer.
The only desktop that will start via xorg server is fluxbox.
These four desktops used to worked in freebasd 11 and under.
I've install virtualbox-ose-addtions and enabled them.
I added myself to the wheel group for X11.
dbus and hald is enabled. Proc filesystem is added to /etc/fstab.
Nothing wrong with FreeBSD - it will run any window manager or desktop you'd like, including those with Wayland, although I never understood why, but that is another topic. There is an issue with your set up probably. I don't run FreeBSD with X so can't really help in that regard. Perhaps ask the question over at the FreeBSD Forums.
You waited until the fourth paragraph before dropping it in there that you're running FreeBSD in some crap x86 VM solution...
A lot of these big bloated desktops require hardware accel and/or other services such as dbus, the /proc file systen or whatever else - and even then they're designed for systemd/Linux. Hence why fluxbox or simple window managers will work whereas those may not.
It's not clear whether you're using a display manager or issuing startx from a terminal?
You waited until the fourth paragraph before dropping it in there that you're running FreeBSD in some crap x86 VM solution...
A lot of these big bloated desktops require hardware accel and/or other services such as dbus, the /proc file systen or whatever else - and even then they're designed for systemd/Linux. Hence why fluxbox or simple window managers will work whereas those may not.
It's not clear whether you're using a display manager or issuing startx from a terminal?
enigma9o7, GhostBSD is irrelevant.
OP tried openbsd cuz he couldnt get a window manager running, so he wasnt stuck on freebsd or something, and mate was one of the desktops he tried. So ghostbsd might possibly be an option, you're not OP are you, so how would you know what might be relevant? Plus its freebsd based... if OPs purpose was to make sure something compiles or runs under freebsd, it would be fine.
You waited until the fourth paragraph before dropping it in there that you're running FreeBSD in some crap x86 VM solution...
A lot of these big bloated desktops require hardware accel and/or other services such as dbus, the /proc file systen or whatever else - and even then they're designed for systemd/Linux. Hence why fluxbox or simple window managers will work whereas those may not.
It's not clear whether you're using a display manager or issuing startx from a terminal?
enigma9o7, GhostBSD is irrelevant.
Xfce4 and Mate are not heavy desktop managers like KDE plasma or gnome. And xfce4 works in openbsd ver 6.9 with dbus and proc enabled.
In the VM, I gave 3GB for ram and 3 CPUs for freeebsd.That's enough for a freebsd system.
Openbsd worked fine with xfce4, dbus and proc enabled and with just 2GB ram and 2 CPUs.
Like I said, these desktops worked fine in freebsd 11 and under.
Last edited by pbadillo555; 09-17-2021 at 05:14 PM.
OP tried openbsd cuz he couldnt get a window manager running, so he wasnt stuck on freebsd or something, and mate was one of the desktops he tried. So ghostbsd might possibly be an option, you're not OP are you, so how would you know what might be relevant? Plus its freebsd based... if OPs purpose was to make sure something compiles or runs under freebsd, it would be fine.
When I select VBoxSVGA or VBoxVGA and click OK, The VM shows VMSVGA as the default. It doesn't let me change the adapter type.
There's no reason you shouldn't be able to change it, unless you're trying to do it while the VM is running or something. Set it to VboxSVGA and give it 128MB VRAM should be ok....
There's no reason you shouldn't be able to change it, unless you're trying to do it while the VM is running or something. Set it to VboxSVGA and give it 128MB VRAM should be ok....
I only change the display type when the OS is not running.
Anyway, it doesn't keep the change I made. I changed it to VBoxSVGA, then I click OK.
I double check to see if it kept the change, and it doesn't. It reverts back to VMSVGA.
I did a reinstall of virtualbox awhile back and it still reverts back to VMSVGA.
It could be a bug, or virtualbox doesn't work well in linux Mint 22.
PS" I changed the VRAM to 128MB and it kept that change. Virtualbox keeps the changes for other settings, but it won't keep the display setting. Weird?????
Anyway, even with 128MB of VRAM, freebsd 13 still won't load xfce4. I still get the bare bones X environment with three terminals.
fluxbox and blackbox are the only ones that work.
Last edited by pbadillo555; 09-18-2021 at 12:09 AM.
I fixed the issue. It wasn't freebsd 13. The culprit was having 3D acceleration enabled.
If 3D acceleration is enabled. It will not let me use VBoxVGA nor VBoxVGA. It reverts back to VMSVGA.
Once I disabled 3D acceleration. I can now use VboxSVGA. And it finally keeps that setting.
Now xfce4 loads up in FreeBSD.
Having 3D acceleration enabled and VMSVGA is no problem with linux as a guest OS. I have to remind myself that FreeBSD is not linux. Linux supports more drivers and features.
On the other hand, OpenBSD worked with 3D acceleration enabled and with VMSVGA. And it loaded xfce4.
Weird...lol
Last edited by pbadillo555; 09-18-2021 at 10:51 PM.
For the record, you should still be able to enable acceleration on that driver; I have it enabled on my ghostbsd VM. But I dunno if its actually working or not; it does work on xp but only with old version of virtualbox (not 6.1; i think only 5.x?) so back when I was testing games on windows I used another version of virtualbox for that.... but anyways unless yer playing games in VM tho 3D doesnt really matter much.
For the record, you should still be able to enable acceleration on that driver; I have it enabled on my ghostbsd VM. But I dunno if its actually working or not; it does work on xp but only with old version of virtualbox (not 6.1; i think only 5.x?) so back when I was testing games on windows I used another version of virtualbox for that.... but anyways unless yer playing games in VM tho 3D doesnt really matter much.
I don't know what the developers are doing with virtualbox.
At least with my version of virtualbox 6.1.26, if 3D is enabled I cannot use VBoxSVGA nor VBoxVGA. It will revert back to VMSVGA. For me to use VBoxSVGA/VBoxVGA, I need to disable 3D.
The weird part is that openBSD worked with 3D and VMSVGA on. And xfce4 loaded as well.
PS: I don't do gaming in virtual machines, it's resource intensive. I do gaming on my linux host using MAME. I love the old classic MAME arcade games.
Last edited by pbadillo555; 09-19-2021 at 01:29 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
