Sponsored Content
Operating Systems Solaris Resolution error sunfire v245 Post 302267816 by saurabh84g on Sunday 14th of December 2008 02:41:09 AM
Old 12-14-2008
Resolution error sunfire v245

Hi all,

I am getting the below error on Solaris sunfire v245 server

Error: can not display this video mode
optimum resolution 1024x768 60Hz

i am not able to resolve this .plz help me out ?
 

10 More Discussions You Might Find Interesting

1. AIX

Error - Symbol Resolution Failed

Hi All, I am trying to run sqlplus on my AIX 5L box but following errors are thrown: $ sqlplus exec(): 0509-036 Cannot load program sqlplus because of the following errors: 0509-130 Symbol resolution failed for /usr/lib/libc.a because: 0509-136 Symbol kaio_rdwr64 (number 0)... (5 Replies)
Discussion started by: run_time_error
5 Replies

2. AIX

Getting Symbol resolution failed for ../../../lib/libc.a Error

Hi I have compiled a binary on AIX 5.3.0.0 but when i run i get following error Could not load program ACE_wrappers/bin/gperf: Symbol resolution failed for ../../../lib/libc.a(posix_aio.o) because: Symbol _posix_kaio_rdwr (number 2) is not exported from dependent module... (0 Replies)
Discussion started by: khan_nayeem
0 Replies

3. Solaris

how to go to system console through ALOM in Sunfire V245

Hello , I am connecting sumfire v245 server to my laptop Through ALOM method.i got the ALOM prompt but after that i am typing sc> console to go to system console but i am not able to,after typing console only this line is coming Type #. to go back to ALOM. What to do ?? That server having... (5 Replies)
Discussion started by: avi157
5 Replies

4. UNIX for Dummies Questions & Answers

No Responses from ALOM using NET MGNT PORT on SunFire v245

Please Help... I have two sunfire V245 servers running Apache on Solaris 5.10. Both servers have the same settings and apps. Before we used serial port to connect to ALOM 1.6. We switched to net mgnt port because of virtualization of all our servers. Situation: Server 1 applied the solaris... (1 Reply)
Discussion started by: glieu
1 Replies

5. Solaris

SunFire V245, External CD/DVD-ROM, Solaris Install

Hey all. Wondering - I have a pair of V245's with no internal CD/DVD-ROM drives, and I want to install the latest/greatest Solaris 10. Booting these machines with an external drive plugged in via USB does no good. Is jumpstart or installing internal drives the only alternative? I'm a... (1 Reply)
Discussion started by: b1f30
1 Replies

6. Solaris

SunFire V890 error -256 when boot

Hi all! I've a machine - SunFire V890, it've been failed by OS error for 2 weeks ago, and now, I must reinstall OS (Solaris 10 2009), the progress was successful, but when I reboot, it displayed the error like : Error -256: Last trap memory ... access aligned Error -256: Last trap memory... (1 Reply)
Discussion started by: trantuananh24hg
1 Replies

7. Solaris

SunFire v245 Environmental PIC micro controller fix

Hello All, We have a v245 that powered itself off for no reason. Searching around we discovered there is a bug were a temp error is being reported but doesnt actually exist, SUN released an EPIC update, the README is shown below but even after upgrading the ALOM to the latest v1.6.10 we do not... (8 Replies)
Discussion started by: Wez
8 Replies

8. Solaris

SunFire T2000 ipmievd error

I'm running Solaris 10 (09/10) on Sun Fire T2000. This error message is logged repeatedly in /var/adm/messages: May 22 10:40:33 EBDW01 last message repeated 25 times May 22 10:40:36 EBDW01 ipmievd: Reading sensors... May 22 10:40:40 EBDW01 ipmievd: Error obtaining SDR info: Unknown... (4 Replies)
Discussion started by: Sun Fire
4 Replies

9. Hardware

POST error on SunFire V245

I've recently bought an SunFire V245. 2x 2.5ghz x64 4gb ram 4x 73gb sas hdd and... an blinking 'Identifior led' (white) with 'Service led' (amber) simultaneously. It boots for +- 5 secs and then the error occurd. Things done: Removed all hdd. Switched cpu Switched/removed ram... (2 Replies)
Discussion started by: niswier2222
2 Replies

10. Hardware

SUN V245 Connecting To router Through Alom

Hello. I have a sun v245 and I have no hard drive for it yet but i would like to connect it to my home router by ethernet cable so I can use Alom remotely. Could someone please tell me how to set it up. Thank You (1 Reply)
Discussion started by: SunV245
1 Replies
GLIDE(4)						     Kernel Interfaces Manual							  GLIDE(4)

