Lighthouse Pup 4.4.2 Final SMP 194M

[Colonel Panic]

Just one thing; provided you don't need anything more than a frugal install, what does work is to start up and run a lightweight Puppy like Todd's Surfpup and then load the Lighthouse sfs pup_301a_lighthouse.sfs from the Boot Manager having first renamed it to something like light.sfs.

I don't know why the Lighthouse sfs (and the Fire Hydrant Inferno one too) loads this way when it won't load in the normal fashion as a Lighthouse sfs, but it seems to work well provided the version numbers are the same or very similar (3.00 and 3.01 etc.).

[tazoc]

LighthousePup 4.1.2 RC1 released, Mariner and Voyager also updated to 4c

* On first run or boot option 'pfix=ram', prompts to reboot & create pup_save before running Xorgwizard. This should make saving your session very reliable.

* Additional options in Xorgwizard display configuration menu for ATI Catalyst drivers in Mariner SFS

More information here
-TazOC

[eztuxer]

Running fine on AAO netbook, just added madwifi .pet for wlan.
Installed on 2GB partition of 16 GB USB stick.
NO shutdown problem, normal behaviour.
Nice look and feel, good job !

[fritzk3]

Hi,

I am able to run Lighthouse from the CD... and then I can install it to a USB flash drive with no problem, but when I boot from the flash drive, almost immediately I get a kernel panic - I think it happens at the point that the boot sequence is trying to move the file system.

The flash drive is using the vfat file system. Any ideas what could be causing the kernel panic?

[tazoc]

Hmm, I don't know. I would copy 'verify-md5-lhp' from the CD to the flash drive, then click on it to check the md5sum of the core files on the flash drive. I can't think of any other reason why it wouldn't boot. Maybe try another flash drive, or test it with Puppy 4.1.2/4.2?
Hope that helps,
TazOC

[vanchutr]

@fritzk3
After I'd same errors like you met. I'd re-installed lighthouse on Kingston 4GB USB. It run well
This is my way:
1. Boot up in Windows
2. Run HPUSB Utility (download from Internet)
3. Format your USB with HPUtility in FAT 32 (no need to make a system disk)
4. Quit Windows
5. Start your Puppy
6. Insert your formatted USB
7. For ex: In Puppy you see your USB named sdb1
8. Don't mount your USB (If it is mounted - then unmount it)
9. Open console (rxvt or the same thing). Use this command: syslinux /dev/sdb1
10. Now open /sdb1, if you see an file named ldlinux - That means "you are success!"
11. Write config file "syslinux.cfg" and copy the three (or four) files vmlinuz, initrd.gz, pup_xxx.sfs to your USB. (or the fourth file zdrv_xxx if exists)
12. Now try to boot off with your USB

NB: May this help you? Answer please. Good luck

[vanchutr]

Is this a bug?
1. Open new document with geany
2. Open Console-LHP
3. Execute an command in Console-LHP
4. Copy message from Console-LHP
5. Click on Geany windows in order to paste the copied stuff to Geany
6. The console-LHP crash (auto close) - And I can't copied the needed message (only garbage info!)

[tazoc]

Vanchutr,
I haven't been able to reproduce the bug. Which window manager/desktop are you in, and what command(s) are you typing in rxvt-LHP? I tried following your steps in KDE and text and commands paste ok into Geany and both the terminal window and Geany remain open. I even tried with 2 terminals and 2 Geany windows. Can you reproduce the bug after booting with 'puppy pfix=ram'? I'll keep trying here.
-TazOC

[vanchutr]

Thank you Tazoc to reply soon

Code: Select all

Vanchutr,
I haven't been able to reproduce the bug. Which window manager/desktop are you in, and what command(s) are you typing in rxvt-LHP? I tried following your steps in KDE and text and commands paste ok into Geany and both the terminal window and Geany remain open. I even tried with 2 terminals and 2 Geany windows. Can you reproduce the bug after booting with 'puppy pfix=ram'? I'll keep trying here.
-TazOC 

I run Lighthouse RC1 in "frugall install" in mode pfix=ram via grub loader and use "default WM". I don't change anything in Lighthouse other than load Vietnames input method (UTF-8 encode).
The rxvt did'nt caused anything. Only Console-LHP will auto-close
How to produce any message from boot?. It runs too fast, I can't read anything. Please tell me.
Thank you again

[tazoc]

Thank you Tazoc to reply soon
How to produce any message from boot?. It runs too fast, I can't read anything. Please tell me.

I'm not sure which message you're looking for. Many in /var/log/messages and /var/log/Xorg.0.log. In LighthousePup, see also /var/log/PuppyLogs.
-TazOC

[chuck5620]

I don't know if anyone else has experienced this problem but when I shutdown from the kde desktop the screen loops 7 times between the 'end this session' and the 'power off' screens. This does not happen with icewm or jvm. Other than that this is a really nice puppy!

Chuck

[ralphv]

* Alsawizard prompts to exit to CL and run 'alsaconf'

I can't get sound to work. alsaconf gives some errors that can't be read because it goes too quickly to 'enjoy using alsa'

alsamixer says function snd_ctl_open failed for default: No such file or directory

in /var/log/messages I have only

