I'm currently in the middle of ongoing work on my BLFS 11.3 build. I followed the LFS 11.3 book on my x86_64 computer, except for six deviations.

One. As I did in my previous LFS 8.0, 8.1 and 11.2 11.2 installs, I am using the Slackware package tools as the package manager for my LFS. This is verified stable technology that I've used before. For LFS 11.2 on, a newer version of the tools was used, with the advantage of not needing a special version of tar as previous versions did. The Slackware package manager is briefly mentioned in Section 8.2.2.7, paragraph four of the LFS 11.3 book. Naturally this means the packages will not be compiled in the $LFS/sources directory but in a different directory tree, in which each package is compiled and packed in its own directory, while the package contents are installed to the usual locations.

Two. The "which" command is a dependency of one of the Slackware tools. I installed the shell script version from the BLFS book, along with the Slackware tools, before the first package of Chapter 8.

Three. The LFS phase, as was done in previous successful builds, was done in multiple sessions. $LFS is defined for all required users and scripting was created for mistake-free chrooting. The LFS volume is in /etc/fstab and is mounted at boot time.

Four. I installed my text editor instead of vim.

Five. Before the system was bootable, cryptsetup, cpio and lvm-related programs were compiled & installed, because all Linux distros on my computer reside on thin-provisioned LVM partitions.

Six. I'm using the 5.15.86 version of the kernel, because that worked so well with my hardware in my LFS 11.2 system.

A pause to quote from Chapter One of the LFS 11.3 book:

The LFS 11.3 install went well, with test results for the three critical packages of binutils, glib and gcc perfect matching those in the LFS book.

Having performed due-diligence as to disclosure about my deviations from the "established procedure," of the LFS 11.3 book, I will now begin my actual BLFS 11.3 question.



I finally got around to getting Xorg into my 11.3 system. Yay.

Root has a grand time running the twm (it's already there) and dwm (fast no-deps compile) window managers. Non-root, not so much. Xorg and the window manager (either one) is brought up correctly on non-root, including anti-alias fonts, but all keyboard and mouse inputs are ignored, requiring me to lean on the power button to get the computer to turn off.

Things I have tried:

• put "dbus-launch" in .xinitrc (note .xsession is a sym link to .xinitrc just to make sure)
• suid on the startx script
• have root set world read write on /dev/input/event* (got this idea from looking at the xorg log)

Those all failed. This is a new one in me. I've never had to put dbus-launch in before in any other install (would be OK if it worked, which it does not), nor have I ever had to resort to the chmod /dev/input/event* kludge. In the past, setting suid on startx was my ultimate fall-back always-works solution. Not this time.

I'm perplexed. Can anyone clue me in as to what I am overlooking in this apparently changed xorg?

Thank you.

I had the same problem. I solved it by adding my user to the group input. I don't know if that is a good way of solving it or if there is a better way.

1 members found this post helpful.

That worked. Yay! Thank you so much!