I attach a pet for ATI cards.
It is the radeon driver, not radeonhd, as radeonhd does not work on my system.
If someone wants to test radeonhd, I can upload that, too, on request.

It is basically intended for this case:

you have a new card, like the HD 4850.
You want DRI accelleration to watch videos fullscreen.
You do NOT need 3D accelleration. It is simply not added yet for the R600/R700 chips.

If you need accellerated 3D, you must use the Catalyst driver instead, but that is slower with 2D.

I don't know how these drivers work with older chips. No idea, if 3D works with them. If you want to try that, check it without savefile first (puppy pfix=ram).

To build the pet I had to run these special steps:
compile git from http://git-scm.com/.
then run such commands:
git clone git://anongit.freedesktop.org/mesa/drm
cd linux-core
git checkout -b r6xx-r7xx-support origin/r6xx-r7xx-support
make radeon.o drm.o

Then copy radeon.ko and drm.ko to the corresponding subfolders in /lib/.

I realize I have not reported back.
I still have the freeze at: freeing unused kernel memory. 376k freed. _________________Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
Consult Wikka
Use peppyy's puppysearch

I added the radeonhd pet, that does not work for me. Maybe I forgot something?
It also needs the other ati pet, as that includes the new kernelmodules.
To test it, edit /etc/X11/xorg.conf, and replace
Driver "radeon"
with
Driver "radeonhd"

New: Mesa 7.4.
This is a bugfix release of 7.3.
You might not see improvements, if Opengl worked for you before.
I cannot check this pet on my own, as my Ati/Nvidia cards are not supported, I need the unfree drivers instead for OpenGL.
I made it as pet, not as sfs. This ensures, that formerly installed OpenGL/dri files get overwritten. With sfs files, this is not the case.
You can get back 30 MB free diskspace, if you delete unneeded dri modues in /usr/X11R7/lib/dri/ after installation.
The pet includes /usr/local/graficsdrivers/mesa.tgz required for newyearspups modified xorgwizard.

To test openGL, install ati-stuff.pet.
Then type:
antinspect -fps
This should launch a small application displaying framerates.
It should run smooth with more that 10 fps ( typically 24-48 ).

Use all at own risk, and best try it with a new savefile first (puppy pfix=ram).
Please tell us, if you have success or not.

I ran across a bug in this version of your pup that did not appear in the first version. It's extremely slow in copying files across a local gigabit network to a Vista or Server 2008 computer. This shows up more obviously on larger (100 megabyte or larger) files. I verified using different computers as the origin and destination. I checked Newyear's pup and the later releases based on this pup are just as slow. Doing the same copying using your earlier pup or the earlier releases of Newyear's pup are very fast.

Top, Pprocess viewer and Conky show very heavy use of the processor, but do not pinpoint any particular process as the one eating up the processor. I tried a variety of different file managers, but none transfer any faster. The regular internet can download as fast as always from my high speed connection.

That's all the clues that I have. I hope someone can diagnose this one!!!

The pets include a modified xorgwizard.
The original xorgwizard was renamed to xorgwizard-puppy.
The new one extracts and deletes several files, depending on your selection.
This is required to solve conflicts among the different drivers.

They are pretty huge, especially the one from Ati.
I had to create a savefile with 256 MB, to be able to install it.
After the pet was installed, the ati will extract 65 MB when you select the driver in xorgwizard. Nvidia needs around 40 MB.
This is more than in the last versions of Newyearspup.
I had to do it, so that other Ati drivers can be installed in addition in future, as 9.3 is the last release, that supports a wide range of cards. 9.4 will support only very new cards.

The new xorgwizard does NOT check yet, if enough space is available.
So ensure, you have enugh space.I'd recommend to have ALWAYS at least 100 MB free diskspace in your savefile

I ran across a bug in this version of your pup that did not appear in the first version. It's extremely slow in copying files across a local gigabit network to a Vista or Server 2008 computer. This shows up more obviously on larger (100 megabyte or larger) files. I verified using different computers as the origin and destination. I checked Newyear's pup and the later releases based on this pup are just as slow. Doing the same copying using your earlier pup or the earlier releases of Newyear's pup are very fast.

Top, Pprocess viewer and Conky show very heavy use of the processor, but do not pinpoint any particular process as the one eating up the processor. I tried a variety of different file managers, but none transfer any faster. The regular internet can download as fast as always from my high speed connection.

That's all the clues that I have. I hope someone can diagnose this one!!!

After a lot of Googling and experimenting, I came up with this partial solution:

By adding mountcifs-1.5.pet from James Bond and changing the file manager in pnethood to Thunar, I have gotten the network file copy speed up to acceptable (not as fast as the earlier pup). Thunar gives a progress bar so that helps psychologically during the wait. You could also use Pcmanfm, but it is slightly unstable for network copies. The processor use is still high, but not as high as it was. The final result is something that I can live with versus something I could not.

What would it take for me to revert this pup to the previous kernel as a test for network file copying? When I just drop in initrd.gz and vmlinuz, it does not seem to detect sound properly although in a very quick test, other things seemed to work.

I attach a pet for ATI cards.
It is the radeon driver, not radeonhd, as radeonhd does not work on my system.
If someone wants to test radeonhd, I can upload that, too, on request.

It is basically intended for this case:

you have a new card, like the HD 4850.
You want DRI accelleration to watch videos fullscreen.
You do NOT need 3D accelleration. It is simply not added yet for the R600/R700 chips.

If you need accellerated 3D, you must use the Catalyst driver instead, but that is slower with 2D.

Mark, I didn't notice any difference when I installed this. I already had the radeon driver with dri enabled just from what came with Wow's Unnamed Puplet. I must be missing something. When I tried to uninstall the pet however, I had trouble until I thought to start X with the xvesa driver. The first three times I tried to uninstall the screen froze as soon as I clicked the Remove Them button. I am going to try the proprietary ati drivers now.

.<Add> The proprietary ati catalyst driver is working nicely, just as in NYP. Thanks again.

playdayz,
did your card work with the drivers (wows and mine)?
Or not?
This is not clear for me.

This driver (from me) should be required only, if wows included driver does not work, because your card is too new.
My HD4850 does not work with wows driver, I only can use vesa. With the new one, it works, so I get correct screenresolution and accellerated video playback.

However, I also use the Catalyst driver now, as that supports 3D, too, and has less bugs (JWM/Icewm).

Sorry for not being clear MU. Both drivers work perfectly in both pups with my hd3850. I should say "all three drivers" the fglrx driver and both yours and Wow's xorg drivers. That was what I was trying to ask, whether there were any differences between the two xorg dirvers, and as you said, yes there are.

The differences between the proprietary and the xorg drivers are that the fglrx driver is faster by 47 to 28 fps in antinspect (because, as you said, of the hardware acceleration) and that the fglrx driver supports Compiz (again, as you said, because of the hardware acceleration). Right now I am using the xorg radeon driver (yours, in NYP) to see if it feels any faster using a browser (I believe it tests faster on 2D but I have not seen any obvious difference).

I greatly appreciate the trouble you take to prepare the drivers--the only choice I have with stock Puppy is the xvesa driver.

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