| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
Rock64 v2.0 u-boot SPI is...
Forum: General Discussion on ROCK64
Last Post: ju0n
Today, 11:02 AM
» Replies: 0
» Views: 53
|
Libby - ebook reader that...
Forum: PineNote Software
Last Post: kiwigoldfish
Yesterday, 04:41 PM
» Replies: 6
» Views: 4,015
|
Pinephone software
Forum: General Discussion on PinePhone
Last Post: Csanderson0313
Yesterday, 08:23 AM
» Replies: 0
» Views: 92
|
PineNote v1.2 - Charges N...
Forum: General Discussion on Pinebook Pro
Last Post: ttsp
07-02-2026, 02:52 AM
» Replies: 0
» Views: 198
|
How to change the PineNot...
Forum: General Discussion on PineNote
Last Post: cameronharring
07-01-2026, 12:22 PM
» Replies: 0
» Views: 105
|
PinePhone Pro disable Vol...
Forum: PinePhone Pro Hardware
Last Post: FR_IV
07-01-2026, 10:53 AM
» Replies: 1
» Views: 1,576
|
Star64/Starpro64 kernel b...
Forum: General
Last Post: tgbgreen
06-30-2026, 12:17 PM
» Replies: 1
» Views: 2,187
|
Manjaro affected by Arch ...
Forum: General
Last Post: tantamount
06-28-2026, 10:45 AM
» Replies: 0
» Views: 257
|
Fix Bricked SPI Flash, Pi...
Forum: PinePhone Pro Hardware
Last Post: FR_IV
06-27-2026, 05:00 PM
» Replies: 0
» Views: 184
|
irradium (based on crux l...
Forum: Linux on RockPro64
Last Post: mara
06-27-2026, 04:09 PM
» Replies: 12
» Views: 19,661
|
|
|
System hang when login ubuntu desktop with NVMe SSD plugged |
|
Posted by: chiang404 - 12-06-2018, 05:30 AM - Forum: General Discussion on ROCKPRO64
- Replies (9)
|
 |
Good day,
When I login Ubuntu desktop, the OS hanged and the PCIe slot power seemed turned off (NVMe SSD LED was off ).
If I unplug the NVMe SSD from the PCIe slot and boot into OS, it was successfully login into desktop and all was normal.
The NVMe SSD can be recognized and normally operated under Ubuntu OS without desktop.
The system would hang during booting or login after installing desktop (I have tried gnome、mate、lxde、xfce...).
I want to use NVMe SSD as my storage under desktop environment (GUI).
If any setting is necessary for installing desktop environment I lost ?
Any one has the same issue or can help with your experience ?
PS. The OS image is the latest release in wiki. The board is ROCKPro64 V2.1.
Thanks!
|
|
|
|
| Rockpro64 NFS root mount (kernel 4.20) - ethernet help? |
|
Posted by: tenspd137 - 12-06-2018, 01:14 AM - Forum: Linux on Pine A64(+)
- No Replies
|
 |
Hi all
Does anyone have any hints on how to get an NFS mount working? I am using kernel 4.20 since it recently had rockpro64 support added. My kernel parameters look like the following:
console=ttyS2,1500000 earlycon=uart8250,mmio32,0xff1a0000 root=/dev/nfs rw nfsroot=10.10.0.1:/export/sysroot,proto=tcp,vers=3 ip=10.10.0.2:10.10.0.1::255.255.255.0:rockpro64:eth0:off raid=noautodetect nfsrootdebug
and I am loading my kernel and kicking it off from u-boot with:
tftpboot 0x2000000 <kernel Image>
tftpboot 0x20000000 rk3399-rockpro64.dtb
booti 0x2000000 - 0x20000000
The NFS debug spits out:
NFS: nfs mount opts='vers=2,udp,rsize=4096,wsize=4096,proto=tcp,vers=3,nolock,addr=10.10.0.1'
NFS: parsing nfs mount option 'vers=2'
NFS: parsing nfs mount option 'udp'
NFS: parsing nfs mount option 'rsize=4096'
NFS: parsing nfs mount option 'wsize=4096'
NFS: parsing nfs mount option 'proto=tcp'
NFS: parsing nfs mount option 'vers=3'
NFS: parsing nfs mount option 'nolock'
NFS: parsing nfs mount option 'addr=10.10.0.1'
NFS: MNTPATH: '/export/sysroot'
NFS: sending MNT request for 10.10.0.1:/export/sysroot
NFS: failed to create MNT RPC client, status=-101
NFS: unable to mount server 10.10.0.1, error -101
I am not convinced that the network interface is coming up. For starters, I never see anything like the following on the console:
IP-Config: Complete:
device=eth0, addr=192.168.1.100, mask=255.255.255.0, gw=255.255.255.255,
host=myboard, domain=, nis-domain=(none),
bootserver=255.255.255.255, rootserver=255.255.255.255, rootpath=
which is what I thought using the ip= parameter was supposed to do and when I turn on:
rpcdebug -m nsfd all
rpcdebug -m rpc all
and watch /var/log/messages on my server, nothing happens - it looks like my devices aren't talking.
I assumed that the in kernel realtek drivers would be sufficient, but I noticed that in the 4.4 kernel, there is an actual rockchip ethernet driver - does that need to be used in the 4.20 kernel? I tried copying it and adding it to my config, but some of the timer interfaces changed, so it does not compile.
Any hints would be helpful.
Thanks!
|
|
|
|
| rust package not avalaible for aarch64 |
|
Posted by: erchache2000 - 12-05-2018, 05:30 PM - Forum: BSD on Pinebook
- Replies (2)
|
 |
I tried to compile firefox via pkgsrc and I can’t because rust isn’t avalaible on aarch64 arch.
Any suggestion to fix it? I’ll keep doing some research... Looking for rust compile instructions...
arm64# pwd
/usr/pkgsrc/lang/rust
arm64# cd ..
arm64# ls rust*
CVS DESCR Makefile buildlink3.mk cargo.mk distinfo files patches
arm64# ls ru
ruby/ ruby-gherkin/ ruby23-base/ runawk/
arm64# pwd
/usr/pkgsrc/lang/rust
arm64# make install
=> Bootstrap dependency digest>=20010302: found digest-20180917
ERROR: This package is not available for these platforms: NetBSD-8.99.26-aarch64.
ERROR: This package has set PKG_SKIP_REASON:
ERROR: rust-1.30.1nb1 is not available for NetBSD-8.99.26-aarch64
*** Error code 1
Stop.
make: stopped in /usr/pkgsrc/lang/rust
arm64#
|
|
|
|
| SATA issues |
|
Posted by: machina - 12-05-2018, 02:05 PM - Forum: RockPro64 Hardware and Accessories
- Replies (25)
|
 |
I'm using the RP64 with the dual SATA board to run two drives in a RAID 1 configuration. This is using OpenMediaVault 4.
The drives were seen as /dev/sda and /dev/sdb.
It was running fine for a while. And then I found that the Raid was showing as 'degraded' and only sda was showing in the Raid config. When I looked at the Disks section I found that sdb had disappeared and sdc had appeared. Using lsblk showed sdc as not having a partition.
Looking through syslog, I found this:
Code: Dec 2 09:07:45 mediavault kernel: [ 1766.245638] ata2.00: irq_stat 0x08000000, interface fatal error
Dec 2 09:07:45 mediavault kernel: [ 1766.251514] ata2: SError: { Handshk }
Dec 2 09:07:45 mediavault kernel: [ 1766.257211] ata2.00: failed command: WRITE FPDMA QUEUED
Dec 2 09:07:45 mediavault kernel: [ 1766.263010] ata2.00: cmd 61/28:00:00:70:08/06:00:01:00:00/40 tag 0 ncq 806912 out
Dec 2 09:07:45 mediavault kernel: [ 1766.263010] res 40/00:b8:00:08:09/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
Dec 2 09:07:45 mediavault kernel: [ 1766.274936] ata2.00: status: { DRDY }
Dec 2 09:07:45 mediavault kernel: [ 1766.280635] ata2.00: failed command: WRITE FPDMA QUEUED
Dec 2 09:07:45 mediavault kernel: [ 1766.286419] ata2.00: cmd 61/d8:08:28:76:08/01:00:01:00:00/40 tag 1 ncq 241664 out
Dec 2 09:07:45 mediavault kernel: [ 1766.286419] res 40/00:b8:00:08:09/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
Followed by those last four lines repeated many times. Then:
Code: Dec 2 09:07:45 mediavault kernel: [ 1766.819510] ata2.00: status: { DRDY }
Dec 2 09:07:45 mediavault kernel: [ 1766.823698] ata2: hard resetting link
Dec 2 09:07:55 mediavault kernel: [ 1776.824271] ata2: softreset failed (1st FIS failed)
Dec 2 09:07:55 mediavault kernel: [ 1776.828531] ata2: hard resetting link
Dec 2 09:08:05 mediavault kernel: [ 1786.829268] ata2: softreset failed (1st FIS failed)
Dec 2 09:08:05 mediavault kernel: [ 1786.833469] ata2: hard resetting link
Dec 2 09:08:40 mediavault kernel: [ 1821.834491] ata2: softreset failed (1st FIS failed)
Dec 2 09:08:40 mediavault kernel: [ 1821.838710] ata2: limiting SATA link speed to 3.0 Gbps
Dec 2 09:08:40 mediavault kernel: [ 1821.842808] ata2: hard resetting link
Dec 2 09:08:42 mediavault kernel: [ 1824.053694] ata2: SATA link down (SStatus 1 SControl 320)
Dec 2 09:08:42 mediavault kernel: [ 1824.058049] ata2: hard resetting link
Dec 2 09:08:45 mediavault kernel: [ 1826.265715] ata2: SATA link down (SStatus 1 SControl 320)
Dec 2 09:08:45 mediavault kernel: [ 1826.269883] ata2: limiting SATA link speed to 1.5 Gbps
Dec 2 09:08:50 mediavault kernel: [ 1831.269486] ata2: hard resetting link
Dec 2 09:08:52 mediavault kernel: [ 1833.480738] ata2: SATA link down (SStatus 1 SControl 310)
Dec 2 09:08:52 mediavault kernel: [ 1833.484879] ata2.00: disabled
Dec 2 09:08:52 mediavault kernel: [ 1833.493213] ata2: irq_stat 0x00000040, connection status changed
Dec 2 09:08:52 mediavault kernel: [ 1833.497272] ata2: SError: { CommWake DevExch }
Dec 2 09:08:52 mediavault kernel: [ 1833.501183] ata2: hard resetting link
Dec 2 09:08:53 mediavault kernel: [ 1834.382757] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dec 2 09:08:53 mediavault kernel: [ 1834.425005] ata2.00: ATA-10: ST1000LM048-2E7172, SDM1, max UDMA/133
Dec 2 09:08:53 mediavault kernel: [ 1834.429135] ata2.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Dec 2 09:08:53 mediavault kernel: [ 1834.484307] ata2.00: configured for UDMA/133
Dec 2 09:08:53 mediavault kernel: [ 1834.488274] sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Dec 2 09:08:53 mediavault kernel: [ 1834.492577] sd 1:0:0:0: [sdb] tag#0 Sense Key : 0x5 [current] [descriptor]
Dec 2 09:08:53 mediavault kernel: [ 1834.496755] sd 1:0:0:0: [sdb] tag#0 ASC=0x21 ASCQ=0x4
Dec 2 09:08:53 mediavault kernel: [ 1834.500726] sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x2a 2a 00 01 08 70 00 00 06 28 00
Dec 2 09:08:53 mediavault kernel: [ 1834.504911] blk_update_request: I/O error, dev sdb, sector 17330176
Dec 2 09:08:53 mediavault kernel: [ 1834.509051] sd 1:0:0:0: rejecting I/O to offline device
Dec 2 09:08:53 mediavault kernel: [ 1834.513001] sd 1:0:0:0: [sdb] killing request
Dec 2 09:08:53 mediavault kernel: [ 1834.516833] sd 1:0:0:0: rejecting I/O to offline device
Dec 2 09:08:53 mediavault kernel: [ 1834.520696] blk_update_request: I/O error, dev sdb, sector 16
Dec 2 09:08:53 mediavault kernel: [ 1834.524624] md: super_written gets error=-5
Dec 2 09:08:53 mediavault kernel: [ 1834.528376] md/raid1:md127: Disk failure on sdb, disabling device.
Dec 2 09:08:53 mediavault kernel: [ 1834.528376] md/raid1:md127: Operation continuing on 1 devices.
Dec 2 09:08:53 mediavault kernel: [ 1834.536240] sd 1:0:0:0: rejecting I/O to offline device
Dec 2 09:08:53 mediavault kernel: [ 1834.540072] blk_update_request: I/O error, dev sdb, sector 16
Dec 2 09:08:53 mediavault kernel: [ 1834.543942] md: super_written gets error=-5
Dec 2 09:08:53 mediavault kernel: [ 1834.547728] sd 1:0:0:0: rejecting I/O to offline device
Followed by that last line repeated many, many times. Followed by this:
Code: Dec 2 09:08:55 mediavault kernel: [ 1836.385630] ata2.00: detaching (SCSI 1:0:0:0)
Dec 2 09:08:55 mediavault kernel: [ 1836.392394] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
Dec 2 09:08:55 mediavault kernel: [ 1836.394083] sd 1:0:0:0: [sdb] Stopping disk
Dec 2 09:08:56 mediavault kernel: [ 1837.154695] scsi 1:0:0:0: Direct-Access ATA ST1000LM048-2E71 SDM1 PQ: 0 ANSI: 5
Dec 2 09:08:56 mediavault kernel: [ 1837.157630] sd 1:0:0:0: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
Dec 2 09:08:56 mediavault kernel: [ 1837.159989] sd 1:0:0:0: [sdc] 4096-byte physical blocks
Dec 2 09:08:56 mediavault kernel: [ 1837.162502] sd 1:0:0:0: [sdc] Write Protect is off
Dec 2 09:08:56 mediavault kernel: [ 1837.164634] sd 1:0:0:0: [sdc] Mode Sense: 00 3a 00 00
Dec 2 09:08:56 mediavault kernel: [ 1837.164779] sd 1:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Dec 2 09:08:56 mediavault kernel: [ 1837.734092] sd 1:0:0:0: [sdc] Attached SCSI disk
Dec 2 09:08:59 mediavault systemd-udevd[4876]: Process '/sbin/mdadm -If sdb --path platform-f8000000.pcie-pci-0000:01:00.0-ata-2' failed with exit code 1.
I have no clue what any of this means. This happened to me before, too, and I assumed it might be a disk fault and used a different (brand new) disk.
Can anyone give me some clues as to what's going on here?
|
|
|
|
| I need some summary information about hardware support by OS for a newbie |
|
Posted by: tahf - 12-04-2018, 07:38 AM - Forum: General Discussion on Pinebook
- Replies (10)
|
 |
Hello. I'm just waiting for my Pinebook. But I have some disappointment after I have read about hardware support. One linux distro doesn't support one of component, another distribution doesn't support another one.
As I see in this table, the most usable distro is KDE neon. But HDMI is not supported and GPU acceleration is marked with "?". Is there any solution to fix HDMI output on KDE Neon? Does GPU work? If yes what driver does it use: from ARM or reverse-engineered?
|
|
|
|
| Hi & some doubts |
|
Posted by: molnar - 12-04-2018, 02:18 AM - Forum: General Discussion on ROCKPRO64
- Replies (4)
|
 |
Hi everybody!!!
I just brought a RockPro64 and I have few doubts/questions.
It is absolutely necessary have an eMMC module if I want to install Android 8.x.x. or I could use it just with my SD card???
I not sure what OS I should use. I would like use my RockPro64 mostly for watch 4k/2k/1080/720 movies, Netflix/HBO/Amazon and internet navigation. What OS do you recommend me?
I was thinking in Android 8 or 7 because I know nothing about the others options (DietPi, LibreELEC, Debian, Linux, etc, etc).
Please, could you recommend me one of them?
Thanks in advance for your help.
|
|
|
|
|