Puppy Linux Discussion Forum

[jemimah]

Someone mentioned on another forum that Chromium was crashing the kernel in Lupu. I don't have time at the moment to test it, but I though I'd post the solution here.

Chrome makes heavy use of /dev/shm in a way that generally kills AUFS after a short time. The solution is to mount some tmpfs onto /dev/shm so that the shared memory is not inside the AUFS union.

I fix it in my puplets, by adding 'mount -t tmpfs none /dev/shm' to my sysinit script. I mentioned this problem to Barry earlier, so LuPu may already have the fix - reading the post about Chromium crashing makes me think it might not be there.

[puprag]

when recording Sweep audio editor is getting maxed out to 100% with lucid pup 5.0.0, not tried 5.0.1 but Xorg is taking up like 70% of the cpu? when recording with sweep, had different results with different cpu's amd got down to 50% but intel is maxed out to a 100 no matter what I have tried.

[playdayz]

I *think* the problem with Chromium is in the testing version of luci-202 and 203. The reason for it is that Chromium 5, the one in Quickpet, seems to crash with the gecko-mediaplayer browser plugins--which are being tested in luci-203 as part of mplayer, which is to replace gxine.

If you are having any trouble with gxine you might want to take an early look at mplayer. In the tests it is looking very good.

So here are gnome-mplayer and mplayer. You need to install both. Gnome-mplayer is a frontend for mplayer--gnome-mplayer has two problems we know about: 1) it does not do full screen properly, and 2) it does not do DVDs with Menus. Other than that it seems to work. On the plus side, it is drag and drop onto the desktop icon, or open the program and look for files of course. I haven't been testing on 5.0.1 but I just run through some quick tests and it played everything that the 5.1 version plays--which is everything I have tried.

http://www.diddywahdiddy.net/Puppy500/gnome-mplayer-Lucid.pet
http://www.diddywahdiddy.net/Puppy500/mplayer-1.0rc3.pet

I regard this as a hot fix for people who have been having trouble with gxine. But as I have said--no update is without some risk, so please back up everything important.

Oh yes, I think it will make Chromium 5 crash, so if you want to use both you should go to /usr/lib/mozilla/plugins and delete the 4 gecko-mediaplayer plugins.

It develops that gnome-mplayer, the frontend for mplayer, will play the videos full screen if the High Performance graphics are enabled. This is another upcoming feature in 5.1. High Performance is just a fun way to say that the graphics use hardware acceleration, and so they can be 10 times or more faster than basic graphics.

This package is for Radeon, Intel, and most other graphics chips except Nvidia. To install, download the pet, click to install, and then Menu -> Shutdown -> Restart the X server. After that you can open a terminal and enter 'glxgears' to see that things are working. All graphics *might* be more stable when the High Performance option is enabled. That might sound counter-intuitive but I believe that most software is probably tested on the High Performance graphics--because those would be standard in some popular distributions.

http://www.diddywahdiddy.net/Puppy500/xorg_full-1.1-lupu.pet

The only oddness I know of about the xorg_full graphics is that you need to already have a lupusave file created--so that means don't install them the first time you boot up--wait until you have shut down and created a lupusave file.

[rsaavedra]

Ok I went to my parents place where the Sony PC I talked about was, and was able to replicate installation options that produce a non-booting Puppy.

I'm sure you guys ought to reproduce this and get exactly the same results if choosing these options. Whoever has a chance to try them, if you also get the problem please indicate so; if you get a different result, please also indicate so.

