LighthousePup 2.15 FINAL (Formerly 215 Beta5) ISO 182M

[puppyluvr]

Solved. :


Hello there ,
First off, love the Lighthouse Puppy. have been using it since December.
Definitly the most complete and usefull Puppy I`ve found. Will try 3.01 version as soon as i have time. Heres my question: I have a Lighthouse based Puppy called BuddaPup using Enlightenment. Works great!!
Recieved a few requests for an iso..(Caneri gratiously agreed to host it)
Have used the iso myself and it works fine..However, one of the first downloaders sent me this message:




" Hello puppyluvr

Nice job you have done with this derivative.
But i think you forgot to include the zdrv_215.sfs in the ISO,
i dont know if that was intentional or just oversight.
I copied the file from Lighthouse215SeaM_Beta5.iso,
and that enabled me to get online."

I used the dougal remaster and mine boots and goes online (wifi) just fine
but i dont know where to look for zdrv215.sfs or even know if its supposed to be there..(i think it contains drivers?) I`ll happily remaster again to include it but i dont know where its supposed to be.(NOOB)
is this file specific to Lighthouse??, and why wouldnt the remaster include it by default? Dont want to breed lame puppies!
Any comments would be appreciated...THXSol

[Colonel Panic]

Is anyone else having trouble booting Lighthouse Puppy? I've got 256 MB of RAM and I'm being told I'm out of memory even while it's still booting
(and then I get the error message I take my user name from.....)

Is it possible to use swap to boot LHPup? I boot from a hard drive not a CD-ROM.

Here's my lilo.conf file;

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
append="splash=silent "
boot = /dev/hda
bitmap=/boot/splash.bmp
bmp-table=234p,348p,1,4
bmp-colors=220,0,,255,220,
bmp-timer=539p,396p,220,0,
prompt
timeout = 34500
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# Normal VGA console
vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda2
label = Zenwalk
initrd = /boot/initrd.splash
read-only
# Linux bootable partition config ends
image = /boot/puppy/vmlinuz
root = /dev/ram0
label = Puppy
initrd = /boot/puppy/initrd.gz
read-only
# Linux bootable partition config begins
image = /boot/lighthouse/vmlinuz
root = /dev/ram0
label = Lighthouse
initrd = /boot/lighthouse/initrd.gz
read-only
# Linux bootable partition config ends

Thanks in advance,

Colonel Panic .

[Barburo]

@Colonel Panic
I hope you're using a frugal install. If you're not I suggest you do - it's by far the safest, easiest and most secure way to use Puppy. You can also run multiple versions and other operating systems too through Grub.
My laptop set-up runs LHPup301a5, Dingo4, MiniMuppy8.13F, Ubuntu, XP and Vista. My more modest desktop runs LHPup215, Muppy813f, XP and Dingo.
I have been happily using LHPup215 for over a year now - with modest RAM (448Mb) and no problems.

Anytime I get into difficulties I do this:

Boot from the .iso CD for LH Pup 215 using pfix=ram parameter which allows you to boot up with no .2fs save file, but you have to go through keyboard selection and xorgwizard again. You should have a working system that will allow you to back-up your .2fs file, ( copy it to say xxx.2fs.bak).
Reboot from the .iso but allow the boot to pick up your save file from before (the one you backed up) and see if you get the same problem.
If yes it's your save file. Otherwise you should be in business again. I keep the .pups and pets that I usually apply in a folder so it's easy to re-create my system and modifications if I need to.
B.

[tazoc]

Colonel Panic,
I think LighthousePup 2.15 (as well as Puppy 2.15CE) didn't yet [Edit: fully] support booting from a [Edit: directory] sub-folder. (LHP 3.01a4 does, [Edit: if one level deep].) To boot LHP 2.15 off your hard drive, copy from the CD-ROM or mounted ISO vmlinuz, initrd.gz, zdrv_215.sfs and pup_215.sfs into / [Edit: system root] of your home drive and change the LILO/GRUB entries accordingly.
Hope that helps,
TazOC

[Colonel Panic]

Thanks for the info, but I don't have the facility to boot from the CD because the community centre from whioch I downloaded LHPup didn't have the facility to burn a bootable CD-ROM, so I had to save the ISO as it is onto the CD and then copy it into a folder on my hard drive, from which I extracted the initrd and vmlinuz files..

[vg1]

Tazoc,

