Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 29,699
» Latest member: bigyoshi
» Forum threads: 16,260
» Forum posts: 117,188

Full Statistics

Latest Threads
Volumio (PINE A64-LTS / S...
Forum: Linux on PINE A64-LTS / SOPINE
Last Post: kapqa
Today, 02:02 AM
» Replies: 8
» Views: 15,508
Reinstallation Arch Linux...
Forum: General Discussion on PineTab
Last Post: rth
Yesterday, 08:25 PM
» Replies: 1
» Views: 205
Old Danctnix server in Pa...
Forum: PineTab Software
Last Post: brorean
11-21-2025, 08:45 PM
» Replies: 1
» Views: 129
PinePhone, PinePhone Pro,...
Forum: PinePhone Hardware
Last Post: brb78
11-20-2025, 04:15 PM
» Replies: 0
» Views: 107
Recycling pinephone as ho...
Forum: PinePhone Hardware
Last Post: biketool
11-20-2025, 09:04 AM
» Replies: 5
» Views: 605
Light Sensor / Proximity ...
Forum: General Discussion on PinePhone
Last Post: WhiteHexagon
11-18-2025, 03:07 PM
» Replies: 1
» Views: 170
How to stop it turning on
Forum: General Discussion on PinePhone
Last Post: biketool
11-18-2025, 02:30 PM
» Replies: 3
» Views: 476
8/24 status of JumpDrive
Forum: PinePhone Software
Last Post: biketool
11-18-2025, 01:27 PM
» Replies: 5
» Views: 2,166
Questions about running U...
Forum: General Discussion on PineTime
Last Post: alicesphere
11-18-2025, 12:48 AM
» Replies: 0
» Views: 103
Difficulty with openSUSE ...
Forum: PinePhone Software
Last Post: danm1988
11-17-2025, 07:49 AM
» Replies: 0
» Views: 103

 
  What would the cost increment be to allow some level of extensibility?
Posted by: realrichardsharpe@gmail.com - 01-19-2020, 11:45 AM - Forum: General Discussion on PinePhone - Replies (2)

One of the advantages of the LibRem 5 is that it has two M.2 slots, so the phone hardware and the WiFi hardware can be upgraded, or one can possibly swap the WiFi card with an M.2 NVMe card or other interesting cards, like WiFi 6.

What would the cost increment be for the PinePhone to include an M.2 slot?


  Kali Linux for Pinebook Pro
Posted by: Luke - 01-19-2020, 09:33 AM - Forum: Linux on Pinebook Pro - Replies (100)

Build script for Kali Linux for the Pinebook Pro is now available.
Many thanks to Steev for the hard work!

Kali Linux Build Script

Image download link


  Backup the EMMC
Posted by: tso4ev - 01-19-2020, 07:23 AM - Forum: General Discussion on Pinebook Pro - Replies (16)

hi all
I'm wondering if there is some way to backup the internal 64gb emmc to an sdcard
Raspberry pie uses a little app called SD card copier it would be nice if there is something like this for the pinebook pro
its very useful if we f*ck up the system just to restore it from the sd card would be amazing
and time consuming just copy back everything with all settings and stuff
hopefully somebody will come up with something


  PineTime display and micropython
Posted by: danielt - 01-19-2020, 04:11 AM - Forum: Development Discussion on PineTime - Replies (17)

Just wondered if anyone has got the display going from MicroPython.

So far I've spent most of my time on PineTime hacking together a bootloader robust enough to allow me to stick the back on (albeit with something I could undo in an emergency). Nothing too fancy... just getting the bootloader and app cooperate to turn the user button into a watchdog enforced long press reset button.

I've been using MicroPython with a BLE REPL as a test payload and the next step is to get something on the display so I just wondered if someone is ahead of me there and already has this going in Python? Once the back is on I'd like to at least see the time!


  RockPro64 PCIx4 soundcard
Posted by: srhtpc - 01-18-2020, 10:31 PM - Forum: RockPro64 Hardware and Accessories - No Replies

Does anyone know if a PCI soundcard (more specifically the ASUS Xonar DX) will be recognized and work soundcard on the RckPro64?


  Speaker idea
Posted by: ab1jx - 01-18-2020, 07:17 PM - Forum: General Discussion on Pinebook Pro - Replies (10)

The speakers in the pbp could use, well, a subwoofer maybe.  I don't know where you'd put one.  To look at the picture they look like ordinary small speakers like you might find in a radio.  Recent advances like neodymium magnets have made big sound from a small space possible, but they're best used in some environment designed for them, not just stuck in there.  Some plastic or fiberglass housing, I remember it's important that sound waves coming off the front of the speaker not reach the back and cause interference and partial cancellation.  A cardboard box is better than nothing with bigger speakers.  There is software like qspeakers for trying to optimize designs, not that I've tried it.

What about cell phone speakers?  They aren't very big but some can belt out those ringtones, which are often music clips.  Seems like there must be some surplus ones around since there are millions of cell phones.


Exclamation Brave Heart First Impressions ?
Posted by: bcnaz - 01-18-2020, 04:06 PM - Forum: General Discussion on PinePhone - Replies (57)

 (January 18, 2019)

   So Brave Heart Edition of the Pine phone started shipping yesterday.

      Have  'YOU'   received Your shipping notice yet ?

    I was in the Crowd waiting when they opened the door on this bout of orders.

     I guess the store is probably closed for the weekend (?)  I hope to hear something soon.

January 25, 2020

When I attempt to track my Brave Heart :

It still has the same old statement that it has "arrived in Switzerland" !

5 Days and not even an update !

GRRrrrr Wish it was DHL

Asendia SUX


  Kernel headers for stock Debian image
Posted by: fader - 01-18-2020, 10:35 AM - Forum: Linux on Pinebook Pro - No Replies

I'm trying to build a couple of kernel modules for the Pinebook Pro but haven't been able to find the kernel headers.  Are there debs of these anywhere?

(I suspect this will be fixed with the mainline kernel work moving to 5.x but I haven't yet found the specific 4.4.207 fork used on the Pinebook Pro.)


  Wifi keeps dropping out after some use
Posted by: conehead - 01-18-2020, 07:11 AM - Forum: General Discussion on Pinebook Pro - Replies (1)

I'm using the default linux image and have updated everything.

After a while of use, the wifi stops working, requiring me to either `ifconfig wlan0 up` or, if that doesn't work, reboot the machine.

If I have it plugged into AC power with the supplied power adapter, I only get maybe 10 minutes of watching fullscreen 720p youtube before the wifi goes out.

If it's on battery, I get longer, maybe a half hour or more before it fails.

I checked the syslog and I see a bunch of wifi-related errors when this happens - lots of assert failures, mismatched lengths etc, then finally a note saying the chip has hanged and it shuts off the wifi.

Does this happen to anyone else? Is this the expected behavior or did I get a bad one?

A snippet from my syslog when this happened:


Code:
Jan 15 12:55:58 Debian-Desktop kernel: [15802.226370] dwmmc_rockchip fe310000.dwmmc: All phases work, using default phase 0.
Jan 15 12:55:58 Debian-Desktop kernel: [15802.227644] dhdsdio_rxglom (superframe): len 0x0010, rounded 0x0100, expect 0x0d00
Jan 15 12:55:58 Debian-Desktop kernel: [15802.227662] dhdsdio_rxfail: abort command, terminate frame, send NAK
Jan 15 12:55:58 Debian-Desktop kernel: [15802.228199] dhdsdio_rxglom (superframe): len 0x1220, rounded 0x1300, expect 0x0d00
Jan 15 12:55:58 Debian-Desktop kernel: [15802.228212] dhdsdio_rxfail: abort command, terminate frame, send NAK
Jan 15 12:55:58 Debian-Desktop kernel: [15802.228602] dhdsdio_rxglom (superframe): HW hdr error: len/check 0x0000/0x0000
Jan 15 12:55:58 Debian-Desktop kernel: [15802.228614] dhdsdio_rxfail: abort command, terminate frame, send NAK
Jan 15 12:55:58 Debian-Desktop kernel: [15802.229001] dhdsdio_rxglom (superframe): HW hdr error: len/check 0x0000/0x0000
Jan 15 12:55:58 Debian-Desktop kernel: [15802.229032] dhdsdio_rxfail: abort command, terminate frame
Jan 15 12:56:01 Debian-Desktop kernel: [15804.901029] sdioh_buffer_tofrom_bus: RX FAILED ffffffc0f1ed4a20, addr=0x08000, pkt_len=32, ERR=-84
Jan 15 12:56:01 Debian-Desktop kernel: [15804.901049] dhdsdio_readframes: RXHEADER FAILED: -35
Jan 15 12:56:01 Debian-Desktop kernel: [15804.901058] dhdsdio_rxfail: abort command, terminate frame, send NAK
Jan 15 12:56:01 Debian-Desktop kernel: [15804.909252] dwmmc_rockchip fe310000.dwmmc: All phases work, using default phase 0.
Jan 15 12:56:02 Debian-Desktop kernel: [15806.188004] sdioh_buffer_tofrom_bus: RX FAILED ffffffc0f1ed4a20, addr=0x08000, pkt_len=32, ERR=-84
Jan 15 12:56:02 Debian-Desktop kernel: [15806.188024] dhdsdio_readframes: RXHEADER FAILED: -35
Jan 15 12:56:02 Debian-Desktop kernel: [15806.188032] dhdsdio_rxfail: abort command, terminate frame, send NAK
Jan 15 12:56:02 Debian-Desktop kernel: [15806.196104] dwmmc_rockchip fe310000.dwmmc: All phases work, using default phase 0.
Jan 15 12:56:03 Debian-Desktop kernel: [15807.244024] sdioh_buffer_tofrom_bus: RX FAILED ffffffc0f1ed4a20, addr=0x08000, pkt_len=32, ERR=-84
Jan 15 12:56:03 Debian-Desktop kernel: [15807.244042] dhdsdio_readframes: RXHEADER FAILED: -35
Jan 15 12:56:03 Debian-Desktop kernel: [15807.244050] dhdsdio_rxfail: abort command, terminate frame, send NAK
Jan 15 12:56:03 Debian-Desktop kernel: [15807.252231] dwmmc_rockchip fe310000.dwmmc: All phases work, using default phase 0.
Jan 15 12:56:03 Debian-Desktop kernel: [15807.253609] dhdsdio_rxglom (superframe): len 0x0022, rounded 0x0100, expect 0x0d00
Jan 15 12:56:03 Debian-Desktop kernel: [15807.253621] dhdsdio_rxfail: abort command, terminate frame, send NAK
Jan 15 12:56:07 Debian-Desktop kernel: [15811.253227] dhd_bus_rxctl: resumed on timeout, INT status=0x20400000
Jan 15 12:56:07 Debian-Desktop kernel: [15811.258552] Dump dongle memory
Jan 15 12:56:08 Debian-Desktop kernel: [15811.379763] dhd_schedule_memdump: buf(va)=ffffffc029000000, buf(pa)=29000000, bufsize=819200
Jan 15 12:56:08 Debian-Desktop kernel: [15811.379785] dhd_bus_rxctl: rxcnt_timeout=1, rxlen=0
Jan 15 12:56:08 Debian-Desktop kernel: [15811.380144] Dump dongle memory
Jan 15 12:56:08 Debian-Desktop kernel: [15811.380218] open file /installmedia/mem_dump_ERROR_RX_TIMED_OUT_1579092968.120553, try /data/
Jan 15 12:56:08 Debian-Desktop kernel: [15811.380222] write_dump_to_file: file_path = /data/mem_dump_ERROR_RX_TIMED_OUT_1579092968.120553
Jan 15 12:56:08 Debian-Desktop kernel: [15811.380227] open file error, err = -2
Jan 15 12:56:08 Debian-Desktop kernel: [15811.380229] dhd_mem_dump: writing SoC_RAM dump to the file failed
Jan 15 12:56:08 Debian-Desktop kernel: [15811.464347] dhd_schedule_memdump: buf(va)=ffffffc029000000, buf(pa)=29000000, bufsize=819200
Jan 15 12:56:08 Debian-Desktop kernel: [15811.464386] dhd_check_hang: Event HANG send up due to  re=1 te=0 e=-110 s=2
Jan 15 12:56:08 Debian-Desktop kernel: [15811.464395] dhd_os_send_hang_message: Event HANG send up due to  re=1 te=0 s=2
Jan 15 12:56:08 Debian-Desktop kernel: [15811.464411] CFG80211-ERROR) wl_cfg80211_get_station : NOT assoc
Jan 15 12:56:08 Debian-Desktop kernel: [15811.464484] open file /installmedia/mem_dump_ERROR_RX_TIMED_OUT_1579092968.204844, try /data/
Jan 15 12:56:08 Debian-Desktop kernel: [15811.464492] write_dump_to_file: file_path = /data/mem_dump_ERROR_RX_TIMED_OUT_1579092968.204844
Jan 15 12:56:08 Debian-Desktop kernel: [15811.464501] open file error, err = -2
Jan 15 12:56:08 Debian-Desktop kernel: [15811.464507] dhd_mem_dump: writing SoC_RAM dump to the file failed
Jan 15 12:56:08 Debian-Desktop kernel: [15811.464533] CFG80211-ERROR) wl_cfg80211_disconnect : Reason 3
Jan 15 12:56:08 Debian-Desktop kernel: [15811.464546] dhd_dbg_stop_pkt_monitor, 1963
Jan 15 12:56:08 Debian-Desktop kernel: [15811.464562] dhd_prot_ioctl : bus is down. we have nothing to do - bs: 2, has: 1
Jan 15 12:56:08 Debian-Desktop kernel: [15811.464570] CFG80211-ERROR) wl_cfg80211_disconnect : error (-1)
Jan 15 12:56:08 Debian-Desktop kernel: [15811.464671] dhd_stop: Enter ffffffc0f0218000
Jan 15 12:56:08 Debian-Desktop kernel: [15811.464685] dhd_prot_ioctl : bus is down. we have nothing to do - bs: 2, has: 1
Jan 15 12:56:08 Debian-Desktop kernel: [15811.464692] CFG80211-ERROR) wl_cfg80211_clear_security : wsec clear failed
Jan 15 12:56:08 Debian-Desktop kernel: [15811.464701] dhd_prot_ioctl : bus is down. we have nothing to do - bs: 2, has: 1
Jan 15 12:56:08 Debian-Desktop kernel: [15811.464707] CFG80211-ERROR) wl_cfg80211_clear_security : auth clear failed
Jan 15 12:56:08 Debian-Desktop kernel: [15811.464717] dhd_prot_ioctl : bus is down. we have nothing to do - bs: 2, has: 1
Jan 15 12:56:08 Debian-Desktop kernel: [15811.464722] CFG80211-ERROR) wl_cfg80211_clear_security : wpa_auth clear failed
Jan 15 12:56:08 Debian-Desktop kernel: [15811.464734] dhd_prot_ioctl : bus is down. we have nothing to do - bs: 2, has: 1
Jan 15 12:56:08 Debian-Desktop kernel: [15811.464740] CFG80211-ERROR) wl_cfg80211_bss_isup : 'cfg bss -C 0' failed: -1
Jan 15 12:56:08 Debian-Desktop kernel: [15811.464747] CFG80211-ERROR) wl_cfg80211_bss_isup : NOTE: this ioctl error is normal when the BSS has not been created yet.
Jan 15 12:56:08 Debian-Desktop kernel: [15811.464778] dhd_prot_ioctl : bus is down. we have nothing to do - bs: 2, has: 1
Jan 15 12:56:08 Debian-Desktop kernel: [15811.464785] CFG80211-ERROR) wl_notifier_change_state : wlan0:error (-1)
Jan 15 12:56:08 Debian-Desktop kernel: [15811.464793] dhd_prot_ioctl : bus is down. we have nothing to do - bs: 2, has: 1
Jan 15 12:56:08 Debian-Desktop kernel: [15811.464799] CFG80211-ERROR) wl_cfg80211_update_power_mode : wl_cfg80211_update_power_mode:error (-1)
Jan 15 12:56:08 Debian-Desktop kernel: [15811.464883] dhd_prot_ioctl : bus is down. we have nothing to do - bs: 2, has: 1
Jan 15 12:56:08 Debian-Desktop kernel: [15811.464890] CFGP2P-ERROR) wl_cfgp2p_disable_discovery : unable to set WL_P2P_DISC_ST_SCAN
Jan 15 12:56:08 Debian-Desktop kernel: [15811.464963] dhd_prot_ioctl : bus is down. we have nothing to do - bs: 2, has: 1
Jan 15 12:56:08 Debian-Desktop kernel: [15811.464986] dhd_prot_ioctl : bus is down. we have nothing to do - bs: 2, has: 1
Jan 15 12:56:08 Debian-Desktop kernel: [15811.464996] CFGP2P-ERROR) wl_cfgp2p_set_discovery : p2p_disc 0 error -1
Jan 15 12:56:08 Debian-Desktop kernel: [15811.465026] CFG80211-ERROR) wl_cfgp2p_down : Clean up the p2p discovery IF
Jan 15 12:56:08 Debian-Desktop kernel: [15811.465047] wl_cfgp2p_del_p2p_disc_if: wdev: ffffffc0ef8ea000, wdev->net:           (null)
Jan 15 12:56:08 Debian-Desktop kernel: [15811.465081] CFGP2P-ERROR) wl_cfgp2p_disable_discovery :  do nothing, not initialized
Jan 15 12:56:08 Debian-Desktop kernel: [15811.465087] Exit. P2P interface stopped
Jan 15 12:56:08 Debian-Desktop kernel: [15811.474962] P2P interface unregistered
Jan 15 12:56:08 Debian-Desktop kernel: [15811.475004] CFGP2P-ERROR) wl_cfgp2p_deinit_priv : In
Jan 15 12:56:08 Debian-Desktop kernel: [15811.475031] dhd_prot_ioctl : bus is down. we have nothing to do - bs: 2, has: 1
Jan 15 12:56:08 Debian-Desktop kernel: [15811.475043] CFG80211-ERROR) wl_dongle_down : WLC_DOWN error (-1)
Jan 15 12:56:08 Debian-Desktop kernel: [15811.475066] dhd_tcpack_suppress_set: TCP ACK Suppress mode 1 -> mode 0
Jan 15 12:56:08 Debian-Desktop kernel: [15811.475085] wl_android_wifi_off in 1
Jan 15 12:56:08 Debian-Desktop kernel: [15811.475091] wl_android_wifi_off in 2: g_wifi_on=1, on_failure=1
Jan 15 12:56:08 Debian-Desktop kernel: [15811.475099] dhd_prot_ioctl : bus is down. we have nothing to do - bs: 2, has: 1
Jan 15 12:56:08 Debian-Desktop kernel: [15811.475117] dhd_dbg_detach_pkt_monitor, 2204
Jan 15 12:56:08 Debian-Desktop kernel: [15811.475125] dhd_bus_devreset: == Power OFF ==
Jan 15 12:56:08 Debian-Desktop kernel: [15811.475159] dhd_txglom_enable: enable 0
Jan 15 12:56:08 Debian-Desktop kernel: [15811.475166] dhd_conf_set_txglom_params: txglom_mode=copy
Jan 15 12:56:08 Debian-Desktop kernel: [15811.475171] dhd_conf_set_txglom_params: txglomsize=0, deferred_tx_len=0
Jan 15 12:56:08 Debian-Desktop kernel: [15811.475176] dhd_conf_set_txglom_params: txinrx_thres=128, dhd_txminmax=-1
Jan 15 12:56:08 Debian-Desktop kernel: [15811.475182] dhd_conf_set_txglom_params: tx_max_offset=0, txctl_tmo_fix=-1
Jan 15 12:56:08 Debian-Desktop kernel: [15811.475186] dhd_bus_devreset:  WLAN OFF DONE
Jan 15 12:56:08 Debian-Desktop kernel: [15811.475376] wifi_platform_set_power = 0
Jan 15 12:56:08 Debian-Desktop kernel: [15811.475384] ======== PULL WL_REG_ON(-1) LOW! ========
Jan 15 12:56:08 Debian-Desktop kernel: [15811.475390] [WLAN_RFKILL]: rockchip_wifi_power: 0
Jan 15 12:56:08 Debian-Desktop kernel: [15811.475414] [WLAN_RFKILL]: wifi shut off power.
Jan 15 12:56:08 Debian-Desktop kernel: [15811.475418] wl_android_wifi_off out
Jan 15 12:56:08 Debian-Desktop kernel: [15811.475425] wl_ext_iapsta_dettach_netdev: ifidx=0
Jan 15 12:56:08 Debian-Desktop kernel: [15811.475464] dhd_stop: Exit
Jan 15 12:56:08 Debian-Desktop kernel: [15811.476275] CFG80211-ERROR) wl_cfg80211_hang : In : chip crash eventing, reason=0x8001


  Article: OpenOCD on Raspberry Pi: Better with SWD on SPI
Posted by: lupyuen - 01-18-2020, 01:23 AM - Forum: PineTime Tutorials - Replies (5)

Hi PineTime Fans: I have modified OpenOCD to run on Raspberry Pi using the faster SPI interface (31 MHz!) instead of the old GPIO Bit Banging.  If this works, we should be able to flash AND debug PineTime firmware with VSCode on Raspberry Pi!

But I need your help to test this modified version of OpenOCD.  (Test instructions are in the article below)  If it's tested OK, I'll publish the steps to debug PineTime firmware on VSCode.  Please lemme know if it works. Thanks! :-)


OpenOCD on Raspberry Pi: Better with SWD on SPI