From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <16f01c4117dabde9f35a84bafd15016b@akira.nop.cx>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] keyboard problems after aux/vga
From: Tim Wiess <tim@nop.cx>
Date: Sun, 19 Nov 2006 19:10:33 -0800
In-Reply-To: <13426df10611191751s22d0f2c3xfbfca49ecdc70d6e@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: e2119cea-ead1-11e9-9d60-3106f5b1d025

>>     i've tried a variety of resolutions with the same results.
>>     i'll try X/vesa and see what happens....
>
> One thing that is very useful when debugging problems with vga etc. is
> to have a serial console. Any chance you can set this up?
>
> we hit this all the time with linuxbios; at some point, serial console
> will save your life.

    yeah, i did set that up recently. interesting thing is that input is also
    lost on the console when i start vga.

    X/vesa does indeed work on this machine. so i guess i'll have to
    start looking at the vesa specs.

    tim