Dual Monitor setup for desktop .....Don't delay, step on up!

Using applications, configuring, problems
Message
Author
User avatar
Monsie
Posts: 631
Joined: Thu 01 Dec 2011, 07:37
Location: Kamloops BC Canada

Dual Monitor setup for desktop..... (unresolvable?)

#21 Post by Monsie »

Hi canbyte,

I'm looking at your Xorg.0.log also. I see that Xinerama is enabled so that part is configured correctly. :)

Looking further along where your Monitors and Connections are being recognized and modules loaded, I see the following:

Code: Select all

76.103] (II) Loading sub module "i2c"76.103] (II) RADEON(0): Output DVI-0 has no monitor section...
76.103] (II) RADEON(0): Output VGA-0 using monitor section Monitor0
[    76.103] (**) RADEON(0): Option "PreferredMode" "1024x768"
[    76.103] (II) RADEON(0): I2C bus "VGA-0" initialized.
[    76.103] (II) RADEON(0): Output DVI-0 has no monitor section...
Notice how your Acer monitor with the vga connection is Monitor0 but where is Monitor1? This suggests to me that you are missing a Monitor1 Section in Xorg.conf or that it is not configured properly for your dvi connection on your Asus monitor. If you do have this second monitor section included in Xorg.conf then the problem is configuring it to work with the dvi connection. One solution is to get a "dvi to vga" adapter so that both connections will configure as vga type in Xorg. This might be the easiest fix here... assuming that this is part of the problem.

HTH,
Monsie
My [u]username[/u] is pronounced: "mun-see". Derived from my surname, it was my nickname throughout high school.

User avatar
canbyte
Posts: 264
Joined: Sat 10 Jan 2009, 20:20
Location: Hamilton, Canada

#22 Post by canbyte »

Hi Monsie
The card has two output ports, one VGA, one DVI so the store gave me an adaptor when they installed the card. I assume it must be correct. But should the system be told about the signal adaptation?

Here is what follows monitor0 section:
Section "Modes"
Identifier "Modes0"
#modes0modeline0
EndSection

Section "Monitor"
Identifier "Monitor1"
#DisplaySize 520 290 # mm
VendorName "ACI"
ModelName "ASUS VH242H"
Option "DPMS"
HorizSync 30.0-85.0
VertRefresh 55.0-71.0
#UseModes "Modes0" #monitor0usemodes
Option "PreferredMode" "1024x768"
EndSection
I included the modes section because i wanted to ask - surely a dual screen mode should be different than a single screen mode, no?

The monitor1 section was modified by me to give xorg the proper details in hopes of preventing monitor1 from going blank as it still does occasionally. Cause unknown / not consistentl. Otherwise xorgwizard only adds a generic monitor1 section.

But yes, i see the following in the log file starting line 19
[ 4277.853] (==) ServerLayout "Xinerama Screen"
[ 4277.853] (**) |-->Screen "Screen0" (0)
[ 4277.853] (**) | |-->Monitor "Monitor0"
[ 4277.853] (**) | |-->Device "Card0"
[ 4277.853] (**) |-->Screen "Screen1" (1)
[ 4277.853] (**) | |-->Monitor "Monitor0"
[ 4277.853] (**) | |-->Device "Card0"
[ 4277.853] (**) |-->Input Device "Mouse0"
[ 4277.853] (**) |-->Input Device "Keyboard0"
[ 4277.853] (**) Option "DontZap" "false"
[ 4277.853] (**) Option "Xinerama" "true"
[ 4277.853] (**) Option "RandR" "on"
So xorg is defaulting back to monitor0 even though xorg shows monitor1. Why? Where is the dual screen instruction? Maybe the above was generated by the screen1 section, but .... heavens, I see screen1 section refers to monitor0, let me change that now and re-edit.

Edit - Gasp! The screens are different. Now the Acer has no icons and no mouse. Let me try changing 'rightof' to leftof. Back in a mo.
Edit - Xorg just puked! Rule1. Don't use Leftof!!! Now xorg.conf has no 1s at all - monitor, screen or device. Let's hope i can reconstruct. But we're getting somewhere.......
Edit - arrrg. back to square 1 ... trying to figure out what i had ...back in a mo..... Edit. Got the separate screens back. Jump to end where I'll enter my present xorg.conf text

I wonder if you are seeing the log file from when i was attempting to follow the gentoo suggestion of dropping the monitor/ screen sections. Hmm, maybe i should attach another one. Some other changes as per prev posts.

BTW, Karl said Racy-5.3 has Xorg-server 1.11.x . How can i determine if Slacko has the same? I see in my xorgwizard:
#110701 synaptics stuff seems to clash with xorg-server 1.10.1.
Xorg.conf text with two different screens - just not positioned properly.
#everything past here is auto-generated by Puppy's Xorg Wizard...


Section "ServerLayout"
Identifier "Xinerama Screen"
Screen 0 "Screen0" 0 0
Screen 1 "Screen1" RightOf "Screen0"
Option "Xinerama" "true"
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection


Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc102"
Option "XkbLayout" "us" #xkeymap0
Option "XkbVariant" "dvorak"
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2" #mouse0protocol
Option "Device" "/dev/mouse"
#Option "Emulate3Buttons"
#Option "Emulate3Timeout" "50"
Option "ZAxisMapping" "4 5" #scrollwheel
EndSection

Section "Monitor"
#DisplaySize 410 260 # mm
Identifier "Monitor0"
VendorName "ACR"
ModelName "Acer AL1916W"
Option "DPMS"
HorizSync 30.0-82.0
VertRefresh 56.0-72.0
#UseModes "Modes0" #monitor0usemodes
Option "PreferredMode" "1024x768"
EndSection

