Bug 756899

Summary: can't boot Fedora Live written on Thinkpad T420s
Product: [Fedora] Fedora Reporter: Jens Petersen <petersen>
Component: livecd-toolsAssignee: Brian Lane <bcl>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: adam.stokes, bcl, bruno, dhuff, Jasper.Hartline, katzj
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-21 22:06:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jens Petersen 2011-11-25 02:43:05 UTC
Description of problem:
If I use F16 to write a Fedora Live image to usb
it doesn't boot my Lenovo Thinkpad T420s.
Using livecd-tools-15.11-1.fc15 it boots fine.

Version-Release number of selected component (if applicable):
livecd-tools-16.9-1.fc16

How reproducible:
100%

Steps to Reproduce:
1. Write Fedora Live to USB with livecd-tools-16.9-1.fc16.
2. Try to boot T420s laptop.
3. Downgrade to livecd-tools-15.11-1.fc15...
4. Try to boot Live on laptop again
  
Actual results:
2. doesn't get to grub?
4. boots normally

Expected results:
2. To boot live image.

Additional info:
This laptop only seems to support GPT with UEFI.
(--efi boot works ok with livecd-tools-16.9-1.fc16.)
Maybe there is some different in partition table
handling between 15.11 and 16.9?

Comment 1 Jens Petersen 2011-11-25 03:10:33 UTC
Sorry the information about 15.11 with F16 is misleading: it doesn't boot either.

Maybe it is another difference between f15 and f16.

I am pretty sure before I upgraded to F16, the images I wrote
with livecd-tools booted ok on my new laptop.

Comment 2 Brian Lane 2011-11-28 18:23:02 UTC
Some Thinkpads have problems booting from GPT labeled disks. When you wrote the USB stick did you use --format --reset-mbr? If not it might be possible that it was trying to boot from non-efi on GPT labeled USB and failing.

running:

parted -s /dev/USBDEV p

on the working and non-working USB sticks would also be helpful.