| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
Thinking about memory bot...
Forum: General Discussion on Pinebook Pro
Last Post: xiley32050
09-02-2026, 01:21 AM
» Replies: 0
» Views: 114
|
Hardware Feature Suggesti...
Forum: Quartz64 Hardware and Accessories
Last Post: Independent Researcher
08-30-2026, 07:19 PM
» Replies: 0
» Views: 140
|
Single-board computers an...
Forum: General
Last Post: Spaker
08-29-2026, 08:12 PM
» Replies: 0
» Views: 151
|
Pinephone visibly losing ...
Forum: General Discussion on PinePhone
Last Post: baptx
08-29-2026, 11:18 AM
» Replies: 9
» Views: 8,506
|
Fixing the Quartz64 USB3 ...
Forum: Quartz64 Tutorials
Last Post: mig
08-28-2026, 01:32 AM
» Replies: 1
» Views: 12,835
|
Pinecil as a Pocket-Sized...
Forum: General
Last Post: Arsen
08-27-2026, 09:15 AM
» Replies: 0
» Views: 170
|
SlateOS feedback needed!
Forum: Development Discussion on PineTime
Last Post: highjumpman
08-24-2026, 08:00 AM
» Replies: 0
» Views: 287
|
Pinephone + Keyboard for ...
Forum: PinePhone Hardware
Last Post: Nambo
08-23-2026, 12:17 AM
» Replies: 18
» Views: 13,790
|
Hello, I am a new member ...
Forum: General
Last Post: WhiteRabbit0
08-20-2026, 12:17 PM
» Replies: 0
» Views: 465
|
Need help compiling andro...
Forum: Android on Pine A64(+)
Last Post: ahegarosib97
08-20-2026, 08:45 AM
» Replies: 2
» Views: 2,101
|
|
|
| Trying to update kernel |
|
Posted by: rlevensa - 03-21-2019, 12:34 PM - Forum: Linux on RockPro64
- Replies (1)
|
 |
