Console command inside and outside a virtualbox

[Tsaukpaetra]

(2014-02-14 10:09)robinsmidsrod Wrote:  I've updated the error page at http://ipxe.org/err/2d8c20 with information on how to get the VESA BIOS mode list debug information included when running the console command.

Thank you.
Now, running the command leaves a bunch of Could not get mode ## information, IO error.
I'm assuming this means that... the... graphics card interface is not connected? Weird?

By carefully adjusting the VBE_MODE_END value, I got the output text to be something less than screen-filling, and I can get the debug text:

Code:

Vesafb saved vga mode 0x03
vesafb found vbe version 2.0 with mode list at c000:6d0d

If I limit the apparent list to almost nothing (I set the end value to 0x4110), I get the error: could not configure console: Not enough space
Seeing as that error is different, it brings me to the conclusion that a known suitable list of modes is being generated at least.

Unfortunately, due to this IO error, I can't even really tell what those modes are supposed to be in the first place. They don't seem to be VESA mode numbers in any case.

On another machine, strangely, enabling debug=vesafb actually allows the console command to work! Whereas not including the debug=vesafb makes it not work. I'm not sure what else besides the debugging messages are being enabled with this setting, but whatever it is is actually allowing the console command to actually work!
Too bad though, I don't have a good enough camera to see the debug messages flash by, I'd like to see what else may be going on.

In any case, I just commented out the DBGC statements so nothing gets printed, and it's like debugging isn't on at all!