FreeBSD/Setup: Difference between revisions

From KDE Community Wiki
(→‎Installing: the xf86-video-intel package (or something like that) is often needed)
Line 43: Line 43:
== quick start guide ==
== quick start guide ==


: <code>pkg ins -y kde5 sddm xorg</code>
: <code>pkg ins -y kde5 sddm xorg xf86-video-intel</code>


: <code>sysrc dbus_enable=yes && service dbus start</code>
: <code>sysrc dbus_enable=yes && service dbus start</code>

Revision as of 04:10, 2 June 2020

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 Dependencies

You should have the following packages installed and configured:

DBus

service dbus start

HAL

service hald onestart

procfs

Without them, either KDE software won't run, or you won't have a keyboard and mouse in the X Window System, which reduces its usefulness considerably.

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)

quick start guide

pkg ins -y kde5 sddm xorg xf86-video-intel
sysrc dbus_enable=yes && service dbus start
sysrc hald_enable=yes && service hald start
sysrc sddm_enable=yes && service sddm start

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

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 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
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
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)

hal

wikipedia:en:HAL (software)

https://www.freshports.org/sysutils/hal/ (Abstraction Layer for simplifying device access)

Recommendations

drm-kmod

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

Problems

See also