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 Tue 25 Jun 2019, 06:30
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
Xenialpup64 CE 7.5 / 25 Nov 2017
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 21 of 56 [829 Posts]   Goto page: Previous 1, 2, 3, ..., 19, 20, 21, 22, 23, ..., 54, 55, 56 Next
Author Message
rek769


Joined: 15 Jul 2010
Posts: 80

PostPosted: Wed 21 Jun 2017, 11:44    Post subject: XenPup64 boot issue
Subject description: Issue booting from CD
 

Now that XP64 is working well for me and is setup the way I want it, I have decided to boot the system from CD rather than the dd-ed flash drive I had been using.

When booting from CD, I keep my savefile inside a directory on my hard drive (1 level deep). This method has worked well for me since the Lucid days. However, I've found that when booting from the CD with XP64 that my savefile is not automatically discovered.

In order to force it to find my save file I had to add this to the isolinux.cfg file, remaster, and then re-burn the CD: psubdir=xenial_64
(where xenial_64 is the name of the subdirectory on my hard drive that contains my savefile.)

I've never had to take this step before and wanted to let it be known that this may be an issue.

Thanks
Back to top
View user's profile Send private message 
Lassar

Joined: 08 Jul 2014
Posts: 229

PostPosted: Wed 21 Jun 2017, 19:47    Post subject: Kodi not updating well on xenialpup64  

I have found that kodi will update okay on xenialpup 32 bit.

But on xenialpup 64 bit, it will fail.

Now in order to see this error, install creation.org, then update from local cache.

Then upate from the creation.org repository.

Now all updates will fail.

I took a look at DISTRO_PKGS_SPECS-ubuntu-xenial, but am not familiar enough with the differences between xenial 64 & xenial 32 bit, to be able to guess, at what causes this error.

Xenial 32 has pwsget & xenial64 doesn't, but I really doubt that causes the error.

.
Back to top
View user's profile Send private message 
rcrsn51


Joined: 05 Sep 2006
Posts: 12627
Location: Stratford, Ontario

PostPosted: Wed 21 Jun 2017, 20:15    Post subject: Re: XenPup64 boot issue
Subject description: Issue booting from CD
 

rek769 wrote:
I've never had to take this step before and wanted to let it be known that this may be an issue.

This sounds familiar. There may have been a deliberate change to the init system that limits how deeply Puppy will look for its savefile.
Back to top
View user's profile Send private message 
Lassar

Joined: 08 Jul 2014
Posts: 229

PostPosted: Wed 21 Jun 2017, 20:59    Post subject: Why is libLLVM-3.8.so.1 in puppy linux?  

For kodipup lite, I had been looking for stuff to cut out.

A prime candidate is libLLVM-3.8.so.1, coming in at 42 megabytes.

From what I read, this library is for compiler related stuff.

Why does a normal puppy even need this?

Should this not go into devx_xenialpup64_7.0.8.5.sfs, instead?

If parts of this library is needed, I bet it could be edited, and recompiled, and made into a pet.

Come on, 42 megabytes for a library!
Back to top
View user's profile Send private message 
peebee


Joined: 21 Sep 2008
Posts: 3892
Location: Worcestershire, UK

PostPosted: Thu 22 Jun 2017, 01:59    Post subject: Re: Why is libLLVM-3.8.so.1 in puppy linux?  

Lassar wrote:
For kodipup lite, I had been looking for stuff to cut out.

A prime candidate is libLLVM-3.8.so.1, coming in at 42 megabytes.

From what I read, this library is for compiler related stuff.

Why does a normal puppy even need this?

Should this not go into devx_xenialpup64_7.0.8.5.sfs, instead?

If parts of this library is needed, I bet it could be edited, and recompiled, and made into a pet.

Come on, 42 megabytes for a library!

It's needed for video drivers....
It is cut down in 2createpackages by it's package-template llvm-cut - but its entry in DISTRO_PKGS_SPECS-slackware-** must be called llvm-cut....

_________________
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPup, ScPup & ScPup64, LxPup, LxPupSc and LxPupSc64
Back to top
View user's profile Send private message Visit poster's website 
Lassar

Joined: 08 Jul 2014
Posts: 229

PostPosted: Sun 25 Jun 2017, 10:32    Post subject: Re: Why is libLLVM-3.8.so.1 in puppy linux?  

peebee wrote:

It is cut down in 2createpackages by it's package-template llvm-cut - but its entry in DISTRO_PKGS_SPECS-slackware-** must be called llvm-cut....


Could you expand on this in a little more detail?
Back to top
View user's profile Send private message 
Sailor Enceladus

Joined: 22 Feb 2016
Posts: 1555

PostPosted: Sun 25 Jun 2017, 11:40    Post subject:  

