Page 9 of 9
Posted: Fri 05 Sep 2008, 10:35
by muggins
Harryc,
good to hear you were successful. I think Richard did all the hard work of getting xorgwizard to recognise the tridents. I'm curious how much RAM you had though? If you open a console and type free, what does it display?
Posted: Fri 05 Sep 2008, 10:43
by harryc
muggins - I have 128MB of RAM and 256MB swap.
Posted: Fri 05 Sep 2008, 15:30
by rerwin
harryc,
I am pleased that puppy4 worked for you as I expected. It can be made to avoid the ctrl-c game if you can give me a bit of information to include in future puppys.
Could you post the last line of file /etc/xorgoverrides here? I can then have that added to the standard puppy. Thanks.
Richard
Posted: Fri 05 Sep 2008, 16:08
by harryc
Richard, I skimmed over your post too fast and didn't pay attention to the ctrl-C. I did not have to do that. I just selected xorg, and the LCD and resolution. The last line of /etc/xorgoverrides is;
oem:Trident CYBER 8820.
Posted: Fri 05 Sep 2008, 17:35
by Tonny
Hello
harryc or rerwin , can you take a look at my post?
http://www.murga-linux.com/puppy/viewtopic.php?t=33188
(problem with Trident Cyber 9382 video chipset)
Posted: Thu 19 Jan 2012, 19:34
by herrdeh
Hi everybody,
I'll try to relaunch this old thread…
Tried to install puppy 5.3.1 slacko today on my girl's Toshiba satellite 1805 with (wow!) 1GB of RAM.
As I expected it would fail when probing the xserver. As I have a working ubuntu (but: no hardware acceleration, that was broken sometimes around ubuntu 7), I mounted the hdd and copied the (known good, exept hardware acceleration) xorg.conf to puppy's /etc/X11. startx or xwin failed both.
I do attach ubuntu's the xorg.conf here - maybe somebody will find something:
Code: Select all
# xorg.conf (X.Org X Window System server configuration file)
#
# Custom file by Michael Minn
Section "InputDevice"
Identifier "Generic Keyboard"
Driver "Kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protoxol" "ImPS/2"
EndSection
Section "Device"
Identifier "Trident Microsystems cyberbladeAi1d"
Driver "trident"
BusID "PCI:1:0:0"
Option "NoDDC"
EndSection
# Section "Device"
# Identifier "Card0"
# Driver "trident"
# VendorName "Trident Microsystems"
# BoardName "CyberBladeAi1d"
# BusID "PCI:1:0:0"
# EndSection
Section "Monitor"
Identifier "ToshLCD"
Option "DPMS"
HorizSync 30-71
VertRefresh 50-100
EndSection
Section "Screen"
Identifier "Default Screen"
Monitor "ToshLCD"
Device "Trident Microsystems cyberbladeAi1d"
DefaultDepth 16
SubSection "Display"
Depth 16
Modes "1024x768"
EndSubSection
SubSection "Display"
Depth 24
Modes "1024x768"
EndSubSection
SubSection "Display"
Depth 16
Modes "800x600"
EndSubSection
SubSection "Display"
Depth 24
Modes "800x600"
EndSubSection
EndSection
Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Configured Mouse"
EndSection
AFAIK the
is crucial on that machine.
As this thread has become very long: I coudnt really get clear where the most recent advice can be found. Could someone give me a hint? - NB.: Is it still valid for 5.3.1?
And another thing: ubuntu needed kernel parameters
not to hang during the boot procedure. Looks as if this were not necessary for puppy.
BTW.: Tried puppy on a 160MB RAM PIII today - awesome!!!!
Greetings,
Wolf
Posted: Tue 28 Feb 2012, 14:05
by herrdeh
Finally I ended up to use puppy "wary" - this works out of the box.
Attn.: Do not "upgrade" to Xorg 7.6, as offered by the system. That one did not work on my machine.
HTH,
Wolf