(old)Puppy Linux Discussion Forum

Posted: **Sun 19 Sep 2010, 13:23**

For laptops with Synaptics touchpads (Dell D600 series and others), I found it helpful to add the following to /etc/X11/xorg.conf in the "Synaptics Mouse" section.
This will keep the cursor from jumping around when you are typing.
Option "PalmDetect" "1"
Option "PalmMinWidth" "10"
Option "PalmMinZ" "10"

Also, this will enable touchpad tapping:
Option "MaxTapTime" "225"
Option "TapButton1" "1"

There are many other options to fool with.
Try synclient -l
from a command console to get the complete list.

Posted: **Sun 19 Sep 2010, 19:59**

Lighthouse Pup 5.00 F (Build 500) released,
Mariner, KDE and Voyager add-ons also updated.
-TazOC

Posted: **Mon 20 Sep 2010, 17:21**

Quick first impressions:
I set up and ran 5F using a copy of my 5D pupsave file.
Update went OK as advertised. I used bootmanager to select new "5F-versions" of Mariner and KDE .sfs files. I think the ability to keep .sfs files in the sub-dir makes good sense, so I used it for the mariner and kde .sfs files. I found that it works fine but bootmanager does not distinguish between .sfs files in /mnt/home from those in /mnt/home/lhp5F so I need to move those other .sfs files to their appropriate sub-dirs so they do not appear in the .sfs list unless common to several versions. (... but does this feature work for previous versions?)
Rebooted into LXDE (that had been my 5D default). Keeps the background through reboots, and has the new network interface system tray app.
Tried KDE4 but it quits before the desktop - falls out to the selection menu. Tried dropping out of X and back again - same. Tried rebooting - same.
Tried Xfce which worked OK but lost the background on reboot.
I am using the same C-F .sfs file as before.
B.

Posted: **Mon 20 Sep 2010, 23:07**

Hi Barburo,
Thanks for the feedback.

Barburo wrote:I think the ability to keep .sfs files in the sub-dir makes good sense, so I used it for the mariner and kde .sfs files. I found that it works fine but bootmanager does not distinguish between .sfs files in /mnt/home from those in /mnt/home/lhp5F so I need to move those other .sfs files to their appropriate sub-dirs so they do not appear in the .sfs list unless common to several versions. (... but does this feature work for previous versions?)

No, that feature is new for Lighthouse 5.00 F and the latest Woof, and only works if the pupsave is in a subdirectory. When booting from GRUB use psubdir parameter e.g., psubdir=lhp5F on the kernel line. So for now, keep SFS files for other versions at /mnt/home.

Rebooted into LXDE (that had been my 5D default). Keeps the background through reboots, and has the new network interface system tray app.
Tried KDE4 but it quits before the desktop - falls out to the selection menu. Tried dropping out of X and back again - same. Tried rebooting - same.

Hmm, strange. What is the o/p of

Code: Select all

plasma-desktop --version
kdeinit4 --version

if that looks normal, exit to command line and type xwin startkde44 (that bypasses the logout panel, which runs from xwin startkde.)

Tried Xfce which worked OK but lost the background on reboot.
I am using the same C-F .sfs file as before.
B.

If Xfce misses the background, edit /etc/xfce/xdg/xfce4/xinitrc, inserting 2 lines at the beginning like this:

Code: Select all

#!/bin/sh
. /etc/profile #100907 TazOC (for wallpaper bug reported by Barburo)
sleep .5 #100907 TazOC

(There must be a space between '.' and /etc/profile.)
-TazOC

Posted: **Tue 21 Sep 2010, 04:28**

I upgraded a frugal install from Lighthouse D to F via the Xdelta3 patches.
Updated Mariner and Voyager via Xdelta3 also.
Worked perfectly,
Upgrade time, including the download, was maybe a half hour. Great work.
My old D spupsave.2fs updated on startup as well.

A couple of small things.
On every reboot or shutdown, after the spupsave.2fs already saved message, I get 5 occurrences of:
modprobe: FATAL /sys is not mounted.
I have no automount drives and no harm is caused by this other than being startled by the word FATAL.

qps fails to start with: qps-qt4 not found.
qps-qt3 works correctly.

Posted: **Tue 21 Sep 2010, 07:03**

Hi TazOC,
The output from those commands:

bash-4.1# kdeinit4 --version
Qt: 4.6.2
KDE: 4.4.4 (KDE 4.4.4)