@Lassar: Try deleting the file(s) /usr/lib/libLLVM*, then running this in the terminal:

Quote:
checkdeps /

A few minutes later, you should get something like what I got in Slacko 6.9.9.9:

Code:
/usr/lib/d3d/d3dadapter9.so.1.0.0
   libLLVM-3.8.so => not found

/usr/lib/dri/gallium_drv_video.so
   libLLVM-3.8.so => not found

/usr/lib/libLTO.so
   libLLVM-3.8.so => not found

/usr/lib/libXvMCnouveau.so.1.0.0
   libLLVM-3.8.so => not found

/usr/lib/libXvMCr600.so.1.0.0
   libLLVM-3.8.so => not found

/usr/lib/libxatracker.so.2.3.0
   libLLVM-3.8.so => not found

/usr/lib/vdpau/libvdpau_nouveau.so.1.0.0
   libLLVM-3.8.so => not found

/usr/lib/vdpau/libvdpau_r300.so.1.0.0
   libLLVM-3.8.so => not found

/usr/lib/vdpau/libvdpau_r600.so.1.0.0
   libLLVM-3.8.so => not found

/usr/lib/vdpau/libvdpau_radeonsi.so.1.0.0
   libLLVM-3.8.so => not found

/usr/lib/xorg/modules/dri/kms_swrast_dri.so
   libLLVM-3.8.so => not found

/usr/lib/xorg/modules/dri/nouveau_dri.so
   libLLVM-3.8.so => not found

/usr/lib/xorg/modules/dri/r300_dri.so
   libLLVM-3.8.so => not found

/usr/lib/xorg/modules/dri/r600_dri.so
   libLLVM-3.8.so => not found

/usr/lib/xorg/modules/dri/radeonsi_dri.so
   libLLVM-3.8.so => not found

/usr/lib/xorg/modules/dri/swrast_dri.so
   libLLVM-3.8.so => not found

/usr/lib/xorg/modules/dri/vmwgfx_dri.so
   libLLVM-3.8.so => not found

/usr/lib/xorg/modules/drivers/vmware_drv.so
   libLLVM-3.8.so => not found
   libLLVM-3.8.so => not found

I think if you delete libLLVM-3.8.so, you can also delete all these drivers since they won't work properly any more (I could be wrong though). I didn't seem to need libLLVM-3.8 or any of those drivers on the 3 older computers I tried, so a pet might work.
Back to top
View user's profile Send private message 
peebee


Joined: 21 Sep 2008
Posts: 3892
Location: Worcestershire, UK

PostPosted: Sun 25 Jun 2017, 12:23    Post subject: Re: Why is libLLVM-3.8.so.1 in puppy linux?  

Lassar wrote:
peebee wrote:

It is cut down in 2createpackages by it's package-template llvm-cut - but its entry in DISTRO_PKGS_SPECS-slackware-** must be called llvm-cut....

Could you expand on this in a little more detail?

Look in:
woof-out_***/packages-templates/llvm-cut

or on github:
https://github.com/puppylinux-woof-CE/woof-CE/tree/testing/woof-code/packages-templates/llvm-cut

entry in DISTRO_PKGS_SPECS should be:
yes|llvm-cut|llvm|exe,dev>null,doc,nls

_________________
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPup, ScPup & ScPup64, LxPup, LxPupSc and LxPupSc64
Back to top
View user's profile Send private message Visit poster's website 
slenkar

Joined: 10 Jul 2009
Posts: 228

PostPosted: Mon 26 Jun 2017, 11:12    Post subject:  

how does one install opera on xenial64?

Doesnt seem to be in repo.
.deb from the website doesnt seem to do anything.
Back to top
View user's profile Send private message 
riedzig

Joined: 01 Oct 2015
Posts: 36

PostPosted: Tue 27 Jun 2017, 01:18    Post subject:  

If you mean the new Opera 46, download the .rpm file from opera.com, extract it and just run /usr/bin/opera
Back to top
View user's profile Send private message 
bigpup


Joined: 11 Oct 2009
Posts: 12234
Location: S.C. USA

PostPosted: Tue 27 Jun 2017, 02:12    Post subject:  

slenkar wrote:
how does one install opera on xenial64?

Doesn't seem to be in repo.
.deb from the website doesn't seem to do anything.

If you downloaded the .deb and left clicked on it to install.
It may not have made any menu entries.
Open a console/terminal.
Type:
Code:
opera


If it does not run.
What do you get for errors?

_________________
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected Shocked
YaPI(any iso installer) http://www.murga-linux.com/puppy/viewtopic.php?t=107601
Back to top
View user's profile Send private message 
slenkar

Joined: 10 Jul 2009
Posts: 228

