I have seen where the mgr versions of the image for IVI do not have the legacy bios bootable flag set in the partition table.
I have a bug against MIC for this can you check and see if the bootable flag is set? I use disk in the following manner.. gdisk /dev/sib x (advanced menu) a (set flags) 1 (partition 1) At this point I found that the boot flag was not set 2 (legacy bios boot flag) <Enter> (done with changes) w (write the changes) N (do not fix the MBR) Y (write the changes to the disk) Michael Demeter Staff Security Engineer Open Source Technology Center - SSG Intel Corporation On Aug 16, 2013, at 12:41 AM, Artem Bityutskiy <[email protected]> wrote: > On Tue, 2013-08-13 at 14:46 -0700, Maurer, Steven wrote: >> The failures were slightly different. My first attempt went as >> follows: >> >> >> 1. Downloaded and decompressed the latest 3.0 ivi-XYZ.raw.bz2 into a >> bootable USB memory stick with Gparted on it. NOT overwriting the >> entire stick, but in the filesystem on it. >> This resulted in a ivi-XYZ.raw being next to the Gparted. >> >> >> 2. Stuck this bootable stick into the machine. Set it to boot from >> the stick (which contained Gparted and a decent micro boot >> environment) >> >> >> 3. In the shell of this environment, did a: dd >> if= ivi-XYZ.raw of=/dev/sda .... in other words, wrote the downloaded >> raw data over the hard drive >> >> >> 4. Used the refresh command within Gparted. This did two things: it >> saw two new partitions created on the disk, and complained that the >> backup MBR wasn't properly set to the end of the partition. It >> asked if I wanted to fix it. > > Yes, I know about this issue. But I think this was about the alternate > GPT partition table. Once we gain a normal Tizen installer, this should > not be an issue anymore. > > Also, I am thinking to teach bmaptool to amend the alternate table. > > The problem is that GPT partition have 2 tables, one at the beginning, > and one at the very end of the disk. I the image the alternate one is > indeed at the end, but once you put the image on a device which is > larger, it is not at the end anymore, and tools consider this to be an > error. But this is not a big deal, at least at this point. > > Although I do not understand why you needed this gparted there at all. > >> 5. I let Gparted fix the backup MBR, reset the box, and attempted to >> boot from disk. >> >> >> Result: Received a "No bootable device" error. > > This is strange. May be gparted messed something? >> >> >> Attempt #2 went as follows: >> >> >> 1. Downloaded and installed bmaptool >> >> >> 2. Since I already had ivi-XYZ.raw.bz2 downloaded, I just tried using >> it to completely overwrite a different stick. >> >> >> 3. bmaptool complained about a missing --nobmap option, so I added it. >> >> >> 4. Tried to boot off of the stick that this command created. >> >> >> Result: A black screen on the device. No error about a non-bootable >> device. >> > Hmm, this is strange. >> >> >> In the successful attempt, I simply downloaded the .map file from the >> website, and removed the --nobmap option. This worked. >> > Frankly, I think there was something else. Dd should really just work. I > can verify today that --nobmap works, just to make double sure, which > version of bmaptool did you use (bmaptool --version)? > > Bmap file does not really do anything magic, it just speeds up flashing, > nothing else. > > There must be something else which affected the first to attempts... > > > -- > Best Regards, > Artem Bityutskiy > > _______________________________________________ > IVI mailing list > [email protected] > https://lists.tizen.org/listinfo/ivi
_______________________________________________ IVI mailing list [email protected] https://lists.tizen.org/listinfo/ivi
