I guess you could say we are "official" now...

Greg, please see the main post for link, same thread actually. Please let me know if it works.JustGreg wrote:I have been using Slacko 5.3.3 on my ASUS Eee PC and it works just fine. When I attempt to boot Slacko 5.4, xorgwizard failed both initially and a manual attempt. ASUS Eee PC uses the Intel Atom with Intel Poulsbo Graphic Chip (500 GMA). Normally, one uses the vesa driver with the Intel hack to the mode table. This has work for a good while. I am surprised that the failure.
I also tried Precise Puppy 5.4.1 and got the same failure. I suspect the problem may be in the Woof build, which is common to the two versions.
For now, I will be using Slacko 5.3.3 with this computer. I did check on possible solutions. Tempestuous did post drivers for Puppy 5.1 back awhile. Any thoughts on possible solutions?
12-10 update: I did check Tempestuous drivers for Puppy 5.0/5.1 The kernel module is build for kernel 2.6.33.2 and not compatible with Slacko 5.4 kernel 3.2.33 I did more searching and found the problem with Slacko 5.4. Tempestuous explains it in this post:http://www.murga-linux.com/puppy/viewto ... 1684246909
Same here, on an HP laptop. You can see the desktop for a split second, then it goes back into suspend mode. If I hit Ctrl-Alt-Backspace at precisely the right moment, I can xwin back in to it.liro wrote:Hi. As recommended by darkcity in this thread in the Beginners Help forum, here's a problem I have with the new Slacko 5.4:
liro wrote:When I first started using Puppy earlier this year, I originally decided to use Wary (5.3), thinking it might be more suitable for my oldish laptop (IBM Thinkpad X31), but eventually changed to Slacko 5.3.3, which has run fine for me since.
One of the main reasons I stopped using Wary was due to a problem with "suspension" on closing the laptop lid. It would suspend okay, but on reopening the lid it wouldn't wake up again, leaving me with a black screen and having to reboot. After spending too much time messing about with the ACPI settings, I eventually gave up and started using Slacko instead.
Now... I've just tested out Slacko 5.4 and unfortunately this same suspension problem I had with Wary has reappeared in the newer version of Slacko.
Does anyone know what has changed from Slacko 5.3.3 to Slacko 5.4 for this problem to have come back? (and if so, how I can fix it). If there's no simple solution, I think I'll just stick with 5.3.3 for now...
Thanks.
Code: Select all
cat /dev/zero > /initrd/pup_ro1/root/bigtestfile
Code: Select all
cat /dev/zero > /initrd/pup_rw/root/bigtestfile
@01micko01micko wrote: Firstly, It's Christmas again and once again Joe Wing is back in action. He is up to revision 587 as of 17 December and seems to have fixed the compositing bug which first appeared in revision 520 (or so).
mozilla-firefox8-bit wrote:I had downloaded and am using Slacko 5.4 Final frugally installed.
The md5sum checks out ok.
But the list of built in files seems to lack inclusion of Firefox in the list.
I want to be able to completely remove Firefox and use Seamonkey in it's place.
I currently have Seamonkey installed and did a rename of the hidden file .mozilla in the /root directory to .oldmozilla.
I then systemlinked my .mozilla directory into /root so I can use it for all my installs of Puppy running Seamonkey.
The problem I am having is that I am getting severe pauses when entering text in a post, videos are also not playing properly etc. when running Seamonkey.
I think it might be a cache problem with Firefox caching stuff even though it is not running but Seamonkey is.
So, is there a list of the files that are installed by Firefox that I can delete and then do a reinstall of Seamonkey.
Of course, I would initially remove the link to my external .mozilla file to protect it until I had Seamonkey installed.
Suggestions gladly accepted.
Code: Select all
echo 1 > /proc/sys/vm/dirty_background_ratio
echo 1 > /proc/sys/vm/dirty_ratio
As we are coming up on the end of the year I want to take a look at a project which is unique and outside the mainstream of Linux projects. I don't think any project embodies distinct and useful technology quite as well as Puppy Linux does. Puppy's 5.4 "Slacko" edition was released recently and it struck me as an interesting and fun way to wrap up the year.
There is a bug in 587-8-9 that causes random X crashes. I have been working with Joe on this and we believe it is solved in revision 590 (attached).01micko wrote: Firstly, It's Christmas again and once again Joe Wing is back in action. He is up to revision 587 as of 17 December and seems to have fixed the compositing bug which first appeared in revision 520 (or so).
Thanks 01micko. Testing jwm-590 now in Upup Precise. If X has not crashed in 24 hours, it surely will look better than previous versions.I tested with new jwm 588 and 589 versions. I got several times X crash and in kernel messages I noticed jwm seqfault message. So...I didnt upgrade jwm. I will see how jwm matures, but nice to see that Joe Wing is again in Christmas time working with jwm.
Yes, I have been compiling for myself with '--enable-debug' and sending the /tmp/xerrs.log to Joe. I did find a reliable way to reproduce the crash, as did Joe and it is fixed in 590.pemasu wrote:From my previous post.
http://murga-linux.com/puppy/viewtopic. ... 579#673579Thanks 01micko. Testing jwm-590 now in Upup Precise. If X has not crashed in 24 hours, it surely will look better than previous versions.I tested with new jwm 588 and 589 versions. I got several times X crash and in kernel messages I noticed jwm seqfault message. So...I didnt upgrade jwm. I will see how jwm matures, but nice to see that Joe Wing is again in Christmas time working with jwm.