Mark Vojkovich wrote:
On Wed, 16 Jul 2003, Christian Convey wrote:
And for the framebuffer-restoration issue, do you think it's telling
that I get this problem with the nv driver but not with the vesa
driver? I.e., does that point to a possible problem in the nv driver's
code that we should
On Wed, Jul 16, 2003 at 11:16:46AM -0700, Mark Vojkovich wrote:
On Wed, 16 Jul 2003, Christian Convey wrote:
Problem 1: When I first ran make install, there was some hp keyboard
config thing that was a file, where the installer wanted it to be a
directory. I renamed that file from hp to
ideas you have. I really appreciate it.
- Christian
Subject: Re: [XFree86] Odd problem with terminals
Date: Sun, 13 Jul 2003 11:55:15 -0700 (PDT)
From: Mark Vojkovich [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
On Sun, 13 Jul 2003, Christian Convey wrote:
Hi guys
On Wednesday, July 16, 2003 10:05 am, Christian Convey wrote:
Also, I stopped using xfs, based on a recommendation from Andy Goth,
just to take one more potential problem out of the situation. I now
explicitely use font paths, and I verified they work ok before I started
installing the new
Andy Goth wrote:
On Wednesday, July 16, 2003 10:05 am, Christian Convey wrote:
Also, I stopped using xfs, based on a recommendation from Andy Goth,
just to take one more potential problem out of the situation. I now
explicitely use font paths, and I verified they work ok before I started
On Wed, 16 Jul 2003, Christian Convey wrote:
Hi Mark,
OK, I build XFree86 from CVS (pulled this morning). The build itself
went cleanly, but I had several problems.
Also, I stopped using xfs, based on a recommendation from Andy Goth,
just to take one more potential problem out of the
Mark Vojkovich wrote:
On Wed, 16 Jul 2003, Christian Convey wrote:
IIRC, however, the main reason you had me pull a new version of XF86 from CVS was to see if it fixed the problem where on my virtual consoles, the last half of the last line is below the bottom of the screen. Unfortunately, I do
On Wed, 16 Jul 2003, Christian Convey wrote:
Mark Vojkovich wrote:
On Wed, 16 Jul 2003, Christian Convey wrote:
IIRC, however, the main reason you had me pull a new version of XF86 from CVS was
to see if it fixed the problem where on my virtual consoles, the last half of the
last
Thanks for the info. Comments below...
Mark Vojkovich wrote:
[snip]
I would normally suggest trying NVIDIA's binary Linux drivers, but
it is my understanding that the last NVIDIA binary Linux driver release
(4363) didn't support GeForceFX laptops but the next release will,
though it has not
On Wed, 16 Jul 2003, Christian Convey wrote:
And for the framebuffer-restoration issue, do you think it's telling
that I get this problem with the nv driver but not with the vesa
driver? I.e., does that point to a possible problem in the nv driver's
code that we should look at?
I
On Tuesday, July 15, 2003 4:30 am, Christian Convey wrote:
What's the best way - just send you XFree86.0.log file resulting from a
vesa run of XF86?
That'll do. I don't care if it's a crash or not. I just want to see the mode
list (plus the rest of the file, if it's convenient).
--
Andy
with that name.
Thanks for any ideas you have. I really appreciate it.
- Christian
Subject: Re: [XFree86] Odd problem with terminals
Date: Sun, 13 Jul 2003 11:55:15 -0700 (PDT)
From: Mark Vojkovich [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
On Sun, 13 Jul 2003, Christian Convey
--ModeLine defined with that name.
Thanks for any ideas you have. I really appreciate it.
- Christian
Subject: Re: [XFree86] Odd problem with terminals
Date: Sun, 13 Jul 2003 11:55:15 -0700 (PDT)
From: Mark Vojkovich [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
On Sun, 13
understand why I got the error I got:
(II) VESA(0): Not using mode 1440x900 (no mode of this name)
because in my config file I do seem to have a Monitor--ModeLine defined with that
name.
Thanks for any ideas you have. I really appreciate it.
- Christian
Subject: Re: [XFree86] Odd
: [XFree86] Odd problem with terminals
Date: Sun, 13 Jul 2003 11:55:15 -0700 (PDT)
From: Mark Vojkovich [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
On Sun, 13 Jul 2003, Christian Convey wrote:
Hi guys,
I just installed Mandrake 9.1 on a new Toshiba P25 laptop (1440x900
)
because in my config file I do seem to have a Monitor--ModeLine defined with
that name.
Thanks for any ideas you have. I really appreciate it.
- Christian
Subject: Re: [XFree86] Odd problem with terminals
Date: Sun, 13 Jul 2003 11:55:15 -0700 (PDT)
From: Mark Vojkovich [EMAIL
On Monday, July 14, 2003 6:31 pm, Christian Convey wrote:
With files this time :/
---//--- XFree86.0.log:
(II) LoadModule: nv
---//--- XF86Config:
Section Device
Identifier device1
#Driver nv
Driver vesa
Option DPMS
Option FlatPanel
Option CrtcNumber 1
EndSection
---//---
Hi guys,
I just installed Mandrake 9.1 on a new Toshiba P25 laptop (1440x900
screen resolution).
With some generous help, I got the regular X server behaving perfectly:
My real and virtual desktops are both 1440x900, and it looks great.
However, when I hit ctrl+alt+F1, to go to the console
On Sun, 13 Jul 2003, Christian Convey wrote:
Hi guys,
I just installed Mandrake 9.1 on a new Toshiba P25 laptop (1440x900
screen resolution).
With some generous help, I got the regular X server behaving perfectly:
My real and virtual desktops are both 1440x900, and it looks great.
1440x900 (no mode of this name)
because in my config file I do seem to have a Monitor--ModeLine defined with that
name.
Thanks for any ideas you have. I really appreciate it.
- Christian
Subject: Re: [XFree86] Odd problem with terminals
Date: Sun, 13 Jul 2003 11:55:15 -0700 (PDT
On Sunday, July 13, 2003 8:34 pm, Christian Convey wrote:
(II) VESA(0): Not using mode 1440x900 (no mode of this name)
because in my config file I do seem to have a Monitor--ModeLine defined
with that name.
vesa works by calling your BIOS to set modes. ModeLines have no effect
(right?).
21 matches
Mail list logo