Меню Рубрики

Установка slackware на raspberry pi

Slackware ARM on the Raspberry Pi 1

Since there are so many ARM devices coming on to the market, it is not possible to provide support for them all in the main tree.

The Raspberry Pi is supported outside of the official Slackware ARM tree by the Slackware community.

Slackware releases 13.37, 14.0, 14.2

Since the release of Slackware ARM 14.0, there have been a number of community efforts to bring Slackware to the device:

Slackware ARM 14.2 is the only available version of Slackware that is officially supported/maintained, that runs on the Raspberry Pi 1. Releases of Slackware ARM greater than version 14.2 are not backwards compatible, since they moved to a hard floating point ABI and has a minimum CPU requirement of ARMv7. The Raspberry Pi 1 only has ARMv6 architecture.

You should follow one of the links in the table below. Each is maintained by a separate author as part of the Slackware-on-Raspberry Pi community.

Site Slackware versions Using official Slackware packages Installation methods Notes
SARPi Project 14.2 Yes Slackware installer An end-to-end HOW TO tutorial taking you through the installation and setup process.
Stanley Garvey 14.0 Yes Slackware installer & pre-made images Pre-made installed OS images ready to copy to an SD card
Dave’s Collective 13.37 Yes Slackware installer An excellent set of instructions in order to have Slackware ARM running on your Raspberry Pi.

Manual installation method

