Although my last bootloader is adventure was pretty easy…installed a completely separate drive for Linux and wanted to boot off of that drive (sdb). A bug in the Linux mint installer put the bootloader on my the windows drive instead (sda).
Was fairly straightforward to switch over though (change in fstab then installing grub). I use the bios boot selector (F11) for me to select either the win loader or my Linux mint efi.
Am switching over to Linux as primary driver. So tired of nags, ads, “switch to Edge”, long updates, etc. love being able to ssh+x onto that (relatively beefy) box from my laptop and run ides and such.
My problems are usually during the installation, not necessarily related to Arch, but more so that EFI requires its own partition. I’ll partition my disk, forget that I need a FAT32 partition and then have to destroy a partition so I can add in the EFS . The other problem I’ve had is that the bootloader entry sometimes doesn’t get written after installation, so you reboot and then nothing, so you have to boot back into the ISO, remount everything, reinstall the bootloader (in my case, Grub), and reboot again.
I’ve been using Linux for more than a decade now as my daily driver.
Count me as ‘basic’ and ‘just starting’, because I quite like the colorful, clicky and nicely animated version, where I don’t have to remember anything and that works just as well.
And now out of my way, while I happily point, click and scroll to adjust my displays brightness, which is entirely possible through the terminal, but I’m not ridiculous or insecure enough for that.
I have multiple devices, but I just use my trusty KNOPPIX LiveCD to unlock the disk and move everything onto an external hard drive before either troubleshooting via chroot or just doing a clean install.
If it takes too long to load the EFI binaries, that might be BIOS setup issue. Have you tried other filesystems except FAT32 for the EFI partition? I’ve had luck with just FAT (FAT16) on some rigs that just refused to read FAT32 (still don’t know why).
Also, make sure the drives are in AHCI mode. Though this is mostly the default nowadays, I’ve seen weird BIOSes that defaulted to IDE mode.
I prefer to explain in detail how to fix that and then say in one short sentence how easier I would fix it on Linux if it happened on Linux, which it obviously wouldn’t. It’s usually completely unbiased and I’m a popular person :)
I have a pair of LaserJet 2200dn printers, they work absolutely fine in any Linux distro but I just have to make sure to use the below driver in my case:
HP LaserJet 2200 Foomatic/lj4dith (grayscale, 2-sided printing)
If I use the default or hpcups drivers it takes fucking forever (over an hour!) to process the pages. Essentially if given the option go for the lj4dith driver for your LaserJet
linuxmemes
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.