Section "Modes"
Identifier "Modes0"
#modes0modeline0
EndSection


Section "Monitor"
Identifier "Monitor1"
#DisplaySize 520 290 # mm
VendorName "ACI"
ModelName "ASUS VH242H"
Option "DPMS"
HorizSync 30.0-85.0
VertRefresh 55.0-71.0
#UseModes "Modes0" #monitor0usemodes
Option "PreferredMode" "1024x768"
EndSection



Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
### <percent>: "<f>%"
### [arg]: arg optional
#Option "NoAccel" # [<bool>]
#Option "SWcursor" # [<bool>]
#Option "Dac6Bit" # [<bool>]
#Option "Dac8Bit" # [<bool>]
#Option "BusType" # [<str>]
#Option "CPPIOMode" # [<bool>]
#Option "CPusecTimeout" # <i>
#Option "AGPMode" # <i>
#Option "AGPFastWrite" # [<bool>]
#Option "AGPSize" # <i>
#Option "GARTSize" # <i>
#Option "RingSize" # <i>
#Option "BufferSize" # <i>
#Option "EnableDepthMoves" # [<bool>]
#Option "EnablePageFlip" # [<bool>]
#Option "NoBackBuffer" # [<bool>]
#Option "DMAForXv" # [<bool>]
#Option "FBTexPercent" # <i>
#Option "DepthBits" # <i>
#Option "PCIAPERSize" # <i>
#Option "AccelDFS" # [<bool>]
#Option "IgnoreEDID" # [<bool>]
#Option "CustomEDID" # [<str>]
#Option "DisplayPriority" # [<str>]
#Option "PanelSize" # [<str>]
#Option "ForceMinDotClock" # <freq>
#Option "ColorTiling" # [<bool>]
#Option "VideoKey" # <i>
#Option "RageTheatreCrystal" # <i>
#Option "RageTheatreTunerPort" # <i>
#Option "RageTheatreCompositePort" # <i>
#Option "RageTheatreSVideoPort" # <i>
#Option "TunerType" # <i>
#Option "RageTheatreMicrocPath" # <str>
#Option "RageTheatreMicrocType" # <str>
#Option "ScalerWidth" # <i>
#Option "RenderAccel" # [<bool>]
#Option "SubPixelOrder" # [<str>]
#Option "ClockGating" # [<bool>]
#Option "VGAAccess" # [<bool>]
#Option "ReverseDDC" # [<bool>]
#Option "LVDSProbePLL" # [<bool>]
#Option "AccelMethod" # <str>
#Option "DRI" # [<bool>]
#Option "ConnectorTable" # <str>
#Option "DefaultConnectorTable" # [<bool>]
#Option "DefaultTMDSPLL" # [<bool>]
#Option "TVDACLoadDetect" # [<bool>]
#Option "ForceTVOut" # [<bool>]
#Option "TVStandard" # <str>
#Option "IgnoreLidStatus" # [<bool>]
#Option "DefaultTVDACAdj" # [<bool>]
#Option "Int10" # [<bool>]
#Option "EXAVSync" # [<bool>]
#Option "ATOMTVOut" # [<bool>]
#Option "R4xxATOM" # [<bool>]
#Option "ForceLowPowerMode" # [<bool>]
#Option "DynamicPM" # [<bool>]
#Option "NewPLL" # [<bool>]
#Option "ZaphodHeads" # <str>
Identifier "Card0"
Driver "radeon" #card0driver
BusID "PCI:4:9:0"
Screen 0
EndSection

Section "Device"
Identifier "Card1"
Driver "radeon" #card1driver
VendorName "ATI Technologies Inc"
BoardName "ATI_RADEON_9200"
Screen 1
EndSection


Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 16
#Option "metamodes" "1024x768_60 +0+0" #METAMODES_0
Subsection "Display"
Depth 16
Modes "1024x768"
EndSubsection
EndSection


Section "Screen"
Identifier "Screen1"
Device "Card1"
Monitor "Monitor1"
DefaultDepth 16
#Option "metamodes" "1024x768_60 +0+0" #METAMODES_0
Subsection "Display"
Depth 16
Modes "1024x768"
EndSubsection
EndSection

#PuppyHardwareProfile=ATI_RADEON_9200AcerAL1916W
Now to experiment with positioning. ....

Clue: A moment ago, before reconstruction was complete, i saw messages - screen0 - no signal
screen1 - out of range... . which kept jumping corner to corner to center in an infinite loop. so i shutdown and restarted and here we are.
clue: on starting - the topmost icon is the browser so i have to 'push' mouse upward which brings the upper icons into view until a border is reached. I can push this window off the screen (upwards) and rightwards but cursor won't appear on screen0 (acer). The icons seem to have been put way above and to the left of the wallpaper/image. Hmm. I seem to recall 'absolute' referencing system being mentioned. Also 'virtual' although my attempts to activate that seem to have sent me back to square1.

Edit - Just as well i recorded xorg.conf but something is now causing it to be overwritten with the original (missing screen1, monitor1, device1). I was thinking of a cleanup and removed some extra spaces between sections. Didn't like? Only clue now is a brief message on Asus monitor1 'out of range'. Maybe this is the moment when xorg reverts to default. So maybe i better reattach the log file.
Attachments
July29trial2.zip
(11.4 KiB) Downloaded 425 times
Last edited by canbyte on Sun 29 Jul 2012, 18:15, edited 1 time in total.
[color=orange]1. Dell Dimension E521, AMD Athln 64, 2 GHz 1.93GB ram,
Puppy 533 on CD, accesses flash drive only,
FFox Nightly12.0
2. Compaq P3 733Hz 375RAM
Printer: Oki C3400 > LAN [/color]

