LinuxQuestions.org
Review your favorite Linux distribution.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - ARM
Reload this Page [SOLVED] Rock PI 4 RK3399 (aarch64)
User Name
Password
Slackware - ARM This forum is for the discussion of Slackware ARM.

Notices


Reply
Page 6 of 7 « First 45 6 7
  Search this Thread
Old 03-08-2020, 08:43 AM   #76
sndwvs
Senior Member
 
Registered: Aug 2014
Posts: 1,900

Original Poster
Rep: Reputation: Disabled

update:
slarm64-current-aarch64-base-rootfs-20200118-5.5.8-rock_pi_4-build-20200308.img.xz
slarm64-current-aarch64-base-rootfs-20200118-5.5.8-rock_pi_4-build-20200308.img.xz.md5
slarm64-current-aarch64-xfce-rootfs-20200118-5.5.8-rock_pi_4-build-20200308.img.xz
slarm64-current-aarch64-xfce-rootfs-20200118-5.5.8-rock_pi_4-build-20200308.img.xz.md5
 
1 members found this post helpful.
Old 04-26-2020, 03:34 PM   #77
slacksam
Member
 
Registered: Oct 2012
Location: Germany
Distribution: Slackware, Salix, slarm64
Posts: 210

Rep: Reputation: 37
Hi,
first of all, thanks for this great distribution.

After installing the current image on my Rock Pi 4A, the system runs fine, but can't detect the NVMe SSD correctly. It's detected as 1GB instead of 250GB can't be partitioned. I also tested Armbian and Manjaro, and both also show the same error. Debian 9 from the Radxa wiki page detects the SSD correctly, so it's no hardware issue.

Some time ago I reported this behavior on the Radxa forum: https://forum.radxa.com/t/hp-ssd-ex9...-1gb-only/2563.

Is it possible to fix that?
 
1 members found this post helpful.
Old 04-27-2020, 12:06 AM   #78
sndwvs
Senior Member
 
Registered: Aug 2014
Posts: 1,900

Original Poster
Rep: Reputation: Disabled
Hi, thanks.

In the official Debian 9 kernel from radxa (if it is delivered in the distribution, I think there will not be such problems, but it is very old), I do not use the extended board for m2.
try the newer kernel kernel-rk3399-5.6.7-aarch64-2mara.txz
Code:
uname -a
Linux rock-pi-4 5.6.7 #1 SMP PREEMPT Fri Apr 24 15:00:09 EEST 2020 aarch64 GNU/Linux

