Slackware - ARMThis forum is for the discussion of Slackware ARM.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
The SOC is a lot different and the core is a 64bit ARMv8 cortex-A53. I've not yet played with any 64 bit arm machines, nor have I documented myself so I don't know if 64 bit ARM supports running 32bit code like x86_64 or if it's a pure 64bit architecture like IA64. If it's a pure 64bit architecture we're stuck until we get an arm64 slackware port, else we can probably use the 32bit slackwarearm userland.
I did a quick search and according to Linaro "ARM’s new 64-bit architecture is fully compatible with its 32-bit architecture. This means that if the processor is running on a 64-bit enabled operating system, the processor is able to run unmodified ARMv7 32-bit binaries" ... my bet is that the RPi3 can tun the slackwarearm userland provided you fetch a kernel that will boot.
It is still with the broadcom chipset though. I'm growing tired of dealing with this proprietary nonsense.
Alternatively I'm waiting for the pine64 boards to ship. This board costs less and is more open.
I'm growing tired of dealing with this proprietary nonsense.
Alternatively I'm waiting for the pine64 boards to ship. This board costs less and is more open.
I have been quickly browsing Pine64 website (admittedly too quickly! ) and didn't find much in terms of openness. Found some references to DRM, secure boot, "can run Netflix", OpenGL ES, hardware support for H265, H264...
Have they claimed somewhere that all this comes Open Source, with no proprietary blob, no proprietary/closed firmware to handle the secure boot and trusted zone stuff?
I have also found some info regarding partial open-sourcing and/or reverse engineering of Allwinner VPU drivers but don't know if it applies also to the more recent Allwinner64 bit SOCs.
Any shed of light or pointer would be much appreciated!
Had to plug into my TV since I haven't had a monitor in years. It wouldn't accept the root password listed with the latest minirootfs so I had to blank it out. Then plugged into the network and couldn't login and remembered ssh doesn't allow blank passwords by anymore. So brought it back down to the TV and booted again and set a password and logged out and back in to test it then back upstairs to a network jack and ssh still won't let me login. Now I remember it won't allow root by default so have to bring it back down and create another account or change the default.
Ok, so finally up and running, although just minirootfs
Raspberry Pi 2 nbench:
Code:
BYTEmark* Native Mode Benchmark ver. 2 (10/95)
Index-split by Andrew D. Balsa (11/97)
Linux/Unix* port by Uwe F. Mayer (12/96,11/97)
TEST : Iterations/sec. : Old Index : New Index
: : Pentium 90* : AMD K6/233*
--------------------:------------------:-------------:------------
NUMERIC SORT : 260.81 : 6.69 : 2.20
STRING SORT : 25.185 : 11.25 : 1.74
BITFIELD : 7.4797e+07 : 12.83 : 2.68
FP EMULATION : 48.977 : 23.50 : 5.42
FOURIER : 258.34 : 0.29 : 0.17
ASSIGNMENT : 4.6781 : 17.80 : 4.62
IDEA : 690.67 : 10.56 : 3.14
HUFFMAN : 384.98 : 10.68 : 3.41
NEURAL NET : 0.40163 : 0.65 : 0.27
LU DECOMPOSITION : 12.853 : 0.67 : 0.48
==========================ORIGINAL BYTEMARK RESULTS==========================
INTEGER INDEX : 12.419
FLOATING-POINT INDEX: 0.502
Baseline (MSDOS*) : Pentium* 90, 256 KB L2-cache, Watcom* compiler 10.0
==============================LINUX DATA BELOW===============================
CPU : 4 CPU ARMv7 Processor rev 5 (v7l)
L2 Cache :
OS : Linux 3.18.9-v7-arm
C compiler : gcc version 5.3.1 20160205 (GCC)
libc : libc-2.22.so
MEMORY INDEX : 2.783
INTEGER INDEX : 3.359
FLOATING-POINT INDEX: 0.278
Baseline (LINUX) : AMD K6/233*, 512 KB L2-cache, gcc 2.7.2.3, libc-5.4.38
Raspberry Pi 3 nbench:
Code:
BYTEmark* Native Mode Benchmark ver. 2 (10/95)
Index-split by Andrew D. Balsa (11/97)
Linux/Unix* port by Uwe F. Mayer (12/96,11/97)
TEST : Iterations/sec. : Old Index : New Index
: : Pentium 90* : AMD K6/233*
--------------------:------------------:-------------:------------
NUMERIC SORT : 685.21 : 17.57 : 5.77
STRING SORT : 69.869 : 31.22 : 4.83
BITFIELD : 1.9941e+08 : 34.21 : 7.14
FP EMULATION : 127.3 : 61.08 : 14.09
FOURIER : 673.65 : 0.77 : 0.43
ASSIGNMENT : 10.549 : 40.14 : 10.41
IDEA : 2037.1 : 31.16 : 9.25
HUFFMAN : 856.88 : 23.76 : 7.59
NEURAL NET : 1.0111 : 1.62 : 0.68
LU DECOMPOSITION : 31.179 : 1.62 : 1.17
==========================ORIGINAL BYTEMARK RESULTS==========================
INTEGER INDEX : 31.960
FLOATING-POINT INDEX: 1.262
Baseline (MSDOS*) : Pentium* 90, 256 KB L2-cache, Watcom* compiler 10.0
==============================LINUX DATA BELOW===============================
CPU : 4 CPU ARMv7 Processor rev 4 (v7l)
L2 Cache :
OS : Linux 4.1.18-v7+
C compiler : gcc version 5.3.1 20160205 (GCC)
libc : libc-2.22.so
MEMORY INDEX : 7.110
INTEGER INDEX : 8.693
FLOATING-POINT INDEX: 0.700
Baseline (LINUX) : AMD K6/233*, 512 KB L2-cache, gcc 2.7.2.3, libc-5.4.38
I got a RPi 3 for a friend of mine a couple of days ago and he got it running with Raspbian for RPi2 32bit.
Then he told me yesterday he got Debian for ARM64 DVDs to play with.
I presume future SlackwareARM will also feature a 32 & 64 builds ?
One step forward, two back.
I had written the rasbain image to my microsd to test the Pi3 and it only made a 1.2G partition so that filled up real quick. I tried to dd it to a USB flash drive and boot from it and it just panics then. Tried again by creating my own partition and then extracting the Slackware miniroot and it just panics as well. Seems there is something missing.
Got it going again, must have been a pebcak error.
Then plugged into the network and couldn't login and remembered ssh doesn't allow blank passwords by anymore. So brought it back down to the TV and booted again and set a password and logged out and back in to test it then back upstairs to a network jack and ssh still won't let me login. Now I remember it won't allow root by default so have to bring it back down and create another account or change the default.
Ok, so finally up and running, although just minirootfs
Thanks, that might save me some time since that is typically something I could do :-P
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
) and didn't find much in terms of openness. Found some references to DRM, secure boot, "can run Netflix", OpenGL ES, hardware support for H265, H264...