User avatar
Karl Godt
Posts: 4199
Joined: Sun 20 Jun 2010, 13:52
Location: Kiel,Germany

#23 Post by Karl Godt »

canbyte : with the "extra" ati driver i meant something like this :

http://support.amd.com/de/gpudownload/l ... linux.aspx

also billtwo knows how to install it :

ati driver

User avatar
canbyte
Posts: 264
Joined: Sat 10 Jan 2009, 20:20
Location: Hamilton, Canada

#24 Post by canbyte »

Hi Karl. I see what you mean - I guess that means i should look for the right driver for the 9600. At the moment, I'm frustrated trying to recreate the dual screen i had earlier per previous post. I should have recorded xorg then. Once there, hopefully just a matter of tweaking. But xorgwizard keeps overruling xorg.conf once the out of range contition occurs. Not sure what I changed. :( but having the screen being not echoed, but different, gives me hope that the driver may not be the problem - just a matter of getting the code right. If only i knew what part of the code i'm getting wrong.

Edit - just had a restart without the out of range message. Second screen section set to monitor1 but card0 is what i set it at. But noticed that the xorg file had reverted to default again. Nuts. Why is xorg not liking my changes?

Just noticed that Xorg.0.log line 2 says
X.Org X Server 1.9.5
This is older than the Racy 5.3 xorg that Karl found above.
The xorg website shows X11R7.7 as being the latest available.
I doubt I'm reading this right and am worn out for the day. Goin' for a nap.
Edit: nap's out. Wife gives me a choice - 'beach or bitch'. I guess you know what that means. cya later.
[color=orange]1. Dell Dimension E521, AMD Athln 64, 2 GHz 1.93GB ram,
Puppy 533 on CD, accesses flash drive only,
FFox Nightly12.0
2. Compaq P3 733Hz 375RAM
Printer: Oki C3400 > LAN [/color]

User avatar
Karl Godt
Posts: 4199
Joined: Sun 20 Jun 2010, 13:52
Location: Kiel,Germany

#25 Post by Karl Godt »

canbyte wrote:But noticed that the xorg file had reverted to default again. Nuts. Why is xorg not liking my changes?
This may be one of the annoying newly introduced features by BK : xorgwizard-automatic.

One cause for me to stay with Puppy 4.

/usr/sbin/xorgwizard-automatic gets launched by /usr/bin/xwin now instead of /usr/sbin/xorgwizard, if the ddcprobe command outputs something different than before.

User avatar
canbyte
Posts: 264
Joined: Sat 10 Jan 2009, 20:20
Location: Hamilton, Canada

#26 Post by canbyte »

Karl, again, i think you hit a nail with something "different than before". It dawned on me that mostly i've been making a change to xorg.conf, then restarting x only to find the change was written over. So I tried reboot instead. Didn't work, but on going to xorgwizard, (for no particular reason), chose xvesa instead of probe. Xwin started as normal with rewritten xorg so I copied over and saved. Rebooted. This time it went through with both monitor/screen/device sections intact. Restarting x didn't revert xorg to default. So this is what i've ended up with
Section "ServerLayout"
Identifier "Xinerama Screen"
Screen 0 "Screen0" 0 0
Screen 1 "Screen1" RightOf "Screen0"
Option "Xinerama" "true"
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection


Section "InputDevice"
-snip-
EndSection

Section "InputDevice"
-snip-
EndSection

Section "Monitor"
#DisplaySize 410 260 # mm
Identifier "Monitor0"
VendorName "ACR"
ModelName "Acer AL1916W"
Option "DPMS"
HorizSync 30.0-82.0
VertRefresh 56.0-72.0
#UseModes "Modes0" #monitor0usemodes
Option "PreferredMode" "1024x768"
EndSection

Section "Modes"
Identifier "Modes0"
#modes0modeline0
EndSection


Section "Monitor"
Identifier "Monitor1"
#DisplaySize 520 290 # mm
VendorName "ACI"
ModelName "ASUS VH242H"
Option "DPMS"
HorizSync 30.0-85.0
VertRefresh 55.0-71.0
#UseModes "Modes0" #monitor0usemodes
Option "PreferredMode" "1024x768"
EndSection



Section "Device"
-snip-
#Option "ZaphodHeads" # <str>
Identifier "Card0"
Driver "vesa" #card0driver
BusID "PCI:4:9:0"
EndSection

Section "Device"
Identifier "Card1"
Driver "radeon" #card1driver
VendorName "ATI Technologies Inc"
BoardName "ATI_RADEON_9200"
Screen 1
EndSection


Section "Screen"
Identifier "Screen0"
Device "Card1"
Monitor "Monitor0"
DefaultDepth 16
#Option "metamodes" "1024x768_60 +0+0" #METAMODES_0
Subsection "Display"
Depth 16
Modes "1024x768"
EndSubsection
EndSection