lsblk -o NAME,MODEL,SIZE,FSTYPE | grep nvme
nvme0n1     ADATA SX8200PNP 238.5G 
`-nvme0n1p1                 238.5G xfs

fdisk -l /dev/nvme0n1
Disk /dev/nvme0n1: 238.49 GiB, 256060514304 bytes, 500118192 sectors
Disk model: ADATA SX8200PNP                         
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 93946329-44B1-2E46-BDF4-AD9E1D6B55B2

Device         Start       End   Sectors   Size Type
/dev/nvme0n1p1  2048 500118158 500116111 238.5G Linux filesystem
 
Old 04-27-2020, 03:16 AM   #79
slacksam
Member
 
Registered: Oct 2012
Location: Germany
Distribution: Slackware, Salix, slarm64
Posts: 210

Rep: Reputation: 37
Thanks for quick reply and the update.

I did the kernel upgrade, but it still fails detecting the NVMe device:
Code:
✔ ⬐ root@rock-pi-4 ~
# uname -a
Linux rock-pi-4.fritz.box 5.6.7 #1 SMP PREEMPT Sat Apr 25 16:24:36 EEST 2020 aarch64 GNU/Linux
✔ ⬐ root@rock-pi-4 ~
# nvme list
Node             SN                   Model                                    Namespace Usage                      Format           FW Rev  
---------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- --------
/dev/nvme0n1     1234   010008A000000 SM2263                                   1           1.07  GB /   1.07  GB    512   B +  0 B   0350
✔ ⬐ root@rock-pi-4 ~
# lsblk -o NAME,MODEL,SIZE,FSTYPE | grep nvme
nvme0n1     SM2263        1024M
✔ ⬐ root@rock-pi-4 ~
# fdisk -l /dev/nvme0n1
Disk /dev/nvme0n1: 1023.102 MiB, 1073741312 bytes, 2097151 sectors
Disk model: SM2263  
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
✔ ⬐ root@rock-pi-4 ~
# cat /boot/uEnv.txt
verbosity=4
console=both
fdtfile=rk3399-rock-pi-4.dtb
rootdev=/dev/mmcblk1p1
✔ ⬐ root@rock-pi-4 ~
#
 
Old 04-27-2020, 08:01 AM   #80
sndwvs
Senior Member
 
Registered: Aug 2014
Posts: 1,900

Original Poster
Rep: Reputation: Disabled
I think it will be useful to dmesg after loading
Last edited by sndwvs; 04-27-2020 at 08:15 AM.
 
1 members found this post helpful.
Old 04-27-2020, 10:10 AM   #81
slacksam
Member
 
Registered: Oct 2012
Location: Germany
Distribution: Slackware, Salix, slarm64
Posts: 210

Rep: Reputation: 37
Attached dmesg outputs from Slarm64 and Debian.
Attached Files
File Type: txt dmesg-slarm64--2020-04-27--17-00.txt (41.0 KB, 13 views)
File Type: txt dmesg-debian--2020-04-27--17-00.txt (68.8 KB, 13 views)
 
1 members found this post helpful.
Old 04-29-2020, 04:54 AM   #82
slacksam
Member
 
Registered: Oct 2012
Location: Germany
Distribution: Slackware, Salix, slarm64
Posts: 210

Rep: Reputation: 37
Now I got a "WD Blue NVMe SSD" and it's being detected correctly:
Code:
✔ ⬐ root@rock-pi-4 ~
# nvme list
Node             SN                   Model                                    Namespace Usage                      Format           FW Rev  
---------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- --------
/dev/nvme0n1     19494L653283         WDC WDS500G2B0C-00PXH0                   1         500.11  GB / 500.11  GB    512   B +  0 B   211070WD
✔ ⬐ root@rock-pi-4 ~
# lsblk -o NAME,MODEL,SIZE,FSTYPE | grep nvme
nvme0n1     WDC WDS500G2B0C-00PXH0 465.8G 
✔ ⬐ root@rock-pi-4 ~
# fdisk -l /dev/nvme0n1
Disk /dev/nvme0n1: 465.78 GiB, 500107862016 bytes, 976773168 sectors
Disk model: WDC WDS500G2B0C-00PXH0                  
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x75d4ac79
✔ ⬐ root@rock-pi-4 ~
#
Attached Files
File Type: txt dmesg-slarm64--2020-04-29--11-56.txt (39.9 KB, 12 views)
Last edited by slacksam; 04-29-2020 at 05:00 AM. Reason: Attached dmesg output
 
Old 04-29-2020, 05:13 AM   #83
sndwvs
Senior Member
 
Registered: Aug 2014
Posts: 1,900

Original Poster
Rep: Reputation: Disabled
slacksam, thanks.

there may be a problem with the specific implementation of the SM2263 controller and the kernel driver
 
1 members found this post helpful.
Old 04-29-2020, 09:45 AM   #84
aaditya
Member
 
Registered: Oct 2013
Location: India
Distribution: Slackware
Posts: 272
Blog Entries: 2

Rep: Reputation: 85
I think its related to u-boot. Came across a thread at Radxa forum with similar issue:
https://forum.radxa.com/t/m-2-nvme-i...ntu-server/698

This is for Intel 660P SSD which uses the same SM2263 controller. Radxa fixed it by making some changes to the bootloader:
https://forum.radxa.com/t/m-2-nvme-i...-server/698/16

Looking at their u-boot source, these seem to be the relevent commits:
https://github.com/radxa/u-boot/comp...355aa58902abb6
 
1 members found this post helpful.
Old 04-29-2020, 11:44 AM   #85
sndwvs
Senior Member
 
Registered: Aug 2014
Posts: 1,900

Original Poster
Rep: Reputation: Disabled
then you need to try with the bootloader from radxa
 
2 members found this post helpful.
Old 07-05-2020, 08:32 PM   #87
verndog
Member
 
Registered: Oct 2007
Posts: 278

Rep: Reputation: 67
Quote:
Originally Posted by sndwvs View Post
I'm very interested in buying this. It appears better than Raspberry Pi 4.
 
Old 08-21-2020, 02:50 PM   #89
aaditya
Member
 
Registered: Oct 2013
Location: India
Distribution: Slackware
Posts: 272
Blog Entries: 2

Rep: Reputation: 85
Hi Mara,

The Xfce image with mainline kernel is missing from the OSDN mirror. Could you please add it?
Thanks!

https://osdn.net/projects/slarm64/st...ges/rock_pi_4/
 
Old 08-22-2020, 02:23 AM   #90
sndwvs
Senior Member
 
Registered: Aug 2014
Posts: 1,900

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by aaditya View Post
Hi Mara,

The Xfce image with mainline kernel is missing from the OSDN mirror. Could you please add it?
Thanks!

https://osdn.net/projects/slarm64/st...ges/rock_pi_4/
it looks like the volume exceeds the allowed size, I made an ticket, let's see if the limit will be increased or not.

raised the quota
Storage capacity increased to 100GB
Last edited by sndwvs; 08-22-2020 at 06:50 AM.
 
1 members found this post helpful.
  


Reply
Page 6 of 7 « First 45 6 7



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
[SOLVED] ROCKPro64 RK3399 (aarch64) sndwvs Slackware - ARM 36 12-07-2021 09:24 AM
Video : RecalBox on the Rock Pi 4 (and other RK3399 boards) NicoD SBC Linux - Embedded & Single-board computer 2 02-01-2019 08:05 AM
ROCK-esque "distro", but not ROCK? piete Linux - Distributions 5 08-21-2006 04:41 PM
Rock Linux -- does it rock ?? rolando Linux - Distributions 2 10-10-2004 01:52 PM

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

All times are GMT -5. The time now is 03:38 AM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
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