Re: problem with nvidia graphics card and -current
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 [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: problem with nvidia graphics card and -current
On Sun, Aug 03, 2003 at 11:48:56PM -0500, wrote: > I was setting up a system today with an nvidia Geforce4-MX 440 > graphics card. I am not at the system at the moment but the -current > sources were from about 2:00 PM CDT. I installed the nvidia-driver > port (1.0.4365) trying various combinations of WITH_FREEBSD_AGP, > FORCE_AGP_RATE, and WITH_NVIDIA_HACKS. I get the same result. The > first time an X server is started, everything works fine, including > glx loading. After exiting the X session and shutting down the > server and then at some point later starting the X server again, the > system will freeze. No messages, no panic, nothing. The only thing > to do is hit the reset button. I played with this a bit more tonight. I rebuilt the kernel (fresh cvsup) and the nvidia-driver bits. I even tried loading without glx. I still have the same problem. At this point I do not know if this is a problem with the nvidia-driver port, a problem with -current, or something I am doing wrong. Does anybody have a functioning nvidia card with FreeBSD -current at this time? -- Glenn Johnson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: problem with nvidia graphics card and -current
On Tue, Aug 05, 2003 at 01:28:58PM +1000, Alastair G. Hogge wrote: > On Tuesday, 05 August 2003 13:07, Glenn Johnson wrote: > > > On Sun, Aug 03, 2003 at 11:48:56PM -0500, wrote: > > > > > I was setting up a system today with an nvidia Geforce4-MX 440 > > > graphics card. I am not at the system at the moment but the > > > -current sources were from about 2:00 PM CDT. I installed the > > > nvidia-driver port (1.0.4365) trying various combinations of > > > WITH_FREEBSD_AGP, FORCE_AGP_RATE, and WITH_NVIDIA_HACKS. I > > > get the same result. The first time an X server is started, > > > everything works fine, including glx loading. After exiting the X > > > session and shutting down the server and then at some point later > > > starting the X server again, the system will freeze. No messages, > > > no panic, nothing. The only thing to do is hit the reset button. > > > > I played with this a bit more tonight. I rebuilt the kernel (fresh > > cvsup) and the nvidia-driver bits. I even tried loading without > > glx. I still have the same problem. At this point I do not know > > if this is a problem with the nvidia-driver port, a problem with > > -current, or something I am doing wrong. Does anybody have a > > functioning nvidia card with FreeBSD -current at this time? > > Yes I do. > > I posted to the list a few days with a glx problem. However the > problem was solved when I did an update one day ago. I didn't have to > changed anything either. I didn't know what was wrong for some reason > X would about with sig 10 or 11 when the glx module was loaded. Well, after much hair pulling and trying various troubleshooting steps I had one last idea. I had the vesa kernel module loaded and thought "maybe that is causing the hangup." I disabled the loading of the vesa kernel module in /boot/loader.conf and rebooted. Sure enough, everything worked. I now have the nvidia card working and can proceed with the rest of the setup for this machine. Thanks for your reply stating that it works for you. It gave me the incentive to try "one more time". 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. Thanks. -- Glenn Johnson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: problem with nvidia graphics card and -current
there may have been a problem over the last few days. check with a version of sys_machdep.c from a few weeks ago and the newest one.. (It may have been fixed yesterday) On Mon, 4 Aug 2003, Glenn Johnson wrote: > On Sun, Aug 03, 2003 at 11:48:56PM -0500, wrote: > > > I was setting up a system today with an nvidia Geforce4-MX 440 > > graphics card. I am not at the system at the moment but the -current > > sources were from about 2:00 PM CDT. I installed the nvidia-driver > > port (1.0.4365) trying various combinations of WITH_FREEBSD_AGP, > > FORCE_AGP_RATE, and WITH_NVIDIA_HACKS. I get the same result. The > > first time an X server is started, everything works fine, including > > glx loading. After exiting the X session and shutting down the > > server and then at some point later starting the X server again, the > > system will freeze. No messages, no panic, nothing. The only thing > > to do is hit the reset button. > > I played with this a bit more tonight. I rebuilt the kernel (fresh > cvsup) and the nvidia-driver bits. I even tried loading without glx. > I still have the same problem. At this point I do not know if this is > a problem with the nvidia-driver port, a problem with -current, or > something I am doing wrong. Does anybody have a functioning nvidia card > with FreeBSD -current at this time? > > -- > Glenn Johnson > [EMAIL PROTECTED] > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: problem with nvidia graphics card and -current
On Mon, Aug 04, 2003 at 11:53:05PM -0500, Glenn Johnson wrote: > 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. Well, I can have the vesa kernel module loaded and use standard modes for the console and all is well. However, If I use any of the VESA video modes, the nvidia driver will not work. I can start the X server once, any subsequent attempt to restart the X server will cause the machine to freeze up if any of the VESA modes for the console are loaded. -- Glenn Johnson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: problem with nvidia graphics card and -current
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. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: problem with nvidia graphics card and -current
On Tuesday, 05 August 2003 13:07, Glenn Johnson wrote: > On Sun, Aug 03, 2003 at 11:48:56PM -0500, wrote: > > I was setting up a system today with an nvidia Geforce4-MX 440 > > graphics card. I am not at the system at the moment but the -current > > sources were from about 2:00 PM CDT. I installed the nvidia-driver > > port (1.0.4365) trying various combinations of WITH_FREEBSD_AGP, > > FORCE_AGP_RATE, and WITH_NVIDIA_HACKS. I get the same result. The > > first time an X server is started, everything works fine, including > > glx loading. After exiting the X session and shutting down the > > server and then at some point later starting the X server again, the > > system will freeze. No messages, no panic, nothing. The only thing > > to do is hit the reset button. > > I played with this a bit more tonight. I rebuilt the kernel (fresh > cvsup) and the nvidia-driver bits. I even tried loading without glx. > I still have the same problem. At this point I do not know if this is > a problem with the nvidia-driver port, a problem with -current, or > something I am doing wrong. Does anybody have a functioning nvidia card > with FreeBSD -current at this time? Yes I do. I posted to the list a few days with a glx problem. However the problem was solved when I did an update one day ago. I didn't have to changed anything either. I didn't know what was wrong for some reason X would about with sig 10 or 11 when the glx module was loaded. have you checked out: http://www.soulwax.net/nvidia/faq.shtml They list a whole bunch of things to try. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: problem with nvidia graphics card and -current
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. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
problem with nvidia graphics card and -current
I was setting up a system today with an nvidia Geforce4-MX 440 graphics card. I am not at the system at the moment but the -current sources were from about 2:00 PM CDT. I installed the nvidia-driver port (1.0.4365) trying various combinations of WITH_FREEBSD_AGP, FORCE_AGP_RATE, and WITH_NVIDIA_HACKS. I get the same result. The first time an X server is started, everything works fine, including glx loading. After exiting the X session and shutting down the server and then at some point later starting the X server again, the system will freeze. No messages, no panic, nothing. The only thing to do is hit the reset button. Any ideas? I saw some discussion about kernel changes made for wine and nvidia but I am not sure if that is relevant in my case. Thanks. -- Glenn Johnson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