Section "Screen"
Identifier "Screen1"
Device "Card0"
Monitor "Monitor1"
DefaultDepth 16
#Option "metamodes" "1024x768_60 +0+0" #METAMODES_0
Subsection "Display"
Depth 16
Modes "1024x768"
EndSubsection
EndSection
I snipped out the junk. Can i remove all the commented-out (#, ##) items in card0 permanently? The mixup of card 0 and 1 seems not to matter. Still no extended desktop though.

The log file looks a bit better:
[ 343.170] (==) ServerLayout "Xinerama Screen"
[ 343.170] (**) |-->Screen "Screen0" (0)
[ 343.170] (**) | |-->Monitor "Monitor0"
[ 343.170] (**) | |-->Device "Card1"
[ 343.170] (**) |-->Screen "Screen1" (1)
[ 343.170] (**) | |-->Monitor "Monitor1"
[ 343.171] (**) | |-->Device "Card0"
[ 343.171] (**) |-->Input Device "Mouse0"
[ 343.171] (**) |-->Input Device "Keyboard0"
[ 343.171] (**) Option "DontZap" "false"
[ 343.171] (**) Option "Xinerama" "true"
[ 343.171] (**) Option "RandR" "on"
[ 343.171] (**) Option "AutoAddDevices" "false"
[ 343.171] (**) Not automatically adding devices
[ 343.171] (==) Automatically enabling devices
[ 343.171] (**) Xinerama: enabled
But there is no mention of 'Rightof' anywhere in the file so that instruction was not picked up. How should one put that command into say, the monitor section or screen section? Anyway, i tried putting into both monitor1 and screen1 section, the following:
Option "RightOf" "Monitor0"

Log file now says
[ 77.716] (**) VESA(0): DPMS enabled
[ 77.716] (WW) VESA(0): Option "PreferredMode" is not used
[ 77.716] (WW) VESA(0): Option "RightOf" is not used
[ 77.716] (**) RandR enabled
Does it mean 'not allowed' instead of not used?

Maybe i should try these other ideas found on the web:

Screen "Screen 3" Relative "Screen 1" 2048 0
Screen 1 "Screen 2" Absolute 1024 0

Sigh, starting to feel like that monkey again.

I did download the driver you mentioned, but can't understand biltoo's instructions on how to install it/ modify xorg or whatever. It has a .run extension. Where should i place it? Will it know anything about puppy directories? Seems quite risky, no?

FWIW, here is the log file when using XVESA. It's that 'Rightof' command. What's stopping xorg from recognizing it?
Attachments
xorgLogVesa.zip
(11.88 KiB) Downloaded 422 times
[color=orange]1. Dell Dimension E521, AMD Athln 64, 2 GHz 1.93GB ram,
Puppy 533 on CD, accesses flash drive only,
FFox Nightly12.0
2. Compaq P3 733Hz 375RAM
Printer: Oki C3400 > LAN [/color]

User avatar
Karl Godt
Posts: 4199
Joined: Sun 20 Jun 2010, 13:52
Location: Kiel,Germany

#27 Post by Karl Godt »

The .run files are archives, often compressed, that have a preceding attached shell script.

bash-3.00# head ati-driver-installer-8-6-x86.x86_64.run
for example gives me
#!/bin/sh
# This script was generated using Makeself 2.1.3
CRCsum="59668481"
MD5="03c98c731cf5a752d69add8fa024025e"
TMPROOT="fglrx-install"

label="ATI Proprietary Linux Driver-8.501"
script="./ati-installer.sh"
scriptargs=""
so it needs to be set executable ie right click > Permissions.

Installing such driver requires the kernel sources.sfs from here :

http://distro.ibiblio.org/pub/linux/dis ... uppylinux/
pet_packages-slacko/

where i get a 403 Forbitten atm .

Then the kernel sources.sfs has to be mounted "on the fly" or by "bootmanager incl. reboot" .

Then you should exit to promt. Navigate to the ati-driver download directory by

Code: Select all

cd /path/to/download
ie /root/Downloads/AMD-Driver/ .
Then you have to execute the .run file by

Code: Select all

./ati-version.run
Follow the instructions.

I have not done it before. Am downloading some amd and nvidia drivers for compiling them if i compile a new kernel .

Good Luck !

[For the other i have to change the box to boot a xorgwizard-automatic Puppy . Open /usr/bin/xwin in geany and change xorgwizard-automatic you find to xorgwizard. This would at least give you a little more control. The changes get saved in the pup-save.3fs -save-file.]

[Another thing : Xvesa is a special Xorg SERVER. This is included in Puppy 4.3.1 by default. NOT in Puppy 5 series anymore. You have chosen the Xorg vesa_drv.so -driver.]

User avatar
Monsie
Posts: 631
Joined: Thu 01 Dec 2011, 07:37
Location: Kamloops BC Canada

Dual Monitor setup for desktop..... (unresolvable?)

#28 Post by Monsie »

Hi canbyte,

You are still hanging in there... :) Well I am still up for the challenge... because it involves computing. :wink: If it involved fixing something in my house that was giving me this much frustration, I probably would have thrown in the proverbial towel a long time ago. :roll:

Anyway... so you are saying that you are using an adapter that allows you to run dvi --> vga? I assume that you have also tried to run a straight dvi --> dvi connection? And if so, what differences have you noticed? Also, I notice two different drivers listed in your latest xorg.conf so I think you'll want to fix that. Once you've done that, see what output you get at the terminal with these two commands separately:

Code: Select all

xdriinfo
xdriinfo nscreens
At this point in troubleshooting, we seem to be at a crossroads of sorts... either carry on with the open source driver and configuration, or try the proprietary driver along with a new configuration. Actually, you could continue to try both methods if you like. :wink: Speaking personally, I favor an eclectic approach along with having user choices available... the bottom line being that if it works for you, then go with it... maybe this way we can work out a solution a bit faster. An aside --some guys are picky about running FOSS so they run a distro such as Fedora... speaking of which, I did see a post of someone who got dual monitor support in Fedora while using the Radeon 9200 card, but I'll hold off on including that specific info for now, as it is four or five years old which I thought might be out of date here.

