FreeBSD/Setup: Difference between revisions

From KDE Community Wiki
(Quick start first (OK?))
m (VBoxSVGA is good with virtualbox-ose-additions 6.1.18. Make the quick start a little more readable.)
Line 1: Line 1:
== Quick start ==
== Quick start ==


Have a suitable driver for your graphics hardware:
=== Graphics first ===
* if you install KDE in VirtualBox, install [https://www.freshports.org/emulators/virtualbox-ose-additions-legacy/ emulators/virtualbox-ose-additions-legacy] 5.2.44_3 (for some, not all, desktop environments, virtualbox-ose-additions [https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254464#c3 6.1.18 is bugged])
* for real hardware, [https://www.freshports.org/graphics/drm-kmod/ graphics/drm-kmod] might be appropriate.


Then:  
For a VirtualBox virtual machine:


# if not already mounted, <code>mount -t procfs proc /proc</code> – see below (''process file system'') to have [https://man.freebsd.org/procfs(5) procfs(5)] mounted automatically  
# preset the machine to VBoxSVGA – '''not''' VMSVGA
# start the machine
# install [https://www.freshports.org/emulators/virtualbox-ose-additions/ emulators/virtualbox-ose-additions] 6.1.18 or greater
# observe the [https://www.freshports.org/emulators/virtualbox-ose-additions/#message package message].
 
For a real machine:
 
* the usual solution is [https://www.freshports.org/graphics/drm-kmod/ graphics/drm-kmod]
 
– and for whatever is installed by drm-kmod, observe the package message.
 
=== KDE and the rest ===
 
# If not already mounted, <code>mount -t procfs proc /proc</code> – or to have [https://man.freebsd.org/procfs(5) procfs(5)] mounted automatically, [[#Other_requirements|see below]]
# <code>pkg install -y kde5 sddm xorg</code>
# <code>pkg install -y kde5 sddm xorg</code>
# <code>sysrc dbus_enable="YES" && service dbus start</code>
# <code>sysrc dbus_enable="YES" && service dbus start</code>

Revision as of 20:42, 25 April 2021

Quick start

Graphics first

For a VirtualBox virtual machine:

  1. preset the machine to VBoxSVGA – not VMSVGA
  2. start the machine
  3. install emulators/virtualbox-ose-additions 6.1.18 or greater
  4. observe the package message.

For a real machine:

– and for whatever is installed by drm-kmod, observe the package message.

KDE and the rest

  1. If not already mounted, mount -t procfs proc /proc – or to have procfs(5) mounted automatically, see below
  2. pkg install -y kde5 sddm xorg
  3. sysrc dbus_enable="YES" && service dbus start
  4. sysrc sddm_enable="YES" && service sddm start
  5. when logging in, avoid the Plasma (Wayland) … default that's presented by sddm – for Plasma, Wayland is not yet reliable.

Setup

To install the current official release, get ports or packages.

To install the bleeding edge, get area51.

Once you have installed whichever version of KDE you like (official ports of KDE4, or KDE Frameworks, Plasma Workspace and Applications from area51, as of early 2017), there are a few more steps to get it running, which we try to list here.

X Window System

To use KDE Software Compilation on FreeBSD, X.Org is required. If you still don't have it, you'll need to install and configure it properly.

Other requirements

Without these things:

  • the X Window System might not recognise your keyboard, mouse or other pointing device
  • some KDE software will not run.
D-Bus

devel/dbus

sysrc dbus_enable="YES" && service dbus start

https://man.freebsd.org/dbus-daemon(1)

process file system

https://man.freebsd.org/procfs(5)

Suggested fstab entry:

proc /proc procfs rw 0 0

FreeBSD Quickstart Guide for Linux® Users: procfs: Gone But Not Forgotten

Starting KDE4

After installing KDE workspace (`x11/kde4-workspace`) either via ports or packages, you can add `kdm4_enable="YES"` to `/etc/rc.conf` to boot into KDE Plasma Desktop via KDM, the KDE Display Manager.

Starting KDE Plasma 5 Workspace

After installing KDE Plasma 5 Workspace (`x11/plasma5-plasma-workspace`) either via ports or packages, you must also install SDDM.

rewrite

by Vater (talk) 18:02, 3 January 2019 (UTC)

Installing

The easiest way to get KDE running (on nearly every FreeBSD box) is to install the KDE binary packages from the standard FreeBSD repository.

#Installing by using the Binary Package Management

The other way to install the KDE is to compile it from (FreeBSD) ports.

#Installing by using the FreeBSD Ports Collection

And you can also install by cloning and compiling sources directly like for Area 51.

#Installing by using the sources for the FreeBSD Port

Installing by using the Binary Package Management

FreeBSD Handbook:Installing Applications: Packages and Ports/Using pkg for Binary Package Management

The default repository for binary packages on FreeBSD is quarterly. An alternate repository for FreeBSD is latest provided from FreeBSD as well.

#Changing the binary packages repository

It is recommended to install and use (#X.Org minimal or) #X.Org.

It is recommended to install and use #SDDM.

Installing only the small stack of KDE Plasma by using the Binary Package Management

Installing the binary package x11/plasma5-plasma (KDE5 plasma meta port)

pkg ins -y plasma5-plasma

#Installing the minimal stack of X.Org by using the Binary Package Management

Optional (To have a first terminal emulator.) installing the (recommended) binary package x11/konsole

pkg ins -y konsole

Installing only a basic stack of KDE by using the Binary Package Management

#Installing only the small stack of KDE Plasma by using the Binary Package Management

Installing the binary package x11/kde-baseapps (KDE5 baseapps meta port)

pkg ins -y kde-baseapps

Installing the full stack of KDE by using the Binary Package Management

Installing the binary package x11/kde5 (KDE Plasma Desktop and Applications (current))

pkg ins -y kde5

#Installing the full stack of X.Org by using the Binary Package Management

Installing Wayland by using the Binary Package Management

Running KDE with Wayland do not work (2020-02).

Installing the binary package x11/plasma5-kwayland-integration (Integration plugins for a Wayland-based desktop)

pkg ins -y kde5

Installing X.Org by using the Binary Package Management

Installing the minimal stack of X.Org by using the Binary Package Management

Installing the (recommended) binary package x11/xorg-minimal (X.Org minimal distribution metaport)

pkg ins -y xorg-minimal

#Installing the graphics driver for X.Org by using the Binary Package Management

Installing the full stack of X.Org by using the Binary Package Management

Installing the (recommended) binary package x11/xorg (X.Org complete distribution metaport)

pkg ins -y xorg

#Installing the graphics driver for X.Org by using the Binary Package Management

Installing the graphics driver for X.Org by using the Binary Package Management

Search a (recommended) graphics driver package for your (hardware) graphics chipset (usually can be find as a part of the x11-drivers category)

pkg sea xf86-video

Installing the (recommended) graphics driver package for your (hardware) graphics chipset x11-drivers/xf86-video-intel (Driver for Intel integrated graphics chipsets)

pkg ins -y xf86-video-intel

Installing the (recommended) graphics driver package for your (hardware) graphics chipset x11-drivers/xf86-video-intel (Driver for Intel integrated graphics chipsets) Adding all the user accounts for the (hardware accelerated X11 sessions) to the group video

If you are the one and only user for the graphical user interface with X11 like KDE.
pw groupmod video -m the-one-and-only-kde-user
or
For more than one user a comma-separated list of user names (for example kde-user-1 and kde-user-2).
pw groupmod video -m kde-user-1,kde-user-2

Installing SDDM by using the Binary Package Management

Installing the binary package x11/sddm

pkg ins -y sddm

#Installing the minimal stack of X.Org by using the Binary Package Management

additional packages

Optional installing the binary package deskutils/plasma5-sddm-kcm

pkg ins -y plasma5-sddm-kcm

Optional installing the binary package x11-themes/sddm-freebsd-black-theme

pkg ins -y sddm-freebsd-black-theme

Changing the binary packages repository

On FreeBSD are a lot of useful tools that optional can be used. For example there is beadm (package sysutils/beadm), a tool to create create and manage ZFS snapshots of your system (independent from your home directory data).

Checking the binary packages repository

Optional printing the standard configuration file for the pkg binary package management (to the standard output)

cat /etc/pkg/FreeBSD.conf

On a default FreeBSD you should get the following.


FreeBSD: {
  url: "pkg+http://pkg.FreeBSD.org/${ABI}/quarterly",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/share/keys/pkg",
  enabled: yes
}

Optional checking the standard directory for custom configurations of the pkg binary package management and printing all configuration files in the standard directory for custom repositories of the pkg binary package management (to the standard output)

ls /local/etc/pkg/ && cat /local/etc/pkg/repos/*

On a default FreeBSD you should get the following.

ls: /local/etc/pkg/: No such file or directory
Changing the binary packages repository quick & dirty

Replacing pkg+http://pkg.FreeBSD.org/${ABI}/quarterly with pkg+http://pkg.FreeBSD.org/${ABI}/latest in the standard configuration file for the pkg binary package management

sed -i '' -e 's/pkg.FreeBSD.org\/\${ABI}\/quarterly/pkg.FreeBSD.org\/\${ABI}\/latest/g' /etc/pkg/FreeBSD.conf

Updating all (currently) installed binary packages

pkg upg -y
Changing the binary packages repository the exemplary FreeBSD way

Installing by using the FreeBSD Ports Collection

FreeBSD Handbook:Installing Applications: Packages and Ports/Using the Ports Collection

Installing SDDM by using the FreeBSD Ports Collection

Installing by using the sources for the FreeBSD Port

Dependencies

display server

Wayland

Configuring Wayland

X.Org

or
X.Org minimal

a smaller stack of #X.Org

Configuring X.Org

display manager

SDDM

SDDM is highly recommended to get KDE running easily. (So you can avoid some problems. SDDM helps to choose the right Screen for example.)

or
Configuring SDDM
Configuring SDDM by using plasma5-sddm-kcm

If you installed sddm by binary package you have to set this rule in order to get this module functional:

Create this file /usr/local/etc/polkit-1/rules-d/40-wheel-group.rules with this content:

polkit.addRule(function(action, subject) {
    if (subject.isInGroup("wheel")) {
    	return polkit.Result.YES;
    }
});

and restart the session.

Configuring SDDM by using the configuration file
diff /usr/local/etc/sddm.conf.sample /usr/local/etc/sddm.conf
$EDITOR /usr/local/etc/sddm.conf

Likewise, if you installed sddm using binary packets perhaps you cannot find sddm.conf and sddm.conf.sample files. You can get one by launching

# sddm --example-config /usr/local/etc/sddm.conf
Service SDDM

Starting the service sddm once

service sddm onestart

Stopping the service sddm once

service sddm onestop

Enabling the service sddm for system starts

sysrc sddm_enable=yes

Starting the (enabled) service sddm now

service sddm start

dbus

wikipedia:en:D-Bus

https://www.freshports.org/devel/dbus/ (Message bus system for inter-application communication)

Recommendations

drm-kmod

https://www.freshports.org/graphics/drm-kmod/ (Metaport of DRM modules for the linuxkpi-based KMS components)

Problems

See also