Open GoogleCodeExporter opened 8 years ago
>>> Syslinux has no problems on the DV6 and can boot any ISO
But how? Do you mean "with memdisk"? Note that a grub4dos way that is
equivalent to memdisk must be by using "map" WITH --mem.
>>> map /Xiaopan0.4.4.iso (0xff)
If I am not mistaken, syslinux has not yet an equivalent way for direct mapping.
If you succeeded using memdisk, try the equivalent way of "map --mem".
You cannot simply compare "non-mem map" with memdisk.
Original comment by tinyb...@gmail.com
on 8 Feb 2014 at 2:43
Booting xiaopan using Unetbootin works on all systems (including the DV6)
Booting xiaopan using grldr works on all systems except DV6.
I don't have an HP DV6 and so cannot test myself, so I have to rely on user
report.
Original comment by Steve6375
on 8 Feb 2014 at 3:01
Sounds like one more case of "BIOS attack". If we lack deeply technical
description, we would not appear to have any chance to solve it.
I am afraid you might have to tell the case of "map --mem", as one of the steps
towards the final solution(with success, hopefully).
Original comment by tinyb...@gmail.com
on 9 Feb 2014 at 1:09
as reported by user
using --mem to load the iso file into memory - it gets stuck on the --mem
command at about 56 out of 96.
Original comment by Steve6375
on 10 Feb 2014 at 10:24
What about the CPU? Is it AMD or Intel?
From the report, it sounds like a buggy CPU with a buggy BIOS.
Similar issue was encountered several years ago, and happens from time to time,
or say, occasionally. Last year an AMD machine was reported to have this issue.
See reports and discussion here in Chinese:
http://bbs.wuyou.com/forum.php?mod=viewthread&tid=311435&page=5#pid2815556
Yes, we have fished out a way(or a workaround). Insert a line of "pause
--wait=S" just before the "hanging-up" line, and the problem could be avoided.
Try various values of S, e.g., from 0 to 30, until you gain a "success" that it
will almost never hang up.
Original comment by tinyb...@gmail.com
on 11 Feb 2014 at 10:46
No more news from user - suggest close this as sounds like a buggy BIOS?
Original comment by Steve6375
on 29 Aug 2014 at 10:39
Original issue reported on code.google.com by
Steve6375
on 4 Feb 2014 at 11:41