NAME
glide - Glide video driver SYNOPSIS
Section "Device" Identifier "devname" Driver "glide" ... EndSection DESCRIPTION
glide is an Xorg driver for Glide capable video boards (such as 3Dfx Voodoo boards). This driver is mainly for Voodoo 1 and Voodoo 2 boards, later boards from 3Dfx have 2D built-in and you should preferably use a driver separate for those boards or the fbdev(4) driver. This driver is a bit special because Voodoo 1 and 2 boards are very much NOT made for running 2D graphics. Therefore, this driver uses no hardware acceleration (since there is no acceleration for 2D, only 3D). Instead it is implemented with the help of a "shadow" framebuffer that resides entirely in RAM. Selected portions of this shadow framebuffer are then copied out to the Voodoo board at the right time. Because of this, the speed of the driver is very dependent on the CPU. But since the CPU is nowadays actually rather fast at moving data, we get very good speed anyway, especially since the whole shadow framebuffer is in cached RAM. This driver supports 16 and 24 bit color modes. The 24 bit color mode uses a 32 bit framebuffer (it has no support for 24 bit packed-pixel framebuffers). Notice that the Voodoo boards can only display 16 bit color, but the shadow framebuffer can be run in 24 bit color. The point of supporting 24 bit mode is that this enables you to run in a multihead configuration with Xinerama together with another board that runs in real 24 bit color mode. (All boards must run the same color depth when you use Xinerama). Resolutions supported are: 640x480, 800x600, 960x720, 1024x768, 1280x1024 and 1600x1200. Note that not all modes will work on all Voodoo boards. It seems that Voodoo 2 boards support no higher than 1024x768 and Voodoo 1 boards can go to 800x600. If you see a message like this in the output from the server: (EE) GLIDE(0): grSstWinOpen returned ... Then you are probably trying to use a resolution that is supported by the driver but not supported by the hardware. Refresh rates supported are: 60Hz, 75Hz and 85Hz. The refresh rate used is derived from the normal mode line according to the following ta- ble: Mode-line refresh rate Used refresh rate 0-74 Hz 60 Hz 74-84 Hz 75 Hz 84- Hz 85 Hz Thus, if you use a modeline that for example has a 70Hz refresh rate you will only get a 60Hz refresh rate in actuality. Selecting which Voodoo board to use with the driver is done by using an option called "GlideDevice" in the "Device" section. (If you don't have this option present then the first board found will be selected for that Device section). For example: To use the first Voodoo board, use a "Device" section like this, for example: Section "Device" Identifier "Voodoo" Driver "glide" Option "dpms" "on" Option "GlideDevice" "0" EndSection And if you have more than one Voodoo board, add another "Device" section with a GlideDevice option with value 1, and so on. (You can use more than one Voodoo board, but SLI configured boards will be treated as a single board.) Multihead and Xinerama configurations are supported. Limited support for DPMS screen saving is available. The "standby" and "suspend" modes are just painting the screen black. The "off" mode turns the Voodoo board off and thus works correctly. This driver does not support a virtual screen size different from the display size. SUPPORTED HARDWARE
The glide driver supports any board that can be used with Glide (such as 3Dfx Voodoo boards) CONFIGURATION DETAILS
Please refer to xorg.conf(5) for general configuration details. This section only covers configuration details specific to this driver. The following driver Options are supported: Option "OnAtExit" "boolean" If true, will leave the Voodoo board on when the server exits. Useful in a multihead setup when only the Voodoo board is connected to a second monitor and you don't want that monitor to lose signal when you quit the server. Put this option in the Device section. Default: off. Option "GlideDevice" "integer" Selects which Voodoo board to use. (Or boards, in an SLI configuration). The value should be 0 for the first board, 1 for the sec- ond and so on. If it is not present, the first Voodoo board found will be selected. Put this option in the Device section. EXAMPLE
Here is an example of a part of an xorg.conf file that uses a multihead configuration with two monitors. The first monitor is driven by the fbdev video driver and the second monitor is driven by the glide driver. Section "Monitor" Identifier "Monitor 1" VendorName "Unknown" ModelName "Unknown" HorizSync 30-70 VertRefresh 50-80 # 1024x768 @ 76 Hz, 62.5 kHz hsync Modeline "1024x768" 85 1024 1032 1152 1360 768 784 787 823 EndSection Section "Monitor" Identifier "Monitor 2" VendorName "Unknown" ModelName "Unknown" HorizSync 30-70 VertRefresh 50-80 # 1024x768 @ 76 Hz, 62.5 kHz hsync Modeline "1024x768" 85 1024 1032 1152 1360 768 784 787 823 EndSection Section "Device" Identifier "fb" Driver "fbdev" Option "shadowfb" Option "dpms" "on" # My video card is on the AGP bus which is usually # located as PCI bus 1, device 0, function 0. BusID "PCI:1:0:0" EndSection Section "Device" # I have a Voodoo 2 board Identifier "Voodoo" Driver "glide" Option "dpms" "on" # The next line says I want to use the first board. Option "GlideDevice" "0" EndSection Section "Screen" Identifier "Screen 1" Device "fb" Monitor "Monitor 1" DefaultDepth 16 Subsection "Display" Depth 16 Modes "1024x768" EndSubSection EndSection Section "Screen" Identifier "Screen 2" Device "Voodoo" Monitor "Monitor 2" DefaultDepth 16 Subsection "Display" Depth 16 Modes "1024x768" EndSubSection EndSection Section "ServerLayout" Identifier "Main Layout" # Screen 1 is to the right and screen 2 is to the left Screen "Screen 2" Screen "Screen 1" "" "" "Screen 2" "" EndSection If you use this configuration file and start the server with the +xinerama command line option, the two monitors will be showing a single large area where windows can be moved between monitors and overlap from one monitor to the other. Starting the X server with the Xinerama extension can be done for example like this: $ xinit -- +xinerama FILES
glide_drv.o SEE ALSO
Xorg(1), xorg.conf(5), Xserver(1), X(7) AUTHORS
Author: Henrik Harmsen. X Version 11 xf86-video-glide 1.2.0 GLIDE(4)
All times are GMT -4. The time now is 05:38 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy