search for: openelec

Hi, I was hoping you could shed some light in usage of the directive MENU HIDDENKEY in syslinux (extlinux 4.04) The docs say: MENU HIDDENKEY key[,key...] command... So, in my conf I have: MENU HIDDENKEY Esc openelec Where openelec is the label of the boot option I want to run only if Esc is pressed. But pressing Esc on boot has no effect. Default is run. So, do I misunderstand the "command" part of the directive? If so, are there any examples I can learn from? My full conf is here: http://pastebi...

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 virtually all of the various systems that I have here at my disposal, except for one. The one system where I am unable to boot from these USB flash drives...

> > 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 virtually all > of the various systems that I have here at my disposal, except for one. > > The one system where I am unable...

We're currently working for project OpenElec on a syslinux menu. We would like to know if it's possible to move the menu position to the middle/bottom instead of the top... Currently we simply use the Vesamenu as it doesn't require much more functionality. I saw a post regarding the option MENU STARTROW, but that doesn't seem t...

...;where 'sdX' is (are) the problematic device. I have done both of the above commands now, for each of the two USB sticks that I still have and that still don't boot on the Gigabyte motherboard. One of these has a recent vintage Ultimate Boot CD on it and the other has a recent vintage OpenELEC on it. In each case, I captured both stdout and stderr, together in one output file. Please find the following four files here: ftp://ftp.tristatelogic.com/private/ady/ ubcd.0 -- results of the first command shown above, when executed against the UBCD USB stick ubcd.1 -...

...uirement to work with these type of (USB) media, not >just for Syslinux. Apparently, yes. And it seems to me that the simplest way (from the point of view of the end user) to insure that these things are done correctly is for the distributors of tools such as Clonezilla, Ultimate Boot CD, and OpenELEC to follow in the footsteps of, e.g. the Archlinux folks and the Debian folks and the LessLinux folks i.e. by just simply distributing images that can be (no-brainer) block-by-block copied onto USB sticks in order to produce a working stick... using either dd or whatever the bleep its counterpart on...

..."hidden sectors" (aka. "sectors > >before") with a corresponding 63. If the values don't match, strange > >things will eventually happen. > > OK. Are you saying that this critical matchup was NOT present in or on > the originals Clonezilla, UBCD, and OpenELEC USB sticks that I had in my > possession before I started this whole thread? You know, the ones that > booted find on other machines (but not on the GA-M55Plus-S3G) ? We have no specific information about those USB drives (not even an "fdisk -l" and similar commands), and we don...

...and it is Good that I did, because as a side-effect of trying to answer your question, I found something TOTALLY ASTONISHING. But we'll get to that in a second... To answer your question... *) with respect to Ultimate Boot CD (5.2.7), the answer is "CHS". *) with respect to OpenELEC (3.2.3, I think), the answer is "CHS". *) with respect to Clonezilla (2.2.0) I can't easly check anymore, because I overwrote the stick that contained that (while performing some of the other tests people asked me to conduct). If it is important, I will get...

...en very much of what you have to say, but it might possibly be enlightening.) >Also avoid any >"multiboot"-related tool or "USB-drive-writing-tool". Currently, most >of these "user-friendly" methods will fail with these particular >tools (specially with openELEC and Clonezilla). I see. Well, I am quite completely sure that I created my OpenELEC stick by executing (under windows 7) the little .exe file that they distribute (in their distribution .zip files) and that they tell you to use in order to actually put OpenELEC onto a USB stick. So if there are...

...Syslinux thing and this later stage ldlinux.c32 thing. But if there are any such issues/problem that are relevant to, or that pertain to the problems that _I_ have described here, then *I* did not create them. I do not hack or diddle these tools that I have mentioned... Clonezilla, UBCD, or even OpenELEC (yet)... in any way. I just download the latest images that are meant for installing on a USB flash drive, and then I just dd them to my USB flash drives, or do whatever the standard install instructions tell me to do. I am not attempting to be clever. I'm just doing exactly the same things...

