Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Sat 07 Dec 2019, 23:58
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Derivatives
Bionic32-light - 27 April, 2019
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 3 of 8 [117 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6, 7, 8 Next
Author Message
davids45


Joined: 26 Nov 2006
Posts: 1237
Location: Chatswood, NSW

PostPosted: Sun 28 Apr 2019, 23:44    Post subject: CUPS now works!!
Subject description: Two sips of Canuck magic needed
 

G'day jrb,

Thanks for the Light ghostscript pet. I tried it in a quickly knocked-up TESTING-Bionic32Light Frugal, first adding some possibly needed library file links:

in /usr/lib, libtiff.so.5.3.0 - two links made to it, libtiff.so.4 and libtiff.so.3 (the '4' for my scanner, the '3' you had suggested in an earlier post)

lib-ld-2.27 - link to this file in /lib needed for printing is ld-lsb.so.3 (or whatever the numbers are after the 'lib-ld-' - this varies from Pup/kernel to Pup/kernel but I need for my Epson printers in virtually every Pup)

Then I installed your ghostscript pet and ran CUPS.....
... but still no good Crying or Very sad Confused .

I vaguely recalled an old problem like this and scrabbling through my Printers archive directory, I found two files provided by rcrsn51 a few years ago which had worked to fix a problem back then.
Another ghostscript pet (~6MB) and a gstoraster pet (~10k) [- full title gstoraster_533-9.0.5.pet, dated 2013].
Installing both these (over the top of your small pet) and printing now worked!

Remembering my post above mentioning "great minds and fools", and being no angel, I rushed in and restarted my TESTING-Bionic32Light Frugal anew but this time installed just your ghostscript pet and rcrsn51's gstoraster pet.

CUPS still worked with my networked Epson Very Happy .
A Light solution to my printing problem.

Thanks to both of you Canadian wizards.

David S.
Back to top
View user's profile Send private message 
jrb


Joined: 11 Dec 2007
Posts: 1324
Location: Smithers, BC, Canada

PostPosted: Mon 29 Apr 2019, 09:04    Post subject: Re: CUPS now works!!
Subject description: Two sips of Canuck magic needed
 

davids45 wrote:
G'day jrb,

Thanks for the Light ghostscript pet. I tried it in a quickly knocked-up TESTING-Bionic32Light Frugal, first adding some possibly needed library file links:

in /usr/lib, libtiff.so.5.3.0 - two links made to it, libtiff.so.4 and libtiff.so.3 (the '4' for my scanner, the '3' you had suggested in an earlier post)

lib-ld-2.27 - link to this file in /lib needed for printing is ld-lsb.so.3 (or whatever the numbers are after the 'lib-ld-' - this varies from Pup/kernel to Pup/kernel but I need for my Epson printers in virtually every Pup)

Then I installed your ghostscript pet and ran CUPS.....
... but still no good Crying or Very sad Confused .

I vaguely recalled an old problem like this and scrabbling through my Printers archive directory, I found two files provided by rcrsn51 a few years ago which had worked to fix a problem back then.
Another ghostscript pet (~6MB) and a gstoraster pet (~10k) [- full title gstoraster_533-9.0.5.pet, dated 2013].
Installing both these (over the top of your small pet) and printing now worked!

Remembering my post above mentioning "great minds and fools", and being no angel, I rushed in and restarted my TESTING-Bionic32Light Frugal anew but this time installed just your ghostscript pet and rcrsn51's gstoraster pet.

CUPS still worked with my networked Epson Very Happy .
A Light solution to my printing problem.

Thanks to both of you Canadian wizards.

David S.

Well Done! Would this be worth including in an update? That is to say, is this a general fix? If so could you write a sequential list of your fixes.

I found gstoraster_s533-9.05.pet.

Also, I'd like a bit more detail on the lib-ld-2.27 link. How do you decide what is needed.
Back to top
View user's profile Send private message 
jrb


Joined: 11 Dec 2007
Posts: 1324
Location: Smithers, BC, Canada

PostPosted: Mon 29 Apr 2019, 09:56    Post subject: Re: Bionic32-light
Subject description: A radically minimized modern OS
 

sheldonisaac wrote:
I need help with getting PUPMODE=13
which works in other Puppys, including Precise Light.

But this Bionic32-light makes pupmode of 5
Code:
 kernel /upbblt/vmlinuz  pdrv=d58c24e4-7a41-4cb7-be6d-08c83a6e2105 pmedia=ataflash psubdir=/upbblt pfix=fsck

Problem located and, kludged. Rolling Eyes There is something amiss in initrd.gz. I substituted in Peebee's initrd.gz from bionicpup32-8.0+3-uefi.iso and your kernel line (with my folder name and uuid) booted to "PUPMODE=13".

You can go ahead and do that substitution if you wish but I will post an ISO update once @davids45 gets back to me about his printer fix.

Cheers, J

Edit: Problem found on line 1256 of init in init.gz, will definitely be updated.

Last edited by jrb on Mon 29 Apr 2019, 11:34; edited 1 time in total
Back to top
View user's profile Send private message 
jrb


Joined: 11 Dec 2007
Posts: 1324
Location: Smithers, BC, Canada

PostPosted: Mon 29 Apr 2019, 10:05    Post subject:  

musher0 wrote:
Hi jrb and all.

Some more testing of Bionic32-light reveals that...

- exchange between the CLI and GUI buffers is awful! It simply does not
work between leafpad and the terminal. Not even Shift-Delete and
Shift-Insert work.

Please find attached an xsel pet archive as an attempt to improve this
situation. I've seen this before, though, in DPupBuster. A solution was
provided in that thread, IIRC; it consisted of adding a udev rule or similar
somewhere in /usr/share/X11.

-- use of lxterminal is awful too (!), not to mention confusing for anyone
used to urxvt. Please replace the defaultterminal file at /usr/local/bin with
this real Wink one:
Code:

#!/bin/sh
# defaultterminal
####
exec urxvt -sr -tr -tint NavajoWhite4 -sh 50 -b 20
# lxterminal "$@"

-- the ever useful replaceit utility is absent. Included as attachment.

IHTH.

Hi musher, Can you give specific examples of these problems for me to try? That way I can do before and after testing with the fixes recommended. And maybe a link to the discussion in DPupBuster?
Back to top
View user's profile Send private message 
musher0

Joined: 04 Jan 2009
Posts: 14526
Location: Gatineau (Qc), Canada

PostPosted: Mon 29 Apr 2019, 11:23    Post subject:  

Hi jrb.

Thanks for your reply.

I should have turned my "pencil" seven times in my hand before writing
about reaction of the CLI buffers. I remember now: it has to do with my
using a track ball instead of a mouse. And because X has changed.

Sorry for the false alarm.

As I think I mentioned earlier, there is a udev script I have to add to
regain use of my middle click for buffering. It's in the DPupBuster thread
somewhere. When I find it, I'll put a link here: many people use a track
ball instead of a regular mouse, it seems.

~~~~~~~~

On the ICU front, I spent several hours yesterday evening compiling the
new version of ICU. In their doc they recognize that their libraries are big
and explain how to reduce their size.

I succeeded in compiling a static ICU with "files" instead of dynamic "so"
libraries, and without the collation and the older character conversions.

So I remove your icu package through ppm and try to install my new one.

Did you know that gtkdialog and ROX-Filer are compiled against the
dynamic version of ICU (the common "so" libraries). Also the ICU libs
being compiled with their version number as suffix, the apps require that
particular version of ICU compiled dynamically and no other. (Not sure if
that is clever.)

Anyway, petget didn't work, to install the new version of ICU!

Interestingly, though, the size of this static-with-files ICU is 12 Mb in total,
not the usual 33 Mg or thereabouts. (Zipped tree attached.)

So there's fish there! More about this later.

BFN.
ICU-static+files.zip
Description 
zip

 Download 
Filename  ICU-static+files.zip 
Filesize  1.79 KB 
Downloaded  120 Time(s) 

_________________
musher0
~~~~~~~~~~
Je suis né pour aimer et non pas pour haïr. (Sophocle) /
I was born to love and not to hate. (Sophocles)
Back to top
View user's profile Send private message 
jrb


Joined: 11 Dec 2007
Posts: 1324
Location: Smithers, BC, Canada

PostPosted: Mon 29 Apr 2019, 12:01    Post subject:  

musher0 wrote:
On the ICU front, I spent several hours yesterday evening compiling the new version of ICU. In their doc they recognize that their libraries are big and explain how to reduce their size.

I succeeded in compiling a static ICU with "files" instead of dynamic "so"
libraries, and without the collation and the older character conversions.

So I remove your icu package through ppm and try to install my new one.

Did you know that gtkdialog and ROX-Filer are compiled against the
dynamic version of ICU (the common "so" libraries). Also the ICU libs
being compiled with their version number as suffix, the apps require that
particular version of ICU compiled dynamically and no other. (Not sure if
that is clever.)

Anyway, petget didn't work, to install the new version of ICU!

Interestingly, though, the size of this static-with-files ICU is 12 Mb in total,
not the usual 33 Mg or thereabouts. (Zipped tree attached.)

So there's fish there! More about this later.

BFN.

Congratulations on the compile, I'm impressed! As for the apps in bionic-light, since they work without ICU at all I suspect it is libxml2 that is the fussy one. I had to compile an older version with no dependence on ICU to get to a desktop. The apps seem happy with it although the copy function in rox sometimes seems very slow. I'm wondering if your comment, "exchange between the CLI and GUI buffers is awful!" may be the key.

I have in the past used patchelf to modify the dependencies of binaries. They're not always set in stone.

edit: changed "readelf" to "patchelf"

Last edited by jrb on Mon 29 Apr 2019, 12:30; edited 1 time in total
Back to top
View user's profile Send private message 
musher0

Joined: 04 Jan 2009
Posts: 14526
Location: Gatineau (Qc), Canada

PostPosted: Mon 29 Apr 2019, 12:06    Post subject:  

Hello all.

The correction for Logitech Marble track ball users is here

However, the way to integrate it will differ in Bionic32-light. The main
difference is that the file already exists. It's at
/usr/share/X11/xorg.conf.d/10-evdev.conf.
You will have to either prepend or append the Marble trackball segment.

This reactivates the copy by middle click between CLI and GUI apps for
users having a Marble track ball.

IHTH.

_________________
musher0
~~~~~~~~~~
Je suis né pour aimer et non pas pour haïr. (Sophocle) /
I was born to love and not to hate. (Sophocles)

Last edited by musher0 on Tue 30 Apr 2019, 10:31; edited 3 times in total
Back to top
View user's profile Send private message 
musher0

Joined: 04 Jan 2009
Posts: 14526
Location: Gatineau (Qc), Canada

PostPosted: Mon 29 Apr 2019, 12:14    Post subject:  

Hi jrb.

Thanks for the reply.

You wrote:
Quote:
> since they work without ICU at all
Then, it's strange that when I un-installed the ICU pet you provided,
calling rox from CLI and gtkdialog stopped working. This ICU stuff is
very mysterious.

I double-checked the libxml and it was already in the upupbb-light.

BFN.

_________________
musher0
~~~~~~~~~~
Je suis né pour aimer et non pas pour haïr. (Sophocle) /
I was born to love and not to hate. (Sophocles)
Back to top
View user's profile Send private message 
jrb


Joined: 11 Dec 2007
Posts: 1324
Location: Smithers, BC, Canada

PostPosted: Mon 29 Apr 2019, 12:32    Post subject:  

musher0 wrote:
Hi jrb.

Thanks for the reply.

You wrote:
Quote:
> since they work without ICU at all
Then, it's strange that when I un-installed the ICU pet you provided,
calling rox from CLI and gtkdialog stopped working. This ICU stuff is
very mysterious.

I double-checked the libxml and it was already in the upupbb-light.

BFN.

Did you remember to uninstall the new libxml2 which I forgot to mention in my first post about the ICU .pet?
Back to top
View user's profile Send private message 
musher0

Joined: 04 Jan 2009
Posts: 14526
Location: Gatineau (Qc), Canada

PostPosted: Mon 29 Apr 2019, 16:00    Post subject:  

Hi jrb.

I hadn't installed libxml2, since it was already there.

~~~~~~~~

I had to restart from scratch. My new ICU libs probably prevented me from getting
to X ( to be investigated why ).

One thing I noticed, working on ICU, is that your removal of ICU was not complete:
you still have ICU's unicode directory in /usr/include. Again to be instigated (I'm
talking somewhat through my hat here),
-- perhaps that explains why your removal of the ICU libs does not seem to have an
effect. But please don't remove this unicode dir!
-- I suspect the i18n at /usr/share may also play a compensating role.

