Re: [gentoo-user] Odd problem with Xorg
On 11/30/18 1:33 AM, Peter Humphrey wrote: Thank you, Dan. I hadn't heard of it, but your report immediately suggested I try it to reduce the wait while chronyd started, on two machines here. Worked like a charm: no waiting for enough entropy to be collected. No problem. What's weird is that bug is known to affect kernels 4.16.x but all my machines use 4.14.x. Out of eight machines only one of them had this problem, which is even more strange. It does happen to be the oldest machine, though. That laptop has had slow boots, but not necessarily Xorg, for a long time and I could never figure it out. I even installed an SSD thinking it could've been the HDD in it a couple years ago; that's how long the slow booting has happened. Never occured to me the random number generator could cause that. Dan
Re: [gentoo-user] Odd problem with Xorg
Peter Humphrey wrote: > On Thursday, 29 November 2018 18:36:11 GMT wabe wrote: > > Daniel Frey wrote: > > > On 11/28/18 12:40 PM, Andrew Udvare wrote: > > > > > >> On Nov 28, 2018, at 15:09, Daniel Frey > > > > > >> > > > >> > > > > > >> wrote: > > > >> I've attached the two log files. > > > >> > > > > > I would like to see your syslog in both cases; dmesg output. > > > > > > > > I left the laptop sitting without logging in and when I came > > > > back ten minutes later I saw that Xorg started. > > > > > > I found this in the log: > > > > > > [ 298.914537] random: crng init done > > > [ 298.914542] random: 5 urandom warning(s) missed due to > > > ratelimiting > > > > > > So about five minutes after boot the random number finished > > > initializing and the Xorg started right after. > > > > You could install sys-apps/haveged. > > > > I really don't know if this will solve your actual problem, but > > maybe it helps to speed up the random generation. > > If you'd read the part you snipped, you'd have seen that Dan had > indeed tried haveged and it worked. > > Thank you, Dan. I hadn't heard of it, but your report immediately > suggested I try it to reduce the wait while chronyd started, on two > machines here. Worked like a charm: no waiting for enough entropy to > be collected. Ops. Sorry, I missed that part. -- wabe
Re: [gentoo-user] Odd problem with Xorg
On Thursday, 29 November 2018 18:36:11 GMT wabe wrote: > Daniel Frey wrote: > > On 11/28/18 12:40 PM, Andrew Udvare wrote: > > > > >> On Nov 28, 2018, at 15:09, Daniel Frey > > >> > > > > >> wrote: > > >> I've attached the two log files. > > >> > > > > I would like to see your syslog in both cases; dmesg output. > > > > > > I left the laptop sitting without logging in and when I came back > > > ten minutes later I saw that Xorg started. > > > > I found this in the log: > > > > [ 298.914537] random: crng init done > > [ 298.914542] random: 5 urandom warning(s) missed due to > > ratelimiting > > > > So about five minutes after boot the random number finished > > initializing and the Xorg started right after. > > You could install sys-apps/haveged. > > I really don't know if this will solve your actual problem, but maybe > it helps to speed up the random generation. If you'd read the part you snipped, you'd have seen that Dan had indeed tried haveged and it worked. Thank you, Dan. I hadn't heard of it, but your report immediately suggested I try it to reduce the wait while chronyd started, on two machines here. Worked like a charm: no waiting for enough entropy to be collected. -- Regards, Peter.
Re: [gentoo-user] Odd problem with Xorg
Daniel Frey wrote: > On 11/28/18 12:40 PM, Andrew Udvare wrote: > > > >> On Nov 28, 2018, at 15:09, Daniel Frey > > > >> wrote: > >> > >> I've attached the two log files. > > > I would like to see your syslog in both cases; dmesg output. > > I left the laptop sitting without logging in and when I came back > > ten minutes later I saw that Xorg started. > > I found this in the log: > > [ 298.914537] random: crng init done > [ 298.914542] random: 5 urandom warning(s) missed due to > ratelimiting > > So about five minutes after boot the random number finished > initializing and the Xorg started right after. You could install sys-apps/haveged. I really don't know if this will solve your actual problem, but maybe it helps to speed up the random generation. -- wabe
Re: [gentoo-user] Odd problem with Xorg
On 11/28/18 12:40 PM, Andrew Udvare wrote: On Nov 28, 2018, at 15:09, Daniel Frey wrote: I've attached the two log files. I would like to see your syslog in both cases; dmesg output. I left the laptop sitting without logging in and when I came back ten minutes later I saw that Xorg started. I found this in the log: [ 298.914537] random: crng init done [ 298.914542] random: 5 urandom warning(s) missed due to ratelimiting So about five minutes after boot the random number finished initializing and the Xorg started right after. After googling around I found a problem in kernels 4.16 that had this type of problem but: 4.14.78-gentoo I waded through results some more and found other having success installing haveged and setting it to start on boot... so I tried it and now the laptop boots normally! Weird. I guess it's solved? Dan
Re: [gentoo-user] Odd problem with Xorg
> On Nov 28, 2018, at 15:09, Daniel Frey wrote: > > I've attached the two log files. I would like to see your syslog in both cases; dmesg output.
[gentoo-user] Odd problem with Xorg
I have this very strange problem on my old laptop (12+ years... maybe it's just dying now...) When starting up, I have sddm configured to start up. But, it doesn't... it just sits there. If I log on as root, the X server immediately starts up. I'm aware of the suid issue on xorg-server. I've compiled with the +suid flag with no difference. I've tried the non-root setup, no difference. From the logs, X starts, says it's switching VTs then some seconds later it shuts down, nothing in the logs at all: [ 103.423] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 11) [ 103.423] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5 [ 103.423] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75 [ 103.423] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.040 [ 103.423] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1 [ 103.423] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1 [ 103.423] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000 [ 103.423] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4 [ 103.423] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found [ 103.423] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0) [ 103.423] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates" [ 104.833] (II) intel(0): EDID vendor "LPL", prod id 0 [ 104.833] (II) intel(0): EDID quirk: Detailed timings give vertical size in cm. [ 104.833] (II) intel(0): Printing DDC gathered Modelines: [ 104.833] (II) intel(0): Modeline "1280x800"x0.0 71.25 1280 1328 1360 1440 800 802 808 823 -hsync -vsync (49.5 kHz eP) [ 104.833] (WW) intel(0): Output LVDS1: Strange aspect ratio (289/2100), consider adding a quirk [ 107.067] (II) event3 - Power Button: device removed [ 107.086] (II) event4 - Video Bus: device removed [ 107.102] (II) event2 - Power Button: device removed [ 107.118] (II) event0 - Sleep Button: device removed [ 107.134] (II) event5 - AT Translated Set 2 keyboard: device removed [ 107.166] (II) AIGLX: Suspending AIGLX clients for VT switch [ 174.780] (II) UnloadModule: "synaptics" [ 174.780] (II) UnloadModule: "libinput" [ 174.780] (II) UnloadModule: "libinput" [ 174.780] (II) UnloadModule: "libinput" [ 174.780] (II) UnloadModule: "libinput" [ 174.780] (II) UnloadModule: "libinput" [ 174.788] (II) Server terminated successfully (0). Closing log file. It *always* fails on the first boot. This had been working before. When Xorg fails to start sddm doesn't even write anything to the its own log file. I've tried `emerge -e @world` as sometime it can fix bizarre problems such as this one, had no luck... I've attached the two log files. Anyone else have any suggestions? Dan [ 368.091] (--) Log file renamed from "/var/log/Xorg.pid-2129.log" to "/var/log/Xorg.0.log" [ 368.092] X.Org X Server 1.20.3 X Protocol Version 11, Revision 0 [ 368.092] Build Operating System: Linux 4.14.78-gentoo x86_64 Gentoo [ 368.092] Current Operating System: Linux lglaptop 4.14.78-gentoo #1 SMP Mon Nov 19 22:51:03 PST 2018 x86_64 [ 368.092] Kernel command line: BOOT_IMAGE=/boot/kernel-4.14.78-gentoo root=PARTUUID=88a3c0b3-06 quiet rootfstype=ext4 [ 368.092] Build Date: 22 November 2018 08:23:42AM [ 368.092] [ 368.092] Current version of pixman: 0.34.0 [ 368.092] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 368.092] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 368.093] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Nov 28 12:01:32 2018 [ 368.101] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 368.102] (==) No Layout section. Using the first Screen section. [ 368.102] (==) No screen section available. Using defaults. [ 368.102] (**) |-->Screen "Default Screen Section" (0) [ 368.102] (**) | |-->Monitor "" [ 368.102] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 368.102] (==) Automatically adding devices [ 368.102] (==) Automatically enabling devices [ 368.102] (==) Automatically adding GPU devices [ 368.103] (==) Max clients allowed: 256, resource mask: 0x1f [ 368.111] (==) FontPath set to: /usr/share/fonts/misc/, /usr/share/fonts/TTF/, /usr/share/fonts/OTF/, /usr/share/fonts/Type1/, /usr/share/fonts/100dpi/, /usr/share/fonts/75dpi/ [ 368.111] (==) ModulePath set to "/usr/lib64/xorg/modules" [ 368.111] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable
