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 95120158041 for ; Wed, 3 Apr 2024 18:53:35 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 84A872BC03D; Wed, 3 Apr 2024 18:53:30 +0000 (UTC) Received: from mail-qv1-f45.google.com (mail-qv1-f45.google.com [209.85.219.45]) (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 17FBF2BC02B for ; Wed, 3 Apr 2024 18:53:29 +0000 (UTC) Received: by mail-qv1-f45.google.com with SMTP id 6a1803df08f44-69923bd731fso103356d6.1 for ; Wed, 03 Apr 2024 11:53:29 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712170409; x=1712775209; h=in-reply-to:reply-to:from:content-language:references:to:subject :user-agent:mime-version:date:message-id:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=acAb/Av3GOkuHDTvlqiBmVTWJ71kJs+5z7z3WIlwmpc=; b=ekJpdl/eVsBsWlBY7NS40QZODiIMTRT1vDXHYzTBKT2zpDq5rVXtO8DTz5+rMBMBKS QYDwzeOXW6/iiuruspXk6k4uLReVX9JvNgpx1iZdoGHC64uDfXewK4STewXquzDH0r/M 1V0Upbi9GjiolglYErazJou9dxzWhT+YzeDvGjNmcMh3NCDOh/OsihcnsrrC35EkLI4c jDs94ks41fEX6AoIs0CjUaID9QIGiq2GN8CLITgdn51hc/1Mk5lKeGajelfh/Tqjirqm SLxIQTrbOXgDpfNxoGnh9Rip6+IV3kh13ZFYJzN9DaKg8iWEeW9cNJbFpZjG3oZKLoyX zv3A== X-Gm-Message-State: AOJu0Yz7U8YALTkIY1HBAKR3hXwizhrNH0Zli2r8XM/is79ruuy9/5j3 grfUyy4K/wc5n3ysCgVpWXjE/yMCUMVYelmB95egq9vo7tEYdwGSEa+ovTGTdiINwdMX6ZvvVNS Q X-Google-Smtp-Source: AGHT+IHm0hG8ZQPMGUjq71buAHUfHujTfg1FDUEZZ4e+p45A6Zs+dNCwhtRQQaVLSZLA5Fma+atFwg== X-Received: by 2002:a05:622a:15d6:b0:432:f422:4d4c with SMTP id d22-20020a05622a15d600b00432f4224d4cmr188018qty.5.1712170409095; Wed, 03 Apr 2024 11:53:29 -0700 (PDT) Received: from [192.168.1.207] (32-216-196-135.bng01.wlmn.ct.frontiernet.net. [32.216.196.135]) by smtp.gmail.com with ESMTPSA id hh1-20020a05622a618100b00430b0f40532sm6765989qtb.9.2024.04.03.11.53.27 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 03 Apr 2024 11:53:28 -0700 (PDT) Content-Type: multipart/alternative; boundary="------------eiuPBntowypD6IR6t7BBiov0" Message-ID: <680bb2fd-a79b-446c-8191-fa9ff9dd5edc@users.sourceforge.net> Date: Wed, 3 Apr 2024 14:53:07 -0400 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 User-Agent: Mozilla Thunderbird Subject: Re: [gentoo-user] Every other startup results in a black screen (possibly SDDM related?) To: gentoo-user@lists.gentoo.org References: Content-Language: en-US-large From: Jack In-Reply-To: X-Archives-Salt: da263259-d8d5-4144-8fa2-ef0b67e818fd X-Archives-Hash: c836c3b858a38436615b84371ee4398c This is a multi-part message in MIME format. --------------eiuPBntowypD6IR6t7BBiov0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 4/3/24 2:29 PM, 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). > > 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. > > Any tips on how to debug this would be much appreciated. Are you certain it hasn't started on some TTY other than 8?  I always start out on TTY1, although I start up text only, no SDDM. However, I do have a very vague memory of something similar, and I believe it was that I needed to change one of the kernel FB related settings.  Sorry not be have more concrete suggestions. --------------eiuPBntowypD6IR6t7BBiov0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
On 4/3/24 2:29 PM, 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).

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.

Any tips on how to debug this would be much appreciated.
Are you certain it hasn't started on some TTY other than 8?  I always start out on TTY1, although I start up text only, no SDDM.  However, I do have a very vague memory of something similar, and I believe it was that I needed to change one of the kernel FB related settings.  Sorry not be have more concrete suggestions.
--------------eiuPBntowypD6IR6t7BBiov0--