LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - ARM
User Name
Password
Slackware - ARM This forum is for the discussion of Slackware ARM.

Notices


Reply
  Search this Thread
Old 03-23-2021, 12:10 PM   #301
sndwvs
Member
 
Registered: Aug 2014
Posts: 897

Original Poster
Rep: Reputation: Disabled

Quote:
Originally Posted by Lockywolf View Post
Well, that solution suggests that 'CONFIG_LEGACY_PTYS' should be enabled in the kernel. For some reason, at least on the sarpi64 5.9.12 kernel it is not enabled. I will try to update to the latest 5.10 in slarm64 and check.
almost everywhere off by default:
Code:
grep CONFIG_LEGACY_PTYS -r
linux-bcm2711-legacy.config:# CONFIG_LEGACY_PTYS is not set
linux-meson-sm1-legacy.config:# CONFIG_LEGACY_PTYS is not set
linux-rk3288-legacy.config:# CONFIG_LEGACY_PTYS is not set
linux-bcm2711-next.config:# CONFIG_LEGACY_PTYS is not set
linux-meson-sm1-next.config:CONFIG_LEGACY_PTYS=y
linux-rk3288-next.config:# CONFIG_LEGACY_PTYS is not set
linux-rk3308-legacy.config:# CONFIG_LEGACY_PTYS is not set
linux-rk3399-legacy.config:# CONFIG_LEGACY_PTYS is not set
linux-rk3399-next.config:CONFIG_LEGACY_PTYS=y
linux-sun50iw1-legacy.config:# CONFIG_LEGACY_PTYS is not set
linux-sun8i-legacy.config:CONFIG_LEGACY_PTYS=y
linux-sun50iw1-next.config:# CONFIG_LEGACY_PTYS is not set
linux-sun8i-next.config:# CONFIG_LEGACY_PTYS is not set
 
Old 03-23-2021, 08:02 PM   #302
Lockywolf
Member
 
Registered: Jul 2007
Posts: 490

Rep: Reputation: 130Reputation: 130
May I ask why? Stock Slackware has legacy ptys on.
 
Old 03-24-2021, 11:58 AM   #303
sndwvs
Member
 
Registered: Aug 2014
Posts: 897

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Lockywolf View Post
May I ask why? Stock Slackware has legacy ptys on.
enebled.
 
Old 04-08-2021, 06:46 PM   #305
KarlF
LQ Newbie
 
Registered: Jul 2019
Posts: 11

Rep: Reputation: Disabled
Rock64 won't boot

Hi,

I think I followed the instructions to the letter, but it will not boot:

On my linux box:
wget http://dl.fail.pp.ua/slackware/image...201029.img.zst
zstd -d slarm64-current-aarch64-base-rootfs-20201023-4.19.153-rock64-build-20201029.img.zst
dd if=slarm64-current-aarch64-base-rootfs-20201023-4.19.153-rock64-build-20201029.img of=/dev/sdd bs=1M

.. where /dev/sdd was the SD card plugged in with a USD adapter. Then I inserted the SD card into my Rock64 v2 and tried to boot. I waited more than 30 minutes, and nothing happened.

What I am doing wrong?
I did check the content of the SD card before I removed it from my linux box, and it looked OK.

Somebody posted that an eMMC module has to exist for the boot to happen. I don't have one (ordered, on its way). Is that true? Will it not boot without one?

Another source of confusion for me is the different image versions. I understand that there are at least two versions, one with XFCE, and one without graphical UI, the 'base' version, but what about all the others there?

slarm64-current-aarch64-base-rock64-4.4.254-built-*.img.zst
slarm64-current-aarch64-base-rock64-5.10.10-built-*.img.zst
slarm64-current-aarch64-base-rootfs-*-4.19.153-rock64-build-*.img.zst
slarm64-current-aarch64-enlightenment-rock64-5.10.10-built-*.img.zst
slarm64-current-aarch64-xfce-rock64-4.4.254-built-*.img.zst
slarm64-current-aarch64-xfce-rootfs-*-4.19.153-rock64-built-*.img.zst

Would someone explain how do the above differ from each-other?
Which is the best for Rock64? I will not need a GUI, because I want to use this for a server, so which of the 3 'base' versions should I use?

