I could boot from USB but the console stops after printing the resolution. I tried on a macbookpro of unknown age (not brand new, not very old) and a newer Air. I could tell by the way my USB key blinked that it actually finished booting and went to the installer, and would shut down properly when I hit the power button. I modified my USB key to enable a vt100 serial console on /dev/cuaU0 in /etc/ttys and used a USB serial console where I could login and run bsdinstall if I wanted. I was able to finish a bootable uefi install to a second USB key but the console on all of these installs stops after printing the resolution. It was not clear to me if it that means it just doesn't support the screen or what. X claimed it could not find a console. On 07/12/2014 10:24, Huang Wen Hui wrote: > As loader.efi and kernel not change at all from USB to CD, I am confuse why > you can boot from CD. > Anyway, I try to boot from CD as you suggest, but I got the same result as > before:( > > > 2014-07-12 18:09 GMT+08:00 Anders Bolt-Evensen <andersbo87_at_icloud.com>: > >> I also got a message like that when I booted from a USB stick on a >> MacBookPro8,3 (17 inch, late 2011). >> >> I fixed it by creating a custom ISO image and burned that onto a DVD using >> an external DVD drive. >> The UEFI installer boots fine from this external DVD drive. >> >> Here is how I did it: >> >> Genereste an ISO with the FreeBSD-CURRENT kernel, mount the ISO and copy >> all files from the root directory in the ISO and unmount >> > cd /usr/src/release >> > sh ./generate-release.sh # You may have to run “make buildworld” and >> be connected to the internet to install required ports. >> > mount -t cd9660 /scratch/R/release/FreeBSD-something-disc1.iso /mnt >> > mkdir freebsd_generic_installer >> #Files copied to the directory in the next command will be copied to a >> new ISO in step 3 >> > cp -R /mnt/ freebsd_generic_installer/ >> > umount /mnt >> 2. Create a FAT filesystem image and place the loader in it in the default >> path that UEFI will look for (the following steps are copied from >> https://wiki.freebsd.org/UEFI#CD.2FDVD_Boot_under_UEFI): >> > dd if=/dev/zero of=efiboot.img bs=4k count=100 >> > mdconfig -a -t vnode -f efiboot.img >> > newfs_msdos -F 12 -m 0xf8 /dev/md0 >> > mount -t msdosfs /dev/md0 /mnt >> > mkdir -p /mnt/efi/boot >> > cp loader.efi /mnt/efi/boot/bootx64.efi >> > umount /mnt >> > mdconfig -d -u 0 >> >> 3. Create the custom ISO image. Please make sure that the entry in >> freebsd_generic_installer/etc/fstab matches the label you choose in the >> command below. >> > makefs -t cd9660 -o bootimage='i386;efiboot.img' -o no-emul-boot -o >> rockridge -o label=“FREEBSD_UEFI_INSTALL" -o publisher="test" uefi-test.iso >> freebsd_generic_installer/ >> >> To get the example in the command above to work, please make sure that the >> entry in freebsd_generic_installer/etc/fstab reads >> "/dev/iso9660/FREEBSD_UEFI_INSTALL / cd9660 ro 0 0" >> >> 4. Burn the image to DVD, reboot your system and choose “EFI Boot”. Note >> that unless you are using a EFI console like rEFIt or rEFInd, you may have >> to kind of wait a couple of minutes while the kernel is loading before >> anything appears on the screen. >> >> >> >> On 04/07/14 16:34, Huang Wen Hui wrote: >> >>> Hi, >>> On my MacbookPro11,3, I got this error message: >>> >>> http://sw.gddsn.org.cn/freebsd/uefi.jpg >>> >>> cheers, >>> >>> Huang WenHui >>> >>> 2014-07-04 22:13 GMT+08:00 Ed Maste <emaste_at_freebsd.org>: >>> >>> On 24 May 2014 19:39, Rafael Espíndola <rafael.espindola_at_gmail.com> >>>> wrote: >>>> >>>>> Yes, I got that in the mac laptops I tried, it worked on a Mac Pro. It >>>>> might be the frame buffer corruption that Ed Maste was mentioning. >>>>> >>>> I purchased a new MacBook Air yesterday (model identifier >>>> MacBookAir6,2). UEFI boot and vt(4) worked correctly. (My image >>>> included Rafael's patch; I haven't tried a boot without.) >>>> >>>> I also committed a change to display the framebuffer parameters >>>> (address, dimensions, etc.) on boot, in order to help identify the >>>> source of this issue. If you have a moment can you build a new USB >>>> stick image and give it a try? >>>> >>>> -Ed >>>> >>>> _______________________________________________ >>> freebsd-current_at_freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org >>> " >>> >> >> > _______________________________________________ > freebsd-current_at_freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org" >Received on Sat Jul 12 2014 - 14:38:23 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:50 UTC
