I tried the raspberry pi distribution at rpi3.fatdog.eu. The slackware installer works fine till the select target and source locations. When the installation starts it just shows a few lines of messages and then said the installation is done. Too bad the messages goes too fast and I can't see them.

Did anyone know what is wrong? How can I proceed?

Follow rpi3.fatdog.eu carefully, I think I ran into what you did because I didn't identify source correctly.

14.2 or -current?

I assume You installed to mmc/SD card?

Could You possibly post some more data?

See, I installed -current to R_Pi breaking no sweat?

Which version of Slackware ARM are you wanting to install and what did you select as your source media?

If you've used a USB memory stick then select "Install from a Slackware USB stick" and make sure the USB stick containing Slackware ARM is plugged in. It should be auto-detected if Slackware ARM is in the root. If Slackware ARM is not in the root of the USB stick then select "Install from pre-mounted directory" and make sure you have already mounted that directory on your system which contains Slackware ARM.

If you are using a http/ftp server as your source media then select "Install from http/ftp server" and use an existing server. For example, to install Slackware ARM current:

URL: http://slackware.uk/
source directory: slackwarearm/slackwarearm-current/slackware

I suspect you have made an error somewhere when you've specified the path to your source media, or you've not mounted the Slackware source directory correctly.

This page http://sarpi.fatdog.eu/index.php?p=srcmedia tells you how to achieve what you're trying to do.

I am installing the -current branch of Raspberry pi 3, hard float support. And yes, I am installing onto a 16GB MicroSD card.

I don't think the source location has problem, as I can see all the packages there, and I can select them.

I have tried using NFS, but failed. Then I tried to copy the data to a USB stick, and also fail.

Any idea?

Have you set the date?

I know it sounds like a stupid question but the only times I have had an install fail is when I ignore the advice to set the date before starting.

sets the date from the internet, if available.
Other than that, refer to:

I have set the date. The first time i get into the terminal I set the date.

And you have created the root and swap partitions and saved the settings using fdisk/cfdisk before running setup?

Yes, I have done everything mentioned in the home pages

1. create the swap partition
2. create the Linux partition
3. Add swap
4. Add Linux partition, format as EXT4
5. Mount partition 1 as /boot
6. Select source partition (NFS)
7. Install everything
8. Oops

Try another microSD card other than the one(s) you have used. That's the only suggestion I can offer considering you seem to have done everything required correctly in order to install Slackware ARM.

there are ways to nc the syslog to an 3rd party (nearby computer)

try man nc and try using it to retrieve what's going wrong that instant?

on rpi:
on other PC:
or
/var/log/messages

or whatever file of interest?

There is no /var/log/syslog or /var/log/messages during install.

Is it wrong?

Finally, I got the error messages from the screen, capture the video and see them frame by frame.

First, the error is

/usr/bin/setup/setup: line 340: /mnt/etc/fstab: No such file or directory

About 10 of this line appears.

I then copy the /etc/fstab to /mnt/etc/fstab, and here it comes

chmod: /mnt/tmp: No such file or directory
/usr/lib/setup/Setconfig: line 53: /mnt/etc/rc.d/rc.keymap: No such file or directory
/usr/lib/setup/Setconfig: line 54: /mnt/etc/rc.d/rc.keymap: No such file or directory
/usr/lib/setup/Setconfig: line 56: /mnt/etc/rc.d/rc.keymap: No such file or directory
/usr/lib/setup/Setconfig: line 57: /mnt/etc/rc.d/rc.keymap: No such file or directory
/usr/lib/setup/Setconfig: line 58: /mnt/etc/rc.d/rc.keymap: No such file or directory
chmod: /mnt/etc/rc.d/rc.keymap: No such file or directory

Seems it needs rc.keymap, is anything missing?

I'll do some testing over the coming weekend and see if I can replicate this error.