SaX2 1280x1024@75Hz but Desktop 1152x864@75Hz only
Hi, I've just installed Suse 9.3 Pro on a somewhat old but working Intel PII server with an onboard Cirrus Logic GD5480 graphic chip. The monitor was configured with SaX2 and tested OK with VESA 1280x1024@75Hz and no 3D. However after rebooting and login to KDE or Gnome the desktop screen resolution is found set to the lower 1152x864@75Hz, and there is no higher resolution available to select. I verified again with YaST2 and the monitor should be set 1280x1024@75Hz. Why does this happends and is it possible to extend the desktop resolution? (On another newer PC, the desktop resolution is set 1280x1024@75Hz just like SaX2 configuration). Thanks, Terje J. Hanssen
Terje J. Hanssen wrote:
Hi,
I've just installed Suse 9.3 Pro on a somewhat old but working Intel PII server with an onboard Cirrus Logic GD5480 graphic chip. The monitor was configured with SaX2 and tested OK with VESA 1280x1024@75Hz and no 3D. However after rebooting and login to KDE or Gnome the desktop screen resolution is found set to the lower 1152x864@75Hz, and there is no higher resolution available to select. I verified again with YaST2 and the monitor should be set 1280x1024@75Hz.
Why does this happends and is it possible to extend the desktop resolution? It is probably a limitation of your graphics card. It could also be video memory. Are you running 16 bit? You could try lowering the bit depth if the memory is short. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
On Fri, 2005-06-03 at 21:21 -0500, Joe Morris (NTM) wrote:
Terje J. Hanssen wrote:
Hi,
I've just installed Suse 9.3 Pro on a somewhat old but working Intel PII server with an onboard Cirrus Logic GD5480 graphic chip. The monitor was configured with SaX2 and tested OK with VESA 1280x1024@75Hz and no 3D. However after rebooting and login to KDE or Gnome the desktop screen resolution is found set to the lower 1152x864@75Hz, and there is no higher resolution available to select. I verified again with YaST2 and the monitor should be set 1280x1024@75Hz.
Why does this happends and is it possible to extend the desktop resolution? It is probably a limitation of your graphics card. It could also be video memory. Are you running 16 bit? You could try lowering the bit depth if the memory is short.
Also try running hwinfo --framebuffer to see which resolutions are supported by the graphics card. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
On Saturday 04 June 2005 04.28, Ken Schneider wrote:
On Fri, 2005-06-03 at 21:21 -0500, Joe Morris (NTM) wrote:
Terje J. Hanssen wrote:
Hi,
I've just installed Suse 9.3 Pro on a somewhat old but working Intel PII server with an onboard Cirrus Logic GD5480 graphic chip. The monitor was configured with SaX2 and tested OK with VESA 1280x1024@75Hz and no 3D. However after rebooting and login to KDE or Gnome the desktop screen resolution is found set to the lower 1152x864@75Hz, and there is no higher resolution available to select. I verified again with YaST2 and the monitor should be set 1280x1024@75Hz.
Why does this happends and is it possible to extend the desktop resolution?
It is probably a limitation of your graphics card. It could also be video memory. Are you running 16 bit? You could try lowering the bit depth if the memory is short.
Also try running hwinfo --framebuffer to see which resolutions are supported by the graphics card.
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
"The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
That doesn't give the correct resolution for X It only gives the resolutions available in framebuffer mode. Take my Matrox G400 DH for instance, I run it at 2x (dual head) 1280x1024 16 bit, but running hwinfo --framebuffer gives: 02: None 00.0: 11001 VESA Framebuffer [Created at bios.521] Unique ID: rdCR.xpCz25nMUV0 Hardware Class: framebuffer Model: "Matrox G400" Vendor: "Matrox" Device: "Matrox G400" SubVendor: "Matrox Graphics Inc." SubDevice: Revision: "00" Memory Size: 32 MB Memory Range: 0xd8000000-0xd9ffffff (rw) Mode 0x0300: 640x400 (+640), 8 bits Mode 0x0301: 640x480 (+640), 8 bits Mode 0x0302: 800x600 (+100), 4 bits Mode 0x0303: 800x600 (+800), 8 bits Mode 0x0310: 640x480 (+1280), 15 bits Mode 0x0311: 640x480 (+1280), 16 bits Mode 0x0312: 640x480 (+2560), 24 bits Mode 0x0313: 800x600 (+1600), 15 bits Mode 0x0314: 800x600 (+1600), 16 bits Mode 0x0315: 800x600 (+3200), 24 bits Config Status: cfg=no, avail=yes, need=no, active=unknown It doesnt list any of the resolutions i use in X. -- /Rikard " Sharing knowledge is the most fundamental act of friendship. Because it is a way you can give something without loosing something." -R. Stallman --------------------------------------------------------------- Rikard Johnels email : rikjoh@norweb.se Mob : +46 763 19 76 25 PGP : 0x461CEE56 ---------------------------------------------------------------
Terje J. Hanssen wrote:
Hi,
I've just installed Suse 9.3 Pro on a somewhat old but working Intel PII server with an onboard Cirrus Logic GD5480 graphic chip. The monitor was configured with SaX2 and tested OK with VESA 1280x1024@75Hz and no 3D. However after rebooting and login to KDE or Gnome the desktop screen resolution is found set to the lower 1152x864@75Hz, and there is no higher resolution available to select. I verified again with YaST2 and the monitor should be set 1280x1024@75Hz.
Why does this happends and is it possible to extend the desktop resolution?
(On another newer PC, the desktop resolution is set 1280x1024@75Hz just like SaX2 configuration).
Thanks, Terje J. Hanssen
Check /var/log/Xorg.0.log, that will tell you what resolutions it's tried and can't do. I've never been able to get a 16M card to do more than 1024x768 properly. That card was supplied in 4, 8 or 16M versions, my guess is you have the 16M version. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM Mainframes and Sun Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks
Sid Boyce wrote:
Check /var/log/Xorg.0.log, that will tell you what resolutions it's tried and can't do. I've never been able to get a 16M card to do more than 1024x768 properly. That card was supplied in 4, 8 or 16M versions, my guess is you have the 16M version.
Maybe CL cards are different, but I have 4M Tseng cards running up to 1600x1200 16 bit, and 16M G400 cards running up to 2048x1536 16 bit. Other chips ought to be able to do as well. -- "Love does not demand its own way." 1 Corinthians 13:5 Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://members.ij.net/mrmazda/
participants (6)
-
Felix Miata -
Joe Morris (NTM) -
Ken Schneider -
Rikard Johnels -
Sid Boyce -
Terje J. Hanssen