Puppy Linux Discussion Forum

Béèm · Posted: Mon 05 Jul 2010, 16:44 Post_subject:

I just saw the announcement of 500C (missed the one for B)
Is it worthwhile to go from A to C, or is the D very close for announcement and wait for it?

Also is it safe to migrate the save file from A to C(D) or is it better to start afresh?

tazoc · Posted: Mon 05 Jul 2010, 17:26 Post_subject:

@Jim1911,
Thanks for the link, yes 2.7 works from there and I'll upload an updated BibleTime SFS soon.

@Béèm,
I don't anticipate 5.00D for at least a couple of weeks. Save a copy of your 5A pupsave just in case, but it should be fine to upgrade to C. I usually start with a fresh pupsave for baseline testing, and most of my personal files are manually symlinked to, or copied over from a separate partition. If you have any problems with the qps process manager in Mariner or KDE 4, try this qps bugfix pet.
-TazOC

Béèm · Posted: Mon 05 Jul 2010, 17:58 Post_subject:

Thank you tazoc.
I just wanted to avoid to be in a lucid environment where all of a sudden every other day a new version is coming out.
Will go to C and when migrating I always make a copy of the old save file as a precaution.

Ray · Posted: Wed 07 Jul 2010, 00:41 Post_subject: Mariner 5.0C

I have downloaded the latest Lighthouse Mariner iso, checksums match ok, burnt the iso to cd and tried to run on one of my spare computers, amd 64 Athlon 5600, 2gb ram. The boot starts and then the following message:

Loading isolinux Disk Error 80, ax=42E0, Drive 9F

Any suggestions as to how to make this work.

Ray

tazoc · Posted: Wed 07 Jul 2010, 02:33 Post_subject:

Ray · Posted: Wed 07 Jul 2010, 03:27 Post_subject:

tazoc · Posted: Wed 07 Jul 2010, 12:47 Post_subject:

Hi Ray,
Make sure that your burning software closes the session or burns as DAO (disc at once). CD-RW might not fit as the Mariner ISO is 684M and some drives are fussy about CD-RW and certain kinds of DVD/DVD-RW. For maximum compatibility as I noted earlier use an 80 min Data CD-R, ideally burned on the same drive you want to boot from.

I haven't used VMWare, but with VirtualBox I also must choose the vesa driver to get X running in Lighthouse. Once LHP is up and running in a virtual machine, it is necessary to unmount the CD-ROM in Lighthouse with Pmount Drives or other method, before using VirtualBox or VMWare to mount a different ISO. Be sure that copy2ram is in effect when booting in a VM (if your VM has at least 512 MB allotted it should do so by default. Don't use safe or nocopy at the boot menu when booting in a VM as the CD-Drive will not be able to unmount.
TazOC

Capt-CDD · Posted: Wed 07 Jul 2010, 16:20 Post_subject: Slackware

Tazoc,
First and foremost I want to thank you for your great work. I have been using LH since the 5.0A release and it is my favorite pup by far!

I noticed in the 5.0c release that we were supposed to be able to get slackware straight from the repositories with dependencies through PPM. That would have solved a big problem for me as I needed; blueman, a bluetooth manger for my head set setup for SIP. When I went in to PPM it came up with the regular puppy selections. I tried to add Slackware 1.13 but it did download the database files, but it did not give me a slackware selection. I tried to follow Barry's guide to editing DISTRO_PET_REPOS, DISTRO_COMPAT_REPOS, and DISTRO_SPECS but could not understand exactly what I was to edit and with what URLs and/or info.

So my questions are two fold. 1. should the Slackware have come up automagically in 5.0C. I did upgrade from 5.0B so did not know if I needed to start fresh or what.

2. If I do still have to edit the files above could someone explain it I in a little simpler terms. I have been a puppy user for years and hence have followed Barry's directions many times in the past but this time I just don't comprehend what I'm supposed to do.

Oh and I did install Blueman from GSLAP but it failed on load I suspect due to depenedencies. All I got was flie/directory does not exist.

If I can't resolve this, any recommendations for another bluetooth audio manager and good softphone application would also be appreciated..

Thanks again for a top shelf Distro! Lighthouse 5.0C is super!!!

Béèm · Posted: Wed 07 Jul 2010, 16:30 Post_subject: first install 500C

Finally could take the time to frugally install 500C.
First nice surprise: no need anymore for nocopy. LH loads fully in memory now (was not the case with 500A)
Second surprise: desktop drive icons retain the size information even with the Belgian locale configures from the beginning.

So this is a good start to continue testing.

Béèm · Posted: Wed 07 Jul 2010, 18:12 Post_subject:

When hovering with the mouse over the xload in the system tray, like in 500A, the cpu freq is 0,000 GHz.
I know I got the reply that sometimes icewm doesn't display the cpu freq there, but hoped the issue was solved.
I know conky displays correctly, but as I have a small screen, conky is always covered.
Still hoping for improvement.

CLAM01 · Joined: 22 May 2010 Posts: 74

Béèm,
Frequency monitoring has to be set up manually: Right-click the desktop for the menu, go to utility and all the way to the top in the submenu. Five down is CPU Frequency Scaling Tool. Left-click to open and sset it up, your frequency will appear in the box when you mouse-over.

Béèm · Posted: Thu 08 Jul 2010, 15:01 Post_subject: Sub_title: Frequency Scaling

tazoc · Posted: Thu 08 Jul 2010, 22:02 Post_subject: Re: Slackware

Béèm

I did choose the be-latin1 keyboard. I also did choose the be one for xkbd.

In native mode (geany etc...) I have no problems with the accented characters and dead key support.

But in wine, I have no accented characters and ê displays as ^e and ô as ^o.

In lucid I have no problems in wine, so I have the impression that LightHouse is to be incriminated.

Any idea if a correction is possible?