That said, I managed to find a fairly recent post in the Ubuntu forums of someone who managed to get dual monitor support with the Ati Radeon 9200 card while using the open source driver: http://ubuntuforums.org/showthread.php?t=1654653 and I noticed a couple of interesting (new) changes... so have a look at that. This person was running Ubuntu 10.10 so it was with Kernel 2.6.35 and Xorg 1.9.0

Somewhere in my research (I have since lost the web page unfortunately) I read that the proprietary driver will give better support for a dual monitor arrangement and is easier to set up --all things considered.

I've never installed a proprietary driver in Puppy, but have done so on my Debian desktop. In Debian, I have been able to launch a file with the .run extension by running the sh command to start the attached shell script that Karl is talking about. However, since run files are basically binary packages, I have also launched them by re-naming the file to the .bin extension. I've done this with the GoogleEarth run package, for instance, because doing so changes the location of where the program is installed --I think to the /opt directory for GoogleEarth (instead of my home directory) if I remember correctly. I don't know if this method works in Puppy or not.

In any event, if you are successful with installing the proprietary driver, I understand that you will have to take out the configuration for Xinerama in Xorg.conf because apparently the new driver will have this support built in, or will auto configure a new Xorg.conf accordingly --not sure which.

Monsie
My [u]username[/u] is pronounced: "mun-see". Derived from my surname, it was my nickname throughout high school.

User avatar
canbyte
Posts: 264
Joined: Sat 10 Jan 2009, 20:20
Location: Hamilton, Canada

#29 Post by canbyte »

Hi Monsie. Thanks to both of you for putting up with my noobiness. Your post is stretching me to the limit - or beyond! I'm running windoz at the moment so I'll just respond to some items and re-edit later.

The ASUS monitor has a second cable/ connector but it's a small thing (~1/2" across) and says HDMI on it (for TV?). So I wouldn't know how to deal with dvi connection - and would be reluctant to mess with the windows setup which was done at the 'puter store that installed the card. Bein' a noob and all! I'm also kinda nervous about the proprietary driver because of what it might do to the rest of the os?? and complicated, noobwise. If i get desperate......

The ubuntu suggestion looks interesting. Is the format of his xorg.conf compatible?? ie. Notice he only has one screen and one device section (which does make sense to me).
Option "Monitor-DVI-0" "Acer"
Virtual 2880 900
I've had trouble with the virtual command but was putting an x in between the numbers. Anyway, i'll try it later on this aft.

I just re-read this para in pizza's post
http://www.murga-linux.com/puppy/viewto ... 477#357477
which seems to suggest why the xorgwizard isn't picking up the second screen (ignoring the ubuntu logic for a moment).
One more change needs to be made to prevent that second change from interfering with the first. In the first one, the # should be removed from inside the grep. Without doing that, Xorg will still start just fine because the additional lines in the Server section will be commented out, but xorgwizard won't bother to create the additional Screen sections. It doesn't hurt to fix it so that it does create them, and that way somebody like me who actually wants to use them just has to uncomment the appropriate line in the Server section, and not have to also create the Screen section.
Maybe Karl can also chime in on that as it resonates with one of his posts. What's a grep?

Thanks again.
[color=orange]1. Dell Dimension E521, AMD Athln 64, 2 GHz 1.93GB ram,
Puppy 533 on CD, accesses flash drive only,
FFox Nightly12.0
2. Compaq P3 733Hz 375RAM
Printer: Oki C3400 > LAN [/color]

User avatar
Monsie
Posts: 631
Joined: Thu 01 Dec 2011, 07:37
Location: Kamloops BC Canada

Dual Monitor setup for desktop..... (unresolvable?)

#30 Post by Monsie »

canbyte,

Thanks for clarifying your monitor connections. Since your Asus Monitor is quite new, it has the hdmi connection instead. I wouldn't bother trying to get an adapter to hook it up, because it is for high definition. If you had a newer graphics card that needed the radeonhd driver, for example, then it would be of use to you.

Yes, I did notice the difference in the number of device and screen sections shown in the Xorg.conf file by the person@ Ubuntu Forums. I think the reason he only has one screen section is because he is using the "virtual" option which effectively combines both monitors to work as a unit. As for the single device section... my guess is that some of the specs may have changed with Xorg and this is some of the challenge with researching this stuff... configurations that have worked are now out of date because some package is deprecated, specs are different now etc. My thought is that the Ubuntu configuration might work for you, since the Xorg version is close to what you have --I believe So, I would definitely modify your existing Xorg.conf file and give it a go.

As for "grep" it is basically a powerful search command. While it can be used by itself, I usually use it in conjunction with another command to get what I am looking for:

Code: Select all

lspci | grep VGA
01:00.0 VGA compatible controller: ATI Technologies Inc Rage 128 Pro Ultra TF
which gives me the exact model of my graphics card. Note that VGA must be in capitals.

Code: Select all

xdpyinfo | grep resolution
  resolution:    86x84 dots per inch
This gives me the dpi setting of my monitor. Anyway, in the quote by Pizzasgood, I believe he was using the term "grep" more loosely to refer to the search parameters defined by the code.

Monsie
My [u]username[/u] is pronounced: "mun-see". Derived from my surname, it was my nickname throughout high school.

User avatar
Karl Godt
Posts: 4199
Joined: Sun 20 Jun 2010, 13:52
Location: Kiel,Germany

#31 Post by Karl Godt »

about the "grep" :

Code: Select all

pman grep
should present something like this : http://unixhelp.ed.ac.uk/CGI/man-cgi?grep
grep is a common linux command for the shell.

Code: Select all

