Re: Succeeded to boot on Lenovo Yoga C630
- Reply: Hiroo Ono (小野寛生) : "Still did not succeed to boot on Lenovo Yoga C630"
- In reply to: Warner Losh : "Re: Succeeded to boot on Lenovo Yoga C630"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 09 Dec 2022 00:25:10 UTC
2022年12月9日(金) 3:19 Warner Losh <imp@bsdimp.com>: > > > > On Wed, Dec 7, 2022 at 4:21 PM Hiroo Ono (小野寛生) <hiroo.ono+freebsd@gmail.com> wrote: >> >> 2022年12月7日(水) 1:18 Warner Losh <imp@bsdimp.com>: >> > >> > >> > >> > On Tue, Dec 6, 2022 at 7:59 AM Hiroo Ono (小野寛生) <hiroo.ono+freebsd@gmail.com> wrote: >> >> >> 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). >> >> In the loader, when comconsole->c_init() is called for the second >> time, the function does not return. (I commented out comconsole to >> make the loader work, but it is rather brutal and is not a proper >> solution). >> But the function parse_uefi_con_out() in stand/efi/loader/main.c >> always returns RB_SERIAL, so the loader tries to use the serial >> console. > > > I wonder why that is. Is this -current or -stable? I have a rather large backlog of MFC-able loader changes. If it is with stable, then it makes sense: I fixed a bug where parse_uefi_con_out would return serial if '8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut' was unset. Is it set? Now we return Video console if we fine evidence there's a video console. It is stable/13. I tried 14-current, and the same change to loader was needed (merging OpenBSD's start.S and ldscript.arm64, and commenting out comconsole). Even with these change, the console defaults to serial, so I changed parse_uefi_con_out() to always return 0. Still, it stops at the same point. The kernel does not seem to boot. Running efi-show from the loader prompt did not show '8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut' The variable name containing 'ConOut' were: global NV,BS,RS ConOut = VenHw(9042A9DE-23DC-4A38-96FB-7ADED080516A),/VenHw(857A8741-0EEC-43BD-0482-27D14ED47D72)/Uart(115200,8,N,1) global NV,BS,RS ConOutDev = VenHw(9042A9DE-23DC-4A38-96FB-7ADED080516A),/VenHw(857A8741-0EEC-43BD-0482-27D14ED47D72)/Uart(115200,8,N,1) > Now, why it fails the second time, I don't know. > >> >> If a similar thing happens with the kernel, it may be stopping at >> serial console initialization. > > > The kernel doesn't use the EFI routines to initialize the serial console. But if the kernel is being told the wrong console, then it could also be booting just fine or almost fine and hitting some bug later. > >> >> > 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. >> >> I managed to load the dtb file and the boot process stopped at the >> same point. The problem is not here? > > > Yea, I don't think so. > > Warner > >> >> > 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 >> >> > >> >>