NVIDIA Quadro FX 3450: 1920x1200 ???
I recently acquired an hp xw9300, dual opteron workstation, including
the subject video card. Additionally, after setting that up with a crt
at 1280x1024, I acquired an hp l2335, wide screen lcd, capable of
1920x1200 resolution -- but, my problem is displaying at that
resolution.
OSD on the lcd shows 1920x1200 ; but, kde control center / peripherals /
display shows only 1280x1024 ;
I will gladly supply ALL information needed to resolve this issue --
PLEASE, ASK. If I need to open a bug on this, please suggest that.
I am not certain what information is required. I have googled, and
searched debian-{kde,user,x} archives -- perhaps, I do not know the best
search terms? For lack of else, please review the following
information:
# apt-cache policy xserver-xorg-video-nv
xserver-xorg-video-nv:
Installed: 1:1.0.1.5-2
Candidate: 1:1.0.1.5-2
Version table:
*** 1:1.0.1.5-2 0
700 ftp://mirrors.kernel.org etch/main Packages
700 ftp://mirrors.kernel.org testing/main Packages
500 ftp://mirrors.kernel.org unstable/main Packages
100 /var/lib/dpkg/status
Even though the card has 256 MB memory, I can only display at 1280x1024
;
# sudo /usr/sbin/ddcprobe
vbe: VESA 3.0 detected.
oem: NVIDIA
vendor: NVIDIA Corporation
product: nv41 Board - q317_3 Chip Rev
memory: 262144kb
mode: 640x400x256
mode: 640x480x256
mode: 800x600x16
mode: 800x600x256
mode: 1024x768x16
mode: 1024x768x256
mode: 1280x1024x16
mode: 1280x1024x256
mode: 320x200x64k
mode: 320x200x16m
mode: 640x480x64k
mode: 640x480x16m
mode: 800x600x64k
mode: 800x600x16m
mode: 1024x768x64k
mode: 1024x768x16m
mode: 1280x1024x64k
mode: 1280x1024x16m
edid:
edid: 1 3
id: 2614
eisa: HWP2614
serial: 01010101
manufacture: 14 2006
input: separate sync, composite sync, sync on green, analog signal.
screensize: 50 31
gamma: 2.20
dpms: RGB, active off, suspend, standby
timing: [EMAIL PROTECTED] Hz (VGA 640x400, IBM)
timing: [EMAIL PROTECTED] Hz (VGA)
timing: [EMAIL PROTECTED] Hz (VESA)
timing: [EMAIL PROTECTED] Hz (VESA)
timing: [EMAIL PROTECTED] Hz (VESA)
timing: [EMAIL PROTECTED] Hz (VESA)
timing: [EMAIL PROTECTED] Hz (Mac II)
timing: [EMAIL PROTECTED] Hz Interlaced (8514A)
timing: [EMAIL PROTECTED] Hz (VESA)
timing: [EMAIL PROTECTED] Hz (VESA)
ctiming: [EMAIL PROTECTED]
ctiming: [EMAIL PROTECTED]
ctiming: [EMAIL PROTECTED]
ctiming: [EMAIL PROTECTED]
ctiming: [EMAIL PROTECTED]
ctiming: [EMAIL PROTECTED]
ctiming: [EMAIL PROTECTED]
ctiming: [EMAIL PROTECTED]
dtiming: [EMAIL PROTECTED]
monitorrange: 30-94, 48-85
monitorname: hp L2335
Selected snippets of /var/log/Xorg.0.log:
(II) VESA(0): Supported VESA Video Modes:
(II) VESA(0): [EMAIL PROTECTED]
(II) VESA(0): [EMAIL PROTECTED]
(II) VESA(0): [EMAIL PROTECTED]
(II) VESA(0): [EMAIL PROTECTED]
(II) VESA(0): [EMAIL PROTECTED]
(II) VESA(0): [EMAIL PROTECTED]
(II) VESA(0): [EMAIL PROTECTED]
(II) VESA(0): [EMAIL PROTECTED]
(II) VESA(0): [EMAIL PROTECTED]
(II) VESA(0): [EMAIL PROTECTED]
(II) VESA(0): [EMAIL PROTECTED]
(II) VESA(0): Manufacturer's mask: 0
(II) VESA(0): Supported Future Video Modes:
(II) VESA(0): #0: hsize: 1024 vsize 768 refresh: 85 vid: 22881
(II) VESA(0): #1: hsize: 1280 vsize 960 refresh: 60 vid: 16513
(II) VESA(0): #2: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
(II) VESA(0): #3: hsize: 1280 vsize 1024 refresh: 85 vid: 39297
(II) VESA(0): #4: hsize: 1600 vsize 1200 refresh: 60 vid: 16553
(II) VESA(0): #5: hsize: 1600 vsize 1200 refresh: 75 vid: 20393
(II) VESA(0): #6: hsize: 1920 vsize 1080 refresh: 60 vid: 49361
(II) VESA(0): #7: hsize: 1920 vsize 1200 refresh: 60 vid: 209
(II) VESA(0): Supported additional Video Mode:
(II) VESA(0): clock: 193.2 MHz Image Size: 495 x 310 mm
(II) VESA(0): h_active: 1920 h_sync: 2048 h_sync_end 2256 h_blank_end
2592 h_border: 0
(II) VESA(0): Total Memory: 4096 64KB banks (262144kB)
(WW) VESA(0): config file hsync range 30-107kHz not within DDC hsync ranges.
(II) VESA(0): Generic Monitor: Using hsync range of 30.00-107.00 kHz
(II) VESA(0): Generic Monitor: Using vrefresh value of 60.00 Hz
(II) VESA(0): Not using mode 1920x1200 (no mode of this name)
(II) VESA(0): Not using mode 1600x1200 (no mode of this name)
(II) VESA(0): Not using built-in mode 2048x1536 (width too large for
virtual size)
(--) VESA(0): Virtual size is 1280x1024 (pitch 1280)
(**) VESA(0): *Built-in mode 1280x1024
(**) VESA(0): *Built-in mode 1024x768
(**) VESA(0): *Built-in mode 800x600
(**) VESA(0): Built-in mode 640x480
--
Best Regards,
mds
mds resource
877.596.8237
-
Dare to fix things before they break . . .
-
Our capacity
Re: ~/.Xdefaults not working ???
Also sprach Brian Kimball (Tue 05 Aug 02003 at 10:07:44AM -0700): Michael D. Schleif wrote: *background: white *foreground: black When I open mutt it is white on black. Mutt is not an X program, it knows nothing about X resources. see section 3.7 of /usr/share/doc/mutt/manual.txt.gz for instructions on setting mutt's colors. Yes, I know this. I have gone to great pains to setup mutt so that it looks identical, regardless how I access it. I can goto a PC and use putty, or ssh into it from another Linux box, c. Initially, I used rxvt to access mutt from the box on which it resides, and had _no_ problems. However, recently I wanted to use a mouse to scroll down long messages, and some kind soul suggested that rxvt wouldn't allow this, but, xterm can do this with this: mutt.vt100.translations: #override \n\ NoneBtn4Down: string() \n\ NoneBtn5Down: string() \n Although I have some problems with that, the most difficult issue is how to get that, and other things like foreground and background color, to behave as I expect. Here are ~/.muttrc color commands: # grep ^color ~/.muttrc | sort color attachment bluedefault color bodybrightblue default (https?|ftp)://[\-\.\,=/%~_:?\#a-zA-Z0-9+]+ color bodybrightblue default [EMAIL PROTECTED] color boldbrightdefault default color hdrdefault bluedefault color header brightblue default ^(From|To|Subject): color indicator brightyellowblack color markers brightred default color message default default color normal default default color quoted default default color search brightyellowcyan color signature red default color status brightyellowblue color tilde bluedefault color treebrightred default color underline default default Only when I do this, is change affected: xrdb -load ~/.Xresources Then, XTerm (Unicode) is white on black (not that I want this effect), and mutt is black on white (which I _do_ want). I did not witness this behavior with the commands and .Xresources you provided, although I am running unstable which has different versions of all of the programs involved. Obviously, I cannot account for your experience; but, my last post describes behaviour common to two (2) different boxen ; Can I safely remove kde from the root-cause analysis? How? Are there other resources that can better facilitate a solution to my problems? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- pgphoWyBhnb20.pgp Description: PGP signature
Re: ~/.Xdefaults not working ???
Also sprach Brian Kimball (Tue 05 Aug 02003 at 04:31:21PM -0700): Michael D. Schleif wrote: Here are ~/.muttrc color commands: # grep ^color ~/.muttrc | sort color attachment bluedefault ^^^ As a quick fix, try setting the background color explicitly. Also, the default background is black in mutt. Mutt apparently does not inherit the terminal's background color as its default background color. # mutt -v Mutt 1.5.4i (2003-03-19) /usr/share/doc/mutt/manual.txt.gz says this: If your terminal supports it, the special keyword default can be used as a transparent color. How is it that you insist that ``default background is black in mutt? Since I require special locale settings, c., I use a wrapper script to call mutt, like this: ## rxvt -font 9x15 -e /usr/bin/mutt xterm -name mutt -e /usr/bin/mutt Can I safely remove kde from the root-cause analysis? How? If you suspect kde is the cause, debug it under a different, simpler, window manager. I prefer twm; it's about as simple as it gets. snip / You make several interesting suggestions that I will try soon. Thank you. -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- pgp8JKzG8aj4q.pgp Description: PGP signature
konqueror: open http://sample.txt without kwrite ???
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Since I upgraded to kde3, when I try to browse to a document that ends with *.txt, I always get this: Open 'http://helices...ume/mds_resume.txt' using 'KWrite'? [Save As] [Open] [Cancel] All I want to do is view an ASCII text file in konqueror ; What do you think? - -- Best Regards, mds mds resource 877.596.8237 - - Dare to fix things before they break . . . - - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . - -- -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/LwdwLUOEaCtUQpwRAtLbAJ4vsiLANOjevc1cXq5Std5aX9tWsACfWi3W RAPJncgA1mT5XZmYgYkUtw4= =PUa3 -END PGP SIGNATURE-
Re: ~/.Xdefaults not working ???
Also sprach Michael D. Schleif (Sun 03 Aug 02003 at 09:00:16PM -0500): # ls -al ~/.Xdefaults -rw---1 mds mds 730 Jul 23 11:53 /home/mds/.Xdefaults # cat ~/.Xdefaults *charClass:33:48,37:48,45-47:48,64:48 xterm*font:9x15 *background: white *foreground: black *scrollKey:true *scrollTtyOutput: false Scrollbar.JumpCursor: true *visualBell: true XTerm*reverseWrap: true XTerm*saveLines: XTerm*scrollBar: true XTerm.VT100.titeInhibit: true XTerm.VT100*dynamicColors: on mutt.vt100.translations: #override \n\ NoneBtn4Down: string() \n\ NoneBtn5Down: string() \n mutt*font: 9x15 mutt*geometry: 150x65+50+50 mutt*scrollBar:false ~/.Xdefaults is *NOT* used on my woody/kde3 boxen, unless I invoke it manually: xrdb -load ~/.Xdefaults What am I missing? Is there some other, kde-way to do this? What do you think? This is a really annoying problem, and neither debian-user nor debian-kde have responded with any ideas. What other mailing list maybe able to assist me with this? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- pgp3AlVkDDNs7.pgp Description: PGP signature
Re: konqueror: open http://sample.txt without kwrite ???
Also sprach Eric Christopherson (Mon 04 Aug 02003 at 08:47:37PM -0500): On Mon, Aug 04, 2003 at 08:25:04PM -0500, Michael D. Schleif wrote: Since I upgraded to kde3, when I try to browse to a document that ends with *.txt, I always get this: Open 'http://helices...ume/mds_resume.txt' using 'KWrite'? [Save As] [Open] [Cancel] All I want to do is view an ASCII text file in konqueror ; What do you think? You need to go into your file associations. For example, go to Control Center KDE Components File Associations (although this might be different depending on which specific version of KDE 3 you are using). Then hit the + sign next to 'text' to expand the list of text file types. Under Left Click Action choose Show file in embedded viewer. Eureka! As slick as that is, could it be any less intuitive? And, is this default action reasonable? Anyway, thank you . . . -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- pgp2hDiVBSBzr.pgp Description: PGP signature
~/.Xdefaults not working ???
# ls -al ~/.Xdefaults -rw---1 mds mds 730 Jul 23 11:53 /home/mds/.Xdefaults # cat ~/.Xdefaults *charClass:33:48,37:48,45-47:48,64:48 xterm*font:9x15 *background: white *foreground: black *scrollKey:true *scrollTtyOutput: false Scrollbar.JumpCursor: true *visualBell: true XTerm*reverseWrap: true XTerm*saveLines: XTerm*scrollBar: true XTerm.VT100.titeInhibit: true XTerm.VT100*dynamicColors: on mutt.vt100.translations: #override \n\ NoneBtn4Down: string() \n\ NoneBtn5Down: string() \n mutt*font: 9x15 mutt*geometry: 150x65+50+50 mutt*scrollBar:false ~/.Xdefaults is *NOT* used on my woody/kde3 boxen, unless I invoke it manually: xrdb -load ~/.Xdefaults What am I missing? Is there some other, kde-way to do this? What do you think? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- pgpsJqNaySQqN.pgp Description: PGP signature