-SCRNSECTION="
+#handle multiple screens
+SCREEN_LIST=$(grep -o '^[^a-zA-Z]*Screen[^"]*"Screen[0-9]\+"' /etc/X11/xorg.conf | grep -o 'Screen[0-9]\+' | grep -o '[0-9]\+')
+SCRNSECTION=""
+for i in $SCREEN_LIST; do
+SCRNSECTION="$SCRNSECTION
 Section \"Screen\"
-	Identifier \"Screen0\"
-	Device     \"Card0\"
-	Monitor    \"Monitor0\"
-    DefaultDepth $FINALDEPTH
-    Subsection \"Display\"
-        Depth       $FINALDEPTH
-        Modes       \"${FINALXY}\"
-    EndSubsection
+	Identifier \"Screen$i\"
+	Device     \"Card$i\"
+	Monitor    \"Monitor$i\"
+	DefaultDepth $FINALDEPTH
+	Subsection \"Display\"
+		Depth       $FINALDEPTH
+		Modes       \"${FINALXY}\"
+	EndSubsection
 EndSection
 "
+done
 echo "$SCRNSECTION" >> /etc/X11/xorg.conf
is interesting code for me. Thanks for digging it up.

This code should create a monitor section for the monitors

Code: Select all

grep -o '^[^a-zA-Z]*Screen[^"]*"Screen[0-9]\+"' /etc/X11/xorg.conf | grep -o 'Screen[0-9]\+' | grep -o '[0-9]\+'
that are written into xorg.conf .
Simply

Code: Select all

grep -o '^[^a-zA-Z]*Screen[^"]*"Screen[0-9]\+"' /etc/X11/xorg.conf
in my one monitor setup it is :

Code: Select all

	Screen      0  "Screen0"
and

Code: Select all

grep -o '^[^a-zA-Z]*Screen[^"]*"Screen[0-9]\+"' /etc/X11/xorg.conf | grep -o 'Screen[0-9]\+' | grep -o '[0-9]\+'
gives

Code: Select all

0
So it should be

Code: Select all

for monitor in 0 1;do
SCRNSECTION="$SCRNSECTION
 Section \"Screen\"
	Identifier \"Screen$monitor\"
	Device     \"Card$monitor\"
	Monitor    \"Monitor$monitor\"
	DefaultDepth $FINALDEPTH
	Subsection \"Display\"
		Depth       $FINALDEPTH
		Modes       \"${FINALXY}\"
	EndSubsection
 EndSection
 "
done
 echo "$SCRNSECTION" >> /etc/X11/xorg.conf
to create two monitor sections.

These two monitors must be inside xorg.conf already at this stage.

One problem to me is that the whole xorgwizard seems to need "for loops" also for the different FINALDEPTH and FINALXY of the monitors, if there is a program available - besides ddcprobe - to detect them .

User avatar
Karl Godt
Posts: 4199
Joined: Sun 20 Jun 2010, 13:52
Location: Kiel,Germany

#32 Post by Karl Godt »

BTW, Karl said Racy-5.3 has Xorg-server 1.11.x . How can i determine if Slacko has the same? I see in my xorgwizard:

Code: Select all

Xorg -version
in urxvt console.

User avatar
canbyte
Posts: 264
Joined: Sat 10 Jan 2009, 20:20
Location: Hamilton, Canada

SOLUTION!!!

#33 Post by canbyte »

edit - New visitors - let's make this thread a 'one-stop' for others (and resource for developers) by adding your card info and how it works or doesn't, what you did about it and tweaks for different resolutions, etc. If extended pages are added, pm me and i'll put pointers in the first post. Thanks
--------------------------------------------------------------------------



Bad news, good nows,,,,, broke finger today so hard ta type right,,, bummur

Good nows, got proper extended screen working using the ubuntu idoa in earlier link from monsie

here are changes to /etc/x11/xorg,conf:
paste the following just after the line that says :
#everything past here is auto-generated by Puppy's Xorg Wizard...
edit: this line isn't aways present, in which case, just start replacing at the first line in the following.

(overwrite to end of file - except last line which is your info for reference)
and after pasting, change card details, monitor names, etc. EDIT: monitor section for old crt monitors at end of post.
Section "ServerLayout"
Identifier "Xinerama Screen"
Screen 0 "Screen0" 0 0
# Screen 1 "Screen1" RightOf "Screen0" yup, this line goes below!
Option "Xinerama" "true"
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection


Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc102"
Option "XkbLayout" "us" #xkeymap0
# Option "XkbVariant" "dvorak"
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2" #mouse0protocol
Option "Device" "/dev/mouse"
#Option "Emulate3Buttons"
#Option "Emulate3Timeout" "50"
Option "ZAxisMapping" "4 5" #scrollwheel
EndSection

Section "Monitor"
#DisplaySize 410 260 # mm
Identifier "acer"
VendorName "ACR"
ModelName "Acer AL1916W"
Option "DPMS"
HorizSync 30.0-82.0
VertRefresh 56.0-72.0
#UseModes "Modes0" #monitor0usemodes
Option "PreferredMode" "1024x768"
EndSection

Section "Modes"
Identifier "Modes0"
#modes0modeline0
EndSection


Section "Monitor"
Identifier "asus"
#DisplaySize 520 290 # mm
VendorName "ACI"
ModelName "ASUS VH242H"
Option "DPMS"
HorizSync 30.0-85.0
VertRefresh 55.0-71.0
#UseModes "Modes0" #monitor0usemodes
Option "PreferredMode" "1024x768"
Option "RightOf" "acer"
EndSection



Section "Device"
Identifier "Card0"
Driver "Radeon"
Option "Monitor-VGA-0" "acer"
Option "Monitor-DVI-0" "Asus"
BusID "PCI:4:9:0"
EndSection


Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "acer"
Monitor "asus"
DefaultDepth 16
Subsection "Display"
Virtual 2048 768
Depth 16
# Modes "1024x768"
EndSubsection
EndSection