So I created another pupsave and populated it a bit.

~~~~~~~~

On another subject, I can't live without the attached! I compiled the most recent
urxvt ( v. 9.22 as of this writing ) on and for your upupbb-light. The urxvt provided
in upupbb-light ex-factory is version 9.05 from 2008.

I compiled it with --enable-everything, which means it compiled against the
libperl.so.5.26.1 the upupbb-light is offering. Thus ready for any perl extension, and
it has the new fade and icon capabilities.

I need the recent urxvt because I have a number of scripts that make rather full use
of urxvt parameters. I've tried to base some scripts on lx-terminal a couple of times,
and it is not as malleable as urxvt. Lx-terminal has a much more limited set of
parameters; it cannot act as a pseudo-GUI like urxvt can.

To reassemble the three parts attached below, go to the download directory, open a
console there and type
Code:
cat xa*.pet > rxvt-unicode-9.22_upbbl.pet
Then double-click on the rxvt-unicode-9.22_upbbl.pet and the pet archive will
install as usual.

Of course you're under no obligation, jrb, but if users want it, it's here.

~~~~~~~~~~~~~~~

Finally, not having the traditional gtk-chtheme is a pain. Also attached.

IHTH.
xaa-rxvt-unicode-9.22_upbbl.pet
Description 
pet

 Download 
