Slackware ARM on a Raspberry Pi 3

The SARPi project forum. For anything and everything relating to Slackware ARM on a Raspberry Pi 1, 2, and 3. This forum is NOT a replacement or substitute for the Slackware (ARM) forums on Linux Questions website! Please try to seek help there first about any issues you may be experiencing, or question you might have, before posting on here.
User avatar
Exaga
FatDog Network Administrator
FatDog Network Administrator
Posts: 198
Joined: Wed Apr 18 2012 - 02:01:03
Location: England [UK]

Slackware ARM on a Raspberry Pi 3

Postby Exaga » Tue Apr 26 2016 - 17:04:03

For all you RPi3 users... SARPi3 is now available.

http://rpi3.fatdog.eu

The SARPi3 installer uses the same kernel and kernel-modules as the SARPi2 installer (because they work) which means days of time, effort, and testing were waived. Once Slackware ARM has been installed, and the system is running, it's very easy to update/upgrade to the 4.x kernel(s) and latest boot-firmware.

It's been tested on 14.1 and -current and seems to work as intended and expected. The SARPi3 guide mentions Slackware ARM 14.2 in places but just ignore these references to 14.2 until it's actually released please. I did this to save time/effort editing the guide a second time once 14.2 has finally been released. :P

Enjoy SARPi3! Let me know if you find any bugs. :1337:

8-)
Exaga

