search for: rbil

Hi, I would like to point out an issue with the enumeration of ISA serial devices in Syslinux. If I interpret the snippet below correctly, Syslinux looks up the device order with the BIOS, while Linux uses the fixed order 3F8,2F8,3E8,2E8. Note that this inconsistency is a real problem, as some motherboards (like e.g. a Supermicro X10DRi with default BIOS settings) have a different order

...he default (Linux) order. Nonetheless the vendor default seems to be COM0=2f8, COM1=3f8. I don't have enough different boards to play with to give you an accurate answer on which SM boards/firmware revisions are affected, but it isn't the first time I have seen something like this. > RBIL MEMORY.LST release 61 starting at line 31: > > --------S-M00400000-------------------------- > MEM 0040h:0000h - BASE I/O ADDRESS OF FIRST SERIAL I/O PORT > Size: WORD > Notes: the BIOS sets this word to zero if is unable to find any serial ports > at the addresses it...

...or_cbios) /* * read sector size. * Should not fail but if it does I assume that at least * previous 512 value is not overridden */ movb $0x48, %ah movw %sp, %si 1: /* Get (C)HS geometry */ int $0x13 Assuming the check EBIOS call failed and returned carry, ah will be 1 (according to RBIL) so this last int 0x13 will execute "INT 13 - DISK - GET STATUS OF LAST OPERATION" not "INT 13 - DISK - GET DRIVE PARAMETERS" which is called with ah=8, which I think was the intention. Similarly if any other condition that are checked for a successful EBIOS check fails, this i...

...> Nonetheless the vendor default seems to be COM0=2f8, COM1=3f8. I don't have > enough different boards to play with to give you an accurate answer on which > SM boards/firmware revisions are affected, but it isn't the first time I > have seen something like this. > >> RBIL MEMORY.LST release 61 starting at line 31: >> >> --------S-M00400000-------------------------- >> MEM 0040h:0000h - BASE I/O ADDRESS OF FIRST SERIAL I/O PORT >> Size: WORD >> Notes: the BIOS sets this word to zero if is unable to find any serial >> ports &g...

(FreeDOS developers, I apologize for the redundant parts of this message. But I want to bring the SYSLINUX folks into the discussion, and the SourceForge mailing list archives are broken.) Background: I have a little Sourceforge project (http://unattended.sourceforge.net/) for which I use SYSLINUX to provide CD-ROM and PXE boot support for my boot disk. And it works great with MS-DOS. However,