Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Yeah, I'm able to pull up nvidia-settings, but even as root it doesn't seem to be working correctly. Some settings seem to change fine, but when I click the 'Save to X Configuration File' I first get a message about Multiple X screens being set to absolute positioning. Then I get a message that it failed to generate x config file. Then it comes up with Save X Configuration but when I click 'show preview' it is blank.You can start nvidia-settings with sudo so it can write to the xconfig file. Might be the easiest road now that you have the GUI up.
Yeah, I'm able to pull up nvidia-settings, but even as root it doesn't seem to be working correctly. Some settings seem to change fine, but when I click the 'Save to X Configuration File' I first get a message about Multiple X screens being set to absolute positioning. Then I get a message that it failed to generate x config file. Then it comes up with Save X Configuration but when I click 'show preview' it is blank.
There were a lot of Linux users who used it primarily as a status thing. Linux wasn't as easy to install and configure so it put them in their own made up elite club of people who could actually use Linux. Over time, things changed and Linux became a lot more accessible. There were GUI's for installing the OS, you didn't have to manually partition to install, you didn't have to understand file systems and swap, and everything you needed would come working out of the box. Hell it wasn't too long ago that using Linux on a laptop was a huge nightmare because 99% of the time, it wouldn't come with wireless or ethernet drivers. Now installing Ubuntu is easier and objectively better than Windows. You can still configure everything like you used to, or you could click 5 things that are all in very plain english and it will install a full GUI desktop, all your drivers will work, and every piece of software you could ever want is installed and ready to use.
The gap was closed between regular computer users and the "elite few" in that special made up club I was talking about earlier. People had issues with Linux being more accessible so they moved to one of the least accessible versions - Arch. Installing Arch isn't hard, it just takes a little effort and maybe a little research. This was enough for some users to fill their gatekeeping jollies. This lasted a couple years until Manjaro came out and became popular. It was Arch, but any person who had even a little bit of computer savyness could install and use it. The gap closed just a little more between regular users and the "elite few". Now the community has turned on itself for Arch. You try and get any kind of help, even something moderately hard to fix, and you get ridiculed for even asking. You even bring up that you use Manjaro and you can practically feel the rage of some Arch users coming through your monitor.
This is an absolutely accurate explanation of why it is a pain in the hole to get help from the Arch community.
There's a Linux server on discord that is run by one of the worst human beings I've ever encountered in my entire life. Now frankly that's reason enough to stay away from that server, but one of the most sacrosanct and rigidly enforced rules in that server is they *absolutely refuse* to help anyone running an Arch derivative (Manjaro, AntergOS, anything) - and that includes Arch itself if the user installed it using Zen Installer - which is absolutely ridiculous because Zen installer is literally a GUI for installing stock Arch. All it really does different is it will partition a drive for you instead of forcing you to decide on a partitioning scheme, and it allows you to enable an extra repository during install if you want to.
Unfortunately this is very much the norm with Arch folk I have found. It's not a case of simply expecting people to have tried to fix their own problems. It's an active and present dislike of anyone that isn't already at their level of understanding.
For example, Arch Wiki did previously have a basic install guide and it was removed. Not because it was outdated or not useful - but because it allowed people who didn't understand Arch to install Arch.
Then you get articles like this one, which are just horrendously written and needlessly confusing: https://wiki.archlinux.org/index.php/fstab
Reason being, it's normal on the Arch Wiki, to never provide a simple explanation inline with your own writing. Instead, every article links to every other article, making it a trawl to understand any given statement because you have to backtrack from what you wanted to know (How fstab works) to what a block device is and fully grok that before you can actually understand fstab.
He was a programmer for Microsoft and was running an in-house version that they designed and he had some kind of part in. This was about a year after Windows 10 was released and I was already in the process of getting ready to move completely to Linux for home/personal use. <snip> He turned right off. I saw that he wasn't about to talk to me anymore about Linux. <snip> The rest of the 6 hour flight he plucked away on his keyboard, drank like it wasn't a 9am flight, and didn't say a word to me.
It's pretty bad when you find another Linux user, they ask what distro you use, and if you say any Ubuntu flavor, Manjaro, or Soulis, they turn their nose up to you. I shit you not I was on a plane from Seattle to go to Microsoft Ignite a couple years ago. I was sitting next to a guy who had a Surface Pro with Linux stickers on it. I glanced over and he was running some flavor of Linux with a Gnome 3 desktop. At the time, Linux pretty much didn't work *at all* on Surfaces and Surface Books so I was curious what he was running. I tried to avoid making it obvious that I was checking out his screen because it looked like he was doing some work on the plane. I asked him about the Tux and other Linux themed stickers on the back and he kind of lit up and got excited. He was a programmer for Microsoft and was running an in-house version that they designed and he had some kind of part in. This was about a year after Windows 10 was released and I was already in the process of getting ready to move completely to Linux for home/personal use. To help the conversation I told him that I was bouncing around distros but I really liked Ubuntu Mate on my laptop (fuck me, right?). He turned right off. I saw that he wasn't about to talk to me anymore about Linux. I brought up that I was a DBA and basically lived in Oracle Linux, our CentOS environment and it all connected to another handful of Windows Servers that was hosting our MSSQL servers for reporting services but he wasn't having it. The rest of the 6 hour flight he plucked away on his keyboard, drank like it wasn't a 9am flight, and didn't say a word to me.
This is an absolutely accurate explanation of why it is a pain in the hole to get help from the Arch community.
For example, Arch Wiki did previously have a basic install guide and it was removed. Not because it was outdated or not useful - but because it allowed people who didn't understand Arch to install Arch.
I'm not sure what guide your talking about, but here is the installation guide.
And that guide is only a shell of what it used to be.
Previously the install guide was so comprehensive and complete a first time linux user could build an Arch system without many issues.
It was literally line by line commands that did the entire install for you.
Yup. And that's a "new" (compared to the old one) page - the edit history only goes back to 2013.
Here's the 2007 Arch Install guide via wayback:
https://web.archive.org/web/2007110...hlinux.org/static/docs/arch-install-guide.txt
Deep, comprehensive, explained in-line and generally far more helpful than the present approach of redirecting a user to 500 other pages to understand the one term they didn't grok immediately on the first page.
Working through the linked guide now, but in a Hyper-V VM...
So far it's a failure, can't get past GRUB, but hey, GRUB!
For building Arch?
Yup. First time; haven't done any of this stuff strictly from the console before.
Figured I should go ahead and earn my 'I use arch btw' poof.
I get the word 'GRUB' and a blinking cursor...
So the infamous blinking cursor error?
At work, will play with it later.
It's Arch, I expect it to be obtuse, and don't expect 'the community' to be of much help.
The chance that someone will answer affirmatively that Arch can by run in Hyper-V, and if so, what adjustments might need to be made...?
Boot to rescue mode and check the logs what went wrong.I get the word 'GRUB' and a blinking cursor...
So the infamous blinking cursor error?
At work, will play with it later.
It's Arch, I expect it to be obtuse, and don't expect 'the community' to be of much help.
The chance that someone will answer affirmatively that Arch can by run in Hyper-V, and if so, what adjustments might need to be made...?
Well, I'll admit that my log-fu is near non-existent. Add it to the list.
But I was able to get it going after some experimentation.
Basically, had to use gdisk (I think) to set partition types after redoing the partitions, with a BIOS partition first, then data, then swap, and then installing grub and running its configuration.
That got me booting!
Now for stuff like GUIs...
ALSA is never what you want to run for DE sound.
For that you want a sound server, pulse. So ya you need to setup both. They aren't duplicated things... ALSA is a low level kernel sound system, Pulse is a sound server very much like windows audio.
Glad you figured it out. All the ragging on arch you are proving their exact point... they aren't holding your hand they want their users to figure out how Linux works under the hood a little. Take that for what it is.... arch isn't intended to be a regular user distro. Some people like to pile on the arch people for not being nice to new Linux users... but they make it very clear they aren't making a distro for new Linux users, you will learn a ton of stuff setting arch up if you are a newer user. But they aren't looking to compete with Ubuntu or Mint. I'm sure newer users trying ti install rolling debian and having issues would run into the same minimally helpful support from Debian gear heads.
Good luck with your further exploration of arch JS it might never be your daily driver... but you'll learn a few things about Linux that might come in handy at some point.
What is DE sound? Default?
I'm slowly working toward it being my daily driver. I've learned a lot since I started my test last year and I appreciate your input and encouragement.
Right now, stealth dependencies are driving me nuts but I'm guessing I'll learn more about that as I go.
I started setting up a dual boot on my laptop which doesn't have a wired ethernet port, so yeah, wireless. On Linux. : /
So, after boot from the USB live image I of course had no internet. No internet means no install.
So, after beating my head on a wall for a few hours I finally came up with this solution.
1. I enabled broadcast on my network SSID and disabled all security. Trying to setup wireless security and connect to the wireless network from a live image was way to complicated to just get an install done. I'm in a relatively rural neighborhood so the short time without security hopefully won't be a problem. Hopefully. lol
2. After boot to the live image, I first type ip link to get my adapter name.
3. Next, I had to turn it on with ip link set wlp2s0 up
4. Next, I then connect to the wireless network with iw dev wlp2s0 connect SSIDName.
5. And finally, run dhcpcd. Just typed dhcpcd and it worked.
6. ping google.com and my device is connected.
Yeah, I'm not a fan of disabling security, but wpa supplicant doesn't seem to be connecting very well to WPA2 even though the wiki says it is supported. I'll deal with that after the install is up and running
For install from the live CD you can just use wifi-menu. Once you learn Arch better you'll also realize that you can install EVERYTHING during the chroot part of the install so after the initial reboot you can have NetworkManager and a DE already up and running making it much easier!
For install from the live CD you can just use wifi-menu. Once you learn Arch better you'll also realize that you can install EVERYTHING during the chroot part of the install so after the initial reboot you can have NetworkManager and a DE already up and running making it much easier!
Ok, looks like there are competing services for internet access. I was attempting to follow the Arch Wiki instructions for Wireless network configuration which uses IW or Wpa_Supplicant. The article doesn't even refer to their own internal project, netctl.
So, I disabled dhcpcd, ran wifi-menu, and bam, it just worked.
Thanks for that recommendation man. I was about to go crazy using iw. : /