2009-12-31, 06:12
***EDIT 6-09-2011 I am currently working on XBMC from GIT on Slackware-Current(6-09-2011) and I will update this post again once I have it working and a tutorial made.
http://forum.xbmc.org/showthread.php?tid=102863
Hi everyone.
Installed Slackware64 version 13 and immediately downloaded the recommended driver from nvidia.com. Used another computer as they use flash on their site and didnt have the plugin installed yet. Nvidia installation went fine as I installed a full install of Slackware so the needed kernel source files were there. Instructions are in the driver package for installation.
Next I went in to /etc/slackpkg/mirrors and very carefully un-commented the mirror that lines up with my location and within the x86_64 section. Mind that this mirrors has sections for different hardware. If you choose the wrong section you will corrupt your install. Next I opened a terminal and Issued
"su" and the root password to get to superuser and
"slackpkg update"
let it grab fresh package and diff listings from the mirror that was un-commented and
"slackpkg update-all"
and it will download new kernel and source as well as the needed mesa library update that we will need to get things built properly. Let it run lilo as if you upgrade a kernel and dont let the script rerun lilo you may corrupt your ability to boot cleanly.
Now that we have an updated system lets get familiar with http://www.slackbuilds.org and in particular sbopkg.
**Edit its important to reinstall the nvidia driver after upgrading ones kernel.
sbopkg is a slackbuilds package manager of sorts. It syncs your computer with slackbuilds.org and allows you to automate the previously manual method of making and installing a slackbuild. Its a command line utility that will open a ncurses dialog allowing you to add and remove software in just a few arrow keys. Not only that but one can search and browse the repository from sbopkg as well. http://sbopkg.org
Time to download the source and find a slackbuild. At the time of writing it is December 31st and if packages change between now and when you try this bear in mind mileage may vary.
Source is available from the downloads section of XBMC.org.
http://sourceforge.net/projects/xbmc...ar.gz/download
Or by following the source link in the downloads section
and the slackbuild I used was obtained here:
http://blog.tpa.me.uk/wp-content/upl...10/xbmc.tar.gz
Direct linking doesnt seem to work on that one so go here and scroll down:
http://blog.tpa.me.uk/
or
http://www.filefactory.com/file/a165b37/n/xbmc.tar.gz
decompress the xbmc.tar.gz folder and then move the source we downloaded (keep it compressed) in to the xbmc folder. Either right click on the xbmc.SlackBuild and open with kate or use nano if you are familiar. Scroll to the line that reads:
ARCH=${ARCH:-i486}
and change it to
ARCH=${ARCH:-x86_64}
Save and exit
Now we will learn about dependencies and how handy sbopkg is.
I had a terminal open with two tabs.
First lets get the slackbuild executable and open a terminal, navigate to the download folder via "cd /home/user/download-folder" replacing the obvious. As superuser or sudo "chmod u+x xbmc.SlackBuild" and then "sh ./xbmc.SlackBuild" to execute it.
Expect a failure.
There will be about 4 or 5 dependencies that we will need to get through sbopkg. As superuser in the second tab type "sbopkg" and search whatever the compile error you saw was related to. In my case I opened firefox and searched off the slackbuilds.org website. Then went in via browse to add the needed deps to the queue in sbopkg. Once you have added the deps to the queue back out to reveal the "queue" menu. Go in and "process" the queue. Proceed and opt to install after building. Sbopkg only wants one instance at a time so after a fail at building close out that instance after aborting and then search the needed packages.
Repeat process until there are no more dependencies left and let the build script finish. In the last few lines you will see that the built package was placed in your /tmp folder. Simply issue in the terminal "installpkg /tmp/xbmc-9.11______.tgz" keeping superuser privileges and you will now be enjoying XBMC on slackware64.
The reason I went slackware was speed and stability. Is so beneficial to compile your programs on your own hardware as they make a better mesh so I prefer a distribution that allows this in its own package management. In my opinion this is the fastest distro I have tried out of Ubuntu64, Sabayon64, Suse64, and Debian Squeeze. I have a DFI lanparty microATX with the Geforce 9400, 4gigs ram and 1.5tb in a monual case. I attach a synology NAS box and utilize an HDHomeRun. The NVidia 190.53 drivers work great. I cant comment enough on how nice XBMC is to interface with. My apple airport xtreme / airport express bridge combination keeps the network from bogging with a wds configuration and I run xbmc on three computers. Two are apples. Makes a great media center for the mac mini too. Just use the m-audio transit if you need surround sound on snowleopard with perian. If your in need of wireless on slackware64 I would recommend looking for wicd as it can maintain the internet connection through the suspend functionality that XBMC provides. This can be a problem for some wifi managers. I did find a slackbuild for wicd somewhere but I forgot to bookmark it. Read the readme once you find it as one needs to make an entry in rc.d executable for wicd to work. Aside from this slackware is easy to script an autologin with as long as you dont fear the terminal. Useful if your making a media center and want to bypass gdm to get right to XBMC without a desktop loading. Lirc is in the slackware packages. I have both android and an ipod touch and utilize the remote apps for both. XBMC team, cheers on a wonderful application!
http://www.slackbook.org/
for more.
Hope it helps. PM me with edits or questions as I may not check here often.
quotaholic
http://forum.xbmc.org/showthread.php?tid=102863
Hi everyone.
Installed Slackware64 version 13 and immediately downloaded the recommended driver from nvidia.com. Used another computer as they use flash on their site and didnt have the plugin installed yet. Nvidia installation went fine as I installed a full install of Slackware so the needed kernel source files were there. Instructions are in the driver package for installation.
Next I went in to /etc/slackpkg/mirrors and very carefully un-commented the mirror that lines up with my location and within the x86_64 section. Mind that this mirrors has sections for different hardware. If you choose the wrong section you will corrupt your install. Next I opened a terminal and Issued
"su" and the root password to get to superuser and
"slackpkg update"
let it grab fresh package and diff listings from the mirror that was un-commented and
"slackpkg update-all"
and it will download new kernel and source as well as the needed mesa library update that we will need to get things built properly. Let it run lilo as if you upgrade a kernel and dont let the script rerun lilo you may corrupt your ability to boot cleanly.
Now that we have an updated system lets get familiar with http://www.slackbuilds.org and in particular sbopkg.
**Edit its important to reinstall the nvidia driver after upgrading ones kernel.
sbopkg is a slackbuilds package manager of sorts. It syncs your computer with slackbuilds.org and allows you to automate the previously manual method of making and installing a slackbuild. Its a command line utility that will open a ncurses dialog allowing you to add and remove software in just a few arrow keys. Not only that but one can search and browse the repository from sbopkg as well. http://sbopkg.org
Time to download the source and find a slackbuild. At the time of writing it is December 31st and if packages change between now and when you try this bear in mind mileage may vary.
Source is available from the downloads section of XBMC.org.
http://sourceforge.net/projects/xbmc...ar.gz/download
Or by following the source link in the downloads section
and the slackbuild I used was obtained here:
http://blog.tpa.me.uk/wp-content/upl...10/xbmc.tar.gz
Direct linking doesnt seem to work on that one so go here and scroll down:
http://blog.tpa.me.uk/
or
http://www.filefactory.com/file/a165b37/n/xbmc.tar.gz
decompress the xbmc.tar.gz folder and then move the source we downloaded (keep it compressed) in to the xbmc folder. Either right click on the xbmc.SlackBuild and open with kate or use nano if you are familiar. Scroll to the line that reads:
ARCH=${ARCH:-i486}
and change it to
ARCH=${ARCH:-x86_64}
Save and exit
Now we will learn about dependencies and how handy sbopkg is.
I had a terminal open with two tabs.
First lets get the slackbuild executable and open a terminal, navigate to the download folder via "cd /home/user/download-folder" replacing the obvious. As superuser or sudo "chmod u+x xbmc.SlackBuild" and then "sh ./xbmc.SlackBuild" to execute it.
Expect a failure.
There will be about 4 or 5 dependencies that we will need to get through sbopkg. As superuser in the second tab type "sbopkg" and search whatever the compile error you saw was related to. In my case I opened firefox and searched off the slackbuilds.org website. Then went in via browse to add the needed deps to the queue in sbopkg. Once you have added the deps to the queue back out to reveal the "queue" menu. Go in and "process" the queue. Proceed and opt to install after building. Sbopkg only wants one instance at a time so after a fail at building close out that instance after aborting and then search the needed packages.
Repeat process until there are no more dependencies left and let the build script finish. In the last few lines you will see that the built package was placed in your /tmp folder. Simply issue in the terminal "installpkg /tmp/xbmc-9.11______.tgz" keeping superuser privileges and you will now be enjoying XBMC on slackware64.
The reason I went slackware was speed and stability. Is so beneficial to compile your programs on your own hardware as they make a better mesh so I prefer a distribution that allows this in its own package management. In my opinion this is the fastest distro I have tried out of Ubuntu64, Sabayon64, Suse64, and Debian Squeeze. I have a DFI lanparty microATX with the Geforce 9400, 4gigs ram and 1.5tb in a monual case. I attach a synology NAS box and utilize an HDHomeRun. The NVidia 190.53 drivers work great. I cant comment enough on how nice XBMC is to interface with. My apple airport xtreme / airport express bridge combination keeps the network from bogging with a wds configuration and I run xbmc on three computers. Two are apples. Makes a great media center for the mac mini too. Just use the m-audio transit if you need surround sound on snowleopard with perian. If your in need of wireless on slackware64 I would recommend looking for wicd as it can maintain the internet connection through the suspend functionality that XBMC provides. This can be a problem for some wifi managers. I did find a slackbuild for wicd somewhere but I forgot to bookmark it. Read the readme once you find it as one needs to make an entry in rc.d executable for wicd to work. Aside from this slackware is easy to script an autologin with as long as you dont fear the terminal. Useful if your making a media center and want to bypass gdm to get right to XBMC without a desktop loading. Lirc is in the slackware packages. I have both android and an ipod touch and utilize the remote apps for both. XBMC team, cheers on a wonderful application!
http://www.slackbook.org/
for more.
Hope it helps. PM me with edits or questions as I may not check here often.
quotaholic
