Just-Lighthouse64-603/604

For talk and support relating specifically to Puppy derivatives
Message
Author
Dry Falls
Posts: 616
Joined: Tue 16 Dec 2014, 23:37
Location: Upper Columbia

patch

#21 Post by Dry Falls »

JL64_patch-0.4.1.pet (439K) added to gdrive. updates busybox & Rox-Filer configs
initrd.xz rebuilt with glib update/busybox to jive with Delta file and patch. Same repo.
dillo-fix.pet same repo
Last edited by Dry Falls on Tue 23 Jun 2015, 16:47, edited 1 time in total.

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

#22 Post by edoc »

Added v 603 to the frugal installs on a laptop.

It looks great but ...

When I try to apply the patch I get this error:
xdelta3: using default output filename: /initrd/mnt/dev_ro2/JL64603frugal/JL64-603.sfs
xdxdelta3: using default output filename: /initrd/mnt/dev_ro2/JL64603frugal/JL64-603.sfs
xdelta3: using default source filename: /initrd/mnt/dev_ro2/JL64603frugal/JL64-603.sfs
xdelta3: source /initrd/mnt/dev_ro2/JL64603frugal/JL64-603.sfs winsize 64 MB size 280375296
xdelta3: target window checksum mismatch: XD3_INVALID_INPUT

Press Enter or close this window to continue.
Have you seen this before and is there a workaround, please?

I have access to this laptop uninterrupted for a few hours so am hoping to get this resolved and updated then chase the printer/CUPS problem.

Note: I do have the new devx set to load at boot.

