From nobody Fri Jun 21 05:55:30 2024 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4W56682kJVz5PXh3 for ; Fri, 21 Jun 2024 05:55:44 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pf1-x435.google.com (mail-pf1-x435.google.com [IPv6:2607:f8b0:4864:20::435]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4W56681Fd3z3wk7 for ; Fri, 21 Jun 2024 05:55:44 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pf1-x435.google.com with SMTP id d2e1a72fcca58-701b0b0be38so1491252b3a.0 for ; Thu, 20 Jun 2024 22:55:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1718949342; x=1719554142; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=9Q3Q2K9kOz+iSoB0Rt3pjUwmCeIBJsNBaDOXDscY9Wo=; b=cx+53DvyAwOrNLztYOMJaa7J025tCvXfEOBGDdGlIbMHvWP/qq4PLBeypRw+AbOBii 5GQkGT+cVhWT9Q9v9Y8VyGV4qajpPPXYsonAuiM+R3Z37dhwrjlkxdOjo9jV2WXdyWlZ PLHCR7rPkRRhEMKYeiJ1lfkkUKgCMoRo6mHWAd0Qf1aCaN19T9jWwUVJwe3r9qxkXuww +kGo+OVne8F37tFyNoX+SOBu5rwZJ4WOFYMPjWFAXSfWjYbM+dYuldxnB/Au8r2z7lLg xnz4r7lEkNGJi0yelUXpc1EiyC6qT7uO1FjZlYHXpFcP8RGI8sq8+mYic30aBtYYNiiQ Xj3g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718949342; x=1719554142; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=9Q3Q2K9kOz+iSoB0Rt3pjUwmCeIBJsNBaDOXDscY9Wo=; b=bqEaJzb7AJeBB6hS+R2NqcFLCc4G9GcDC9xMVKdEj84gbu/AWFY7LMLr3kSocwSBsG m9qWotbSosOICvvAvyb/Y5inWfZfUzeT2zZVB+IutjhwYgIHDnqFfvUHSlW9mTENmhX1 245YSVLk8z0pJcahBr1TnnE9IhyGOBuws0dEvvOc1+XD5emguT75HPPmLwAOeIdqMLzd 9RyrOHkOgR3Vb4NGfp/DuSrMCRM4vhzOQk2IcDVHISc7lozgIrTiH5uxEyYo1P6JAWlP nh1DAbdtx+1utLEAddrVlVxxQmkV7WJ8MP0OUtF5/VVweVVbBqWJiixSTOFm/v9PPS8f IsqQ== X-Forwarded-Encrypted: i=1; AJvYcCWYz5jCKAFWyzuJCTlU1CIDK+UFZtKGQXi1kXFfJDYXqxNSa8EQwA7G0Ak5ZjBUahclZKYmnZDnvarEh5o/wZRo+R1xvSh7Zw== X-Gm-Message-State: AOJu0Yzwyn1wP94LKHtzueTrJUkWhqyCtiKsZ6xod3jhPsranTzul5DH roqbes1quNLk1enoKNDbj8SyZjSG+qGDCXXnjs7FBacRbFCGTYHNK3b3P0CKNeyNHVyw6f0n73d mZkcTKkomTdw7gYpU76FWvxCB9c7IRCW82dUaGw== X-Google-Smtp-Source: AGHT+IHgwXDngAiscHap6vTDTtpUOi8DqRhrjFk0Uc38FrKmNp6P9xUc2hdSV9Foz6eTaaxmlJfeva6CqwOZhvZf7Sc= X-Received: by 2002:a05:6a21:3288:b0:1af:b0b6:a35f with SMTP id adf61e73a8af0-1bcbb39fd6amr9166676637.2.1718949342013; Thu, 20 Jun 2024 22:55:42 -0700 (PDT) List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@FreeBSD.org MIME-Version: 1.0 References: <9BE6FB50-27DC-453E-B915-131D45C901CD.ref@yahoo.com> <9BE6FB50-27DC-453E-B915-131D45C901CD@yahoo.com> In-Reply-To: From: Warner Losh Date: Thu, 20 Jun 2024 23:55:30 -0600 Message-ID: Subject: Re: FreeBSD OS installation stuck after selecting Boot installer To: "Anantharam, Arjun" Cc: Mark Millard , FreeBSD ARM List Content-Type: multipart/alternative; boundary="000000000000eb02ac061b601438" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4W56681Fd3z3wk7 --000000000000eb02ac061b601438 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Jun 20, 2024, 11:46=E2=80=AFPM Anantharam, Arjun wrote: > Thanks Mark for your response =F0=9F=99=82 > From the FreeBSD Boot loader, after adding the below configurations, i no > longer see error messages or warning message on device tree blob: > > *set comconsole_speed=3D115200* > *echo comconsole_speed is set to ${comconsole_speed}* > > *set acpi_load=3D"YES"* > *set fdt_enable=3D"NO"* > *echo acpi_load is set to ${acpi_load}* > *echo fdt_enable is set to ${fdt_enable}* > > *boot* > > But still run into FreeBSD installation getting stuck after > displaying some garbage message: > > =E2=96=92=CA=82C=D2=8AC=C3=878=E2=96=92=C3=83=E2=96=92=CB=A3=E2=96=92=E2= =96=92=E2=96=92=E2=96=92B=E2=96=92=E2=96=92=E2=96=92B=CB=96=E2=96=92=E2=96= =92=E2=96=92v=E2=96=92=E2=96=92=D3=975=E2=96=92=E2=96=92=E2=96=92lx]=E2=96= =92O=E2=96=92O=E2=96=92=E2=96=92=E2=96=92=E2=96=92XUVZ}=E2=96=92H=E2=96=92= =E2=96=92=E2=96=92=E2=96=92=CF=97=E2=96=92GZ > > =E2=96=92=E2=96=92=E2=96=92BR=EF=BF=BD=E2=96=92=CA=97=E2=96=92=E2=96=92= =E2=96=92=E2=96=92=EF=BF=BD=E2=96=92=C6=96H=E2=96=92=E2=96=92]=E2=96=92} > > I tried changing the console to vidconsole, but looks like that is > not supported: > Yes. That's just for bios. What does is hw.uart.console in the boot loader? In fact can you share all the loader's variables. Also, can you do show-efi so we can see what ConOut is set to? The above sure looks like a baud issue. There's automatic things tgat override stuff. This isn't the PC where comconsole settings do much. Comconsole is an alias for eficom, for example. Thanks Warner > *Output in boot loader, when set console=3D"vidconsole":* > *console vidconsole is unavailable * > *no valid consoles! * > *Available consoles: efi eficom comconsole* > > So, i am not sure what the issue is here to get the FreeBSD installed. An= y > pointers are much appreciated!! > Thanks, > Arjun > ------------------------------ > *From:* Mark Millard > *Sent:* Thursday, June 20, 2024 10:07 PM > *To:* Anantharam, Arjun ; FreeBSD ARM List < > freebsd-arm@freebsd.org> > *Subject:* Re: FreeBSD OS installation stuck after selecting Boot > installer > > Anantharam, Arjun wrote on > Date: Thu, 20 Jun 2024 17:07:29 UTC : > > > If the screenshots are not visible, i have included below errors seen i= n > screenshot: > > > > From 1st screenshot(below errors seen during FreeBSD installation after > selecting Boot installer): > > Loading kernel.. > > Loading configured modules.. > > cant find 'etc/hostid' > > cant find 'boot/entropy' > > FYI, the 2 lines: > > > No valid device tree blob found! > > Warning! Trying to fire up the kernel, but no device tree blob found! > > are normal messages for ACPI booting. They are not error messages and > do not indicate a stop of the ACPI-based boot sequence. > > I've never liked that working ACPI booting puts out those 2 messages. > > > "Garbage displayed" > > > > From 2nd Screenshot: > > ACPI option enabled by default in FreeBSD > > =3D=3D=3D > Mark Millard > marklmi at yahoo.com > > --000000000000eb02ac061b601438 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Thu, Jun 20, 2024, 11:46=E2=80=AFPM Anantharam, Arj= un <arjun.anantharam@intel= .com> wrote:
Thanks Mark for your response =F0=9F=99=82
From the FreeBSD Boot loader, after adding the below configurations, i no l= onger see error messages or warning message on device tree blob:

set comconsole_speed=3D115200
echo comconsole_speed is set to ${comconsole_speed}
=C2=A0
set acpi_load=3D"YES"
set fdt_enable=3D"NO"
echo acpi_load is set to ${acpi_load}
echo fdt_enable is set to ${fdt_enable}

boot

But still run into FreeBSD installation getting stuck after displaying=C2= =A0some garbage message:

=E2=96=92=CA=82C=D2=8AC=C3=878=E2=96=92=C3=83=E2=96=92=CB=A3=E2=96=92=E2=96= =92=E2=96=92=E2=96=92B=E2=96=92=E2=96=92=E2=96=92B=CB=96=E2=96=92=E2=96=92= =E2=96=92v=E2=96=92=E2=96=92=D3=975=E2=96=92=E2=96=92=E2=96=92lx]=E2=96=92O= =E2=96=92O=E2=96=92=E2=96=92=E2=96=92=E2=96=92XUVZ}=E2=96=92H=E2=96=92=E2= =96=92=E2=96=92=E2=96=92=CF=97=E2=96=92GZ
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =E2=96=92=E2=96=92= =E2=96=92BR=EF=BF=BD=E2=96=92=CA=97=E2=96=92=E2=96=92=E2=96=92=E2=96=92=EF= =BF=BD=E2=96=92=C6=96H=E2=96=92=E2=96=92]=E2=96=92}

