From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <13426df10611191751s22d0f2c3xfbfca49ecdc70d6e@mail.gmail.com> Date: Sun, 19 Nov 2006 18:51:10 -0700 From: "ron minnich" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: [9fans] keyboard problems after aux/vga In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <088f98b6fd3aeadc98eebb6c96f4d8e7@coraid.com> Topicbox-Message-UUID: e20c3a02-ead1-11e9-9d60-3106f5b1d025 On 11/19/06, Tim Wiess wrote: > > vesa is tough. the first thing i would check is if X11 runs in vesa mode > > under linux on this machine. > > > > if vesa memory isn't where the driver expects or is a different size, you are > > likely to overwrite something important. are you trying the lowest vesa resolution? > > 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. ron