This is the guide I followed when I was installing Arch manually. I hope the method has not changed. Make sure to choose the correct partition if you’re planning on dual booting.
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?
and a need to find another PC to flash an archiso to a flash drive ('cause ofc I didn’t have one at the time).
you can do that from your phone using etchdroid
i don’t remember ever breaking my system in a terrible way, but when i started using linux (with linux mint) i uninstalled ca-certificates and i think that uninstalled the whole DE
Probably PoP_OS!. There isn’t anything wrong with the os itelf, my problem is rather that its often sugested as a beginer friendly distro which in my experience it absolutely isn’t. The amount of issues I encountered while trying to use it almost drove me away from Linux as a whole. (It was the first distro i tried) The time I spent trying to make everything work was comparable to Arch.
I realy like the idea and the DE they ship by default is one of the best ones I’ve seen (it’s like GNOME but in my opinion much better) but the bugs make it a terrible suggestion for new users.
There are a few ways to investigate, but for that we would need a bit more info. Firstly, what distro do you use ? Try using a different bootloader than GRUB to see if it solves the issue. Otherwise you could also try to use Linux’s UEFI stub.
About 90% of what I know about ssh, terminal multiplexing, scripting, and diagnostic programs grew from an optimization project.
I had a vague desire to build a one-stop dashboard where I could monitor, update, and control a half-dozen linux computers at once. It was just for fun, but it kept me reading through the manpages for weeks.
I didn’t, but only because my solution wasn’t novel or generalized for other people. I made a script to fire up tmux on a ‘primary’ computer with key-based access to my other computers, load up a set of windows and panes, and ssh into each computer. One window would be computers in one section of my home, another window would be computers elsewhere. The only challenge was getting a baseline grasp of the tmux scripting syntax.
I initially set it up to run htop on each computer (dashboard goal, plus easy ability to terminate programs), but the basic setup was flexible. I could set other programs to run by default or and send terminal command updates to each computer from any device that could ssh into the primary computer. Automating updates on a computer-by-computer basis is a better solution, but the setup let me quickly oversee and interactively start multiple system updates at once, from a phone, tablet, or laptop.
user@hostname:$ ls /etc/subuid ls: cannot access ‘/etc/subuid’: No such file or directory user@hostname:$ ls /etc/subgid ls: cannot access ‘/etc/subgid’: No such file or directory
Well, that’s your problem. sub?id is what defines which uids and gids are available to a user for purposes of making user namespaces. It’s strange that those files don’t already exist; useradd should create them automatically. What distro are you using?
Regardless, you can create those files yourself. Here’s a line from subuid my machine: administrator:100000:65536. The first field is the username (you can also use a uid), the second is the starting uid for the block of uids, and the third field is the number of uids in that block. So uids from 100000-165535 (inclusive) are allocated to the user administrator.
I tried some distros but always went back to Ubuntu and then I settled there. Until like 3 days ago. I installed Parch (basically Arch with a GUI installer) and I think I will stay for the AUR.
Solution: the RPM Fedora version did work, the version from Flathub or the Fedora flatpack repo did not work. I guess the flatpack versions don't have the most recent xfreerdp version? I don't really know...
U til you mentioned Guitarix I wasn’t even familiar with that software. Unfortunately I don’t believe there is any connectivity between PowerCab or my Helix with guitarix. But Guitarix could still be handy to me. Thank you!
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.