[obsolete] Compiz-Fusion Puplet for testing -- aka "W...
the first one looks interesting
info on 3D in ati express 200M:
http://www.ensode.net/ati_radeon_xpress_200m_linux.html
http://ubuntuforums.org/showthread.php?t=221320&page=21
info on 3D in ati express 200M:
http://www.ensode.net/ati_radeon_xpress_200m_linux.html
http://ubuntuforums.org/showthread.php?t=221320&page=21
Taking Puppy Linux to the limit of perfection. meanwhile try "puppy pfix=duct_tape" kernel parem eater.
X86: Sager NP6110 3630QM 16GB ram, Tyan Thunder 2 2x 300Mhz
Sun: SS2 , LX , SS5 , SS10 , SS20 ,Ultra 1, Ultra 10 , T2000
Mac: Platinum Plus, SE/30
X86: Sager NP6110 3630QM 16GB ram, Tyan Thunder 2 2x 300Mhz
Sun: SS2 , LX , SS5 , SS10 , SS20 ,Ultra 1, Ultra 10 , T2000
Mac: Platinum Plus, SE/30
I honestly don't know if there is any major difference between the regular and the mobile versions of the cards in terms of setup. I suggest you create a new save file (or boot from CD if you have a full HD install) and try it on the clean file so that you don't mess up anything important if it doesn't work.
Be brave that God may help thee, speak the truth even if it leads to death, and safeguard the helpless. - A knight's oath
So just to be clear -- For The Jinx and Caneri 3D acceleration and thus wNOP will only work for you once the fglrx driver is properly installed, that needs to be the first thing to happen.
Also just to be clear about installing this driver:
(1) You will need to be in wNOP to run it.
(2) devx_301.sfs must be installed on wNOP
(2)(a) This can be done by booting wNOP with a savefile, then placing devx301.sfs in /mnt/home. If devx_301 doesn't mount on subsequent boots then use Xfce Menu -> Puppy Setup -> Bootmanager to make sure it does. To test if devx_301 is installed typing at the terminal should return the output:
(3)The command:
needs to be run from the terminal after successful driver installation.
(4) Reboot needed
(Don't worry all this will be in wNOP2!)
SirDuncan
Thanks for those dump files. Interestingly the radeon driver dump appears to be perfect! DRI is active and xorg.conf reports no errors. The only clue I can see is that the module "intel_agp" is being loaded, no doubt because of a legacy intel graphics card which I assume you have disabled through the BIOS or whatever. Strictly that module shouldn't be loaded, but I'm not sure how to stop it, but then I'm not totally sure it's the cause of the problem. What I really need to see now is the output of from within that first fresh (ie pfix=ram) boot of wNOP.
As for the fglrx dump file, xorg.conf has not been setup, so maybe you didn't run "aticonfig --initial" after installation. Also did you follow most of the steps outlined above? And would it be possible to run the installer from the terminal to catch any of its output -- I know its got a horrible long name but something I only just learnt recently is that if you type the first few letters of a command and then press tab twice bash autocompletes with suggestions!
Thanks And no rush.
Okay I can wait for Kiba, it looks fantastic though. If I get desperate I'll go a-hunting in the Ubuntu forests
P.S. Seeing as it looks like the fglrx driver will be an added feature and so added MBs to wNOP2, it would be great to try and compile the Compiz-Config-Settings-Manager into a standalone executable. I reckon that could cut a fair amount of MBs away from the final ISO size. If anybody has any python experience I've been looking at PyInstaller to do the job.
An ode to the wobble
Upon the shoulders of our forebears,
Barry, gray and wow to name but some,
Through rain, snow and ripple effects --
We shall strive to conquer fusion.
So that every corner may be activated
And as if from the highest summit
We may see the truest vista --
all windows in a single desktop fit
Also just to be clear about installing this driver:
(1) You will need to be in wNOP to run it.
(2) devx_301.sfs must be installed on wNOP
(2)(a) This can be done by booting wNOP with a savefile, then placing devx301.sfs in /mnt/home. If devx_301 doesn't mount on subsequent boots then use Xfce Menu -> Puppy Setup -> Bootmanager to make sure it does. To test if devx_301 is installed typing
Code: Select all
gcc
Code: Select all
gcc: no input files
Code: Select all
aticonfig --initial
(4) Reboot needed
(Don't worry all this will be in wNOP2!)
SirDuncan
Thanks for those dump files. Interestingly the radeon driver dump appears to be perfect! DRI is active and xorg.conf reports no errors. The only clue I can see is that the module "intel_agp" is being loaded, no doubt because of a legacy intel graphics card which I assume you have disabled through the BIOS or whatever. Strictly that module shouldn't be loaded, but I'm not sure how to stop it, but then I'm not totally sure it's the cause of the problem. What I really need to see now is the output of
Code: Select all
compiz-manager
As for the fglrx dump file, xorg.conf has not been setup, so maybe you didn't run "aticonfig --initial" after installation. Also did you follow most of the steps outlined above? And would it be possible to run the installer from the terminal to catch any of its output -- I know its got a horrible long name but something I only just learnt recently is that if you type the first few letters of a command and then press tab twice bash autocompletes with suggestions!
Thanks And no rush.
Okay I can wait for Kiba, it looks fantastic though. If I get desperate I'll go a-hunting in the Ubuntu forests
P.S. Seeing as it looks like the fglrx driver will be an added feature and so added MBs to wNOP2, it would be great to try and compile the Compiz-Config-Settings-Manager into a standalone executable. I reckon that could cut a fair amount of MBs away from the final ISO size. If anybody has any python experience I've been looking at PyInstaller to do the job.
An ode to the wobble
Upon the shoulders of our forebears,
Barry, gray and wow to name but some,
Through rain, snow and ripple effects --
We shall strive to conquer fusion.
So that every corner may be activated
And as if from the highest summit
We may see the truest vista --
all windows in a single desktop fit
Somehow I was afraid that the old Intel card might be a problem. I would have removed it if it weren't built in to the motherboard. I'll have to see what I can do to stop it from loading.
I did run "aticonfig" although I used the command "aticonfig --initial --something_else_I_don't_remember_but_was_told_to_do_in_a_how-to_I_found". Perhaps I shall try just "aticonfig --initial" next time.
Most of what I'm trying to do with Kiba right now is to weed out the unnecessary packages. The Ubuntu repo had it split into a lot of seperate packages. I have it narrowed down to 3-4 right now. That might be good enough to post it for testing. I'll do that when I get home, I have my last final for the quarter in about half an hour. Then I get to go home for winter break.
I already have my desktop packed to leave, so I won't get to do any testing until late tonight (probably early morning tomorrow for you) or tomorrow. I'll be spending most of today driving.
I did run "aticonfig" although I used the command "aticonfig --initial --something_else_I_don't_remember_but_was_told_to_do_in_a_how-to_I_found". Perhaps I shall try just "aticonfig --initial" next time.
Most of what I'm trying to do with Kiba right now is to weed out the unnecessary packages. The Ubuntu repo had it split into a lot of seperate packages. I have it narrowed down to 3-4 right now. That might be good enough to post it for testing. I'll do that when I get home, I have my last final for the quarter in about half an hour. Then I get to go home for winter break.
I already have my desktop packed to leave, so I won't get to do any testing until late tonight (probably early morning tomorrow for you) or tomorrow. I'll be spending most of today driving.
Be brave that God may help thee, speak the truth even if it leads to death, and safeguard the helpless. - A knight's oath
sirduncan: If you have screen1 display1 or card1 are in your xorg.conf delete those lines
you should only have screen0 display0 and card0
and try deleting anything that pertains to the intel gpu
that is how I got the nvida 6200 with integrated intel gpu to work
you should only have screen0 display0 and card0
and try deleting anything that pertains to the intel gpu
that is how I got the nvida 6200 with integrated intel gpu to work
Taking Puppy Linux to the limit of perfection. meanwhile try "puppy pfix=duct_tape" kernel parem eater.
X86: Sager NP6110 3630QM 16GB ram, Tyan Thunder 2 2x 300Mhz
Sun: SS2 , LX , SS5 , SS10 , SS20 ,Ultra 1, Ultra 10 , T2000
Mac: Platinum Plus, SE/30
X86: Sager NP6110 3630QM 16GB ram, Tyan Thunder 2 2x 300Mhz
Sun: SS2 , LX , SS5 , SS10 , SS20 ,Ultra 1, Ultra 10 , T2000
Mac: Platinum Plus, SE/30
svn downloaded for kiba here you go!
no i don't have svn in puppy ..... downloaded with Xpee..at school
no i don't have svn in puppy ..... downloaded with Xpee..at school
- Attachments
-
- akamaru.zip
- (13.48 KiB) Downloaded 510 times
-
- kiba-ephy-extension.zip
- (27.57 KiB) Downloaded 509 times
-
- kiba-gaim-plugin.zip
- (36.97 KiB) Downloaded 497 times
Taking Puppy Linux to the limit of perfection. meanwhile try "puppy pfix=duct_tape" kernel parem eater.
X86: Sager NP6110 3630QM 16GB ram, Tyan Thunder 2 2x 300Mhz
Sun: SS2 , LX , SS5 , SS10 , SS20 ,Ultra 1, Ultra 10 , T2000
Mac: Platinum Plus, SE/30
X86: Sager NP6110 3630QM 16GB ram, Tyan Thunder 2 2x 300Mhz
Sun: SS2 , LX , SS5 , SS10 , SS20 ,Ultra 1, Ultra 10 , T2000
Mac: Platinum Plus, SE/30
I get home and the first thing I go to do is upload Kiba, only to find that CB has beat me to it. Since he posted the source, I suppose I can still post the binaries (though I will probably recompile now that I have access to source to ensure full Puppy compatibility).
These were plucked from an Ubuntu repository. All 4 are necessary (well, you could leave out the settings manager, but I don't suggest it) and are only tested on wNOP. They should work with any 3.01 (possibly older versions as well) that has Compiz Fusion.
Now, back to work getting wNOP functional on my 9550.
These were plucked from an Ubuntu repository. All 4 are necessary (well, you could leave out the settings manager, but I don't suggest it) and are only tested on wNOP. They should work with any 3.01 (possibly older versions as well) that has Compiz Fusion.
Now, back to work getting wNOP functional on my 9550.
- Attachments
-
- libakamaru0-0.1.pet
- The Akamaru physics engine (yes this is required)
- (7.21 KiB) Downloaded 567 times
-
- kibasettings-0.1.pet
- The control panel for Kiba
- (32.93 KiB) Downloaded 542 times
Be brave that God may help thee, speak the truth even if it leads to death, and safeguard the helpless. - A knight's oath
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
An ode to the wobble
Upon the shoulders of our forebears,
Barry, gray and wow to name but some,
Through rain, snow and ripple effects --
We shall strive to conquer fusion.
So that every corner may be activated
And as if from the highest summit
We may see the truest vista --
all windows in a single desktop fit Smile
Set
to wobble
Phases on
Stun
Fusion enthuses us to jell
Nvidia GeForce 7300 GS up and running
Great Job this is running off of a memory stick and is working great. Also the sound module configured itself perfectly, normally I have to work on it to get it up and running.
!!!The Kernel Source SFS is also needed to use the ATI installer!!!
However if you don't wnat to use the installer here is a [temporarily unavailable dotpet] for the ATI fglrx v8.42.3 driver. I must point out that I do not have an ATI card supported by this driver, so I cannot say that it works. Also, it will only work with Puppy 3 or Xorg7.1 and later.
In order to make this dotpet I used the "--bldpckg Slackware/All" option when running the original installer. With the thus outputted packages I adjusted the directory for Puppy's xorg library (ie: usr/lib -> /usr/X11R7/lib/xorg), updated the symlinks and made the dotpet. I did test it on my system and /var/log/Xorg.0.log reported the 'correct error' of something like "unsupproted device", therefore everything went alright up to the point of the driver actually trying to talk to my Mobility Radeon 9000.
If anyone has an ATI card more recent than the 9500 series and is willing to try this dotpet out that would be great. You will need to:
(1) Boot into Puppy 3 (any version -- the original, NOP 3.01 or wNOP using <plain Xfce> option) in preparation that EVERYTHING is going to go wrong! Therefore, better make it a pfix=ram session
(2) install the dotpet
(3) upon completion type: into a terminal
(4)restart X (CTRL+ALT+BACKSPACE then type xwin to return)
All we're looking for at the moment is that after step (4) you see a desktop and some icons, we can worry about Wobbilyness later.
Good Luck!
PS Thanks azieser
However if you don't wnat to use the installer here is a [temporarily unavailable dotpet] for the ATI fglrx v8.42.3 driver. I must point out that I do not have an ATI card supported by this driver, so I cannot say that it works. Also, it will only work with Puppy 3 or Xorg7.1 and later.
In order to make this dotpet I used the "--bldpckg Slackware/All" option when running the original installer. With the thus outputted packages I adjusted the directory for Puppy's xorg library (ie: usr/lib -> /usr/X11R7/lib/xorg), updated the symlinks and made the dotpet. I did test it on my system and /var/log/Xorg.0.log reported the 'correct error' of something like "unsupproted device", therefore everything went alright up to the point of the driver actually trying to talk to my Mobility Radeon 9000.
If anyone has an ATI card more recent than the 9500 series and is willing to try this dotpet out that would be great. You will need to:
(1) Boot into Puppy 3 (any version -- the original, NOP 3.01 or wNOP using <plain Xfce> option) in preparation that EVERYTHING is going to go wrong! Therefore, better make it a pfix=ram session
(2) install the dotpet
(3) upon completion type:
Code: Select all
aticonfig --initial
(4)restart X (CTRL+ALT+BACKSPACE then type xwin to return)
All we're looking for at the moment is that after step (4) you see a desktop and some icons, we can worry about Wobbilyness later.
Good Luck!
PS Thanks azieser
Last edited by tombh on Fri 23 Nov 2007, 23:37, edited 1 time in total.
Well I survived the ati.pet.
I had to make a pup_save file as the first attempt failed and broke xorg...xwin command didn't work when restarted XFCE.
After a pup_save file was created on a spare usb flash I had the ati.pet installed with a warning about a missing a dependency (I forgot to write it down..sheesh). With restarted X the desktop was there.
After a full shutdown/reboot the desktop was there with ati.pet installed.
Tested on an ATI Mobility Radeon X1600/256mb ram (M56 71C5)
I had to make a pup_save file as the first attempt failed and broke xorg...xwin command didn't work when restarted XFCE.
After a pup_save file was created on a spare usb flash I had the ati.pet installed with a warning about a missing a dependency (I forgot to write it down..sheesh). With restarted X the desktop was there.
After a full shutdown/reboot the desktop was there with ati.pet installed.
Tested on an ATI Mobility Radeon X1600/256mb ram (M56 71C5)
[color=darkred][i]Be not afraid to grow slowly, only be afraid of standing still.[/i]
Chinese Proverb[/color]
Chinese Proverb[/color]
I would love to help in testing, but i have no idea what steps i should take. I understand I am suppose to install the dotpet, but what do i do with the kernel Source SFS. Do i still follow the instructions to install the devs_301.sfs a couple of post earlier.
In addition, while i am on wNOP i notice that i cannot sign on to this forum(something about SQL problems) and i and having problems playing movies.(all i see is lines of color) could this have anything to do with me choosing xorg with Generic Drivers.
~ The Jinx
In addition, while i am on wNOP i notice that i cannot sign on to this forum(something about SQL problems) and i and having problems playing movies.(all i see is lines of color) could this have anything to do with me choosing xorg with Generic Drivers.
~ The Jinx
I can run compiz in PCLinux OS with this xorg.conf will atempt to copy to puppy right now..... the chip is an integrated intel 865 Chipset Graphics Controller
Code: Select all
Identification
Vendor: Intel Corp.
Description: 865 Chipset Graphics Controller
Media class: DISPLAY_VGA
Connection
Bus: PCI
Bus PCI #: 0
PCI device #: 2
PCI function #: 0
Vendor ID: 0x8086
Device ID: 0x2572
Sub vendor ID: 0x1028
Sub device ID: 0x019d
Misc
Module: Card:Intel 865
Code: Select all
# File generated by XFdrake (rev 57713)
# **********************************************************************
# Refer to the xorg.conf man page for details about the format of
# this file.
# **********************************************************************
Section "Files"
# font server independent of the X server to render fonts.
FontPath "unix/:-1"
# minimal fonts to allow X to run without xfs
FontPath "/usr/share/fonts/misc:unscaled"
EndSection
Section "Extensions"
Option "Composite"
EndSection
Section "ServerFlags"
#DontZap # disable <Crtl><Alt><BS> (server abort)
#DontZoom # disable <Crtl><Alt><KP_+>/<KP_-> (resolution switching)
AllowMouseOpenFail # allows the server to start up even if the mouse does not work
EndSection
Section "Module"
Load "dbe" # Double-Buffering Extension
Load "v4l" # Video for Linux
Load "extmod"
Load "type1"
Load "freetype"
Load "glx" # 3D layer
Load "dri" # direct rendering
EndSection
Section "InputDevice"
Identifier "Keyboard1"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
Option "XkbOptions" "compose:rwin"
EndSection
Section "InputDevice"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "ExplorerPS/2"
Option "Device" "/dev/mouse"
EndSection
Section "Monitor"
Identifier "monitor1"
VendorName "Plug'n Play"
ModelName "DELL E153FP"
HorizSync 30-63
VertRefresh 56-76
# TV fullscreen mode or DVD fullscreen output.
# 768x576 @ 79 Hz, 50 kHz hsync
ModeLine "768x576" 50.00 768 832 846 1000 576 590 595 630
# 768x576 @ 100 Hz, 61.6 kHz hsync
ModeLine "768x576" 63.07 768 800 960 1024 576 578 590 616
EndSection
Section "Device"
Identifier "device1"
VendorName "Intel Corp."
BoardName "Intel 865"
Driver "i810"
Option "DPMS" "false"
Option "May_Need_ForceBIOS" "1"
Option "XaaNoOffscreenPixmaps" "1"
EndSection
Section "Screen"
Identifier "screen1"
Device "device1"
Monitor "monitor1"
DefaultColorDepth 16
Subsection "Display"
Depth 8
Modes "1024x768" "832x624" "800x600" "640x480" "480x360" "320x240"
EndSubsection
Subsection "Display"
Depth 15
Modes "1024x768" "832x624" "800x600" "640x480" "480x360" "320x240"
EndSubsection
Subsection "Display"
Depth 16
Modes "1024x768" "832x624" "800x600" "640x480" "480x360" "320x240"
EndSubsection
Subsection "Display"
Depth 24
Modes "1024x768" "832x624" "800x600" "640x480" "480x360" "320x240"
EndSubsection
EndSection
Section "ServerLayout"
Identifier "layout1"
InputDevice "Keyboard1" "CoreKeyboard"
InputDevice "Mouse1" "CorePointer"
Screen "screen1"
EndSection
- Attachments
-
- wNOPdump.tar.gz
- (11.83 KiB) Downloaded 485 times
Taking Puppy Linux to the limit of perfection. meanwhile try "puppy pfix=duct_tape" kernel parem eater.
X86: Sager NP6110 3630QM 16GB ram, Tyan Thunder 2 2x 300Mhz
Sun: SS2 , LX , SS5 , SS10 , SS20 ,Ultra 1, Ultra 10 , T2000
Mac: Platinum Plus, SE/30
X86: Sager NP6110 3630QM 16GB ram, Tyan Thunder 2 2x 300Mhz
Sun: SS2 , LX , SS5 , SS10 , SS20 ,Ultra 1, Ultra 10 , T2000
Mac: Platinum Plus, SE/30
-
- Posts: 56
- Joined: Fri 19 Jan 2007, 14:06
- Contact:
Nvidia 6200 xorg.conf using both dvi and crt outputs...
Here's what I've got going on this so far.
I'm using an Nvidia 6200.
With this xorg.conf I have it ignoring the intel onboard graphics, with full 3-D, glx, and whatever else all that stuff is...
This config is allowing me to use the xinerama extension, and have one large cube for both of my screens, or an individual cube for each, or each of the 4 sides of each cube, in an octagon, on each screen. I'd figured I'd post it in this thread to maybe help anyone out who could use it.
Keep in mind, the options for how many cubes and how they're rendered is in the options of the compizconfig settings manager.
But to get those options and have them work correctly, your xorg.conf must be configured correctly.
I'm using an Nvidia 6200.
With this xorg.conf I have it ignoring the intel onboard graphics, with full 3-D, glx, and whatever else all that stuff is...
This config is allowing me to use the xinerama extension, and have one large cube for both of my screens, or an individual cube for each, or each of the 4 sides of each cube, in an octagon, on each screen. I'd figured I'd post it in this thread to maybe help anyone out who could use it.
Code: Select all
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings: version 1.0 (buildmeister@builder3) Wed Sep 12 14:30:30 PDT 2007
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (buildmeister@builder3) Wed Sep 12 14:29:35 PDT 2007
#Special base config file used in Puppy Linux.
# **********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
# **********************************************************************
# Files section. This allows default font and rgb paths to be set
# **********************************************************************
# **********************************************************************
# Server flags section.
# **********************************************************************
#everything past here is auto-generated by Puppy's Xorg Wizard...
#PuppyHardwareProfile=NVIDIA
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
RgbPath "/usr/X11R7/lib/X11/rgb"
FontPath "/usr/X11R7/lib/X11/fonts/misc/"
FontPath "/usr/X11R7/lib/X11/fonts/Type1/"
FontPath "/usr/X11R7/lib/X11/fonts/TTF/"
EndSection
Section "Module"
# This loads the DBE extension module.
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
# This loads the font modules
Load "dbe" # Double buffer extension
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
Load "type1"
Load "freetype"
# This loads the GLX module
Load "glx"
# This loads xtrap extension, used by xrandr
Load "xtrap"
EndSection
Section "ServerFlags"
# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.
# Option "DontVTSwitch"
# Enables mode switching with xrandr
# There is a report that this can cause Xorg not to work on some
# video hardware, so default is commented-out...
# but i want to use it in xorgwizard so leave on...
# Removed Option "Xinerama" "0"
# Removed Option "Xinerama" "1"
Option "RandR" "on"
Option "Xinerama" "0"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc102"
Option "XkbLayout" "us" #xkeymap0
EndSection
Section "InputDevice"
#Option "Emulate3Timeout" "50"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2" #mouse0protocol
Option "Device" "/dev/mouse"
#Option "Emulate3Buttons"
Option "ZAxisMapping" "4 5" #scrollwheel
EndSection
Section "Modes"
#modes0modeline0
Identifier "Modes0"
EndSection
Section "Monitor"
#UseModes "Modes0" #monitor0usemodes
Identifier "Monitor0"
VendorName "Unknown"
ModelName "DELL M991"
HorizSync 30.0 - 96.0
VertRefresh 50.0 - 160.0
EndSection
Section "Monitor"
Identifier "Monitor1"
VendorName "Unknown"
ModelName "HP MX70"
HorizSync 30.0 - 70.0
VertRefresh 47.0 - 120.0
EndSection
Section "Device"
#card0driver
Identifier "Card0"
Driver "nvidia"
VendorName "nVidia Corporation"
BoardName "NV44A [GeForce 6200]"
EndSection
Section "Device"
Identifier "Videocard0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 6200"
EndSection
Section "Device"
Identifier "Videocard1"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 6200"
BusID "PCI:1:9:0"
Screen 1
EndSection
Section "Screen"
# Removed Option "TwinView" "0"
# Removed Option "metamodes" "CRT-0: 1280x1024 +0+0"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
Option "RenderAccel" "True"
Option "AllowGLXWithComposite" "True"
Option "AddARGBGLXVisuals" "True"
Option "DisableGLXRootClipping" "True"
Option "TwinView" "1"
Option "metamodes" "CRT-0: 1280x1024 +0+0, CRT-1: 1280x1024 +1280+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Screen"
Identifier "Screen1"
Device "Videocard1"
Monitor "Monitor1"
DefaultDepth 24
Option "RenderAccel" "True"
Option "AllowGLXWithComposite" "True"
Option "AddARGBGLXVisuals" "True"
Option "DisableGLXRootClipping" "True"
Option "TwinView" "0"
Option "metamodes" "CRT-1: 1280x1024 +0+0"
EndSection
Section "Extensions"
Option "Composite" "Enable"
EndSection
But to get those options and have them work correctly, your xorg.conf must be configured correctly.
[url=http://www.uptime-project.net/profile.php?uid=115727][img]http://img.uptime-project.net/img/8/115727.png[/img][/url]
I'm not too familiar with Linux so I can't run your script but everything is running well on my Dell Inspiron 9300 with Pentium M, GeForce Go 6800 and 2Gig RAM. I turned off some of effects because the shadows weren't rendering too well (funny blockiness to them).
So many options in Linux it's easy to get confused! Having a USB Drive to run linux from, though, helps to make the transition more friendly.
So many options in Linux it's easy to get confused! Having a USB Drive to run linux from, though, helps to make the transition more friendly.
Caneri & The Jinx
It suddenly occured to me that if the radeon driver does not support 5th generation ATI cards like yours then what do you do in ordinary Puppy? Do you just have to use the generic Xorg vesa driver all the time? There is an open source radeon driver that is being developed to run your cards, it's called "radeonhd". However, it's not currently in Puppy and currently lacks 3D support.
Caneri
Sounds like it worked. The acid test is:
If that doesn't return nothingness then we're in business. If you can send me a wNOPdump from within that booted session containing the installed ati.pet then I can check it out and post you a personalised xorg.conf that will enable Compiz-Fusion
The Jinx
Ah yes okay, I'll clarify that a bit: The ATI website has a 43MB program that will compile and install the most recent ATI driver. In order to run this installer you need devx_301.sfs (60MB) and kernel-source_301.sfs(56MB) aswell, so that's about 160MB just for a video driver! Not very 'Puppy'! So what I did was to do it all myself and then save and compress the result -- thus creating the ATI-8.42.3.pet weighing in at just 13MB and consisting of a single download. Much more 'Puppy' However, as I said, I am not able to test if it works as I don't have a new enough ATI card (but you do).
Right, so to test you can follow the instructions I gave previously, but just to recap:
(1) Boot into a Puppy session you are willing to lose as uninstalling the ATI.pet is rather complicated.
(2) Download or copy (using a USB stick for example) the ATI.pet and install it by double clicking on it.
(3) Upon completion, type into the terminal:
(4) Judging by Caneri's experience a full reboot might be best, therefore you will need to create a pup_save file if you haven't already so that all your changes don't get lost.
If the desktop appears then you have success, then post me a wNOPdump (see the very first post of this thread) and I can setup Compiz-Fusion for you. Let me know how it goes.
As for the forum not working, I think that applied to everyone! And the video not working properly in wNOP is very likely a sympton of generic drivers. Do you have the same issue with other versions of Puppy?
cb88
Did you try pakt's fix for Intel cards? Basically:
restart X
Bob's yer uncle
titanreign
Octagon
teajay
Thanks for the confirmation. It's great that wNOP is inspiring you to consider the possibility of using a computer without MS Windows.
It suddenly occured to me that if the radeon driver does not support 5th generation ATI cards like yours then what do you do in ordinary Puppy? Do you just have to use the generic Xorg vesa driver all the time? There is an open source radeon driver that is being developed to run your cards, it's called "radeonhd". However, it's not currently in Puppy and currently lacks 3D support.
Caneri
Sounds like it worked. The acid test is:
Code: Select all
lsmod | grep fglrx
The Jinx
Ah yes okay, I'll clarify that a bit: The ATI website has a 43MB program that will compile and install the most recent ATI driver. In order to run this installer you need devx_301.sfs (60MB) and kernel-source_301.sfs(56MB) aswell, so that's about 160MB just for a video driver! Not very 'Puppy'! So what I did was to do it all myself and then save and compress the result -- thus creating the ATI-8.42.3.pet weighing in at just 13MB and consisting of a single download. Much more 'Puppy' However, as I said, I am not able to test if it works as I don't have a new enough ATI card (but you do).
Right, so to test you can follow the instructions I gave previously, but just to recap:
(1) Boot into a Puppy session you are willing to lose as uninstalling the ATI.pet is rather complicated.
(2) Download or copy (using a USB stick for example) the ATI.pet and install it by double clicking on it.
(3) Upon completion, type into the terminal:
Code: Select all
aticonfig --initial
(4) Judging by Caneri's experience a full reboot might be best, therefore you will need to create a pup_save file if you haven't already so that all your changes don't get lost.
If the desktop appears then you have success, then post me a wNOPdump (see the very first post of this thread) and I can setup Compiz-Fusion for you. Let me know how it goes.
As for the forum not working, I think that applied to everyone! And the video not working properly in wNOP is very likely a sympton of generic drivers. Do you have the same issue with other versions of Puppy?
cb88
Did you try pakt's fix for Intel cards? Basically:
Code: Select all
modprobe -n i915
modprobe i915
Bob's yer uncle
titanreign
Octagon
teajay
Thanks for the confirmation. It's great that wNOP is inspiring you to consider the possibility of using a computer without MS Windows.
lsmod | grep fglrx...returned nothing..rats.
I also have no aticonfig file in /usr/bin..thus no aticonfig --initial
The install broke form my playing around too much.. so I need to restart a new install...
As for what I did for 3d before..I only had it running once and lost it when I forgot to use puppy pfix=ram on a test run for a new puppy release.
I'll look again later tonight....I just gotta wobble!
EDIT..Nov23..I am not going to have time to test for awhile...I have to get some other work done...I'll be following and get back when I can...rats
I also have no aticonfig file in /usr/bin..thus no aticonfig --initial
The install broke form my playing around too much.. so I need to restart a new install...
As for what I did for 3d before..I only had it running once and lost it when I forgot to use puppy pfix=ram on a test run for a new puppy release.
I'll look again later tonight....I just gotta wobble!
EDIT..Nov23..I am not going to have time to test for awhile...I have to get some other work done...I'll be following and get back when I can...rats
[color=darkred][i]Be not afraid to grow slowly, only be afraid of standing still.[/i]
Chinese Proverb[/color]
Chinese Proverb[/color]
ok...work can wait...just gotta wobble
The beauty of puppy is to reinstall an OS is measured in minutes...you just have to love that.
I have a dump file this time..and I didn't have to do a pupsave...dunno why..I did a save anyway so I can get back to where I left off.
alas no output from lsmod | grep fglrx....
ATI Mobility Radeon X1600/256mb (M56 71C5)
The beauty of puppy is to reinstall an OS is measured in minutes...you just have to love that.
I have a dump file this time..and I didn't have to do a pupsave...dunno why..I did a save anyway so I can get back to where I left off.
alas no output from lsmod | grep fglrx....
ATI Mobility Radeon X1600/256mb (M56 71C5)
- Attachments
-
- wNOPdump.tar.gz
- (11.27 KiB) Downloaded 499 times
Thanks Caneri. I see what the problem is -- the directory structure of the ati dotpet is wrong, I'm going to have to try another way of packaging up the dotpet -- I've got a lot to learn about it so I'll probably take my time over it. I've removed the link from my previous post. Meanwhile, you could always try the devx and kernel-source method I mentioned before, that will automatically put the ati driver files in the correct directories. Either way here is your personalised xorg.conf for when the driver is properly installed. If you do use the devx/kernel method you won't need to run aticonfig afterwards, just replace your xorg.conf with the one I edited for you. Please feel free to ask for any help if you try this way. I mean I have to get this ati.pet working anyway cos it will be essential to wNOP2.