RE: my nvidia 3D acceleration seems to have conked out..... (problem now FIXED)
----------------------------------------
> Date: Sun, 25 May 2008 17:20:30 -0400
> From: rjisaac@gmail.com
> To: debian-amd64@lists.debian.org
> Subject: Re: my nvidia 3D acceleration seems to have conked out..... (problem now FIXED)
>
> Just a shot in the dark, change:
>
>> SubSection "Display"
>> Modes "1280x768"
>> EndSubSection
> to:
>> SubSection "Display"
>> Modes "1360x768" "1280x768"
Thanks, I tried this.
But it still dropped the 1360 x 768 option and went for the 1280x768 one instead:
Here is part of the Xorg output:
(--) NVIDIA(0): CRT-1: 400.0 MHz maximum pixel clock
(II) NVIDIA(0): Assigned Display Device: CRT-1
(WW) NVIDIA(0): No valid modes for "1360 x 768"; removing.
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0): "1280x768"
(II) NVIDIA(0): Virtual screen size determined to be 1280 x 768
(WW) NVIDIA(0): Unable to get display device CRT-1's EDID; cannot compute DPI
(WW) NVIDIA(0): from CRT-1's EDID.
(==) NVIDIA(0): DPI set to (75, 75); computed from built-in default
(==) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0xdfffe000 - 0xdfffe0ff (0x100) MX[B]
[5] -1 0 0xdffff000 - 0xdffff0ff (0x100) MX[B]
[6] -1 0 0xd0000000 - 0xcfffffff (0x0) MX[B]O
[7] -1 0 0xda000000 - 0xdbffffff (0x2000000) MX[B](B)
[8] -1 0 0xa0000000 - 0xbfffffff (0x20000000) MX[B](B)
[9] -1 0 0xdc000000 - 0xdcffffff (0x1000000) MX[B](B)
[10] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B]
[11] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B]
[12] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B]
[13] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[14] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[15] -1 0 0x0000f000 - 0x0000f0ff (0x100) IX[B]
[16] -1 0 0x0000f600 - 0x0000f61f (0x20) IX[B]
[17] -1 0 0x0000f700 - 0x0000f71f (0x20) IX[B]
[18] -1 0 0x0000f800 - 0x0000f81f (0x20) IX[B]
[19] -1 0 0x0000f900 - 0x0000f91f (0x20) IX[B]
[20] -1 0 0x0000fa00 - 0x0000fa0f (0x10) IX[B]
[21] -1 0 0x0000f400 - 0x0000f4ff (0x100) IX[B]
[22] -1 0 0x0000fb00 - 0x0000fb0f (0x10) IX[B]
[23] -1 0 0x0000fc00 - 0x0000fc03 (0x4) IX[B]
[24] -1 0 0x0000fd00 - 0x0000fd07 (0x8) IX[B]
[25] -1 0 0x0000fe00 - 0x0000fe03 (0x4) IX[B]
[26] -1 0 0x0000ff00 - 0x0000ff07 (0x8) IX[B]
[27] -1 0 0x0000f200 - 0x0000f2ff (0x100) IX[B]
[28] -1 0 0x0000ef00 - 0x0000ef7f (0x80) IX[B](B)
[29] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B]
[30] 0 0 0x000003c0 - 0x000003df (0x20) IS[B]
(II) NVIDIA(0): Initialized GPU GART.
(II) NVIDIA(0): Setting mode "1280x768"
(II) Loading extension NV-GLX
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(**) Option "dpms"
(**) NVIDIA(0): DPMS enabled
(II) Loading extension NV-CONTROL
(==) RandR enabled
(II) Setting vga for screen 0.
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension XAccessControlExtension
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(II) Initializing extension GLX
(**) Option "CoreKeyboard"
(**) Generic Keyboard: always reports core events
(**) Option "Protocol" "standard"
(**) Generic Keyboard: Protocol: standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xorg"
(**) Generic Keyboard: XkbRules: "xorg"
(**) Option "XkbModel" "pc105"
(**) Generic Keyboard: XkbModel: "pc105"
(**) Option "XkbLayout" "gb"
(**) Generic Keyboard: XkbLayout: "gb"
(**) Option "CustomKeycodes" "off"
(**) Generic Keyboard: CustomKeycodes disabled
(**) Option "Protocol" "ImPS/2"
(**) Configured Mouse: Device: "/dev/input/mice"
(**) Configured Mouse: Protocol: "ImPS/2"
>> EndSubSection
>
> Also it _isn't_ a good idea to punch in random HorizSync and
> VertRefresh rates as wrong values will kill a monitor eventually. I'd
> put a call into the manufacturer's support line to ask for the correct
> values, they should be able to do that much for a paying customer.
I have found it hard to track down these numbers from some manufacturers......
Are these numbers as important with LCD machines as with CRT's in terms of damage to the machine if they are wrong. Someone else on the list here said that the horizontal and vertical refresh rates didn't apply or matter so much for LCDs as for CRTs....
Yet my old 15 inch LCD monitor did specify the resolution (1024 x 768)and horizontal and vertical refresh rates and I use them in xorg.conf to good effect.
I got the HW191 D monitor at work to finally run at its full resolution of 1440 x 900 the other day. Now I am worried that the horizontal and vertical refresh rates might be a bit off and I could be damaging the monitor.
I will keep at it.
Regards
MF
>
>
> --
> To UNSUBSCRIBE, email to debian-amd64-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
_________________________________________________________________
http://clk.atdmt.com/UKM/go/msnnkmgl0010000007ukm/direct/01/
Reply to: