Hikari: Abort Trap in Intel Hardware

F

Ferocious1881

I am trying to setup FreeBSD with wayland server in a laptop with Intel Integrated graphics that I have, it is a Acer Aspire R11, that was gifted to me, but I am being unable to setup the Wayland server as it gives me this error:

Code: 
Jul 27 05:44:10 hostname seatd[11813]: 01:00:26.534 [INFO] [seatd/server.c:146] New clent connected (pid: 86614, uid: 1001, gid: 1001)
Jul 27 05:44:10 hostname seatd[11813]: 01:00:26.534 [INFO] [seatd/seat.c:170] Added client 1 to seat0
Jul 27 05:44:10 hostname seatd[11813]: 01:00:26.536 [INFO] [seatd/seat.c:480] Opened client 1 on seat0
Jul 27 05:44:12 hostname seatd[11813]: 01:00:28.017 [INFO] [seatd/client.c:471] Client disconnected
Jul 27 05:44:12 hostname seatd[11813]: 01:00:28.017 [INFO] [seatd/seat.c:418] No clients on seat0 to activate
Jul 27 05:44:12 hostname seatd[11813]: 01:00:28.018  [INFO] [seatd/seat.c:524] Closed client 1 on seat0
Jul 27 05:44:12 hostname seatd[11813]: 01:00:28.018  [INFO] [seatd/seat.c:192] Removed client 1 on seat0

To replicate run the following as root in a fresh install of FreeBSD, with all hardenings enabled.

Code: 
pw groupmod video -m monkey
pkg install wayland seatd
mkdir -p /var/run/user/1001
chown monkey /var/run/user/1001
echo export XDG_RUNTIME_DIR=/var/run/user/1001 >> ~/.profile
pkg install drm_kmod
echo 'kld_list+="i915kms"' >> /boot/loader.conf
sysrc seatd_enable=YES
pkg install hikari alacritty
reboot
And then in your user with had to have uid 1001 run the following

Code: 
mkdir ~/.config/hikari
cp /usr/local/etc/hikari/hikari.conf ~/.config/hikari
hikari -c ~/.config/hikari/hikari.conf
 
You may try compiling drm-61-kmod from the ports but it shouldn't be necessary. I suppose it can't hurt, though... FWIW, on my intel laptop I have this installed, your mileage may vary:

Code: 
cpu-microcode-intel-20240531   Intel CPU microcode updates
gpu-firmware-intel-kmod-tigerlake-20230625 Firmware modules for tigerlake Intel GPUs
libva-intel-media-driver-23.4.3 VAAPI driver for Intel HD 5000 (Gen8) or newer
drm-61-kmod-6.1.92             DRM drivers modules
 
fmc000 said:
You may try compiling drm-61-kmod from the ports but it shouldn't be necessary. I suppose it can't hurt, though... FWIW, on my intel laptop I have this installed, your mileage may vary:

Code: 
cpu-microcode-intel-20240531   Intel CPU microcode updates
gpu-firmware-intel-kmod-tigerlake-20230625 Firmware modules for tigerlake Intel GPUs
libva-intel-media-driver-23.4.3 VAAPI driver for Intel HD 5000 (Gen8) or newer
drm-61-kmod-6.1.92             DRM drivers modules
Click to expand...
Also How do I compile drm-61-kmod?
 
SirDice said:
docs.freebsd.org

Chapter 4. Installing Applications: Packages and Ports

FreeBSD provides two complementary technologies for installing third-party software: the FreeBSD Ports Collection, for installing from source, and packages, for installing from pre-built binaries
docs.freebsd.org docs.freebsd.org
Click to expand...
So you are saying me that what fmc00 mean with compile is just install the port?, because the use of the work compile kind of implied to me something like clone some git repo and then compile or something like that.
 
Freebsd 14.1 already creates the XDG_RUNTIME_DIR directory and exports the variable

so you dont need to create the XDG_RUNTIME_DIR
or export it in your shell config

i have used hikari before and i started it with a script like this

Code: 
#!/bin/sh

# start dwl with dbus
exec dbus-launch --exit-with-session hikari
 
Here are some tutorials on install different Wayland window managers on Freebsd

dwl - wayland version of dwm

forums.freebsd.org

freebsd dwl wayland tiling window manager install

freebsd dwl wayland tiling window manager install with patches in a separate git branch. the reason why you need to build dwl on freebsd rather than using the port or packages is because the dwl package lets you set an variable called DWL_HOME_CONFIG that points to a dwl config.h file which...
forums.freebsd.org forums.freebsd.org

labwc - wayland version of openbox

forums.freebsd.org

labwc a stacking wayland window manager inspired by openbox

Labwc is a wlroots-based window-stacking compositor for wayland, inspired by openbox. In this video i cover window placement , setting the theme, creating keyboard shortcuts to switch workspaces and move windows to different workspaces and monitors How to warp your cursor between monitors...
forums.freebsd.org forums.freebsd.org

