Jump to content


  • Posts

  • Joined

  • Last visited

1 Follower

Recent Profile Visitors

1343 profile views
  1. CryBaby


    Take the SD card out and put it into another machine. Copy the whole card as an image. To restore you just copy it back. On Linux I would use dd for this: sudo dd if=/dev/mmcblk0 of=backup.img bs=1M status=progress making sure you have the right dev. It should not be mounted while you do this. On Windows... Balena Etcher?
  2. You are mistaken. Please reread Steeman's last post until you understand it.
  3. Plug your phone in. Set it to USB tethering. NetworkManager will probably detect the connection and you can use it like an ethernet connection.
  4. apt-cache search libpython3 will show you which versions are available. I would expect any version higher than 3.7 would also work for you. sudo apt install python3 will install the latest available version.
  5. Another option I have read about is to set SECLEVEL to 0, so you would have: [system_default_sect] CipherString = DEFAULT:@SECLEVEL=0 Options = UnsafeLegacyRenegotiation
  6. If you are using WPA then you probably don't have RADIUS as that is for central auth in enterprise environments, usually they use PEAP. That doesn't necessarily rule out OpenSSL as the culprit though. I get the same error as you at work but have no problem at home where my router runs OpenWRT. Perhaps there is a menu option in your router for firmware updates. You could try the workaround suggested in the link I posted: > > adding this to /usr/lib/ssl/openssl.cnf fixes the issue. > > > > [system_default_sect] > > Options = UnsafeLegacyRenegotiation It may not be quite that simple, it didn't work for me. Alternatively, you could get hold of another router (gl-inet.com) that you can connect to and hook it up to your main router with a cable from WAN to LAN ports.
  7. Is your router using RADIUS? https://www.spinics.net/lists/hostap/msg09840.html OpenSSL has disabled insecure old TLS auth which should have been fixed 10 years ago but it turns out not everyone has. Try updating your router firmware.
  8. This is the real solution. Annoying passwords are only enforced at installation. Change it straight afterwards and forget the annoying one.
  9. Blimey! $369, I think I paid $129 for mine. It is a lovely machine which I hope to get working again soon. I wonder if there is a P3 in the works.
  10. I have tried the clearing of eMMC option. Unsurprisingly it cleared the eMMC and I can no longer boot to Station OS. I can still boot to Balbes' UPDATE_UBOOT image from SD card. The other option is 'Delete bootloader'. I have not tried this but I think it must clear the SPI. You would definitely want a working uboot in eMMC before doing that. The question I have is if you do that and have an empty SPI will the bootrom go to the eMMC or will it hang? Firefly have RK356x_NorFlash2eMMCLoader_20211209.img which suggests you need something in SPI (aka NorFlash) to redirect to the eMMC. This page goes into it. I don't have Windows, no longer have Station OS (so no ADB) and have so far failed to enter MaskROM mode so I'm a bit stuck.
  11. Only build them if you actually want feedback, otherwise we'll just annoy you with bug reports.
  12. Now I look at the contents of p2-station-update-uboot I see it has in fact not worked; the writing of the new uboot did not occur. Presumably the SPI must be erased first. So how do I do that safely?
  13. root@station-p2:~# sudo /vendor/p2-station-update-uboot 16384+0 records in 16384+0 records out 8388608 bytes (8.4 MB, 8.0 MiB) copied, 0.378473 s, 22.2 MB/s 8192+0 records in 8192+0 records out 4194304 bytes (4.2 MB, 4.0 MiB) copied, 0.159035 s, 26.4 MB/s I have had this P2 for a year and have updated to the latest Station OS, and enabled/disabled the OS Bootloader several times. I have of course studied that thread. I was hoping your fix was in the latest Station OS update but I guess not. It is not clear to me how to erase the SPI as you suggest. There are some advanced options that might do it in the OS Bootloader. I worry that I may end up unable to boot anything.
  14. The image here does contain the p2-station-update-uboot script. It runs successfully but Armbian_22.05.3_Station-p2_bullseye_edge_5.18.0_xfce_desktop.img and Armbian_22.08.0-trunk_Station-p2_sid_edge_5.19.3_xfce_desktop.img do not boot.
  15. The instructions at the P2 page cannot be followed. The image at the link does not contain the p2-station-update-uboot script. I have tried using the Station OS multi-boot thing but that didn't work either. What is the correct way to do it now?
  • Create New...