I installed Bionic Containers aarch64 (DockerCE & Kubernetes) [microSD / eMMC Boot] [0.7.9] image. I'm booting from a microSD. I must be missing something obvious, but I can't boot to a different kernel.
The kernel install looks good.
Code: sudo apt install linux-image-4.14.0-rockchip-ayufan-136-gee91453
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
linux-image-4.14.0-rockchip-ayufan-136-gee91453
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/10.9 MB of archives.
After this operation, 41.6 MB of additional disk space will be used.
Selecting previously unselected package linux-image-4.14.0-rockchip-ayufan-136-gee91453.
(Reading database ... 48989 files and directories currently installed.)
Preparing to unpack .../linux-image-4.14.0-rockchip-ayufan-136-gee91453_0.5.15_arm64.deb ...
Unpacking linux-image-4.14.0-rockchip-ayufan-136-gee91453 (0.5.15) ...
Setting up linux-image-4.14.0-rockchip-ayufan-136-gee91453 (0.5.15) ...
update-initramfs: Generating /boot/initrd.img-4.14.0-rockchip-ayufan-136-gee91453
Creating new extlinux.conf...
Installing new extlinux.conf...
The extlinux.conf has the new kernel information.
Code: cat /boot/extlinux/extlinux.conf
timeout 10
menu title select kernel
default kernel-4.13.0-rc1-rockchip-ayufan-102-g6104f84
label kernel-4.14.0-rockchip-ayufan-136-gee91453
kernel /boot/vmlinuz-4.14.0-rockchip-ayufan-136-gee91453
initrd /boot/initrd.img-4.14.0-rockchip-ayufan-136-gee91453
devicetreedir /boot/dtbs/4.14.0-rockchip-ayufan-136-gee91453
append rw panic=10 init=/sbin/init coherent_pool=1M ethaddr=${ethaddr} eth1addr=${eth1addr} serial=${serial#} cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 root=LABEL=linux-root rootwait rootfstype=ext4
label kernel-4.14.0-rockchip-ayufan-136-gee91453-memtest
kernel /boot/vmlinuz-4.14.0-rockchip-ayufan-136-gee91453
initrd /boot/initrd.img-4.14.0-rockchip-ayufan-136-gee91453
devicetreedir /boot/dtbs/4.14.0-rockchip-ayufan-136-gee91453
append rw panic=10 init=/sbin/init coherent_pool=1M ethaddr=${ethaddr} eth1addr=${eth1addr} serial=${serial#} cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 root=LABEL=linux-root rootwait rootfstype=ext4 memtest
After rebooting, it still has the original kernel.
Quote:uname -r
4.4.132-1075-rockchip-ayufan-ga83beded8524
Thanks for any help!
|
|
|
|
| there no hdmi out on OMV |
|
Posted by: chengjianwen - 03-21-2019, 09:00 AM - Forum: General Discussion on ROCKPRO64
- No Replies
|
 |
I installed OMV, and there is no HDMI output always.
and every it crashed(I think) and can't boot again, I must install the fresh OMV again, and again.
I installed autoshutdown plugin, and the system seems never shutdown by it.
I configure the interface to WoL enabled, but I can't wake it up use a perl/python script.
the only worked component is ats, the fan worked well.
the two hard 4G disks /dev/sda and /dev/sdb always disappeared when boot the system from a long downtime.
I want to known if I shoud change to debian + samba, to let problems simply.
BTW, I use a 16GB eMMC to boot the system, and installed flash memory plugin, too.
|
|
|
|
| video not working |
|
Posted by: greenhobby - 03-21-2019, 05:56 AM - Forum: RockPro64 Hardware and Accessories
- No Replies
|
 |
Hi,
I just plugged in my RockPro64 for the first time and all is fine for a few minutes (basic Ubuntu 18 image from this site). I was able to cd around and look at things. Ran htop, etc. Then the video dies and it won't come back up (interesting, the green led on the NIC port went out as well). Tried refreshing, rebooting, checked monitor/cable on other system (fine). Any ideas on how to troubleshoot? I detect it's booting ok since keyboard and mouse are lit up after a few seconds and white light comes on.
Also, the fan purchased here does not work when plugged into the fan connector.
Thanks in advance for helping.
-gh
|
|
|
|
| HDMI 2.0a CEC compliancy issue? |
|
Posted by: Willem53 - 03-21-2019, 04:19 AM - Forum: General Discussion on ROCK64
- Replies (1)
|
 |
Hi,
my Transformer/Rock64 <-->HDMIv2.0a cable<-->AVR:Onkyo TX-NR686<-->HDMIv2.0a cable<-->LG OLED55B8PLA setup has a compliancy issue.... I think.
For CEC and ARC audioreturn to perform the Transformer/Rock64 need to be fisicaly disconnected from HDMI cable, a soon as it is connected to the AVR over HDMI the CEC and ARC fails and the LG OLED can no longer transmit sound over HDMI to the AVR for any application or service.
any suggestions or questions are welcome as I think this could be a major deal breaker.
|
|
|
|
| Rp64 my new gaming station? |
|
Posted by: NightCrawler504 - 03-20-2019, 09:24 PM - Forum: General Discussion on ROCKPRO64
- Replies (1)
|
 |
Hello everyone 
So stadia announcement is out, if everything falls down as Google expects as it probably will, even if it takes time, my power hungry gaming pc would pretty much become obsolete, just around to play some present titles that eventually will become obsolete. Should I be selling it asap?
Under that stadium I would only need a 4k streaming capable device to play online and connect to my TV, ideally it would also be low power. I think my rp64 is just the device I would be looking for. Development on Linux is starting to become enjoyable and in the future could just right about be all I need even as a desktop.
I'm curios to read what might your thoughts be, understand lag fears as well as the portion of ppl that modify their games for cheats etc but can we really fight the future, is this sbc the future of gaming next to stadia, low power consumption 4k experience gaming? Am I just dreaming, is this posible? Should I be exited? Will rp64 be part of this future?
|
|
|
|
| PCIe failure |
|
Posted by: odhinnhrafn - 03-19-2019, 02:32 PM - Forum: RockPro64 Hardware and Accessories
- Replies (11)
|
 |
Just received my RockPro64, NAS case, and all the goodies. I installed the Ubuntu Bionic LXDE image, loaded up great, added ATS, etc. Everything is great except that the 2 WD Reds are not recognized. Opening the case back up, I see that the PCIe doesn't have its LED lit up. I'm trying to decide if this is the img or the hardware. I have gotten the LED to illuminate a couple times by unplugging the SATA cables, but it doesn't stay on. Also, during boot, the LED will blink on and off, then stay off. lspci -v shows nothing, df -h / fdisk -l do not show the HDDs.
I do not have the board that requires removing a resistor.
boot log for pci:
[ 0.505675] of_get_named_gpiod_flags: parsed 'gpio' property of node '/vcc3v3-pcie-regulator[0]' - status (0)
[ 0.505723] reg-fixed-voltage vcc3v3-pcie-regulator: Looking up vin-supply from device tree
[ 0.505761] vcc3v3_pcie: supplied by dc_12v
[ 0.505828] vcc3v3_pcie: 3300 mV
[ 0.505988] reg-fixed-voltage vcc3v3-pcie-regulator: vcc3v3_pcie supplying 3300000uV
[ 1.166830] ehci-pci: EHCI PCI platform driver
[ 2.894277] vcc3v3_pcie: disabling
[ 3.257493] phy phy-pcie-phy.9: Looking up phy-supply from device tree
[ 3.257501] phy phy-pcie-phy.9: Looking up phy-supply property in node /pcie-phy failed
[ 3.260566] rockchip-pcie f8000000.pcie: GPIO lookup for consumer ep
[ 3.260590] rockchip-pcie f8000000.pcie: using device tree for GPIO lookup
[ 3.260679] of_get_named_gpiod_flags: parsed 'ep-gpios' property of node '/pcie@f8000000[0]' - status (0)
[ 3.261231] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply from device tree
[ 3.261553] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply from device tree
[ 3.261575] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply property in node /pcie@f8000000 failed
[ 3.261629] rockchip-pcie f8000000.pcie: no vpcie1v8 regulator found
[ 3.276048] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply from device tree
[ 3.276086] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply property in node /pcie@f8000000 failed
[ 3.276142] rockchip-pcie f8000000.pcie: no vpcie0v9 regulator found
[ 3.290608] rockchip-pcie f8000000.pcie: invalid power supply
[ 3.350984] PCI host bridge /pcie@f8000000 ranges:
[ 3.387121] rockchip-pcie f8000000.pcie: PCI host bridge to bus 0000:00
[ 3.394721] pci_bus 0000:00: root bus resource [bus 00-1f]
[ 3.401970] pci_bus 0000:00: root bus resource [mem 0xfa000000-0xfbdfffff]
[ 3.409375] pci_bus 0000:00: root bus resource [io 0x0000-0xfffff] (bus address [0xfbe00000-0xfbefffff])
[ 3.417072] pci 0000:00:00.0: [1d87:0100] type 01 class 0x060400
[ 3.417190] pci 0000:00:00.0: supports D1
[ 3.417196] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
[ 3.417676] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 3.425545] pci_bus 0000:01: busn_res: can not insert [bus 01-ff] under [bus 00-1f] (conflicts with (null) [bus 00-1f])
[ 3.425588] pci 0000:01:00.0: [1b21:0612] type 00 class 0x010601
[ 3.425642] pci 0000:01:00.0: reg 0x10: initial BAR value 0x00000000 invalid
[ 3.432368] pci 0000:01:00.0: reg 0x10: [io size 0x0008]
[ 3.432397] pci 0000:01:00.0: reg 0x14: initial BAR value 0x00000000 invalid
[ 3.438957] pci 0000:01:00.0: reg 0x14: [io size 0x0004]
[ 3.438971] pci 0000:01:00.0: reg 0x18: initial BAR value 0x00000000 invalid
[ 3.445415] pci 0000:01:00.0: reg 0x18: [io size 0x0008]
[ 3.445429] pci 0000:01:00.0: reg 0x1c: initial BAR value 0x00000000 invalid
[ 3.451804] pci 0000:01:00.0: reg 0x1c: [io size 0x0004]
[ 3.451818] pci 0000:01:00.0: reg 0x20: initial BAR value 0x00000000 invalid
[ 3.458122] pci 0000:01:00.0: reg 0x20: [io size 0x0020]
[ 3.458137] pci 0000:01:00.0: reg 0x24: [mem 0x00000000-0x000001ff]
[ 3.458150] pci 0000:01:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
[ 3.460470] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[ 3.460537] pci 0000:00:00.0: BAR 8: assigned [mem 0xfa000000-0xfa0fffff]
[ 3.470994] pci 0000:01:00.0: BAR 6: assigned [mem 0xfa000000-0xfa00ffff pref]
[ 3.497156] pci 0000:01:00.0: BAR 5: assigned [mem 0xfa010000-0xfa0101ff]
[ 3.504734] pci 0000:01:00.0: BAR 4: no space for [io size 0x0020]
[ 3.510579] pci 0000:01:00.0: BAR 4: failed to assign [io size 0x0020]
[ 3.516276] pci 0000:01:00.0: BAR 0: no space for [io size 0x0008]
[ 3.521936] pci 0000:01:00.0: BAR 0: failed to assign [io size 0x0008]
[ 3.527605] pci 0000:01:00.0: BAR 2: no space for [io size 0x0008]
[ 3.532503] pci 0000:01:00.0: BAR 2: failed to assign [io size 0x0008]
[ 3.537180] pci 0000:01:00.0: BAR 1: no space for [io size 0x0004]
[ 3.541789] pci 0000:01:00.0: BAR 1: failed to assign [io size 0x0004]
[ 3.546404] pci 0000:01:00.0: BAR 3: no space for [io size 0x0004]
[ 3.550983] pci 0000:01:00.0: BAR 3: failed to assign [io size 0x0004]
[ 3.555226] pci 0000:00:00.0: PCI bridge to [bus 01]
[ 3.559035] pci 0000:00:00.0: bridge window [mem 0xfa000000-0xfa0fffff]
[ 3.563143] pcieport 0000:00:00.0: enabling device (0000 -> 0002)
[ 3.567436] pcieport 0000:00:00.0: Signaling PME through PCIe PME interrupt
[ 3.571440] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
[ 3.575103] pcie_pme 0000:00:00.0:pcie01: service driver pcie_pme loaded
[ 3.575213] aer 0000:00:00.0:pcie02: service driver aer loaded
|
|
|
|
|