May 7 19:06:13 (none) user.info kernel: ACPI: PCI interrupt for device 0000:00:1b.0 disabled
May 7 19:06:29 (none) user.info kernel: ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 16 (level, low) -> IRQ 16
May 7 19:06:29 (none) user.debug kernel: PCI: Setting latency timer of device 0000:00:1b.0 to 64
May 7 19:06:29 (none) user.info kernel: hda_codec: Unknown model for ALC883, trying auto-probe from BIOS...
May 7 19:06:45 (none) user.info kernel: apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
May 7 19:06:45 (none) user.notice kernel: apm: disabled on user request.
May 7 19:06:45 (none) daemon.notice modprobe: FATAL: Error inserting apm (/lib/modules/2.6.25.16/kernel/arch/x86/kernel/apm.ko): No such device

ALC883 is a realtek sound card

Any ideas? All my other puppy versions and other linuxes have sound working

Ralph

[tazoc]

@Chuck5620,
Thank you for your comments. I haven't seen the looping behavior you described. To workaround you can try Ctrl+Alt+BackSpace and type 'poweroff' or 'reboot'.

@Ralphv,
Open a console and type 'modprobe snd-hda-intel' <Enter>. Then log out to a command line and re-run 'alsaconf'. If that doesn't help I would post on the forum at Hardware / Audio section.
http://www.murga-linux.com/puppy/index.php?f=29

Hope that helps,
TazOC

[ralphv]

@Ralphv,
Open a console and type 'modprobe snd-hda-intel' <Enter>. Then log out to a command line and re-run 'alsaconf'. If that doesn't help I would post on the forum at Hardware / Audio section.
http://www.murga-linux.com/puppy/index.php?f=29

Hope that helps,
TazOC

Found out my problem. I was using a pup-save made in puppy 4.10, having been unable to make a new one in lighthouse. Sound works without a pup_save. I was able to make a pup save running lighthouse in virtualbox, so I used that, got funny video until I copied the xorg.conf out of the other pup save. Now it works fine.

Ralph

[Jim1911]

Thanks tazok, your RC1 is the best LH yet and the finest KDE pup available. It is fast, stable, has lots of good software, and is easily customized.

Xsane is the only problem that I've had. It cannot find my usb HP5280 all-in-one printer.

Thanks again,
Jim

[tazoc]

Hi Jim,
Thank you for your excellent feedback and praise! The first time I tried to detect my scanner Xsane couldn't find it either. But then I rebooted with the scanner on and then restarted Xsane and still couldn't find it. On a hunch I decided to unplug the USB cable and reconnect it. Then I restarted Xsane and wah-la, it works. So give that a try if you haven't already.

I also found a stray library that didn't belong at

Code: Select all

/usr/lib/libsane.so.1.0.18

If you have it, delete that file and try again. (libsane.so.1.0.19 is the correct one and there should be two symlinks pointing to it, libsane.so.1 and libsane.so).
-TazOC
PS: I'm working on a slimmer 181M RC2 incorporating the SMP kernel 2.6.28.5 from Newyearspup plus a new version of Gslapt and I hope to release it in the next week or two.

[Jim1911]

tazok,

Thank you for your reply. It's great that you are finishing up your RC2 while incorporating the SMP kernel 2.6.28.5 from Newyearspup plus a new version of Gslapt. Newyearspup and Lighthouse are my favorite distributions and I am usually booted up into one of them every day.

Looking forward to seeing the new Gslapt, is it version 5 or later? I have used the current version on each of your releases to install Bibletime, Thunderbird, and Pidgin. Installing Bibletime and Pidgin was a chore on RC1 this time because of missing dependencies that seemed to be due to slackware updates. However, they are working fine now.

Excited about your next release and I'll wait until then to tackle the problem with xsane.

Thanks again,
Jim

[tazoc]

Looking forward to seeing the new Gslapt, is it version 5 or later?

Yes, RC1 has Gslapt 0.4.0; RC2 will have 0.5.1a or newer as well as slapt-get 0.10.1a and a few Slackware 12.2 repos.
-TazOC

[Barburo]

Hi Taz,
Good news abut the SMP kernel 2.6.28.5 - I'll be watching for it and testing to see whether I can get connected with it.

I set up a new instance of Puppy 4.1.2 Retro and ran it and by accident it picked up your latest Mariner ...412.sfs file that was in my home directory. Of course there was no indication it had picked up any sfs files other than the stock "creating the layered file system" message.

I first checked my connectivity - I ran the same connect script that I use for 3.01g with no changes (same kernel I guess) and had no problem getting a wireless connection.

I decided to see if everything worked, and strangely enough most things did. Your mariner install script ran and I chose the default, and the menus all got updated. I was able to switch to icewm, and then to KDE (which I now use in your implementation almost exclusively in 3.01g) and the add-ons in mariner like Amarok, K3b all functioned OK (not conky though).

With this set-up I have the faster-booting 4.1.2 retro without your changes for the boot scripts or the ability to layer more than three .sfs files, but can live with that.

Can you think of any caveats that I should look out for if I continue to use this set-up over 3.01g?
B.

[tazoc]

Hi Barburo,
No caveats off the top of my head, in fact I've run Mariner 4c and Voyager 4c SFS with Puppy 4.1.2 standard kernel and tried to make them as compatible as possible.

However I haven't tested with Puppy 4.2 and the upcoming Mariner 4rc2 and later may not be compatible with Puppy 4.2 due to LHP's newer kernel, Xorg7.4 and different ATI and nVidia display drivers in Mariner 4rc2.

To fix conky, open ~/.conkyrc with a text editor and remove this code near line 100:

Code: Select all

${color #FFEB9B}${if_existing /etc/LHPVERSION}${color #99bbff}Lighthouse ${head /etc/LHPVERSION 1}${endif}

save the file and restart conky. If it still won't work you can either rename .conkyrc, or run 'conky' in a terminal and post the output here.
Take care,
TazOC