bweh

ts good but ftlog why installing waydroid is so hard on there😭

this is the end of the world

ok came back im stupid

ayo this the bigger than sign

without the proprietary google services package yes, but not entirely free from google. one obv example is connectivity check that pings google is still there as far as im aware (please feel free to correct)

ima ruffle up that fur🫳

id bow to her everyday😩

stk and luanti are the only real games

bwahaha that went a tad deeper than your regular “cute!!” comments expected under a post in this and similar cat communities 🧨

Apparently I don’t need to reattach the CMOS battery as attaching the big one works for saving the settings and keeping the clock ticking, so far no difference though regardless if i reconfigured it or not

No, it just places a bang (!) on the left of any of the entries on the screen, and if I hit shift + 1 on Linux Boot Manager and reboot, I get greeted with a completely empty boot menu now (Except the Application menu with a Diagnostic Screen and Setup options), removing the bang with the exact same key combination and rebooting shows it back, but no new entries seem to be able to add in any way as I understand.

Have doubts that it will change if I’ll replace that CMOS battery (and make it hold in place somehow) when its the same even without the battery but will try…

Err, it’s completely broken off now (the plastic holder broke) so it isn’t even in place at the moment. It was connected during the incident so may be a reason?

Hm. Any actions I can take to further identify the issue and get more understanding of what can be done?

i am no longer. embrace tolerance.

The drive we booted from that time was in frequent use actually, it had Ventoy on it and booted ok on all my other computers, including some of other people’s devices. This exact drive was lost not that long ago, but I have an another one with Ventoy too, works perfectly on all my other devices as did the previous one, except for this laptop. Like the supposedly default entries were not really hardcoded into the thing that saves them, or something? And installing systemd-boot just wiped all of them off? Either way, not sure if boot devices themselves are the problem as they boot fine on others.

working on it

iam with you my frien