assume you mean to say that lhp301 supports booting from a folder [ie one level deep].
I don't think lhp301 [or any p3/p4 derivative] will work from a subfolder, ie all files in a folder two levels deep. Kernel & initrd are found if two levels deep, but p_xxx.sfs & save_file are not. It works if they are on the root, with the obvious limitation. I made several tests with various p3/p4 derivatives, they all behave the same. They will only boot from a folder one level deep.
If anyone has found a way to make them boot from a subfolder please speak up.

Colonel Panic,

lhp215 can be made to boot from a folder or subfolder with some tweaking. See my posts elsewhere on booting teenpup that way. However some have found it too difficult, so not sure this will help you.

vg

[tazoc]

Tazoc,

assume you mean to say that lhp301 supports booting from a folder [ie one level deep].
...
vg

Yes, I've tested LHP3.01 and Puppy3.01 booting (with GRUB installed to MBR) from a directory one level deep, not two levels deep--so I edited my post above accordingly. Thanks for the info and clarification.
TazOC

[Colonel Panic]

Thanks once again.Unfortunately it still won't boot even with the folder only one level deep. It may be that my RAM is the limiting factor, but I'm going to see if I can get it burnt properly to a CD.

I'm posting from Puppy 2.15CE, which takes about 115 MB for its iso file, so it may be that you need at least as much RAM as you've got hard drive space for the iso file.

[tazoc]

Thanks once again.Unfortunately it still won't boot even with the folder only one level deep.

I'm confused... Which is "it"? If it's LHP2.15, then one level deep usually won't work, put all 4 core files at / (zero levels deep.) For LHP3.01 the 4 files can be in a directory one level deep.

I haven't used LILO, only GRUB, but the section beginning with 'image =' looks too short, I think you may need more parms there.

Can someone familiar with LILO help? Here is my GRUB entry for LHP2.15:

Code: Select all

title         LighthousePup 215 (frugal on hda8)
rootnoverify    (hd0,7)
kernel         (hd0,7)/vmlinuz root=/dev/ram0 PMEDIA=idehd PDEV1=hda8 PHOME=hda8 loglevel=3 quiet vga=normal
initrd         (hd0,7)/initrd.gz

and for LHP3.01:

Code: Select all

title         LighthousePup 3.01 (frugal on hda8)
rootnoverify    (hd0,7)
kernel         (hd0,7)/lhp301/vmlinuz root=/dev/ram0 pmedia=idehd pdev1=hda8 phome=hda8 psubdir=lhp301 loglevel=3 vga=normal
initrd         (hd0,7)/pup301/initrd.gz

The core file pup_215.sfs is approximately 162 MB so 256 MB RAM should be enough, though a Linux-swap partition on a local, preferably fast disk drive may be useful. I'm glad you plan to burn a bootable CD, that's the best way to start. Type in "puppy pfix=ram" at the boot screen to run in ram. Then you can use pmount to mount or unmount any drive and use Start | Utilities | gParted, if you need to create a Linux-swap partition, create or re-size your existing partitions.
TazOC

[Colonel Panic]

Thanks for replying.

I'm confused... Which is "it"?

LH 3.01.

If it's LHP2.15, then one level deep usually won't work, put all 4 core files at / (zero levels deep.) For LHP3.01 the 4 files can be in a directory one level deep.

I did, but so far it still hasn't loaded.

I haven't used LILO, only GRUB, but the section beginning with 'image =' looks too short, I think you may need more parms there.

Probably but I might try GRUB, I've got a copy of it somewhere.

Can someone familiar with LILO help? Here is my GRUB entry for LHP2.15:

Code: Select all

title         LighthousePup 215 (frugal on hda8)
rootnoverify    (hd0,7)
kernel         (hd0,7)/vmlinuz root=/dev/ram0 PMEDIA=idehd PDEV1=hda8 PHOME=hda8 loglevel=3 quiet vga=normal
initrd         (hd0,7)/initrd.gz

and for LHP3.01:

Code: Select all

title         LighthousePup 3.01 (frugal on hda8)
rootnoverify    (hd0,7)
kernel         (hd0,7)/lhp301/vmlinuz root=/dev/ram0 pmedia=idehd pdev1=hda8 phome=hda8 psubdir=lhp301 loglevel=3 vga=normal
initrd         (hd0,7)/pup301/initrd.gz

The core file pup_215.sfs is approximately 162 MB so 256 MB RAM should be enough, though a Linux-swap partition on a local, preferably fast disk drive may be useful. I'm glad you plan to burn a bootable CD, that's the best way to start.

