Date: Tue, 6 Dec 2022 23:59:30 +0900 From: =?UTF-8?B?SGlyb28gT25vICjlsI/ph47lr5vnlJ8p?= <hiroo.ono+freebsd@gmail.com> To: Mark Millard <marklmi@yahoo.com> Cc: freebsd-arm@freebsd.org Subject: Re: Succeeded to boot on Lenovo Yoga C630 Message-ID: <CANtk6Shwaea09TiTZq3UZwzCoXjm8TqkA930QQwS_i3_Awd5bg@mail.gmail.com> In-Reply-To: <B55013C7-B04C-48E4-BC0F-C106DA08348F@yahoo.com> References: <CANtk6SgUoqC_Jgdtu=CZnFvnLzqP445MQqfwhV5%2BBgX_%2BVFUZA@mail.gmail.com> <B55013C7-B04C-48E4-BC0F-C106DA08348F@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thank you. 2022=E5=B9=B412=E6=9C=886=E6=97=A5(=E7=81=AB) 3:49 Mark Millard <marklmi@ya= hoo.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=3D0x2a8 text=3D0x8bcbf0 text=3D0x1f97ac data=3D0x1a6ac0 data=3D0x0+0x381000 syms=3D[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. > . . . > > 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. > > > =3D=3D=3D > Mark Millard > marklmi at yahoo.com >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANtk6Shwaea09TiTZq3UZwzCoXjm8TqkA930QQwS_i3_Awd5bg>