#PuppyHardwareProfile=ATI_RADEON_9200AcerAL1916W
edit Sept 30, - when running under Lupu 528, the colours went wonky and needed to be set at 24, not 16. After changing the Depth parameter above to 24, the colours got better but the larger screen (ASUS) is too light / washed out so maybe there's a way to fix that


easier to comment out than retype - It's really time for a beer!

edit - note the vga / dvi commands in device section - makes sense, since the card doesn't know the dvi-vga adaptor is there.
also note that rightof is in quote marks, not sure if required but aint gonna fool with it now!! As noted earlier, I never got 'leftof' to do anything but crash but maybe it works now - but not trying it!!

i assume i can remove all lines starting # or ## or ###?? does it matter if # is not at start of line? edit - seems so, i just did.


Here is what xorg -version says in answer to Karl's question
# xorg -version
bash: xorg: command not found
# Xorg -version

X.Org X Server 1.9.5
Release Date: 2011-03-17
X Protocol Version 11, Revision 0
Build Operating System: Slackware 13.37 Slackware Linux Project
Current Operating System: Linux puppypc12547 3.1.10-slacko_4gA #1 SMP Tue Mar 13 14:58:11 EST 2012 i686
Kernel command line: video=640x480 initrd=initrd.gz pmedia=cd BOOT_IMAGE=vmlinuz
Build Date: 18 March 2011 12:08:03AM

Current version of pixman: 0.20.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
#

i didn't got into tho grep stuff as i was hoping to avoid anything non-noob which thankfully worked out, Thanks a bailout for all your holp and monsie and maarten256 from ubuntuforum,org too, i bottor not count chickons befor hatching so better go now to save everything,

edit - reboot, restart completed, still working, i'll go above and take out commented lines mostly but leave a few so noobs see what's not needed.
PS. I'll attach the working log file in case it is useful.


Thanks again
Choors!

EDIT JAN 2013: Am fooling around with 2nd setup using old monitors in a different section of the house. One monitor is an old CRT type. Here is the section that handles that ok. You'll notice an easier protocol for naming monitors which needs the rest to be changed accordingly.
Section "Monitor"
#DisplaySize 410 260 # mm
Identifier "monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
Option "DPMS"
HorizSync 35-81
VertRefresh 59-76
#UseModes "Modes0" #monitor0usemodes
Option "PreferredMode" "1024x768"
EndSection
If Monsie happens to catch this, I'm having hardware problems so i've hand to shelve getting a new / old pc to support dual monitors until i find a cheap box that will run it in both windows and puppy. The old P3 couldn't handle the nvidia card so i took it out and gave up. Back as situation develops. [/quote]
Attachments
dualScreenGoodLog.zip
(11.28 KiB) Downloaded 487 times
Last edited by canbyte on Tue 29 Jan 2013, 16:37, edited 6 times in total.
[color=orange]1. Dell Dimension E521, AMD Athln 64, 2 GHz 1.93GB ram,
Puppy 533 on CD, accesses flash drive only,
FFox Nightly12.0
2. Compaq P3 733Hz 375RAM
Printer: Oki C3400 > LAN [/color]

User avatar
Karl Godt
Posts: 4199
Joined: Sun 20 Jun 2010, 13:52
Location: Kiel,Germany

#34 Post by Karl Godt »

It's really time for a beer!
+1
Second that.
Congrats !

User avatar
canbyte
Posts: 264
Joined: Sat 10 Jan 2009, 20:20
Location: Hamilton, Canada

#35 Post by canbyte »

cheers ...
small gremlin crept in - on boot or xwin, the desktop opens with a dialog box saying SFS-load-on-fly. I can't recall opening this (probably from install package). No big deal but where to look to stop it from opening??
[color=orange]1. Dell Dimension E521, AMD Athln 64, 2 GHz 1.93GB ram,
Puppy 533 on CD, accesses flash drive only,
FFox Nightly12.0
2. Compaq P3 733Hz 375RAM
Printer: Oki C3400 > LAN [/color]

User avatar
Karl Godt
Posts: 4199
Joined: Sun 20 Jun 2010, 13:52
Location: Kiel,Germany

#36 Post by Karl Godt »

In former times the

/usr/sbin/delayedrun

was used to launch

Code: Select all

bootmanager extrasfs quiet
if some extra .sfs were detected somewhere.

Am running full mainly.

User avatar
Monsie
Posts: 631
Joined: Thu 01 Dec 2011, 07:37
Location: Kamloops BC Canada

Dual Monitor setup for desktop ..... (solved)

#37 Post by Monsie »

Hi canbyte,

Way to go! You managed to hang in there :D

When you are able to type better, please consider posting your Xorg.conf in a condensed write-up for future reference. I'm sure there are many others who would be interested in running a dual monitor setup at some point (myself included). This could save users a lot of time spent searching for answers, and so the community will benefit overall.

Congrats,
Monsie
My [u]username[/u] is pronounced: "mun-see". Derived from my surname, it was my nickname throughout high school.

User avatar
canbyte
Posts: 264
Joined: Sat 10 Jan 2009, 20:20
Location: Hamilton, Canada

#38 Post by canbyte »

Thanks Monsie, what a relief! For now I've edited the first post and the solution above so users can hopefully navigate easily - and who knows, the junk might be useful if someone is having problems with the final setup.

Also thanks Karl - i made a file like you suggested. Presumably it worked - the gremlin went away! All's well that ends well.

