Installing Xorg

F

fsck100

NOOB Warning

Installing on Intel Core i3, 16gb RAM - not VM

I am preparing to install for the first time. Below are the instructions I have for installing Xorg and XFCE. Just asking if this is correct procedure. Thanks.

## 1. Installing Xorg (the base graphical system)

Xorg provides the fundamental framework for a graphical environment.

### Steps:

1. **Open a terminal and become root:**
```sh
su
```
Enter your root password when prompted.

2. **Install the `xorg` package:** This is the easiest way to get a full Xorg installation.
```sh
pkg install xorg
```
Confirm the installation when prompted by pressing `y`.

3. **(Optional) Install a minimal Xorg:** For experienced users who want more control:
```sh
pkg install xorg-minimal
```
For most desktop users, the full `xorg` package is recommended.

4. **Install the Direct Rendering Manager (DRM) kernel module:** This is crucial for hardware acceleration.
```sh
pkg install drm-kmod
```

5. **Add your user to the `video` group:** Replace `<your_username>` with your actual username.
```sh
pw groupmod video -m <your_username>
```
If the `video` group doesn't exist, try adding to the `wheel` group:
```sh
pw groupmod wheel -m <your_username>
```

6. **Enable the DRM kernel module at boot:** Edit `/boot/loader.conf`:
```sh
ee /boot/loader.conf
```
Add the following line (adjust driver as needed):
```
kern.vty=vt
kld_list="amdgpu i915kms" # Example for AMD or Intel.
```
* **AMD:** Use `amdgpu` (newer) or `radeon` (older).
* **Intel:** Use `i915kms`.
* **NVIDIA:** Requires separate proprietary driver installation (search "nvidia freebsd install").

7. **Enable `devd`:** Edit `/etc/rc.conf`:
```sh
ee /etc/rc.conf
```
Add the line:
```
devd_enable="YES"
```

8. **Reboot your system:**
```sh
reboot
```

## 2. Installing a Well-Supported Desktop Environment

**XFCE** and **KDE Plasma** are generally the best-supported desktop environments on FreeBSD. **MATE** is also a good option.

### a) Installing XFCE

A lightweight, fast, and stable desktop environment.

1. **Become root:**
```sh
su
```

2. **Install the XFCE meta-package:**
```sh
pkg install xfce
```

3. **(Recommended) Install `sddm` display manager:**
```sh
pkg install sddm
```

4. **Enable `sddm` at boot:** Edit `/etc/rc.conf`:
```sh
ee /etc/rc.conf
```
Add:
```
sddm_enable="YES"
```
 
fsck100 said:
NOOB Warning
Click to expand...
Just follow the instructions in the handbook mate. That's why we have one: https://docs.freebsd.org/en/books/handbook/

fsck100 said:
**Enable the DRM kernel module at boot:** Edit `/boot/loader.conf`:
Click to expand...
No. Don't.

Code: 
kern.vty=vt
vt(4) has been the default console driver for several years now, don't need to set it. The 'old' sc(4) console driver is scheduled to be removed.
Code: 
kld_list="amdgpu i915kms" # Example for AMD or Intel.
Goes in /etc/rc.conf, not /boot/loader.conf. And you typically load one or the other (whichever one is appropriate for your system), not both.

Code: 
devd_enable="YES"
Doesn't need to be added to rc.conf, devd(8) is enabled by default (the system can't do much without it).
 
Well that was interesting. I installed according to the handbook and then my pc couldn't boot at all. Won't be doing that again. You can delete my account on this forum. I certainly will never be installing this garbage ever again.
 
SirDice said:
Just follow the instructions in the handbook mate. That's why we have one: https://docs.freebsd.org/en/books/handbook/


No. Don't.

Code: 
kern.vty=vt
vt(4) has been the default console driver for several years now, don't need to set it. The 'old' sc(4) console driver is scheduled to be removed.
Code: 
kld_list="amdgpu i915kms" # Example for AMD or Intel.
Goes in /etc/rc.conf, not /boot/loader.conf. And you typically load one or the other (whichever one is appropriate for your system), not both.

Code: 
devd_enable="YES"
Doesn't need to be added to rc.conf, devd(8) is enabled by default (the system can't do much without it).
Click to expand...
Just saying go to the handbook and providing a link to ... the handbook, at no specific page, isn't going to help a brand new person I can't think? Not to mention the page you land on is just that and typing xorg into the search on the index leads to....nothing.