Filename  xaa-rxvt-unicode-9.22_upbbl.pet 
Filesize  225.57 KB 
Downloaded  138 Time(s) 
xab-rxvt-unicode-9.22_upbbl.pet
Description 
pet

 Download 
Filename  xab-rxvt-unicode-9.22_upbbl.pet 
Filesize  225.57 KB 
Downloaded  131 Time(s) 
xac-rxvt-unicode-9.22_upbbl.pet
Description 
pet

 Download 
Filename  xac-rxvt-unicode-9.22_upbbl.pet 
Filesize  225.57 KB 
Downloaded  129 Time(s) 
gtk-chtheme.zip
Description  Missing in upupbb-light. This is the one from your Precise-Light and it works fine in
your upupbb.
zip

 Download 
Filename  gtk-chtheme.zip 
Filesize  10.87 KB 
Downloaded  115 Time(s) 

_________________
musher0
~~~~~~~~~~
Je suis né pour aimer et non pas pour haïr. (Sophocle) /
I was born to love and not to hate. (Sophocles)

Last edited by musher0 on Mon 29 Apr 2019, 21:12; edited 1 time in total
Back to top
View user's profile Send private message 
sheldonisaac

Joined: 21 Jun 2009
Posts: 865
Location: Philadelphia, PA

PostPosted: Mon 29 Apr 2019, 17:38    Post subject: Re: Bionic32-light, a raTdically minimized modern OS
Subject description: The initrd.gz - pupmode problem
 