Thanks ...
[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

Dry Falls
Posts: 616
Joined: Tue 16 Dec 2014, 23:37
Location: Upper Columbia

delta

#23 Post by Dry Falls »

I was real careful to use the same original basefile as I uploaded, but I can be scatter-brained at times and may have used the wrong file. That said, I have seen that problem over and over again and just figured out yesterday that the delta file and original file have to be in different directories. I put the file I wanted to patch in a directory called, of all things, "orig". then the delta file outside (where there be no other file at all). Open the gui and drag the icons into the respective location fields. This is pretty basic, but no one has ever explained it to me. Anyway, it worked for me, and I'm running with it. If it's not operator error, then I obviously picked the wrong file to patch. Make sure your basefile is from the latest upload (do a midsum check) and get back to me. That way I can start over with the right patch for your file.

df

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

#24 Post by edoc »

The gdrive md5sum differed from my JL64-603.iso

I am downloading the current gdrive JL64-603.iso then will recheck the md5sum.

After that I'll replace the existing one and reboot the laptop.

That way we're using the same base iso.

Sound like a good plan?
[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

Dry Falls
Posts: 616
Joined: Tue 16 Dec 2014, 23:37
Location: Upper Columbia

#25 Post by Dry Falls »

the midsum is in the file at gdrive. Don't download again unless your sfs is NOT 5cef736b75c8420ad8d8036e449417b0. That's the one on the iso.

Unfortunately, my patch goes with 4036a0e8e9005b6540f3742cdca54ff1.

I'm going to have to make a new one.

df

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

#26 Post by edoc »

The JL64-603.iso I just downloaded shows a md5sum of:

Code: Select all

bash-4.1# md5sum JL64-603.iso
fc7b9efe18af7cf1b90a72a0aca5015d  JL64-603.iso
<root> /initrd/mnt/dev_save/savestuff/downloads/justlh64
bash-4.1# 
EDIT: That matches the md5sum on gdrive "fc7b9efe18af7cf1b90a72a0aca5015d JL64-603.iso"
[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

Dry Falls
Posts: 616
Joined: Tue 16 Dec 2014, 23:37
Location: Upper Columbia

#27 Post by Dry Falls »

that's the midsum of the iso. You need the number for the JL64-603.sfs. My numbers check out. That's the one I patched, for sure. Try it again. It could be that the patch itself was corrupted in the upload. It's midsum should be 866fffe956f821c7b17a4c2753b9da42.

df

edit, in case I wasn't clear, the delta is for the sfs file, not the iso image.

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

#28 Post by edoc »

This is from the first JL64-603.sfs from the iso that I had loaded on the laptop:

Code: Select all

bash-4.1# md5sum JL64-603.sfs     
820f9da8713c2c2a129d29bc1950814d  JL64-603.sfs
<root> /mnt/+mnt+home+savestuff+downloads+justlh64+JL64-603-old.iso
bash-4.1# 
This is from the JL64-603.sfs from the iso I more recently downloaded and updated to the laptop:

Code: Select all

bash-4.1# md5sum JL64-603.sfs     
4036a0e8e9005b6540f3742cdca54ff1  JL64-603.sfs
<root> /mnt/+mnt+home+savestuff+downloads+justlh64+JL64-603.iso
bash-4.1# 
This is the patch:

Code: Select all

bash-4.1# md5sum kdepatch-JL64-2-x86_64-PET.txz.gz
9301cc98f4d0aac1e2729486163a74e3  kdepatch-JL64-2-x86_64-PET.txz.gz
<root> /initrd/mnt/dev_save/savestuff/downloads/justlh64
bash-4.1# 
[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

Dry Falls
Posts: 616
Joined: Tue 16 Dec 2014, 23:37
Location: Upper Columbia

#29 Post by Dry Falls »

edoc wrote:This is the patch:

Code: Select all

bash-4.1# md5sum kdepatch-JL64-2-x86_64-PET.txz.gz
9301cc98f4d0aac1e2729486163a74e3  kdepatch-JL64-2-x86_64-PET.txz.gz
<root> /initrd/mnt/dev_save/savestuff/downloads/justlh64
bash-4.1# 

Code: Select all

[?]kdepatch-JL64-2-x86_64-PET.txz.gz[/?]
That is a .txz file which adds a few minor (cosmetic) changes to desktop configuration (where windows appear). What we were talking about is the delta file

Code: Select all

JL64-603.sfs___JL64-603.sfs.delta
It should have the mdsum

Code: Select all

866fffe956f821c7b17a4c2753b9da42
That's what you use the Delta file gui (menu/utility/xdelta file difference manager) on. It only works for delta files. An 8.49M file will transform the base file just means I don't need to use up 700M+ of my satellite quota every time I make a little change and Mr. Google Warbucks and his buddies over at Global Commmunication Amalgamated don't get quite the dividend trading non-tangible commodities like bandwidth usages at Walmart, er, Walstreet like it was a friggin video horserace.

df

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

#30 Post by edoc »

I'm still blaming my inattention to detail on the hot weather here in SE-central GA, USA ...

Code: Select all

bash-4.1#  md5sum JL64-603.sfs___JL64-603.sfs.delta
866fffe956f821c7b17a4c2753b9da42  JL64-603.sfs___JL64-603.sfs.delta
<root> /initrd/mnt/dev_save/savestuff/downloads/justlh64
bash-4.1# 
[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

Fishy
Posts: 234
Joined: Fri 27 Jan 2006, 01:22

Up-todate

#31 Post by Fishy »

Colour me clueless but is the iso on the g-drive up todate with all patches installed? :oops:

Dry Falls
Posts: 616
Joined: Tue 16 Dec 2014, 23:37
Location: Upper Columbia

Re: Up-todate

#32 Post by Dry Falls »

Fishy wrote:is the iso on the g-drive up todate with all patches installed?
No such color, or it's the one universal colour.
The iso is unpatched.

df.

ps, "Patch" is one of those multiple entendre words easily confused if we're too highly trained. I use the word in its most generic sense, like the artificial birthmark on the right side of an 18th century french aristocrat's face when staring in the mirror, but transfigured to the left when facing the public, ever fearing appearing on the wrong page (or thread if there's a taylor about).

Dry Falls
Posts: 616
Joined: Tue 16 Dec 2014, 23:37
Location: Upper Columbia

Delta2

#33 Post by Dry Falls »

The last delta file

Code: Select all

JL64-603.sfs___JL64-603.sfs.delta
md5 checksum: 6f306551dc49acd16843a11a66ffad25
is uploaded to replace the former. It is 19.6M and contains all the previous patches and fixes. It is to be applied to JL64-603.sfs which is on the iso. The new initrd.xz file should as well replace the one on the iso.

df

Fishy
Posts: 234
Joined: Fri 27 Jan 2006, 01:22

Boot Issue

#34 Post by Fishy »

Md5sum correct but all boot attempts stop at cannot find JL64-603.sfs. The same thing happened when I tried 602. Nice boot screen which goes to load drivers and then stops. The sfs requested is on the cd (burned with Burniso2cd). Fatdog64 and Tahr Ce all work fine on my box.

thanks

Dry Falls
Posts: 616
Joined: Tue 16 Dec 2014, 23:37
Location: Upper Columbia

#35 Post by Dry Falls »

@Fishy: So it sounds like you did a remaster with the patch applied. Did you boot uefi (grub2) or legacy (isolinux)? at the boot menu screen, you need to specify pmedia=cd* (or pmedia=usbflash if you you're booting from a usb stick). On grub.cfg, that would be menu entry 3 (or 3b for usb). Otherwise, it will search the drive/partitions for JL64-603.sfs.

With isolinux.cfg, there is a mistake on line 54. It should read "append pmedia=cd pfix=ram,copy" instead of cd/dvd. Sorry about that. Here are the specified parameters for pmedia:
Type of media booting from. Choose one of these:
usbflash usbhd usbcd ataflash atahd atacd atazip scsihd scsicd cd

*Lighthouse treats cd & dvd the same, so if you're booting off a dvd, it's still pmedia=cd.

Fishy
Posts: 234
Joined: Fri 27 Jan 2006, 01:22

#36 Post by Fishy »

Nope just burnt iso to cd like all others. Prefer to keep things simple which is why I use Puppy. Sorry, but if I cannot boot staight from cd or dvd it is not of use to me. In the past I used Lighthouse pup without any problems.

Good luck and thanks for the effort.

Dry Falls
Posts: 616
Joined: Tue 16 Dec 2014, 23:37
Location: Upper Columbia

#37 Post by Dry Falls »

@fishy: are you saying you don't use menu options? Just want everything automatic and given? Then this distro is definitely not for you. Sorry to waste your time.

df

gcmartin

#38 Post by gcmartin »

WHat @Fishy describes is the SAME phenomenon I have booting JLH on some BIOS PCs I have (not my UEFI model). I think I reported this earlier, too. It is PC configuration dependent issue as the same DVD boots on other PCs I have. It drops out of boot immediately, with a message in RED, after it has searched for "... usb ... Done". (And, yes, my checksum (md5) matches for both downloads and DVD creation.) Its something that has been introduced but I am unsure how to trap and report the boot time problem for developer review. Selecting Prompt is not the way because it occurs when trying to load the system's SFS. Any Ideas to help isolate this?

Service Delta
For DVD users, like myself, what is the recommended method for the Delta so that the service is maintained across "save-session-reboots"?

Dry Falls
Posts: 616
Joined: Tue 16 Dec 2014, 23:37
Location: Upper Columbia

#39 Post by Dry Falls »

For DVD users, like myself, what is the recommended method for the Delta so that the service is maintained across "save-session-reboots"?
Delta file should, it seems to me, only be useful with a frugal install (to rebuild the base sfs file). Then you can make a new iso to burn a new dvd with lighthouse remaster.

If Lighthouse or Mariner (the originals) booted correctly on 'pre-uefi' equipment, I don't know what could be the problem, as I've changed or introduced nothing in that department. Tell me, was there a similar problem with k3.18.8 or earlier? Because I don't remember the problem being reported. That kernel package is still at gdrive. If I had an older 64bit machine, I could experiment. If someone would like to try this test, don't forget to swap the kernel modules inside initrd.xz.

If it's not a kernel issue, I can't imagine what it would be.

df

gcmartin

#40 Post by gcmartin »

Dry Falls wrote:... If it's not a kernel issue, ...
I'm inclined to agree with you. Has to be something in there as by the time the system gets around to loading the main SFS, it has lost its ability to find it on the DVD.

Again, this only happens on selected platforms, not the others. The DVD does boot on the others finding all of its resources needed for booting. (Please remember that this problem is totally different from the problem I reported where loop occurs prior to desktop.) So this makes the problem unique to ONLY that class/model of PCs.

And, your question on earlier LH booting on the system in question, yes it always did. Now, I just need to figure out which of the 5 PCs I ran into that problem. hummm???

Edit: I just found it. It is still sitting on the screen where the abort occurs. It is an Acer desktop X2 with 2 GB RAM and a DVD writer. It is sitting at a prompt.

Is there any commands that you feel would yield useful information that I can gather at its current prompt (Remember, the RED message "JLH64-603.sfs is not found. Dropping out to initial-ramdisk console...") which anyone feels would be helpful???

I have used the same DVD on my UEFI PC without problems seen on other BIOS PCs.

Edit#2: I just did

Code: Select all

# uname -a
Linux (none) 4.0.1-JL-64 #1 SMP Sat May 2 11:23:52 PDT ...
Edit#3: Same result. same uname report.

Edit#4: Used a JLH DVD I have dated May 20th. Same problem and same uname report

Edit#4: Used a JLH DVD I have dated Feb 28th. WORKS!

Code: Select all

bash-4.1# uname -a
Linux Mariner15897 3.18.5-64 #4 SMP Fri Feb 27 04:49:10 PST 2015 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ AuthenticAMD GNU/Linux
Last edited by gcmartin on Wed 24 Jun 2015, 21:56, edited 3 times in total.

Post Reply