Re: Succeeded to boot on Lenovo Yoga C630

On Tue, Dec 6, 2022 at 7:59 AM Hiroo Ono (小野寛生) <hiroo.ono+freebsd@gmail.com>
wrote:

> Thank you.
>
> 2022年12月6日(火) 3:49 Mark Millard <marklmi@yahoo.com>:
>
> > The following might be involved in your context.
> >
> > The following is from a successful boot of a HoneyComb via
> > UEFI/ACPI (not device tree) via an old log file that I
> > have around. Note the first two lines.
> >
> > . . .
> > No valid device tree blob found!
> > WARNING! Trying to fire up the kernel, but no device tree blob found!
> > EFI framebuffer information:
> > addr, size     0x0, 0x0
> > dimensions     0 x 0
> > stride         0
> > masks          0x00000000, 0x00000000, 0x00000000, 0x00000000
> > ---<<BOOT>>---
> > GDB: no debug ports present
> > KDB: debugger backends: ddb
>
> OK, I (and the subject) was wrong. The loader boots, and show
> following log at last:
>
> Loading kernel...
> /boot/kernel/kernel text=0x2a8 text=0x8bcbf0 text=0x1f97ac
> data=0x1a6ac0 data=0x0+0x381000 syms=[0x8+0x11f6a0+0x8+0x1439ea]
> Loading configured modules...
> can't find '/boot/entropy'
> can't find '/etc/hostid'
> No valid device tree blob found!
> WARNING! Trying to fire up the kernel, but no device tree blob found!
> EFI framebuffer information
> addr, size        0x80400000, 0x7e9000
> dimensions     1920 x 1080
> stride             1920
> masks            0x00ff0000, 0x0000ff00, 0x000000ff, 0xff000000
>
> and it stops here. No "<<BOOT>>" line is displayed.
> So, it seems that the kernel is loaded but could not be started.


There are several causes of this.

Most likely is that the console is setup to go somewhere else. Though if
you are on the video display and getting that framebuffer output, it won't
not go there w/o some setting to override (say to force serial).

Next most likely is that FreeBSD doesn't cope well with having both FDT and
ACPI information available. But since not DTB is being passed in (per that
message) that's not likely at play here.

Finally, the loader passes a large number of tables, etc to the kernel.
It's quite possible that, for reasons still unknown, that data is wrong or
if standard conforming not expected by the kernel. this leads to a crash
before we've setup the console in the kernel which looks a lot like a hang.

Warner



> > . . .
> >
> > Such also happens for stable/13, releng/13.* based installations
> > as well --and likely others too.
> >
> > ACPI booting does not use Device Tree information but the messages
> > are output anyway about the lack. Only if you know that the context
> > is a Device Tree style of boot are the messages actually reporting
> > a problem.
> >
> >
> > ===
> > Mark Millard
> > marklmi at yahoo.com
> >
>
>