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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'd like to compile the image with the buildkit - on aarch64, *not* cross compile like its setup. A lot of tools used in the bashscript are x86_64 and wont execute on my computer.
Would someone be willing to compile Slackware on Ayufan's 0.6.38 kernel and upload the iso? That kernel version is what works for my rock64. Might there be small differences between boards that makes some them not boot?
I'd like to compile the image with the buildkit - on aarch64, *not* cross compile like its setup. A lot of tools used in the bashscript are x86_64 and wont execute on my computer.
At the moment, there is no such possibility, but you can compile the kernel after the download point with the usual commands make Image; make modules; make modules_install
Quote:
Originally Posted by ansic
Would someone be willing to compile Slackware on Ayufan's 0.6.38 kernel and upload the iso? That kernel version is what works for my rock64. Might there be small differences between boards that makes some them not boot?
difference only in the amount of memory, can the bootloader be written in spi?
try erasing spi
With the latest patch the slackware managed to boot up. It did a few reboots during the boot process but then I was welcomed with a login prompt. HDMI worked well. However, after plugging USB devices, HDMI and ethernet in and out the Rock64 did reboot for a unknown reason. It wont boot up anymore. The last thing it does in the boot process is mounting memorycard. Here is the log: http://termbin.com/bgpq
Edit: After running 'fsck' on the sdcard partition Slackware created/extended the /swap on first boot then after a second boot, it managed to show the login-prompt. If the power-coord is unplugged without issuing poweroff command the next boot will get stuck in the state my dmesg show. A fsck on the partition will fix the issue. Is this behaviour expected? Thanks.
Last edited by ansic; 07-22-2018 at 01:22 PM.
Reason: New information to the problem has come
and there is an installation field there is 1 start and one overload to expand the partition on the sdcard.
i have this not observed, maybe not enough good board power or with the sdcard, try to re-record the image
I hope you read my last posts edit, I managed to boot from the sdcard by fsck:ing the partition.
I'm not statisfied with having the linux-root on a memory card, USB booting is the solution! ..but booting off USB proved to be difficult: The boot.cmd is edited to mount /dev/sda1, fstab is edited to mount it as well. boot.scr is "recompiled" with mkimage as suggested in boot.cmd. The boot process fails when it tries to re-mount the linux-root. The errors varies depending on if its Ext4 or XFS, if its the first or second try. "Synchornizing SCSI cache. USB disconnect".
you do not need to recompile boot.src, you need to add the parameter rootdev=/dev/sda1 to uEnv.txt and fix it in /etc/fstab, you also need to delete the parameter data=writeback
Multimedia
--------------
The video is played by the MPV player, which is configured with the default profile x11 (for playing divx/xvid)
and the profile rkmpp (for playing h264/h265/VP9 720p,1080p)
update:
- glibc 2.29
- kernel 4.4.172
- video hardware decoding via mpv
configured by default to output video via x11 (divx/xvid)
using profile --profile=rkmpp play video MPEG-1, MPEG-2, MPEG-4, H.263, H.264, H.265, VC-1, VP9, VP8, MVC
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
