linux-kernel - Re: Problems with edd

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 10 Jun 2008 15:48:07 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	devzero@....de
CC:	keith@...sites.net, linux-kernel@...r.kernel.org
Subject: Re: Problems with edd

devzero@....de wrote:
>> Hi all. I have a problem with trying to boot from a Fedora 9 
>> installation CD-R. It works on another machine, so the disk 
>> is OK. I guess if anyone knows the answer then it will be 
>> found here on the kernel developers list.
>>
>> When trying to boot from a CD-R installation disk, on my 
>> Advent 6415 laptop I get the following:
>>
>> Welcome to Fedora 9! [the installer splash screen]
>>
>>  I then click on either:
>>
>>  Install or upgrade an existing system
>>  [or]
>>  Install or upgrade an existing system (text mode)
>>
>>  [both give me the same following error]
>>
>> Loading vmlinuz........................................... 
>> ..............
>>
>>  Loading initrd.img........................................ 
>> .................
>>  ...............ready.
>>  Probing EDD (edd=off to disable)... ok
>>  vmlinuz: attempted DOS system call
>>  boot:

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/