Lighthouse 3.01g Gold ISO 353M, Mariner SFS 150M

[tazoc]

Copied from: http://www.murga-linux.com/puppy/viewtopic.php?t=35059

Hi.
My first impression is of an extremely nice iso. Well done. Unfortunately after running Lighhouse 3.01c in ram, on reboot the Maus & dark Desktop freezes. To shut down and reboot I have to pull the plug. Any ideas why?

UJ

Thank you for trying LighthousePup. I have not seen this behavior before. Maybe some specifics will allow us to reproduce it. Has this happened with official Puppy or any other system you've run? At shutdown did you save your session/settings to a file (default) or to the drive? How much RAM does your machine have? At what point in shutdown or startup did the freeze occur, e.g. before or after the "Starting Lighthouse", KDE splash, or what was on the screen just prior to?
-TazOC

[Bligh]

Lighthouse 3x is running fine on 2 laptops and 1 desktop. However, my daily ride, always on 24/7 since 04 has no sound. It came free with win 98 and 273 instances of spyware and malware. It has run Linspire for 4 yrs almost continuously with some sound, there seems to be a conflict between the mozilla browsers and the sys sound. Puppy 4.1 also has no sound. I replaced the original sound/modem card with a soundblaster card. ca0106. I tried the sound setup wizzard, still no sound. Pclinuxos does have sound on this box, also with kde. I boot from the cd and have a 500mb save file. This is a p3 500mhz 384 mb. Any suggestions?
Cheers

[Barburo]

@Bligh
Take a look here - The "isapnp" is no longer in /etc/modprobe.conf but you could try a different slot for your sound-card.
http://www.murga-linux.com/puppy/viewtopic.php?t=20788
Also try browsing through
Forum index » Advanced Topics » Hardware » Audio
- there maybe more hints there.
B.

[Bligh]

Thanks, after much searching, I found it in Advanced topics>hardware>audio. It was something like this, make sure the bloody volume is turned up in the mixer. duh! who would have thought?
Cheers

[tazoc]

@Bligh,
So it's working now? Glad you and Barburo solved it--I was at a loss and planned to search the forums--hoping I would find something useful. Good job!

@Barburo,
Thank you for your suggestions. Now I know where to look next time something similar comes up.

Regards,
TazOC

[Bligh]

I was somewhat red faced when I made that post. That was 3.01a4, haven't tried 3.01c on that box yet. xsane and juk are certainly inviting though. Could puppy use a swap file, would there be any advantage/disadvantage?
Cheers

[tazoc]

Bligh,
It's OK, next time we'll know to check the mixer. Not sure why it wasn't turned up by Puppy.

I think you mean a 'linux-swap' partition, which does have a number of advantages, mostly based on improved memory management. Will boot Lighthouse and can copy main file to RAM with less total RAM. Better able to handle large multiple apps / multitasking. Linux-swap works like the Windoze swap file, except that it exists on a separate partition, and is probably more efficient. Even a small one is a big help.

It is easy to create one with Gparted Partition Manager in KDE's Utilities Menu. Boot in LiveCD mode ('lhp pfix=ram') before running Gparted. Good idea to back up any important files/data to CD/other external media just in case something goes wrong. Then you can resize an existing partition to make room for a swap partition. The only situation that I know of where you might run into difficulty would be on a box that has Vista installed. Might prevent Vista from booting. A Vista box probably has loads of RAM so you could get by without a linux-swap anyway.

512M-768M swap should be good, a little more or less won't hurt. The swap partition can be anywhere on a hard drive, though at the beginning is probably ideal.
Hope that helps,
TazOC

[Bligh]

I believe some linux distro's use a swap file rather than a swap partition. I was just wondering if puppy could utilize a swap file, and if there would be any advantage other than avoiding the issues presented. I suppose it would require a larger pup save file if nothing else. I am in over my head here, but Linspire used a swap file.
Cheers

[puppyluvr]

Hello tazoc,

