Re: failed to set mtrr: invalid argument

2009-05-21 Thread Andriy Gapon
on 20/05/2009 18:56 Robert Noland said the following: On Wed, 2009-05-20 at 17:26 +0200, Paul B. Mahol wrote: On 5/20/09, Robert Noland rnol...@freebsd.org wrote: Yes, if xserver is built with HAL support, I see it linked with libthr. If HAL is disabled, it doesn't appear to be. I'm trying to

Re: failed to set mtrr: invalid argument

2009-05-20 Thread Robert Noland
On Tue, 2009-05-19 at 16:10 -0700, Chris H wrote: So, zapping is off by default now in 1.6.x. If you want it, add Option DontZap off. The cross hatch is also gone, that is what the -retro option is supposed to do. The session leader in a failsafe twm session is the left hand xterm.

Re: failed to set mtrr: invalid argument

2009-05-20 Thread Paul B. Mahol
On 5/20/09, Robert Noland rnol...@freebsd.org wrote: On Tue, 2009-05-19 at 16:10 -0700, Chris H wrote: So, zapping is off by default now in 1.6.x. If you want it, add Option DontZap off. The cross hatch is also gone, that is what the -retro option is supposed to do. The session leader

Re: failed to set mtrr: invalid argument

2009-05-20 Thread Robert Noland
On Wed, 2009-05-20 at 16:16 +0200, Paul B. Mahol wrote: On 5/20/09, Robert Noland rnol...@freebsd.org wrote: On Tue, 2009-05-19 at 16:10 -0700, Chris H wrote: So, zapping is off by default now in 1.6.x. If you want it, add Option DontZap off. The cross hatch is also gone, that is what

Re: failed to set mtrr: invalid argument

2009-05-20 Thread Chris H
Quoting Robert Noland rnol...@freebsd.org: On Tue, 2009-05-19 at 16:10 -0700, Chris H wrote: So, zapping is off by default now in 1.6.x. If you want it, add Option DontZap off. The cross hatch is also gone, that is what the -retro option is supposed to do. The session leader in a

Re: failed to set mtrr: invalid argument

2009-05-20 Thread Robert Noland
On Wed, 2009-05-20 at 17:26 +0200, Paul B. Mahol wrote: On 5/20/09, Robert Noland rnol...@freebsd.org wrote: On Wed, 2009-05-20 at 16:16 +0200, Paul B. Mahol wrote: On 5/20/09, Robert Noland rnol...@freebsd.org wrote: On Tue, 2009-05-19 at 16:10 -0700, Chris H wrote: So, zapping is off

Re: failed to set mtrr: invalid argument

2009-05-20 Thread Chris H
Quoting Robert Noland rnol...@freebsd.org: On Wed, 2009-05-20 at 16:16 +0200, Paul B. Mahol wrote: On 5/20/09, Robert Noland rnol...@freebsd.org wrote: On Tue, 2009-05-19 at 16:10 -0700, Chris H wrote: So, zapping is off by default now in 1.6.x. If you want it, add Option DontZap off.

Re: failed to set mtrr: invalid argument

2009-05-20 Thread Paul B. Mahol
On 5/20/09, Robert Noland rnol...@freebsd.org wrote: On Wed, 2009-05-20 at 16:16 +0200, Paul B. Mahol wrote: On 5/20/09, Robert Noland rnol...@freebsd.org wrote: On Tue, 2009-05-19 at 16:10 -0700, Chris H wrote: So, zapping is off by default now in 1.6.x. If you want it, add Option

Re: failed to set mtrr: invalid argument

2009-05-19 Thread Chris H
Quoting Chris H chr...@1command.com: Quoting Chris H chr...@1command.com: Greetings, I'm unable to get xorg-7.4 to accomodate my Gforce4 MX 440. On 7.1-7.2 releases. I'm currently working (struggling) with it on a 7.1 install/GENERIC with cvsup over the weekend (Sunday), I've seen only a few

Re: failed to set mtrr: invalid argument

2009-05-19 Thread Paul B. Mahol
On 5/19/09, Chris H chr...@1command.com wrote: Quoting Chris H chr...@1command.com: Quoting Chris H chr...@1command.com: Greetings, I'm unable to get xorg-7.4 to accomodate my Gforce4 MX 440. On 7.1-7.2 releases. I'm currently working (struggling) with it on a 7.1 install/GENERIC with

Re: failed to set mtrr: invalid argument

