Ah, so it’s the boot order and why it can’t mount the volume.
The wiki seems to suggest a process to boot reliably from SD card, but I’m seeing a lot of posts with the same issues. https://wiki.friendlyelec.com/wiki/index.php/NanoPi_R5C#Install_OS
Bad SD card.
SD cards aren’t meant to handle sustained read/write loads, and they wear out and die quickly on these devices. Start with a fresh card, and if you run a lot of services that generate a lot of log noise, set up log2ram to help extend the life of the SD card. A more permanent fix would be to boot from an SSD which won’t have these failure issues.
If it’s a time-based issue, it’s heat or memory.
If you can boot back to Windows and have no problems at all, that would be interesting.
In Gnome it will appear as a network device in the quick menu. Just like Ethernet or WiFi. On KDE, YMMV because it already has issues with network devices that come and go.
Yes, and I’m telling them how. The MODEM is the device that will be the piece of hardware that works or doesn’t. eSIM doesn’t matter.
Heat or memory issue.
Are your fans running?
eSIM is just a card. That card plugs into a modem. That modem hardware is what needs to be supported by the kernel. Find out what the modem is, then search that to find out if it’s well supported.
Are you behind a few distro upgrades? They do deprecate the non-LTS mirrors.
404 HTTP error. Your mirror is down. Try again later, or switch your mirror.
Lookup the modem model and see
If you’re just trying to familiarize yourself with GUI programming in general, the fastest is going to be Gnome Builder or QT Creator (depending on which DE you’re working in). Both are great tools, and make it super easy to understand what goes into all the different pieces of making a GUI app.
If you want something more portable to mobile, maybe Ionic or Cordova would be interesting to you.
Love that you put it in quotes as if to be sarcastic. Hilarious.
This is basically how the entire Internet works, but you know that from your post. Surely you also know that traffic gets “routed” from place A to B all the time without SSH as well.
So if you want to “route” a remote instance back to another place, you:
Another alternative is using Tailscale and setting an exit node on your network, which is essentially the same thing.
But you already knew that, and that’s why you chimed in with your comment. Stupid me.
How fucking stupid must I look, huh?
Wut. C’mon.
If I’m reading this right, you just need to learn about routing. SSH has nothing to do with this. This is basic networking at best.
What kernel are you on?
It stretches the player models out and makes them easier to hit I guess? Seems pretty stupid, but people do it.
It’s not that there’s anything inherently wrong with this, but it’s not the most in line with your goals. If you’re worried about data loss, you could have made a volume that spans both drives like RAID1/Z1, or you could have setup some clever data spanning with BTRFS or likewise. Then you’d be killing two birds with one stone for the Timeshift portion.
If you want safe backups, you need a separate backup drive at a bare minimum.
Well Nix and other immutable distros are about versioning with binary compatible layers that will be repeatable. Directory structure is already baked-in, so that’s sort of my point.
This project, from the docs at least, seemed like a week intentioned thing that has been handled and passed over in a different way.
Not to offend, but the entire premise of this distro is about directory names, which seems a bit…dated. What are the other selling points?
The other option here seems to be using uboot to boot your SD card: https://docs.u-boot.org/en/latest/usage/partitions.html
Since you know you can boot it via USB, you can just tell it to then boot from your SD Card instead of relying on the r4s to boot it. Docs say it’s possible to flash to the eMMC as well https://wiki.friendlyelec.com/wiki/index.php/NanoPi_R4S#eMMC_Boot