Yes, you’ll be fine

Many fancy motherboards have a button to reset these settings as well. Often the bios settings are referred to as CMOS settings as well.

I don’t know of any project to do this, but it’s an interesting idea.

For most/all phones, you would need to break the phone’s software security to boot another OS. To boot via USB the phone’s firmware would need to support that, or a sufficient USB vulnerability could be used to take over a running system and boot into a new OS. This would almost certainly be unreliable and only work on specific devices.

Note that if part of your goal is to extract data from the phone, only old phones store data unencrypted these days. One advantage of using a vulnerability to hijack the current os would be the availability of the keys to decrypt the phone’s storage if the storage is already unlocked.

Although it’s not as interesting, you certainly can load firmware on an android device that will boot from USB. Not sure if this already exists or would need to be built.

Have you tried changing the connections in this script to use the audacity inputs instead of pw-record?

Also I thought audacity was out, tenacity is in.

Also it looks like wireplumber has some options that my be relevant like node.features.audio.monitor-ports listed here:

https://pipewire.pages.freedesktop.org/wireplumber/daemon/configuration/settings.html

Lower decks

I second this. I need to try guix, nixos has been my daily driver for years now.

Maybe try kscreen-doctor? I don’t use kde regularly but that showed up in a search.

Maybe this? https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/3678

Try using alsamixer, check for channels that are muted.

Also check if your distro is saving and restoring alsa settings every boot and remove the settings file

Grub should be able to boot mint fine, just know where grub is installed and which disk boots the system before formatting anything. To test, unplug the windows disk and see what happens

I think xvnc does this with vnc. If using gnome start gnome-remote-desktop with systemctl --user start gnome-remote-desktop then use grdctl to set it up (or the settings gui). I’ve had luck with rdp on a Wayland session this way.

Sounds like the right choice! I’m glad you got Debian up and running,

I get paid by the hour! 😅 But for real though it’s a struggle. Mostly I try to use msys2 for everything but. I still have native git. There are some long standing bugs that make the vim excruciatingly slow to open or close, really I should go try to fix it but it doesn’t feel like a fun problem.

For work, I just use windows. Not my machine not my problem.

Don’t be afraid of the command line, breaking Linux is how you end up learning how to use it!

I haven’t done this tutorial but if that kind of thing helps you this one looks pretty good.

My best guess is you need to do something like:

(In the shell, one line at a time, enter runs the command)

mkdir /mnt/tmp
mount /dev/sda2 /mnt/tmp
nano /mnt/tmp/etc/fstab

Nano is a text editor that uses your whole terminal, so you will see the contents of /mnt/tmp/etc/fstab (the file that controls where disks are mounted) and replace ‘sdb’ with ‘sda’ on the line starting with /dev/sdb2. The bottom of nano’s screen shows you the keyboard shortcuts, I think Ctrl W will make it write the file, asking for confirmation of the filename, which should stay the same. Exit nano (Ctrl+x maybe?) then reboot with the command ‘reboot’

If you get any errors about access denied or permissions, run ‘sudo bash’ to get a shell with more power and try again.

Good luck!

What most likely happened is your disk order switched and, as others have mentioned, using /dev/sda1 or something similar to point to partitions is unstable and can’t be trusted. Once your system is back up, look up how to specify partitions in /etc/fstab using UUID (something like /dev/disks/by-uuid/xxxx-xxxxxxxxxx-xxxx instead of /dev/sda2)

When this happens to me I mostly assume Linux shutdown automatically because of a critical over temperature event. I’ve seen it in the logs a few times but I don’t usually check anymore.

There’s an example of this here https://unix.stackexchange.com/questions/502226/how-do-you-find-out-if-a-linux-machine-overheated-before-the-previous-boot-and-w

Idk I just bought a 32GB stick of ddr4 sodimm for $60, adapters are less than $10 each so maybe not if you stay away from scalpers and don’t pay attention to ram speed 😅

I was also thinking the soldered CPU motherboard with 8 cores must cost at least 200 but maybe that’s a bad assumption and I didn’t look it up.

Looks like most of the nibbles are fine. Maybe something happened to the connectors or traces. At least you know it’s the ram not your motherboard.

Also, what do you mean by crashes? Kernel panic? Random app death because the oom killer was activated should be expected when pushing the memory limits on Linux.

I’m running 8 and 32 in my T490, seems to work fine. I’m building software and leaking memory like crazy and it’s never been weird. I don’t see why 8 + 32 would be any different than 8 + 16 other than capacity.

Doesn’t the channel balance not matter that much? Like operations can be done in parallel. I always thought the benefits came from reading different things from each ram chip not synchronizing them byte for byte.