First, as I have said before, Lighthouse 215 is the cream of the crop in Puppy. The attention to detail, choice of packages, eye candy, and tons of extra scripts make it the most useful Puppy ever IMHO..I based the first Buddapup on it, and use it a lot still...
I have not really used the 3.01 version much yet, as I dont like KDE, but I will take a closer look when I get more time..

I dont have a question, or a complaint, I just wanted to say how much I liked your work on 215 and that Ive found it inspiring..

@The Inland Empire...
I grew up in Spokane...

[Barburo]

Just a quick note.
MU suggests a minimum swap partition size of about 500Mb or so. I agree with TazOC that Puppy works better with a small Linux swap partition.
If you have Vista use the Vista repartition tool to create a swap partition first. You can then fire up puppy (From CD or frugal install) and use gparted to reformat the partition as Linux swap. When Puppy boots it automatically recognizes Linux swap.
If you use gparted from within Puppy to create the swap partition it confuses the heck out of Vista - it likes to think it's in control of everything! Vista might even go away and sulk for an extended period the next time you boot it.

I run a multi-boot notebook with a 120Gb hard drive with Vista in one partition (55Gb), XP in another (35Gb), a 20Gb ext3 partition that I use for frugal installs of various flavours of Puppy and some local storage, and a 630 Mb Linux swap partition.

One final note - Vista insists on having control over the master boot record so Grub does not co-exist very well with Vista.
I use the Vista boot manager to provide the initial menu of which OS to boot on initial start-up. In my set-up the Linux option is the default, and I have that option start Grub4Dos that is maintained through EasyBSD from NeoSmart Technologies (installed on Vista or XP). It functions like regular Grub and EasyBSD can also get back your Vista partition if like for me your XP install changed the MBR and made Vista vanish. The menu.lst file is on the Vista partition in a directory called NST and you can maintain your Grub entries in menu.lst from Puppy without ever needing to boot Vista by simply mounting the Vista partition. Other parts of this forum have all the details about how to set this up.

Of course you can also use space on either Vista or XP ntfs partitions to store your Pup_save files which I have also done in the past quite successfully if you don't want to format a separate Linux ext3 partition. Vista goes away and sulks if you change any files on its partition but it eventually fires up OK. I also used to run Ubuntu in a separate partition, but I've pretty much abandoned it in favour of Lighthouse Pup (ever since 2.15)
B.

[Bligh]

For me, the beauty of Puppy is not having to install it to have a fully functional linux os. AFAIK Puppy is the only one developing the potential of the live cd. I am still at the (I wonder what this does?)stage with Lighthouse and Puppy. I use hdd racks and laptops with easily swapable hdd's. I don't have any me or vista hdd"s. I run Puppy with the Linspire 5x hdd's installed hence no swap partition.although one could easily be created. I also have one laptop with xp installed, it has pup save files for Lighthouse 215, Pup 3, 4 and 4.1. It has only 256 mb so I will probably run lh2, lhc, or pup 4.1x on it.
I only have experience with win and kde desktops so LH is great for learning other desktops. Puppy is Great and Lighthouse is Outstanding
Nearly all of my hdd's have an os partition and a data partition, usually fat32. On one drive I saved the pup files to the data partition, pup does not seem to be able to access the os partition, which may be more secure.
Cheers

[playdayz]

This is a very pretty desktop and even better, kde runs with good responsiveness. However, that is only on first boot, because when I reboot I get the message "Could not start kdeinit - Check your installation." This happens with both xorg and xvesa. When shutting down the first time, I create a 1GB pup-save. I have 256MB ram and a 512MB swap file. When it fails to start kdeinit I can then choose to switch to jwm and it starts and runs fine.

[Barburo]

Hi TazOC,
Here are a couple of screen shots of my set-up - iceWM and KDE.
Everything I use seems to be working (including scanning)
Thanks for all your work on this,
B.

[tazoc]

This is a very pretty desktop and even better, kde runs with good responsiveness. However, that is only on first boot, because when I reboot I get the message "Could not start kdeinit - Check your installation." ...

Thank you, hmm not sure what to suggest... glad you can still use JWM and 'xwin starticewm' should work also. Let me think on that; should be able to fix it by deleting some cached KDE files I think. You might just reboot with

