10-07-2002
Found on Sunsolve (realize things like Stop-a may crash your server):
Here are the steps to set up several (TurboGX) tgx cards.
(This may make assumptions about the OpenBoot[TM] prom rev level
and the resolutions the frame buffer supports.)
1) The console monitor is set up using output-device
User can find which device is the console monitor with:
L1-A (Stop-a)
ok devalias screen
It should say something like /sbus@1,f8000000/cgsix@3,0 this is
the console screen. This string will differ on other types of
hardware. For instance, it may be /obio/cgfourteen@2,0 on a
sparc-20.
Next, look at all the frame buffers on the system:
ok show-devs
... /cgsix@0,0
... /cgsix@2,0
... /cgsix@3,0
It has already been seen which device was the console frame buffer.
The other two frame buffers are cgsix@2 and cgsix@3. This output
will widely vary depending on the system architecture.
Now, set up a shell script:
#!/bin/sh
eeprom output-device='screen:r1280x1024x76'
eeprom fcode-debug\?=true
eeprom nvramrc='probe-sbus
" /iommu/sbus/cgsix@2" select-d ev
r1280x1024x76
" /iommu/sbus/cgsix@2" " set-resolution" execute-device-method drop
device-end
" /iommu/sbus/cgsix@3" select-dev
r1280x1024x76
" /iommu/sbus/cgsix@3" " set-resolution" execute-device-method drop
device-end
install-console
banner
'
eepr om use-nvramrc\?=true
Pay attention to the spaces within the double-quotes.
The output-device line sets the resolution for the console, which
is the primary frame buffer.
The nvramrc line sets up code that executes each time the system
boots. This program sets up the resolution on the second and
third tgx devices.
The last line says to use the script in nvramrc when booting.
Notes:
To find built-in resolutions available for some of the newer frame
buffers (this doesn't work for all devices), type:
L1-A
ok show-devices
...
/sbus@1,f8000000/cgsix@3,0 <-- this is the frame buffer
...
ok cd /sbus/cgsix@3,0
ok words
The resolutions supported show up like r1280x1024x76 (or hdtv).
Other references:
Open Boot Command Reference
Writing Fcode Programs
9 More Discussions You Might Find Interesting
1. Solaris
Hi,
I would like to know how to change the display resolution in solaris on sparc.
Can anyone please help me.
Regards,
Raja (3 Replies)
Discussion started by: RajaRC
3 Replies
2. Solaris
I searched and found something about kdmconfig, but it's not installed.
Isn't there an easy way to change the screen resolution in the CDE by right clicking or anything like that (like in Linux's KDE)? (1 Reply)
Discussion started by: lyonsd
1 Replies
3. UNIX for Dummies Questions & Answers
I would like to know how to change the display resolution in UnixV4.0D.
Can anyone please help me.
Regards,
Avgust (1 Reply)
Discussion started by: avgust
1 Replies
4. UNIX for Dummies Questions & Answers
Hi all,
i am one of the newbies with linux. i just install the Enterprise AS on my ibm z60t. I am trying to change the color setting to hight resolution, unfortunately, it does not work. it works only with the 256 color setting.
It seems the widescreen or the vga card of my notebook does not... (3 Replies)
Discussion started by: sanlen
3 Replies
5. UNIX for Dummies Questions & Answers
Hello,
We have a Suse Linux 9.0 box at work and I need to change the video resolution on it. We have command line interface only. Can someone please tell me how to go about doing so?
Thanks, (0 Replies)
Discussion started by: mojoman
0 Replies
6. Debian
Hi gurus I have notebook with connected external monitor. output of my xrandr looks like
Screen 0: minimum 320 x 200, current 2960 x 1050, maximum 2960 x 1050
VGA connected 1680x1050+1280+0 (normal left inverted right x axis y axis) 478mm x 300mm
1680x1050 60.0*+
1280x1024 ... (2 Replies)
Discussion started by: wakatana
2 Replies
7. Linux
Dear all
I install Cent OS 5.5 ( Linux OS), with bshell and also Windows OS on the my laptop (ASUA) maximum screen resolution in Windows OS is 1024*760 but in Cent OS 5.5 is 800 *600, I have a program that is necessary to install on Cent OS and I have problem with other Linux distributions... (2 Replies)
Discussion started by: mkhorami76
2 Replies
8. AIX
Hello,
Running X on AIX local display - want to change resolution.
On Linux for example I used xrandr.
?
thanks
Vilius (1 Reply)
Discussion started by: vilius
1 Replies
9. UNIX for Beginners Questions & Answers
Hello All,
Wasn't sure if I was supposed to post this under Hardware so posting here...
Device: CuBox-i
OS: OpenSuSE 13.1
Uname: Linux CuBox-PC 3.14.14-cubox-i #1 SMP Sat Sep 13 03:48:24 UTC 2014 armv7l armv7l armv7l GNU/Linux
Window Manager: XFCE
Display Manager: lightdm (*XDM?)
I... (2 Replies)
Discussion started by: mrm5102
2 Replies
LEARN ABOUT PHP
path_to_inst
path_to_inst(4) File Formats path_to_inst(4)
NAME
path_to_inst - device instance number file
SYNOPSIS
/etc/path_to_inst
DESCRIPTION
/etc/path_to_inst records mappings of physical device names to instance numbers.
The instance number of a device is encoded in its minor number, and is the way that a device driver determines which of the possible
devices that it may drive is referred to by a given special file.
In order to keep instance numbers persistent across reboots, the system records them in /etc/path_to_inst.
This file is read only at boot time, and is updated by add_drv(1M) and drvconfig(1M).
Note that it is generally not necessary for the system administrator to change this file, as the system will maintain it.
The system administrator can change the assignment of instance numbers by editing this file and doing a reconfiguration reboot. However,
any changes made in this file will be lost if add_drv(1M) or drvconfig(1M) is run before the system is rebooted.
Each instance entry is a single line of the form:
"physical name" instance number "driver binding name"
where
physical name is the absolute physical pathname of a device. This pathname must be enclosed in double quotes.
instance number is a decimal or hexadecimal number.
driver binding name is the name used to determine the driver for the device.
This name may be a driver alias or a driver name. The driver binding name must be enclosed in double quotes.
EXAMPLES
Example 1: Sample path_to_inst Entries
Here are some sample path_to_inst entries:
"/iommu@f,e0000000" 0 "iommu"
"/iommu@f,e0000000/sbus@f,e0001000" 0 "sbus"
"/iommu@f,e0000000/sbus@f,e0001000/sbusmem@e,0" 14 "sbusmem"
"/iommu@f,e0000000/sbus@f,e0001000/sbusmem@f,0" 15 "sbusmem"
"/iommu@f,e0000000/sbus@f,e0001000/ledma@f,400010" 0 "ledma"
"/obio/serial@0,100000" 0 "zs"
"/SUNW,sx@f,80000000" 0 "SUNW,sx"
FILES
/etc/path_to_inst
SEE ALSO
add_drv(1M), boot(1M), drvconfig(1M), mknod(1M)
WARNINGS
If the file is removed the system may not be bootable (as it may rely on information found in this file to find the root, usr or swap
device). If it does successfully boot, it will regenerate the file, but after rebooting devices may end up having different minor numbers
than they did before, and special files created via mknod(1M) may refer to different devices than expected.
For the same reasons, changes should not be made to this file without careful consideration.
NOTES
This document does not constitute an API. path_to_inst may not exist or may have a different content or interpretation in a future
release. The existence of this notice does not imply that any other documentation that lacks this notice constitutes an API.
SunOS 5.10 2 Nov 1995 path_to_inst(4)