VESA mode on VMWare doesn't show a command prompt until you hit ENTER
Project: | JNode Core |
Component: | Code |
Category: | bug report |
Priority: | normal |
Assigned: | Unassigned |
Status: | active |
When I try to boot in VESA mode on VMWare, I get a console that looks like it is not working. The screen looks like the attached image. When I hit ENTER, the VESA console jump scrolls to the end of the buffer and I see a command prompt.
The issue is that the console should come up with the input cursor at the end of the buffer, and I should see the bootstrap messages scrolling to the console ... without me needing to hit ENTER.
This is my original issue description ...
When I try to boot in VESA mode on VMWare, I don't get a working console. Instead, I get a pretty looking screen with the first page full of console messages; see the attached image. When I configure the serial port and boot with kdb, the kernel debug output doesn't contain anything that points to the problem.
Attachment | Size |
---|---|
Screenshot-JNode.png | 35.19 KB |
- Login to post comments
#1
Missing attachment ...
#2
It might be a problem in refreshing the screen.
What happens if you press enter?
#3
Magic! It works. I'll update the title and issue description to say that VESA-mode console needs to do something to cause the screen to refresh.
#4
#5
I tried it in kvm today and with "-vga std" VESA works.
startawt works without the refresh trick (I have to do some more testing but I have the feeling that this is dependent on the kvm version, I tried kvm-83)
On Thinkpad X60 the vesa mode didn't work at all btw as the grub version (0.97 too) does not understand the vbeset command for some reason.
And on another note: the software cursor is broken, too. If you move the cursor to the upper border you get garbage.
#6
Its not working with thinkpad i have tried several option but somehow cant make it working.Any help would be appreciated.I have done google search visited n number of forums but no respite.
#7
what's your hardware ? does it support VESA ?
if you have a stacktrace, it could help