From nobody Tue Dec 06 14:59:30 2022 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 4NRNqh0S3Pz4jsN4 for ; Tue, 6 Dec 2022 14:59:44 +0000 (UTC) (envelope-from hiroo.ono@gmail.com) Received: from mail-pl1-x62d.google.com (mail-pl1-x62d.google.com [IPv6:2607:f8b0:4864:20::62d]) (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 "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4NRNqg45qzz3sMQ for ; Tue, 6 Dec 2022 14:59:43 +0000 (UTC) (envelope-from hiroo.ono@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pl1-x62d.google.com with SMTP id y17so14172250plp.3 for ; Tue, 06 Dec 2022 06:59:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :reply-to:in-reply-to:references:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=cEgvRyONh53zQkqp7T6dBEs+vAXtrdxckdERlUNMYxU=; b=SvZss7mIeWNao7yleXUhi0uf7Jji1OzMiClFlllPQcpKNu6dRPVN+lyc8N8qmrJSsb zJpIUJYtqZTuzh19zwAGkuzBWIaks5DQiyUPrBNJDjpYwo5wfWVzV2IGZGzz9mgo81l9 H43WVGzLTx6aa7GOrRteIlYlb2uobrKtOYMdcZQDKnkt60SXs7HQQ+2Q9oEk4RRUCR2a CZpl28cnObhxp2nvgQ+TW3pkmktjoqOI9RhPQgxe/CLh6NYhmeAA2D0FbbSGnLl3fQLj ErI9WxApNxngWemMXRhscuEmD4gR2U+pcDUXffnfPuARgClBTR3W6V8HSz6IYMA074ss 3N1w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :reply-to:in-reply-to:references:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=cEgvRyONh53zQkqp7T6dBEs+vAXtrdxckdERlUNMYxU=; b=scaoqNC5b+2Qyi6wE86Lj4KpFsSTcB1il54n9LvsObzJNEzVjyBa86SNSW9ux7aV6h u3bPFklDTzTGATeNqrns9hgR9r8gJGGKpPnAi+kO6y+enCvs0c+LjSkT+Xb8NqeNf8Fx ADsOgGxVXINDocr14f2dnwbOJI2+FrogjZen0QMwSYlbjfaMF5mu6iSWGyR7gWZUbiLB WUILXlHl2Z8dBwcZn0WUKG2PdOzXbYt5sR5tK29sEQk+2Sx369eu9Uc2Zx42TE11qoO1 gq2/+YdDv9RtkSAJHdp73FUudCfQKwb6Ed7sSw1Lo3PXxHshHbf6R+46YrlenvUkOAqH 0Aqw== X-Gm-Message-State: ANoB5pmipxzu1hJUNNcE0JKVlWYeAM7XAxjePKlFz7RWNHGV4d0HXt7N dsEaniDz7s63f2FdV2m9ReKFGM/sND50BMws7ykGAiOy X-Google-Smtp-Source: AA0mqf7bLaFvL8a1bW/g3rng4IY79xCv5hArogGCrcppkMVVek8OztiI58kejH/3/r+3Lc6PQmnK15g/hwz/VqRoLNo= X-Received: by 2002:a17:902:7049:b0:189:e07f:933d with SMTP id h9-20020a170902704900b00189e07f933dmr7208093plt.7.1670338782299; Tue, 06 Dec 2022 06:59:42 -0800 (PST) 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: In-Reply-To: Reply-To: hiroo.ono+freebsd@gmail.com From: =?UTF-8?B?SGlyb28gT25vICjlsI/ph47lr5vnlJ8p?= Date: Tue, 6 Dec 2022 23:59:30 +0900 Message-ID: Subject: Re: Succeeded to boot on Lenovo Yoga C630 To: Mark Millard Cc: freebsd-arm@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4NRNqg45qzz3sMQ X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; TAGGED_FROM(0.00)[freebsd] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N Thank you. 2022=E5=B9=B412=E6=9C=886=E6=97=A5(=E7=81=AB) 3:49 Mark Millard : > 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 > ---<>--- > 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 "<>" 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 >