jrb (in part) wrote:
sheldonisaac wrote:
I need help with getting PUPMODE=13 which works in other Puppys, including Precise Light.

Problem located and, kludged. Rolling Eyes There is something amiss in initrd.gz. I substituted in Peebee's initrd.gz from bionicpup32-8.0+3-uefi.iso and your kernel line (with my folder name and uuid) booted to "PUPMODE=13".

You can go ahead and do that substitution if you wish but I will post an ISO update once @davids45 gets back to me about his printer fix.

Cheers, J

Edit: Problem found on line 1256 of init in init.gz, will definitely be updated.


Many thanks, jrb, for tracking it down! I'll just wait, no hurry at all.

Sheldon

_________________
Dell E6410: BusterPup, Ermine, Xenial, etc
Intel DQ35JOE, Dell Vostro 430
Dell Mini 9, Acer Aspire One, EeePC 1018P
Back to top
View user's profile Send private message 
davids45


Joined: 26 Nov 2006
Posts: 1237
Location: Chatswood, NSW

PostPosted: Mon 29 Apr 2019, 20:54    Post subject: Printing with CUPS & Epson
Subject description: Filter fail fix with /lib file link
 

G'day jrb,

I'm glad you located the pet of rcrsn51's gstoraster, despite my typo (too many decimal points in 905 Embarassed ).

Quote:
Also, I'd like a bit more detail on the lib-ld-2.27 link. How do you decide what is needed.


Sorry for my second typo in that post - it's just "ld-" not "lib-ld-" Embarassed Embarassed .

Again, years ago, I think rcrsn51's pets for installing Epson printers often included creating a link to add ld-lsb.so.3 (or earlier, ld-lsb.so.2) into Pups where this was missed by the Pup developer. Seems now to be missed in every new Pup Shocked .

This /lib/ld-lsb.so.3 link omission sees the Epson printer showing "Filter fail" when CUPS is opened after a failure to print.
Over the years, I've added this link manually for a series of my Epson printers across a wide range of Pups (I'm a bit of an Epson-fanboy/OAP). So far, it's always worked after a "Filter fail".

What does change often are the numbers at the end of the ld-file in /lib. It's usually the first file in /lib as it doesn't have the prefix 'lib-' so easy to find.

In this morning's Pup (Slacko-6.9.6.7 with a 3.16.43 kernel), it's ld-2.23.so.
Your Light Bionic has increased the ld- to ld-2.27.so
But so far, whatever the numbering, making the link "ld-lsb.so.3" to ld-x.xx.so has been OK - I'm waiting til ld-lsb.so.4 is needed Smile .

