>Number: 184910 >Category: misc >Synopsis: bootcode not installed correctly by bsdinstall >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Dec 16 19:50:00 UTC 2013 >Closed-Date: >Last-Modified: >Originator: Max Parmer >Release: 10.0-RC1 >Organization: >Environment: FreeBSD fatima.local 10.0-RC1 FreeBSD 10.0-RC1 #0 r259068: Sat Dec 7 17:45:20 UTC 2013 [email protected]:/usr/obj/usr/src/sys/GENERIC amd64 >Description: Following a simple UFS autopartitioned install from `bsdinstall` on a Lenovo x220 (w/latest BIOS image available from Lenovo) the bootcode does not appear to be installed. I.e. the system reacts as if there is no bootable OS on the boot drive.
I experimented with GPT partitioning and also made some attempts to get bootcodes working for ZFS (with both but MBR and GPT schemes) and never quite sorted out what to bootcode to install where to render the install bootable. It is my understanding the x220s (and some other Lenovo laptops) have some known idiosyncratic boot behavior, but it also seems as if bsdinstall has been skipping the branch wherein it installs bootcodes on this system. In all experiments I used the memstick USB image I have not experienced this issue with virtualized systems >How-To-Repeat: Install with any autopartitioned option in `bsdinstall` on a Lenovo x220 (regardless of legacy boot vs. EFI boot BIOS setting) with either a current or vintage BIOS installed. >Fix: To remedy this I have exited to a shell following the installer, and have manually run: gpart bootcode -b /boot/mbr /dev/ada0 gpart bootcode -b /boot/boot /dev/ada0s1 >Release-Note: >Audit-Trail: >Unformatted: _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "[email protected]"
