Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Fri, 12 May 2023 13:47:45 +0200
From:   Corentin Labbe <clabbe.montjoie@gmail.com>
To:     Dave Hansen <dave.hansen@intel.com>
Cc:     tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
        dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
        pjones@redhat.com, deller@gmx.de, linux-fbdev@vger.kernel.org,
        linux-kernel@vger.kernel.org
Subject: Re: Cannot boot an i386-UEFI thinkpad lenovo tablet-2
Message-ID: <ZF4nYQT31qDH_9qb@Red>
References: <ZFnoXiZGGhuWDl2S@Red>
 <af88a590-e20a-0669-c0d8-e073cc6e109f@intel.com>
 <ZFqvCeNxKJDOYDaT@Red>
 <055b41e9-b345-03fe-755c-cdcb08e4098b@intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <055b41e9-b345-03fe-755c-cdcb08e4098b@intel.com>
Precedence: bulk

Le Tue, May 09, 2023 at 01:48:26PM -0700, Dave Hansen a ?crit :
> On 5/9/23 13:37, Corentin Labbe wrote:
> > Le Tue, May 09, 2023 at 07:01:02AM -0700, Dave Hansen a ?crit :
> >> On 5/8/23 23:29, Corentin Labbe wrote:
> >>> The tablet has only one port, so I use a hub for keyboard and USB key.
> >>> Immediatly after booting Linux, all hub port light goes to off.
> >> If it's dying in the installer, can you boot it to a shell or rescue
> >> media?  Are you getting any kernel messages on the screen before the
> >> installer?
> >>
> > Sorry my sentence was not precise ("after booting linux"),
> > 
> > It die after pressing enter on grub menu.
> > No kernel message, nothing new on screen.
> > Only visible change are USB light off.
> > 
> > I have really no clue.
> 
> A lot of distros set the 'quiet' option to _keep_ the kernel from
> spewing messages at boot.  Ubuntu sets "quiet splash", for instance.
> 
> Going into the grub menu and killing the 'quiet' and replacing it with
> 'debug' is a good place to start.  earlyprintk=vga can also help if
> things are still blank at that point.  I thought we used to have an
> earlyprintk=efi, but it seems to have vanished at some point.
> 
> But, you've got a bit of oddball hardware.  It's from the _far_ extreme
> end of 32-bit-only hardware.  The fact that it had Windows on it isn't a
> great sign.  There could be a BIOS bug that trips Linux up but Windows
> is perfectly happy with.  There was definitely a sad period of time
> where folks were not interested in fixing issues like that.

Thanks for your hints.
I have already disabled quiet and unfortunatly, none of earlyprintk= changed anything.