2009-05-19 Thread Dimitry Andric
On 2009-05-19 08:40, Chris H wrote: I see. Well I'm specifically using the nv driver. Here's another attempt to provide the relevant info: I could not find the error message from $subject in these logs. Where is it? :) ___ freebsd-stable@freebsd.org

Re: failed to set mtrr: invalid argument

2009-05-19 Thread Paul B. Mahol
On 5/19/09, Dimitry Andric dimi...@andric.com wrote: On 2009-05-19 08:40, Chris H wrote: I see. Well I'm specifically using the nv driver. Here's another attempt to provide the relevant info: I could not find the error message from $subject in these logs. Where is it? :) In thread subject.

Re: failed to set mtrr: invalid argument

2009-05-19 Thread Chris H
Quoting Dimitry Andric dimi...@andric.com: On 2009-05-19 08:40, Chris H wrote: I see. Well I'm specifically using the nv driver. Here's another attempt to provide the relevant info: I could not find the error message from $subject in these logs. Where is it? :) If I had found it, I would

Re: failed to set mtrr: invalid argument

2009-05-19 Thread Laurent Grangeau
I think I can handle this answer. This is the default behavior of Xorg 7.4. If you want to see the old screen, launch Xorg with the -retro option. The command should be like this : X -config xorg.conf.new -retro If your mouse or your keyboard doesn't seem to work, look if you have enable

Re: failed to set mtrr: invalid argument

2009-05-19 Thread Chris H
Quoting Laurent Grangeau thorz...@gmail.com: I think I can handle this answer. This is the default behavior of Xorg 7.4. If you want to see the old screen, launch Xorg with the -retro option. The command should be like this : X -config xorg.conf.new -retro If your mouse or your keyboard

Re: failed to set mtrr: invalid argument

2009-05-19 Thread Robert Noland
On Tue, 2009-05-19 at 09:57 -0700, Chris H wrote: Quoting Dimitry Andric dimi...@andric.com: On 2009-05-19 08:40, Chris H wrote: I see. Well I'm specifically using the nv driver. Here's another attempt to provide the relevant info: I could not find the error message from $subject in

Re: failed to set mtrr: invalid argument

2009-05-19 Thread Chris H
Hello Robert, and thank you for taking the time to respond. Quoting Robert Noland rnol...@freebsd.org: On Tue, 2009-05-19 at 09:57 -0700, Chris H wrote: Quoting Dimitry Andric dimi...@andric.com: On 2009-05-19 08:40, Chris H wrote: I see. Well I'm specifically using the nv driver. Here's

Re: failed to set mtrr: invalid argument

2009-05-19 Thread Chris H
Quoting Robert Noland rnol...@freebsd.org: On Tue, 2009-05-19 at 11:47 -0700, Chris H wrote: Quoting Chris H chr...@1command.com: Quoting Laurent Grangeau thorz...@gmail.com: I think I can handle this answer. This is the default behavior of Xorg 7.4. If you want to see the old screen,

Re: failed to set mtrr: invalid argument

2009-05-19 Thread Robert Noland
On Tue, 2009-05-19 at 13:14 -0700, Chris H wrote: Hello Robert, and thank you for taking the time to respond. Quoting Robert Noland rnol...@freebsd.org: On Tue, 2009-05-19 at 09:57 -0700, Chris H wrote: Quoting Dimitry Andric dimi...@andric.com: On 2009-05-19 08:40, Chris H wrote:

Re: failed to set mtrr: invalid argument

2009-05-19 Thread Robert Noland
On Tue, 2009-05-19 at 13:52 -0700, Chris H wrote: Quoting Robert Noland rnol...@freebsd.org: On Tue, 2009-05-19 at 11:47 -0700, Chris H wrote: Quoting Chris H chr...@1command.com: Quoting Laurent Grangeau thorz...@gmail.com: I think I can handle this answer. This is the

failed to set mtrr: invalid argument

2009-05-18 Thread Chris H
Greetings, I'm unable to get xorg-7.4 to accomodate my Gforce4 MX 440. On 7.1-7.2 releases. I'm currently working (struggling) with it on a 7.1 install/GENERIC with cvsup over the weekend (Sunday), I've seen only a few discussions regarding this, but no joy. I'm not sure what to post for

Re: failed to set mtrr: invalid argument

2009-05-18 Thread Chris H
Quoting Chris H chr...@1command.com: Greetings, I'm unable to get xorg-7.4 to accomodate my Gforce4 MX 440. On 7.1-7.2 releases. I'm currently working (struggling) with it on a 7.1 install/GENERIC with cvsup over the weekend (Sunday), I've seen only a few discussions regarding this, but no joy.