as you can see "ok" , then this is no edd problem
it would have been an edd problem if you could only see

no, but i`m sure that this is not related to edd.

not sure if this is fedora specific, but it seems so - see for example:

http://blogs.gnome.org/diegoe/2008/04/10/vesamenuc32-attempted-dos-system-call/

maybe some issue with the vesa bios probe for getting video mode information or switching to appropriate mode.


see that link. try booting with "linux" or "linux0".


regards
roland

_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=100071&distributionid=000000000066

--

Thanks for the helpfull repies.

Please can you CC me or email directly regarding this 
subject, as I'm moving to the Fedora rawhide developrs list 
with this one now.

I will post the solution once it has been found to LKML.

Kind Regards

Keith Roberts.
--

I have put in syslinux 3.70-pre16 code to print the source of this 
message.  You may want to try to grab isolinux from this release and 
update your CD image to get some useful debugging info out of this.

	-hpa
--

Not being a kernel guru, I'm not sure how to do that hpa?

Where do I get isolinux from please?

how do I update my CD image?

I'm willing to give this a try if it will sort out the 
problem.

Please CC me as I'm off the list now. Can't seem to get back 
on again either.

Kind Regards,

Keith
--

You will need to run mkisofs with the same options used to generate the 
image.

In a pinch, if you can point me to the original ISO I could try to 

That would be useful.  This is potentially a previously unreported BIOS 
issue which might have a straightforward workaround, so I'm eager to get 
the data.

	-hpa
--

I originally got mine from:

http://mirror.switch.ch/ftp/mirror/fedora/linux/releases/9/Fedora/i386/iso/Fedora-9-i3...

The sha1sum is:

3b1df20ece05d64c34dd9c64400975b74eded0f2  Fedora-9-i386-netinst.iso

I have also put it on my website, just in case it gets 
updated on the mirrors:

http://www.karsites.net/fedora/9/Fedora-9-i386-netinst.iso

obviously same sha1sum ;)

The Fedora guys are following this thread now. I have put 
the link to your patch on my Fedora bug report:

https://bugzilla.redhat.com/show_bug.cgi?id=450678

I have never built an iso file before, but I'll read up on 
it. My plan was to copy the files from the F9 net-installer 
CD to my hard drive, update them with your patch, and then 
re-make the iso file and burn that back to CD-R. Would that 

Regards

Keith
--

Yes, that should work, assuming the iso file is generated with the same 
mkisofs options as the original image.

	-hpa
--

This message means something has invoked an interrupt in the range 0x20 
to 0x3f, which it should never have done, since that's in the operating 
system range.

Given the complaint about vesamenu further down the page, I'm assuming 
the VESA BIOS is invoking a DOS interrupt(!!!!)... although it's very 
hard to say for sure.

It might be possible to track down by augmenting syslinux to print the 
CS:IP of the supposed DOS system call; if this is the VESA BIOS, it 
would be in the range C000:xxxx.

This probably would be a useful hack anyway, so I'll just implement it.

	-hpa
--

This message usually means your vesamenu.c32 is out of sync with the 
underlying Syslinux version.

If that is not an issue, there is virtually no information in that blog 
(lovely to use a blog instead of filing a proper bug report) that one 
can hang a hat on.

	-hpa
--