Getting Started, Documentation, Tips & Tricks

How to get 1680x1050 resolution on a Fuel V10?

I am trying to get a resolution of 1680x1050 on my Fuel V10. xsetmon offers this resolution. After selecting it, xsetmon promises it will be available
after reboot. But after an reboot it is still the old low resolution. How to get it right?

_________________
:Fuel: 600 MHz, 2 GB RAM, 72 GB 15k RPM HD
:O2: 180 MHz
you have to start xsetmon as root.

_________________
:Octane2: 2xR12000 400MHz, 4GB RAM, V12 GFX
SGI - the legend will never die!!
After you've loaded the 1680x1050 format and rebooted, what does /usr/gfx/gfxinfo -vv show?

_________________
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************
I have loaded the settings as root and rebooted. /usr/gfx/gfxinfo -vv shows:
Code:
Managed (":0.0") 1280x1024
BUZZ version B.2
PB&J version 1
32MB memory
Banks: 2, CAS latency: 3
Monitor 0 type: VSC 3871
Input Sync: Voltage - Video Level; Source - Internal; Genlocked - False
Channel 0:
Origin = (0,0)
Video Output: 1280 pixels, 1024 lines, 60.00Hz (1280x1024_60)
Video Format Flags:  (none)
Sync Disabled
Using Gamma Map 0
Monitor Type:  VSC-3871
Gain (all color components) - 0.000000 ; range [1,10]

_________________
:Fuel: 600 MHz, 2 GB RAM, 72 GB 15k RPM HD
:O2: 180 MHz
Then the most likely answer is IRIX looked at the DDC info provided by your monitor doesn't consider the timing of the format used as compatible.

The right way to correct the situation is to use the Video Format Compiler (VFC) and build a format that is specific to your monitor.

The shot in the dark fix is to try and fool IRIX by loading the format and not powering up the monitor until *after* IRIX reboots. This method doesn't always work, but even if it does I don't recommend it - if it produces a display the timing inside the format might be off enough to cause damage to your monitor.

_________________
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************
The times when you could damage your monitor with an out-of-spec signal should be long over. It was back in the times when voltages were proportional to the input frequency that a monitor would just fry itself when given a signal with too high a frequency - that was back when a "multisync" CRT was high tech.

Any TFT monitor (but possibly not a separate panel) should know precisely when it can display a signal and when it can't.
@rwengerter - we're you able to get a working 1680x1050 display on your Fuel?

_________________
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************
Unfortunately I was not able to get 1680x1050 resolution on my Fuel V10. The monitor is a 27.5 inch TFT-monitor from
Viewsonic with a native resolution of 1920x1200 pixels.

_________________
:Fuel: 600 MHz, 2 GB RAM, 72 GB 15k RPM HD
:O2: 180 MHz
rwengerter wrote:
Unfortunately I was not able to get 1680x1050 resolution on my Fuel V10. The monitor is a 27.5 inch TFT-monitor from
Viewsonic with a native resolution of 1920x1200 pixels.


If you can get a modeline or (better yet) EDID info specific to your monitor you may be able to create a custom vfo file. Be glad to offer assistance if needed.

_________________
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************