| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 30,111
» Latest member: p789betbiz
» Forum threads: 16,362
» Forum posts: 117,533
Full Statistics
|
| Latest Threads |
Pinephone software
Forum: General Discussion on PinePhone
Last Post: Csanderson0313
11 hours ago
» Replies: 2
» Views: 151
|
Rock64 v2.0 u-boot SPI is...
Forum: General Discussion on ROCK64
Last Post: ju0n
07-05-2026, 11:02 AM
» Replies: 0
» Views: 76
|
Libby - ebook reader that...
Forum: PineNote Software
Last Post: kiwigoldfish
07-04-2026, 04:41 PM
» Replies: 6
» Views: 4,032
|
PineNote v1.2 - Charges N...
Forum: General Discussion on Pinebook Pro
Last Post: ttsp
07-02-2026, 02:52 AM
» Replies: 0
» Views: 239
|
How to change the PineNot...
Forum: General Discussion on PineNote
Last Post: cameronharring
07-01-2026, 12:22 PM
» Replies: 0
» Views: 130
|
PinePhone Pro disable Vol...
Forum: PinePhone Pro Hardware
Last Post: FR_IV
07-01-2026, 10:53 AM
» Replies: 1
» Views: 1,597
|
Star64/Starpro64 kernel b...
Forum: General
Last Post: tgbgreen
06-30-2026, 12:17 PM
» Replies: 1
» Views: 2,209
|
Manjaro affected by Arch ...
Forum: General
Last Post: tantamount
06-28-2026, 10:45 AM
» Replies: 0
» Views: 276
|
Fix Bricked SPI Flash, Pi...
Forum: PinePhone Pro Hardware
Last Post: FR_IV
06-27-2026, 05:00 PM
» Replies: 0
» Views: 195
|
irradium (based on crux l...
Forum: Linux on RockPro64
Last Post: mara
06-27-2026, 04:09 PM
» Replies: 12
» Views: 19,669
|
|
|
| Rock64 LCD compatibility for linux. |
|
Posted by: AmroIb - 05-04-2019, 09:09 PM - Forum: General Discussion on ROCK64
- No Replies
|
 |
Hello,
I searched a ton before posting but I cloud not find definite answer. Most LCDs won't work with rock64 but a solution is HDMI Switch like these here. Most other displays will not work.
Is there any LCD display that definitely work on rock64 ?
Will this product work ? since it use usb+hdmi here.
I'm fairly new rock64 is my first single computer board.
|
|
|
|
| Help with getting a Marvell 9230 to work |
|
Posted by: epoliqui - 05-04-2019, 09:43 AM - Forum: RockPro64 Hardware and Accessories
- Replies (9)
|
 |
Hey all,
I recently got a RockPro64 and installed the Armbian Desktop image to it.
I want to use this as a NAS, so I bought a iocrest marvell 9230 sata card (non raid) but I'm not sure about how I get it to work. Are there any drivers or settings I need to change? None of the drives I'm plugging into it are being read. Right now when I type lspci into the terminal I get this
Quote:01:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9230 PCIe SATA 6Gb/s Controller (rev 11)
and when I try to get more info using lspci -vvv I get
Quote:root@localhost:~# lspci -vvv
00:00.0 PCI bridge: Device 1d87:0100 (prog-if 00 [Normal decode])
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 244
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 00000000-00000fff
Memory behind bridge: fa000000-fa0fffff
Prefetchable memory behind bridge: 00000000-000fffff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [80] Power Management version 3
Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0+,D1+,D2-,D3hot+,D3cold-)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable+ 64bit+
Address: 00000000fee30040 Data: 0000
Masking: 00000000 Pending: 00000000
Capabilities: [b0] MSI-X: Enable- Count=1 Masked-
Vector table: BAR=0 offset=00000000
PBA: BAR=0 offset=00000008
Capabilities: [c0] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #0, Speed 5GT/s, Width x4, ASPM L1, Exit Latency L0s <256ns, L1 <8us
ClockPM- Surprise- LLActRep- BwNot+ ASPMOptComp+
LnkCtl: ASPM Disabled; RCB 128 bytes Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt+ AutBWInt+
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise-
Slot #0, PowerLimit 0.000W; Interlock- NoCompl-
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
Control: AttnInd Off, PwrInd Off, Power+ Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL+ CmdCplt- PresDet- Interlock-
Changed: MRL- PresDet- LinkState-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID 0000, PMEStatus- PMEPending-
DevCap2: Completion Timeout: Range B, TimeoutDis+, LTR+, OBFF Via message ARIFwd+
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled ARIFwd-
LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-
Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1-
EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
Capabilities: [100 v2] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
Capabilities: [274 v1] Transaction Processing Hints
Interrupt vector mode supported
Device specific mode supported
Steering table in TPH capability structure
Kernel driver in use: pcieport
01:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9230 PCIe SATA 6Gb/s Controller (rev 11) (prog-if 01 [AHCI 1.0])
Subsystem: Marvell Technology Group Ltd. 88SE9230 PCIe SATA 6Gb/s Controller
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Interrupt: pin A routed to IRQ 243
Region 0: I/O ports at 0000
Region 1: I/O ports at 0000
Region 2: I/O ports at 0000
Region 3: I/O ports at 0000
Region 4: I/O ports at 0000
Region 5: Memory at fa040000 (32-bit, non-prefetchable) [size=2K]
Expansion ROM at fa000000 [size=256K]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit-
Address: fee30040 Data: 0000
Capabilities: [70] Express (v2) Legacy Endpoint, MSI 00
DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s <1us, L1 <8us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #0, Speed 5GT/s, Width x2, ASPM L0s L1, Exit Latency L0s <512ns, L1 <64us
ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
DevCap2: Completion Timeout: Not Supported, TimeoutDis+, LTR-, OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled
LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1-
EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
Capabilities: [e0] SATA HBA v0.0 BAR4 Offset=00000004
Capabilities: [100 v1] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
AERCap: First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn-
I'm seeing malfunctions and errors but I really don't know what they mean.
Any help would be super appreciated!
|
|
|
|
| Marvell 88SE9235 PCI SATA card in LibreELEC |
|
Posted by: StefanRvO - 05-04-2019, 06:51 AM - Forum: Linux on RockPro64
- Replies (6)
|
 |
