I wouldn’t be surprised if they started working on it, but even if they had a design ready, it wouldn’t happen overnight. Apps, and Android itself, don’t yet have support for RISC-V (though I believe Android 15 has preliminary support).
At the moment, Qualcomm likely has to bend over and take it
Arcane is a fantastic series, eagerly awaiting the next season. Even my sister is into it (and as far as I know she has no clue what League of Legends is)
Another point for Linux
Anal (Ubuntu)
Because at this point, if you’re still on it you’re taking it up the ass from Canonical
If I had stopped reading after 2 seconds I wouldn’t know it was the lemonade, something that should be put front and center because if I was a drinker of minute maid zero sugar lemonade and I saw “Coke recalls popular zero sugar drink”, I wouldn’t’ve bothered reading further.
Headline could be written better, I warned my friend who’s sister is a diabetic before realizing its just the lemonade
Interesting, both of my F40 installs with btrfs only have a root folder, but it looks like yours has created separate ones for /, /home, and /boot. run ll /mnt/boot; ll /mnt/home; ll /mnt/root so I can take a quick look at where things are located. My best guess is that sda1 gets mounted to /mnt/boot, while everything else (/dev, /sys, etc) gets mounted to /mnt/root
Since you’re using btrfs, there is likely another subfolder under /mnt. ll /mnt will tell you this, but the drive isn’t still mounted from the other day. When you’re mounting the EFI partition, you’re going to want to mount it to that folder, and not /mnt itself (/mnt/root/boot/efi, instead of /mnt/boot/efi) same for the binds (/dev, /proc, /run, etc)
Yup, should be the same release, just using a different token and therefore needs approved separately
Ugh they didn’t keep the same oauth flow so I have to get IT to approve it again for Outlook
Could you send me the output of lsblk -no FSTYPE /dev/sda3 and ll /mnt?
Apologies, I think I got a bit ahead of myself in the description.
Once you’ve determined which partition is which (in your case, /dev/sda1 does appear to be the EFI partition, and /dev/sda3 appears to be your root partition), you need to mount them in this order
mount /dev/sda3 /mnt
mount /dev/sda1 /mnt/boot/efi
That’s alright, I’ll do my best to walk you through it.
Your drive contains multiple partitions (/dev/sda1 through /dev/sda3).
One of these drives is going to be your EFI partition. This is what your system can read before linux boots, your BIOS can’t understand ext4 / btrfs / etc, but it can understand fat32.
If you run lsblk -no FSTYPE /dev/sda1 it should return vfat if that’s your EFI partition. That’s what we’re going to mount to /mnt/boot/efi
I’m assuming that /dev/sda3 is your data partition, e.g. where your linux install is. You can find the filesystem format the same way as your EFI partition.
Edit: After determining which partition is which, you’re going to want to mount the root partition, and then the EFI partition
mount /dev/sda3 /mnt
mount /dev/sda1 /mnt/boot/efi
Unix systems have theology of “everything is a file”, all devices and system interfaces are mounted as files. As such, to be able to properly chroot into an offline install, we need to make binds from our running system to the offline system. That’s what’s achieved by running for i in /dev /dev/pts /proc /sys /run; do sudo mount -B $i /mnt$i; done
This is just a simple loop that mounts /dev, /dev/pts, /proc, /sys, and /run to your offline install. You’re going to want to either add /sys/firmware/efi/efivars to that list, or mount it (with -B, which is shorthand for --bind, not a normal mount).
Once you’ve done this, you should be able to successfully chroot into /mnt (or /mnt/root if running btrfs)
At this point, you should be able to run your grub repair commands.
I’m doing my morning scroll before I start my day, so I can’t delve too deep, but this is the article I always reference when I have to do repairs
https://askubuntu.com/a/831241
#1 thing I noticed in your image is that lsblk only shows you partitions, and doesn’t mount them. You probably want /dev/sda3 mounted at /mnt
The only thing from the article you want to modify is using
mount -B /sys/firmware/efi/efivars /mnt/sys/efi/efivars, I believe the functionality changed since that article was written and that’s what worked for me
Additionally, if you drive is formatted as btrfs instead of ext4, once you mount your drive your root will most likely be at /mnt/admin or similar. Mount subdirectories to that folder instead of /mnt
If you have questions lmk and I’ll get back to you at some point today
SFC has worked numerous times for me, usually for botched updates. Haven’t used it in a long time after leaving tech support
This got me to finally move away from Edge. Only thing I’m wishing comes soon is native PWA support. The addon is so janky and my biggest gripe about using Firefox, but I can put up with it since I’ve now got vertical tabs and multiple profiles
I took a peek in a recycling bin last time I was at Target and saw a handful of vapes in there, this would be a good place to start.
Had to do a demo the other day and looked like a fool because I couldn’t screen share on Wayland
That’s how I’m reading it at least
I’m using the stick pixel os (rooted) and keep my bootloader locked with this https://github.com/chenxiaolong/avbroot