search for: regs_in

Hey, Looks like read disk function which was launched in 3.35 isnt working. Did anyone test this on any hardware? I'm using it thru the com32 interface to read contents of the active partition of a USB boot key (syslinux). I did a sample test like: void scanAndPrint() { com32sys_t regs_in; char *sectorBuf = __com32.cs_bounce; int i; memset(sectorBuf, 0x0, 512); // XXX MARK 1 for (i=0; i< 10; i++) { int j; memset(&regs_in, 0, sizeof regs_in); regs_in.eax.l = 0x0019; regs_in.edx.l = i; // sector number regs_in.ecx.l = 1; // sector cou...

...have. When mboot was querying the BIOS for their E820 memory maps they were getting gobbly gook and not the proper memory maps. We did not see this problem with our Dell Proliant 1750's. I found a fix which I've applied to mboot.c32 and it seems to fix the problem. The issue is that the regs_in struct passed into the INT15/E820 call the full register structure was not being cleared. Although the mboot.c code does clearly set the designated fields for the e820 interrupt apparently the HP bios's can do strange things depending upon the value of the unspecified register fields. The reg...

...the real root on sda1. The problem is that everytime I try and boot I get to this line and it just hangs: Booting: MBI=0x00010120, entry=0x00100000 I found references to this problem in the archives (http://syslinux.zytor.com/archives/2006-March/006654.html ) and made sure that the memset of the regs_in was happening, and that is being done in 3.20-pre8 (hence the reason I'm even using it). I found some references to using particular versions of gcc, I'm currently using 3.4.4could this be a potential issue? I'm hoping that once I get past the mboot.c32 issues and actually get into my...

I'm seeing this on a HP Blade and i'm not sure why this is happning since the nature of the issue is so wierd. I compiled mboot.c with a DEBUG defined in the mboot.c file. In the funciton init_mmap(), it prints the e820 map and on the HP blade this map values come out to be totally random. Some weird numbers which dont make any sense at all. However, if i add a while(1); or a exit(1); at

...a bug in mboot.c. If you can send me the kernels and configuration files you're using, I'll try to reproduce the problem here. > I found references to this problem in the archives > (http://syslinux.zytor.com/archives/2006-March/006654.html ) > and made sure that the memset of the regs_in was happening, and that is > being done in 3.20-pre8 (hence the reason I'm even using it). I found some > references to using particular versions of gcc, I'm currently using > 3.4.4could this be a potential issue? Shouldn't be; I've built mboot.c32 with that version of GC...