Lighthouse Pup 5.00 G 185M

[tasmod]

Hmm, first time I have really struggled to get an iso working.

Video problems with i810.

I had all the symptoms as described at each point. Finally got it working and it crashed out at the save routine. !!

Option of save created a new line in a cli showing the bash prompt and wouldn't do anything else.

Needless to say it didn't create the save file.

I'll continue on with my favourite LHP4 version for now.

[dwillis]

This looks like a truly great pup. But i have tried with both a fixed and multi-session CD burn and neither releases the CD so it can be unmounted to play movies. Tried a search for the problem, but no luck. Must be something simple i'm doing wrong. Ideas?

I'm looking forward to switching to this version. It's worth a donation, for sure. Thanks.

[Béèm]

Me too, I had the kernel panic issue, but when using pfix=nocopy I could load and use Lighthouse 5.00
But there is a showstopper for me
Altho I have selected the Belgian keyboard, and altho this is correctly in xorg.conf, the keyboard stays in qwerty.

Don't see how I can change thhis.

[Béèm]

At first start when I have to configure X and I take the 'default' xorgwizard, I get a black screen. I have to power off and when doing so I hear two barks before the laptop powers off.

My video controller is a ATI mobility Radeon 7500

On the next trial I used the ATI entry and selected the radeon driver.
This time I get to the desktop.
Not sure if I could/should use the radeonhd one.

Once in the desktop I haven't tried to go to the X prompt, type xorgwizard and see if I have the same issue.

[Béèm]

desktop drive icons show 0GB space
The desktop drive icons show correctly the file system, but don't give the size of the partition. They all show 0GB.

At bit annoying.

[Jim1911]

Xsane which has never worked before with Lighthouse is now working with my HP Photosmart C5280 all-in-one. All I needed to do was turn the printer on, install the correct driver with CUPS, and then install the hplip-3.9.12-scan.pet from here.

[tazoc]

Hello.
Im beginner user puppy linux.
Today I install lh-puppy in my old computer, and yet found bug.
I cant use polish kayboard - I dont have polish letter, for examle: ż,ć,ą,ę... etc.

If I click right Alt, and try make Any letter, comuter think that I use enter, and text go down.

I try change kayboard for english and again for polish, reboot computer, but It nothing to do.

PS: In normal puppy linux (5.01,5.00,4.3.1) polish kayboard work exellent!

Hi misiek998,
I haven't been able to reproduce the right Alt giving Enter behavior and the Polish letters are working for me from right Alt in Geany and Abiword, and here in Firefox: ąśðđŋħjĸźćńµþóę
However in Sakura console some of them don't work. Rxvt seems OK though.

It occurred to me that I've always selected the defaults at first boot and then changed layouts later so you might try booting with pfix=ram, choosing 'us' for all (just hit Enter), then once in X use the Input Wizard and Localization wizards to change back to pl. Certainly this workaround is inconvenient at best but until I find a better solution it may have to do.
-TazOC

Video problems with i810.

I had all the symptoms as described at each point. Finally got it working and it crashed out at the save routine. !!

Option of save created a new line in a cli showing the bash prompt and wouldn't do anything else.

Hi Rob,
Sorry about that, this Alpha release was a bit rocky huh? I believe I fixed the kernel panic bug for the next release by changing the timing (a sleep 1 in the right place) of the copy2ram progress loop in the initscript. But the save dialog at first shutdown bug continues to vex me. I wonder if there is a way to do it from X, instead of in the console dialog, post X? After all GParted runs in X. Maybe leaving X is necessary for committing all changes to the new save file or in certain modes?

You might try hitting the 'S' key if Tab/Enter don't respond. (If it drops you to CLI, just type reboot and it might go back to the Save dialog.)

I don't have an Intel graphics box to test on, but have you tried xforcevesa nosetmode at the boot menu, then in Xorgwizard, xorgwizard | choose | intel? Or is vesa the only one that works? I will have a go at compiling the proprietary drivers from Intel. I've already added nosetmode to the defaults in isolinux.cfg for the next release and I may put xforcevesa in also. A new F2 screen will display the various options to override as needed.
-TazOC

This looks like a truly great pup. But i have tried with both a fixed and multi-session CD burn and neither releases the CD so it can be unmounted to play movies. Tried a search for the problem, but no luck. Must be something simple i'm doing wrong. Ideas?

Hello and thank you. When booting from the LiveCD without copy2ram the CD cannot be unmounted as it is accessed for running programs. The next release should work better with copy2ram as long as there are about 311M free in RAM. Normally the main file is copied to local disk at shutdown so that the CD is not required for access to the main file, but with multi-session CD mode it may still be impossible to unmount the CD, as it has the save layer.
-TazOC