====
__ KEEP THE DOG ALIVE!!!
()'`; /
/\|` W00f W00f W00f
www.fatdog.eu

User avatar
Exaga
FatDog Network Administrator
FatDog Network Administrator
Posts: 198
Joined: Wed Apr 18 2012 - 02:01:03
Location: England [UK]

Re: Slackware ARM on a Raspberry Pi 3

Postby Exaga » Thu May 05 2016 - 20:59:11

The latest SARPi3 installer (04 May 2016) now runs the 4.4.8-v7-arm kernel.

Download it here: http://rpi3.fatdog.eu/index.php?p=downloads

Enjoy! 8-)
Exaga

====
__ KEEP THE DOG ALIVE!!!
()'`; /
/\|` W00f W00f W00f
www.fatdog.eu

User avatar
myrddin
New member
New member
Posts: 2
Joined: Sat Jun 04 2016 - 18:53:20

Re: Slackware ARM on a Raspberry Pi 3

Postby myrddin » Sat Jun 04 2016 - 19:09:38

I'm trying to install on a RPi 3 without a monitor, (i.e. via ssh).
I've made the changes to cmdline.txt (added 'kbd=uk nic=auto:eth0:dhcp'),
plugged in power and ethernet, and the boot seems to have gone ok, judging by the LEDs.
Orange light comes on at eth0 port, so that's OK too.

HOWEVER
I can't log in via ssh, as it looks like sshd isn't running. If I run an nmap scan on the network,
I get

Code: Select all

Nmap scan report for 192.168.0.110
Host is up (0.00063s latency).
All 1000 scanned ports on 192.168.0.110 are closed
MAC Address: B8:27:EB:C9:26:85 (Raspberry Pi Foundation)

Is there anything I need to do to run sshd on first boot?

cheers

Myrddin

User avatar
Exaga
FatDog Network Administrator
FatDog Network Administrator
Posts: 198
Joined: Wed Apr 18 2012 - 02:01:03
Location: England [UK]

Re: Slackware ARM on a Raspberry Pi 3

Postby Exaga » Mon Jun 06 2016 - 22:49:48

myrddin wrote:Is there anything I need to do to run sshd on first boot?


I'm not sure why it's not working for you. I've tested using the exact methods you are using and had no problems. I really cannot explain why you are unable to connect via SSH.

You could try activating the NIC manually using (for example):
# ifconfig eth0 192.168.x.x netmask 255.255.255.0 up

... and then running dropbear for SSH:
# /etc/rc.d/rc.dropbear start

Then try logging in via SSH as before.
Exaga

====
__ KEEP THE DOG ALIVE!!!
()'`; /
/\|` W00f W00f W00f
www.fatdog.eu

User avatar
myrddin
New member
New member
Posts: 2
Joined: Sat Jun 04 2016 - 18:53:20

Re: Slackware ARM on a Raspberry Pi 3

Postby myrddin » Thu Jun 09 2016 - 01:39:03

Hi Exaga, thanks for the reply.

I'm trying to do a totally headless install, just booting the install image and then connecting via ssh, which I think used to work a few years ago.
If I can't ssh into the pi, I can't activate the nic or start dropbear.....
I was hoping there was an easy way to hack the rc.d scripts on the install image before booting, but that looks a bit above my pay-grade.
I think I'll just wait till I get a TRRS / RCA lead so I can do it locally - probably the easiest way.

thanks a lot for the advice anyway, I really appreciate people taking the time to help others

Myrddin

UPDATE
======
I poked initrd.gz a bit harder and realised it was a cpio archive, so maybe not totally beyond me. I will carry on poking to see if I can find out
where my problem is, and report back. (A little out of my comfort zone, so I may be gone some time!)

User avatar
Exaga
FatDog Network Administrator
FatDog Network Administrator
Posts: 198
Joined: Wed Apr 18 2012 - 02:01:03
Location: England [UK]

Re: Slackware ARM on a Raspberry Pi 3

Postby Exaga » Sat Jun 11 2016 - 11:15:42

myrddin wrote:thanks a lot for the advice anyway, I really appreciate people taking the time to help others



You're welcome. Being able to log in locally is what you need in order to problem-solve this one. Without the ability to see what's going on (or gone wrong) it's not easy to offer any solutions. :lol:
Exaga

====
__ KEEP THE DOG ALIVE!!!
()'`; /
/\|` W00f W00f W00f
www.fatdog.eu

User avatar
DJ1975
New member
New member
Posts: 1
Joined: Sun Jul 10 2016 - 20:08:16

Re: Slackware ARM on a Raspberry Pi 3

Postby DJ1975 » Sun Jul 10 2016 - 20:19:04

First of all thanks for one of the most useful distributions out there for the Pi.

I was installing on a RPI3 for the first time (already have it running on RPI2s) and had the same issue as described by the Original Poster.

I the connected with a HDMI and USB keyboard, and attempted to start dropbear with the init script, no luck.

root@slackware:~# cat /var/log/dropbear.log
[811] Jan 01 00:00:10 Premature exit: Error opening banner file '/etc/motd.net'
[852] Jan 01 00:00:56 Premature exit: Error opening banner file '/etc/motd.net'

I then started by /sbin/dropbear and things worked as expected. Perhaps this is something that can be fixed easily, I don't know?

Again thanks for a useful core distro for RPI. There simply is no serious alternative.

User avatar
ingesi
Registered user
Registered user
Posts: 7
Joined: Wed Jul 27 2016 - 18:48:38

Re: Slackware ARM on a Raspberry Pi 3

Postby ingesi » Wed Jul 27 2016 - 19:08:35

I've found the same bug with dropbear

In /etc/rc.d/rc.dropbear I've found this line to start dropbear

/sbin/dropbear -b /etc/motd.net 2>> /var/log/dropbear.log

but the file /etc/motd.net doesn't exist -- there's instead a file named /etc/motd

Kind regards

Alessandro Barisone

User avatar
Exaga
FatDog Network Administrator
FatDog Network Administrator
Posts: 198
Joined: Wed Apr 18 2012 - 02:01:03
Location: England [UK]

Re: Slackware ARM on a Raspberry Pi 3

Postby Exaga » Sun Jul 31 2016 - 00:48:38

Thank you all for the kind remarks and compliments, you gorgeous Slackers! However, the real thanks and praise must genuinely go to the hard working Slackware Team, especially Mozes. These are the guys who make everything possible. :love:

I simply can't guess what's happening with dropbear for you guys. If/when I'm doing a headless install, prior to booting, I usually edit the /boot/cmdline.txt file and specify 'kbd=us nic=auto:eth0:dhcp'. Then, on first boot, the network is enabled and configured. Using this method seems to work flawlessly every time for me. Whenever I've enabled and configured eth0 manually there's been no problems or issues.

Obviously some of you are having problems but I cannot seem to replicate them. :?
Exaga

====
__ KEEP THE DOG ALIVE!!!
()'`; /
/\|` W00f W00f W00f
www.fatdog.eu

User avatar
ingesi
Registered user
Registered user
Posts: 7
Joined: Wed Jul 27 2016 - 18:48:38

Re: Slackware ARM on a Raspberry Pi 3

Postby ingesi » Mon Aug 01 2016 - 13:06:17

here I have found the bug:

image rpi3-slackwarearm-install_20May16_fd.img.xz , inside initrd.gz, file /etc/rc.d/rc.dropbear , line 18:

/sbin/dropbear -b /etc/motd.net 2>> /var/log/dropbear.log

but the file /etc/motd.net doens't exists, so dropbear doesn't start

Kind regards

Alessandro Barisone

User avatar
Ilgar
Registered user
Registered user
Posts: 9
Joined: Tue Aug 23 2016 - 22:06:56

Re: Slackware ARM on a Raspberry Pi 3

Postby Ilgar » Tue Aug 23 2016 - 22:14:58

Hi all,

Is there something wrong with the

Code: Select all

rpi3-slackwarearm-install_20Aug16_fd.img.xz

image file? The md5sum checks out fine but when I mount the partition, the text files like README, cmdline.txt appear to be corrupt (they look like binary files in an editor).

User avatar
glorsplitz
Registered user
Registered user
Posts: 36
Joined: Sun Aug 07 2016 - 22:54:24

Re: Slackware ARM on a Raspberry Pi 3

Postby glorsplitz » Wed Aug 24 2016 - 17:14:50

@Ilgar

I successfully followed all the instructions and have slackware 14.2 installed on my rpi3.

What do you mean when you mounted the partition?

From the Install Slackware instructions here http://rpi3.fatdog.nl/index.php?p=sdconfig it says

put your sdcard in and run
xz -dc rpi3-slackwarearm-install_20Aug16_fd.img.xz | dd of=/dev/sda bs=65536

this creates a bootable rpi sdcard used to boot the rpi to install slackware, you've done this and the files are corrupt?

User avatar
Ilgar
Registered user
Registered user
Posts: 9
Joined: Tue Aug 23 2016 - 22:06:56

Re: Slackware ARM on a Raspberry Pi 3

Postby Ilgar » Wed Aug 24 2016 - 21:52:51

@glorsplitz

I don't have my RPi3 yet; I was hoping to run the installer on my RPi2 to have the memory card ready, then I would move it to the RPi3 device when I have it (it will run on RPi2 too, I assume). Anyway, I need to do a headless install so that's why I wanted to edit the configuration files in the installer partition for network access.

Here is what I get when I probe the partition:

Code: Select all

root@ilgar:/tgz/build/sarpimg# fdisk -l
Device     Boot Start    End Sectors  Size Id Type
/dev/sde1  *       32 187519  187488 91.6M  c W95 FAT32 (LBA)

root@ilgar:/tgz/build/sarpimg# mount /dev/sde1 /mnt/cdrom/
root@ilgar:/tgz/build/sarpimg# ls /mnt/cdrom/
COPYING.linux*           bcm2708-rpi-cm.dtb*   cmdline.txt*   fixup_x.dat*  start.elf*
LICENCE.broadcom*        bcm2709-rpi-2-b.dtb*  config.txt*    initrd.gz*    start_cd.elf*
README*                  bcm2710-rpi-3-b.dtb*  fixup.dat*     kernel.img*   start_db.elf*
bcm2708-rpi-b-plus.dtb*  bcm2710-rpi-cm3.dtb*  fixup_cd.dat*  kernel7.img*  start_x.elf*
bcm2708-rpi-b.dtb*       bootcode.bin*         fixup_db.dat*  overlays/

root@ilgar:/tgz/build/sarpimg# head -n1 /mnt/cdrom/README
����[|���� ���`ꅿL�H(H�@�A<9�`�CF2�"'A�\�x�4䠕H�)�e��2,P�����L�6⚱�?e���]�j?u�4Ȅp�ϑ�4�%asM�y⥱h5���>�������G�9���iɽ�Vƭ��܍,Z�$!>��p���"x�J�hBHlY�p#g�m���H�[Æ,�\   &(0a�@,b��$d(��(�8�eiD)��#���8�|���


Other what-should-be-text-files are like that, too.

User avatar
Ilgar
Registered user
Registered user
Posts: 9
Joined: Tue Aug 23 2016 - 22:06:56

Re: Slackware ARM on a Raspberry Pi 3

Postby Ilgar » Wed Aug 24 2016 - 22:11:58

By the way, yes, I created the partition by following the instructions precisely.

User avatar
glorsplitz
Registered user
Registered user
Posts: 36
Joined: Sun Aug 07 2016 - 22:54:24

Re: Slackware ARM on a Raspberry Pi 3

Postby glorsplitz » Wed Aug 24 2016 - 23:57:30

fdisk -l /dev/mmcblk0p1
Disk /dev/mmcblk0p1: 91.6 MiB, 95993856 bytes, 187488 sectors
Disklabel type: dos

I see a most of the files you listed, doing what you did
head -n1 /boot/README
### Slackware ARM on a Raspberry Pi 3 ###

Not sure what issue you have and whatever other files could be incorrect too.

I like that idea of installing on the rpi2 to be ready for rpi3, I'm trying to get around to imaging the sdcard I seem to have setup proper in case anything gets messed up, I like this plug and play os stuff.

Let us know if you find anything or maybe someone else can provide an idea.

User avatar
Ilgar
Registered user
Registered user
Posts: 9
Joined: Tue Aug 23 2016 - 22:06:56

Re: Slackware ARM on a Raspberry Pi 3

Postby Ilgar » Thu Aug 25 2016 - 20:02:10

When did you create your partition? Did you use the image file from Aug 20th?

I am quite sure that the SD card and adapter are functioning properly. I can test them with positive results on different cards or computers. The md5sum checks out, too. It must be something in the image file.

Besides, if there were a malfunctioning of the card, adapter or even the software (xz or dd!) you'd expect it to result in a totally rubbish output. But it creates the right kind of partition with the right file and directory structure.

Perhaps something went wrong in the packaging step (an xz bug maybe???).

User avatar
glorsplitz
Registered user
Registered user
Posts: 36
Joined: Sun Aug 07 2016 - 22:54:24

Re: Slackware ARM on a Raspberry Pi 3

Postby glorsplitz » Fri Aug 26 2016 - 02:40:31

@Ilgar

You caught me, I didn't see that's updated img since 8/15 when I used rpi3-slackwarearm-install_20May16_fd.img.xz.

So I downloaded rpi3-slackwarearm-install_20Aug16_fd.img.xz,
xz -dc rpi3-slackwarearm-install_20Aug16_fd.img.xz | dd of=/dev/sdc bs=65536

fdisk /dev/sdc
Disk /dev/sdc: 7.4 GiB, 7964983296 bytes, 15556608 sectors
Device Boot Start End Sectors Size Id Type
/dev/sdc1 * 32 187519 187488 91.6M c W95 FAT32 (LBA)

mount /dev/sdc1 /mnt/tmp

ls /mnt/tmp/README
/mnt/tmp/README*

head -n1 /mnt/tmp/README
### Slackware ARM on a Raspberry Pi 3 ###

xz -V
xz (XZ Utils) 5.2.2
liblzma 5.2.2

I'm doing this on slackware 14.2 all up to date. Any of the other text files open and look ok.

Your output from head -n1 /mnt/cdrom/README looks like maybe img file.

User avatar
Ilgar
Registered user
Registered user
Posts: 9
Joined: Tue Aug 23 2016 - 22:06:56

Re: Slackware ARM on a Raspberry Pi 3

Postby Ilgar » Fri Aug 26 2016 - 08:42:05

I finally figured it out:

My laptop's card reader isn't working, so I'm using an all-in-one usb card reader. It looks like its microSD slot is borked, too:

Code: Select all

root@ilgar:~# dd if=/dev/zero of=/dev/sde
dd: writing to '/dev/sde': Input/output error
52129+0 records in
52128+0 records out
26689536 bytes (27 MB, 25 MiB) copied, 7.42965 s, 3.6 MB/s
root@ilgar:~# dd if=/dev/urandom of=/dev/sde
dd: writing to '/dev/sde': Input/output error
95409+0 records in
95408+0 records out
48848896 bytes (49 MB, 47 MiB) copied, 18.1154 s, 2.7 MB/s
root@ilgar:~# dd if=/dev/urandom of=/dev/sde
dd: writing to '/dev/sde': Input/output error
66721+0 records in
66720+0 records out
34160640 bytes (34 MB, 33 MiB) copied, 13.4677 s, 2.5 MB/s


The healthy writes are much enough to write the partition table and filesystem layout so that I get the illusion of a working device.

When I use a micrSD-to-SD adapter and the SD card slot, all works fine.

Thanks for the time you spent on this glorsplitz!

User avatar
glorsplitz
Registered user
Registered user
Posts: 36
Joined: Sun Aug 07 2016 - 22:54:24

Re: Slackware ARM on a Raspberry Pi 3

Postby glorsplitz » Sat Aug 27 2016 - 04:48:45

Good to hear you figured it out, now we can get on to Slackware ARM hardware floating point port!

User avatar
Exaga
FatDog Network Administrator
FatDog Network Administrator
Posts: 198
Joined: Wed Apr 18 2012 - 02:01:03
Location: England [UK]

Re: Slackware ARM on a Raspberry Pi 3

Postby Exaga » Sat Aug 27 2016 - 15:44:27

glorsplitz wrote:Good to hear you figured it out, now we can get on to Slackware ARM hardware floating point port!


http://rpi3.fatdog.nl/index.php?p=downloads

Knock yourself out! :D
Exaga

====
__ KEEP THE DOG ALIVE!!!
()'`; /
/\|` W00f W00f W00f
www.fatdog.eu

Return to “SARPi Project - Slackware ARM on a Raspberry Pi”

Who is online

Users browsing this forum: CommonCrawl [Bot] and 0 guests