Lighthouse 64 602 Beta2 with GIMP-2.8.4 (6-29-2013)

For talk and support relating specifically to Puppy derivatives
Message
Author
User avatar
edoc
Posts: 4729
Joined: Sun 07 Aug 2005, 20:16
Location: Southeast Georgia, USA
Contact:

Re: Frugal without the USB stick

#61 Post by edoc »

tazoc wrote:
QUESTION: Will I always have to boot with the USB stick or will I at some point be able to boot in Frugal without the USB stick?
Good job! If the installer shows a 'UEFI hard drive' (frugal install guide) button to the right, (on a machine with a GPT hard drive) you can try that. Let us know if you have any questions. The install guide (based on FD64's) is also here:
http://www.lhpup.org/help/faqs/uefi-harddrive.html
It only works on a machine with UEFI firmware, typically with Windows 7/8. If you don't have the 'UEFI hard drive' button in the Universal Installer, let us know.
Yes, it does show "UEFI hard drive" & I started the process, but ...

I don't see a way to boot without a Savefile.

The Frugal install will not allow sda4 to be seen and used as it is in use, it only sees the USB stick.

BTW: sda4 is an ext3 Filesystem

Am I missing it or does the option to boot like the common "puppy pfix=ram" need to be added to the other several boot options in the menu?

So I understand that for now there is an extra step to install Frugal - one must first create and use the USB/UEFI flash drive and then perform the UEFI hard drive for Frugal?
Last edited by edoc on Wed 03 Jul 2013, 00:21, edited 3 times in total.
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603

tlchost
Posts: 2057
Joined: Sun 05 Aug 2007, 23:26
Location: Baltimore, Maryland USA
Contact:

#62 Post by tlchost »

[quote="dancytron"
Thom[/quote]

I haven't really tested it, but I added "pfix=noautosave" to the boot command.[/quote]

Is autosave the one that you see on reboot, or is it the one that defaults to every 30 minutes? I want to control whether or not I write to the save file when I reboot/shutdown.

Thom

tlchost
Posts: 2057
Joined: Sun 05 Aug 2007, 23:26
Location: Baltimore, Maryland USA
Contact:

Re: Pidgin Logs

#63 Post by tlchost »

tazoc wrote:Open a terminal in /mnt/home/ or (where ever your .purple resides,) and type:

Code: Select all

chown -R spot .purple
If for some reason that doesn't work, you can run pidgin as root:
Open /usr/local/bin/defaultchat with a text editor and change pidgin.sh to pidgin
Same goes for /usr/share/applications/pidgin.desktop, in the line that begins with Exec=
Tried the second method....works...will try the chown, since that would mean not changing the individual scripts, .desktops, etc.

Thanks!

dancytron
Posts: 1519
Joined: Wed 18 Jul 2012, 19:20

#64 Post by dancytron »

Regarding autosave.

It seems to ask you whether you want to save on every reboot. I don't know if it turns off the periodic save or if setting the puppy event manager field to 0 is what did that.

tlchost
Posts: 2057
Joined: Sun 05 Aug 2007, 23:26
Location: Baltimore, Maryland USA
Contact:

Re: Pidgin Logs

#65 Post by tlchost »

tazoc wrote:. So make .purple owned by spot, (root can still write to files owned by spot.) Open a terminal in /mnt/home/ or (where ever your .purple resides,) and type:

Code: Select all

chown -R spot .purple
If for some reason that doesn't work, you can run pidgin as root:
Not matter what I try chown does not change the ownership of any of the files/directories on
/mnt/home.

I guess to do what I want, I'll have to track down every application that runs as spot and change the parameters to run as root.

Lots of work....is there a list?

User avatar
edoc
Posts: 4729
Joined: Sun 07 Aug 2005, 20:16
Location: Southeast Georgia, USA
Contact:

#66 Post by edoc »

OK, so it was there right in front of me ... except ... I cannot choose LH without savefile AND the Radeon bypass.

How do I do that because choosing LH without savefile brings me to an unusable screen & choosing LH with the Radeon bypass forces the savefile - making Frugal setup impossible.

Help, please? :roll:
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603

gcmartin

#67 Post by gcmartin »

edoc wrote:OK, ... How do I do that because choosing LH without savefile brings me to an unusable screen & choosing LH with the Radeon bypass forces the savefile - making Frugal setup impossible.

Help, please?
This may work (although I've never tried it):
  1. Boot system
  2. When boot manager screen pops-up, highlight the Radeon line and hit your tab key
  3. A line will pop at the bottom on the screen. Add the following to that line

    Code: Select all

    pfix=ram
  4. Hit the enter key to allow boot to proceed
Hope this helps

Sylvander
Posts: 4416
Joined: Mon 15 Dec 2008, 11:06
Location: West Lothian, Scotland, UK

#68 Post by Sylvander »

dancytron wrote:I added "pfix=noautosave" to the boot command. I did this by adding an entry to the syslinux.cfg file.
Where should I find the syslinux.cfg file?

User avatar
tazoc
Posts: 1157
Joined: Mon 11 Dec 2006, 08:07
Location: Lower Columbia Basin WA US
Contact:

Re: lid suspend

#69 Post by tazoc »

Marv wrote:Suspend occurred correctly on lid closure, wireless shut down ok. On reopening, x restarted, network enabled, frisbee acquired a lease... and then it immediately suspended again.

Cause is, in /etc/acpi/events,lid calls /etc/acpi/action/suspend.sh for any lid event, open or close. Could put a test in it so only a closure calls suspend.sh but the appropiate test already exists in lines 4 through 7 of /etc/acpi/actions/suspend.sh. I uncommented those lines as below and changed the comment line slightly to better reflect what it does

Code: Select all

# do not suspend on lid open event
if [ "$(cat /proc/acpi/button/lid/*/state | grep open)" != "" ] ; then
exit
fi
and the false resuspend is gone.
Thank you, Marv. Will add that change to the next update.
[url=http://www.lhpup.org/][b][size=100]lhpup.org[/size][/b] [img]http://www.lhpup.org/gallery/images/favicon.png[/img][/url] [url=http://www.lhpup.org/release-lhp.htm#602]Lighthouse 64 6.02[/url]

User avatar
tazoc
Posts: 1157
Joined: Mon 11 Dec 2006, 08:07
Location: Lower Columbia Basin WA US
Contact:

Re: KDE4 workaround

#70 Post by tazoc »

Jim1911 wrote:When WM tries to start it shows an error: "kstartupconfig4 does not exist or fails. The error code is 127." Clicking on OK provides the shutdown screen and allows me to switch to another WM. All other WM work fine
Hi Jim,
I googled the error msg and found this:

Code: Select all

chown -R root.root /root/.kde
Maybe it will help you.
-TaZoC
[url=http://www.lhpup.org/][b][size=100]lhpup.org[/size][/b] [img]http://www.lhpup.org/gallery/images/favicon.png[/img][/url] [url=http://www.lhpup.org/release-lhp.htm#602]Lighthouse 64 6.02[/url]

User avatar
edoc
Posts: 4729
Joined: Sun 07 Aug 2005, 20:16
Location: Southeast Georgia, USA
Contact:

#71 Post by edoc »

gcmartin wrote:
edoc wrote:OK, ... How do I do that because choosing LH without savefile brings me to an unusable screen & choosing LH with the Radeon bypass forces the savefile - making Frugal setup impossible.

Help, please?
This may work (although I've never tried it):
  1. Boot system
  2. When boot manager screen pops-up, highlight the Radeon line and hit your tab key
  3. A line will pop at the bottom on the screen. Add the following to that line

    Code: Select all

    pfix=ram
  4. Hit the enter key to allow boot to proceed
Hope this helps
The tab key does not respond.

When the boot menu opened I hit the arrow key (any key may work the same, I don't know).

I then hit "e" to enter edit mode.

I first tried to add "puppy pfix=ram" but it generated an error on "puppy" and I had to reboot and start over.

I then tried just "pfix=ram" but the screen was twitchy & the mouse unresponsive - used Alt-f4 to get a command window & typed reboot to a command line where I had to type reboot again.

It occurred to me that I may not have used the disable Radeon boot so I tried again making sure I was on that selection before adding "pfix=ram" and that got me a working screen but sda4 was still locked.

Why is it ignoring the "pfix=ram" ?
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603

User avatar
edoc
Posts: 4729
Joined: Sun 07 Aug 2005, 20:16
Location: Southeast Georgia, USA
Contact:

#72 Post by edoc »

FOUND IT! :lol:

I needed to put the "pfix=ram" on the same line as the disable radeon line.

Now I need to work through the Frugal install process ...
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603

User avatar
edoc
Posts: 4729
Joined: Sun 07 Aug 2005, 20:16
Location: Southeast Georgia, USA
Contact:

#73 Post by edoc »

The Frugal/UEFI install instructions say to create a FAT32 partition.

Is this necessary or can this be done in ext3 or ext4?
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603

dancytron
Posts: 1519
Joined: Wed 18 Jul 2012, 19:20

#74 Post by dancytron »

Sylvander wrote:
dancytron wrote:I added "pfix=noautosave" to the boot command. I did this by adding an entry to the syslinux.cfg file.
Where should I find the syslinux.cfg file?
It was on the usb thumb drive when I had it installed there. I installed it using UniversalUSBInstaller from Windows. If you are using grub, then you'd put it in the menu.1st file.

User avatar
Barburo
Posts: 298
Joined: Thu 14 Jun 2007, 18:49

#75 Post by Barburo »

Hi Taz,
I'm late to the party as usual, but LHP64 is getting better with every release. LHP602 has cool new wallpaper and gentle sound of waves on the shore to greet me. No problems booting straight to the desktop with correct resolution:
Processor : AMD Sempron(tm) Processor 3000+
Memory : 1020MB (566MB used)
Operating System : Lighthouse 64 6.02 B2
-Display- Resolution : 1680x1050 pixels
OpenGL Renderer : Gallium 0.4 on ATI R481
Thanks for including the .sfs for Chrome v.26 - I don't know if anyone else uses chrome browser, but here's a problem I've had for the last few releases of LHP64:
Chrome browser opens up and CPU rapidly goes to 99% to 100% and stays there.

The browser opens (slowly) and I sometimes get the "unresponsive page" alert, but chrome continues to work but slower than molasses. Obviously not what I need.

Firefox uses a similar large CPU on startup but rapidly diminished to usual levels with excellent responsiveness.

I use Chromium-browser in Precise Puppy 5.5 and Mint14 on this same box, and it behaves normally without the memory usage problem.

Any suggestions about how I can Chrome working properly?
B.
Attachments
chrome.jpg
(26.19 KiB) Downloaded 490 times
[i]Laptop[/i]: Acer Aspire 5810TZ

User avatar
edoc
Posts: 4729
Joined: Sun 07 Aug 2005, 20:16
Location: Southeast Georgia, USA
Contact:

#76 Post by edoc »

After doing all of the setup stuff for Frugal I went to reboot and the Save to File did not provide the same valuable options as usual - in fact it appeared that it might write the Savefile to sda1 rather than sda4.

There was an option to save to the sda4 partition but I have not done that previously in Frugal and don't know if that is recommended.

I chose Abort then rebooted then decided to try Save to File and only then saw that it provided the options of save location, filesystem type, etc.

It may be helpful to edit the Save window to say that further options will appear in the next window.

The laptop defaults to MS Win7 with no user interaction and if I hit esc I get a menu that only offers Win7.

If I hit F2 during boot I get a HP PC Hardware Diagnostics UEFI menu.

NOTE: The USB boot stick is not plugged in (it should not be necessary for Frugal) and neither is the LH64-b2 DVD.

How do I get to a menu where I can select LH64-b2 or MS win7, please?
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603

User avatar
Barburo
Posts: 298
Joined: Thu 14 Jun 2007, 18:49

#77 Post by Barburo »

Compiz-Fusion works just fine in 602B2:

Add CompizFusion-0.8.8-x86_64-3.sfs to bootup selection, (available at lhpup.org).
Reboot, go to "Shutdown" select "Change WM" and "Fusion" appears as a selection. Just click and desktop will reload with C-F as your WM. Compiz-Fusion Icon will appear on the taskbar and you rightclick for Settings manager or Emerald Theme Manager.
Simple and effective.
B.
[i]Laptop[/i]: Acer Aspire 5810TZ

Sylvander
Posts: 4416
Joined: Mon 15 Dec 2008, 11:06
Location: West Lothian, Scotland, UK

#78 Post by Sylvander »

dancytron wrote:It was on the usb thumb drive when I had it installed there.
a. I'm booting my Lighthouse-5.6.1 from a CD-RW, with L64Save.4fs+SFS files in a folder in the root of a partition on my internal HDD.
I cannot find a syslinux.cfg file on the CD, nor anywhere inside the L64Save file.

b. On the optical disk, there is a file named isolinux.cfg...
Might this be the file to which I should add the code?
I know HOW to do that, but need confirmation of WHAT to add.

Jim1911
Posts: 2460
Joined: Mon 19 May 2008, 20:39
Location: Texas, USA

Re: KDE4 workaround

#79 Post by Jim1911 »

tazoc wrote:
Jim1911 wrote:When WM tries to start it shows an error: "kstartupconfig4 does not exist or fails. The error code is 127." Clicking on OK provides the shutdown screen and allows me to switch to another WM. All other WM work fine
Hi Jim,
I googled the error msg and found this:

Code: Select all

chown -R root.root /root/.kde
Maybe it will help you.
-TaZoC
Sorry, it did not work, still have the same symptoms.

tlchost
Posts: 2057
Joined: Sun 05 Aug 2007, 23:26
Location: Baltimore, Maryland USA
Contact:

Re: KDE4 workaround

#80 Post by tlchost »

Jim1911 wrote:[]Sorry, it did not work, still have the same symptoms.
Did the command change the group and owner to root?

Same command to changer ownership to spot also did not work.

Odd.

Thom

Post Reply