Just got my PBP yesterday. It doesn't seem to matter whether I use the barrel charger or usb the red light goes out after being on for 1-2 hours. If the battery is not charged completely and I have power supplied to the unit should it boot? Press the start button and will not turn on. Any ideas on issues? Any help is appreciated. Thanks

Last week I got my sealed PineTime. I could connect to it using GadgetBridge from my Android Phone and flash it with InfiniTime 1.14.0.

It seems to work fine in general - but only while it's in the charging cradle!

The moment I remove it from the cradle, ...

• I can no longer wake the watch by tapping the screen.
  
  
• I can no longer wake the watch by pressing the physical button. It doesn't matter how long I press - I tried short, a few seconds, 10 seconds, 20 seconds
  
  
• GadgetBridge says that the watch is no longer connected.
  
  
• Re-running the bluetooth device search in GadgetBridge does not find the watch either.
  I also tried removing the device from GadgetBridge first. In that case, the device shows up in the search results. When I do not connect but remove the watch from its cradle, the device disappears from the search results page instantly.
  

I have a custom PCIe x4 lane card that I'm trying to integrate with a RockPro64 SBC. This custom card has been tested with many users on different platforms including a linux x86 system. When I try this card in a RK3399 system, I get a strange result when I view the assigned address space with the lspci command. It appears the address assigned is the exact value of the BAR address size for each BAR. If I change the BAR size the assigned address changes to that value. Below is a dmesg dump along with a lspci output for my device. Device is  [ad00:001e]. Any guidance?
 
dmesg:
[    2.395091] rockchip-pcie f8000000.pcie: host bridge /pcie@f8000000 ranges:
[    2.395148] rockchip-pcie f8000000.pcie:      MEM 0x00fa000000..0x00fbdfffff -> 0x00fa000000
[    2.395175] rockchip-pcie f8000000.pcie:       IO 0x00fbe00000..0x00fbefffff -> 0x00fbe00000
[    2.396226] rockchip-pcie f8000000.pcie: supply vpcie1v8 not found, using dummy regulator
[    2.396376] rockchip-pcie f8000000.pcie: supply vpcie0v9 not found, using dummy regulator
[    2.571466] rockchip-pcie f8000000.pcie: wait 1000 ms (from device tree) before bus scan
[    3.582289] rockchip-pcie f8000000.pcie: PCI host bridge to bus 0000:00
[    3.582303] pci_bus 0000:00: root bus resource [bus 00-1f]
[    3.582316] pci_bus 0000:00: root bus resource [mem 0xfa000000-0xfbdfffff]
[    3.582330] pci_bus 0000:00: root bus resource [io  0x0000-0xfffff] (bus address [0xfbe00000-0xfbefffff])
[    3.582387] pci 0000:00:00.0: [1d87:0100] type 01 class 0x060400
[    3.582547] pci 0000:00:00.0: supports D1
[    3.582557] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
[    3.588072] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    3.588301] pci 0000:01:00.0: [ad00:001e] type 00 class 0x000000
[    3.588382] pci 0000:01:00.0: reg 0x10: [mem 0xfffffe00-0xffffffff]
[    3.588455] pci 0000:01:00.0: reg 0x18: [mem 0xffe00000-0xffffffff]
[    3.588606] pci 0000:01:00.0: Upstream bridge's Max Payload Size set to 128 (was 256, max 256)
[    3.588632] pci 0000:01:00.0: Max Payload Size set to 128 (was 128, max 128)
[    3.589238] pci_bus 0000:01: busn_res: [bus 01-1f] end is updated to 01
[    3.589272] pci 0000:00:00.0: BAR 14: assigned [mem 0xfa000000-0xfa2fffff]
[    3.589287] pci 0000:00:00.0: PCI bridge to [bus 01]
[    3.589302] pci 0000:00:00.0:   bridge window [mem 0xfa000000-0xfa2fffff]
[    3.589497] pcieport 0000:00:00.0: enabling device (0000 -> 0002)
[    3.589853] pcieport 0000:00:00.0: PME: Signaling with IRQ 37
[    3.590302] pcieport 0000:00:00.0: AER: enabled with IRQ 37
 
lspci -v:
00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3399 PCI Express Root Port (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 37
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Memory behind bridge: fa000000-fa2fffff [size=3M] [32-bit]
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
BridgeCtl: Parity- SERR+ NoISA- VGA- VGA16- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: <access denied>
Kernel driver in use: pcieport

01:00.0 Non-VGA unclassified device: Alta Data Technologies LLC Device 001e
Subsystem: Alta Data Technologies LLC Device 001e
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 0
Region 0: Memory at fffffe00 (32-bit, non-prefetchable) [disabled] [size=512]
Region 2: Memory at ffe00000 (32-bit, non-prefetchable) [disabled] [size=2M]
Capabilities: <access denied>
 

Thank you so much to all admins, moderators, whomever is responsible for bringing it back up!  

I can almost imagine how much work and anxiety was involved.

I thought this might have been what took the forums down! :-) But it seems no one had posted yet:

This Mastodon post tells how to activate wifi with the updated driver:
https://fosstodon.org/@phundrak@emacs.ch...9643222233

WARNING: This activates the testing repo which means you get bleeding-edge updates.

In this case, the only bleeding edge I have found is that sleep mode just hangs. I have to power off the device and back on if I accidentally try to let it sleep (by, for example, closing the cover). 

So it's definitely not perfect. But it works, and works quite well in my few days of playing with it.

It makes the Pinetab a whole new device for me!

So I was playing around with my Quartz64 board and I did a reboot and it didn't come back up. All I get now is the power led but there is not activity on the display or network. I don't know what I did but I'm hoping it didn't just randomly die. 

Has anyone had something like this happen? If so, how did you fix it? I really hope the answer isn't to buy another one. 


Darin

I have Manjaro installed on both eMMC and NVME in my Pinebook Pro. 

At some point in the last few weeks or month maybe, networking stopped working on both installs. I get the box with the red icon on the bottom.

I plug in a known good USB WiFi dongle, but it doesn't show up in ifconfig or "ip a". 

Dmesg does show the device connecting.

I assume something broke in Manjaro.

I have Armbian on a MicroSD card and there are no network problems with it.

Has anyone seen this?

I hadn't realized but I had spent an inordinate amount of time on a project for my rockpro64 NAS. So much so, that I thought it maybe of use to others since, through its many iterations, it has become nicely refined, maybe to the extent of a viable product.

I designed it out of a block of aluminium.
it had to be passive cooled to be in a heavily dusty environment.
it would be working hard, and in a hot workshop. As a result it had to have ample cooling, for chips and ram.
It turned out rather sleek like, apple esc due to the nature of how I chose to passively cool it.
Had to house and protect 3 SSD's.

 Do I have to host pics to post them here?

can someone tell me how to revert to an older version of U-Boot or upgrade to a working version?  I am currently running version 2023.07+dfsg-1.  It will no longer boot from an SD card.   I put a screen shot with the errors then after it flashes like it is adjusting video then boots.  I does then same on reboot but get stuck at the flashing screen.

Attached Files

Thumbnail(s)
       

Hello there,

I am new here and owner of PinePhone pro, As far as i know that Pine64 products are made in Taiwan, but when received my phone and checked the shipping tracking it was originated from Hong Kong China, even my shipment was designated to Taiwan, can someones shed the light on this.

Thanks