Code: Select all

puppy pfix=ram,copy

rename your pup_save.2fs to 'pup_save.2fs.save', then shutdown creating a new one, say 256M or 512M to see if that helps. You can always re-size it later with the 'Resize personal storage file' in System or Utility menu.

@Bligh & Barburo,
Thank you for your encouraging comments and insight. Nice screenshots Barburo! Is that Audacious? skinned or default? I want it! Glad your scanner is working... I wasn't able to get Xsane to detect my Agfa USB Snapscan--no biggie I don't use it much anyway.

[tazoc]

Lighthouse Mariner SFS 132M for Lighthouse 3.01c
Includes Amarok, Gslapt, Opera, Xscreensavers & 75 games

Details 1st post of this thread and http://lhpup.org/download.htm#SFS



Bugs: Amarok sometimes pops up a little message "The script 'Default' exited with error code 127" at song change. [Edit 11/14] Fix: Use Gslapt to install ruby-1.8.7_p72-i486-1. Next update of Mariner will include ruby. Instead of closing it I just minimize it and then it doesn't come back. If anyone knows how to fix it, let me know. Still Amarok is a great app with an amazing feature set and attention to detail--the audio is rock solid.

Its been quite an experience putting this together. Hope you enjoy it as much as I do.
-TazOC

[Barburo]

Yes it's audacious with a winamp skin "Nucleo_NLog_v102_.wsz" my son found somewhere. I tried uploading it but the forum won't allow .wsz extension so I renamed it to .zip.
To make scanning work I found I needed to download front-ends and back-ends for Sane.
I used these pets:
sane_backends 1.0.17
sane_frontends 1.0.14

[Barburo]

Hi TazOC,
I just downloaded the new SFS pack and I admire your installation tools. I'm looking through all of the menus and both KDE and IceWM have things in the right place. Thanks for Amarok - I also get the pop-up error you mentioned. More later if I find anything.

I have a bug with Glipper in IceWM (from before the new Mariner SFS): The system tray looses the "Glipper" icon each reboot.
I have to go into the GUI (desktop .. Glipper), click "disable glipper"
exit and repeat, but click "enable glipper" ... and the icon is in the system tray.
Next reboot it has disappeared.
B.

[tazoc]

Hi Barburo,
Thank you for the cool Winamp skin and sane info. I will try them. Glad Mariner is working for you so far.

A Glipper bug! Good work. Seems okay in JWM so here's what I did.

Open /root/.icewm/startup in a text editor.

Copy and paste the following two lines into the bottom (end) of the startup script:

Code: Select all

pidof glipper && killall glipper
[ -e ~/.glipper_on ] && glipper &

Save the file, log off and restart X. I'll try to get it into the next update or service pack for LHP3.01c.
-TazOC

[Barburo]

I tried your fix for Glipper - doesn't make any difference on my machine (Notebook) - still the same problem.

I have an outstanding problem with volume control in iceWM that has persisted through all versions of LHPup3.01.
In KDE the volume application that sits in the system tray area controls many different things and it works just fine.
In iceWM's Zmixer there are sliders for Master, PCM, CD, line and mic. For me all of these sliders are frozen at minimum except PCM which does allow me to vary the volume. However if I've set the "Front" slider in KDE to say about 50% then that is the maximum that I can increase PCM to in iceWM. If I go into KDE, set the slider to 100% then return to IceWM I have full volume control through the PCM slider.
So there's two things going on here. KDE seems to control the maximum volume for IceWM and I don't know why the other sliders in Zmixer are locked out.
B.

[tazoc]

Barburo,
Can you check gPS to see if Glipper is running when it should be? Also, open Rox and see if '.glipper_on' exists in /root. If that file is there, then Glipper should be running in IceWM. And paste the bottom half of your IceWM startup file up here so I can read it, please. We need to look at the lines that have icewmtray and glipper.

Try 'kmix' from Multimedia menu or console, instead of zmixer. If it works better we can figure out how to start it in the tray in IceWM.
-TazOC