bash-4.1# plasma-desktop --version
plasma-desktop: error while loading shared libraries: libQtScript.so.4: cannot open shared object file: No such file or directory

... so I guess I'm missing a library. I had noticed something amiss in 5D KDE desktop but it still functioned OK.

I thought perhaps that the "lost" xfce desktop was due to Desktop getting set somehow to "Solid Color" instead of "Transparent" but it happened again so I put in your /etc/profile line and that seems to fix it.
B.

Posted: **Tue 21 Sep 2010, 18:09**

[quote]Çüìž@9*Çªó

Posted: **Tue 21 Sep 2010, 22:13**

[quote="Sage"][quote]Çüìž@9*Çªó

Posted: **Tue 21 Sep 2010, 22:57**

@All,
I've found an inconsistency with the way that SFS files are layered in LHP 5.00 F when one or more are in a subdir. They are loaded, but in a different order than if all are in /mnt/home. This is significant in Lighthouse because the KDE and Mariner SFS must be layered above the others. That is why their filename begins with a numeral, e.g., 5-Mariner-5F_500.sfs

Until this is sorted out, if you have moved any SFS add-ons into a subdir e.g., /mnt/home/subdir/5-Mariner-5F_500.sfs, please move them back to /mnt/home, re-run BootManager and deselect back to the left pane the SFS that were moved, then re-select them back to the right pane, and reboot. (This does not affect the main file spup-500.sfs--it is fine in a subdir.)

Please try that first if something isn't right with the latest release.

Barburo,
Please do the same as that could be the reason for KDE not starting. When that is done as described above, open /initrd/tmp/EXTRASFSS with a text editor and verify that /mnt/dev_save/4-KDE-4.4.4-F.sfs is listed first. If so, and KDE still won't start, please let me know.
Thanks,
TazOC

Posted: **Wed 22 Sep 2010, 01:06**

HI TazOC,

5F is working great as a new frugal installation. Only problem noted is that I was unable to update a 5D save file. The file appeared to update, but never completed the boot operation. New save file works great. I'm using the KDE desktop, other than jwm, haven't tried the others.

Cheers,
Jim

Posted: **Wed 22 Sep 2010, 01:38**

Hi Jim,
Thanks for testing 5.00 F. After the boot failed did you happen to run click-to-verify, or boot from the new CD? Do you recall if a specific error was displayed when the boot failed?

It would be nice if I could reproduce that and fix it. Of course upgrading a pupsave is not perfect but has worked OK here so far. Will keep testing and trying to improve...
-TazOC

Posted: **Wed 22 Sep 2010, 02:56**

tazoc wrote:Hi Jim,
Thanks for testing 5.00 F. After the boot failed did you happen to run click-to-verify, or boot from the new CD? Do you recall if a specific error was displayed when the boot failed? -TazOC

It went to a prompt after trying to execute xwin, xorgwizard would run, and I selected the nv driver, however it would just return to a prompt, same thing with choose option, so I gave up and rebooted. Apparently, the problem is with the driver that was in the 5.00 D save file. I have no problem creating a new save file since my important info is at mnt/home, nothing critical in the save file.

I always manually install to a new subdirectory and boot using grub, never bother with burning and booting from a CD. Since, everything appears to be working with a new save file, I have no reason to suspect a bad download, so I haven't run click-to-verify.

Cheers,
Jim

Posted: **Wed 22 Sep 2010, 06:25**

What version of LHP or Puppy are you in and is that the 5.00 F ISO? By access base .iso, do you mean mounting the ISO from within a file manager?

This is when trying to d/l 5.00F base .iso. I just get a screenful of code. The d/l is never there - it never triggers. It only happens with the .iso, the delta d/l starts up nicely.
I've had this before, quite often with very new uploads. I can usually choose another mirror and get the same d/l to start normally. Either something to do with server overload or local overload of my system?? There's probably a very simple explanation, but I don't know it.

Posted: **Wed 22 Sep 2010, 16:35**

Jim1911 wrote:
tazoc wrote:
I always manually install to a new subdirectory and boot using grub, never bother with burning and booting from a CD. Since, everything appears to be working with a new save file, I have no reason to suspect a bad download, so I haven't run click-to-verify.

Cheers,
Jim

Hi Jim. Can you point to a tutorial on this? Thanks
Rick

Posted: **Wed 22 Sep 2010, 16:40**

Hi TazOC,
Moving the .sfs files from the sub-dir to /mnt/home fixed KDE not loading.
I will continue testing 5F.
B.

