/proc/kcore - why is BIOS not at 0xF0000?

From: Anthony Hay (ahay_at_centennial.co.uk)
Date: 07/30/03

  • Next message: Ben Hall: "Customizing default RH (Gnome) desktop" 
    To: <redhat-list@redhat.com>
Date: Wed, 30 Jul 2003 16:16:10 +0100

    We just installed Red Hat 9 on a Compaq Evo D510 SFF. A tool we use that
    reads DMI data from the IBMPC BIOS failed. We found the BIOS is not
    where we expected it at offset 0xF0000 in /proc/kcore, but at offset
    0xF3000 instead. I thought /proc/kcore was a straight-forward map of
    physical memory. Why the 0x3000 byte offset? Can anyone suggest a
    reliable way to locate the BIOS in /proc/kcore? 

    -- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
  • Next message: Ben Hall: "Customizing default RH (Gnome) desktop"

    Relevant Pages

    • Re: Setting The System Clock [Linux]
      ... the existing timezone files for your geographic locale should ... and change your system offset for you. ... will only cause the planned shift in the timezone file to become an ... And if you save to the bios while you are offset wrongly from UTC ...
      (comp.os.linux.misc)
    • Re: Setting The System Clock [Linux]
      ... the existing timezone files for your geographic locale should ... and change your system offset for you. ... will only cause the planned shift in the timezone file to become an ... And if you save to the bios while you are offset wrongly from UTC ...
      (comp.unix.questions)
    • Re: Race betwen the NMI handler and the RTC clock in practially all kernels
      ... >> information about how to boot, and this caused the BIOS to lock up. ... Normally the offset of the CMOS RAM is left an an unused ...
      (Linux-Kernel)
    • Re: Dont understannd MBR-Boot-Code
      ... >> Why does the Processor tranfere 485 Bytes from an area ... >> Bytes are loaded from BIOS into RAM) to position 0x0000:0x061B (Offset ...
      (alt.lang.asm)