:)
[color=orange]1. Dell Dimension E521, AMD Athln 64, 2 GHz 1.93GB ram,
Puppy 533 on CD, accesses flash drive only,
FFox Nightly12.0
2. Compaq P3 733Hz 375RAM
Printer: Oki C3400 > LAN [/color]

DarwinIcesurfer
Posts: 1
Joined: Sat 08 Sep 2012, 22:25

ATI Driver 12.4 and GUI work for Radeon 3200

#39 Post by DarwinIcesurfer »

I spent a significant amount of time trying to get a dual monitor setup in place for my HP dv7 laptop with a ATI Radeon 3200 video chip. While this thread was very useful to understand all the settings in the xorg.conf file, I found the easiest way to get the system working was to use the prebuilt ATI drivers and the ATI Catalyst GUI. I found the .pet at http://distro.ibiblio.org/puppylinux/pe ... es-slacko/ under amd_fglrx which surprised me because I was looking for ATI or Catalyst. It turns out that amd acquired ATI and the fglrx is the open source version of Catalyst. After installing Catalyst I had to reboot the system and it told me that I should run aticonfig -- initial from a terminal upon reboot. While that program can be used to change the xorg.conf file, I found it much easier to use the Catalyst GUI that was installed under menu-> system -> (I forgot the title of the next menu) -> ATI Catalyst.

I initially didn't want to use the 12.4 driver because there were notes in the ATI documentation that the old radeon chip driver support ended with [?? somewhere below 10, can't find exact quote ??]. However in some later posts I found that ATI had reversed their decision and was now supporting my old Radeon chip in the 12.4 (and perhaps newer) drivers.

I hope that this post may save someone else a few hours trying to get a dual monitor setup for their ATI based system.

One annoying thing about the ATI driver is that the taskbar is forced onto the monitor that is connected to the laptop rather than on the laptop, this is unfortunate if you want to use a projector. If anyone has a solution to that I'd appreciate hearing about it!

User avatar
canbyte
Posts: 264
Joined: Sat 10 Jan 2009, 20:20
Location: Hamilton, Canada

#40 Post by canbyte »

Well, here i am again, trying to get a dual screen working on my old compaq p3 with a nvidia 8400gs installed. I tried the same mods to xorg.conf as per the above post (see below) but without success. It just doesn't want to recognize the 'virtual' command to form a contiguous screen.

Here's the changes to my xorg.conf so far. Much appreciated any thoughts as to what to try next. You can see some trials that i commented out with #. Below I'll ask about nvidia drivers.


Section "ServerLayout"
Identifier "X.org Configured"
#Identifier "Twinview Screen"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc102"
Option "XkbLayout" "dvorak" #xkeymap0
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2" #mouse0protocol
Option "Device" "/dev/mouse"
#Option "Emulate3Buttons"
#Option "Emulate3Timeout" "50"
Option "ZAxisMapping" "4 5" #scrollwheel
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
HorizSync 31.5-48.5
VertRefresh 40-70
#UseModes "Modes0" #monitor0usemodes
Option "PreferredMode" "1024x768"
EndSection

Section "Modes"
Identifier "Modes0"
#modes0modeline0
EndSection

Section "Monitor"
Identifier "Monitor1"
#DisplaySize 520 290 # mm
VendorName "Dell"
ModelName "Dell"
Option "DPMS"
HorizSync 30.0-85.0
VertRefresh 55.0-71.0
#UseModes "Modes0" #monitor0usemodes
Option "PreferredMode" "1024x768"
Option "RightOf" "monitor0"
EndSection

Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
### <percent>: "<f>%"
### [arg]: arg optional
#Option "SWcursor" # [<bool>]
#Option "HWcursor" # [<bool>]
#Option "NoAccel" # [<bool>]
#Option "ShadowFB" # [<bool>]
#Option "UseFBDev" # [<bool>]
#Option "Rotate" # [<str>]
#Option "VideoKey" # <i>
#Option "FlatPanel" # [<bool>]
#Option "FPDither" # [<bool>]
#Option "CrtcNumber" # <i>
#Option "FPScale" # [<bool>]
#Option "FPTweak" # <i>
#Option "DualHead" # [<bool>]
Identifier "Card0"
Driver "nv" #card0driver
BusID "PCI:3:0:0"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Card0"
Option "Twinview"
Monitor "Monitor0"
Monitor "Monitor1"
DefaultDepth 24
#Option "metamodes" "1024x768_60 +0+0" #METAMODES_0
Subsection "Display"
Depth 24
Virtual 2048 768
# Twinview 2048 768
# Screen "2048x768"
# virtual "2048x768"
Modes "1024x768"
# Modes "Twinview"
EndSubsection
EndSection

#PuppyHardwareProfile=NVIDIA

Nvidia has drivers on this page but I need help with understanding the instructions (what is the puppy equivalent).
http://www.geforce.com/drivers/results/52240

Also, I'm a little reluctant to install commercial drivers and am hoping that the above code can be made to work as it did for my other machine.

Installation instructions: Once you have downloaded the driver, change to the directory containing the driver package and install the driver by running, as root, sh ./NVIDIA-Linux-x86-310.19.run

One of the last installation steps will offer to update your X configuration file. Either accept that offer, edit your X configuration file manually so that the NVIDIA X driver will be used, or run nvidia-xconfig

Thanks in advance.
[color=orange]1. Dell Dimension E521, AMD Athln 64, 2 GHz 1.93GB ram,
Puppy 533 on CD, accesses flash drive only,
FFox Nightly12.0
2. Compaq P3 733Hz 375RAM
Printer: Oki C3400 > LAN [/color]

Post Reply