Im planning on giving it a try. Thought I would try dual booting pop os.
Windows wants me to update to 11, but my processor is too old. So if I’m going to update my processor, I’ll need to update the motherboard. But the OEM license is tied to the motherboard. So I’ll have to buy a new copy of windows just to get on 11.
So just gonna see if all the things I like to play work on pop os.
I think the biggest thing is that I use c# for hobby programming, and I know .net core should run on Linux, but not sure about the IDE.
Hey there. I run Linux on my daily but also work in a Windows-centric PC repair shop.
“Official” answer: You can move your key over to a new mobo by signing in to Windows with a Microsoft account, installing your new hardware, and activating Win 11 through the Settings->Activation->Troubleshooting (button)->“I recently changed hardware”. And that will pull your key back down from your account. But it does lock you into an account.
“Unofficial” answer: you can absolutely update to Win 11 on old hardware. The easiest way is to boot a Win 11 iso in Ventoy. That works fairly often. You can alternatively edit the installer to not do the TPM check in the installer, which you can search for guides for online/YouTube.
Alternatively: you can hop on g2a, kinguin, etc and buy Windows keys cheap.
To be clear I know this is all bullshit, but it’s options. Hope this helps!
Several years ago I had a significant hardware failure and was without a PC for longer than I care to admit. When I finally rebuilt it, Windows wouldn’t activate. So I nuked it and haven’t looked back. It’s not the first time I installed Linux. But it has been my daily driver since. Now I only use Windows for work, and Linux even there whenever I can (which isn’t often, but sometimes anyway.)
I had a few programs for various things and one was simply an extension from the gnome extension manager. I updated it and my screen turned black and I couldn’t get it back. I had to revert to a previous version, then uninstall everything until I figurd out what caused it.
Nope, I’ve checked and I don’t have any PulseAudio, JACK, or other audio packages that could interfere. This install has only ever used PipeWire for audio.
Could be kernel related, I don’t know. That’d be quite over my head, but I’ve had this issue using both the standard linux kernel and the zen kernel.
I didn’t see anything in journalctl’s logs that relates to audio as far as I can tell.
Reinstalling alsa utils twice? Interesting and weird.
Want to know what’s even more fun? I need to re-install alsa-utils thrice now after properly enabling pipewire.service like I did on that other comment thread :P
Nope, I’ve checked and I don’t have any PulseAudio, JACK, or other audio packages
Ok good. We should be able to rule that out.
Could be kernel related, I don’t know.
What version? The command uname -r will give it to you. More info here
Also… If you run dmesg do you see any audio related devices or errors? I should’ve thought to ask about that last time.
Want to know what’s even more fun? I need to re-install alsa-utils thrice now
Whee!™ Are we having fun yet lol
That is seriously bizarre.
Did I ask what audio hardware chipset you’re using?
It should show up in dmesg output. Or alternatively look up your motherboard specs and get it that way. Assuming you’re using the built in motherboard audio and not a separate card.
Hey don’t apologize for offering free help to a stranger online! It’s much appreciated. uname -r returns “6.7.0-zen3-1-zen”, but like I said I had this issue with the standard Linux kernel as well.
Nothing stands out to me when I run dmesg in terms of errors. I’m not sure which part is the audio hardware chipset, so here is the output relating to audio. I’m running both the built-in CPU audio and GPU audio through HDMI.
Edit: Forgot to add my ALSA and Pipewire packages. For ALSA I got:
Hm. Nothing really jumping out then. I am racking my brain trying to think of anything else to look at.
Dumb question but… Shouldn’t headphones be plugged into the headphone jack, not line out?
Headphones typically have a lower impedance than, say, an amplifier.
I’m just wondering if the audio hardware checks load impedance for audio out to prevent issues and the headphones are reading too low (tens to hundreds of ohms instead of, say, 10k-100k ohm or whatever) for a line out.
I don’t know how that explains reinstalling alsa-utils twice or thrice to fix it until the next reboot. So I guess my theory isn’t all that great.
Does it make a difference if you unplug the headphones before rebooting?
I had a similar issue with my laptop, where Arch wouldn’t be recognized as a bootable system on my NVMe drive unless I disabled RST with Optane on the BIOS, setting it to AHCI mode.
I do remember seeing a similar issue a while ago as well, but I don’t remember if the user managed to fix it.
I could suggest removing the Windows drive, installing Arch and checking if everything works, then plugging the Windows drive back in. Windows loves to delete non-Windoes bootloaders from every drive it can.
Dang, similar stuff happened to me on nixos. Had to instruct one of the relatives on how to reboot the machine and choose a previous generation in the boitloader 🤣
I’m relatively new to Mint, but I thought that sudo apt update just checked for updates and sudo apt upgrade -y was for actually installing the updates. I don’t see why that would break it though.
Actually, I have a story that I’d consider an achievement even though it was extremely stupid and by all accounts should’ve bricked the system but didnt.
So I was on windows and wanted to install linux as a dual-boot on the main drive. The problem was that my mobo didnt like this particular and the only flash drive I’ve had, dropping it out mid-boot, before I got any usable terminal, so a usual install method wasn’t an option. So I had this crazy idea to start a vmware vm in windows and pass the linux iso and the boot drive directly to it and try to install it live over the running system. Unfortunately, vmware guys thought of this and there’s a check that disallows passing the boot drive to vms. So i created a bunch of .vmdks for another drive and fiddled with them in notepad until I somehow managed to trick vmware and at some point it started booting the same windows copy that I was sitting on. I quickly powered it off, added the linux iso and proceeded to install like I usually would. It did involve some partition shuffling, but, somehow, it went smoothly, linux installed, grub caught on, and even windows somehow survived, even though it was physically moved around on the disk. It serms that vmware later patched this out, because later in an attempt to re-create the trick of running the same copy of windows twice, but after updates to both windows and vmware, I was met with the same old error that boot drive is not allowed when trying to add that same virtual drive I had laying around.
I had a similar debacle, when I managed to corrupt a btrfs file system to point it wouldn’t mount again…
I was preparing it to have as my main system on bare hardware. I had accidentally mounted the same block device simultaneously in the host and guest: kablamo silent corruption and all 5 hours of progress lost.^*^ :(
I had a similar setup once. Dualboot, plus the VM with the same physical disk, to access windows, while running linux.
All it took was a small distraction… I’ve missed the grub timeout, and accidentally booted the same ubuntu partition in a VM that was running on the real HW. To shreds…
Allrighty, now we officially need a program (I’m hesitant to call it malware since technically it’s for the user’s good XD) that covertly replaces a running copy of windows with linux… Besides, I think it was possible before to install stuff like Ubuntu directly from windows?
I was testing a custom initramfs that would load a full root into a ramdisk, and when I was going to shut down I tried to run rm -rf --no-preserve-root / to see what would happen, since I was on a ramdisk anyway. The computer would not boot after that because it nuked the UEFI options.
Lifetime Microsoft expert here, I have had machines with Linux in one flavour or another for 15+ years at least.
But for ease of use I just keep coming back to Windows… Because I know it backwards and upside down.
The structure of it makes sense to me. And I have ADHD so I have a terrible working memory and Linux relies FAR too much on command console to do anything effective.
But Linux is hands-down the better system to get away from Microsoft’s enshitification of Windows. But I personally like Windows better.
So I will always run both. But if I need to be really productive, Windows Desktop it is. If I need a server, Linux every time. (Unless it’s MS SQL or a website).
I like it, but I’m not exactly a power user and the only other distros I’ve used are Ubuntu and mint. I think if you want a Debian based distro that’s not tied to Ubuntu then Mx is a good choice. I know there’s LMDE too but as far as I know that’s only available with cinnamon, so Mx having KDE plasma is nice too.
There’s the whole sysvinit Vs systemd but I don’t have a dog in that fight and enabled systemd, which Mx makes very easy even though they advise against it.
I am using UEFI, and GRUB for my bootloader. I did update my post with a bit more information now.
I was not able to select boot order in BIOS because it wasn’t reporting properly, or my drives were “messed up” along the way.
I did not have the option for my Windows drive listed as a bootable option. It did however show a generic entry for my WD Black drive (which is what I installed Arch on) as a bootable entry, but it ended up booting to windows after forcing the machine down because Arch hung at initializing Ramdisk.
I had the afterthought to choose to install os-prober for grub within additional packages.
Not being able to select boot order in BIOS suggests something very strange is going on, because it suggests that the BIOS can’t see all the drives. That has to happen before the bootloader can be evoked.
It sounds like GRUB is installed on the WD Black. BIOS -> drives it can see -> boot loader
What was the specific error that the Arch boot attempt threw? How did os-prober work for you?
It sounds like the issue is with the lid latch/sensor, not with the graphics. Some laptops may not boot if the lid is closed, and some have options on the firmware to enable to boot when the lid is closed / on a docking station.
This seems unlikely since it boots with a monitor attached. From past experience most laptops that refuse to boot while closed don’t boot even if an HDMI display is connected.
linux
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.