SGI: Hardware

Wide Screen (16:9, etc) resolution - Page 1

Do SGI's support wide screen format? I'm thinking about a wide screen LCD and wondering if it would be supported on either my O2, or Octane.... I'm really considering it for the O2.

Any help would be appreciated.

Thanks :D
o2 does /w flat panel adapter option + 1600sw monitor. The resolution is 1600x1024. I don't think you can get 16:9 proportions via vga on the o2. You should be able to find the fpa and a 1600sw on ebay for fairly cheap - $200 max, but if you have a good eye you can get them for less.
Is it possible to go from 1600sw card to a standard monitor either VGA of DVI ? I think I already have the card for the 1600sw but I would prefer to use a 24inch dell flat screen.

miunk wrote: o2 does /w flat panel adapter option + 1600sw monitor. The resolution is 1600x1024. I don't think you can get 16:9 proportions via vga on the o2. You should be able to find the fpa and a 1600sw on ebay for fairly cheap - $200 max, but if you have a good eye you can get them for less.
You would be better off attaching an Octane to wide display; the O2 really only supports the 1600sw via widescreen. There is no adapter on the market (to my knowledge) that would convert the FPA's LVDS output to a DVI output (though the Multilink goes the other way, allowing the LVDS 1600sw to attach to a DVI graphics card).

A V10/V12 Octane would have no trouble connecting to a 24" Dell TFT.
Twitter: @neko_no_ko
IRIX Release 4.0.5 IP12 Version 06151813 System V
Copyright 1987-1992 Silicon Graphics, Inc.
All Rights Reserved.
nekonoko wrote: A V10/V12 Octane would have no trouble connecting to a 24" Dell TFT.


I'm using a Dell 24" LCD with a V8 equipped Octane at 1920x1200 - so a V8 could go on that list as well.
recondas wrote:
nekonoko wrote: A V10/V12 Octane would have no trouble connecting to a 24" Dell TFT.


I'm using a Dell 24" LCD with a V8 equipped Octane at 1920x1200 - so a V8 could go on that list as well.


I don't recommend the V6/V8 for TFT due to the timing bug, but they do "work" in a manner of speaking.
Twitter: @neko_no_ko
IRIX Release 4.0.5 IP12 Version 06151813 System V
Copyright 1987-1992 Silicon Graphics, Inc.
All Rights Reserved.
nekonoko wrote:
recondas wrote:
nekonoko wrote: A V10/V12 Octane would have no trouble connecting to a 24" Dell TFT.


I'm using a Dell 24" LCD with a V8 equipped Octane at 1920x1200 - so a V8 could go on that list as well.


I don't recommend the V6/V8 for TFT due to the timing bug, but they do "work" in a manner of speaking.


The V6/V8 timing bug is mostly related to not being about to run at 1280x1024 at the most common refresh rates for TFTs (you will need to drop down to 8byte framebuffer to run 1280x1024 60hz).

This does not in affect V8s running at 1920x1200. In fact, in some ways V8 would be better than V10 running at 1920x1200 because of the higher framebuffer memory. V10 running at that resolution would have hardly any texture memory left.

Officially supported resolutions:
http://www.sgi.com/products/remarketed/ ... tions.html
My Systems:
Apple MacBookPro, 2.66Ghz Dual Core i7, Nvidia 330M GT, 8GB RAM, 240GB SSD + 750GB (optibay)
AMD Phenom II X4 3.4Ghz, Nvidia 9800GT, 8Gb RAM, 2TB + 1.5TB
Apple iBook G4, 1.2ghz G4, ATI 9200, 768MB RAM, 80GB.
HP c8000, 1.1Ghz Dual Core PA-8900, ATI FireGL X3, 6GB RAM, 2x73GB
nekonoko wrote: the O2 really only supports the 1600sw via widescreen.

I think, there is also another solution.

There is a way how to get 1600x1024 60 Hz from the DB25 VGA output :-)

Just turn on O2 with the FPA adapter in on and you WILL get also 1600x1024 60 Hz resolution from VGA connector.

I have tried this. :-)

This is (max. 60 Hz of vertical referesh) not good for most CRT monitors ! , because of screen blinking, it is NOT recommended by SGI, but LCD should do fine also with 60 Hz :-) ))))))))

