From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 83A62158041 for ; Thu, 4 Apr 2024 04:55:56 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 94A6BE2A70; Thu, 4 Apr 2024 04:55:49 +0000 (UTC) Received: from fout3-smtp.messagingengine.com (fout3-smtp.messagingengine.com [103.168.172.146]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 2921FE2A4D for ; Thu, 4 Apr 2024 04:55:49 +0000 (UTC) Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailfout.nyi.internal (Postfix) with ESMTP id AA1D91380164 for ; Thu, 4 Apr 2024 00:55:48 -0400 (EDT) Received: from imap43 ([10.202.2.93]) by compute6.internal (MEProxy); Thu, 04 Apr 2024 00:55:48 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gustafsson.io; h=cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm1; t=1712206548; x=1712292948; bh=GdqLIXxwSF 6bR/R6BUZc2yK5clDuyYABI0p5h0W+WH8=; b=YWG2QlDNB3xD7oxPzW8cKsoL1V +gd73Pgz1Sc1kZmA4H0gotdQw1GfIlmQExE2k42XLBb2v2ulxUBYfGmy52q+xRt0 HOfNqnRsHtZwlQIXn4fWMw8pEBVT/91jF2eyygg83ZawgF/SJ4fZaagh6eKmZasJ eB8SKMx6yw2XNEcBEQmzVD0ecH7FM+lsQUZsvW7bfFl3xfnS5J2WWFSSF8Y+P8hs 3RDl9SLIBbRuLJ6Vw7JIydbsOkczixvhG9yvGpWvaLZmqheUBDoHX297eL5+Zr5y 6zTZ1qetfaHAX+frGQRk+NGKlRZAqyRmylxqKLi/Y7yPXVtT7BzfNzxEY64w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; t=1712206548; x=1712292948; bh=GdqLIXxwSF6bR/R6BUZc2yK5clDu yYABI0p5h0W+WH8=; b=xvmWad9qcj2hDLtClbqQwb8geLwUPaYHOnRi3xVSo+Zb 9HFjnLY8QrdISbX9p92WNuiXWrLNsZ9M0D7norBvX/VM3YmhpjwbFZLKwj5WIdqI 6mUmie41YOcJMWTzGaFyoLggw0ll7rqPXfEqHG2ba1CSa1USZR/E7sYuh5AIIR2v xQb6p8tNC+WEJpbslOT4KDKR7aEXJoXVeIQbgYXz6eFJvDnbadJX73e8UgOGV3+d ThZ4Eri2pn8n88J7/40h/WGfkk+LXHPhylapmiyFjK1Cr1FpLuT9ED3t1jWKW/Jg 2ziMsTn3plG+/FN7QWUWhMh9SH14wNtx5vwy8rNz2g== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrudefjedgledtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsehttd ertderredtnecuhfhrohhmpedfofgrrhhkuhhsucfiuhhsthgrfhhsshhonhdfuceomhgr rhhkuhhssehguhhsthgrfhhsshhonhdrihhoqeenucggtffrrghtthgvrhhnpeektdfgfe fhveevheeifeduveevkeduudeiledvtdefjefgueelvedtgfdutdekfeenucffohhmrghi nhepghgvnhhtohhordhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpe hmrghilhhfrhhomhepmhgrrhhkuhhssehguhhsthgrfhhsshhonhdrihho X-ME-Proxy: Feedback-ID: i5ee1425c:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id 601932D4007D; Thu, 4 Apr 2024 00:55:48 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.11.0-alpha0-333-gbfea15422e-fm-20240327.001-gbfea1542 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Message-Id: In-Reply-To: <2272199.iZASKD2KPV@rogueboard> References: <2272199.iZASKD2KPV@rogueboard> Date: Thu, 04 Apr 2024 06:55:20 +0200 From: "Markus Gustafsson" To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Every other startup results in a black screen (possibly SDDM related?) Content-Type: text/plain X-Archives-Salt: 9a5660a0-10af-42ee-8e27-858c04d1dd68 X-Archives-Hash: 5a48f19abc141a6c4fe3cdc9505fad32 Hi again, I tried to catch the error again and while doing so I realized you guys are of course correct: sddm usually starts on tty 2. I don't know why I got it into my head that it would start on tty 8. Anyway, when I finally got it to reproduce (took a few restarts) I didn't get a blinking cursor on tty 2, the monitor just goes to sleep (kind of like it does when it has no signal). Switching to tty 1 showed me the init log and let me log on so I could run the commands suggested earlier in this thread: > $ ps aux | grep sddm > root 2253 0.0 0.0 142408 14248 ? Ssl 06:26 0:00 /usr/bin/sddm > root 2300 0.2 0.2 1653332 89588 ? Ssl 06:26 0:00 /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_UanezA -noreset -displayfd 16 > root 2358 0.0 0.0 61872 14024 ? S 06:26 0:00 /usr/libexec/sddm-helper --socket /tmp/sddm-auth-49123ec6-075d-4982-860d-ea1de56059ca --id 2 --start /usr/bin/sddm-greeter --socket /tmp/sddm-:0-emmSdV --user sddm --greeter > sddm 2359 0.0 0.4 1557540 135804 ? Sl 06:26 0:00 /usr/bin/sddm-greeter --socket /tmp/sddm-:0-emmSdV > sddm 2365 0.0 0.0 4320 1892 ? S 06:26 0:00 dbus-launch --autolaunch d3bb17ba0dc5f70ad177e3f764fe168e --binary-syntax --close-stderr > sddm 2366 0.0 0.0 4620 224 ? Ss 06:26 0:00 /usr/bin/dbus-daemon --syslog-only --fork --print-pid 5 --print-address 7 --session > $ rc-service sddm status > * rc-service: service `sddm' does not exist This is what the command yields for a successful startup as well though. Should 'sddm' perhaps be 'display-manager' in the command above? Anyway: > rc-status > Runlevel: default > sysklogd [ started ] > dhcpcd [ started ] > dbus [ started ] > netmount [ started ] > chronyd [ started ] > cupsd [ started ] > switcheroo-control [ started ] > display-manager [ started ] > numlock [ started ] > local [ started ] > Dynamic Runlevel: hotplugged > Dynamic Runlevel: needed/wanted > display-manager-setup [ started ] > avahi-daemon [ started ] > Dynamic Runlevel: manual This is also what it looks like for a successful startup. And finally from /var/log/sddm.log: > [06:26:03.740] (II) DAEMON: Initializing... > [06:26:03.743] (II) DAEMON: Starting... > [06:26:03.743] (II) DAEMON: Logind interface found > [06:26:03.743] (II) DAEMON: Adding new display... > [06:26:03.744] (II) DAEMON: Loaded empty theme configuration > [06:26:03.744] (II) DAEMON: Xauthority path: "/run/sddm/xauth_UanezA" > [06:26:03.744] (II) DAEMON: Using VT 2 > [06:26:03.744] (II) DAEMON: Display server starting... > [06:26:03.744] (II) DAEMON: Writing cookie to "/run/sddm/xauth_UanezA" > [06:26:03.744] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_UanezA -noreset -displayfd 16 > [06:26:04.993] (II) DAEMON: Setting default cursor > [06:26:05.010] (II) DAEMON: Running display setup script "/usr/share/sddm/scripts/Xsetup" > [06:26:05.012] (II) DAEMON: Display server started. > [06:26:05.012] (II) DAEMON: Socket server starting... > [06:26:05.012] (II) DAEMON: Socket server started. > [06:26:05.012] (II) DAEMON: Loaded empty theme configuration > [06:26:05.012] (II) DAEMON: Greeter starting... > [06:26:05.022] (II) HELPER: [PAM] Starting... > [06:26:05.022] (II) HELPER: [PAM] Authenticating... > [06:26:05.022] (II) HELPER: [PAM] returning. > [06:26:05.142] (II) HELPER: Writing cookie to "/tmp/xauth_hBdSRs" > [06:26:05.142] (II) HELPER: Starting X11 session: "" "/usr/bin/sddm-greeter --socket /tmp/sddm-:0-emmSdV" > [06:26:05.152] (II) DAEMON: Greeter session started successfully > [06:26:05.208] (II) DAEMON: Message received from greeter: Connect Regards, Markus On Thu, Apr 4, 2024, at 01:02, Michael wrote: > On Wednesday, 3 April 2024 19:29:11 BST Markus Gustafsson wrote: >> Hi, >> >> I'm having a problem I'm not quite sure how to tackle: every other startup >> or so results in a black screen. Usually nothing gets printed (no bios >> splash, not GRUB menu, no OpenRC prints), and the monitor goes to low power >> mode after a while (I haven't quite confirmed if this is actually the case, >> or if everything happens before my monitor have actually stated, but I'd >> expect the GRUB menu would hang long enough for it to do so). > > You can increase the GRUB timeout to a longer interval, but if this an > intermittent phenomenon it is probably related to hardware. Check your cable > and replace it if possible, or use an alternative port (DP/HDMI/DVI). > > >> However, it does wake up if I switch to another TTY (e.g. ctrl+alt+F4) and >> lets me log on, so it has obviously booted up. If I switch back to TTY 8 >> from there it just shows a blinking cursor (i.e. not SDDM, which is what >> I'd expect). If I reboot from the TTY that lets me log on, the boot process >> is usually normal and leaves me at the SDDM login. > > As others have mentioned sddm now starts in the first available tty, normaly > on VT2. However, some users/PCs appear to have problems with more recent sddm > versions, whereby the sddm-greeter fails to start, or fails to login into a > desktop: > > https://bugs.gentoo.org/913862 > >> Any tips on how to debug this would be much appreciated. > > Check the output on /var/log/ssdm when this problem manifests. > > Attachments: > * signature.asc