Thanks, Mark!!! Wonderful! (':D')MU wrote:I uploaded proprietary graficsdrivers:
Mark
Unnamed puplet 1.1 (puppy411 kernel-2.6.28.5 Xorg-7.4 LXDE)
Re: Bug copying files across netwwork
After a lot of Googling and experimenting, I came up with this partial solution:techtype wrote: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!!!
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.
Previous kernel
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.
MU said:
.<Add> The proprietary ati catalyst driver is working nicely, just as in NYP. Thanks again.
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.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.
.<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).
Mark
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).
Mark
- Béèm
- Posts: 11763
- Joined: Wed 22 Nov 2006, 00:47
- Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win
Apparently this issue is a tough one.Béèm wrote:I realize I have not reported back.wow wrote:@Béèm, try to add this boot option:_________________________________________________________________Code: Select all
memory_corruption_check=1
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
Find packages in a snap and install using Puppy Package Manager (Menu).
Consult Wikka
Use peppyy's puppysearch
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.
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.
This message extends:
http://www.murga-linux.com/puppy/viewto ... 007#292007
I added Ati Catalyst 9.4.
Important:
the r300 to r500 chips are no longer supported by this driver!
So you need at least a HD 2400.
For older chips, use Catalyst 9.3.
Or the free ati radeon driver in xorgwizards autodetection.
I also updated the NYP xorgwizard in it.
The menus are easier to use now.
Mark
http://www.murga-linux.com/puppy/viewto ... 007#292007
I added Ati Catalyst 9.4.
Important:
the r300 to r500 chips are no longer supported by this driver!
So you need at least a HD 2400.
For older chips, use Catalyst 9.3.
Or the free ati radeon driver in xorgwizards autodetection.
I also updated the NYP xorgwizard in it.
The menus are easier to use now.
Mark
Last edited by MU on Sat 18 Apr 2009, 19:36, edited 1 time in total.
I got a report, that INTEL driver 2.6.3 works erratic on a G45.
http://www.murga-linux.com/puppy/viewtopic.php?t=41343
That driver is included in Newyearspup 02rc9.
Installing the 2.6.0 fixed it.
There remains an issue:
the display is very dark.
I found this message about a non working backlight:
https://bugzilla.redhat.com/show_bug.cgi?id=492458
According to reports, this is fixed with driver 2.6.99.x from april, 3rd.
So I compiled the latest driver now.
It also requires a new libdrm.
I attach them for tests.
Please let me know, if they work better than 2.6.0.
Mark
http://www.murga-linux.com/puppy/viewtopic.php?t=41343
That driver is included in Newyearspup 02rc9.
Installing the 2.6.0 fixed it.
There remains an issue:
the display is very dark.
I found this message about a non working backlight:
https://bugzilla.redhat.com/show_bug.cgi?id=492458
According to reports, this is fixed with driver 2.6.99.x from april, 3rd.
So I compiled the latest driver now.
It also requires a new libdrm.
I attach them for tests.
Please let me know, if they work better than 2.6.0.
Mark
- Attachments
-
- libdrm-2.4.9-i486.pet
- (113.85 KiB) Downloaded 636 times
Last edited by MU on Sat 18 Apr 2009, 18:14, edited 1 time in total.
This message extends:
http://www.murga-linux.com/puppy/viewto ... 007#292007
I updated all the proprietary Ati/Nvidia pets.
Changes:
- replaced Nvidia 180.29 with Nvidia 180.44.
- Included newest NYP-xorgwizard in all pets.
- In the Nvidia menu, you now can read a list, that shows, which driver supports which card.
Mark
http://www.murga-linux.com/puppy/viewto ... 007#292007
I updated all the proprietary Ati/Nvidia pets.
Changes:
- replaced Nvidia 180.29 with Nvidia 180.44.
- Included newest NYP-xorgwizard in all pets.
- In the Nvidia menu, you now can read a list, that shows, which driver supports which card.
Mark
Thanks, Mark. You are the graphic card master!!MU wrote:This message extends:
http://www.murga-linux.com/puppy/viewto ... 007#292007
I updated all the proprietary Ati/Nvidia pets.
Mark
Newer kernel
The new Fatdog pup has kernel 2.6.28.6 and has fast local network copy. I tried several times to drop the kernel into this pup, but I am not yet up to the task. (even trying Mark's instructions, I get a lot of scary errors about the file system -- I don't want to lose my other work)
Updated the Ati/Nvidia pets again, they now include this bugfix:
http://www.murga-linux.com/puppy/viewto ... 634#298634
Mark
http://www.murga-linux.com/puppy/viewto ... 634#298634
Mark