I'd welcome you adding the ghostscript+gstoraster files to your next Bionic32-Light, plus the /lib link - these are not going to "heavy-up" Light by much. And the libtiff links in /usr/lib/ too, of course.

Perhaps other owners/users of Epson printers and scanners could comment and test?

Thanks,
David S.
Back to top
View user's profile Send private message 
jrb


Joined: 11 Dec 2007
Posts: 1324
Location: Smithers, BC, Canada

PostPosted: Mon 29 Apr 2019, 23:38    Post subject: Re: Printing with CUPS & Epson
Subject description: Filter fail fix with /lib file link
 

davids45 wrote:
G'day jrb,

I'm glad you located the pet of rcrsn51's gstoraster, despite my typo (too many decimal points in 905 Embarassed ).

Quote:
Also, I'd like a bit more detail on the lib-ld-2.27 link. How do you decide what is needed.


Sorry for my second typo in that post - it's just "ld-" not "lib-ld-" Embarassed Embarassed .

Again, years ago, I think rcrsn51's pets for installing Epson printers often included creating a link to add ld-lsb.so.3 (or earlier, ld-lsb.so.2) into Pups where this was missed by the Pup developer. Seems now to be missed in every new Pup Shocked .

This /lib/ld-lsb.so.3 link omission sees the Epson printer showing "Filter fail" when CUPS is opened after a failure to print.
Over the years, I've added this link manually for a series of my Epson printers across a wide range of Pups (I'm a bit of an Epson-fanboy/OAP). So far, it's always worked after a "Filter fail".

What does change often are the numbers at the end of the ld-file in /lib. It's usually the first file in /lib as it doesn't have the prefix 'lib-' so easy to find.

In this morning's Pup (Slacko-6.9.6.7 with a 3.16.43 kernel), it's ld-2.23.so.
Your Light Bionic has increased the ld- to ld-2.27.so
But so far, whatever the numbering, making the link "ld-lsb.so.3" to ld-x.xx.so has been OK - I'm waiting til ld-lsb.so.4 is needed Smile .

I'd welcome you adding the ghostscript+gstoraster files to your next Bionic32-Light, plus the /lib link - these are not going to "heavy-up" Light by much. And the libtiff links in /usr/lib/ too, of course.

Perhaps other owners/users of Epson printers and scanners could comment and test?

Thanks,
David S.

Thanks David, I'm sure that there are other printers out there that will need this ghostscript, perhaps with tweaking, and gstoraster is tiny so no great burden. The fact you got it to work is an excellent indicator that it will work for others. Very Happy
Back to top
View user's profile Send private message 
Sage

Joined: 04 Oct 2005
Posts: 5501
Location: GB

PostPosted: Tue 30 Apr 2019, 04:07    Post subject:  

This light offering is a stroke of genius, in keeping with the original aims of Puppy. Staying with 32bit, sine qua non - it's LIGHT, and still works with 64bit, of course, worth mentioning only because that fact seems to evade many folks! Perfect for diagnosis, repair and demonstration. Did I say "It works", unlike some other bodged attempts at 'slim' versions. Certainly worth bug-squashing but avoid the siren voices that plague distrospace with requests for more, bigger, & co. - send them to major releases; wood-for-trees syndrome abounds.
Back to top
View user's profile Send private message 
musher0

Joined: 04 Jan 2009
Posts: 14526
Location: Gatineau (Qc), Canada

PostPosted: Tue 30 Apr 2019, 11:58    Post subject:  

Hi, jrb.

You may wish to replace mplayer with madplay to play the chime at boot.

mplayer sends 9.7 Kb of useless warnings to /tmp/xerrs.log, while madplay
sends none. Evidence attached.

The sound quality is equivalent.

IHTH
mplayer-issues-warnings-in-xerrs_log-at-boot.jpg
 Description   
 Filesize   226.85 KB
 Viewed   235 Time(s)

mplayer-issues-warnings-in-xerrs_log-at-boot.jpg

madplay-issues-none.jpg
 Description   
 Filesize   237.64 KB
 Viewed   232 Time(s)

madplay-issues-none.jpg


_________________
musher0
~~~~~~~~~~
Je suis né pour aimer et non pas pour haïr. (Sophocle) /
I was born to love and not to hate. (Sophocles)
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 3 of 8 [117 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6, 7, 8 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Derivatives
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.2196s ][ Queries: 12 (0.0203s) ][ GZIP on ]