Date: Mon, 4 Aug 2003 23:53:05 -0500 From: Glenn Johnson <glennpj@charter.net> To: "Alastair G. Hogge" <agh@tpg.com.au> Cc: FreeBSD current users <FreeBSD-current@freebsd.org> Subject: Re: problem with nvidia graphics card and -current Message-ID: <20030805045305.GA1137@gforce.johnson.home> In-Reply-To: <200308051438.05939.agh@tpg.com.au> References: <20030804044856.GA1904@gforce.johnson.home> <20030805041159.GA898@gforce.johnson.home> <20030805003300.I99550@sasami.jurai.net> <200308051438.05939.agh@tpg.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Aug 05, 2003 at 02:38:05PM +1000, Alastair G. Hogge wrote: > On Tuesday, 05 August 2003 14:34, Matthew N. Dodd wrote: > > > On Mon, 4 Aug 2003, Glenn Johnson wrote: > > > > > Question for the developers: Is there someway to avoid having > > > the combination of vesa and nvidia cause a total lockup of the > > > machine? I have a feeling I may not be the last person to try the > > > nvidia driver with vesa enabled, either as a module, or compiled > > > in the kernel. > > > > I'm running a system with the VESA stuff compiled in; the nvidia > > drivers work just fine. > > > > IIRC you're running with ACPI; try not doing that. > > I'm also running a system with the vesa module loaded. I'm also > running ACPI. Hmm, the only other thing I can offer here is that I had the console screen set to "-g 100x37 VESA_800x600". How does that fit into the picture? Perhaps I could have left vesa in but just set the resolution to something else. Perhaps the machine just has quirky hardware. It is a VIA KT-133 chipset, Athlon-tbird processor. -- Glenn Johnson glennpj@charter.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030805045305.GA1137>