Although the community does its best to keep up with the hardware changes there may be times when the above notes and images are unusable. If this happens you may work around the problem by using a miniroot image and a functional boot partition from some other source (like borrowing them from rasbian). If the kernel is the only issue you can compile your own kernel from sources (see here for a guide on doing that http://elinux.org/RPi_Kernel_Compilation).

Here are the steps involved in setting up a minimal Slackware ARM system from a miniroot image:

Download the current stable raspbian image from http://www.raspberrypi.org/downloads Unzip it and mount the partitions therein via loopback and then put all that is needed in a tarball for later use:

Please note the sectors of the beginning of the partitions: 8192 and 137216. We need to multiply these by 512 to get the byte offset for the loop device setup. This is done by $((8192 * 512)) and $((137216 * 512)). You will need to change these if the image partitioning scheme changes.
Now partition and format an SD like this: (NB the “fdisk -l” is just to show how I partitioned my SD)

It’s not a typo I got a bad headache figuring out why it did not work: the boot partition is to me made with id “c” but such small partitions have issues when you try to make a fat32 filesystem on them, you will get an error lamenting some issue with insufficient clusters but some sort of filesystem is made and if you ignore that and proceed you end up with something that does not boot. What you need to do is actually tell mkdosfs to make a fat16 filesystem and then things start to work right.

Now you can extract the Slackware ARM miniroot and then the raspbian_boot_stuff.tgz in /mnt/hd.
Edit the /mnt/hd/boot/cmdline.txt and add at the end “ro” and check that the root parameter matches the partitioning of the SD.
Edit the fstab to match your formatting (if that was like I suggested it will look like this:)

You can now umount the SD, insert it into the RasbberyPI and boot into your Slackware ARM miniroot to add whatever else you need.
I generally add whatever else I need by simply using wget to pull down slackpkg, installing manually the downloaded slackpkg, editing the mirrors file and then install the rest that’s needed with slackpkg itself (internet connection is required for this).
You might want to edit or comment the serial console in inittab to suppress the “s0” respawning to fast message.

Incidentally if you download a recent version of raspbian this procedure will create bootable images for the RPi, RPi 2, RPi 3, and RPi Zero.


Установка slackware на raspberry pi

Your SD Card is ready so you can insert it in the Raspberry Pi and boot.

You can connect remotely to your Raspberry Pi as root through SSH.

As soon as you are logged, you might want to install additional Slackware ARM packages:

5. Tips and tricks

5.1. Bluetooth

The Raspberry Pi has a Broadcom chip providing Bluetooth. However, the required firmware is not installed on Slackware ARM. It means that you need to download and install it:

Then build your own Slackware ARM bluez-firmware-brcm package and install it.

In order to enable Bluetooth you need to add the Bluetooth module, run the Bluetooth daemon, attach the device then open and initialize the device. Add the following lines to the end of the /etc/rc.d/rc.local file:

Remark: Sometimes there is a failure with the hciattach command so that is why you need a while .

You can check that Bluetooth is working by typing:

Now, the Bluetooth is correctly set.

5.2. Keyboard

The default keyboard map on Slackware ARM is the one of United Kingdom. If you want to load an other keyboard map, edit the /etc/rc.d/rc.keymap file.

If you want to change the keyboard layout for X11, you need to copy the X11 configuration file then edit it:

Now, the keyboard is correctly set.

5.3. Memory

You can check the current memory by typing:

Now, the memory is correctly set.

5.4. Processor

Now, the processor is correctly set.

5.5. Time

Unfortunately, the Raspberry Pi does not provide a Real-Time Clock (RTC). That is why there is no battery included with the board. It means that each time you shutdown the Raspberry Pi, the time is reset! However, if you have internet access, you can update the time during the Slackware ARM boot. Add the following line to the end of the /etc/rc.d/rc.local file:

Now, the time is correctly set.

Unfortunately, the Raspberry Pi is not compatible with OpenGL (it is compatible with OpenGL ES that is a subset of OpenGL). It means that, by default, each application requiring OpenGL will be slow. However, you can reach 60 FPS with OpenGL applications on the Raspberry Pi by using the correct driver.

Firstly, you need to build Mesa (>= 17.1.10) with the VC4 DRI driver:

Then build your own Slackware ARM mesa package and install it (you can safely upgrade the one provided by Slackware ARM).

Secondly, add the following line to the end of the /boot/config.txt file:

Then reboot the Raspberry Pi.

You can check that you are able to get 60 FPS with OpenGL applications on the Raspberry Pi by typing the following command in an X11 terminal:

An other problem with the video is that the default resolution is 1824×984. It means that you can see black borders around your 1920×1080 screen. In order to fix that, add the following line to the end of the /boot/config.txt file:

Then reboot the Raspberry Pi.

You can check that you are using a 1920×1080 resolution on the Raspberry Pi by typing the following command in an X11 terminal:

Now, the video is correctly set.

5.7. UART

In the /etc/inittab file, s0 refers to the mini UART that is disabled by default on the Raspberry Pi. Consequently, every 5 minutes, this line will be written to /dev/tty1 by the init process:

An easy fix is to edit the /etc/inittab file and replace the following line:

Then reboot the Raspberry Pi. Now, the UART is correctly set.


Tuesday 31 March 2020 — 06:19:08

Slackware ARM on a Raspberry Pi

Welcome to SARPi

The SARPi Project promotes and supports Slackware ARM Linux on a Raspberry Pi. A step-by-step, end-to-end, ‘HOW TO Install Slackware ARM on a Raspberry Pi’ tutorial is available, with purpose-built Slackware ARM installer images and packages. SARPi supports Slackware ARM -current hard float port and Slackware ARM 14.2 soft float port versions. The SARPi installer image (.xz) archives, /boot partition files (.zip) archives, and (.txz) packages, are available from the Downloads page. The Mini Projects page contains fun and educational things to do after the Slackware ARM OS has been installed, which includes a guide on Monitoring & Solving Thermal [Overheating] Issues on a Raspberry Pi.

To start the SARPi ‘How To install Slackware ARM on a Raspberry Pi’ tutorial, click [Install Slackware] on the left menu. Or, for less detailed instructions, see the SARPi.README which accompanies each installer image.

Use the menu links on the left to navigate around the website and/or any text links on the page(s).

Important: Development of Slackware ARM 14.2 related software by the SARPi Project is being phased out and further updates — from 24 January 2020 — will be to fix any problems which may arise or exist in the currently available SARPi files! This will only affect Raspberry Pi (1) users. For the Raspberry Pi 2, 3, and 4 you can install Slackware ARM -current to keep updated.

It’s taken for granted that those using this website are not complete novices to Linux, or the Raspberry Pi. Although, you may find it easy to follow even if you’ve not spent that much time in a Linux shell. Whether you’re a beginner or an expert in Linux, or the Raspberry Pi, it’s certainly worth giving Slackware ARM a try. For further information click the [About Slackware] link on the left menu.

The SARPi Project is a community effort by SARPi.FatDog.EU and is not officially endorsed by Slackware Linux Inc. or the Raspberry Pi Foundation.

Slackware Linux Wallpaper

Download a FREE Slackware Linux wallpaper for your desktop. It’s called Slacksplash and was created using a free wallpaper, and a 3-D Slackware logo, both downloaded from Google. It’s simple and effective, yet quite eyecatching, and of course totally cool!

Please take time to visit.

Slackware.uk — Slackware Linux mirror services.

Acknowledgements & Thanks

SARPi.FatDog.EU would like to offer our gratitude to all those who’ve had input into the SARPi project. As well as all those who share their ideas, their work, and their experiences with Slackware (e.g. on SlackDocs) which continues to be an asset.

Special thanks to Patrick Volkerding and the entire Slackware Team for a truly wonderful OS; especially MoZes for his ceaseless efforts towards the Slackware ARM port. Additional thanks goes to alienBOB and Ponce (along with many others) for their SlackBuild scripts. Thanks to the online community of Slackers at LinuxQuestions.org for all the constructive input and feedback, and to Mr Jackson («Get the beers in?») for all the helpful advice and testing. Much respect and kudos to Dave Spencer @ Dave’s Collective whose work has profoundly inspired and motivated us over the years (particularly when the SARPi Project was in its infancy) and still does! Without you, and people like you, the entire SARPi Project would not be where it is today!

THANK YOU ALL! Updated: 28 Feb 2020 16:48:24

Disclaimer: The SARPi Project website is for non-commercial and general information purposes only. The content is provided by SARPi.FatDog.EU and while we endeavour to keep information up to date and correct, we make no representations or warranties of any kind, express or implied, about the completeness, accuracy, reliability, suitability or availability with respect to the website or any information, software, products, services, or related graphics which is available on the website for any purpose. Any reliance you place on such information is therefore strictly at your own risk. In no event will SARPi.FatDog.EU be liable for any loss or damage including without limitation, indirect or consequential loss or damage, or any loss or damage whatsoever arising from loss of data or profits arising out of, or in connection with, the use of this website or any of its contents. Through this website you are able to visit other websites which are not under our control. SARPi.FatDog.EU has no influence over the nature, content or availability of any external URLs. The inclusion of any URLs does not necessarily imply a recommendation or endorsement of any content therein. Every effort is made to ensure the SARPi Project website remains accessible. However, SARPi.FatDog.EU takes no responsibility for, and will not be liable for, the SARPi Project website being temporarily unavailable due to technical issues beyond our control. SARPi.FatDog.EU is in no way affiliated with Slackware Linux, Inc, or the Linux Foundation, or the Raspberry Pi Foundation, or any of their members, trustees, partners, or associates.

Linux® is the registered trademark of Linus Torvalds.

Raspberry Pi™ and the Raspberry Pi logo ™ are trademarks of the Raspberry Pi Foundation.


Установка slackware на raspberry pi

Slackware ARM on a Raspberry Pi 3

Slackware ARM on a Raspberry Pi 3 — SARPi3

Slackware ARM RPi3 installer image archive (.xz) and individual system packages (.tgz) are available on the downloads page.

This website supports Slackware ARM Linux on a Raspberry Pi 3 and is intended as a reference and tutorial. As such, it is a community effort by fatdog.eu and is not officially endorsed by Slackware Linux Inc. or the Rabsperry Pi Foundation.

Re: Slackware ARM on a Raspberry Pi 3

Re: Slackware ARM on a Raspberry Pi 3

I’m not sure what you mean by «being regularly updated». It’s an installer which doesn’t really need updating. After it’s been built and configured for the RPi3 it should work forever. If you mean «Is Slackware being regularly updated?» then the answer is «Yes of course!» The much anticipated Slackware 14.2 release is imminent and expected any day now.

Once Slackware ARM is installed, updates to the latest 4.x kernel(s) and firmware can done via rpi-update, or manually. Updates to the Slackware ARM system and packages can be downloaded, and then installed manually using ‘pkgtools’ or via the package manager ‘slackpkg’. Slackware ARM package updates are very frequent. Keeping Slackware up-to-date is the job of the system admin, not the installer we’ve provided.

If you’re asking, «Is it possible to install the latest version of Slackware ARM on the RPi3 using this installer?» then the answer would be «Yes, of course!» You can install and run any version of Slackware ARM on the RPi3 using this installer, as long as the source is available.

Re: Slackware ARM on a Raspberry Pi 3

Slackware is most likely _NOT_ going to interest most of you on this forum. If your experience with Linux systems amounts to point-n-clicking then you will be in for a surprise. Slackware is command-line based. It’s the most ‘UNIX-like’ Linux distro available. It’s also THE BEST educational tool you will find on any Linux platform and on that basis Slackware remains peerless. If you really want to know and learn about Linux then Slackware is something you should seriously consider using. There really is no better learning-curve available on any other Linux-based system than Slackware.

It still amazes me that Slackware, being one of the most powerful, stable, and secure Linux distros available, has not been embraced more by Raspberry Pi users in general. Maybe it’s too ‘old’ or too ‘hard’ for them, I’m not really sure. The only thing I’m certain of is that the Raspberry Pi Foundation seem to refuse to even acknowledge that Slackware exists. Given that Slackware offers the best education to Linux users and is inherently more stable and secure than most other distro’s, you’d think it was a no-brainer.

There’s an old Internet aphorism, «Use Debian and learn Debian. Use Ubuntu and learn Ubuntu. Use Slackware and learn Linux!»


Slackware 14.2 на Raspberry Pi 1 (512 Mb RAM)

Таки удалось поставить Slackware 14.2 на Raspberry Pi 1 (512 Mb RAM) благодаря наработкам проекта http://sarpi.fatdog.eu/ .

В целом работает весьма неплохо, но не на 100%. Например, нельзя запустить emacs и vim в GUI-режиме. vim автоматически выпадает в текстовый режим, а emacs начинает запускаться, но после первой отрисовки окошка портит его и висит. Можно предположить, что на Raspberry Pi 2/3 оно должно работать гораздо лучше.

А так слакбилды компиляются (понятное дело, не все), своё писать и запускать вполне можно. Но, тем, кому надо всё и сразу, Raspbian, определённо, подойдёт гораздо больше.

На скриншоте оконный менеджер mwm (The Motif Window Manager), который идёт в комплекте с библиотекой motif, три xterm’а, xcalc и PDF-файл, открытый в gv.

Что они там натворили что emacs и vim не работают?

Почему все на английском? Где божественная кои8?

Обилие ошибок «Illegal Instruction» вполне могут намекать на то, что бинарники собраны не совсем под armv6l. Впрочем, многое вполне работает. djview4 на Qt вполне собрался и работает, хотя слакбилд собрать пакет не смог — засыпался с «Illegal Instruction» на конвертировании иконок. gtk-demo стартует, но потом засыпается с «Illegal Instruction». gtk3-demo даже не стартует, сразу выпадает в «Illegal Instruction».

А почему бы не собрать под armv6l?

По ходу, после появления armv7 все дружно отвернулись от armv6 (за исключением, может быть, команды Raspbian’а), и теперь в первую очередь всё собирают именно под armv7. В инструкции сабжевого проекта при описании установки на Raspberry Pi 1 чёрным по белому прописано как удалить ядро с модулями для armv7, а потом поставить ядро для armv6, что я и сделал. Видимо, и сами оптимизированные бинарники оптимизированы под armv7. При этом это ещё stable версия. Их current ветка по их словам на armv6l вообще не должна работать:

Slackware ARM -current hard float port has a minimum CPU requirement of ARMv7-a architecture and cannot be installed on a Raspberry Pi (1) which features ARMv6 architecture. Slackware ARM -current hard float port can only be installed on a Raspberry Pi 2 and Raspberry Pi 3.

gentoo есть для таких случаев. А под старые процы и так везде прогибаются. Из-за 2 процессоров в armv7 везде используют только 16 vfp регистров и не используют neon

Не могу не спросить про KOI8-R. Впрочем слабо понимаю назначение Raspberry Pi.

я думаю лучше отжалеть денег на rpi2 ибо rpi это дикий тормоз. 2я версия намного будет приятнее в работе.

ну а там и терминалы глядишь перестанут тормозить 🙂

Почему не PuppyLinux?

SlackoPup — PuppyLinux на основе Slackware?

Я так понимаю, фон рабочего стола ест больше памяти, чем всё остальное вместе взятое (включая ядро).

Тьфу, вспомнил бмпшки на 98-й винде в десятки мегабайт съедающие всю оперативку.

а emacs начинает запускаться, но после первой отрисовки окошка портит его и висит.

А какой тулкит использовался при этом? У меня была такая же проблема с emacs-lucid на Xaw3d, но с IceWM. Запускался emacs, показывалось окно, а дальше 100% нагрузка на процессор и висит. Проблема оказалась в несколько странном минорном изменении в IceWM — он посылал ConfigureNotify, когда выставлялись WM_NORMAL_HINTS, а не должен посылать. Emacs при получении ConfigureNotify выставлял WM_NORMAL_HINTS, а IceWM снова по этому случаю отправлял синтетический ConfigureNotify. И впадаем в бесконечный цикл. Пришлось патч отправлять. Происходило это только с Emacs, другие приложения были ОК.

Кстати, бесконечный цикл обрывался, если emacs-lucid делаешь fullscreen, например.

UPD: запусти emacs с xtrace, посмотри, что прет между emacs и X-сервером, когда окошко висит.

А почему бы не собрать под i386?

GTK2. Уже писал выше, что это, по ходу, следствие оптимизации ряда бинарников под armv7.

djview4 на Qt вполне собрался и работает, хотя слакбилд собрать пакет не смог — засыпался с «Illegal Instruction» на конвертировании иконок. gtk-demo стартует, но потом засыпается с «Illegal Instruction». gtk3-demo даже не стартует, сразу выпадает в «Illegal Instruction».


Читайте также:  Установка mists of pandaria

Добавить комментарий