[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #43062] boot-directory not in core.img

From: Jay Michael
Subject: [bug #43062] boot-directory not in core.img
Date: Thu, 20 Nov 2014 04:36:47 +0000
User-agent: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.2; WOW64; Trident/6.0; Touch)

Follow-up Comment #3, bug #43062 (project grub):

     What was supposed to change?

     I've lost track of where I was and what I was doing.  I believe I
reported the "bug" while trying to get a handle on doing a BIOS boot from and
external drive that uses 4k sectors.  Since then, I have managed to get a
64-bit Ubuntu to boot in EFI mode from that drive.  I would now hesitate to
fling grub-install at that drive, for fear of damaging something.

     When I re-ran the old bootinfoscript to confirm the old results before
running the new bootinfoscript, I got different results:  Instead of

core.img is at this location and looks in partition 112 for .

I get

, but core.img can not be found at this location.

I don't know when or why in installing Ubuntu in EFI boot mode it would have
wiped out the BIOS-boot bits.

     Another change to the BIS seems to have been how picky it is about which
version of AWK it uses.  The new script expressed dissatisfaction with the
version of *mawk* in my Live-USB environment -- the old version seems to fall
back on a BusyBox version with just a little grumbling.  I created a symbolic
link from /usr/bin/gawk to mawk to get the new script to run -- I assume that
has nothing to do with the differences I'm seeing.

     Let me know if you want me to follow up on anything.

(file #32482, file #32483)

Additional Item Attachment:

File name: bis-061-results.txt            Size:40 KB
File name: bis-20140825-results.txt       Size:38 KB


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]