How to tag keyboard to udev

E

escape

While installing desktop back as in this link about i386 support . (To use with Latex.)

The desktop has been installed using slim() -login manager. Slim opens a graphical display with a username and password prompt. The problem is that every keyboard event (button press) creates multiple stars as password and multiple unknown characters in username. Command startx does not work. It could be that some issue (modeset setting the resolution or other) has been bypassed by using slim. The problem seems to be the keyboard.

How can I tag the keyboard I'm using as a keyboard to 'udev' as in the last lines of Xorg.0.log ?

Bash: 
[140462.144] (II) event5  - Keychron Keychron K6, class 0/0, rev 2.00/1.01, addr 3: is tagged by udev as: Mouse
[140462.185] (II) event5  - Keychron Keychron K6, class 0/0, rev 2.00/1.01, addr 3: device is a pointer

udev seems to be a new addition to FreeBSD. There are no man -pages about this.

esc
 
This problem is update and upgrade related and this post should have been in another forum.

In the update from FreeBSD 12 to 14 there were (new?) xorg.conf files in default search path in /usr/local/share/X11/xorg.conf when there were old keyboard settings in /usr/local/etc/X11/xorg.conf.d. In these new files, in 40-libinput.conf the keyboard settings were given again. Probably the first one (the custom one) was the effectrive one. The keyboard problem was removed by removing double "InputClass" -entries. The old driver Driver "keyboard" does not work anymore and it should be replaced by Driver "libinput". This solved the keyboard problem.

Currently the X11 -session works with root -user. The slim does not work with the regular users. startx does not work with regular user (the only usual X user). It looks like that there are some init -scripts to go through. In the machine there was a custom configured XFCE -session still not working.
 
escape said:
In the update from FreeBSD 12 to 14 there were (new?) xorg.conf files in default search path in /usr/local/share/X11/xorg.conf when there were old keyboard settings in /usr/local/etc/X11/xorg.conf.d.
Click to expand...
None of these files had anything to do with upgrading the base OS. Xorg isn't part of the base.

You upgraded packages after the (major) version upgrade, as you should. If you went from 12.x to 14.x you very likely had an old x11/xorg installed. That got upgraded to the latest version.
 
escape said:
The xorg has changed?
Click to expand...
If you previously ran 12.x you have been missing at least 2 years worth of changes to x11/xorg. FreeBSD 12 has been EoL for quite some time.
escape said:
How about starting the XFCE, it does not yet work?
Click to expand...
If X doesn't work, anything running on top of X (like XFCE) certainly won't either.

What's in /etc/sysctl.conf? Anything in /boot/loader.conf from the 12 era that shouldn't be there anymore?
 
This must be a scholar regression analysis. Are you giving a grade?

Really. I have a problem. I'm trying to (as defined in the first post) take this XFCE4 back into use and lines

DISPLAY=":0.0"
export DISPLAY
XFSM_VERBOSE="1"
export XFSM_VERBOSE
xrdb .Xresources
xrandr --output VGA1 --fb 1280x1024 --rate 75.02 --panning 1280x1024+0+0 --verbose --primary
CK="ck-launch-session dbus-launch --exit-with-session"
exec ${CK} startxfce4 .my_display


creates a black screen where there is a mouse cursor. Mouse cursor moves. startx would start X11 session with two windows and a clock without this .xinitrc .

Why the display is not working?
 
escape said:
creates a black screen where there is a mouse cursor. Mouse cursor moves. startx would start X11 session with two windows and a clock without this .xinitrc .
Click to expand...
If you do NOT use your .xinitrc, you are saying X starts as non root and you wind up with TWM as a windowmanager.
Is that correct?

I'm assuming you have xterm install (which xterm) to verify.

If yes, create a .xinitrc containing JUST the line "exec xterm" then run startx. That should start X and a single xterm with no windowmanager.
If you get that far, move mouse to xterm, left click in window then type in "startxfce4" and see what happens.
No arguments like your ".my_display", no setting DISPLAY or anything else.


See what happens. Does it start? If so then then use that as your starting point. Add in lines one at a time from your original posed in #6.

To me the lines relating to DISPLAY and xrandr may be an issue.

escape said:
This must be a scholar regression analysis. Are you giving a grade?
Click to expand...

Completely unrelated but a bit of civility when asking for help from unpaid folk in the community goes a heck of a long way in getting a response.
 
For SLiM to work correctly ~/.xinitrc should look something like this:
Code: 
DEFAULTWM= startxfce4

[ -f "$HOME/.Xresources" ] && xrdb "$HOME/.Xresources"

if [ -n "$1" ]; then
        case $1 in
                default) exec ck-launch-session ${DEFAULTVM}
                         ;;
                *) exec $@
                         ;;
        esac
else
        exec ck-launch-session ${DEFAULTVM}
fi

Note that SLiM passes an argument depending on the DE/WM you picked (or sends "default").

Disable SLiM for the time being, login as a user and test your X with startx. The above .xinitrc should work with that too.
 
A nice way to install Desktop environments @"Installing a Desktop Environment on FreeBSD", written by FreeBSD Foundation. It looks easy. There are some tools to help to change the desktop environment. In this case it don't help.

SirDice said:
For SLiM to work correctly ~/.xinitrc should look something like this:
Click to expand...
I was not fixing slim and the script I've written is a simplified version executing the same command as I've written in this simplified script. Slim is ok. It is not about slim, there was a similar switch-case -structure.

mer said:
Completely unrelated but a bit of civility when asking for help from unpaid folk in the community goes a heck of a long way in getting a response.
Click to expand...
I think if it begins to be too regressive and not creatively solving the problem at hand, it must resemble a nonsense answer and actually what I've seen already elsewhere. This is why mentioning the scholar. I'm too wondering where one can get the bread and butter in computing and I can ensure that the wining is not going to help in it. Wining could help to improve the social behaviour, manners and the work culture. Eventually this is really high in the University. One should talk about the problem at hand instead of finding faults elsewhere.

mer said:
If you do NOT use your .xinitrc, you are saying X starts as non root and you wind up with TWM as a windowmanager.
Is that correct?
...
Click to expand...
Yes, it must be TWM as default around the windows. Something to add was to add the user into group video.
mer said:
...
See what happens. Does it start? If so then then use that as your starting point. Add in lines one at a time from your original posed in #6.
Click to expand...

A startxfce4 only. Here is an image of what happens with the correct localizations:
1771278103438.jpeg


Thunar I've found and installed. I wonder from what package the xfdesktop comes from. There is unable to connect to D-Bus and a file, is this a socket could not be found:
# ls -latr /tmp/*dbus*
ls: No match.
# service dbus onestart
dbus already running? (pid=1185).


dbus is enabled and running. Is hald needed?
 
After installing xfce4-desktop
again:
# pkg install xfce4-desktop

The following happened:
1771280618628.png


There are multiple desktops inside one other, the original xclock and xterm in the background.

This time the slim does not work.
 
You must log in or register to reply here.
Back
Top