Posted: Wed 20 May 2009, 17:05
Thanks for this T. Works flawlessly...............
READ-ONLY Archive
https://oldforum.puppylinux.com/
mafae wrote:Menu>System>Manage Printing
Kills CUPS nearly always!
In updated 4.21 again the same problem.floborg wrote:In the lower left-hand corner of the desktop, the drive icons are clustered on top of one another. In the lower right-hand corner, the Lock and Trash icons are clustered on top of one another.
The above happened using an 800x600 resolution, but did not occur in Puppy 4.1.2.
I can verify this bug. Again, it does not occur in Barry's latest puppy release (upup).mave wrote:In updated 4.21 again the same problem.floborg wrote:In the lower left-hand corner of the desktop, the drive icons are clustered on top of one another. In the lower right-hand corner, the Lock and Trash icons are clustered on top of one another.
The above happened using an 800x600 resolution, but did not occur in Puppy 4.1.2.
Any help?
I believe this has been fixed in 4.2.1tempestuous wrote:Because I have never bothered to download Puppy 4.2, I only learned about this problem with Broadcom wifi devices recently:That's because the new Broadcom b43/b43legacy modules, which work in conjunction with the ssb module, should be used in preference to the deprecated bcm43xx module. The firmware in Puppy is compatible with b43/b43legacy, and is NOT compatible with bcm43xx.trio wrote:In 4.2 Final..bcm43xx is still being a problem...for those of you who wants a workaround..just edit /etc/rc.d/MODULESCONFIG
Unfortunately (groan) there are also reports that Puppy 4.2 fails to automatically uncompress the b43 firmware, but hopefully this may be fixed once the preferences are corrected.
I now attach the correct MODULESCONFIG with PREFLIST entries. This is to replace trio's "No_bcm43xx_patch.pet", which is wrong.
Please use this in the next 4.2 update.
It has been placed where it belongs ... here:SilverPuppy wrote:Hey moderators,
Where'd you move the hornets nest I stirred up to? I don't see it, but it's obviously been relocated......
The only thing I've noticed so far that didn't work out-of-the-box on my system [with Puppy 4.2.1] was sound (never had that problem with any pup before). I haven't checked all the above threads to see if others have had the same problem because I fixed it for myself. However, a new user wouldn't have a clue how to fix it. For me I had to:
open an rxct console and enter:
alsaconf
That program correctly detected my card and on the next boot the until then missing taskbar volume icon appeared and sound worked.
First, @ WhoDo,makropo wrote:I believe this has been fixed in 4.2.1tempestuous wrote:Because I have never bothered to download Puppy 4.2, I only learned about this problem with Broadcom wifi devices recently:That's because the new Broadcom b43/b43legacy modules, which work in conjunction with the ssb module, should be used in preference to the deprecated bcm43xx module. The firmware in Puppy is compatible with b43/b43legacy, and is NOT compatible with bcm43xx.trio wrote:In 4.2 Final..bcm43xx is still being a problem...for those of you who wants a workaround..just edit /etc/rc.d/MODULESCONFIG
Unfortunately (groan) there are also reports that Puppy 4.2 fails to automatically uncompress the b43 firmware, but hopefully this may be fixed once the preferences are corrected.
I now attach the correct MODULESCONFIG with PREFLIST entries. This is to replace trio's "No_bcm43xx_patch.pet", which is wrong.
Please use this in the next 4.2 update.
Until 4.2.1 was released I was removing 4.2 and booting 4.1.2 for a wireless connection. Now in 4.2.1 b43 loads and wireless is detected right away.
Yes, that is a major problem. Firefox, for example, also uses sqlite to store lots of config data and the database can grow large over time: I find that urlclassifier3.sqlite-journal become pretty huge quite quickly.Proudog wrote:This and important bug, the Mozilla browser cache is eating the size of pup_save.2fs, file in the frugal install.