goathunter

  • Posts

    24
  • Joined

  • Last visited

Recent Profile Visitors

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

goathunter's Achievements

  1. Has anyone tried the latest upgrade to 5.10.34 to see if this problem has been resolved?
  2. 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!
  3. 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.
  4. 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
  5. Thanks for your reply. I'm glad I'm not the only one seeing it!
  6. 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.
  7. 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.
  8. 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!
  9. 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.
  10. 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.
  11. I attempted to upgrade one of my Pines running 4.19 to 20.04 LTS. It didn't complain, but I discovered when it rebooted that the installation had wiped out several files in my /boot directory. No idea why, but I couldn't recover from it. I ended up just starting from scratch with the Armbian Focal distribution. I'm now running that on two of my three Pines (I finally gave up on the fourth one, as it kept having various hardware issues). It's only been a couple of days, but there've been no time jumps yet with the new kernel (5.4-43).
  12. It's now May 26. None of my Pine systems has time-jumped since going to 5.3.9 and patched 4.19.83 as described in my March 25 post. I still have not retried 5.4 or higher. FWIW.
  13. Interesting. I finally took the time to pull down the current Armbian kernel code and build it so I could see what's in there. The post-build arm_arch_timer.c files are identical for my patched 4.19.83 and the sources I got with "git clone" this morning, which means that the patch is included in the current sources. But I have other issues with 5.4.20, as I documented above, so maybe 5.4.20 does solve the time-jump problem, and I just don't know it because I haven't run it long enough (because of the other problems: kworker processes chewing up CPU time when idle, incorrect CPU temperature readings). 5.3.9 did not solve it, but perhaps the patch wasn't included in that. I haven't tried to figure out how to check that. Update: after a week and a half, all four Pines are fine (two on patched 4.19..83, two running 5.3.9). No time jumps on any of them.
  14. Link sent. If anyone else wants them, let me know. Hunter