Just-Lighthouse64-603/604

[edoc]

I ran '/etc/cups/resetCUPS'

Then I rebooted to reset the save file.

The printer was still there but despite the same error - this time it allowed me to print a Test Page.

It also allowed me to print the CUPS page.

And it allowed me to change the Share Printer setting in Administration.

However, I now get a "Getting printer information failed" error on another laptop that has been working fine.

Do I need to reboot this other laptop and/or run "/etc/cups/resetCUPS" on it as well?

NOTE1: CUPS Administration can't access the printer settings for the Brother printer on this other laptop - so I cannot delete and re-add it. If I run "/etc/cups/resetCUPS" on this machine will it mess up the settings on the other one - where I just got printing working? (CUPS has always mystified me.)

NOTE2: The printer is connected to the USB port of an ASUS router and has worked fine across multiple wifi connected laptops in the past. (Just to eliminate the ASUS router as the source of the problem.)

Thanks ...

[edoc]

Everything was powered-down for the night - powered up JLH-64 laptop with printer working first, then this one with the error message, and though the error (re. unable to get printer) popped up - this time it disappeared and now allows me to print.

Mark this one SOLVED.

[Dry Falls]

JL64-603 Release notes added to opening post

df

[stemsee]

* SFS files are for the time being only available at g-drive and only downloadable via browser or Stemsee's 'nluug-get'

nluug-get and gdrive-get are the work of fredx181 (DebianDog developer).
I only packaged them for puppy, and provided a few ideas and two lines of code to improve user experience.

[Dry Falls]

I've added a delta-patch to gdrive:

JL64-603.sfs___JL64-603.sfs.delta ... size=8.46M

available in the upload directory, 'JL64-603( Just-Lighthouse64)', in the opening post. This fixes a problem with udev & glib solibs. Also there is new Devx64-603 with corresponding changes.

df

[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

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

[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

[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?

[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

[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"

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

[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# 

[Dry Falls]

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

[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# 

[Fishy]

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

[Dry Falls]

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]

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]

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]

@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.