And what are boot-*.tar.xz files? What are those for?

Sorry for the dumb questions. I looked around a bit but I did not find any info about these.

Thanks a lot,

Karl
PS: My Rock64 boots with Armbian, but I really want to use Slackware.
 
Old 04-09-2021, 12:22 AM   #306
sndwvs
Member
 
Registered: Aug 2014
Posts: 897

Original Poster
Rep: Reputation: Disabled
Hi Karl,

is optional for eMMC to work. boot - *.tar.xz is a separately packaged bootloader (in case you need/want to update on the installed system). images are divided into basic and desktop, the difference is only in the set of packages, then they are subdivided according to the type of kernel legacy 4.4.y, mainline 5.11.y and experimental (from rockchip).

you need base images: slarm64-current-aarch64-base-rock64-5.11.11-build-20210402.img.zst or slarm64-current-aarch64-base-rock64-4.4.254-build-20210130.img.zst
then follow the instructions README.TXT

Last edited by sndwvs; 04-09-2021 at 12:25 AM.
 
1 members found this post helpful.
Old 04-09-2021, 07:52 AM   #307
shelldweller
Member
 
Registered: Mar 2019
Distribution: Freenix & Slarm64
Posts: 181

Rep: Reputation: Disabled
Your build box must be much faster than mine, you always beat me to the punch. ;-) In any case, here is a second version of LibreOffice; this one has no third party dependencies at all, and also no JDK support, just in case anyone wants to try an alternate version.

LibreOffice-7.1.2.2-aarch64-1_shldwlr.tgz
LibreOffice-7.1.2.2-aarch64-1_shldwlr.tgz.sha256
 
Old 04-09-2021, 12:06 PM   #308
KarlF
LQ Newbie
 
Registered: Jul 2019
Posts: 11

Rep: Reputation: Disabled
Quote:
Originally Posted by sndwvs View Post
Hi Karl,

is optional for eMMC to work. boot - *.tar.xz is a separately packaged bootloader (in case you need/want to update on the installed system). images are divided into basic and desktop, the difference is only in the set of packages, then they are subdivided according to the type of kernel legacy 4.4.y, mainline 5.11.y and experimental (from rockchip).

you need base images: slarm64-current-aarch64-base-rock64-5.11.11-build-20210402.img.zst or slarm64-current-aarch64-base-rock64-4.4.254-build-20210130.img.zst
then follow the instructions README.TXT
I appreciate your answer very much. I tried both those images - my rock64 v2.0 did not boot. Then, for sanity check, I flashed a new Armbian (because it worked previously), and it did NOT boot either. There is something wrong with the hardware. I read a bit on the internet and learned that rock64 has many hardware issues.

I think I am going to move on to another system. Can you please recommend another ARM device that supports Slackware? I was going to use rock64 as a router/server/openvpn. It has filled that role nicely before with Armbian, but I want to stick with Slackware. And now it seems my rock64 is broken.

Thank you!

Karl
 
Old 04-09-2021, 12:25 PM   #309
sndwvs
Member
 
Registered: Aug 2014
Posts: 897

Original Poster
Rep: Reputation: Disabled
maybe you need to erase SPI. write to the card and boot.
not bad Rock Pi E, Rock Pi 4, Station M1 and other boards on rockchip also good odroid C/CH4.
 
1 members found this post helpful.
Old 04-09-2021, 01:59 PM   #310
KarlF
LQ Newbie
 
Registered: Jul 2019
Posts: 11

Rep: Reputation: Disabled
Quote:
Originally Posted by sndwvs View Post
maybe you need to erase SPI. write to the card and boot.
not bad Rock Pi E, Rock Pi 4, Station M1 and other boards on rockchip also good odroid C/CH4.
I did erase the SPI. Didn't help.
Strange, because just before I started with Slackware, I inserted the old SD with Armbian on it, and it did start to boot. Then it ran into a problem, but I though it was a file system error. Anyway something has broken.
 
Old 04-09-2021, 05:12 PM   #311
KarlF
LQ Newbie
 
Registered: Jul 2019
Posts: 11