...ant to create a useful stand-alone bootable tool too. Obviously, Syslinux is a key and critical part of the process of creating such a thing. But where might a person find instructions and advice on how to create the NEXT part, i.e. a minimalist Linux... along the lines of what is used to support OpenELEC or Clonezilla... for the world's next great stand alone bootable app? Is there any one place where enlightenment about THIS part of the process is concentrated? (Not that I have any plans myself to work on creating the world's next great stand-alone application. I am just acutely aware t...

...board Dom0: Debian Wheezy stock xen (v4.1.3) + Debian stock kernel (3.2.x / 3.6.x) 64 bit version. Note that both of us have only one gpu in the system. They difference is that the lucky guy has an DQ77MK while mine is an AsRock. Another different is that he picks win 8 as domU, while my target is openelec 2.0, a linux 3.2.x based HTPC distro. So basically what I can see is a functional domU, almost, I mean. It does not freeze / lock up at all. All the assigned devices (IGD, audio, USB) are recognized and appears to work. I can hear sound from aplay, so audio is working. I can see the mouse I attach...

...years experience with.) >>From your own reports, I am confident that you don't need to keep >trying different ISO images, dd'ing some additional distro, expanding >additional archives. Good. >The initial problem has nothing to do with UBCD, nor Clonezilla Live, >nor OpenELEC, Even I understood from the outset that the problem... whatever it is/was... had nothing specifically to do with those tools. That is why I came here, you know, as opposed to directing a bunch of questions to the producers of those tools. >This particular mainboard might be using different BI...

Hi developers, I met some domU issues and the log suggests missing interrupt. Details from here: http://www.gossamer-threads.com/lists/xen/users/263938#263938 In summary, this is the suspicious log: (XEN) vmsi.c:122:d32767 Unsupported delivery mode 3 I''ve checked the code in question and found that mode 3 is an ''reserved_1'' mode. I want to trace down the source of this

...VBR should indicate the "hidden sectors" (aka. "sectors >before") with a corresponding 63. If the values don't match, strange >things will eventually happen. OK. Are you saying that this critical matchup was NOT present in or on the originals Clonezilla, UBCD, and OpenELEC USB sticks that I had in my possession before I started this whole thread? You know, the ones that booted find on other machines (but not on the GA-M55Plus-S3G) ? >Generally speaking, the BIOS itself has to support (understand) the >values that are being used in the MBR. Yes. But what ex...

> 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

...s but doesn't even show up in the Boot Priority list of the GA-M55PLUS-S3G! Isn't that enough evidence, even just all by itself, to convince us all that the GA-M55PLUS-S3G BIOS is hopelessly brain damaged? If not, then combine it with the fact that I also have Clonezilla *and* UBCD *and* OpenELEC sticks that also boot just fine everywhere except on the GA-M55PLUS-S3G, and the verdict is clear, I think. This board is worth any more of my time, and most probably isn't worth any more of your's either. >By the time I am writing this, the issue about the "LBA" flag has &g...

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

...better to older > motherboards and older Award BIOSes, such as what I have? Lastly, > may I also safely assume that at some appropriate point in the future, > Mr. Syslinux, or some close associate, will actively take steps > to actively encourage the developers of UBCD, Clonezilla, and OpenELEC > to incorporate the new "fixed" version of Syslinux into their future > distributions, you know, so that other poor sods like me won't in > future be beset by these issues? (For my part, *I* have already > ordered a new/replacement motherboard, so all of this work we'...

...need additional commands / steps / writing. *** >From your own reports, I am confident that you don't need to keep trying different ISO images, dd'ing some additional distro, expanding additional archives. The initial problem has nothing to do with UBCD, nor Clonezilla Live, nor OpenELEC, nor... The problem is related to using an adequate partitioning (one) and a formatting tool (one), with the adequate values, together in combination with adequate BIOS settings. Mixing different partitioning tools (with different behaviors and default values) might sometimes corrupt the boot c...