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 Mon 20 Oct 2014, 08:04
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Derivatives
SlackBones x86_64
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 7 of 7 [103 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6, 7
Author Message
pemasu


Joined: 08 Jul 2009
Posts: 5463
Location: Finland

PostPosted: Fri 05 Jul 2013, 01:37    Post subject:  

Catdude. version.h missing is known problem with ati compiling. You need to manually patch the kernel sources by symlinking version.h from its newer location to the older location.

something like this:
ln -s /lib/modules/3.8.5.0/build/include/generated/uapi/linux/version.h /lib/modules/3.8.5.0/build/include/linux/version.h

just change the kernel version and other needed location descriptions so that actual version.h is symlinked to where the ati compiler expects it to be ie /include/linux/version.h

It can be that ati needs other patches also which you need to manually include into it after manually extracting ati package. It depends on kernel version and used ati package version.
Back to top
View user's profile Send private message 
Q5sys


Joined: 11 Dec 2008
Posts: 1073

PostPosted: Sat 06 Jul 2013, 00:03    Post subject:  

Thanks for the info pemasu!
_________________



Back to top
View user's profile Send private message Visit poster's website 
CatDude


Joined: 03 Jan 2007
Posts: 1484
Location: UK

PostPosted: Sat 06 Jul 2013, 02:55    Post subject:  

Hi

@ pemasu
pemasu wrote:
Catdude. version.h missing is known problem with ati compiling. You need to manually patch the kernel sources by symlinking version.h from its newer location to the older location.

something like this:
ln -s /lib/modules/3.8.5.0/build/include/generated/uapi/linux/version.h /lib/modules/3.8.5.0/build/include/linux/version.h

just change the kernel version and other needed location descriptions so that actual version.h is symlinked to where the ati compiler expects it to be ie /include/linux/version.h

Thanks, but i had already done that after reading this post of your's

pemasu wrote:
It can be that ati needs other patches also which you need to manually include into it after manually extracting ati package. It depends on kernel version and used ati package version.

OK, I found these patches catalyst-patch-3.8-legacy.tar.gz which you posted here
and applied them all except for the arch-fglrx-3.8.patch (i assumed i did not require it)
After applying those, i was able to create a slackware package. Very Happy

For future reference, could you please explain the correct method of applying those patches. Question

@ Q5sys
Q5sys wrote:
What you could do is install strace from the slackware repo and have that output to a file when you run the ATI run file.
Then post that and I may be able to find out what's not being found.
I'd need to know what tools are missing to be able to provide them for you.

Thank you for the suggestion,
prior to applying the patches mentioned above, i did as you suggested and installed strace
but i didn't really know what to do with it, so i ran it like this:
Code:
strace -o /root/strace-ati-log.txt sh amd-driver-installer-catalyst-13.1-legacy-linux-x86.x86_64.run

which resulted in 1000 plus lines of complete gobbledegook. Rolling Eyes

Was that command correct, or should i have used something different (could you provide an example)
also do you have any decent links that explain what the output means.

So, we can say that my initial problem is solved,
but.... how did simply applying some patches miraculously resolve those 'missing tools' Question


Once again, thanks to you both
CatDude

P.S
Any progress on v2.0 Question

.

_________________

Back to top
View user's profile Send private message 
smokey01


Joined: 30 Dec 2006
Posts: 1828
Location: South Australia

PostPosted: Sat 06 Jul 2013, 09:10    Post subject:  

Q5sys is there any way to increase the personal storage file in slackbones?

Thanks

_________________
Puppy Software <-> Distros <-> Puppy Linux Tips
Back to top
View user's profile Send private message Visit poster's website 
Q5sys


Joined: 11 Dec 2008
Posts: 1073

PostPosted: Sat 06 Jul 2013, 11:49    Post subject:  

CatDude wrote:

@ Q5sys
Q5sys wrote:
What you could do is install strace from the slackware repo and have that output to a file when you run the ATI run file.
Then post that and I may be able to find out what's not being found.
I'd need to know what tools are missing to be able to provide them for you.

Thank you for the suggestion,
prior to applying the patches mentioned above, i did as you suggested and installed strace
but i didn't really know what to do with it, so i ran it like this:
Code:
strace -o /root/strace-ati-log.txt sh amd-driver-installer-catalyst-13.1-legacy-linux-x86.x86_64.run

which resulted in 1000 plus lines of complete gobbledegook. Rolling Eyes

Was that command correct, or should i have used something different (could you provide an example)
also do you have any decent links that explain what the output means.

So, we can say that my initial problem is solved,
but.... how did simply applying some patches miraculously resolve those 'missing tools' Question


Once again, thanks to you both
CatDude

P.S
Any progress on v2.0 Question

.


You ran Strace properly, that 1000 lines of gobbledegook as you put it it should hold the answer. But I see you're problem is resolved from following the advice from the other thread. As to Strace Output and making sense from it, thats really well beyond the context of this thread, but a simple google search should give you some links which may explain what all you are seeing. Basically it logs and reports the status of all system calls that a program makes when trying to run or when its running. Also gives you a good idea of just how much is going on in the background when you dont see anything. lol.

As for how the patches fixed your 'missing tools', the problem most likely is that the installer was looking in the wrong place for the tools, so it was reporting them missing. IE, it was looking in say /usr/bin for something, and not finding it becuase it was in /usr/local/bin. I just made up that example, but if it couldnt find it in /usr/bin it may report it as missing because its not where it thinks it should be. Without looking at the patch I have no clue, but it may have been an issue like that.

V2 is taking a bit longer than I wanted, because I just havent had the time to work out the last few kinks and polish it up a bit.
And to be honest, due to the time its taken, some of the core slackware components have been updated, so I'm thinking of updating those as well. Just pulled down a local copy of the most recent slackware-current mirror to update some things.
I was previously going with the 3.9.4 kernel as shown previously, but Im thinking of maybe going with the 3.10 branch, if I can build it without issue.

smokey01 wrote:
Q5sys is there any way to increase the personal storage file in slackbones?

Thanks

Hmm... That probably would be a good thing to include. lol.
I've never used the resize script that comes with Puppies... I just manually created the pupsaveresize.txt file in my /mnt/home directory and then put in the appropiate value. Its in MB. so for 256mb you'd just type "262144"
Then save it. Then on reboot it'll increase the save file that size.
That 'SHOULD' work for SB, since it uses the same save file system as FatDog.
I've never looked into how save files got expanded during a boot cycle. I'll see if JamesBond can shed more light on that.

_________________



Back to top
View user's profile Send private message Visit poster's website 
smokey01


Joined: 30 Dec 2006
Posts: 1828
Location: South Australia

PostPosted: Tue 09 Jul 2013, 23:24    Post subject:  

Quote:
I just manually created the pupsaveresize.txt file in my /mnt/home directory and then put in the appropiate value. Its in MB. so for 256mb you'd just type "262144" Then save it. Then on reboot it'll increase the save file that size.


I tried the above, it didn't work.

I also transported the Fatdog savefile tool to SB and it didn't appear to work either. The savefile does however appear to have increased in size but it is not recognised by the save file indicator in the task bar.

Cheers

_________________
Puppy Software <-> Distros <-> Puppy Linux Tips
Back to top
View user's profile Send private message Visit poster's website 
jamesbond

Joined: 26 Feb 2007
Posts: 2221
Location: The Blue Marble

PostPosted: Tue 16 Jul 2013, 00:26    Post subject:  

The recipe to increase savefile (asssuming unecnrypted ext2/3/4 savefile):

1. Boot without savefile.
2. Increase the savefile size, like this (say you want to increase by 256M).
Code:
head -c 256M /dev/zero >> /path/to/savefile

3. The increase the savefile's filesystem, like this:
Code:
e2fsck -y /path/to/savefile
resize2fs /path/to/savefile
e2fsck -y /path/to/savefile


e2fsck must be run twice, before and after resize2fs.

4. Done!

Change '256M' to '1G' or '2G' or '512M' or '141M' or whatever you want Smile Make sure you use >> (two greater-than signs) and not > (one sign), if you accidentally use only one sign then goodbye savefile, hello frustration.

The Fatdog savefile tool should work but I haven't tested it myself, it could depend on some obscure tool Fatdog that isn't in SB.

_________________
Fatdog64, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread
Back to top
View user's profile Send private message 
noprob


Joined: 17 Mar 2007
Posts: 19
Location: Mountains of WV. U.S.of A.

PostPosted: Mon 28 Apr 2014, 16:46    Post subject: SlackBones x86_64
Subject description: v2
 

I have read this thread in hopes of downloading SlackBones x86_64 v2

Will v2 of SlackBones x86_64 v2 see the light of day?

to be downloaded for those of us interested?

Thx.

P.S. I may have a go at v1.2 SlackBones x86_64 v2 and thank you to those who have put the effort into this version Puppy Linux.

noprob

-eof
Back to top
View user's profile Send private message Visit poster's website 
noprob


Joined: 17 Mar 2007
Posts: 19
Location: Mountains of WV. U.S.of A.

PostPosted: Mon 28 Apr 2014, 16:47    Post subject: SlackBones x86_64
Subject description: v2
 

duplicate post (deleted)
Back to top
View user's profile Send private message Visit poster's website 
greengeek

Joined: 20 Jul 2010
Posts: 2591
Location: New Zealand

PostPosted: Sat 21 Jun 2014, 06:13    Post subject:  

Iguleder wrote:
Got all these, built automatically under both a Slackware 14.0 (x86_64) and Ubuntu 12.04 (i686):
Code:
libsigc++
shed
vim
linux-source
advancecomp
bitlbee
elinks
tudu
dropbear
aspell6-en
terminus-font
unnethack
slock
screen
libav
abook
optipng
rxvt-unicode
snownews
gpm
fetchmail
msmtp
ncdu
fbset
surfraw
dash
aria2
bwm-ng
libtorrent
fbpdf
locale-gen
fbshot
mktemp
linux-headers
cmus
busybox
irssi
syslinux
squashfs-tools
lftp
fbv
linux
vifm
libbsd
licenses
cddetect
setvol
cgtkcalc
elspci
xload
aufs3-util
bcrypt
bbc_provided
ddcprobe
getcurpos
915resolution
dhcpcd
aqualung
maildrop
cwm
rtorrent
figlet
aspell
xdotool
htop
dtach
frost
roar-ng-ii
mplayer2
calcurse
dvtm
iana-etc
mutt
bash


I can cross-compile them to any other architecture. The list contains some Puppy-specific packages (e.g elspci) and I'm working on more build scripts for such packages.

I want to make the building of all packages under Packages-puppy-common-official automated, so we can port Puppy to x86_64 or any other architecture easily. It's an on-'n-off project I've been working on for months now.


Could you help me find a package that includes an xdootol prerequisite of libxdo.so.2 (64 bit version) please? thx!
Back to top
View user's profile Send private message 
smokey01


Joined: 30 Dec 2006
Posts: 1828
Location: South Australia

PostPosted: Sat 21 Jun 2014, 07:45    Post subject:  

Have you tried:
http://www.smokey01.com/software/Fatdog64-600/xdotool-fd64.pet

_________________
Puppy Software <-> Distros <-> Puppy Linux Tips
Back to top
View user's profile Send private message Visit poster's website 
ciento

Joined: 17 Sep 2010
Posts: 180

PostPosted: Sat 21 Jun 2014, 16:20    Post subject:  

jamesbond wrote:
The recipe to increase savefile (asssuming unecnrypted ext2/3/4 savefile):
Thanks for sharing this! I'll try it soon.
Cheers
Back to top
View user's profile Send private message 
greengeek

Joined: 20 Jul 2010
Posts: 2591
Location: New Zealand

PostPosted: Sat 21 Jun 2014, 18:08    Post subject:  

smokey01 wrote:
Have you tried: http://www.smokey01.com/software/Fatdog64-600/xdotool-fd64.pet

Thanks smokey, that has given me what I need. Not sure why I couldnt pull that lib out of other pets though. I tried several of them from various sources and could not see that lib available in any of them when I unzipped them. Mustve been doing something wrong somewhere.
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 7 of 7 [103 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6, 7
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.1006s ][ Queries: 13 (0.0071s) ][ GZIP on ]