Sponsored Content
Operating Systems Solaris Separate X screens on x86 Solaris 11.3 Post 303026388 by defs on Tuesday 27th of November 2018 02:03:40 AM
Old 11-27-2018
Separate X screens on x86 Solaris 11.3

Good morning,

I` am trying to make a separate X screens on x86 machine
Dell XE2 Intel i5 2.5Ghz .
Video : Xeon E3-1200 v3/4 Gen Core Processor Integrated Graphics processor

Using Solaris 11.3
Release: kernel SunOS 5.11
Gnome 2.30.2
So right now I have tried to change /etc/X11/xorg.conf by adding in:
Code:
Section “device”
Identifier “intel0”
Driver “intel”
Option “ZaphodHeads” “DP1”
Option “AccelMethod” “sna”
BusID “0:2:0”
The same for second device except Indetifier “intel1” and Option Zahodheads “HDMI”
In selection “ServerLayout” 
Screen 0 “screen0”
Screen “screen1” LeftOf  “screen0”
And a second Sections for Monitor and Screen


As I restart Xserver , Xserver does not start. In Log /var/log/Xorg.0.log I see “ (EE) no screens found”
When I comment line Option - “AccelMethod” “sna” I can start it again, but it starts as twin view.

While Xserver is working I see in log file 2 screens- DP1 and HDMI


I did try xrandr , but no luck, ( xrandr see only 1 screen)
I know that that if I could use Nvidia video card then everything would be ok, but I can`t.

Any ideas how to make separate x screens on x86 using intel integrated video?

Last edited by defs; 11-27-2018 at 04:08 AM..
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Save Solaris x86

Anyone who uses, has used, or would like to use Solaris on Intel-compatible hardware should rush right over to this site: http://www.save-solaris-x86.org/ If you want it, make sure you speak up! (3 Replies)
Discussion started by: LivinFree
3 Replies

2. UNIX for Dummies Questions & Answers

Solaris 8 x86

Hi There, I search a lot across the board but didn't find answer... first of all... I installed the Companion CD. So Kde is supposed to work... I ran the script to have it in my login screen, and it's there... but when I enter it, it only kicks me to the login screen once... (1 Reply)
Discussion started by: Erythro73
1 Replies

3. Solaris

solaris on x86

hi, need help! i've installed solaris 9 on my x86 box...problems with kdmconfig. here what i have: 1- Dell 17" Flat monitor ( 31kHz-80kHz horizontal and 56 Hz-76Hz Vertical) 2- Matrox Millenium G550 card what choices do i have to made? best regards thank you in advance (1 Reply)
Discussion started by: hmaiida
1 Replies

4. UNIX for Dummies Questions & Answers

How to switch between terminal screens in Sun Solaris 10

:) Hi everybody.. This is my firt post in this great forum.: I have installed Sun Solaris 10 on an Intel machine.. Now i login in CDE desktop as root. I want to switch between terminal screens pressing CTRL+ALT F1 (through F6) but nothing happens ?? any suggestions thank you (2 Replies)
Discussion started by: peterpan
2 Replies

5. Solaris

Solaris 10 X86

Ok here goes, this MCSE is now fed up with MS, they are telling me that my Legal XP has a s/num they didnt issue. After countless emails I am P with them and am loooking for a new OS. Tried Linux, got it working but seems too flaky for me. Have installed Solaris 10 X86 (on a temp pc AMD Athlon... (1 Reply)
Discussion started by: mickie
1 Replies

6. Solaris

Installing Solaris 10 (x86)

I tried installing Solaris 10 (x86) 01/06 on a VMWARE machine. Installation went on pretty smoothly for CD 1 but I seem to have problem installing the rest of the CDs. I have a few questions to ask: After installing CD 1, I was prompted to reboot, when the system rebooted, I was back at the... (3 Replies)
Discussion started by: owls
3 Replies

7. Solaris

Solaris x86 on D<LL (OK I said it)

OK, I have a DELL Poweredge 2850 fresh out of the box sitting here. I'm thinking of putting Solaris 9 x86 on it. Has anyone ever attempted this before, do you think it will work? I dont want to get into something that is just going to be a enormus waste of time, so I am wondering if anyone... (1 Reply)
Discussion started by: BG_JrAdmin
1 Replies

8. UNIX for Dummies Questions & Answers

Running Solaris Sparc Apps on X86 Solaris

I know that Sun make s a version of Solaris for Sparc platforms and also an x86 (Intel/AMD) release of Solaris. Can an application that runs on Solaris/Sparc also run on a PC running the x86 release of Solaris? Would a different release be required or any re-compling of the application? jim (1 Reply)
Discussion started by: stocksj
1 Replies

9. Solaris

Jumpstart Solaris 10 x86

I need a little help figuring out why my custom jumpstart network installation is dumping me to a manual install. I am trying to install Solaris 10 (unattended) over the wire from my jumpstart server to an HP Proliant DL380 server but I'm having difficulties with the unattended part. So, what... (2 Replies)
Discussion started by: alias.256
2 Replies

10. Solaris

Solaris: clnt_create fails on solaris x86

Hi, I am facing an issue with Solaris x86 machine Machine Details: uname -a SunOS sol10-64 5.10 Generic_137138-09 i86pc i386 i86pc .............................. Description: I am trying to register a programm with proramm ID 300760 with version number 1, and tryint to create a... (0 Replies)
Discussion started by: DivakarAdari
0 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 04:46 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy