Re: FreeBSD OS installation stuck after selecting Boot installer

Mark Millard <[email protected]>
Newsgroups gmane.os.freebsd.devel.arm
Message-ID <[email protected]>
On Jun 21, 2024, at 17:02, Anantharam, Arjun <[email protected]> wrote:

> P {margin-top:0;margin-bottom:0;} I did try to set these values in boot loader prompt:
> 
> set hw.uart.console="io:0x3F8,br:115200"
> set efi_max_resolution=1920x1080
> set hint.uart.0.disabled="1"
> set hint.uart.1.disabled="1"
> 
> However, i was unable to change "efi_com_port" to say 1(default is 0)
> 
> With this, i no longer see Garbage data being displayed. But the installation does not proceed either, it is sort of stuck:
> 
> <image.png>

Did you notice the "aa" vs. "a" in:

hint.uart0.disaabled
vs.
hint.uart1.disabled

? (No claim it is an essential issue for your overall problem.)

[This did not seem worth sending to Warner.]

> i.e after boot cmd, i see EFI Framebuffer information all set to 0x0(In case the above screenshot is not visible)
> 
> So, i am not sure what sort of UART related setting i need to change or set..
> 
> Thanks,
> Arjun
> 
>> From: [email protected] <[email protected]> on behalf of Anantharam, Arjun <[email protected]>
>> Sent: Friday, June 21, 2024 8:31 AM
>> To: Warner Losh <[email protected]>
>> Cc: Mark Millard <[email protected]>; FreeBSD ARM List <[email protected]>
>> Subject: Re: FreeBSD OS installation stuck after selecting Boot installer   Hi Warner,
>> 
>> Here are the details:
>> 
>> OK show hw.uart.console
>> variable 'hw.uart.console' not found
>> 
>> OK show
>> COLUMNS=80
>> LINES=50
>> acpi.oem=INTEL
>> acpi.revision=2
>> acpi.rsdp=0x00000044b6e30018
>> acpi.rsdt=0x0000000000000000
>> acpi.xsdt=0x00000044b6e3fe98
>> acpi.xsdt_length=36
>> acpi_dsdt_load=NO
>> acpi_dsdt_name=/boot/acpi_dsdt.aml
>> acpi_dsdt_type=acpi_dsdt
>> acpi_load=YES
>> acpi_video_load=NO
>> audit_event_load=NO
>> audit_event_name=/etc/security/audit_event
>> audit_event_type=etc_security_audit_event
>> autoboot_delay=NO
>> bitmap_load=NO
>> bitmap_name=splash.bmp
>> bitmap_type=splash_image_data
>> boot_serial=YES
>> bootenv_autolist=YES
>> bootfile=kernel
>> console=efi
>> cpu_microcode_load=NO
>> cpu_microcode_name=/boot/firmware/ucode.bin
>> cpu_microcode_type=cpu_microcode
>> currdev=disk0p2:
>> efi-version=2.70
>> efi_com_port=0
>> efi_com_speed=115200
>> efi_max_resolution=1x1
>> entropy_cache_load=YES
>> entropy_cache_name=/boot/entropy
>> entropy_cache_type=boot_entropy_cache
>> entropy_efi_seed=YES
>> fdt_enable=NO
>> hint.acpi.0.disabled=0
>> hint.smbios.0.mem=0x44bbfd0000
>> hostuuid_load=YES
>> hostuuid_name=/etc/hostid
>> hostuuid_type=hostuuid
>> interpret=OK
>> kernel=kernel
>> kernel_options=
>> kernels_autodetect=NO
>> loaddev=disk0p2:
>> loader.efi=1
>> loader_conf_dirs=/boot/loader.conf.d
>> loader_menu_multi_user_prompt=Installer
>> local_loader_conf_files=/boot/loader.conf.local
>> module_blacklist=drm drm2 radeonkms i915kms amdgpu
>> module_path=/boot/modules;/boot/dtb;/boot/dtb/overlays
>> module_verbose=2
>> nextboot_conf=/boot/nextboot.conf
>> prompt=${interpret}
>> ram_blacklist_load=NO
>> ram_blacklist_name=/boot/blacklist.txt
>> ram_blacklist_type=ram_blacklist
>> screensave_load=NO
>> screensave_name=green_saver
>> script.lang=lua
>> smbios.bios.reldate=Apr  4 2024
>> smbios.bios.revision=1.2
>> smbios.bios.vendor=Intel
>> smbios.bios.version=Intel(R) IPU Embedded UEFI FW 1.2.0 for AArch64
>> smbios.chassis.maker=Intel
>> smbios.chassis.serial=N/A
>> smbios.chassis.tag=N/A
>> smbios.chassis.type=Other
>> smbios.chassis.version=N/A
>> smbios.memory.enabled=3145728
>> smbios.socket.enabled=16
>> smbios.socket.populated=16
>> smbios.system.family=Intel(R) IPU E2100
>> smbios.system.maker=Intel
>> smbios.system.product=Intel(R) IPU Adapter E2100-CCQDA2
>> smbios.system.serial=000000
>> smbios.system.sku=000000000000
>> smbios.system.uuid=30313245-3030-3030-6e0c-56812e49f70f
>> smbios.system.version=N/A
>> smbios.version=3.3
>> splash_bmp_load=NO
>> splash_pcx_load=NO
>> splash_txt_load=NO
>> twiddle_divisor=16
>> verbose_loading=NO
>> vesa_load=NO
>> vfs.mountroot.timeout=10
>> OK
>> 
>> 
>> From efi-show, details relevant to ConOut:
>> 
>> global NV,BS,RS ConIn = VenHw(D3987D4B-971A-435F-8CAF-4967EB627241)/Uart(115200,
>> 8,N,1)/VenMsg(7D916D80-5BB1-458C-A48F-E25FDD51EF94)
>> global NV,BS,RS ConOut = VenHw(D3987D4B-971A-435F-8CAF-4967EB627241)/Uart(115200
>> ,8,N,1)/VenMsg(7D916D80-5BB1-458C-A48F-E25FDD51EF94)
>> global NV,BS,RS ErrOut = VenHw(D3987D4B-971A-435F-8CAF-4967EB627241)/Uart(115200
>> ,8,N,1)/VenMsg(7D916D80-5BB1-458C-A48F-E25FDD51EF94)
>> 
>> 
>> global BS,RS ConInDev = VenHw(D3987D4B-971A-435F-8CAF-4967EB627241)/Uart(115200,
>> 8,N,1)/VenPcAnsi(),/VenHw(D3987D4B-971A-435F-8CAF-4967EB627241)/Uart(115200,8,N,
>> 1)/VenVt100(),/VenHw(D3987D4B-971A-435F-8CAF-4967EB627241)/Uart(115200,8,N,1)/Ve
>> nVt100Plus(),/VenHw(D3987D4B-971A-435F-8CAF-4967EB627241)/Uart(115200,8,N,1)/Ven
>> Utf8(),/VenHw(D3987D4B-971A-435F-8CAF-4967EB627241)/Uart(115200,8,N,1)/VenMsg(7D
>> 916D80-5BB1-458C-A48F-E25FDD51EF94),/VenHw(D3987D4B-971A-435F-8CAF-4967EB627241)
>> /Uart(115200,8,N,1)/VenMsg(E4364A7F-F825-430E-9D3A-9C9BE6817CA5),/VenHw(D3987D4B
>> -971A-435F-8CAF-4967EB627241)/Uart(115200,8,N,1)/VenMsg(FBFCA56B-BB36-4B78-AAAB-
>> BE1B97EC7CCB),/VenHw(D3987D4B-971A-435F-8CAF-4967EB627241)/Uart(115200,8,N,1)/Ve
>> nMsg(8E46DDDD-3D49-4A9D-B875-3C086F6AA2BD),/VenHw(D3987D4B-971A-435F-8CAF-4967EB
>> 627241)/Uart(115200,8,N,1)/VenMsg(FC7DD6E0-813C-434D-B4DA-3BD649E9E15A)
>> global BS,RS ConOutDev = VenHw(D3987D4B-971A-435F-8CAF-4967EB627241)/Uart(115200
>> ,8,N,1)/VenPcAnsi(),/VenHw(D3987D4B-971A-435F-8CAF-4967EB627241)/Uart(115200,8,N
>> ,1)/VenVt100(),/VenHw(D3987D4B-971A-435F-8CAF-4967EB627241)/Uart(115200,8,N,1)/V
>> enVt100Plus(),/VenHw(D3987D4B-971A-435F-8CAF-4967EB627241)/Uart(115200,8,N,1)/Ve
>> nUtf8(),/VenHw(D3987D4B-971A-435F-8CAF-4967EB627241)/Uart(115200,8,N,1)/VenMsg(7
>> D916D80-5BB1-458C-A48F-E25FDD51EF94),/VenHw(D3987D4B-971A-435F-8CAF-4967EB627241
>> )/Uart(115200,8,N,1)/VenMsg(E4364A7F-F825-430E-9D3A-9C9BE6817CA5),/VenHw(D3987D4
>> B-971A-435F-8CAF-4967EB627241)/Uart(115200,8,N,1)/VenMsg(FBFCA56B-BB36-4B78-AAAB
>> -BE1B97EC7CCB),/VenHw(D3987D4B-971A-435F-8CAF-4967EB627241)/Uart(115200,8,N,1)/V
>> enMsg(8E46DDDD-3D49-4A9D-B875-3C086F6AA2BD),/VenHw(D3987D4B-971A-435F-8CAF-4967E
>> B627241)/Uart(115200,8,N,1)/VenMsg(FC7DD6E0-813C-434D-B4DA-3BD649E9E15A)
>> global BS,RS ErrOutDev = VenHw(D3987D4B-971A-435F-8CAF-4967EB627241)/Uart(115200
>> ,8,N,1)/VenPcAnsi(),/VenHw(D3987D4B-971A-435F-8CAF-4967EB627241)/Uart(115200,8,N
>> ,1)/VenVt100(),/VenHw(D3987D4B-971A-435F-8CAF-4967EB627241)/Uart(115200,8,N,1)/V
>> enVt100Plus(),/VenHw(D3987D4B-971A-435F-8CAF-4967EB627241)/Uart(115200,8,N,1)/Ve
>> nUtf8(),/VenHw(D3987D4B-971A-435F-8CAF-4967EB627241)/Uart(115200,8,N,1)/VenMsg(7
>> D916D80-5BB1-458C-A48F-E25FDD51EF94),/VenHw(D3987D4B-971A-435F-8CAF-4967EB627241
>> )/Uart(115200,8,N,1)/VenMsg(E4364A7F-F825-430E-9D3A-9C9BE6817CA5),/VenHw(D3987D4
>> B-971A-435F-8CAF-4967EB627241)/Uart(115200,8,N,1)/VenMsg(FBFCA56B-BB36-4B78-AAAB
>> -BE1B97EC7CCB),/VenHw(D3987D4B-971A-435F-8CAF-4967EB627241)/Uart(115200,8,N,1)/V
>> enMsg(8E46DDDD-3D49-4A9D-B875-3C086F6AA2BD),/VenHw(D3987D4B-971A-435F-8CAF-4967E
>> B627241)/Uart(115200,8,N,1)/VenMsg(FC7DD6E0-813C-434D-B4DA-3BD649E9E15A)
>> 
>> 
>> Please let me know if you need more details..
>> 
>> Thanks for your help!!
>> Arjun
>> From: Warner Losh <[email protected]>
>> Sent: Thursday, June 20, 2024 10:55 PM
>> To: Anantharam, Arjun <[email protected]>
>> Cc: Mark Millard <[email protected]>; FreeBSD ARM List <[email protected]>
>> Subject: Re: FreeBSD OS installation stuck after selecting Boot installer   
>> 
>> On Thu, Jun 20, 2024, 11:46 PM Anantharam, Arjun <[email protected]> wrote:
>> Thanks Mark for your response 🙂
>> 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=115200
>> echo comconsole_speed is set to ${comconsole_speed}
>>   set acpi_load="YES"
>> set fdt_enable="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:
>> 
>> ▒ʂCҊCÇ8▒Ã▒ˣ▒▒▒▒B▒▒▒B˖▒▒▒v▒▒ӗ5▒▒▒lx]▒O▒O▒▒▒▒XUVZ}▒H▒▒▒▒ϗ▒GZ
>>                                                             ▒▒▒BR�▒ʗ▒▒▒▒�▒ƖH▒▒]▒}
>> 
>> 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="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. Any pointers are much appreciated!!
>> Thanks,
>> Arjun
>> From: Mark Millard <[email protected]>
>> Sent: Thursday, June 20, 2024 10:07 PM
>> To: Anantharam, Arjun <[email protected]>; FreeBSD ARM List <[email protected]>
>> Subject: Re: FreeBSD OS installation stuck after selecting Boot installer   Anantharam, Arjun <arjun.anantharam_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 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
>> 
>> ===
>> Mark Millard
>> marklmi at yahoo.com
>> 
> 
===
Mark Millard
marklmi at yahoo.com
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.