I tried changing=C2=A0the console to vidconsole, but looks like that is not= =C2=A0supported:

=

Yes. That's just fo= r bios.

What does is hw.= uart.console in the boot loader? In fact can you share all the loader's= variables.

Also, can yo= u do show-efi so we can see what ConOut is set to?
<= br>
The above sure looks like a baud issue. There= 9;s automatic things tgat override stuff. This isn't the PC where comco= nsole settings do much. Comconsole is an alias for eficom, for example.

Thanks

Warner
Output in boot loader, when set=C2=A0console=3D"vidconsole":
console vidconsole is unavailable=C2=A0
no valid consoles!=C2=A0
Available consoles: =C2=A0=C2=A0=C2=A0 efi =C2=A0=C2=A0=C2=A0 eficom =C2= =A0=C2=A0=C2=A0 comconsole

So, i am not sure what the issue is here to get the FreeBSD installed. Any = pointers are much appreciated!!
Thanks,
Arjun
From:=C2=A0Mark Millard <marklmi@yahoo.com>
Sent:=C2=A0Thursday, June 20, 2024 10:07 PM
To:=C2=A0Anantharam, Arjun <arjun.anantharam@intel.com>; FreeBSD ARM List <freebsd-arm@freebsd.org>
Subject:=C2=A0Re: FreeBSD OS installation stuck after selecting Boot= installer
=C2=A0
Anantharam, Arjun <arjun.ananth= aram_at_intel.com> wrote on
Date: Thu, 20 Jun 2024 17:07:29 UTC :

> If the screenshots are not visible, i have included below errors seen = in screenshot:
>
> From 1st screenshot(below errors seen during FreeBSD installation afte= r selecting Boot installer):
> Loading kernel..
> Loading configured modules..
> cant find 'etc/hostid'
> cant find 'boot/entropy'

FYI, the 2 lines:

> No valid device tree blob found!
> Warning! Trying to fire up the kernel, but no device tree blob found!<= br>
are normal messages for ACPI booting. They are not error messages and
do not indicate a stop of the ACPI-based boot sequence.

I've never liked that working ACPI booting puts out those 2 messages.
> "Garbage displayed"
>
> From 2nd Screenshot:
> ACPI option enabled by default in FreeBSD

=3D=3D=3D
Mark Millard
marklmi at yahoo.com

--000000000000eb02ac061b601438--