Hi
I have a Marvell 88SE9235 SATA PCI card(https://www.aliexpress.com/item/SATA-III...06828.html) attached to my ROCKPRO64 which i would like to use together with LibreELEC. However, drivers plugged into the card doesn't show up, so i think i may be missing some drivers.
I am running the latest LibreELEC build. with kernel 4.4.154.
I was previously running ayufan's ubuntu build, but couldn't get video acceleration to work in kodi, so i switched to LibreELEC where it seems to work without problems. However, my disks did show up when i ran Ubuntu, which makes me think it is probably a problem with the kernel drivers.
I actually tried compilling kodi myself, and set these extra kernel build options. However it did not seem to make any difference:
CONFIG_ARCH_MV78XX0=y
CONFIG_ARCH_DOVE=y
CONFIG_SATA_MV=y
CONFIG_SCSI_MVSAS=y
CONFIG_MACH_RD78X00_MASA=y
CONFIG_MARVELL_PHY=y
CONFIG_RAID_ATTRS=y
CONFIG_SCSI_NETLINK=y
CONFIG_SCSI_MQ_DEFAULT=y
If anybody have any ideas to what i might be missing to get the SATA card working?
Regards
Stefan
|
|
|
|
| [SOLVED] Pinebook stopped to charge |
|
Posted by: UltraBloxX - 05-04-2019, 03:22 AM - Forum: Pinebook Hardware and Accessories
- Replies (7)
|
 |
Hello!
My Pinebook was working just fine, but yesterday it has stopped to charge. That is, when I plugged it in - it appears to detect charger plugged in, but battery is not charged and LED near power socket doesn't light up.
Battery is not undercharged and in fact, there's still 26% as I type this message. According to XFCE power manager in Armbian, the battery is "discharging", and at same time, AC power supply is detected. From the charge level, it seems that Pinebook runs mostly from AC power and battery depletes much slower than usual. But I'm puzzled, why doesn't it charge. Battery voltage is around 3.8-3.7V, so it's nowhere close to be "flat", and PMIC should detect and charge it. I still opened bottom cover and tried to detach and reattach battery connector, but nothing seems to have changed.
Here's upower -d dump:
Code: $ upower -d
Device: /org/freedesktop/UPower/devices/line_power_axp813_ac
native-path: axp813-ac
power supply: yes
updated: Sat 04 May 2019 12:00:19 PM MSK (830 seconds ago)
has history: no
has statistics: no
line-power
warning-level: none
online: yes
icon-name: 'ac-adapter-symbolic'
Device: /org/freedesktop/UPower/devices/battery_axp20x_battery
native-path: axp20x-battery
power supply: yes
updated: Sat 04 May 2019 12:12:20 PM MSK (109 seconds ago)
has history: yes
has statistics: yes
battery
present: yes
rechargeable: yes
state: discharging
warning-level: none
energy: 0 Wh
energy-empty: 0 Wh
energy-full: 0 Wh
energy-full-design: 0 Wh
energy-rate: 0 W
voltage: 3.721 V
percentage: 26%
capacity: 100%
icon-name: 'battery-low-symbolic'
Device: /org/freedesktop/UPower/devices/DisplayDevice
power supply: yes
updated: Sat 04 May 2019 12:00:19 PM MSK (830 seconds ago)
has history: no
has statistics: no
battery
present: yes
state: discharging
warning-level: none
energy: 0 Wh
energy-full: 0 Wh
energy-rate: 0 W
percentage: 26%
icon-name: 'battery-low-symbolic'
Daemon:
daemon-version: 0.99.4
on-battery: no
lid-is-closed: no
lid-is-present: yes
critical-action: PowerOff
|
|
|
|
| USB |
|
Posted by: MathiasJ - 05-03-2019, 01:06 AM - Forum: General
- Replies (1)
|
 |
Hi,
I'm new here and I'd like to ask you following:
At the USB-Port how many mA do I have?
It's possible to make
max_usb_current=1
like at the Raspberry PI?
I neeed at last 1200mA for a USB-Port.
Gretings
|
|
|
|
| Poll: interest for SPDIF-only POT board? |
|
Posted by: amp - 05-01-2019, 11:17 PM - Forum: POT modules
- No Replies
|
 |
As per https://forum.pine64.org/showthread.php?...&pid=46055
Quote:tllim wrote:
Quote:amp wrote:
[...] it would be very nice to also have a SPDIF only board (Toslink and co-axial) for those of us that don't need the DAC (e.g. using external receiver to decode), but don't have the time/skill/parts/tools to build one.
[...]
if SDPIF only POT board is a popular request, we will consider.
Please vote for the option you would consider buying (if any).
|
|
|
|
How to Install Google PlayStore |
|
Posted by: NightCrawler504 - 05-01-2019, 12:39 PM - Forum: RockPro64 Projects, Ideas and Tutorials
- Replies (2)
|
 |
You will need:
Hardware:
1) Usb type c cable, if you don’t have a type c cable you can also use an adapter
Software:
1) Drivers if you hadn’t installed already:
files.pine64.org/doc/rock64/tools/DriverAssitant_v4.5.zip
2) ADB files (platform tools) from Domo:
Android 7.1:
https://forum.pine64.org/showthread.php?tid=6683
Android 8.1:
https://forum.pine64.org/showthread.php?tid=6684
Ok let’s start:
1) Go to settings/about tablet and tap build number at the end of the menu 7 times, this enables developer options on settings
2) Verify that usb debugging is enabled on settings/developer options, if it’s on turn off and turn on again
3) Restart device, wait for it to start…
4) Connect usb to type c cable (adb only works on the usb type c port)
5) Go to folder where you downloaded your Platform Tools, hold down the shift key and right click in a white portion inside the explorer window of the platform tools directory while still holding the shift key, select open command window here, wait for screen to open.
6) Type:
Adb devices
It will start running deamon and do device recognition, if you had already opened adb it will only show available devices, if device does not show verify you have usb debugging enabled and restart again and you have connected usb type c to your computer, not all cables will work if you repeat process and device is not recognized change cable, still not showing try in another usb port on your computer.
7) Go to Domo guide that is the same as your android version
Android 7.1:
https://forum.pine64.org/showthread.php?tid=6683
Android 8.1:
https://forum.pine64.org/showthread.php?tid=6684
Copy paste commands in the same order as Domo instructions.
Copy paste without the ./ at the start of every command
Some commands will auto run if they don’t press enter after pasting
Remember to also run last 2 commands in adb shell after you have restarted device
That’s it, quick and easy, if you have questions comment bellow
Thanks Domo for sharing platform tools.
Link to visual aid in the following video:
https://youtu.be/jQtJ3jGoVMA
|
|
|
|
|