OSDev.org

I disagree with the term "it works perfectly". The first set, specifically:

Places the value of 0xB8000 at offset [vmem] within your binary file.
Then when you do:

The processor does:

However, DS may not be where you think it is.

Now, the reason why you think

works perfectly is because the code is actually using a word sized memory position, somewhere in DS:, probably not where you think vmem is, even though the code looks correct.

Without looking any further, I would almost guaranty that you do not have your segments/selectors set up correctly. i.e.: DS doesn't pointer where you think it does at the start of your C code.

Compile it as is, but place

at the beginning. Then load it into the Bochs Debugger and hit 'c'ontinue. The code will run until it hits that instruction. Then you can see what the DS, ES, CS, etc. segment/selectors are.

If you don't use Bochs, make your emulator of choice crash or have an infinite loop, then stop the emulator. The emulator should print out the segment register values at end of emulation.

Anyway, some how find out what these values are and you will find out they are not what you think they should be.

Ben

I set the DS register to 0x10 which is data segment in my GDT.
Maybe it is the problem in my GDT?
I've just debugged my code and all segment registers were 0x10(except cs, it was 0x08).

Those are just selectors, to select an entry in the GDT. You need to check your GDT *and* check the "origin" or starting offset that GCC is placing on your binary file. I use PE files so that the starting address is really easy to find.

Ben