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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 0BC321382C5 for ; Fri, 14 May 2021 01:12:38 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B55F8E0839; Fri, 14 May 2021 01:12:33 +0000 (UTC) Received: from mail-pf1-f178.google.com (mail-pf1-f178.google.com [209.85.210.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 60AC9E07D7 for ; Fri, 14 May 2021 01:12:33 +0000 (UTC) Received: by mail-pf1-f178.google.com with SMTP id y70so296555pfg.2 for ; Thu, 13 May 2021 18:12:33 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:reply-to:message-id :date:user-agent:mime-version:in-reply-to:content-language; bh=C9MgYGGHIR+x7xZakP2036jJGgtcj3LfvbH9oRdkLfI=; b=mSYTXf2ajEP921YHd3M/8oeiIVc++OpiLeDkskwXVDv4v2L9zAasLs25vWg68zsbCv 7JRCX5qMj6sS+0t5IzeZaU/j+IdvFlfIggiJz0ybVlUJbWtTdJMkJuHRuBdIw1Szhp78 9py06CaeG8lkt2JF7khFm9FiVbWTDp88s8iVZxqgzGQt/0F+Kd0uf5pFmCT7DPNnw+k3 VtDaavjgvZfV5aiI4++8eaZEJeIo9oPzeH082DrtLkUW50XtvxxV+Wqzunfx+BbP+Pz9 GLxa97LOd3fDB41zk2J/k0nRlcdZ+XKjxpWzEYrn29MmH6G4E5GCi1bkZ7byRyL6BncB w5oA== X-Gm-Message-State: AOAM5339YnlY3HTlgCgig9K0yB2/wU0xJq7YvddcQFmgTrg92KWNADLo RWejvrEsMEGV0cAOzTsppE3pOVET8G32yA== X-Google-Smtp-Source: ABdhPJzjNE8KRSBWInQ/mvonGrsHHxeRrGwn7ztcMYyMfOlQm6v/s02xxBrubB5g5FKjNd4nGs9bCw== X-Received: by 2002:aa7:81c8:0:b029:2c4:b8d6:fd2 with SMTP id c8-20020aa781c80000b02902c4b8d60fd2mr20072463pfn.13.1620954752086; Thu, 13 May 2021 18:12:32 -0700 (PDT) Received: from [10.231.8.222] ([24.121.29.90]) by smtp.gmail.com with ESMTPSA id y14sm8058960pjr.51.2021.05.13.18.12.30 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 13 May 2021 18:12:31 -0700 (PDT) Subject: =?UTF-8?Q?Re=3a_=5bgentoo-user=5d_Re=3a_=5bgentoo-user=5d_boot_hang?= =?UTF-8?B?cyBmb3JldmVyIGF0IOKAnExvYWRpbmcgaW5pdGlhbCByYW1kaXNrLi4u4oCd?= To: gentoo-user@lists.gentoo.org References: From: Jack Message-ID: <1b7b0ba0-47fe-59e3-dd1f-50e5ab93125a@users.sourceforge.net> Date: Thu, 13 May 2021 19:12:14 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1 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 In-Reply-To: Content-Type: multipart/alternative; boundary="------------AA49DEAD4B8D51345A6B9438" Content-Language: en-US-large X-Archives-Salt: dd934461-6787-4753-9388-c5e967bf6c7f X-Archives-Hash: 25926841522a732afbf1e2d1618cfc1d This is a multi-part message in MIME format. --------------AA49DEAD4B8D51345A6B9438 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit On 5/13/21 6:51 PM, John Blinka wrote: > On Thu, May 13, 2021 at 7:23 PM Jack > wrote: > > > I'd start by removing any "quiet" or "splash" from the kernel command > line.    You should be able to see them when you hit "e". I'm not > sure > if it will actually help, but it should be a start. > > > Thanks, but neither one appears.  My command line is > > linux  /vmlinuz… root=UUID=… ro loglevel=4 nomodeset > > Here I’ve replaced the full name of the kernel and the uuid of the > boot partition with ellipses because it’s too tedious to type.  I’ve > scrutinized the actual ones for typos and am convinced there are > none.  Leaving out the loglevel command doesn’t change the behavior at > all. Given  you say the UUID is for the boot partition, then both the linux and initrd should just have the name of the kernel and initrd files (without leading "/boot",) which sounds like what you've got.  I'd next wonder if something is missing from the kernel/initrd combination, such as a kernel module necessary for some early part of the boot process or a file system (per Dale's suggestion.)  Assuming that you ran genkernel after booting a live image and chrooting into the new system, then we know the hardware can boot a good kernel/image combo.  Mainly I'm  just thinking out loud here, trying to coax someone's little gray cells into action. --------------AA49DEAD4B8D51345A6B9438 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit
On 5/13/21 6:51 PM, John Blinka wrote:
On Thu, May 13, 2021 at 7:23 PM Jack <ostroffjh@users.sourceforge.net> wrote:

I'd start by removing any "quiet" or "splash" from the kernel command
line.    You should be able to see them when you hit "e". I'm not sure
if it will actually help, but it should be a start.

Thanks, but neither one appears.  My command line is

linux  /vmlinuz… root=UUID=… ro loglevel=4 nomodeset

Here I’ve replaced the full name of the kernel and the uuid of the boot partition with ellipses because it’s too tedious to type.  I’ve scrutinized the actual ones for typos and am convinced there are none.  Leaving out the loglevel command doesn’t change the behavior at all.

Given  you say the UUID is for the boot partition, then both the linux and initrd should just have the name of the kernel and initrd files (without leading "/boot",) which sounds like what  you've got.  I'd next wonder if something is missing from the kernel/initrd combination, such as a kernel module necessary for some early part of the boot process or a file system (per Dale's suggestion.)  Assuming that you ran genkernel after booting a live image and chrooting into the new system, then we know the hardware can boot a good kernel/image combo.  Mainly I'm  just thinking out loud here, trying to coax someone's little gray cells into action.


--------------AA49DEAD4B8D51345A6B9438--