PostPosted: Wed 28 Jun 2017, 13:27    Post subject:  

I installed opera-stable_46_amd64.deb

when typing opera into the terminal it says it doesnt exist,
also cant find it in usr/bin or with a file search

do you want me to try the .rpm file?
Back to top
View user's profile Send private message 
mikeslr


Joined: 16 Jun 2008
Posts: 3165
Location: 500 seconds from Sol

PostPosted: Wed 28 Jun 2017, 20:13    Post subject: Opera: Ubuntu-based 64bit OSes can't find x86_64-linux-gnu  

Hi slenkar,

deb, rpm - same difference. Rolling Eyes Both these packages are designed for an operating system which is truly multi-architecture. Puppies built from Ubuntu binaries aren't. When you install or unpack debs or rpms, you'll find that they locate some lib files in /usr/lib/x86_64-linux-gnu and/or /usr/local/lib/x86_64-linux-gnu. Puppies can't find those libs. The workaround is to unpack the deb or rpm and move those libs to /usr/lib or usr/local lib, respectively.

I run opera from /mnt/home where I unpacked, I think, the package ending in tar.gz or tgz. To run it, I installed a "handmade" pet. [I may want to upgrade or use it from another Puppy]. But you can skip the pet creation part and simply include its 3 files. One is just an opera icon (png) which I placed in /usr/share/pixmaps. The second was a desktop file placed in /usr/share/applications --this creates a menu listing. Mine, named opera.desktop, reads:

[Desktop Entry]
Encoding=UTF-8
Name=Opera64 web browser
Icon=/usr/share/pixmaps/opera.png
Comment=Opera from /mnt/home/Pup-Apps
Exec=/root/my-applications/bin/opera64
Terminal=false
Type=Application
Categories=X-Internet
GenericName=Opera web browser

Note the Exec argument. Puppy expects executables/binaries to be "on the Path" -- which means within any "bin" or "sbin" folder. The one in /root/my-applications/ was especially constructed for, and is peculiar to, Puppies. A more common location in Linux would be /usr/local/bin.

The Exec argument points to the third file. It's a bash script "on the path". You create them by right-clicking an empty space and selecting New>script, and giving it a name such as opera64. You then open it in geany/text editor

Mine reads:

#!/bin/sh
exec /mnt/home/Pup-Apps/opera64/usr/lib/x86_64-linux-gnu/opera/opera "$@"

The first line is created for you. The second you have to do yourself, being careful to accurately point to the executable --the last "opera" of the line-- by providing the entire path, properly spelled. Exec says its an executable; and my guess is that somehow "$@" got to mean "do it". Cool After creating the script, make sure it's executable. Right-Click it, select "Properties" and make certain all the boxes in the Exec column are checked.

You can unpack the tgz/deb/rpm anywhere. A common place is /opt. That's where Chrome and its clones folders are found. But be sure that the bash script accurately point to wherever the executable will be found.

Since all other files relating to opera are within one folder --that named opera-- Puppies don't have to search far and can find all the libs.

But an easier solution is to use either the pet or sfs Mike Walsh built of Iron. You'll find them here: https://yadi.sk/d/_S5b4g7tpcyZn. Take it from a long-time opera fan. It's just a better program.

mikesLr

Last edited by mikeslr on Fri 30 Jun 2017, 19:03; edited 2 times in total
Back to top
View user's profile Send private message 
slenkar

Joined: 10 Jul 2009
Posts: 228

PostPosted: Wed 28 Jun 2017, 23:10    Post subject:  

i unpacked the deb as per your suggestion and found all those files that failed to install, then i was able to create the menu item
thanks!
Back to top
View user's profile Send private message 
Lassar

Joined: 08 Jul 2014
Posts: 229

PostPosted: Fri 30 Jun 2017, 17:50    Post subject:  Found a bug in xenialpup64  

In my quest, to get kodi to handle addon updates, in xenialpup64, I found a bug.

What made me suspicious, is I got updates to work, after creating a new folder, and copying the guts of the .kodi folder into it.

Deleted the old .kodi folder, and rename the new folder to .kodi.

After I did this, addon updates would work.

In researching this problem, I found a web page, that says file attributes do not copy over, from the source to target.

Which explains, why the copying, from the .kodi folder to the new folder worked.

I went to the terminal and typed lsattr /root.

I got "Inappropriate ioctl for device While reading flags on ..." every file and folder as far as I can tell.

Xenialpup64 cannot handle lsattr, and I bet chattr either.

Definitely a bug.
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 21 of 56 [829 Posts]   Goto page: Previous 1, 2, 3, ..., 19, 20, 21, 22, 23, ..., 54, 55, 56 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Projects
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.1045s ][ Queries: 13 (0.0369s) ][ GZIP on ]