Altho I have selected the Belgian keyboard, and altho this is correctly in xorg.conf, the keyboard stays in qwerty.

Don't see how I can change thhis.

Hi Béèm,
I tried it myself and noticed that there was no 'be' keymap at first boot, just 'be-latin1' which didn't work. However if I choose 'us' and then ran Input-Wizard from X I could select 'be' which gives: &é"'(§è!çà azertyuiop qsdfghjklmù wxcvbn; with Right Alt: œþæßðđŋħjĸł

desktop drive icons show 0GB space
The desktop drive icons show correctly the file system, but don't give the size of the partition. They all show 0GB.

At bit annoying.

Yes, indeed you're right, if I don't choose the default 'us' at first boot. When I chose the defaults at first boot and then switched to 'be' once in X the partition sizes are OK. I don't know why that is the case.
-TazOC

[CLAM01]

Hi TazOC, I'm not using 5 yet, but I use non-standard keyboards, international us (with deadkeys) and a couple of nationality specific. I'm able to set them up, starting from us and setting in X, but they don't stay through shutdown. Each reboot goes back to vanilla us. I work around by using the wbar looknfeel >mouse keyboard >advanced Xorg at the start of each session. I open the layouts and variants dialogs, see my settings there and so hit the cancel to leave them unchanged, then click the apply button to reset them for the session. The settings then work everywhere, including in open office, but go away at shutdown. I have found that the setting puts a script in /tmp. It apparently doesn't put the script in a directory that is saved at shutdown, and the X start scripts don't reset the one in /tmp. I don't know which would be the correct cure, or if a link from somewhere to somewhere is needed. Meanwhile the workaround makes non-us and international keyboards work in Lighthouse.
P.S. The background lighthouse labeled "a lighthouse in Oregon" is the Yaquina Head lighthouse.

[tazoc]

Hi CLAM01,
Thank you for the feedback. The Advanced Xorg keyboard button only updates /etc/X11/xorg.conf, whereas the first option, Choose keyboard layout updates keymap, codepage and fontmap in /etc. I tried several settings in Advanced Xorg and could not find a new script in /tmp.

I'm wondering if maybe you are using one of the proprietary drivers for Xorg (ATI Catalyst or nVidia) as I think they use the profile-specific /etc/X11/xorg.conf<ChipVendor><MonitorVendor> and it looks like the Advanced Xorg applet only updates the standard /etc/X11/xorg.conf. But if that was the case, I would think that restarting X would lose your custom settings, so maybe I'm on the wrong track.

In any case I will see if it's possible to update /etc/keymap from /etc/X11/xorg.conf so at least that part would be retained after reboot. However if you can verify that your settings are retained when restarting X and attach the script you found in /tmp that might help me figure this out. Otherwise I will give this some more thought and hopefully find a solution. Also please give me the specific keyboard model, layout and variant you've selected prior to rebooting so I can repeat the test after making changes to the scripts.

@All, I've updated the script /etc/rc.d/rc.country that runs at first boot and will test to see if it helps the keymap-related bugs discussed in my last post.
-TazOC

[Béèm]

Altho I have selected the Belgian keyboard, and altho this is correctly in xorg.conf, the keyboard stays in qwerty.

Don't see how I can change thhis.

Hi Béèm,
I tried it myself and noticed that there was no 'be' keymap at first boot, just 'be-latin1' which didn't work. However if I choose 'us' and then ran Input-Wizard from X I could select 'be' which gives: &é"'(§è!çà azertyuiop qsdfghjklmù wxcvbn; with Right Alt: œþæßðđŋħjĸł

desktop drive icons show 0GB space
The desktop drive icons show correctly the file system, but don't give the size of the partition. They all show 0GB.

At bit annoying.

Yes, indeed you're right, if I don't choose the default 'us' at first boot. When I chose the defaults at first boot and then switched to 'be' once in X the partition sizes are OK. I don't know why that is the case.
-TazOC

Very weird.
In other puppies I select be-latin1 for my Belgian keyboard.
So I wanted to try your procedure and got to the X command.
To my surprise I was in azerty.
But after typing Input-Wizard I got a message the script wasn't found.
So I restarted X and went into the keyboard setup.
I selected be instead of be-latin1 and restarted X.
I am indeed in azerty now.
As I said, weird as I never had to select be, but at least I can continue looking at Lighthouse.

As for the 0GB size, if I understand well, I have to do an initial install, leave us keyboard, then select afterward be. As I have a save file already, I'll leave it for the moment.

Thanks for the tip.

[Béèm]

Another showstopper.
Some important keys are missing in wine altho they are there in puppy.
The most important ones are é è ç à
As my e-mail and news clients are wine programs, and as I write often in French, this is a real showstopper.

Never had this issue in other puppies.

How can this be corrected?

[Béèm]

When going with the mouse over the CPU icon in the system tray, I get the CPU load, Ram, Swap and ACPI Temp, but the CPU Freq stays at O,OOOGHz.

[Béèm]

My cpu, special when running video's from youtube, is running hot. At times at 80°C
There is a thread about this in BUGS and adjusting the frequency with the cpu frequency scaling tool temperature can be limited. For Lucid and Quirky this tool is in Utility.
I have looked through the quite extensive menu of Lighthouse, but didn't find this tool.
Isn't it there? Does it exist?

[tazoc]

Hi Béèm,
The cpu frequency scaling tool is in the Utility Menu. In IceWM you have to scroll up with your mouse pointer as it may not show all the entries (move the cursor all the way up.) If it's not there, choose Menu | Window Manager | Refresh Menus. Still isn't there? Open /applications in ROX and click on cpu_freq.desktop.

To fix the drive icon size info, choose Menu | Desktop Settings | Desktop Drive Icons manager and tick 'Re-align existing icons'. Then restart X.

If that doesn't help, delete the files keymap, codepage and fontmap, all in /etc. Delete /etc/X11/xorg.conf. Then in /etc/profile change LANG=be to LANG=en_US. Then reboot and press Enter when prompted for country/region/language. Xorgwizard will run again. Back at the desktop, repeat the step in the previous paragraph to re-draw the icons and restart X. Then reset your keyboard and locale to 'be' with Menu | Setup | Mouse/Keyb wizard | Choose Keyboard Layout and FR_be with Menu | Desktop | Chooselocale.

Sometimes the CPU graph in IceWM doesn't show the CPU Freq so use Menu | Desktop Settings | Conky and it will show the CPU Freq in the middle of the second line. I will continue working on the next release which hopefully will avoid all these workarounds for be_latin1.
-TazOC

[CLAM01]

Hi tazOC,
My graphics chipset is the Intel G45M. I setup X using the Xorg-auto setup. My alternative Xkb setups also don't survive restarts of X. The keyboards I add most often are Danish and French, sometimes others, depending what characters I will need and how often. I add and remove since puppy doesn't have a chooser. When I activate alternate Xkb two files are added to tmp, one, XkbVariantDialog, which is the script, the other XkbVariantList. I have put screenshot jpgs of tmp before and after and of the added files open in geany in a file I will try to upload.
In caveat, I tend to mess my system up doing whatever I think might work. My setup is a mix now: To get desktop icons I copied a 4.3 pup-save file to my lighthouse partition and let lighthouse integrate with it. My background picture comes up during loading then goes away when the IceWM sets the desktop, leaving a dark blue background now, but everything seems to work, and I can drop files on icons to start the programs, which is what I wanted.
Apart from having to reset Xkb I have to start and then reboot to start cpu cooling. Apci doesn't start the cooling fans, or change their speeds. I let the cpu warm to about 40C then reboot, the bios sets the cooling fan on low, where it keeps cpu temp 35-38C. if I reboot at 50C the fan sets higher and the cpu runs 25-29C.
With these two fiddles I'm able to go to work.

[tazoc]

Hi CLAM01,
Maybe the Xorg Xkb settings aren't taking because the Xorg Autosetup (xorgwizard option 1) doesn't generate a full xorg.conf, just enough to keep the xwin script happy. So either run xorgwizard, option 2 then probe or choose 'intel', or maybe copy your xorg.conf over from your Puppy 4.3.1 setup.

If that doesn't help please run the Video Reporting Tool in the System Menu and attach /tmp/root/report-video-full.gz to a post. You can attach any small file by renaming it with a .zip extension with a note as such, or by running gzip <filename>.
Thanks,
TazOC

Edit: Does the CPU Freq Scaling Tool cool your CPU?

[Béèm]

Hi Béèm,

Hi tazoc

The cpu frequency scaling tool is in the Utility Menu. In IceWM you have to scroll up with your mouse pointer as it may not show all the entries (move the cursor all the way up.) If it's not there, choose Menu | Window Manager | Refresh Menus. Still isn't there? Open /applications in ROX and click on cpu_freq.desktop.

I hadn't noticed the menu was so big and that it was scrollable. A little arrow at the top and bottom of the menu would help.
I activated Cpu Freq Scaling by copying one from another puppy, but now I know I can change the values from the menu as well.
BTW after CFS was activated, I had the cpu freq value in the system tray also.
So that is sorted as well.

To fix the drive icon size info, choose Menu | Desktop Settings | Desktop Drive Icons manager and tick 'Re-align existing icons'. Then restart X.

That didn't help

If that doesn't help, delete the files keymap, codepage and fontmap, all in /etc. Delete /etc/X11/xorg.conf. Then in /etc/profile change LANG=be to LANG=en_US. Then reboot and press Enter when prompted for country/region/language. Xorgwizard will run again. Back at the desktop, repeat the step in the previous paragraph to re-draw the icons and restart X. Then reset your keyboard and locale to 'be' with Menu | Setup | Mouse/Keyb wizard | Choose Keyboard Layout and FR_be with Menu | Desktop | Chooselocale.

When I came at the point that Xorgwizard should I only got the selection panel for the keyboard. I then got to the Desktop and continued the advice with the selection of be as keyboard and be also in the layout.
As reported before I had done this already and indeed in linux I got the accented characters. But the showstopper which remains is that in Wine I don't have the accented characters like é§èçà. When pushing one of those, the cursor doesn't advance even. In all other puppies, I can select be-latin1 and all is ok even in wine. Hopefully you find why this is so and a solution for the next Lighthouse 5.00

Sometimes the CPU graph in IceWM doesn't show the CPU Freq so use Menu | Desktop Settings | Conky and it will show the CPU Freq in the middle of the second line. I will continue working on the next release which hopefully will avoid all these workarounds for be_latin1.

After setting the CPU freq scaling I have the CPU freq in the system tray as stated above already.

-TazOC

Bernard

[Béèm]

When I installed Lighthouse, I had to choose a 128MB save file.
Now the system tray says it's 124MB. Where could the 4MB be?
I use LH now some week, but didn't install packages.
I only added 3 sfs files, OOo, Pidgin 2.6.1, and virtual box.
When I looked this afternoon, the free space was already down to 12MB.
I left the PC running and when I came back, another 4MB was gone.
Leaving me with 8MB.

I tried to look where all those MB's could have been gone to, but didn't find it.
Someone has an idea?

[tazoc]

Hi Bernard,
I'm working on a context menu for freememapplet_tray for that very reason. The pupsave can fill up very quickly! I usually start with a 256M pupsave and end up enlarging it to around 448M. If you chose a .3fs format, there is some overhead for the journal and file system so not all of the pupsave is available. You can close all your apps and restart X. That will clear away some temporary files.

The quickest way to see where the space went in a frugal install is to open GdMap Graphical Disk Usage in the Utility or File System menu and then open /initrd/pup_rw. Then just hover your mouse pointer over the biggest items and read the file names and sizes.

Xorgwizard in LHP installs some Mesa GL libraries that use about 3.6M. Wine gobbles up ~40M the first time it's used and browsers like SeaMonkey have security features that use a lot of space just by having the browser open a while. Rebooting will clear the cache and most of those temporary files. Otherwise just add free space with Resize personal storage file in the System Menu.

See also /usr/share/doc/freememapplet.htm. I'm updating that page as well.
TazOC

[CLAM01]

Hi TazOC,
I've been looking in logs and /etc/X11/xorg.conf files in both Lighthouse and puppy 431, hoping to find why kbd language settings persist in P but not LHP. The settings are there in xorg.conf in both and the Xorg logs of both list all the same being loaded in the same places. I did find that the two extra files in /tmp are for the Xorg keyboard settings gui. By short-cutting, going from llooknfeel just to the keyboard-layouts-variants gui and clicking "yes, activate" and exiting, the settings activate and the two files don't appear. The few clicks are easy to do, so the settings not persisting through X-restarts is not a problem, just a quirk, one of those little glitches that has to be some detail, a set not setting or being reset by something following.
The cpu fan not being started by acpi is common to both P431 and lighthouse. I checked for frequency scaling. It is on and seems to be working. Acpi recognizes eight throttling settings for the cpu cores and a cooling fan for each, and their state, on or off. When I restart it recognizes the cooling fan on. Frequency scaling offers two sets, 1.2 and 2. ghz. It advances frequency to 2. when the cpu loads seriously. Opera trying to add some kind of auto-update feature went loopy and tested this, loading the cpu cores to 100% on both at 2. ghz. Cpu temp went from 35C to 58C, but steadied there [I really like having the monitoring aplet in the tray--it's much better than the keyboard getting hot detection method]. airflow didn't feel faster, but 58C is well below the bios failsafe threshold, 84C, when it kicks the fan on full.