Description of problem: The option in the boot menue "Boot from harddisk" does not work when you use a usb key as install medium. Possible cause: usb key is regarded as harddisk, so the system boots from this medium again. Version-Release number of selected component (if applicable): Installer of Beta2 ISO
Same for me. With the dvd install iso put on a USB stick, the option "boot from harddisk" put me back every time to the boot menu.
CC: (none) => marianne
for me, it worked, except that i used a real DVD.
CC: (none) => maarten.vanraes
I have tested it on two machines. on both the usb-stick is regarded as harddisk (not as removable device). So it's normal, that a "boot from harddisk" boots the stick.
CC: (none) => magnus.mud
I think Magnus is right, "boot from harddisk" means boot from the first bootable-HD... But maybe gfxboot logic should be adapted to work even in that case? (though it mayn't be possible as GRUB thinks "first bootable HD" in this case).
CC: (none) => boklm, mageia, pterjanComponent: Installation => RPM PackagesSource RPM: (none) => mageia-gfxboot-themeSeverity: normal => enhancement
Yes this is "normal" as the bios will list the usb device as first hard disk isolinux config is set to "localboot 0x80" for the harddisk entry Reading the doc I found this: With ISOLINUX, the "type" specifies the local drive number to boot from; 0x00 is the primary floppy drive and 0x80 is the primary hard drive. The special value -1 causes ISOLINUX to report failure to the BIOS, which, on recent BIOSes, should mean that the next device in the boot sequence should be activated. It means giving -1 should work but I am scared by the "recent bios" thing
perhaps it can be adjusted to get the next one if the first one is the one you just booted from?
Feel free to patch isolinux :)
:-( well, i don't use usbstick installs, so i don't care... someone else can fix it.
I actually had a look at the (asm) code, this -1 uses int 18h to mark the current boot device as failed so that bios jumps to the next one. I don't know how many years ago this "recent bios" mention appears but I would expect it to be supported by very old BIOS... http://en.wikipedia.org/wiki/BIOS_interrupt_call#.E2.80.8BINT_18h.E2.80.8B:_execute_BASIC Code is http://git.kernel.org/?p=boot/syslinux/syslinux.git;a=blob;f=core/localboot.inc;h=1fe3102df9bc12d13f19d26f09e31ed94106abb3;hb=HEAD As you can see there is currently no logic there, except the test for -1 I think using -1 instead of 0x80 should be quite safe
except if you had another CDrom in it? or you installed from cdrom, but had an usb stick in it as well? maybe. but nice thinking... sounds like a good idea?
Duplicate bug *** This bug has been marked as a duplicate of bug 180 ***
Status: NEW => RESOLVEDCC: (none) => ennael1Resolution: (none) => DUPLICATE
This bug has more info.
Status: RESOLVED => REOPENEDResolution: DUPLICATE => (none)
*** Bug 180 has been marked as a duplicate of this bug. ***
CC: (none) => shikamaru
Assigning to maintainer now that our maintainers database has an entry for this package. Please assign back to bugsquad@mageia.org in case of a mistake from me.
CC: (none) => stormiAssignee: bugsquad => balcaen.john
CC: (none) => balcaen.johnAssignee: balcaen.john => watersnowrock
pinging. because nothing happened to this report since more than 3 months ago, and it still has the status NEW or REOPENED @ Donald Please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead.
CC: (none) => marja11
I was sure that I had commented on this but I guess not.... If someone who had the technical know how, ie Pascal as I don't, then by all means change 0x80 to -1 and see if it fixes the issue. I would appreciate any help with maintaining the more technical sides of this package, as i am more interested in the artwork side of it. I will be the assigne for now, unless someone else feels that they want it.
Status: REOPENED => ASSIGNED
Blocks: (none) => 4299
(
Blocks: 4299 => (none)
*** Bug 5957 has been marked as a duplicate of this bug. ***
CC: (none) => eeeemail
syslinux/gfxboot bug more technical than with the artwork iirc
Status: ASSIGNED => NEWAssignee: watersnowrock => bugsquadSeverity: enhancement => normal
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
Duplicate 5957 was against pre 2 final. I take it this bug was still valid for 2 final
Keywords: NEEDINFO => (none)Whiteboard: (none) => (MGA2)
Yes, it is marja.
Whiteboard: (MGA2) => (MGA2) 3alpha1
Valid mga3 alpha1
valid mga3 alpha2
Whiteboard: (MGA2) 3alpha1 => (MGA2) 3alpha1 3alpha2
Whiteboard: (MGA2) 3alpha1 3alpha2 => 3alpha1 3alpha2 3alpha3 3beta1 (MGA2)
valid 3beta2
Whiteboard: 3alpha1 3alpha2 3alpha3 3beta1 (MGA2) => 3alpha1 3alpha2 3alpha3 3beta1 3beta2 (MGA2)
confirmed on RC (from 2013-05-04)
Whiteboard: 3alpha1 3alpha2 3alpha3 3beta1 3beta2 (MGA2) => 4alpha3 3alpha1 3alpha2 3alpha3 3beta1 3beta2 (MGA2)
*** Bug 11887 has been marked as a duplicate of this bug. ***
CC: (none) => dvgevers
Whiteboard: 4alpha3 3alpha1 3alpha2 3alpha3 3beta1 3beta2 (MGA2) => 4beta2 3alpha1 (MGA2)
If https://bugs.mageia.org/show_bug.cgi?id=11887 is a duplicate, the subject is wrong. Moreover, I would suggest that is blocks bug #11704 !
Summary: "Boot from harddisk" does not work when using a usb key as install medium => "Boot from harddisk" does not work when using a classical iso or usb key as install mediumWhiteboard: 4beta2 3alpha1 (MGA2) => 4RC (MGA2)
Maybe this is a stupid remark, but it works from Live disks, so why cannot same be applied to classical disks?
I've been looking at this problem and found a solution. That's solved by revision 567352. Can anyone start a rebuild of the syslinux package ? Cheers,
Status: NEW => RESOLVEDCC: (none) => erwanaliasr1Resolution: (none) => FIXED
Sorry but the iso containing syslinux-6.02-4.mga4 does not boot from hd via the boot menu option.
Status: RESOLVED => REOPENEDResolution: FIXED => (none)Whiteboard: 4RC (MGA2) => 4final (MGA2)
To complete the info: I tried from DVD (not usb)
If it cannot be fixed I would propose to remove the option from the final iso's (better invisible than broken)
Blocks: (none) => 11704
(In reply to Dick Gevers from comment #33) > If it cannot be fixed I would propose to remove the option from the final > iso's (better invisible than broken) Can you describe the behavior you have on the latest syslinux ?
I believe comment #5 explains why this is expected. Config should be changed if we want a different behaviour.
@erwanaliasr1 re #c34 >Can you describe the behavior you have on the latest syslinux ? Use one of the classical isos and as soon as I select "Boot from hard disk" and press Enter the screen goes black and on the top is printed one line reading: Booting from local disk... and nothing else happens. Machine can now only be hard reset.
*** Bug 12459 has been marked as a duplicate of this bug. ***
CC: (none) => andybiker
Solved in this afternoon's classical DVD. Thanks
Status: REOPENED => RESOLVEDResolution: (none) => FIXED
Glad to see my patch worked \o/ that will allow to stay on 6.02 + patch for the release.
CC: boklm => (none)
Erwan, looks broken again on cauldron https://bugs.mageia.org/show_bug.cgi?id=13680
Version: Cauldron => 4Source RPM: mageia-gfxboot-theme => syslinux
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=13680
evident in Mageia-5-rc-LiveCD-KDE4-en-i586-CD
CC: (none) => westel