Posted: **Wed 22 Sep 2010, 18:38**

@pudgypup
I don't burn a CD from the downloaded .iso file. To try a new Puppy or a new version of an existing Puppy, I create in /mnt/home a new folder for the Puppy I want to try.

I download the .iso in Puppy, or create a new .iso by downloading the xdelta3 and processing it against the previous .iso. Lighthouse makes this very simple and easy to do for for both .iso and .sfs files. Detailed instructions are on TazOC's web site.

I open the new .iso in a Puppy session by clicking on it, and I copy the vmlinuz, initrd.gz, and .sfs files to the new directory. All Lighthouse .iso's have a "check md5 sum" executable on the .iso. Click on it to verify the files on the .iso which is fast and easy.

I create an entry for the new Puppy in my menu.lst file by copying an existing entry and just changing the sub-dir name and title. Save and reboot, and the new puppy will be shown on the grub menu next time you boot.

On booting to the grub menu, press "e" to edit the grub entry and then "e" to edit the kernel line. For first time boot you specify pfix=ram and whatever you need for testing (like debug or acpi=off). Press enter to save the changes and press "b" to boot using your temporary changes.

On exit from first boot create the pup-save file in the new sub directory (It defaults to this) and your new Puppy will be self-contained.

I can post or PM you detailed instructions about how I setup and configure my computers hard disks using gparted and install-grub if you need them.
B.

Posted: **Wed 22 Sep 2010, 20:39**

Yes, I follow the same procedure.
I also copy over the click-to-verify-lhp file so I can check them later if there is a problem.

Also, if you copy a recent spupsave.2fs file to that new directory and tell Lighthouse where it is (eg, psubdir=lhp500), Lighthouse will update it as well on the first boot and you will have everything loaded and configured as in that recent version. Very convenient.

Here is what my menu.lst entry for Lighthouse looks like:
# Linux bootable partition config begins
title Lighthouse Pup 5.0F frugal (on /dev/sda8/lhp500)
rootnoverify (hd0,7)
kernel /lhp500/vmlinuz pmedia=atahd pdev1=sda8 psubdir=lhp500 xforcevesa nomodeset
initrd /lhp500/initrd.gz
# Linux bootable partition config ends

Posted: **Thu 23 Sep 2010, 22:04**

I'm trying this nice nice puplet,

I tried the 3D-demo and got a sloow 16FPS

After isntalling ATI Catalyst pet I notice a valuable graphic speed-up, for example when passing cursor above WBar, but the 3D-Demo does not start anymore!

Calling /usr/libexec/xscreensaver/3ddemo simply execute with no sign of life.

Any advice?

P.S.: too, too many icons, for example / folders... how do I reset them?

Posted: **Fri 24 Sep 2010, 00:31**

Hi neurino,
Paste this into a terminal:

Code: Select all

/usr/libexec/xscreensaver/antinspect -fps

To reset the icons in ROX-Filer, rename /root/.config/rox.sourceforge.net/ROX-Filer/globicons and restart X. Still too many? Rename /root/Choices/ROX-Filer/globicons then restart X. Icon themes can be changed in ROX | Options | Types | Icon Theme.

In the / (top level) folder of ROX you can delete the symlinks (small arrow in the icon) Help and wine-drive_c and maybe some of the others if you don't use them. Just don't delete the ones without an arrow on the icon or something will break.
-TazOC

Posted: **Fri 24 Sep 2010, 01:22**

Ran tkhearts from a terminal and got this:

bash-4.1# tkhearts-0.80.sh
Application initialization failed: this isn't a Tk applicationunknown color name "BACKGROUND"
Error in startup script: this isn't a Tk applicationunknown color name "BACKGROUND"
(database entry for "-background" in widget ".")
invoked from within
"load /usr/lib/tk8.5/../libtk8.5.so Tk"
("package ifneeded Tk 8.5" script)
invoked from within
"package require Tk"
(file "/usr/local/bin/tkhearts-0.80.sh" line 22)
<root> ~
bash-4.1#

B.

(old)Puppy Linux Discussion Forum

Lighthouse Pup 5.00 G 185M

Synaptics touchpad palm detect

Lighthouse Pup 5.00 F (Build 500) released

5F

Re: 5F

non fatal error on shutdown

Re: Seen this before?

Please move your SFS add-ons back to /mnt/home/

Install Lighthouse without burning a CD

tkhearts bug