similar to: USB boot problems on Gigabyte GA-M55Plus-S3G

In message <BLU0-SMTP557B92590B4CC34F8318088BB30 at phx.gbl>, Ady <ady-sf at hotmail.com> wrote: >Since in all cases you get to see at least the Syslinux copyright >message, the problem doesn't seem to be related to whether your BIOS >can identify the USB disk and boot from it. I can only agree. >Some GA motherboards might identify some USB drives as

> > In message <BLU0-SMTP1383C5798F6C577E5FFF368BA40 at phx.gbl>, > Ady <ady-sf at hotmail.com> wrote: > > >> With respect to all of the actually important stuff however, I may have > >> missed it all, but I don't recall having read or seen an explanation of > >> what Ady & everybody else finally figured out about all this... > >

> > >This particular mainboard might be using different BIOS values than > >others, and there are several other alternative explanations for all > >these issues. Your last few tests suggest that we are on a good track > >now. > > I have just a couple of questions. First, who exactly is Mr. Syslinux? > Who is the primary developer/maintainer? Second, may I

> >Are you willing to dd such image (*not* using Windows OS) and provide > >feedback? > > Yes. More broadly, I am willing to dd and try *any* image you might > ask me to try. > Hi Ronald, You posted in a recent email in this same email thread, about successfully booting an ArchLinux USB. Among several differences in comparison to your prior tests, you used a

> > In message <BLU0-SMTP2805E16A0E7A33B925EDF458BB80 at phx.gbl>, > Ady <ady-sf at hotmail.com> wrote: > > >Now, to move forward with Clonezilla in your USB drive, we need to > >proceed with some steps that are not as simple as dd'ing an image. > > Apologies for my impertinence, but I have one question: Why? > > I was under the impression

> > It looks like Clonezilla and Ultimate Boot CD both prescribe > special installation procedures for USB stick. > isohybrids can be put onto stick just by e.g.: dd of=/dev/sdb > Make a backup of the stick if you later want to restore its > partitioning. > The (recent yet not latest) versions of Clonezilla that used Syslinux 5.xx will fail in some systems when writing

> With respect to all of the actually important stuff however, I may have > missed it all, but I don't recall having read or seen an explanation of > what Ady & everybody else finally figured out about all this. What is > the answer, in the end? I did get the part about how (for my board, > at least) tweeking some of the info within the relevant MBR partition > table

On 01/19/2014 03:47 PM, Ronald F. Guilmette wrote: > > Doesn't the Syslinux project provide (hopefully strong) specific > reccomendations, to its user base, for how these things should best > be done, you know, in order to insure maximal interoperability? > We try (see our wiki), but those recommendations can only come from mass testing across many, many systems -- which we

In message <BLU0-SMTP47F18ED7837B2CE7C672C88BBE0 at phx.gbl>, Ady <ady-sf at hotmail.com> wrote: >@Ronald, > >I have to admit I am a little bit frustrated. lol Join the club! I've invested hours and hours and hours on this little project, and all I have at the end is a board that _still_ has a brain damaged BIOS that won't boot things that everything else I own

Ady, before responding to you further, I'll ask you now to take onje more (fresh) look at this thread that I started over in the GParted forums: http://gparted-forum.surf4.info/viewtopic.php?pid=31834 Please note that I have now followed-up on myself and that I have added quite a lot of new & additional information. It now appears to me that GParted's reporting of the status of

> > You will be happy to know that your test image _does_ appear to boot OK > on my GA-M55Plus-S3G, from either/both of my test sticks (4GB & 8GB). > > Whatever magic you did, it seems to have worked. (Please _don't_ go > into too much technical detail, but... in layman's terms... what did > you do?) > > Here is what I got after booting from the 8GB

In message <BLU0-SMTP145A44932CB6CC2DB4621568BB30 at phx.gbl>, Ady <ady-sf at hotmail.com> wrote: >Recent (testing) Clonezilla versions include changes related to >booting problems, so there are valid reasons to try the very latest >version available. At the time I am writing this email, Clonezilla >Live 2.2.1-22 is the latest available (at this moment, under

Am 18.01.2014 04:30, schrieb Ronald F. Guilmette: > The results were the same in both cases. In both cases, LessLinux > Search & Rescue booted up and began a timed 10 second countdown, which > I allowed it to finish in each case. After that, it started to do > something... I'm not even sure what, exactly... and eventually froze > up while displaying a progress bar,

> > I have successfully created bootable USB flash drives containing the > following bootable products: > > 1) Clonezilla (recent version) > 2) Ultimate Boot CD (recent version) > 3) OpenELEC (recent version) > > All of these apparently use SYSLINUX as part of the boot process. > > All three boot up just fine and with no problems at all on

In message <BLU0-SMTP4359BC7EA366B1FB76EA9188BBF0 at phx.gbl>, Ady <ady-sf at hotmail.com> wrote: >I am probably misunderstanding something. We seem to go backwards. Yes, and ever moreso. >"Something" changed. If you now cannot see your USB drive in your >list (press F12 during POST), there is no point on redacting >instructions. *Now* that I have set up

In message <1767645779554124797 at scdbackup.webframe.org>, "Thomas Schmitt" <scdbackup at gmx.net> wrote: >Hi, > >> > debian-7.3.0-i386-netinst.iso >> This image also boots with no problems on the GA-M55Plus-S3G. > >So isohybrid boots with and without additional GPT. >It boots with partition start 0 and with partition start at 32 kB. OK. If

Op 2014-01-20 om 00:04 schreef Ronald F. Guilmette: > In message <52DCC023.7000100 at zytor.com>, H. Peter Anvin wrote: > >On 01/19/2014 03:47 PM, Ronald F. Guilmette wrote: > >> > >> Doesn't the Syslinux project provide (hopefully strong) specific > >> reccomendations, to its user base, for how these things should best > >> be done, you

Hi, (mixing statements from various mails) Ronald F. Guilmette wrote: > To repeat, I already do know exactly how to set or unset the bootable > flag. Sorry for not getting this right on the first reading. I currently understand that a set active/bootable flag prevents the USB stick from showing up in BIOS, and that without that flag it begins to boot but fails with files not found.

In message <BLU0-SMTP145A44932CB6CC2DB4621568BB30 at phx.gbl>, Ady <ady-sf at hotmail.com> wrote: >> Is there something specific I should try? /boot/syslinux ? >> > >>From the syslinux boot prompt in UBCD you could try: >/boot/syslinux/config.c32 /boot/syslinux/syslinux.cfg /boot/syslinux/ > >(Yes, it is the same basic absolute path, three times, all

In message <73645861681468542 at scdbackup.webframe.org>, "Thomas Schmitt" <scdbackup at gmx.net> wrote: >me: >> > Check whether it fails with Clonezilla. >Ronald F. Guilmette: >> Please be specific. For Clonezilla, there are many different versions > >Any failure on the same stick which also succeeds is enough >to kill the theory of bad