I'm not sure if you mis-linked but nothing was accomplished here. I'd just erase this whole thread, it helps nothing, it eats a search result.

While I will say the handbook for setting up my first FreeBSD is the best documentation I've used in 52 years. I need not one YouTube video, just the text.

IDK, if someone leads with "NOOB warning" ?? I mean.
 
I use Firefox, and I've disabled all blocking (no scripts, don't care...). I also get nothing when I type xorg or Xorg.
However, Prin... manages to display the Printing chapter, WINE, OK, etc.
But Xorg, xorg = nothing.

Also in the chromium
Curious.
 
It's 5 commands or so to get a graphical screen with xterm. Install xinit, create ~/.xinitrc as basic startup script and type startx to run it without anything that calls itself desktop. (They always find themselves important) The script may not end. That's the end of the X session too.

Also: did you try without /etc/X11/xorg.conf? Default single screen almost always works.
 
SirDice said:
No. Don't.
Click to expand...
At least nvidia drivers (regardless DRM/KMS or old-school UMS) causes random mis-behaviors (usually panic or crash without panic) when loaded via /boot/loader.conf, because it's too large to be loaded before kernel takes over loader.
Note that tunables like hw.nvidiadrm.modeset and hw.nvidia.registry.EnableGpuFirmware are needed to be set BEFORE nvidia{-modesetting|-drm}.ko is loaded, otherwise these cannot be fetched on driver initialization.

Maybe Intel and AMD, too, too large.

SirDice said:
vt(4) has been the default console driver for several years now, don't need to set it. The 'old' sc(4) console driver is scheduled to be removed.
Click to expand...
Not 100% sure but isn't legacy BIOS boots defaulting back to sc when graphics supports are dropped from bootcodes for legacy BIOS (as of additions of newly added ZFS features)?
 
T-Aoki said:
Not 100% sure but isn't legacy BIOS boots defaulting back to sc when graphics supports are dropped from bootcodes for legacy BIOS (as of additions of newly added ZFS features)?
Click to expand...
Legacy BIOS boots (CSM, or really old systems) use vt(4) too (it has a 'vbefb' backend). Ever since they made the switch I've never seen it "automatically" fallback to sc(4), this was always a deliberate switch (setting kern.vty=sc). I deliberately switched on some really old systems, using really old (not KMS aware) Nvidia drivers. But that was mainly to be able to switch between ttyv9 (Xorg) and other consoles.

Maybe some 32 bit MIPS or PowerPC systems had some issues, but those have been deprecated now. Never owned or used one of those systems, so I have zero experience with it.

NB. While I'm here, seen the post long before it got reported. Can't be bothered to respond. Don't feed the trolls.
 
fjdlr said:
For clarity, I'll test with a clean Firefox profile.
Without any add-ons
Click to expand...
That's crazy!
Clean Firefox profile
Same here

pkg inf firefox


firefox-150.0,2
Name : firefox
Version : 150.0,2
Installed on : Sun Apr 19 14:51:51 2026 CEST
Origin : www/firefox
Architecture : FreeBSD:15:amd64
Prefix : /usr/local
Categories : wayland www
Licenses :
Maintainer : gecko@FreeBSD.org
WWW : https://www.firefox.com/
Comment : Web browser based on the browser portion of Mozilla
 
I type xorg freebsd into firefox (I use start page rather than google) and the Handbook chapter was the first thing that came up.

Second thing seems to be this thread. :)
 
scottro said:
I type xorg freebsd into firefox (I use start page rather than google) and the Handbook chapter was the first thing that came up.

Second thing seems to be this thread. :)
Click to expand...
I'm having trouble explaining this strange observation.
On the handbook's homepage (in the index search field), if I type "Xorg" or "xorg", no chapter appears.
However, "print", "Print", or "Printing" does indeed take me to the "Printing" chapter.
This is just one example; other occurrences also work.
It's purely anecdotal and has no impact on reading the handbook.
 
fjdlr said:
That's crazy, I'm going to test it with an OP user test profile to see.

But I don't understand the reason.
Same with Chromium.
Click to expand...
xorg and x11 aren't really good search words because they aren't in the text, apparently. The search seems only about the index.
"graphics" works.
 
There are two search boxes on the FreeBSD Handbook page.

One in the upper right corner left of the Donate-Button and one on the left side above the table of contents.

When I type xorg in the search box in the upper right corner I get search results. When I enter xorg in the
search box on the left side above the table of contents I get no result.
 
You must log in or register to reply here.
Back
Top