wayfire

forums.freebsd.org

Freebsd 14 Wayland and Wayfire using Nvidia on Dell XPS 15

Freebsd 14 Wayland running the Wayfire compositor on a Dell XPS 15 2019 using a Nvidia graphics card All the hardware works but you need to use wifibox for the wifi drivers, and nvidia on freebsd doesnt yet support nvenc and cuda the packages needed are nvidia-driver nvidia-settings...
forums.freebsd.org forums.freebsd.org

forums.freebsd.org

Freebsd 14 Wayland Desktop with Wayfire on a MacBook Air

Inspired by pure wayland desktop example i installed Freebsd on my old 2011 Macbook Air as a pure Wayland desktop with Wayfire in the video below i cover setting up wayland and wayfire with dbus for desktop notification with emacs ednc, zfs home datasets, beadm boot enviornments, ext2fs kernel...
forums.freebsd.org forums.freebsd.org
 
NapoleonWils0n said:
Freebsd 14.1 already creates the XDG_RUNTIME_DIR directory and exports the variable

so you dont need to create the XDG_RUNTIME_DIR
or export it in your shell config

i have used hikari before and i started it with a script like this
Click to expand...
That is not reflected in the Handbook https://docs.freebsd.org/en/books/handbook/wayland/#wayland-overview, whose instructions, which I followed, ask me to do such things.
NapoleonWils0n said:
Here are some tutorials on install different Wayland window managers on Freebsd
Click to expand...
There is one for Plasma 6?
 
fmc000 said:
The relevant part of the handbook has already been posted, please don't expect to be fed with all the detailed instructions. I compiled drm-61-kmod the second day I was using FreeBSD, if I did it anyone can do it.
Click to expand...
Manual entry unhelpful, I am at # cd /usr/ports/devel/git on my device, ran ls and is already populated, even if I delete everything under this tree, and ran all the commands in the section, it would be still unhelpful, as no instructions says how to find where is a port nor clear instructions of how to build, only suggesting with an example that you have to go to the port's directorty and run make. The manpage ports() agree with that conclusion, and looks to being centered everythings about that exact paradigm of going to the port's directory and run make commands.

But no one said me where to find that directory nor I have it in my memory from born, thus I ran sudo find / -iname "*drm-61*", which found the directory that I presume is your port directory as /usr/ports/graphics/drm-61-kmod, in which I am running the command sudo make install.

Therefore I shall said that
SirDice said:
docs.freebsd.org

Chapter 4. Installing Applications: Packages and Ports​

FreeBSD provides two complementary technologies for installing third-party software: the FreeBSD Ports Collection, for installing from source, and packages, for installing from pre-built binaries
docs.freebsd.org
docs.freebsd.org
Click to expand...
is a worse response that just saying ports(). And considering that it, possessively, is in a subdirectory in /usr/ports, makes it unhelpful to anyone that is not already familiarized with ports.

The response probably should have either be the refereed handbook page or ports(), with the directory of graphics/drm-61-kmod. It definitively should have included such directory.

This is not even considering that not doing graphics/drm-61-kmod is against the rules: Thread formatting-guidelines.49535.
 
Did you try using a different compositor, i.e. Wayfire that I'm sure it works on Intel because I tried it myself, of maybe just plain X11 with XFCE or MATE, which I'm also sure they work because of personal experiences?
 
Ferocious1881 said:
I did uninstall drm-kmod and then installed graphics/drm-61-kmod.
Click to expand...
Read my previous post carefully.
I do not at all said to deinstall graphics/drm-kmod.
DEINSTALL graphics/drm-515-kmod. Then, install graphics/drm-61-kmod.

graphics/drm-510-kmod, graphics/drm-515-kmod and graphics/drm-61-kmod are conflicting each other and cannot be installed at the same time.

And possibly I've overlooked, but graphics/drm-61-kmod builds only on OSVERSION >= 1400508.
This means it does not build on releases before 14.1.
To be precise, 5 or higher on digit at "hundred" means it's stable branch.
For 1400508, it's stable/14 before releng/14.1 is branched and newer than any of releng/14.0 branch. Currently, it's 1401501 when I'm writing this, becaise releng/14.1 branch is already created for 14.1-Release.
 
fmc000 said:
Did you try using a different compositor, i.e. Wayfire that I'm sure it works on Intel because I tried it myself, of maybe just plain X11 with XFCE or MATE, which I'm also sure they work because of personal experiences?
Click to expand...
Yes tried sway
Ferocious1881 said:
I get the same error when running sudo pkg install sway swayidle swaylock-effects alacritty dmenu-wayland dmenu && sway. As in the manual https://download.freebsd.org/doc/en/books/handbook/handbook_en.pdf
Click to expand...
 
You must log in or register to reply here.
Back
Top