iPXE, iSCSI and int13
|
2016-03-12, 00:21
(This post was last modified: 2016-03-12 12:17 by mr_jrt.)
Post: #8
|
|||
|
|||
RE: iPXE, iSCSI and int13
So, I'm having a looksie at the source, (and learning AT&T ASM syntax, it seems), and I'm drawn to int13_load_mbr in int13.c.
Am I reading it correctly when I read that it calls interrupt 13 function 2 with a request for 1 sector from CHS 0,0,1 from the specified drive number (0) into the buffer address (0x7c00) passed in via the variable "address", and if that succeeds, we zero-out the AX register, otherwise leave it be and save it out into the variable "status"? I ask because that would explain why I'm seeing status 01 reported - it's read one sector (and the iSCSI side of the logging and tracing suggests this is all fine as well), but for some reason the carry flag is being set, triggering reporting as an error. I'll have to dig into the iSCSI hook to see why that would be... Code: Mar 11 22:27:23 192.168.60.5 ipxe: Booting from SAN device 0x80 |
|||
« Next Oldest | Next Newest »
|
Messages In This Thread |
iPXE, iSCSI and int13 - mr_jrt - 2016-03-07, 00:55
RE: iPXE, iSCSI and int13 - mcb30 - 2016-03-07, 23:44
RE: iPXE, iSCSI and int13 - mr_jrt - 2016-03-07, 23:53
RE: iPXE, iSCSI and int13 - mr_jrt - 2016-03-09, 00:48
RE: iPXE, iSCSI and int13 - mr_jrt - 2016-03-10, 01:58
RE: iPXE, iSCSI and int13 - NiKiZe - 2016-03-10, 19:34
RE: iPXE, iSCSI and int13 - mr_jrt - 2016-03-11, 02:14
RE: iPXE, iSCSI and int13 - mr_jrt - 2016-03-12 00:21
RE: iPXE, iSCSI and int13 - mcb30 - 2016-03-12, 03:17
RE: iPXE, iSCSI and int13 - mr_jrt - 2016-03-12, 13:32
RE: iPXE, iSCSI and int13 - mcb30 - 2016-03-12, 14:02
RE: iPXE, iSCSI and int13 - mr_jrt - 2016-03-12, 15:47
|
User(s) browsing this thread: 1 Guest(s)