Syslinux - Nov 2006 - isolinux menu32 (Re: Problems booting on Intel i9x5 motherboards.)

See: http://syslinux.zytor.com/archives/2006-May/006887.html

I think I've tracked the problem down a bit more specifically.

In edd.S when the kernel calls int 0x13 with %dl=80 [primary disk] &
%al=1 [read one sector] and ah set to READ_SECTORS it never returns.
However, the following code [which does drive diagnostics] works.

	mov     $0x7E, %al
	call prtchr
	movw $0x0000, %ax
	movb $0x14 , %ah
	int $0x13
	mov     $0x7E, %al
	call prtchr

However, when I attempt to reset the disk controller:
	movw    $0x0000, %ax
	movb    $0x80, %dl
	int     $0x13
It also fails to return

The weird thing is if I boot without the menu everything works just
fine. Is there something in the menu code which could cause this kind
of behaviour? Or does anyone have any recommendations of a good place
to start looking?

Cheers,

Holden

-- 
Cell: 613-276-1645

Holden Karau wrote:
> See: http://syslinux.zytor.com/archives/2006-May/006887.html
> 
> I think I've tracked the problem down a bit more specifically.
> 
> In edd.S when the kernel calls int 0x13 with %dl=80 [primary disk] &
> %al=1 [read one sector] and ah set to READ_SECTORS it never returns.
> However, the following code [which does drive diagnostics] works.
> 
> 	mov     $0x7E, %al
> 	call prtchr
> 	movw $0x0000, %ax
> 	movb $0x14 , %ah
> 	int $0x13
> 	mov     $0x7E, %al
> 	call prtchr
> 
> However, when I attempt to reset the disk controller:
> 	movw    $0x0000, %ax
> 	movb    $0x80, %dl
> 	int     $0x13
> It also fails to return
> 
> The weird thing is if I boot without the menu everything works just
> fine. Is there something in the menu code which could cause this kind
> of behaviour? Or does anyone have any recommendations of a good place
> to start looking?
> 
Does it work if you add "edd=skipmbr" or "edd=off"?

	-hpa

Holden Karau wrote:
> See: http://syslinux.zytor.com/archives/2006-May/006887.html
> 
> I think I've tracked the problem down a bit more specifically.
I might add here that this is the exact same machine as before.

--Pat