On Fri, May 1, 2020 at 1:43 PM Ken Moffat <zarniwh...@ntlworld.com> wrote: > > On Fri, May 01, 2020 at 12:33:44AM -0400, Bud Rozwood wrote: > > Hi, > > > > I went through most of the X Window chapter in the BLFS version 9.1 but I > > can't seem to get the server going. I've attached my Xorg log file for > > reference. > > > > Umm, /var/log/Xorg.log ? That is the old way, running the server > as root. We now use rootless X with a log in ~/.local/share/xorg/ > unless you have added the '--enable-install-setuid' when building > the server (or chmod'd it afterwards). > > For sysvinit, that brings elogind and its dependencies (dbus, PAM, > build xorg-server, rebuild dbus), and then I reboot to be able to > use my mouse and keyboard in X. > > (for sysvinit, see the second Note in 'Testing Xorg') > > I think that systemd builds are now much the same in regard to X > (obviously, systemd replaced the very much cut down elogind) but > possibly do not need to reboot. > > Also, when I changed my own build to use rootless X (around the time > of our 9.0 release) it took me a long time to get it working, and > for a while I reverted to suid on the server to get past that. I > never did find exactly _why_ I'd had problems. > > Late thought after writing some stuff below: are you trying to run > X as root, to test the setup ? That would explain why it can log in > /var/log, but should not be necessary with current xorg drivers > (i.e. might be needed for very very old hardware, or maybe for > binary drivers, but you are using intel so those do not apply). > > > It's saying "XKB: Couldn't compile keymap" but I have XKBConfig installed. > > Could I be missing something? > > On my current systems I think I get those keymap messages on stderr > when I close X, so they are not critical. > > > [139291.219] > > X.Org X Server 1.20.7 > > X Protocol Version 11, Revision 0 > > [139291.222] Build Operating System: Linux 5.5.19 x86_64 > > [139291.223] Current Operating System: Linux zetasum 5.5.19 #1 SMP Fri Apr > > 24 17:40:50 UTC 2020 x86_64 > > [139291.223] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.5.19-lfs-9.1 > > root=/dev/sda4 ro > > [139291.224] Build Date: 30 April 2020 11:44:09PM > > [139291.225] > > [139291.226] Current version of pixman: 0.38.4 > > [139291.227] Before reporting problems, check http://wiki.x.org > > to make sure that you have the latest version. > > [139291.227] Markers: (--) probed, (**) from config file, (==) default > > setting, > > (++) from command line, (!!) notice, (II) informational, > > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > > Stripping down to concentrate on the (EE) messages: > > > [139291.232] (EE) dbus-core: error connecting to system bus: > > org.freedesktop.DBus.Error.FileNotFound (Failed to connect to socket > > /run/dbus/system_bus_socket: No such file or directory) > > [139291.232] (++) using VT number 6 > > I'm not sure if you are using sysvinit or systemd. This error, on > rootless X (i.e. without the server suid) would, I think, be enough > to stop the keyboard and mouse working (but X would start, giving > you an empty screen and requiring a reboot). > > With systemd, I guess you would not have a conventional log and > would need to use journalctl to read it - but in a mis-built or > misconfigured system I guess all manner of things are possible, > > > > > [139291.253] (II) LoadModule: "intel" > > [139291.253] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so > > [139291.253] (II) Module intel: vendor="X.Org Foundation" > > [139291.253] compiled for 1.20.7, module version = 2.99.917 > > [139291.253] Module class: X.Org Video Driver > > [139291.253] ABI class: X.Org Video Driver, version 24.1 > > [139291.253] (II) LoadModule: "modesetting" > > [139291.253] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so > > [139291.253] (II) Module modesetting: vendor="X.Org Foundation" > > [139291.253] compiled for 1.20.7, module version = 1.20.7 > > [139291.253] Module class: X.Org Video Driver > > [139291.253] ABI class: X.Org Video Driver, version 24.1 > > [139291.253] (II) LoadModule: "fbdev" > > [139291.254] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so > > [139291.254] (II) Module fbdev: vendor="X.Org Foundation" > > [139291.254] compiled for 1.20.7, module version = 0.5.0 > > [139291.254] Module class: X.Org Video Driver > > [139291.254] ABI class: X.Org Video Driver, version 24.1 > > [139291.254] (II) LoadModule: "vesa" > > [139291.254] (WW) Warning, couldn't open module vesa > > [139291.254] (EE) Failed to load module "vesa" (module does not exist, 0) > > Fine, not a problem. > > > [139291.254] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets: > > i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, > > 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, > > Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, > > GM45, 4 Series, G45/G43, Q45/Q43, G41, B43 > > > [139291.300] (II) intel(0): Setting screen physical size to 508 x 285 > > [139291.330] (EE) Error compiling keymap (server-0) executing > > '"/usr/bin/xkbcomp" -w 1 "-R/usr/share/X11/xkb" -xkm "-" -em1 "The > > XKEYBOARD keymap compiler (xkbcomp) reports:" -emp "> " -eml "Errors from > > xkbcomp are not fatal to the X server" "/tmp/server-0.xkm"' > > [139291.330] (EE) XKB: Couldn't compile keymap > > [139291.330] (EE) XKB: Failed to load keymap. Loading default keymap > > instead. > > [139291.345] (EE) Error compiling keymap (server-0) executing > > '"/usr/bin/xkbcomp" -w 1 "-R/usr/share/X11/xkb" -xkm "-" -em1 "The > > XKEYBOARD keymap compiler (xkbcomp) reports:" -emp "> " -eml "Errors from > > xkbcomp are not fatal to the X server" "/tmp/server-0.xkm"' > > As it says, not fatal. > > > [139291.345] (EE) XKB: Couldn't compile keymap > > [139291.345] XKB: Failed to compile keymap > > [139291.345] Keyboard initialization failed. This could be a missing or > > incorrect setup of xkeyboard-config. > > [139291.345] (EE) > > Fatal server error: > > [139291.345] (EE) Failed to activate virtual core keyboard: 2(EE) > > [139291.345] (EE) > > I think dbus is probably the cause of this. > > > Please consult the The X.Org Foundation support > > at http://wiki.x.org > > for help. > > [139291.345] (EE) Please also check the log file at "/var/log/Xorg.0.log" > > for additional information. > > [139291.345] (EE) > > [139291.345] (II) AIGLX: Suspending AIGLX clients for VT switch > > [139291.456] (EE) Server terminated with error (1). Closing log file. > > Alternatively, perhaps a full filesystem ? (/tmp, / or /home). > > If you have built dbus, elogind, fixed PAM, rebuilt dbus at any > point after the xorg libs, and built xorg-server without forcing > suid, then I think you could try rebooting and then running startx > as your normal user. > > ĸen > -- > See You Later, Holy Poppadom! > -- Red Dwarf, The Promised Land > -- > http://lists.linuxfromscratch.org/listinfo/lfs-support > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > Unsubscribe: See the above information page > > Do not top post on this list. > > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > A: Top-posting. > Q: What is the most annoying thing in e-mail? > > http://en.wikipedia.org/wiki/Posting_style
> Late thought after writing some stuff below: are you trying to run > X as root, to test the setup ? Sorry for not clarifying. I'm running it as normal user. > I'm not sure if you are using sysvinit or systemd. This error, on > rootless X (i.e. without the server suid) would, I think, be enough > to stop the keyboard and mouse working (but X would start, giving > you an empty screen and requiring a reboot). I'm using sysvinit. > I think dbus is probably the cause of this. I agree, I just noticed that error involving dbus as well. > For sysvinit, that brings elogind and its dependencies (dbus, PAM, > build xorg-server, rebuild dbus), and then I reboot to be able to > use my mouse and keyboard in X. I don't have elogind installed. It says that it's recommended but I didn't think it was a requirement. I was trying to install dbus without it using the option "--disable-systemd=no" but I still get the same error for dbus. -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
