LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
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 09-26-2020, 04:38 AM   #16
sndwvs
Member
 
Registered: Aug 2014
Posts: 892

Original Poster
Rep: Reputation: Disabled

update:
 
Old 01-27-2021, 06:43 PM   #20
0XBF
Member
 
Registered: Nov 2018
Location: Winnipeg
Distribution: Slackware
Posts: 310

Rep: Reputation: 280Reputation: 280Reputation: 280
Hi sndwvs,

I just received my rockpro64 this week (my first arm board), and I'm trying out your slarm64 images on a micro sd to try to get slackware up and running on it. It seems that only the images with kernel 4.4.230 (2020-07-11) will run. I've tried the newer 4.4.249 and 5.9.16 images and they both hang at "Booting using the fdt blob at 0x1f00000". I'll link a picture of the boot screen at the end of this post, if it helps.

I'm new to running anything on an arm board so I'm not sure the cause but it seems to be a problem with uboot, and working with that is completely new to me. Perhaps you have an idea on what can be done to get a newer image to boot?

For now I can run with the 4.4.230 images. Both base and xfce work fine, I just need to figure out what I want to use.

That picture of the stuck boot: https://imgur.com/9S1l9BB
 
Old 01-28-2021, 01:36 AM   #21
sndwvs
Member
 
Registered: Aug 2014
Posts: 892

Original Poster
Rep: Reputation: Disabled
Hi 0XBF,

try rewriting the bootloader to the installed image on the card:
Code:
dd if=idbloader.img of=/dev/mmcblk0 seek=64 status=noxfer
dd if=u-boot.itb of=/dev/mmcblk0 seek=16384 status=noxfer
where /dev/mmcblk0 or /dev/sd? is your card with slarm64.

update:
this is a known (as it turns out the problem).
i will update the images.

Last edited by sndwvs; 01-28-2021 at 03:26 PM.
 
1 members found this post helpful.
Old 01-28-2021, 04:04 PM   #23
0XBF
Member
 
Registered: Nov 2018
Location: Winnipeg
Distribution: Slackware
Posts: 310

Rep: Reputation: 280Reputation: 280Reputation: 280
Quote:
Originally Posted by sndwvs View Post
Hi 0XBF,

try rewriting the bootloader to the installed image on the card:
Code:
dd if=idbloader.img of=/dev/mmcblk0 seek=64 status=noxfer
dd if=u-boot.itb of=/dev/mmcblk0 seek=16384 status=noxfer
where /dev/mmcblk0 or /dev/sd? is your card with slarm64.

update:
this is a known (as it turns out the problem).
i will update the images.
Thanks for the bug info sndwvs. I see you've removed the latest images already so I will wait to test your latest build once you upload it.

Downloading the new base image at the moment. Today I'm getting ~50KB/sec so it'll be a little while until I can test things

Last edited by 0XBF; 01-28-2021 at 05:29 PM. Reason: update
 
Old 01-28-2021, 09:00 PM   #24
0XBF
Member
 
Registered: Nov 2018
Location: Winnipeg
Distribution: Slackware
Posts: 310

Rep: Reputation: 280Reputation: 280Reputation: 280
A little update,

I got your latest "slarm64-current-aarch64-base-rockpro64-5.10.11-build-20210128.img.zst" image downloaded and copied to my sd card and it booted up properly. My usb keyboard plugged into the rockpro64 is working fine too. I was wondering how that would go since those bug reports were talking about breaking usb keyboard support.

Thanks for getting those new images up!
 
Old 03-09-2021, 06:55 PM   #26
mralk3
Senior Member
 
Registered: May 2015
Distribution: Slackware, OpenBSD
Posts: 1,547

Rep: Reputation: 869Reputation: 869Reputation: 869Reputation: 869Reputation: 869Reputation: 869Reputation: 869
I wasn't sure where to post this: https://www.linuxquestions.org/quest...ml#post6228925
 
Old 03-10-2021, 10:05 AM   #27
sndwvs
Member
 
Registered: Aug 2014
Posts: 892

Original Poster
Rep: Reputation: Disabled
to download and then erase the SPI use the method:
Disable SPI (while booting)
Quote:
There is a second possibility to jumper your ROCKPro64: If you mess-up your SPI and are unable to boot, jumpering pins 23 (CLK) and 25 pin (GND) on the PI-2-bus header will disable the SPI as a boot device. (This was taken from the IRC logs, 09 August 2018 @ 17:23) You have to remove the jumper 2 seconds after having started your RP64 (before the white LED turns ON) otherwise the SPI will be missing and you won't be able to flash it. Ayufan images contain (at the moment) only one script for the SPI and the RP64, it's "rockpro64_reset_spi_flash". Other SPI scripts are dedicated to the R64 (as it is written on the name) and it will mess-up your RP64 SPI if you use them.
with erasing SPI after loading
Code:
flash_erase /dev/mtd0 0 0
or by the u-boot itself
Code:
sf probe
sf erase 0 400000
 
2 members found this post helpful.
Old 03-10-2021, 10:39 AM   #28
mralk3
Senior Member
 
Registered: May 2015
Distribution: Slackware, OpenBSD
Posts: 1,547

Rep: Reputation: 869Reputation: 869Reputation: 869Reputation: 869Reputation: 869Reputation: 869Reputation: 869
After erasing SPI Flash, "env default -a ; reset", and finally booting the SD Card with slarm64, I was able to get Linux booted again. Thanks for the information. It's surprisingly difficult to glean any information about u-boot. There are so many versions and platforms that have different u-boot commands. A lot of the information I found was old, incorrect, or missing commands.
 
Old 03-13-2021, 02:20 PM   #29
mralk3
Senior Member
 
Registered: May 2015
Distribution: Slackware, OpenBSD
Posts: 1,547

Rep: Reputation: 869Reputation: 869Reputation: 869Reputation: 869Reputation: 869Reputation: 869Reputation: 869
Is there any chance that the kernel packages, firmware, and source could be refreshed?
 
Old 03-13-2021, 02:30 PM   #30
sndwvs
Member
 
Registered: Aug 2014
Posts: 892

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by mralk3 View Post
Is there any chance that the kernel packages, firmware, and source could be refreshed?
they are available
 
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
slarm64 (aarch64 unofficial slackware) sndwvs Slackware - ARM 317 Today 11:38 AM
Slackware for Firefly-RK3399 sndwvs Slackware - ARM 26 05-16-2020 06:25 AM
[SOLVED] How to install Debian onto rk3399 set top box trumpforprez Debian 1 03-23-2018 08:04 AM
LXer: Fedora 21 for AArch64 LXer Syndicated Linux News 0 01-12-2015 06:30 AM

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

All times are GMT -5. The time now is 09:22 PM.

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