I have an O2 with FPA. Unfortunatelly, I dont have WORKING 1600SW now :-( - I do have one - but It does not work :-( .
I doubt there is any chance to get 1920x1200 out of an O2. I built a 1680x1050 mode for O2 lately, as somebody requested one in a different thread but i have yet to get any feedback for it. I have no idea if it works as i don't have access to an O2 or a 1680x1050 display:

http://www.kanera.net/modes/crm/1680x1050_60-205bw.nfo

it is based on a similar mode i compiled for VPro before but i had to lower the TotalPixelsPerLine a bit or vfc would refuse to compile it for CRM at all. So if it works at all, its probably pretty close to what you can get out of the O2.

As for Octane, any VPro will happily do 1920x1200. V6 and V10 would have to run it at 8 bytes/pixel though, as it would need ~36 MB framebuffer at 16 bytes/pixel. At 8 bytes/pixel there should be ~10 MB left for textures, actually more than what is left at the usual 1280x1024 at 16 bytes/pixel..

Cheers,
Timo
What's an FPA? Is that something SGI-Specific?



vvostenak wrote:
nekonoko wrote: the O2 really only supports the 1600sw via widescreen.

I think, there is also another solution.

There is a way how to get 1600x1024 60 Hz from the DB25 VGA output :-)

Just turn on O2 with the FPA adapter in on and you WILL get also 1600x1024 60 Hz resolution from VGA connector.

I have tried this. :-)

This is (max. 60 Hz of vertical referesh) not good for most CRT monitors ! , because of screen blinking, it is NOT recommended by SGI, but LCD should do fine also with 60 Hz :-) ))))))))

I have an O2 with FPA. Unfortunatelly, I dont have WORKING 1600SW now :-( - I do have one - but It does not work :-( .
Twitter: @neko_no_ko
IRIX Release 4.0.5 IP12 Version 06151813 System V
Copyright 1987-1992 Silicon Graphics, Inc.
All Rights Reserved.
Is it possible to run widescreen on a 1600sw with an Indigo2 Max Impact machine?
Grummz wrote: Is it possible to run widescreen on a 1600sw with an Indigo2 Max Impact machine?


I ran my MaxImpact for a (short) while at 1600x1200. The thing is: it works, but you loose so much of the graphics board memory to the framebuffer that few remains for Z buffer etc. Essentially, you turn this former 3D workhorse into a glorified 2D framebuffer :cry:

I don't even know if you can get 1600x1024 out of MaxImpact. And then you'd have to convert the signal into something the 1600SW likes. I don't think this worked for Octane with Impact graphics, so I wouldn't expect it to work for an Indigo2.

A lot of LCD's do work on SGI's. I got a freebie 17" Iiyama 430 the other day and it turned out it works perfectly with an Indy (so an Indigo2 should be a problem either). And that's [email protected], something the SGI's default to :)
Now this is a deep dark secret, so everybody keep it quiet :)
It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi

Currently in commercial service: Image :Onyx2: (2x) :O3x02L:
In the museum : almost every MIPS/IRIX system.
Wanted : GM1 board for Professional Series GT graphics (030-0076-003, 030-0076-004)
Oh great! Thanks for replying to this thread. I reposted the question to the other thread...oh well.

Didn't SGI have a 19 inch LCD that was 4:3 aspect ratio?
Grummz wrote: Oh great! Thanks for replying to this thread. I reposted the question to the other thread...oh well.

Didn't SGI have a 19 inch LCD that was 4:3 aspect ratio?

Yes, F190
Was just trying to load the NFO file but can't manage to find which program loads this file..... hrmmmmmm.



schleusel wrote:
I doubt there is any chance to get 1920x1200 out of an O2. I built a 1680x1050 mode for O2 lately, as somebody requested one in a different thread but i have yet to get any feedback for it. I have no idea if it works as i don't have access to an O2 or a 1680x1050 display:

http://www.kanera.net/modes/crm/1680x1050_60-205bw.nfo

it is based on a similar mode i compiled for VPro before but i had to lower the TotalPixelsPerLine a bit or vfc would refuse to compile it for CRM at all. So if it works at all, its probably pretty close to what you can get out of the O2.

As for Octane, any VPro will happily do 1920x1200. V6 and V10 would have to run it at 8 bytes/pixel though, as it would need ~36 MB framebuffer at 16 bytes/pixel. At 8 bytes/pixel there should be ~10 MB left for textures, actually more than what is left at the usual 1280x1024 at 16 bytes/pixel..

Cheers,
Timo
Ah I got it to load the file ! Just needed to rename .nfo to .vfo.

Display works, but when you try to move windows, or click on the toolchest it freaks out.

Looks like you almost got it tho...





schleusel wrote:
I doubt there is any chance to get 1920x1200 out of an O2. I built a 1680x1050 mode for O2 lately, as somebody requested one in a different thread but i have yet to get any feedback for it. I have no idea if it works as i don't have access to an O2 or a 1680x1050 display:

http://www.kanera.net/modes/crm/1680x1050_60-205bw.nfo

it is based on a similar mode i compiled for VPro before but i had to lower the TotalPixelsPerLine a bit or vfc would refuse to compile it for CRM at all. So if it works at all, its probably pretty close to what you can get out of the O2.

As for Octane, any VPro will happily do 1920x1200. V6 and V10 would have to run it at 8 bytes/pixel though, as it would need ~36 MB framebuffer at 16 bytes/pixel. At 8 bytes/pixel there should be ~10 MB left for textures, actually more than what is left at the usual 1280x1024 at 16 bytes/pixel..

Cheers,
Timo
The MXI losing everything at UXGA thing is what made me decide to fix my 1800FP panel and use that in place of a 2001FP until I score a V12 one day.

1600x1024 does not work on Dell 2001FPs. The controller thinks it's being fed 1280x1024 and won't budge from that.

Frankly, though, the 1800FP is a damn good display as it uses an LG S-IPS panel with 8-bit subpixels and no dithering. 18" SXGA is always better for the eyes than 17" SXGA. 19" SXGA is even better.

_________________
-- I'm a PeeCee and I can kick your ass . --
Slow PeeCee - i7 940 OC 4.1GHz, 20GB DDR3 OC 1.8GHz, 2x1TB WD RAID0, ATI 5870 1GB, 3008WFP
Dev PeeCee - IBM Intellistation A Pro - Dual Opteron 290 2.8GHz, 8GB ECC DDR, 500GB SATA, 8400GS, 2x1800FP
Slow PeeCee Cluster - 30x Opteron 275, 60.5GB RAM, 2.2TB, 2x1.5TB
Octane 2xR12K-300, 1.5GB, 36GB 10K, 73GB 10K, V8
Indigo2 195MHz, 1GB, 36GB, SI

There are 10 kinds of people in the world:
Those who understand Ternary. Those who don't. Those who could give a shit less.
Seems like you are talking about the Octane......

Does anyone know if O2 has ever worked on a wide-screen res ?

I'm looking for any resolution that might work with the O2.

Also looking for how the VFO was compiled that I tested previously.... Any details would be extremely helpful. thanks.

I think I may try to embark on compiling my own VFO file. Yikes!


MisterDNA wrote:
The MXI losing everything at UXGA thing is what made me decide to fix my 1800FP panel and use that in place of a 2001FP until I score a V12 one day.

1600x1024 does not work on Dell 2001FPs. The controller thinks it's being fed 1280x1024 and won't budge from that.

Frankly, though, the 1800FP is a damn good display as it uses an LG S-IPS panel with 8-bit subpixels and no dithering. 18" SXGA is always better for the eyes than 17" SXGA. 19" SXGA is even better.
SGIFanLongTime wrote:
Does anyone know if O2 has ever worked on a wide-screen res ? I'm looking for any resolution that might work with the O2.

Probably not what you meant, but I ran one at 1600x1024 for several years using an FPA & 1600SW.


SGIFanLongTime wrote:
Also looking for how the VFO was compiled that I tested previously.... Any details would be extremely helpful. thanks.

I think I may try to embark on compiling my own VFO file. Yikes!


SGI has a tool called the Video Format Compiler <a.k.a. VFC>. You can get a basic idea of how it works with man vfc . There's also a Video Format Compiler Programmer's Guide available on-line at SGI's TechPubs.

If you're not already familiar with how to boot into single user mode, you might want to include that in your reading list <and it's good stuff to know any how>, just in case you have any near misses while your compiling your video formats and need to reset your display properties from a command line.