http://rpi2.fatdog.eu

Website is currently being developed. There´s no installation guide (yet) but the Slackware ARM installer and 3.18.x kernel/module/boot packages are available for download.

Voila!

I assumed it would be the same as the original RPi, is it that much different? I haven't had a chance to mess with mine yet.

Ahh I see, it is pretty much the same install instructions.

Finally got the chance to start, took about 2 hours from downloading smalckware-arm current, writing the sd and usb flash, setup, remove the unneeded packages and installing the three rp2 packages and I now have a running RP2.

Good work. Glad you´ve managed to get it all up and running.

I´ve noticed a few errors, here and there, pre- (and post-) installation. These errors will be resolved in future releases of the SARPi2 installer.

The important thing is that it´s working as intended and makes it easier for Raspberry Pi 2 owners to install and run Slackware ARM on the device. Happy days!

Need to thank MoZes for his minirootfs and making this possible.

I didn't see any real errors, I noticed that the kernel and firmware packages were just in one place instead of two subdirectories but thats pretty minor. May have been easier because I went through the install with an original Pi and took my own notes of just the steps I needed leaving out the windows specific or mounting the USB flash as floppy (the setup finds it either way).

The SARPi2 installer guide is now available, albeit in a rough-diamond state. It´s still being worked on, and reworked. Thanks for your patience.

Expect changes to the installer guide and the available downloads within the next few days.

Feedback is always good. If you notice any errors or something that´s not quite correct, please let me know.

Thanks,

any reason why you made the swap 256M?

I also found its not necessary to mount the source usb flash drive, the slackware installer will find it anyway (bottom of the infodrives page)

Also is there any way to have the instructions all on one page instead of multiple (I typically will save system install directions locally).

Well this is a dilemma; ;-D

The Slackware ARM on a Raspberry Pi guide *is* all on one page. A few people have commented that it´s a bit long-winded and hard to follow if you lose track. So, we broke down the Slackware ARM on a Raspberry Pi 2 guide into shorter sections.

Mounting the USB stick is always optional. It´s also good practice to do so. Installing from the network doesn´t require a USB stick. I thought this was clear in the guide. I will go through it again and make sure it is clear and makes sense.

There is no specific reason for the 256MB /swap. Use whatever size suits your needs best.

The only reason for one is so I can save it off. I've seen pages like that where they have a link that I believe is just a script that cat's all the files together into one to make a single file. No biggie, I've made my own notes for this project.

I think its the wording on the infodrives page "Once this has been done you now have the option to Mount your USB memory stick if you are using it for your Slackware source."

sounds like its needed to be mounts to use it as a source, but it can be used as a source also without mounting. But then again I'm nitpicky, I don't like to call it a stick either ever since I had a user go to $PCSHOP$ and get handed a (Sony memory) Stick when they asked for a stick.

If you have made your own notes then you have no need for an installation guide. If you have no need of an installation guide there's no reason to ask for it being modified.

The wording at the bottom of that page makes perfect sense if you care to read it all in context. "You can mount a USB stick *IF* you are using it as the location of Slackware source media" (and the next line says) "*IF NOT* carry on to the next page..." is how I read it.

USB stick is what it's called during Slackware setup. You see USB stick on the setup screen. You see USB stick in the guide. It's the same thing. No debating over whether a USB storage/pen/memory/device and stick is the same thing. Trust me, some people get confuzzled in that respect.

Just suggestions, no big deal.

The RP2 is working a lot better, the original failed when I imported my calendar to owncloud, the 2 kept on working.
I have this box:

Dell Latitude D630, 1TB Drive, 2G RAM

That I run as a secondary workstation as well as a DLNA and samba server and my OwnCloud server. I'm going to move OwnCloud to the RP2 to split the load.

Hi,

I just tried a couple of times to install raspi2 but the installation does not happen. The installer runs but nothing gets actually installed and I can reboot 5 secs after choosing the packages.

The packages are on a USB drive but this was not recognized initially (slackarm is in a separate directory on that usb-drive) and only after manually mounting it the packages were found.

Is it not possible to install slackarm straight onto the SD card from within a PC with slackware installed (and the arm-packages somewhere in a directory)? That would be an enormous time-saver.

PS: some quirks which I do not know are intentional: when checking the md5sum of the downloads it throws an error when the files are not in /tmp. The md5sum calls the file instead of, what would be less restrictive, . (I do not keep stuff I like to hold on to in /tmp; that gets erased every reboot)

PS2: would it be a problem with the usb-drive or power?

That's what I had to do when I first started the port since I had no other option.
The script below was written in 2004 and hasn't been used since 2006 but it would give you an idea of how to do it
ftp://ftp.arm.slackware.com/slackwar...ts/tinstall.sh

The problem with this approach is that some packages' post installation script runs the binaries it just installed, which obviously isn't going to work since you cannot run ARM binaries natively on a different platform, therefore some packages would not be set up properly.
Some of the installation scripts also act upon the content of /proc/cpuinfo to make decisions about what to configure, which also won't be effective if not running on ARM. There aren't many of these any more, but there are still a couple.

Somebody is welcome to make an x86 ARM installer though - if someone wanted to work out which packages needed to be installed natively, it wouldn't be overly difficult to write a 'first boot' script that fixed the stuff and removed itself upon completion. It just would need maintenance.

Take a look at this: install-slack-via-raspbian.txt

It's a cheeky way of getting Slackware ARM to run off the back of Raspbian and may be helpful.

There's also a Slackware ARM on a Raspberry Pi 2 installer guide you might not be aware of. Good luck!

Hi Stuart,

Thanks for the advice. I am afraid I am not up for this job.; but at last, at the moment something is happening (libcgroup has just been installed)....

And Penthux, yes, I found the ; that's the one I have been following. Today, I started again with a fresh download of the slackarm sources and copied this all to a new USB drive and now with this, using mains power to feed the pi2, on the third attempt (and I do not know why, as I did not really change anything, but repeated the same steps) the installer started to work and is now copying... (I am at the mariadb now ;-).

What I observed:
a) only the A-series could be installed (not the whole set was visible) during the first coupleof attempts
b) premounting a drive is not always taken/kept. The created mount point seems to get lost during subsequent set-up (because of formatting the linux partition?). So the installer could not find the packages. I communicate with the home-networked pi2 over ssh and from an another terminal I ssh-ed in again and repeated the creation of a mount point (mkdir /mnt/source) and attached my drive to it (mount -t vfat /dev/sda1 /mnt/source). Then from the original connection with setup running, I could continue...and I even got a screen to pick from the complete series of sources (skipped E,KDE and T) and off I was.

Hopefully it will complete ...(installing the kernel now)...

Hi brobr,

Just a suggestion you might want to try for yourself...

Change the USB stick you are using. Try plugging it into different USB ports when installing. I've heard of a few issues with certain USB sticks when installing Slackware ARM if they are plugged into the USB ports not next to the Ethernet port on the raspi2. Don't know if this applies to the problems you're having but it's worth testing.