Rep: Reputation: Disabled
Success!

Quote:
Originally Posted by KarlF View Post
I did erase the SPI. Didn't help.
Strange, because just before I started with Slackware, I inserted the old SD with Armbian on it, and it did start to boot. Then it ran into a problem, but I though it was a file system error. Anyway something has broken.
Thank you for pointing out erasing the SPI. What finally solved my problem was point #4, "4. Fix for SPI Flashing failures" in this post: https://github.com/ayufan-rock64/lin...s/flash-spi.md

(Actually there is an error there, instead of "sudo ./rock64_erase_spi_flash.sh" the correct command is "sudo rock64_erase_spi_flash.sh"

Slackware booted, and now I am back in business.

Thanks, again,

Karl
 
1 members found this post helpful.
Old 04-09-2021, 05:50 PM   #312
mralk3
Senior Member
 
Registered: May 2015
Distribution: Slackware, OpenBSD
Posts: 1,554

Rep: Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872
If you had a u-boot prompt, it is actually better to just run:

Code:
env default -a -f
..snip..
saveenv
reset

This will get rid of your settings in SPI Flash, while still retaining the soc distributiors default u-boot that is know to work with that hardware. I made the mistake of removing the u-boot image in SPI flash and replacing it. Had a ton of problems recently due to this mistake, including USB and Serial connections. Once I restored the defaults with an upstream u-boot build, problems disappeared.
 
1 members found this post helpful.
Old 04-09-2021, 06:02 PM   #313
KarlF
LQ Newbie
 
Registered: Jul 2019
Posts: 11

Rep: Reputation: Disabled
Quote:
Originally Posted by mralk3 View Post
If you had a u-boot prompt, it is actually better to just run:

Code:
env default -a -f
..snip..
saveenv
reset

This will get rid of your settings in SPI Flash, while still retaining the soc distributiors default u-boot that is know to work with that hardware. I made the mistake of removing the u-boot image in SPI flash and replacing it. Had a ton of problems recently due to this mistake, including USB and Serial connections. Once I restored the defaults with an upstream u-boot build, problems disappeared.
Thank you, but you lost me there. Are you recommending to restore the u-boot image? I don't even know how to start. What should I do?

My original problem was that my rock64 did not boot at all. Shorting the SPI Clock pin allowed me to boot into ayufan's image, and I just followed his instructions.

Karl
 
Old 04-09-2021, 06:59 PM   #314
mralk3
Senior Member
 
Registered: May 2015
Distribution: Slackware, OpenBSD
Posts: 1,554

Rep: Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872
Once you get your sustem running again, copy over the latest u-boot from ayufan ( i think that is the spelling). Put it on the SPI flash mtd0, I think. It is basically the same thing as erasing the flash, except you are flashing it instead with a new image. From what you posted it looks like Right now your sd card has u-boot on it and that is why the sbc still boots. Just be careful not to put the wrong image, file or /dev/random onto SPI flash. You will have to jump the SPI flash again and erase it, rinse, repeat the SPI flash write.
 
1 members found this post helpful.
Old 04-09-2021, 11:25 PM   #315
shelldweller
Member
 
Registered: Mar 2019
Distribution: Freenix & Slarm64
Posts: 181

Rep: Reputation: Disabled
I am not sure if anyone here is interested in this, but I uploaded my slightly old Rock64 base image, with a 5.6.19 kernel. I am pretty sure this one boots without needing the eMMC attached, and is one of the most stable images I ever produced for the Rock64 board. The kernel is a bit outdated, but otherwise it might be worth playing around with if you are still having trouble booting the other images:

slarm64-current-aarch64-base-rootfs-20201023-5.6.19-rock64-build-20201031.img.zst
slarm64-current-aarch64-base-rootfs-20201023-5.6.19-rock64-build-20201031.img.zst.sha256
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
AArch64 kernel and modules to install Slackware ARM current on the RPi3 Exaga Slackware - ARM 27 02-07-2017 10:45 AM
LXer: ARM64/AArch64 Support Going Into Linux 3.7 Kernel LXer Syndicated Linux News 0 10-02-2012 06:20 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - ARM

All times are GMT -5. The time now is 01:31 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration