Date: Mon, 16 Mar 2015 19:00:35 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 198642] EFI boot yields various error messages Message-ID: <bug-198642-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198642 Bug ID: 198642 Summary: EFI boot yields various error messages Product: Base System Version: 10.1-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: misc Assignee: freebsd-bugs@FreeBSD.org Reporter: cipher_nl@hotmail.com I'm trying to get EFI boot working by following the document: https://wiki.freebsd.org/UEFI It roughly says: gpart create -s gpt da0 gpart add -t efi -s 800K da0 gpart add -t freebsd-ufs da0 dd if=/boot/boot1.efifat of=/dev/da0p1 newfs /dev/da0p2 I created a USB Stick roughly using the guideline above, but use a MFSroot on the UFS partition instead, and have partitions aligned to 1024K-boundaries. Then, i used RaWrite to create the USB stick. When trying to boot my USB stick on two real hardware systems (J1900) however, it first yields an error message that it cannot load /boot/loader.conf, and when it tries to load /boot/kernel/kernel, i get random error messages from the the following list: --- inflate: invalid code lengths set invalid distance too far back invalid distance code inflate: invalid stored block lengths readin failed. elf64_loadimage: read failed inflate: invalid block type --- The strange thing is that trying to boot (OK loader prompt) will yield a different error. I would expect getting the same error from the same input. It appears the error is randomly chosen from the above list. Maybe this is a clue? I am using a preloaded mfsroot. I saw some recent commits to HEAD (r279929) about addressing some issues with EFI staging area. But i'm not sure this is the problem, since the loader cannot load /boot/loader.conf or even the kernel itself. So loading the mfsroot of about 10MB would probably not be the issue? Having a working EFI boot is important, since some motherboards will not boot from MBR bootsector when GPT partitions are detected, or do not support MBR-style boot at all and insist on EFI boot. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-198642-8>