Page 15 of 20
Posted: Sun 27 Sep 2015, 21:30
by Dry Falls
edoc wrote:Is there anything from the USB stick that works that I might open and post that might shed some light as to why it works and these two tries failed?
Dry Falls wrote:From menu -> setup, scroll down to 'Lighthouse Universal installer' which is what you originally used (judging from the screenshot).
then choose 'Make UEFI flash drive'. It does the same as if you folowed the instructions in the 'isohybrid-usbflash' folder on the iso: 'uefi-flashdrive.html'
df
Posted: Mon 28 Sep 2015, 00:28
by edoc
'Lighthouse Universal installer' is requiring a file specified as Just-Lighthouse.iso - which I don't have.
The iso's I have are all JL64-603*.iso etc.
Is there a workaround, please?
Thanks.
EDIT1: I had not noticed the "*" in the name which gave me a tip-off.
I created a subfolder, copied the 150820 iso there, then renamed it - appears to be creating the UEFI USB boot stick now ...
EDIT2: It worked but I think it's defaulting to the .iso in the subfolder - or maybe opening a copy of the JL64 .SFS somewhere - but I don't know how to determine where it is looking & I'm not sure how to tell it to look where I want it to :/mnt/home/stuff/jl64/
The goal is for this to be a Frugal install (necessarily booted from USB due to the weird UEFI on this laptop) so that I can update and modify easily.
This new boot method seems to have added extra steps & complicated the simple ... but maybe it's merely unfamiliar ...
Posted: Mon 28 Sep 2015, 01:50
by Dry Falls
'Lighthouse Universal installer' is requiring a file specified as Just-Lighthouse.iso - which I don't have.
I will add a distro-spec parameter to the script. So in the mean time, rename the file. Right. Thanks for pointing this out!
EDIT2: It worked but I think it's defaulting to the .iso in the subfolder & I'm not sure how to tell it to look where I want it to :/mnt/home/stuff/jl64/
You can only go one directory deep. (You did mean ".sfs", not ".iso"?)
This new boot method seems to have added extra steps & complicated the simple ... but maybe it's merely unfamiliar ...
It's not a new method, it's the original. But if it's the only way to boot your machine, then ...
Once you've booted, drag your cfg file to the partition or folder with the kernel+initrd+basefile and edit. Grub will find it but I'm not sure about isolinux. You may have to enter 'e' at the boot menu to add boot parameters (pdev1=*, pmedia=*, psubdir=*) each time if that doesn't work.
df
Posted: Sat 03 Oct 2015, 16:45
by edoc
Finally got few minutes to get back to this ...
Coffee isn't compensating for the short night's sleep like it used to ...
Where would I look for the cfg file that I need to drag over, please?
Would it be on the boot USB stick or ??
I see grub.cfg and isolinux.cfg in JL64_LIVE - are those the ones I want?
This is a dual-boot setup from 2013.
sda1 contains an EFI folder and a file labeled "grldr"
sda2 is something for MS
sda3 is ntfs for MS
sda4 is ext3
sda5 is linux-swap
sda6 is fat32 for MS
Can't tell you why it's laid out like that - looks messy to me.
Posted: Sat 03 Oct 2015, 17:11
by edoc
Here's the grub.cfg
I edited just lines 5 & 6 - as in quote box - get it done?
linux /mnt/home/jl64/vmlinuz pfix=noautosave,copy,fsck
initrd /mnt/home/jl64/initrd.xz
Code: Select all
insmod png
background_image /menu.png
set timeout=10
menuentry "Default Just-Lighthouse64 - noautosave" {
linux /mnt/home/vmlinuz pfix=noautosave,copy,fsck
initrd /mnt/home/initrd.xz
}
menuentry "Start Lighthouse64 with xorgwizard - ram" {
linux /vmlinuz pfix=xorgwizard,ram,copy
initrd /initrd.xz
}
menuentry " ---" { true; }
menuentry "1 Just-Lighthouse64" {
linux /vmlinuz
initrd /initrd.xz
}
menuentry "2 Just-Lighthouse64 without savefile" {
linux /vmlinuz pfix=ram
initrd /initrd.xz
}
menuentry "3 Clean boot Just-Lighthouse64 from CD/DVD / first multisession" {
linux /vmlinuz pmedia=cd pfix=ram,copy
initrd /initrd.xz
}
menuentry "3b Clean boot Just-Lighthouse64 from USB / first multisession" {
linux /vmlinuz pmedia=usbflash pfix=ram,copy
initrd /initrd.xz
}
menuentry "4 Just-Lighthouse64 with multisession support CD/DVD" {
linux /vmlinuz pmedia=cd pfix=copy
initrd /initrd.xz
}
menuentry "4b Just-Lighthouse64 with multisession support USB" {
linux /vmlinuz pmedia=usbflash pfix=copy
initrd /initrd.xz
}
menuentry "5 Lighthouse64 without graphical desktop" {
linux /vmlinuz pfix=nox
initrd /initrd.xz
}
menuentry " ---" { true; }
menuentry "6 For problematic Radeon cards - disable radeon driver" {
linux /vmlinuz blacklist=radeon
initrd /initrd.xz
}
menuentry "7 For problematic Nvidia cards - disable nouveau driver" {
linux /vmlinuz blacklist=nouveau
initrd /initrd.xz
}
submenu "8 For severe video problems - disable KMS, use wizard" {
menuentry "Set video resolution to 640x480" {
terminal_output console
set gfxmode=640x480
set gfxpayload=keep
terminal_output gfxterm
}
menuentry "Set video resolution to 800x600" {
terminal_output console
set gfxmode=800x600
set gfxpayload=keep
terminal_output gfxterm
}
menuentry "Set video resolution to 1024x768" {
terminal_output console
set gfxmode=1024x768
set gfxpayload=keep
terminal_output gfxterm
}
menuentry "List all supported video resolutions" {
videoinfo
echo "Press Enter to continue ..."
read
}
menuentry "Use video resolution not listed in this menu" {
echo "Enter video resolution (WxH e.g. 800x600), press Enter to continue."
read gfxmode
terminal_output console
set gfxpayload=keep
terminal_output gfxterm
}
menuentry "Start Lighthouse64 with the chosen resolution" {
linux /vmlinuz nomodeset pfix=xorgwizard,ram
initrd /initrd.xz
}
}
menuentry "9 Just-Lighthouse64 with file system check" {
linux /vmlinuz pfix=fsck
initrd /initrd.xz
}
menuentry " ---" { true; }
menuentry "Firmware configuration" {
fwsetup
}
menuentry "Shutdown" {
halt
}
menuentry "Reboot" {
reboot
}
Here's isolinux.cfg
Would editing lines 35 & 37 the same as I did grub.cfg be correct?
linux /mnt/home/jl64/vmlinuz
append pfix=noautosave,copy,fsck
initrd /mnt/home/jl64/nitrd.xz
Code: Select all
default save-on-demand
prompt 1
timeout 100
F1 help.msg blank.png
F2 sfs.msg blank.png
F3 help2.msg blank.png
F4 kernel.msg blank.png
ui vesamenu.c32
menu title Just-Lighthouse64
menu resolution 800 600
menu background menu.png
menu tabmsg Use arrow keys to navigate, <Tab> to edit entry, <F1> for boot options, <Esc> for boot prompt.
menu color border 37;40 #80FFFFFF #00000000 std
menu color title 1;36;44 #ff93CBF0 #00000000 std
menu color unsel 37;44 #90FFFFFF #00000000 std
menu color sel 7;37;40 #ffE6C57D #40519BCB std
menu color hotkey 1;37;44 #ffE6C57D #00000000 std
menu color hotsel 1;7;37;40 #ffFFE3A8 #40519BCB std
menu color tabmsg 31;40 #ff93CBF0 #00000000 std
menu color help 37;40 #80E6C57D #00000000 std
menu color cmdmark 1;36;40 #c093CBF0 #00000000 std
menu margin 1
menu rows 19
menu tabmsgrow 25
menu cmdlinerow -2
menu passwordrow 19
menu timeoutrow 28
menu helpmsgrow 30
label save-on-demand
linux vmlinuz
append pfix=noautosave,copy,fsck
initrd initrd.xz
menu label 1 ^Just-Lighthouse64
text help
Start Just-Lighthouse64 with save-on-demand
endtext
label xorgwizard
linux vmlinuz
append pfix=xorgwizard,ram,copy
initrd initrd.xz
menu label 2 ^Just-Lighthouse64 modesetting
text help
Start Just-Lighthouse64 with xorgwizard (first-run/ram)
endtext
label JL64
linux vmlinuz
initrd initrd.xz
menu label 3 ^Just-Lighthouse64
text help
Start Just-Lighthouse64 normally.
endtext
label ram
linux vmlinuz
initrd initrd.xz
append pfix=ram
menu label 4 Just-Lighthouse64 without ^save file
text help
Clean boot Just-Lighthouse64 without loading any prior sessions. (pfix=ram)
endtext
label cd/dvdram
linux vmlinuz
initrd initrd.xz
append pmedia=cd pfix=ram,copy
menu label 5 Clean boot Lighthouse64 from ^CD/DVD / first multisession
text help
Start Just-Lighthouse64 without using a save file, and boot from an
optical disc drive, so that all drives can be unmounted. This is
recommended before using GParted or other partitioning tools.
Also used to initialize a new multisession CD/DVD by saving the
first session back to the same optical disc at shutdown.
(pmedia=cd pfix=ram,copy)
endtext
label usbram
linux vmlinuz
initrd initrd.xz
append pmedia=usbflash pfix=ram,copy
menu label 5b Clean boot Lighthouse64 from ^USB / first multisession
text help
Start Just-Lighthouse64 without using a save file, and boot from an
usb drive, so that all drives can be unmounted. This is
recommended before using GParted or other partitioning tools.
Also used to initialize a new multisession usb by saving the
first session back to the same drive at shutdown.
(pmedia=usbflash pfix=ram,copy)
endtext
label multi-optical
linux vmlinuz
initrd initrd.xz
append pmedia=cd pfix=copy
menu label 6 Just-Lighthouse64 with m^ultisession support
text help
Start Just-Lighthouse64 with multisession support from an optical disc drive.
Upon startup, previous sessions (if any) will be loaded from the disc.
If desired, changes can be saved as a new session to the disc.
Recommend to use DVD+RW as the disc media. (pmedia=cd pfix=copy)
Note: Use option 3 above for saving the first session back to CD/DVD.
endtext
label multi-usb
linux vmlinuz
initrd initrd.xz
append pmedia=usbflash pfix=copy
menu label 6b Just-Lighthouse64 with m^ultisession support
text help
Start Just-Lighthouse64 with multisession support from a usb flash drive.
Upon startup, previous sessions (if any) will be loaded from the disc.
If desired, changes can be saved as a new session to the drive.
endtext
label nox
linux vmlinuz
initrd initrd.xz
append pfix=nox
menu label 7 Just-Lighthouse64 without ^graphical desktop
text help
Start Just-Lighthouse64 in command-line mode, Linux console. (pfix=nox)
The graphical desktop can be started later by typing "xwin".
endtext
menu separator
label noradeon
linux vmlinuz
initrd initrd.xz
append blacklist=radeon
menu label 8 For problematic ^Radeon cards - disable radeon driver
text help
Start Just-Lighthouse64 without loading the radeon driver. (blacklist=radeon)
endtext
label nonouveau
linux vmlinuz
initrd initrd.xz
append blacklist=nouveau
menu label 9 For problematic ^Nvidia cards - disable nouveau driver
text help
Start Just-Lighthouse64 without loading the nouveau driver. (blacklist=nouveau)
endtext
label nokms
linux vmlinuz
initrd initrd.xz
append nomodeset pfix=xorgwizard,ram
menu label 10 For severe ^video problems - disable KMS, use wizard
text help
Start Just-Lighthouse64 without save file, without KMS (nomodeset) and launch
xorgwizard-puppy to choose video resolutions before starting the graphical desktop.
(pfix=xorgwizard,ram)
endtext
menu separator
label f
linux vmlinuz
initrd initrd.xz
append pfix=fsck
menu label 11 Just-Lighthouse64 with ^file system check
text help
Start Just-Lighthouse64 with file system check on ext2/3/4 partitions and
save file, if present. (pfix=fsck)
endtext
menu separator
label h
localboot 0x80
MENU LABEL Boot operating system on ^hard disk
text help
Boot from first hard disk. (localboot 0x80)
endtext
menu separator
LABEL memtest
LINUX memtest
MENU LABEL ^Memtest86+ memory diagnostic
text help
Run system memory stress test.
endtext
menu separator
LABEL reboot
MENU LABEL R^eboot
COM32 reboot.c32
LABEL poweroff
MENU LABEL ^Power Off
COMBOOT poweroff.com
label puppy
menu hide
linux vmlinuz
initrd initrd.xz
label c
menu hide
linux vmlinuz
initrd initrd.xz
append pfix=copy
label vesa
menu hide
linux vmlinuz
initrd initrd.xz
append nomodeset pfix=vesa,ram
label safe
menu hide
linux vmlinuz
initrd initrd.xz
append nomodeset debug pfix=ram,fsck,nox,vesa,nocopy
label lb0
menu hide
localboot 0x80
label lb1
menu hide
localboot 0x81
label lb2
menu hide
localboot 0x82
label lb3
menu hide
localboot 0x83
label lb4
menu hide
localboot 0x84
label lb5
menu hide
localboot 0x85
label lb6
menu hide
localboot 0x86
label lbf
menu hide
localboot 0x00
Posted: Sat 03 Oct 2015, 18:25
by edoc
I made the changes to the copies of grub.cfg and isolinux.cfg on my HDD, located in /mnt/home/jl64/
I'm not certain how to tell if the OS is running from my Frugal install on the HDD (/mnt/home/jl64/) or from the copy that was installed on the USB boot stick (JL64_LIVE) by Lighthouse Installer.
Seamonkey crashes every time I open it - so I cannot get work done.
JL64_LIVE is a read-only file system.
I cannot edit grub.cfg or isolinux.cfg on the USB stick.
What should I try next, please?
Posted: Sat 03 Oct 2015, 18:57
by edoc
Oh, BTW, in a few minutes I'll be looking over the shoulder of our 20yr old son as he starts this online Linux course:
https://training.linuxfoundation.org/li ... on/outline
Maybe I will learn, and remember, enough to solve more problems with fewer questions?
Y'all can hope ...
Posted: Sat 03 Oct 2015, 21:11
by Dry Falls
hi edoc. Which seamonkey are you using? v2.35 is much improved in that regard over earlier versions. I'm a bit surprised to hear this. Are you using the sfs addon tailored for JL64 (Seamonkey-2.35-x86_64.sfs @ gdrive)?
This "old fashioned" usb install dd's the iso onto the usb stick, so it will behave (read-only) the same. Drag the kernel, initrd.xz & grub.cfg on to the top of your drive partition, not in a folder! Grub (if that is what you're using), will use it instead of from the usb stick. The base file & savefile can be there OR in a subdirectory. If you don't copy the logo/menu images, you'll know when you get to the boot menu which you're running from.
I think isolinux should work the same way but not sure.
df
Posted: Sat 03 Oct 2015, 22:15
by edoc
I had Seamonkey-2.33_x86_64-1.sfs
I'll try the newer version.
I need to clean out the old clutter in /mnt/home/.
linuz.gx & initrd.xz to /mnt/home/
jl64-603.sfs to /mnt/home/jl64/ (I presume I can keep all of the SFS files there or do some or all of the others have to be in /mnt/home/ ?
jl64save.4fs to /mnt/home/savestuff/
Once running I then need to run the delta - and what it changes will be saved to the savefile?
Let's see how much of a mess I can make ...
JL64-604
Posted: Tue 06 Oct 2015, 11:32
by Dry Falls
see opening post for JL64-604 first release. Trying out pupnet, after peebee's release of lxtahrpup64 there. It seems a lot friendlier so far. ftp upload is nice for a change.
Anyway, it's a pretty bare bones iso. No efi boot, so it can be edited/remastered with isomaster. It presented no problems booting with qemu. The pet on the iso has the stock dri modules for mesa 9.17. They just didn't work for me so I left in the originals from 8.04. The rest of the package is upgraded.
Dual hybrid iso will be forthcoming and contains the devx & kernel modules. No wine. Use the old zWine renamed appropriately or apply the delta patch.
edit:
Need more work on 4_kde addon. Some conflict in qt, although the version (4.85) is the same. Puzzled.
df
Re: JL64-604
Posted: Wed 07 Oct 2015, 05:36
by James C
Dry Falls wrote:see opening post for JL64-604 first release. Trying out pupnet, after peebee's release of lxtahrpup64 there. It seems a lot friendlier so far. ftp upload is nice for a change.
Anyway, it's a pretty bare bones iso. No efi boot, so it can be edited/remastered with isomaster. It presented no problems booting with qemu. The pet on the iso has the stock dri modules for mesa 9.17. They just didn't work for me so I left in the originals from 8.04. The rest of the package is upgraded.
Really busy but gave it a quick run live. Had to use
xorgwizard-puppy to get the display working but otherwise appeared to be working as expected.
More when I find some free time....
Posted: Sat 10 Oct 2015, 15:52
by David Andrew
Hello, thanks for the hard work maintaining this Puppy.
I’ve used the original Lighthouse64 since 2013, and (until recently) had been using the same savefile for all that time. Interestingly enough, I managed to get many Slackware 14.1 packages working for it. However, somewhere down the line I messed something up and my primary browser, (Firefox), was frequently crashing, with no obvious solution (believe me I tried everything).
So about a month ago I had to decided to start anew with either the original ISO, or this newly maintained JL64. So as I like to keep on top of things, the logical choice was this one, and so far I’ve had no major problems with it. The few problems I have been having will be pointed out. As I write, I’m using the very latest 604g ISO, where Wine is no longer integrated (a good choice IMO).
Some feedback:
I had a lot of trouble getting some of my 32-bit programs to work. I have tried the Slacko-32 SFS from the JL64 add-ons page and they didn’t work. Some 32-bit programs did work, just not the ones I use. I then tried some of the original Slacko-32 SFS’s and those didn’t work either. I did find a solution. From the latest Slacko 32 bit ISO, I copied all of the libs (libs & usr/libs) into to the corresponding JL64 “lib32 & usr/lib32“ directories, and now my 32-bit programs are working perfectly.
With the original LH64 I was able to upgrade to the latest Mesa by building and creating the package with a Slackbuild script. This doesn’t seem possible with JL64, nor does upgrading Mesa to version 10 or beyond. When I try to install a Mesa TZX package with the “upgrade
Posted: Sat 10 Oct 2015, 16:44
by Dry Falls
Hi David. The thing with JL64 is it still has the original xorg server (1.12.3). I also reverted back to the original busybox. An upgraded xorg will probably be necessary for further upgrades to mesa. The thing is that xorg progressively does less and less (Xorg has the opposite philosophy as systemd), but Lighthouse depends on it doing more. The result is that fonts and displays get screwed up. Personally, I always run xorgwizard-puppy any way, letting the kernel provide the video drivers. I have to do this in April and fatdog as well, so there's no real advantage for me to upgrade xorg from that side of things, and as you say, the existing mesa works pretty well.
Wine is still useful for the 32 bit libs, and has the same slacko32 libs built in. But your solution works, so no problem. I only use wine for the sattelite usage monitor (only works under windows) and my check register from windows3.1/95. To use the newest slack32 package ( fd repo has it), it has to be rebuilt, since lighthouse arranges things a bit differently than fatdog or slacko. While mostly compatible, it's not a woof-CE build.
more later
df
Posted: Sun 11 Oct 2015, 20:31
by David Andrew
Dry Falls wrote:Hi David. The thing with JL64 is it still has the original xorg server (1.12.3). I also reverted back to the original busybox. An upgraded xorg will probably be necessary for further upgrades to mesa. The thing is that xorg progressively does less and less (Xorg has the opposite philosophy as systemd), but Lighthouse depends on it doing more. The result is that fonts and displays get screwed up. Personally, I always run xorgwizard-puppy any way, letting the kernel provide the video drivers. I have to do this in April and fatdog as well, so there's no real advantage for me to upgrade xorg from that side of things, and as you say, the existing mesa works pretty well.
Wine is still useful for the 32 bit libs, and has the same slacko32 libs built in. But your solution works, so no problem. I only use wine for the sattelite usage monitor (only works under windows) and my check register from windows3.1/95. To use the newest slack32 package ( fd repo has it), it has to be rebuilt, since lighthouse arranges things a bit differently than fatdog or slacko. While mostly compatible, it's not a woof-CE build.
more later
df
Understood.
Mesa 9.17 is working fine for me as well, and I don't want to mess around with things that I don't fully understand again, like I did with my previous LH64 setup. I think I took it a bit too far. I noticed no obvious improvements with Mesa 10 - 11.
As a rule of thumb, I'll stick to what is supported by the new gslapt manager etc. Got everything working exactly as before now.
I like how it's evolving to be more user friendly.
Posted: Fri 16 Oct 2015, 00:40
by Dry Falls
"Mariner" version uploaded. Iso contains DevX and kernel sources. Following the lead taken in the libre-Pup thread, I've included qupzilla browser (with qt-4.8.7) on the 5)JL64 sfs addon.
Base file is different than the one on the noefi iso. Browsers at g-drive are still applicable. I pretty much go with palemoon & seamonkey.
Just-Lighthouse64-604.3.iso
Just-Lighthouse64-604.3.iso.md5sum.txt
df
Posted: Fri 16 Oct 2015, 02:17
by edoc
Cool to see the new versions!
Tried to download twice & failed twice, first time at 20MB second at 17MB.
Is there a trick?
Thanks ...
Posted: Fri 16 Oct 2015, 16:57
by edoc
Third try - today - worked!
Now to find time in-between interruptions to give it a try ...
Posted: Fri 16 Oct 2015, 17:16
by edoc
Dry Falls wrote:hi edoc. Which seamonkey are you using? v2.35 is much improved in that regard over earlier versions. I'm a bit surprised to hear this. Are you using the sfs addon tailored for JL64 (Seamonkey-2.35-x86_64.sfs @ gdrive)?
I still only see v. 2.33 on gdrive.
Posted: Fri 16 Oct 2015, 22:08
by Dry Falls
I still only see v. 2.33 on gdrive.
Try refreshing your browser cache (reload page). v2.35 is there.
Sounds like you experienced server timeout at filepup. It may not be a good pick for large files if this happens frequently. What can I say? Still experimenting.
df
Posted: Fri 16 Oct 2015, 23:54
by edoc
I tried Refresh and I tried sending this link
https://drive.google.com/folderview?id= ... sp=sharing
... to another computer - same result.
The only Seamonkey that shows is 2.33...
I cannot explain why.