frozen login screen for Fury with xfce

User avatar
CodeSlinger
Posts: 8
Joined: Thu Mar 26, 2020 12:55 pm

Re: frozen login screen for Fury with xfce

Post by CodeSlinger »

Glad you found a solution. I was on the right track earlier, but didn't know why until I read... My bad for ignoring UPDATING.

Code: Select all

pkg updating | more
20200220:
AFFECTS: users of x11-servers/xorg-server
AUTHOR: zeising@FreeBSD.org

x11-servers/xorg-server has been updated to 1.20.7.

With this update, xorg-server has switched from using the devd backend to
the udev backend for device configuration on FreeBSD 12 and 13. If you have
issues with input devices, please see the install message for details.

The HAL backend option has been completely removed, as it was deprecated.

If you have problems with input devices, ensure that both x11/libinput and
x11-drivers/xf86-input-libinput are installed. They are installed in the
default configuration, but if you have a custom configuration, they might not
be.
Installing xorg-server now includes this message
Xorg-server has been installed.

If your kernel is compiled with the EVDEV_SUPPORT option enabled
(default starting from FreeBSD 12.1) it is recommended to enable evdev mode in
pointer device drivers like ums(4) and psm(4). This will give improvements like
better tilt wheel support for mice and centralized gesture support via
xf86-input-synaptics or libinput drivers for touchpads.

This is also needed for PS/2 devices to be properly detected by Xorg when
moused service is disabled in /etc/rc.conf and kernel is compiled with
EVDEV_SUPPORT.

To enable evdev in such a device, run the following:

# sysctl kern.evdev.rcpt_mask=6

To make it persistent across reboots, add the following to /etc/sysctl.conf:

kern.evdev.rcpt_mask=6
So after confirming I have xorg-server, xf86-input-keyboard, xf86-input-libinput, xf86-input-mouse, xorg-server, libinput, and setting kern.evdev.rcpt_mask=6, I have a working system.
--
CodeSlinger

aschiebe
Posts: 19
Joined: Sun Mar 29, 2020 10:43 am
Been thanked: 2 times

Re: frozen login screen for Fury with xfce

Post by aschiebe »

Hi Codeslinger,
all right I have now two working system, my vmclient and the nvidia desktop, both done with my steps and add moused to rc.conf.
Tanxs for help and hints.
But about your posts to xorger, where they mentinoned that dbus is depricated. If I comment out the dbus_enable="YES" in my rc.conf I end up in a black screen after reboot, tested on my vbox client, is this a misunderstanding that?
Looks like that the dbus_enable entry is still needed.
Nevertheless, my systems are updated and running well.
TanXs for your investigations,
Ciao Arnold

aschiebe
Posts: 19
Joined: Sun Mar 29, 2020 10:43 am
Been thanked: 2 times

Re: frozen login screen for Fury with xfce

Post by aschiebe »

for me my issue is done, but I can see no way how I can mark it as solved, maybe the admin can do this.
Please mark it as solved.
TanXs

Post Reply