Dual Monitor setup for desktop .....Don't delay, step on up!
Dual Monitor setup for desktop .....Don't delay, step on up!
Keywords: Dual screen, extended screen, dual port graphics card, vga/ dvi, multiple screens, multiple graphics cards, ATI radeon, Nvidia, twinview, xinerama.
Just got a flatscreen monitor for 5 bucks at a garage sale. It even works! Local shop had a used dual port card for $30.
Why have a dual screen? Awesome! You'll never go back. For research, spreadsheets, games, convenience, artwork, CAD, efficiency, etc. Cutting /pasting much easier.
Rant: Q. Why are so many newer web pages unable to size down onto a smaller window?
A. Follow the money - their ads don't show properly. It's all about them, not about you. End Rant.
Searching on this topic, it seems most entries are old, or for laptops. There was some mention of incorporating dual monitor into Puppy but so far, I haven't found anything in the menu.
First I identified the video card. Slickpet easily probed my system and reported the following:
ATI RV280 (Radeon 9200 SE Rev1). It has two output jacks - a vga and a dvi - for which i got an adapter. This means that one output is dvi.
Until Puppy upgrades xorgwizard, one must edit /etc/x11/xorg.conf. There are several threads, some very long/ too complex for a noob to figure out and was nervous about just copy/pasting the whole thing which may be for a different puppy, etc.
Caution: messing with xorg can cause puppy to crash and be unable to start up again as I found out the hard way. Fortunately John Doe was able to point out that if your modified xorg stops in startup leaving you at a prompt, you just type 'xorgwizard' and then after it has finished, 'xwin', to continue the startup. You should still backup your pup_save file since if the screen goes wonky, you may not be able to recover - as i learned the hard way - again!
edit - well, there is a way - during bootup, hit F2 key when instructed, enter
puppy pfix=nox
this will eventually get to a prompt where you can enter 'xorgwizard' as above
edit2 - umm, seems i lost my printer setup so better save the _save file after all.
There are 4 things to change in xorg - server layout, screen, monitor and device, and you must tell Puppy that screen1 is left or right of screen0 (the default is all screens showing same image). Order seems not to be important. But for some reason, leftof never worked so just use rightof.
Also note that while the solution arrived at seems general in nature, it may be only applicable to my particular video card. Well, I mean the format is what hopefully works for you, specific details must naturally change to suit your machine.
Thanks to Monsie and Karl Godt for their invaluable help - and patience with this noob.
Edit - Getting the Nvidia card to work was a whole different story.
************************* masochists read on, all others hit this next link for ATI and other cards,
http://www.murga-linux.com/puppy/viewto ... 0&start=33
or the following for nvidia cards
http://www.murga-linux.com/puppy/viewto ... 0&start=50
although you'll have to work back a bit too.
----------------------------------------------------------------------------------------------------------
Mazes - what follows is the bowels of my researches and howls of my discontent and the helpful comments that ultimately led to success. Proceed at your own risk!
Here's the links found so far with a brief notation.
http://www.murga-linux.com/puppy/viewtopic.php?t=74601
for laptop based on the Navidia card not the ATI Radeon that I have. Also the instructions there were meant for experts - I'll need something more detailed. It mentioned twinview, openbox, Compiz/Beryl, xfce but I don't know what to do with this info.
http://www.murga-linux.com/puppy/viewtopic.php?t=18073
another thread (for laptop) I can't seem to follow - but may well have the solution (in sublinks)
http://www.murga-linux.com/puppy/viewtopic.php?t=9013
a more basic/ helpful thread which I'm trying to follow
- but not too successfully. I think there is a syntax problem.
http://www.murga-linux.com/puppy/viewto ... aaf48078b8
Lobster says future puppies will fix this and gives a link (below) for code to insert.
http://bkhome.org/blog/?viewDetailed=01213
Barry's Blog. He gives a link to Pizzagood's code but link is broken. I've asked Barry for a repost and will post here when available. Apparently it was put in Woof but not Slacko??
http://www.murga-linux.com/puppy/viewto ... ba3e7e97e8
A more complex setup but easily understood. Not sure how to change all the variables.
http://www.murga-linux.com/puppy/viewtopic.php?t=16086
Very complex. Long post. Can't decipher it.
Well, that's as far as I've got so maybe I'll stop and post, especially as the larger monitor just blinked out (no signal). Seems not to be liking whatever I've done so hopefully some kind soul will come along!! Hoping also I didn't bust anything.
So, what am I doing wrong? Why is larger monitor turning off after some minutes?
Just got a flatscreen monitor for 5 bucks at a garage sale. It even works! Local shop had a used dual port card for $30.
Why have a dual screen? Awesome! You'll never go back. For research, spreadsheets, games, convenience, artwork, CAD, efficiency, etc. Cutting /pasting much easier.
Rant: Q. Why are so many newer web pages unable to size down onto a smaller window?
A. Follow the money - their ads don't show properly. It's all about them, not about you. End Rant.
Searching on this topic, it seems most entries are old, or for laptops. There was some mention of incorporating dual monitor into Puppy but so far, I haven't found anything in the menu.
First I identified the video card. Slickpet easily probed my system and reported the following:
ATI RV280 (Radeon 9200 SE Rev1). It has two output jacks - a vga and a dvi - for which i got an adapter. This means that one output is dvi.
Until Puppy upgrades xorgwizard, one must edit /etc/x11/xorg.conf. There are several threads, some very long/ too complex for a noob to figure out and was nervous about just copy/pasting the whole thing which may be for a different puppy, etc.
Caution: messing with xorg can cause puppy to crash and be unable to start up again as I found out the hard way. Fortunately John Doe was able to point out that if your modified xorg stops in startup leaving you at a prompt, you just type 'xorgwizard' and then after it has finished, 'xwin', to continue the startup. You should still backup your pup_save file since if the screen goes wonky, you may not be able to recover - as i learned the hard way - again!
edit - well, there is a way - during bootup, hit F2 key when instructed, enter
puppy pfix=nox
this will eventually get to a prompt where you can enter 'xorgwizard' as above
edit2 - umm, seems i lost my printer setup so better save the _save file after all.
There are 4 things to change in xorg - server layout, screen, monitor and device, and you must tell Puppy that screen1 is left or right of screen0 (the default is all screens showing same image). Order seems not to be important. But for some reason, leftof never worked so just use rightof.
Also note that while the solution arrived at seems general in nature, it may be only applicable to my particular video card. Well, I mean the format is what hopefully works for you, specific details must naturally change to suit your machine.
Thanks to Monsie and Karl Godt for their invaluable help - and patience with this noob.
Edit - Getting the Nvidia card to work was a whole different story.
************************* masochists read on, all others hit this next link for ATI and other cards,
http://www.murga-linux.com/puppy/viewto ... 0&start=33
or the following for nvidia cards
http://www.murga-linux.com/puppy/viewto ... 0&start=50
although you'll have to work back a bit too.
----------------------------------------------------------------------------------------------------------
Mazes - what follows is the bowels of my researches and howls of my discontent and the helpful comments that ultimately led to success. Proceed at your own risk!
Here's the links found so far with a brief notation.
http://www.murga-linux.com/puppy/viewtopic.php?t=74601
for laptop based on the Navidia card not the ATI Radeon that I have. Also the instructions there were meant for experts - I'll need something more detailed. It mentioned twinview, openbox, Compiz/Beryl, xfce but I don't know what to do with this info.
http://www.murga-linux.com/puppy/viewtopic.php?t=18073
another thread (for laptop) I can't seem to follow - but may well have the solution (in sublinks)
http://www.murga-linux.com/puppy/viewtopic.php?t=9013
a more basic/ helpful thread which I'm trying to follow
- but not too successfully. I think there is a syntax problem.
http://www.murga-linux.com/puppy/viewto ... aaf48078b8
Lobster says future puppies will fix this and gives a link (below) for code to insert.
http://bkhome.org/blog/?viewDetailed=01213
Barry's Blog. He gives a link to Pizzagood's code but link is broken. I've asked Barry for a repost and will post here when available. Apparently it was put in Woof but not Slacko??
http://www.murga-linux.com/puppy/viewto ... ba3e7e97e8
A more complex setup but easily understood. Not sure how to change all the variables.
http://www.murga-linux.com/puppy/viewtopic.php?t=16086
Very complex. Long post. Can't decipher it.
Well, that's as far as I've got so maybe I'll stop and post, especially as the larger monitor just blinked out (no signal). Seems not to be liking whatever I've done so hopefully some kind soul will come along!! Hoping also I didn't bust anything.
So, what am I doing wrong? Why is larger monitor turning off after some minutes?
Last edited by canbyte on Wed 13 Mar 2013, 13:37, edited 26 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]
Puppy 533 on CD, accesses flash drive only,
FFox Nightly12.0
2. Compaq P3 733Hz 375RAM
Printer: Oki C3400 > LAN [/color]
Seems very interesting. I hope you continue we do need this kind of threads.
Re on of the links
http://www.murga-linux.com/puppy/viewto ... 1783935379
that way it works better or why not just like this
http://www.murga-linux.com/puppy/viewtopic.php?t=74601
Re on of the links
http://www.murga-linux.com/puppy/viewto ... 1783935379
that way it works better or why not just like this
http://www.murga-linux.com/puppy/viewtopic.php?t=74601
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
Interesting .
I got me a splitter today and the main problem turns out to be the " ddcprobe " command used in xorgwizard and xwin .
bash-3.00# ddcprobe
vbe: VESA 3.0 detected.
oem: NVIDIA
vendor: NVIDIA Corporation
product: NV18 Board Chip Rev A2
memory: 65536kb
mode: 640x400x256
mode: 640x480x256
mode: 800x600x16
mode: 800x600x256
mode: 1024x768x16
mode: 1024x768x256
mode: 1280x1024x16
mode: 1280x1024x256
mode: 80x60 (text)
mode: 132x25 (text)
mode: 132x43 (text)
mode: 132x50 (text)
mode: 132x60 (text)
mode: 320x200x64k
mode: 320x200x16m
mode: 640x480x64k
mode: 640x480x16m
mode: 800x600x64k
mode: 800x600x16m
mode: 1024x768x64k
mode: 1024x768x16m
mode: 1280x1024x64k
mode: 1280x1024x16m
edid:
edid: 1 2
id: 0710
eisa: ANC0710
serial: 00010100
manufacture: 40 2000
input: sync on green, analog signal.
screensize: 32 24
gamma: 2.200000
dpms: RGB, active off, suspend, standby
timing: 640x480@60 Hz (VGA)
timing: 640x480@75 Hz (VESA)
timing: 800x600@60 Hz (VESA)
timing: 800x600@72 Hz (VESA)
timing: 800x600@75 Hz (VESA)
timing: 1024x768@75 Hz (VESA)
ctiming: 256x256@60
ctiming: 256x192@60
ctiming: 256x192@69
ctiming: 256x192@69
dtiming: 1024x0@2007
monitorname: @
monitorrange: 24-80, 50-0
monitorname: @0
*
So i got me a xorg.conf named /etc/X11/xorg.conf.NVIDIA without monitor appending . I am not happy about the chip/card detection because i have three different Nvidia Cards and Hardware Changes are not recognized because "NVIDIA" is everywhere the same but the Chip not .
I have one recent Nvidia card with DVI-I, HDMI and VGA port and ddcprobe only tests for the first one, the DVI one . If i attach the VGA cable to the VGA port directly, ddcprobe fails completely with no output at all . The kernel console is OK .
*
Next problem is a DELL Mini-Tower with onboard Intel Graphics chip and PCIe slot containig the recent Nvidia Card . If the board VGA port is connected to one monitor and the Nvidia Card to a second monitor, the DELL Bios shows a message on the screen it would accept only one graphic chip and i would need to fix that .
I got me a splitter today and the main problem turns out to be the " ddcprobe " command used in xorgwizard and xwin .
bash-3.00# ddcprobe
vbe: VESA 3.0 detected.
oem: NVIDIA
vendor: NVIDIA Corporation
product: NV18 Board Chip Rev A2
memory: 65536kb
mode: 640x400x256
mode: 640x480x256
mode: 800x600x16
mode: 800x600x256
mode: 1024x768x16
mode: 1024x768x256
mode: 1280x1024x16
mode: 1280x1024x256
mode: 80x60 (text)
mode: 132x25 (text)
mode: 132x43 (text)
mode: 132x50 (text)
mode: 132x60 (text)
mode: 320x200x64k
mode: 320x200x16m
mode: 640x480x64k
mode: 640x480x16m
mode: 800x600x64k
mode: 800x600x16m
mode: 1024x768x64k
mode: 1024x768x16m
mode: 1280x1024x64k
mode: 1280x1024x16m
edid:
edid: 1 2
id: 0710
eisa: ANC0710
serial: 00010100
manufacture: 40 2000
input: sync on green, analog signal.
screensize: 32 24
gamma: 2.200000
dpms: RGB, active off, suspend, standby
timing: 640x480@60 Hz (VGA)
timing: 640x480@75 Hz (VESA)
timing: 800x600@60 Hz (VESA)
timing: 800x600@72 Hz (VESA)
timing: 800x600@75 Hz (VESA)
timing: 1024x768@75 Hz (VESA)
ctiming: 256x256@60
ctiming: 256x192@60
ctiming: 256x192@69
ctiming: 256x192@69
dtiming: 1024x0@2007
monitorname: @
monitorrange: 24-80, 50-0
monitorname: @0
*
So i got me a xorg.conf named /etc/X11/xorg.conf.NVIDIA without monitor appending . I am not happy about the chip/card detection because i have three different Nvidia Cards and Hardware Changes are not recognized because "NVIDIA" is everywhere the same but the Chip not .
I have one recent Nvidia card with DVI-I, HDMI and VGA port and ddcprobe only tests for the first one, the DVI one . If i attach the VGA cable to the VGA port directly, ddcprobe fails completely with no output at all . The kernel console is OK .
*
Next problem is a DELL Mini-Tower with onboard Intel Graphics chip and PCIe slot containig the recent Nvidia Card . If the board VGA port is connected to one monitor and the Nvidia Card to a second monitor, the DELL Bios shows a message on the screen it would accept only one graphic chip and i would need to fix that .
Thanks for joining in. I fixed link as nooby suggested! I tried the ddcprobe command in rxvt as Karl suggested but how does one copy the result to paste it here? ^C doesn't seem to work
It only sees one monitor (Acer). But is says monitorrange: 30-82, 56-76 so is the second range for the second monitor? What is all that other info for?
I also notice that there are many xorg.conf files in the /etc/x11 directory, one called xorg.conf.ATIRADEON_9200AcerAL1916W which corresponds to my video card/ primary monitor.
There's also an xorg.conf.NVIDIASUSVH242H. I'm wondering if Nvidia was the old videocard (gone at 'puter store!). Maybe I should restart after unplugging the small monitor. Hmm. - edit - tried. Had to restart X to get right keyboard. Command ddcprobe stopped halfway - said 'edidfail' - end edit.
So which of these many xorg files is supposed to be modified? Maybe I try the main xorg.conf......
Why is the second (larger) monitor shutting down? edit - I found by looking at the generated xorg file that the monitor settings were somewhat different so I'll try setting monitor1 accordingly. - end edit
Thanks in advance. edit - I see we're both posting at same time! I'll try editing xorg to add the other monitor info - but I'm confused how to arrange - put monitor sections together or keep separate? eg:
Section "Monitor"
Identifier "Monitor0"
details
endsection
Section "Monitor"
Identifier "Monitor1"
details
endsection
or to put together with only one endsection after both monitors are described? Or maybe it doesn't matter?
It only sees one monitor (Acer). But is says monitorrange: 30-82, 56-76 so is the second range for the second monitor? What is all that other info for?
I also notice that there are many xorg.conf files in the /etc/x11 directory, one called xorg.conf.ATIRADEON_9200AcerAL1916W which corresponds to my video card/ primary monitor.
There's also an xorg.conf.NVIDIASUSVH242H. I'm wondering if Nvidia was the old videocard (gone at 'puter store!). Maybe I should restart after unplugging the small monitor. Hmm. - edit - tried. Had to restart X to get right keyboard. Command ddcprobe stopped halfway - said 'edidfail' - end edit.
So which of these many xorg files is supposed to be modified? Maybe I try the main xorg.conf......
Why is the second (larger) monitor shutting down? edit - I found by looking at the generated xorg file that the monitor settings were somewhat different so I'll try setting monitor1 accordingly. - end edit
Thanks in advance. edit - I see we're both posting at same time! I'll try editing xorg to add the other monitor info - but I'm confused how to arrange - put monitor sections together or keep separate? eg:
Section "Monitor"
Identifier "Monitor0"
details
endsection
Section "Monitor"
Identifier "Monitor1"
details
endsection
or to put together with only one endsection after both monitors are described? Or maybe it doesn't matter?
Last edited by canbyte on Wed 25 Jul 2012, 22:00, edited 1 time in total.
Normally highlighting with the mouse keeping left button held down, releasing the left button and press the middle button to pastecanbyte wrote:Thanks for joining in. I fixed link as nooby suggested! I tried the ddcprobe command in rxvt as Karl suggested but how does one copy the result to paste it here? ^C doesn't seem to work
Honestly no idea, but this seems interesting : http://grenage.com/xorg.html especially with the part of downloading the EDID for the monitors to be used by Xorg .It only sees one monitor (Acer). But is says monitorrange: 30-82, 56-76 so is the second range for the second monitor? What is all that other info for?
xorgwizard and xwin have code to copy xorg.conf to xorg.conf${chip)${monitor} like this :I also notice that there are many xorg.conf files in the /etc/x11 directory, one called xorg.conf.ATIRADEON_9200AcerAL1916W which seems to relate to my video card/ primary monitor.
Code: Select all
if [ "$CURRENT_XORG_PROFILE" != "$CURRENT_HARDWAREPROFILE" ];then
mv -f /etc/X11/xorg.conf /etc/X11/xorg.conf.${CURRENT_XORG_PROFILE} #### Rename
[ -f /etc/X11/xorg.conf.${CURRENT_HARDWAREPROFILE} ] && cp -af /etc/X11/xorg.conf.${CURRENT_HARDWAREPROFILE} /etc/X11/xorg.conf # CP new xorg.conf
YesThere's also an xorg.conf.NVIDIASUSVH242H. I'm wondering if Nvidia was the old videocard (gone at 'puter store!). Maybe I should restart after unplugging the small monitor. Hmm.
Xorg uses the xorg.conf file but since the xorg.conf$CHIP$MONITOR might be used to overwrite xorg.conf i bet this should be a duplicate of the altered xorg.conf .So which of these many xorg files is supposed to be modified?
? When ? BIOS POST, While booting, When Xorg starts ?Why is the second (larger) monitor shutting down?
Hi Karl, I answered some questions by editing previous post but here is ddcprobe printout (presently with both monitors plugged in (edid didn't fail this time). As you can see the ASUS monitor is not mentioned,
The monitor has been failing at unexpected moments, usually during editing this thread. I think after I can tell it the new settings it should hopefully stop doing this. I realized the second number question I asked before - the second #s refer to the vertical, first is horizontal range. I'll edit above later.
That's an interesting link you posted, especially the last part - have you figured out how it applies in Puppy?
Here is what I'm trying to get xorg to run (just showing the last half of the file - after the line that says
edit - didn't work Whot next? And to save work, can I just paste into xorg instead of inserting every different line? ie. it appears different if I open xorg as text (no colours) vs opening it by clicking on it (colour codes for active lines - i guess)?? Thanks
# ddcprobe
vbe: VESA 2.0 detected.
oem: ATI RADEON 9200
memory: 131072kb
mode: 800x600x16
mode: 1024x768x16
mode: 320x200x32k
mode: 320x200x64k
mode: 320x200x16m
mode: 1600x1200x256
mode: 640x400x256
mode: 640x480x256
mode: 640x480x32k
mode: 640x480x64k
mode: 640x480x16m
mode: 1600x1200x32k
mode: 800x600x256
mode: 800x600x32k
mode: 800x600x64k
mode: 800x600x16m
mode: 1600x1200x64k
mode: 1024x768x256
mode: 1024x768x32k
mode: 1024x768x64k
mode: 1024x768x16m
mode: 1280x1024x256
mode: 1280x1024x32k
mode: 1280x1024x64k
mode: 1280x1024x16m
mode: 132x25 (text)
mode: 132x43 (text)
edid:
edid: 1 3
id: ad52
eisa: ACRad52
serial: 54800345
manufacture: 48 2005
input: sync on green, analog signal.
screensize: 41 26
gamma: 2.200000
dpms: RGB, active off, no suspend, no standby
timing: 720x400@70 Hz (VGA 640x400, IBM)
timing: 720x400@88 Hz (XGA2)
timing: 640x480@60 Hz (VGA)
timing: 640x480@67 Hz (Mac II, Apple)
timing: 640x480@72 Hz (VESA)
timing: 640x480@75 Hz (VESA)
timing: 800x600@60 Hz (VESA)
timing: 800x600@72 Hz (VESA)
timing: 800x600@75 Hz (VESA)
timing: 832x624@75 Hz (Mac II)
timing: 1024x768@87 Hz Interlaced (8514A)
timing: 1024x768@70 Hz (VESA)
timing: 1024x768@75 Hz (VESA)
timing: 1280x1024@75 (VESA)
ctiming: 1280x1024@60
ctiming: 1280x960@60
ctiming: 1152x864@75
dtiming: 1440x900@69
monitorrange: 30-82, 56-76
monitorname: Acer AL1916W
monitorserial: ETL5209005
The monitor has been failing at unexpected moments, usually during editing this thread. I think after I can tell it the new settings it should hopefully stop doing this. I realized the second number question I asked before - the second #s refer to the vertical, first is horizontal range. I'll edit above later.
That's an interesting link you posted, especially the last part - have you figured out how it applies in Puppy?
Here is what I'm trying to get xorg to run (just showing the last half of the file - after the line that says
#everything past here is auto-generated by Puppy's Xorg Wizard....
[/quote]Section "ServerLayout"
# InputDevice "Synaptics Mouse" "AlwaysCore" #serverlayoutsynaptics
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
Screen 1 "Screen1" 0 0 RightOf "Screen0"
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" #monitor0prefmode
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 "Modes"
Identifier "Modes0"
#modes0modeline0
EndSection
#110627 remove...
#server can find BusID automatically, comment out...
#Section "Device"
# Identifier "Card0"
# Driver "vesa" #card0driver
# VendorName "Unknown Vendor"
# BoardName "Unknown Board"
# BusID "PCI:0:2:0" #card0busid
#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" #screen0modes
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" #screen0modes
EndSubsection
EndSection
#PuppyHardwareProfile=ATI_RADEON_9200AcerAL1916W
edit - didn't work Whot next? And to save work, can I just paste into xorg instead of inserting every different line? ie. it appears different if I open xorg as text (no colours) vs opening it by clicking on it (colour codes for active lines - i guess)?? Thanks
[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]
Puppy 533 on CD, accesses flash drive only,
FFox Nightly12.0
2. Compaq P3 733Hz 375RAM
Printer: Oki C3400 > LAN [/color]
Some progress: The following code now works to restart x so evidently, the separate monitor/ screen descriptions are the proper format. What is not happening is the combining of both screens into one. Seems something is missing besides just the layout section.
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
Screen 1 "Screen1" LeftOf "Screen0"
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" #monitor0prefmode
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 "Modes"
Identifier "Modes0"
#modes0modeline0
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"
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 "Card0"
Monitor "Monitor1"
DefaultDepth 16
#Option "metamodes" "1024x768_60 +0+0" #METAMODES_0
Subsection "Display"
Depth 16
Modes "1024x768" #screen0modes
EndSubsection
EndSection
#PuppyHardwareProfile=ATI_RADEON_9200AcerAL1916W
[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]
Puppy 533 on CD, accesses flash drive only,
FFox Nightly12.0
2. Compaq P3 733Hz 375RAM
Printer: Oki C3400 > LAN [/color]
Fed up i am beginning to get. Just found a sort of official looking post that suggests that the only way to resolve the issue is for each user to determine exactly the version of xorg used and perhaps RandR also. per the following
http://en.gentoo-wiki.com/wiki/Talk:X.Org/Dual_Monitors
I would have to conclude that the xorg/ RandR thing is being constantly upgraded and my guess is that Puppy developers can't/ wont keep up with such details for only a very small segment of users. Thus, how can a noob hope to ever sort out all the permutation of versions and which applies when Puppy might have adopted them (or part thereof)??? Hopeless - unless one has nothing else to do! Seems like I bit off more than I could chew. Besides it's summertime and it seems not many folks are around. Sorry folks. Abandoning ship, hoping for rescue. SOS.
on this page (which didn't work)
Hi, I understand that since randr 1.3 you don't need xinerama anymore. Is that right?
[edit] randr 1.3 fullscreen
That's true there doesn't need to be a device section, screen section, server flag section or server layout section. In fact you only need two monitor sections with two lines in it:
Section "Monitor"
Identifier "Monitor0"
Option "Primary" "True" #This is optional since the first port gets priority
EndSection
Section "Monitor"
Identifier "Monitor1"
Option "RightOf" "Monitor0"
EndSection
With this you will get a fulling working Dual Monitors setup. BUT, you need the use flag xinerama for your programs to work properly with two monitors. It seems this wiki page is extremely outdated.
http://en.gentoo-wiki.com/wiki/Talk:X.Org/Dual_Monitors
I would have to conclude that the xorg/ RandR thing is being constantly upgraded and my guess is that Puppy developers can't/ wont keep up with such details for only a very small segment of users. Thus, how can a noob hope to ever sort out all the permutation of versions and which applies when Puppy might have adopted them (or part thereof)??? Hopeless - unless one has nothing else to do! Seems like I bit off more than I could chew. Besides it's summertime and it seems not many folks are around. Sorry folks. Abandoning ship, hoping for rescue. SOS.
[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]
Puppy 533 on CD, accesses flash drive only,
FFox Nightly12.0
2. Compaq P3 733Hz 375RAM
Printer: Oki C3400 > LAN [/color]
Dual Monitor setup for desktop ..... (unresolvable?)
Hi canbyte,
I am interested in your situation, would like to see a successful outcome here, so I did some research...
If you haven't done so already, try enabling Xinerama in xorg.conf This seems worth a try given your ATI graphics card, otherwise... if you had an nVidia card, you would use the TwinView configuration.
Where you have:
try modifying it to this:
One important note is that both of your monitors must be set to the same color depth eg. 16 bpp or 24 bpp for Xinerama to work properly. Another note worth mentioning is to make sure that you have two listings for each section concerning: Monitor Device & Screen.
Monsie
I am interested in your situation, would like to see a successful outcome here, so I did some research...
If you haven't done so already, try enabling Xinerama in xorg.conf This seems worth a try given your ATI graphics card, otherwise... if you had an nVidia card, you would use the TwinView configuration.
Where you have:
Code: Select all
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
Screen 1 "Screen1" LeftOf "Screen0"
Code: Select all
Section "ServerLayout"
Identifier "Xinerama Screen"
Screen 0 "Screen0" 0 0
Screen 1 "Screen1" LeftOf "Screen0"
Option "Xinerama" "true"
EndSection
Monsie
My [u]username[/u] is pronounced: "mun-see". Derived from my surname, it was my nickname throughout high school.
canbyte,
While I no nothing about setting up dual monitors, I did find the code from Pizzasgood that you were looking for.
http://www.murga-linux.com/puppy/viewto ... 687#357687
It looks like his change had to do with fixing a problem for someone who had only one monitor but had a video card that supported two monitors. So it may not be helpful in your case.
And, yes, it does look like Pizzasgood's code was added to the xorgwizard that is currently in Woof2.
Do note this line in Pizzasgood's message:
Probably the lack of support for automatically handling multiple monitors is related to this comment in xorgwizard:
Anyway, you seem to have already progressed well beyond this in your manual changes to xorg.conf. So if you were still curious about Pizzasgood's change, this should shed some light on that, but I fear that it won't bring you any closer to your goal than you already are. I hope that Monsie's post above will be more helpful to you.
While I no nothing about setting up dual monitors, I did find the code from Pizzasgood that you were looking for.
http://www.murga-linux.com/puppy/viewto ... 477#357477canbyte wrote:Barry's Blog. He gives a link to Pizzagood's code but link is broken.
http://www.murga-linux.com/puppy/viewto ... 687#357687
It looks like his change had to do with fixing a problem for someone who had only one monitor but had a video card that supported two monitors. So it may not be helpful in your case.
And, yes, it does look like Pizzasgood's code was added to the xorgwizard that is currently in Woof2.
Do note this line in Pizzasgood's message:
So, although xorgwizard does much of the work, if one runs multiple monitors a user still has to make that manual change to one line in xorg.conf. But I see that this is not your problem, since your Screen1 line in your ServerLayout section is not commented-out.Pizzasgood wrote:. . . 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.
Probably the lack of support for automatically handling multiple monitors is related to this comment in xorgwizard:
This seems to be limited by ddcprobe, which doesn't seem to have good support for multiple monitors.#echo "Probing the video card and monitor..."
#code below is not distinguishing multiple cards/monitors...
Anyway, you seem to have already progressed well beyond this in your manual changes to xorg.conf. So if you were still curious about Pizzasgood's change, this should shed some light on that, but I fear that it won't bring you any closer to your goal than you already are. I hope that Monsie's post above will be more helpful to you.
Hi Monsie/ npierce. Thanks for dropping by.
I tried Monsie's mod, unfortunately no luck which maybe corroberates the note from yesterday that xinerama is now obsolete. After yesterday's readings, I'm convinced that the screw up is the lingo confusion and that the wording should reflect this reality :
screen0 is comprised of monitor0 and monitor1. Screen0 width should be 2048 not 1024. There is no screen1 desired. The gentoo fix was to add a line about 'virtual' in the monitor section but I've had no luck trying this.
So I should be saying monitor1 is rightof monitor0 - somewhere, no?
The colour depth is 16 for both.
To clarify/confirm, there is only one device, not two but yes, there are two monitor sections and for now, despite the above, two screen sections. But should we really ignore the statement "there doesn't need to be a device section, screen section, server flag section or server layout section. " (even if it's on a gentoo forum)??
Re npierce/ pizza's mods for xorgwizard - does make sense to mod the parent rather than the child, however, it appears that the mods are already present in my xorgwizard. Starts on line 1320.
One exception. Pizza's code in xorgwizard.diff is shown below. The code in red is not included in my xorgwizard (or in Pizza's on screen version). I doubt it matters but please comment if it is needed.
Sigh.
I tried Monsie's mod, unfortunately no luck which maybe corroberates the note from yesterday that xinerama is now obsolete. After yesterday's readings, I'm convinced that the screw up is the lingo confusion and that the wording should reflect this reality :
screen0 is comprised of monitor0 and monitor1. Screen0 width should be 2048 not 1024. There is no screen1 desired. The gentoo fix was to add a line about 'virtual' in the monitor section but I've had no luck trying this.
So I should be saying monitor1 is rightof monitor0 - somewhere, no?
The colour depth is 16 for both.
To clarify/confirm, there is only one device, not two but yes, there are two monitor sections and for now, despite the above, two screen sections. But should we really ignore the statement "there doesn't need to be a device section, screen section, server flag section or server layout section. " (even if it's on a gentoo forum)??
Re npierce/ pizza's mods for xorgwizard - does make sense to mod the parent rather than the child, however, it appears that the mods are already present in my xorgwizard. Starts on line 1320.
One exception. Pizza's code in xorgwizard.diff is shown below. The code in red is not included in my xorgwizard (or in Pizza's on screen version). I doubt it matters but please comment if it is needed.
Bottom line is that as npierce suggested, this tack looks to be at a dead end, or at least not the place my meager noobish talents will do any good! The wizard is complex, as I guess all wizards are. Back to xorg.conf.#now write the Screen section...
-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
PREFERREDMODE=$FINALXY #v3.98 rerwin - set monitor preferred mode same as
Sigh.
Last edited by canbyte on Sat 28 Jul 2012, 02:47, 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]
Puppy 533 on CD, accesses flash drive only,
FFox Nightly12.0
2. Compaq P3 733Hz 375RAM
Printer: Oki C3400 > LAN [/color]
Dual Monitor setup for desktop ..... (unresolvable?)
canbyte,
Hold on... I still think that you are on the right track.
Given your posting of xorg.conf and ddcprobe I believe this is what your "Device" sections should look like. Note that I didn't include the rest of the Device Options in my example for the sake of brevity... you can include that information if you want... as it is optional.
Hope this helps,
Monsie
Hold on... I still think that you are on the right track.
Yes, try changing "LeftOf" in the ServerLayout section to "rightof" because I have seen this used in example configurations of Xorg. I kept your terminology in the sample configuration I gave you because I didn't think it mattered, but maybe, in fact, it does.So I should be saying monitor1 is rightof monitor0 - somewhere.
I am of the understanding that this does matter when using Xinerama, so I would give it a try:To clarify/confirm, there is only one device, not two but yes, there are two screen and monitor sections.
Code: Select all
Section "Device"
Identifier "Card0"
Driver "radeon" #card0driver
VendorName "ATI Technologies Inc"
BoardName "ATI_RADEON_9200"
Screen 0
EndSection
Section "Device"
Identifier "Card1"
Driver "radeon" #card1driver
VendorName "ATI Technologies Inc"
BoardName "ATI_RADEON_9200"
Screen 1
EndSection
Hope this helps,
Monsie
My [u]username[/u] is pronounced: "mun-see". Derived from my surname, it was my nickname throughout high school.
Thanks Monsie. I changed 'leftof' to 'rightof' and inserted your 2nd device code as suggested but no luck. I've tried so many combinations of words and sections I've lost track - but feeling like the monkey trying to type the works of Shakespeare!
[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]
Puppy 533 on CD, accesses flash drive only,
FFox Nightly12.0
2. Compaq P3 733Hz 375RAM
Printer: Oki C3400 > LAN [/color]
Hi Karl. What an amazing file - over 1100 lines generated every time puppy starts! Now i can see why startup takes time. I'd clip out some but it looks like 3/4 of lines mention Radeon. Having browsed some other sites, it seems that various items may be involved and need to be activated (dri? mf?, etc.) - pages might be useful:
http://www.linuxquestions.org/questions ... -a-680669/
http://www.linuxquestions.org/questions ... -a-558746/
http://ubuntuforums.org/showthread.php?t=1021516&page=5
which says as a last suggestion:
Thanks
Edit - turns out i don't know how to add attachment so for other noobs like me..... A link shows allowed extensions but shows max upload size as 0 bytes!! Trying it anyway then it says "The Extension log is not allowed". Hmm, i see a zip thing on desktop so let's try that. Worked. Attachment added. Hooray! I'll pray you find something.
http://www.linuxquestions.org/questions ... -a-680669/
http://www.linuxquestions.org/questions ... -a-558746/
http://ubuntuforums.org/showthread.php?t=1021516&page=5
which says as a last suggestion:
Re: Dual Screen with ATI Radeon 9200 on Ubuntu 8.10
Looks like the radeon driver is loading, so all should be good for you now. To be sure run Code: glxgears
Thanks
Edit - turns out i don't know how to add attachment so for other noobs like me..... A link shows allowed extensions but shows max upload size as 0 bytes!! Trying it anyway then it says "The Extension log is not allowed". Hmm, i see a zip thing on desktop so let's try that. Worked. Attachment added. Hooray! I'll pray you find something.
- Attachments
-
- Xorg0log.zip
- (11.34 KiB) Downloaded 783 times
Accordingly to this everything should be fine . But both as "-0" irritates me.[ 76.387] (II) RADEON(0): Output VGA-0 connected
[ 76.387] (II) RADEON(0): Output DVI-0 connected
[ 76.387] (II) RADEON(0): Output S-video disconnected
[ 76.387] (II) RADEON(0): Using user preference for initial modes
[ 76.387] (II) RADEON(0): Output VGA-0 using initial mode 1024x768
[ 76.387] (II) RADEON(0): Output DVI-0 using initial mode 1024x768
VGA-0
DVI-1
seems more logical.
Probably the VGA-DVI mismatches things. Probably better both are DVI or VGA.
Racy-5.3 has Xorg-server 1.11.x .
Hi Karl
All i found in /etc/modprobe.d/ was radeon.conf and a few other files.
All radeon.conf contained was
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.
All i found in /etc/modprobe.d/ was radeon.conf and a few other files.
All radeon.conf contained was
Somewhere i saw a reference to nouveau. nouveau.conf containsoptions radeon modeset=0
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.options nouveau modeset=1
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.
[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]
Puppy 533 on CD, accesses flash drive only,
FFox Nightly12.0
2. Compaq P3 733Hz 375RAM
Printer: Oki C3400 > LAN [/color]
No, then i would change modeset=0 to modeset=1canbyte wrote:Hi Karl
All i found in /etc/modprobe.d/ was radeon.conf and a few other files.
All radeon.conf contained was
Somewhere i saw a reference to nouveau. nouveau.conf containsoptions radeon modeset=0You 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.options nouveau modeset=1
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.
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.
edit - there are 8 other radeon related files in various directories. What should i look for? edit2 - since pfind lists directories as files, that 8 is closer to 4. radeon.so, ...so.1 and ....so.1.0,0 radeon_drv.so
edit - there are 8 other radeon related files in various directories. What should i look for? edit2 - since pfind lists directories as files, that 8 is closer to 4. radeon.so, ...so.1 and ....so.1.0,0 radeon_drv.so
[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]
Puppy 533 on CD, accesses flash drive only,
FFox Nightly12.0
2. Compaq P3 733Hz 375RAM
Printer: Oki C3400 > LAN [/color]