From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: Date: Thu, 5 Jan 2006 01:14:59 -0500 From: Russ Cox To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: [9fans] some installation problems (was "panic: vmap") In-Reply-To: <87f034ae0601040900l3e115881l3c39f947d8fdd952@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <87f034ae0601040019x34daf965rcb172ea06e8dfc12@mail.gmail.com> <87f034ae0601040900l3e115881l3c39f947d8fdd952@mail.gmail.com> Topicbox-Message-UUID: d1873570-ead0-11e9-9d60-3106f5b1d025 > It seems the fix that was made that took away the "panic: vmap" error > only applied to the boot disc. Now I get the same result from my > installation: when using VGA (that message) and when using VESA (a > distorted screen). Try typing none at the mouseport prompt and then run 9fs sources pull to get a new kernel. Then you'll have to install it in your 9fat partition= : 9fat: cp /386/9pcf /n/9fat/9pcf The new kernel should both fix the panic: vmap and give you a working cursor. You'll still have to arrange to run echo hwaccel off >/dev/vgactl before running aux/vga, or you will get the (very slow) timeout prints. Those are due to the nvidia driver not knowing how to drive your card, and there is nothing I can do about that. If someone else wants to fiddle with the nvidia driver, have fun. I've reached my lifetime limit for vga hacking. Russ