[Bug 249045] Loader still gets confused with a CD-ROM and prevents booing from fixed disk.
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Mon Sep 14 06:23:17 UTC 2020
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249045
--- Comment #12 from rallenh at hotmail.com ---
I wasn't updating the EFI partition after rebuilding and installing. I updated
my EFI boot with:
sudo gpart bootcode -p /boot/boot1.efifat -i 1 mfid0
It looks like EFI_DEBUG is being turned on? Here's an output from 12-STABLE
build and updated boot block:
>> FreeBSD EFI boot block
Loader path: /boot/loader.efi
Initializing modules: ZFS UFS
Load Path: \EFI\BOOT\BOOTX64.EFI
Load Device:
Acpi(PNP0A08,0x0)/Pci(0xA,0x0)/Pci(0x0,0x0)/Ctrl(0x0)/Scsi(0x0,0x0)/HD(1,GPT,24DF125F-F561-11EA-8E3D-002219BF8EC3,0x28,0x64000)
BootCurrent: 0000
BootOrder: 0000[*] 0003
Probing 8 block devices...not supported
not supported
better
not supported
not supported
not supported
not supported
not supported
done
ZFS found no pools
UFS found 1 partition
command args: -Dh
Consoles: EFI console
Reading loader env vars from /efi/freebsd/loader.env
Setting currdev to disk0p2:
FreeBSD/amd64 EFI loader, Revision 1.1
Command line arguments: loader.efi -Dh
EFI version: 2.10
EFI Firmware: Dell Inc. (rev 6.1537)
Console: efi (0x20001000)
Load Path:
HD(2,GPT,39C9EC31-F561-11EA-8E3D-002219BF8EC3,0x64028,0x827800000)
Load Device:
Acpi(PNP0A08,0x0)/Pci(0xA,0x0)/Pci(0x0,0x0)/Ctrl(0x0)/Scsi(0x0,0x0)/HD(2,GPT,39C9EC31-F561-11EA-8E3D-002219BF8EC3,0x64028,0x827800000)
BootCurrent: 0000
BootOrder: 0000[*] 0003
BootInfo Path:
Acpi(PNP0A08,0x0)/Pci(0xA,0x0)/Pci(0x0,0x0)/Ctrl(0x0)/Scsi(0x0,0x0)/HD(1,GPT,24DF125F-F561-11EA-8E3D-002219BF8EC3,0x28,0x64000)
Ignoring Boot0000: Only one DP found
Trying ESP:
Acpi(PNP0A08,0x0)/Pci(0xA,0x0)/Pci(0x0,0x0)/Ctrl(0x0)/Scsi(0x0,0x0)/HD(2,GPT,39C9EC31-F561-11EA-8E3D-002219BF8EC3,0x64028,0x827800000)
Setting currdev to disk0p2:
Loading /boot/defaults/loader.conf
Loading /boot/defaults/loader.conf
Loading /boot/device.hints
Loading /boot/loader.conf
Loading /boot/loader.conf.local
Loading kernel...
I am now able to boot on 12-STABLE with these two settings my
/boot/loader.conf:
beastie_disable="YES"
vfs.root.mountfrom="ufs:/dev/mfid0p2"
I can tell that something still isn't right even though I can boot to
multi-user with those settings. I get this after loader.efi (I think) hand-off:
/boot/kernel/kernel text=0x16bc864 data=0x140 data=0x75fe80
syms=[0x8+0x17e098+0x8+0x19bdd7]
Loading configured modules...
/etc/hostid size=0x25
can't find '/boot/entropy'
Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel]...
Start @ 0xffffffff80373000 ...
EFI framebuffer information:
addr, size 0xd7800000, 0x800000
dimensions 640 x 480
stride 640
masks 0x00ff0000, 0x0000ff00, 0x000000ff, 0xff000000
There is a '/boot/entropy' in my /boot:
117 1566758595 -rw------- 1 root wheel 3128999143 4096 "Sep 12 21:48:11 2020"
"Sep 14 01:57:16 2020" "Sep 14 01:57:16 2020" "Sep 12 21:48:11 2020" 32768 8
0x1 /boot/entropy
Sometimes I will get a similar error for /etc/hostid. That file exists as well:
117 1221175408 -rw-r--r-- 1 root wheel 2438831983 37 "Sep 14 01:57:14 2020"
"Sep 12 21:51:56 2020" "Sep 12 21:51:56 2020" "Sep 12 21:51:56 2020" 32768 8 0
/etc/hostid
I have removed the EFI boot menu I manually added. I also can't boot into the
Beastie Menu but at least I can boot without alot of ceremony.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-bugs
mailing list