First, I apologize for posting in the General forum but couldn't find the Ox64 section.

Any ideas on how to remedy this?

Win 10 pro
Dev Cube 1.8.3
Using firmware dated 2 weeks ago
Silicon Labs CP2104 USB to UART Bridge
Following the instructions on the Github page found HERE

Dev Cube MCU page flashing m0 and d0 was successful but then moved to the IOT tab of Dev Cube in order to flash the BL808-firmware.bin to address 0x800000 and received the following error:

TL;DR version

I made a quick test with a none Pine64 USB-C Docking Bar. It has a USB-C charging port, where I attached the power source. Then it has a HDMI port and two USB-C connectors. I plugged it into my PinePhone with pmOS over usb-c, and then plugged in a HDMI monitor, a usb mouse and a usb keyboard. None of the peripherals worked out of the box.

Is the Pine64 USB-C Docking Bar a miracle bar with miracle software and the one and only docking bar, or should also other docking bars work? Or does eventually installation of drivers help to get my non Pine64 docking bar to work?

While (intending to) backup files before installing Tow-Boot, I accidentally deleted all the files in my boot partition on my NVMe SSD. The root partition is fine.

Afterwards, I installed a fresh Manjaro image to my eMMC and I am currently booting it. I suspect that my NVMe root partition contains everything I need to restore /boot on the NVMe. For example, I have /var/cache/pacman/pkg/linux-6.25-1-aarch64.pkg.tar.zst and all my other package archives.

Can I run pacman from my eMMC system and tell it to install the needed package(s) from my NVMe drive onto the boot partition of my NVMe drive?
Perhaps I can simply umount the eMMC /boot partition, mount the NVMe boot partition in its place and then open a terminal in on the NVMe (/run/media…/var/cache/pacman/pkg/) folder and type "pacman -U <package.zst> but I also suspect a chroot to the NVMe system will be necessary.

What packages do I need to install? Maybe all I need to do is re-install the kernel under chroot and it will build a new initramfs-linux.img, etc.

Thanks so much for any help with the process.

-Cal

P.S. Unrelated but why does Tow-Boot say

I have been using a Raspberry Pi Model B as a home server for a decade now. Mainly as an http/cronjob server, it has never failed on me (did a SD card upgrade at some point for additional disk space). Backup was just a couple of SDs ready to replace the failing one.



Now I need more CPU power so I got myself a RockPro64 4GB and plan to setup it with two M2 SSDs in RAID 1.



My current inventory:

- board

- 60W power adapter

- PCIE to M2 SATA adapter (two slots) based on the JMB582 chip



Items I am waiting for:

- heat sink (forgot to order it with the board)

- serial to usb adapter (because apparently you cannot install Debian without it as video fails: https://youtu.be/dENsLmDhq5Y)

- 2x SATA SSDs (1TB each)



Tried installing Debian 12 but (as per the linked YouTube video) I think I got this https://wiki.pine64.org/wiki/ROCKPro64#N..._on_Debian so now I need something to hook up to the uart (please let me know if I am wrong on this).



Manjaro worked great and I was able to at least confirm the SATA adapter is loaded fine:
$ lspci
00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3399 PCI Express Root Port
01:00.0 SATA controller: Micron Technology Corp. JMB58x AHCI SATA controller

Hi all.
For over two years, I've had a great time using my PinePhone as a daily driver under postmarketOS edge. Up to this point, I've been able to overcome just about any issue. However, I've suddenly run into a hardware problem, which I can't seem to troubleshoot...
Here are the symptoms:

1. The phone will start to boot, (green LED lights), but about 1 second into the ToW boot loader the LED just goes dark.
   
2. Plugging in a USB-C cable from my labtop results in a boot loop; the phone will boot until the OS splash screen flickers for a brief moment before repeating.
   
3. Plugging in a slow USB-1.2 charger allows the phone to boot normally. However, I noticed that my battery status indicated a 100% charge state. (I have always set the OS to undercharge to no more than 90%...)
   
4. The phone also boots normally on a slow USB-1.2 charger with the battery removed. The battery status indicated a 0% charge state, in this case.
   
5. In either case #3 or #4, all radios are disabled within the OS.
   

1. I booted from a SDcard Jumpdrive using a USB-1.2 power source. It boots fine to the Jumpdrive splash.
   
2. I then let it sit for hours attempting to slowly bring the phone battery back to life.
   
3. This Jumpdrive charge method did not seem to work. Pulling the charging cable immediately kills the phone, and attempting to boot from the battery has the same symptoms as above.
   
4. Measuring the voltage across the battery terminals shows 4.2V, though... This indicates a fully charged lithium-ion battery under no-load, correct?
   

Hello, I was wondering what actions and when are needed in order to not "fall" into debian stable with coming bookworm stable, and keep the system on debian testing migrating to debian trixie?

The recorder app on KDE has lost its ability to either record or playback the Opus audio codec. So a switch to use the Vorbis codec is called for.

And I found it necessary to install the Alsa audio mixer to get good levels.

Since Telegram (aka telegram-desktop) installs fine on several distros, I wouldn't put it under any of them, but rather here in the general PP software.

After surpassing the initial hurdle - some sort of musical chairs shell game with my daughter's Telegram on android, where she cloned herself on my phone, then I reinvented myself as someone else, then she disowned the clone... few more steps that I couldn't even memorize, but okay, I have a working Telegram. Can chat, can talk (audio works), even saw a video of my wife from her (Mint) PC, and perhaps I'll be able to use my phone cameras once - tried that a couple of times, once it didn't work, second time had to reboot the phone.

That first run was in november. Since then I got a couple of updates and my desktop icon went missing. Just disappeared altogether. I have to launch a console and type telegram-desktop, and keep the console open, and eventually, when I quit Telegram, dismiss a dialog telling me that it knows that I had quit Telegram.

I've found the org.telegram.desktop.desktop file somewhere (where it should be), and no matter what I tried, it doesn't show on the desktop. I learned more about .desktop files than I ever wanted to, and still no dice. Is there some simple trick to make it show up?

Hello everyone,
I got second hand pinephone (not pro) from ebay. And I installed some distros and I decided use https://github.com/Shubhamvis98/kali-pinephone

I can run OS from sd card but my main OS is still broken (non updatable ubuntu)
Can I install kali or other distro permanently? So I want to replace main OS (ubuntu)

Hi all,

I'm in bookworm mobian and do all latest available updates/upgrades on repo.

I have megapixels with 1.6.0-1+b1 version.

As suggest, i have installed necessary packages "dcraw" and "imagemagick".

In log, flash strobe is not openned.