Hi Karl
All i found in /etc/modprobe.d/ was radeon.conf and a few other files.

All radeon.conf contained was

Quote:

options radeon modeset=0

Somewhere i saw a reference to nouveau. nouveau.conf contains

Quote:

options nouveau modeset=1

You seem to be zeroing in on the problem - surely this setup has to involve many settings. Should I copy the code you quoted into the Radeon.conf file? As is (minus the numbers starting each line?). Well, I'll post this and give it a try, making the change you suggested. I'll post if it works, otherwise i'll reset to original. edit - that change made no difference but didn't do any harm either! So it's still there.

Hi Karl
All i found in /etc/modprobe.d/ was radeon.conf and a few other files.

All radeon.conf contained was

Quote:

options radeon modeset=0

Somewhere i saw a reference to nouveau. nouveau.conf contains

Quote:

options nouveau modeset=1

You seem to be zeroing in on the problem - surely this setup has to involve many settings. Should I copy the code you quoted into the Radeon.conf file? As is (minus the numbers starting each line?). Well, I'll post this and give it a try, making the change you suggested. I'll post if it works, otherwise i'll reset to original.

I'm using Slacko 5.3.3. I only downloaded racy to see if it was any better and since Barry mentioned Pizza's code being incorporated into Woof 2. Slacko seems more advanced and seems to incorporate Pizza's code as well.

No, then i would change modeset=0 to modeset=1

modeset=0 practically means in my experience that if you boot with vga=normal then if the driver loads the sreen still stays 80x25 at boottime but modeset=1 makes the driver setting a mode like 132x60. Don't know if this affects other things .

Hmmm as i see there is a
kernel/drivers/gpu/drm/radeon/radeon.ko by "default" . What's your extra ati driver called again ?

I tried changing modeset=1 in radeon.conf but no change, no problems. I found the radeon.ko in /lib/modules/3.1.10-slackoS4ga/kernel/drivers/gpu/drm/radeon directory. Is that what you mean by extra radeon drivers? I'll search around a bit and let you know if anything else turns up.

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 username is pronounced: "mun-see". Derived from my surname, it was my nickname throughout high school.

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?

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.

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:

Quote:

#110701 synaptics stuff seems to clash with xorg-server 1.10.1.

Xorg.conf text with two different screens - just not positioned properly.

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.

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?

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

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"

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?

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:

cd /path/to/download

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

Code:

./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.]

You are still hanging in there... Well I am still up for the challenge... because it involves computing. 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.

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:

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. 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 username is pronounced: "mun-see". Derived from my surname, it was my nickname throughout high school.

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.

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 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:

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum