I know I must have some sort of uncommon PRi one model B revision ... but I ran into trouble again while trying to boot it with fatdog's kernel, kernel modules and boot firmware. I went and got the stuff from raspbian wheezy and it boots fine.

while getting the stuff I noticed that there are 2 kernel images and 2 sets of kernel modules ... and 2 sets of other stuff in the boot partition ... I can now confirm that it's for booting both RPi and RPi2.

Another thing I found useful is loading the hardware random number generator kernel module (bcm2708-rng) that is not loaded by default in fatdog's rc.modules. If you do this you get an extra character special device file /dev/hwrng ... when you read from there you are reading random thermal noise from a component in the pi's SOC ... it may make better random numbers then /dev/random.

What kind of trouble are you running into with the FatDog.eu image(s)?

Sometimes they just don't boot on my RPi1. It's just a report that maybe fatdog will pickup and correct so that possibly other people with same peculiar revision don't run into the same problem. I generally work around the problem by using the "Manual installation method" I wrote myself on http://docs.slackware.com/howtos:har...rm:raspberrypi

Do you mean the SARPi installer doesn't boot or the system doesn't reboot after installation? Also, which model revision of the RPi (1) are you using? Perhaps further testing is required but initially I'm just trying to get a clear grasp of what the problem is or could be.

I have done the manual install method quite a few times too. Although I need to turn off fsck checks on the root partition or else it panics on reboot. In the section below (taken from the slackdocs page) fsck pass is set to "1" on the root partition and I just change it to "0":

Then it will boot/reboot and work for me without any problems.

I don't use the installer anyway.. I use the boot stuff to get a miniroot to boot just like described in the manual installation method ... just try to get the boot stuff from fatdogs boot packages. Fstab is ok I'm sure because just by extracting the boot stuff off raspbian the same root image boots fine.

The sixth and last field is the fsck pass number and it's still set to 1 in the fragment you show .... you may have set / not to be dumped. I'm not sure why your pi crashes if dump is enabled ... if I've time I'll look into it. The only Pi I care about is running with / in read only so I don't care about either dump or fsck.

The B not the B+ right? I just redid mine with his latest image and it worked fine.

I'm sure most do work: I must have an odd uncommon revision as it's not the first time I noticed this and subsequently using boot stuff from raspbian solves the issue.

I had a *lot* of trouble running Slackware ARM with the RPi 1 (Micron RAM version) when it was first released but all the issues were solved in one simple firmware update.

I read somewhere that the Pis with the micron chip also had an issue with SD cards smaller then 2Gb ... well I've a Micron chip on one of my Pis but it boots fine even with 256Mb SD cards.
Another odd thing both my Pi 1 do: even with high quality 5V power supply inserting a full power usb dongle into them causes a reboot. My Pi2 doesn't do that.
I even suspect that I might have a Chinese fake Pi or something like that ... thankfully grabbing kernel, modules and boot firmware from rasbian gets it to boot.

Every time I have had a boot issue with Fatdog's stuff, it has turned out to be crappy SD Card problems (including name brand SD Cards). I've found that ALOT of SD cards (mostly the unbranded chinese ones) won't boot at all. Some will boot with Raspbian will not with SlackArm.

Go get a good SD card and try fatdog's image again.

The best microSD cards I have found is the Samsung EVO range. I have found these cards to be almost as reliable as Slackware!

Have Slackware on two RPis (i think it's 2 B) and I can confirm that SD cards can be an issue.
I use a TF card with an adapter and had some troubleshooting and media swapping done back then...