It probably is. Unfortunately I'm dependent on the local community centre for big downloads (because they have broadband and I don't), and their resources are limited, e.g. the machine with a rewriter also doubles as the only machine you can print from so it's much in demand. So even downloading the ISO can't be guaranteed although I did get the Lighthouse one.

At the moment I'm working on the basis that the ISO is all I'm going to be able to get.

Type in "puppy pfix=ram" at the boot screen to run in ram. Then you can use pmount to mount or unmount any drive and use Start | Utilities | gParted, if you need to create a Linux-swap partition, create or re-size your existing partitions.TazOC

Thanks, I'll have a look at GRUB anyway.

[tazoc]

Thanks for replying

I'm confused... Which is "it"?

LH 3.01.

If it's LHP2.15, then one level deep usually won't work, put all 4 core files at / (zero levels deep.) For LHP3.01 the 4 files can be in a directory one level deep.

I did, but so far it still hasn't loaded.

Ahh LHP3.01 (thread here.) Ok that is larger with KDE included and the core file pup_301a_lighthouse.sfs is 258 MB. So 256 MB RAM may not be enough, though an available Linux-swap partition might help.

At the moment I'm working on the basis that the ISO is all I'm going to be able to get.

Be sure to check the md5 on your ISO when downloading, or verify the core Lighthouse base files on the ISO, CD-ROM or Frugal Install drive by clicking on 'verify-md5-lhp'. More about md5s here: http://www.lhpup.org/download.htm
TazOC

[Colonel Panic]

Thanks for replying again.

My bad. I looked at the lhpup page and saw a RAM requirement of 256 MB, and assumed that would be the case whichever version of Lighthouse I downloaded.

Sorry if you feel I wasted your time. I'll see if I can get a copy of the
Lighthouse 2.15 ISO some time soon, it'd be good to get it working on this machine.

Thanks for all your help anyway,

Colonel Panic .

[steevieb]

Are you in the UK? I have a spare LHP 215 beta 4 (or 5) cd I could send you.
I also have a LHP 301 alpha cd if you would like that.

[Colonel Panic]

Yes I would, thanks. I'll pm you about it.

Colonel Panic.

[djringjr]

I love Lighthouse Puppy - but today it has given me a problem.

When in kde, the menus on the screen and the tool bar disappeared.

When I rebooted all I have is the K of the KDE menu and no entries. I still have the desktop 1 and 2 and by using "run command" I was able to get into ROX and from there into the command line and run programs.

Can someone tell me how to rebuild or restore the menus?

Thanks

David

[tazoc]

I love Lighthouse Puppy - but today it has given me a problem.

When in kde, the menus on the screen and the tool bar disappeared.

David

Are you using Lighthouse 3.01? (This is the 2.15 thread.)
If you have no KDE Panel at all, type on command line or run box:

Code: Select all

kicker &

or log out and choose 'Restart KDE'. If you have the Panel and KMenu but no entries in it, copy and paste into a terminal:

Code: Select all

fixmenus      
cd /root/.config/menus
cp applications-kmenuedit.menu applications-kmenuedit.menu.`date +"%Y-%m-%d_%T"` 
rm -f applications-kmenuedit.menu # deleting menu file will force KDE to rebuild KMenus

then log out and restart KDE.
Hope that helps,
TazOC

[Colonel Panic]

Hi. I'm enjoying using Lighthouse 2.15 but I've noticed that both conky and Muppy Icedock autoload when I start up X Windows. I don't need both; how do I turn either of them off?

One small fault I've noticed too (though it's easily corrected); the menu entry for Midnight Commander doesn't mention a terminal for MC to load up in so the link goes nowhere. Something like "xterm -e /usr/local/bin/mc" will fix it.

Thanks for a great job of work anyway,

Colonel Panic .

[tazoc]

Hi. I'm enjoying using Lighthouse 2.15 but I've noticed that both conky and Muppy Icedock autoload when I start up X Windows. I don't need both; how do I turn either of them off?

On the taskbar click QuickLaunch (the rocket icon) | Advanced Settings | Open Autostart Folder.

Middle click on the new DisabledItems folder to open it in a new window. Now you can move items with drag and drop between folders to enable and disable autorun action as desired. You'll see that numlockx-on and xmms-p are disabled by default. Right-click | Open as Text to see what an item is; or just click to execute.
TazOC

[Colonel Panic]

Thanks.

[Colonel Panic]

Juist one more quick question (probably applicable to other versions of Puppy as well); how do you change the colour of the icon font on the desktop. for example to harmonise better with the wallpaper?

Thanks in advance,

Colonel Panic.