First of all, and just in case, the machine has a WinXP installation on one ntfs partition, then there's another ntfs partition with just data, then there's a logical partition which has inside just two partitions: a linux-swap, and the one partition for Puppy. (I really don't think the partition arrangement matters, but the dual boot setup aspect ought to matter.)

Booted Puppy from the CD with the puppy pfix=ram option, so as not to be affected by whatever puppy was on the harddrive already. Reformatted that latter partition above, so no more Puppy in the machine's harddrive. Turned on the boot flag of that partition.

Then here's exactly an enumeration of all the options I chose to get the problematic installation. As you'll see, it was actually a FRUGAL, not a FULL install what I had done. I had mentioned "full" because there was nothing else on the partition, and the partition was going to be exclusively for Puppy; but even so, I think the installation option I had chosen was Frugal, not Full. Here are the options:

- Install icon (on Desktop)
- Click button to run the Universal Installer [doggy button]
- Internal (IDE or SATA) hard drive [OK]
- sda ATA ... 18.6 GiB [OK] (Size here will depend on your harddrive, of course)
- sda6 size 6.174 GiB, install Puppy to sda6: [doggy button] (partition and size will depend on your particular config, of course)
- You have chosen ... on /dev/sda6 which has ext3 filesystem... and size is ... [OK]
- ... [CD]
- ... [OK]
- ... [FRUGAL]
- ... puppy500 [OK]
<A NicoEdit window pops up showing menu.lst text. I ignore it and simply close it.>
- "If you do not have GRUB or GRUB4DOS installed, just click OK, then go to system menu and run the GRUB or GRUB4DOS installer" [OK]
- "Okay, all done" [OK]

- Menu -> System -> Grub bootloader config
- Simple [OK]
- Standard (frame buffer console) [OK]
- "Where do you want grub files to go?" /dev/sda6 [OK]
- MBR (possibly unsafe) [OK]
- "Grub successfully installed on MBR..." [OK]

- Menu -> Shutdown -> Reboot computer
- [DO NOT SAVE]


Machine reboots. Grub menu appears. I select the "Linux on /dev/sda6" option, and get:

Error 15: File not found

And the machine halts. Puppy never boots.

Those however can't be exactly the same options I originally had run which left the Puppy install unbootable, because with these options above I did not get the kernel panic message. Still, they yield a non-bootable Puppy. That suggests there are more than one set of install options that leave Puppy non-bootable, because of (easy to fix, yet annoying and boot-fatal) misconfigurations in menu.lst.

Once again, properly editing menu.lst fixes these problems, but in any case, the installation does not boot "as is" with those options, and this problem is extremely likely to put off newbies who happen to try those install options.

[8-bit]

I have installed a few packages on Lucid Puppy 5.0 and have had support files disappear.
The thing is that I do not know why those files disappeared.
Is it just me and my frugal install, or have others had that problem?
Any idea what is causing it?

Also, after installing my xerox p12 lazer printer, I find that abiword sees the paper type as A4 even though I had set it up as letter in CUPS printer options.
Also, paper type selection is grayed out in abiword.
I can print a test page in cups just fine, but if I try to print the printer test file in abiword, the printer errors out and I have to restart it.
EDIT!
After a reboot of Puppy, the paper size/type works in abiword.
So that one is a false report.
Sorry for it.

[bremer]

Hi, I've been carrying around a tiny boot CD of Puppy with me for over a year and decided it was time to upgrade. Unforunately, version 5.01 does not work for me as well as my last puppy.

The number one regression for me is that the video probe gives me a blank screen and hangs. The problem is similar to http://murga-linux.com/puppy/viewtopic.php?p=421475#421475. After choosing 1024x768, I just get a blank screen. Switching virtual terminals does not work and I must reboot by holding down the powerbutton. Using the VESA driver does work.

My hardware is a Toshiba Satellite A55-S326 laptop. The builtin video device is an Intel 855GM, which has long been well supported by Xorg.

I apologize if this bug has already been reported. I have read the FAQ and searched using both the forum search tool and the Google. The Google was slightly more helpful as the forum search returned a thread with 83 pages with no indication of which page had the terms I was searching for.

[ICPUG]

bremer,

This has been reported a few times now and the Intel problem in general has been discussed on Barry's developer blog.

You will find that the problem is not just related to Puppy. For example, the latest Ubuntu has the same problem. It is all to do with the combination of kernel version and intel driver used. The way the kernel is compiled may have some impact.

At the moment it would seem that any linux using a 2.6.33+ kernel is affected and replacing the intel.drv with i810.drv (used in the past) does not help.

It would seem that Intel and Linux now think Intel855 is too old to support.

As far as Puppy is concerned it looks as if we might have to wait for Wary (currently in test) to appear to get full support of Intel855 back again.

There is a lot of maybe's and mights in the above. This is because the thread on LighthousePup 5.0.0.a has also discussed this and introduced some new options to try. While some Intel graphics have been got working using this info no one has yet reported success with Intel855.

[rickyricardo]

[playdayz]

puprag

[playdayz]

[smokey01]

[rickyricardo]

[bremer]

[rjbrewer]

My inspiron 700m has Intel 855gm graphics.
The 2 versions of Wary are the best for xorg-vesa of any Puppy
I've ever seen.
The Lupu-Lucid versions.......the worst.

[ICPUG]