Jump to content


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. In fact, everything has been rock solid for me since I got rid of a couple of boards that obviously had hardware issues (those were different problems that had nothing to do with Armbian). My point is that the Armbian distributions for my Pine A64s and RockPro64s has been problem-free since late 2020.
  2. It did make it in. I've been running fine with the stock kernels since 5.4-43.
  3. Thanks. I gave up and retired my Pine A64 LTS. It had some apparent hardware issues that were a pain. I replaced it with a non-LTS Pine, and I've had no problems since.
  4. Just FYI, i have retired my Pine A64 LTS. I don't know if the recent kernel updates ever fixed this problem or not, because I never had/took the time to try them. But over the past few months, I've had a recurring issue of my USB system disk going AWOL. A reboot would clear everthing up. I thought maybe it was a power problem, so I eventually moved the system disk to a powered hub instead of plugging it directly into the Pine. That seemed to help for a bit, but the problem returned and actually got worse---the system would run OK for a couple or three days, then there'd be errors about writing to the drive and the system would hang. (All checks I ran on the disk showed no problems at all.) With all of this, I decided a few weeks ago to move everything on the system (Plex server, primarily) to one of my non-LTS Pine A64s, and the system has run perfectly fine ever since. No disk access problems, no system hangs---and no special SOPINE kernel. After I determined that it was stable, I decided I was tired of messing with the LTS, and I recycled it. I've always been confused about why the LTS version had several hardware changes made to it (the memory, the power connector, etc).... It's seems like a new model, not just an LTS version of the original. Anyway, it's history.
  5. Has anyone tried the latest upgrade to 5.10.34 to see if this problem has been resolved?
  6. Thanks, @dippywood! I hadn't seen that thread. I figured the problem had to be something simple, but it never occurred to me to look where you did. I'd go with your solution if I hadn't also experienced the Ethernet throughput issues I mentioned. So far, dropping down to 5.9.14 seems to have corrected those problems, too. I'm fortunate to still be doing work on VMS!
  7. Another issue I've had for a little while is that incoming wired Ethernet speeds have been terrible. Outgoing is as fast as ever, but incoming is anywhere from 4MBs down to 100KBs. It's usually in the 24MBs to 28MBs range. On a whim yesterday, I decided to drop back down to the 5.9.14 kernel. So far, so good. My problems started when I went to 5.10. But again, only on my LTS with the SoPINE images. I'm currently frozen at 5.9.14.
  8. This post from January is a for a different device and a different version, but the same symptom, based on the provided screenshot. Boot problem after upgrade to linux-image-current-sunxi64_20.11.7
  9. Thanks for your reply. I'm glad I'm not the only one seeing it!
  10. This is definitely a problem with 5.10.21 somehow. I'll spare you the details, but I managed to start fresh with 5.10.12, then upgraded to 5.10.16, and all was well. The MicroSD card could still be seen. Upgraded to 5.10.21, no more /dev/mmcblk0p1 device at all. I'm now frozen at 5.10.16 for the time being, and everything is as it should be. And to clarify, I do not see this problem with 5.10.21 on two PINE A64s (non-LTS) and on a RockPro64. Only the PINE A64-LTS (the SOPINE images) has the problem.
  11. FWIW, I double-checked using another system: the UUID has not changed on the MicroSD card. I decided to start fresh with a second MicroSD. I downloaded the current SoPINE Focal image from Armbian: Armbian_21.02.3_Pine64so_focal_current_5.10.21.img On the first boot, it loaded the kernel, hung for a bit after the "done." shown in the image---and then the MicroSD could not be found.
  12. Yesterday, I upgraded my Pine A64 LTS to the 5.10.21 kernel: The system rebooted just fine, though took longer then before. I didn't realize why until today, when I tried to access /media/mmcboot and discovered that it wasn't there. In fact, there is no /dev/mmcblk0p1 device at all. It's bizarre: it boots from the MicroSD, switches to my SSD, but then the MicroSD card device is simply gone when the system is up. I do not see this on two other Pine A64 (not LTS) systems. I was able to mount the microSD card on one of the other systems, and fsck reported everything was fine. I could also see all of the files just fine. The files in /boot had been updated for 5.10.21. But booting up the LTS again resulted in the same thing: it boots, but /dev/mmcblk0p1 does not exist. Any ideas? Thanks!
  13. All has been fine with my Pines for months now.
  14. No, they're not. Three separate systems: two Pine A64+ systems and one Pine A64-LTS. And they've now been running for over 54 days.
  15. Update: It's been a little over two weeks now, and all three of my Pines are running Ubuntu 20.04 LTS with the 5.4-43 kernel, and all have been running without problem.
  • Create New...