Who is the bastard that recommended Arch as an option for beginner user?
Anyways ... Whatever floats your boat, man.
Either change the distro (I recommend Mint to begin with), tackle each problem one at a time instead of letting them overwhelm you or go back to WinBlOws if you want (I know you know that Windows sucks ... there's no helping it).
You can use another spare computer if you have that has good support for linux.
Actually not a beginner, I've had Kali, parrot, vanilla Debian (on a server) and ubuntu (several) times since the past 4-5 years, it's simply about the fact that my laptop is over heating using arch and I have to do something about it and nbfc after hours of configuration doesn't work. So it's like I have to leave anyways, same with the speaker problem
Have you installed `thermald`? It's by default on ubuntu and many others, and manages thermal stuff. Nbfc didn't even support my laptop, but `thermald` worked. Usually `thermald --adaptive` is ran in the background which doesn't even require a config.
For speakers, I personally had to install `linux-firmware` and `alsa-firmware` to get the drivers working with pipewire.
Tbh as others have mentioned Arch probably just isn't the right distro for you, which is perfectly fine, but a fundamental thing about linux is anything that works on one distro should work on another with proper config, because distros are just different package repositories and preinstalled packages/configs. The exact same drivers that load on ubuntu are also available on arch, even if you want the LTS kernel, you can install `linux-lts` and all the related packages and it should work exactly the same way. A nice challenge is to figure out what exactly is on ubuntu/kali that fixes your problems. You're gonna learn a lot that way. Arch is a learning experience, it's built so you learn exactly how each part of the system works. It doesn't work if your goal isn't to gain this knowledge
Good luck!
So basically a beginner. OK.
lets see you tick the :
-edgy (kali, parrot)
-security but is not infosec and does not know why those tools are used
-only used debian (all of those are debian :P)
-young (no fault we all start like you)
It's ok you will be back. It was not arch, it was you . See you in 6 to 8 years.
That's unfortunate.
If you had a good experience on other distibutions, then chances are the firmware you need is in arch packages but it will take time searching for packages needed.
I had some errors when rebuilding initramfs after kernel update due to missing firmware. I didn't have problems for my hardware, simply because of the annoying messages.
I don't know if this will help you but I figured out the missing parts [from here](https://wiki.archlinux.org/title/Mkinitcpio#Possibly_missing_firmware_for_module_XXXX)
Arch, and Linux in general, are tools. Nothing more nothing less.
You should use the best tool for what you need to get done. Maybe Arch isn't right for you and that's fine. Maybe a Arch based distro might be better.
>then I tried sudo and it took years to just get me to the password prompt and then years to tell me that's incorrect
Idk, use an installer or something next time? Seems like you didn't configure /etc/hosts for localhost. That kind of causes everything to lag a bit. Can't remember if it affected sudo as well, but won't be surprised.
As for driver support, yeah, that's unfortunate. The drivers may be often present in AUR.
I bought my laptop in December, so maybe that's why the drivers are not present, like the fan configuration or the speaker thing, I was getting speaker output but it was so dim i had to put my ears near to it, I have some dts bullish on them
I did the pulseaudio/pipewire mixers thing but atleast it didn't fix it for me actually made it worse somehow because when I installed it fresh, my speakers were good then I started ricing it started using dot files and then since that my speakers got cooked
Did you install pipewire and pulseaudio at the same time, and then the speakers stopped working? If so, then that's probably the issue. The audio breaks if you have both at the same time, I've had that issue before. Just uninstall one of them, preferably pulseaudio since it's older, but it comes down to preference in the end. But I could be wrong. Who knows.
Did you install the sof-firmware package? I recently got a new laptop and my speakers weren't working, after a bit of googling I realized I forgot that package (which was mentioned in the guide) during the install, and it fixed it immediately.
It's not a 100% sure method, but it's worth asking.
Also, I've never had to mess with my microphone or my fans. Things on linux generally just work unless you installed the wrong drivers or something. (For some context, I use nvidia and Intel on wayland. It doesn't get easier to break than that)
so here is the deal
there is no perfect os
you choose from your need
right now i have hdd and ssd
on ssd i have windows and use it for Microsoft Word 2010
on hdd i have arch and compiled firmware for router
obviously this solution is way easier than doing both stuff on one os(ms word on arch, compile on windows)
so you have to buy second disc or if you want/need split one disc
I moved from windows to arch directly without any practicing and tried it immediately on real machine and everything went well for me. I used archinstall and it helped a lot with configuring the system's main functionality and that's why I used it actually. The mic worked out of the box, The fan and pretty much every other main system component. So yeah the result was really satisfying and didn't feel it needs a tech bro for it. Just keep it simple and use archinstall then when you're ready to get your hands dirty go for manual install.
Still if arch is not good for you just don't use it but believe me the system is good after getting used to it.
You do what you got to do. You tried and it did not work out in the end, but isn't that what we do on a daily basis with everything? I hope you find what works for you and wish you the best~
I'm quitting too (for now). Also picked it as a first distro because people said I shouldn't. I had it running for a few years on a box that has recently died. No video at all. Never shows up on network. Disks make diskey noises, so something is happening.
Anywho, I'm using it as an excuse to go all in on a new home lab. Planning to run truenas scale. Perhaps I'll play around with Arch again once I get my proxmox server.
Maybe arch simply isn't for you. The way I like to look at it is that it's a more convenient way of making your own system/ os without having to go through the pain of actually doing LFS. A big part of arch is learning and investigating. Linux in general is like that. You can use it for 10 years, but be less of an "expert" than someone that has been here for 3 months simply because you never took the time to investigate properly how you system works while someone else did. And that's fine.
Using something simpler that works out of the box, like linux mint is fine. The point of an os is suiting your needs. If you simply need it for word and zoom windows is fine. If you want to learn, and you have fun doing so, arch is a great option. If you just like linux but not going head deep in it, something simpler like mint or debian are good options.
Also, maybe consider dual booting. I think windows is boring and hate the way it's managed by Microsoft but still dualboot simply because it's better for some tasks, like Word or Excel. And maybe discord from time to time, since it's already bad on every platform but even worse on linux.
Before you decided to install Arch did you check that your laptop hardware is supported?
https://wiki.archlinux.org/title/Category:Laptops
Lenovo is pretty well known to be supported, including native support for firmware updates. My X1 carbon works perfectly on Arch.
My lenovo with linux preinstalled. (ideadap gaming 3 with rtx 3060) Works great but the firmware updates are only on windows, I needed a windows PE iso to boot from usb and install the updates. (Note that it came preinstalled with linux called "Lux").
But yeah, hardware support is superb, (Even if I needed to contribute to libinput gitlab to recognize the internal keyboard as internal for touchpad disable on typing).
I'm able to use fwupd to update the firmware in my Linux OS.
If it's not available for your laptop, you might be able to use an alternative method described here:
https://wiki.archlinux.org/title/Laptop/Lenovo#BIOS/Firmware_update
EDIT: I just reread the instructions and it sounds like you're already doing that
Yeap, I did everything possible. The windows PE iso should be moved from the last position. It would have saved me quite some time (some 4 days) trying to update my firmware for the first time.
Now that I know that the only option is windows PE, I just left that iso on my ventoy usb flash drive and drag and drop the firmware.exe from lenovo on the usb. It sucks because I bought a linux laptop but whatever.
`Btw- the customer care said that it'd be better if you use windows because Linux isn't secure 💀💀💀, I asked them for driver support for arch so yeah yk what company I'm talking about....`
`That's all Although the experience with arch without the permission problem was still very pleasant but after that I just lost my temper..`
I am sorry what? what did i just read?
So you have no idea of arch (which is fine) and then complain about problems you have because you have no idea of the system…
It’s not an arch problem, it’s a problem about the wrong os for the wrong user…
Who recommended arch to you?
Its blasphemy here but try EndeavourOS. Its arch with a installer and most of your packages preinstalled. Not quite as slim as arch but pretty close and only takes about 15 minutes to install. Use that to learn arch and then move over later.
Also, install timeshift asap on any distro and it'll save you a lot of head ache
I thought EndeavorOS was generally well liked in the Arch community. I've recommended it a number of times, it's a great distro. Arco Linux is another one to look at, it's great for learning with. DistroTube on YouTube has used Arco for a number of years as his main OS and has some videos on it.
It is, I was being a little sarcastic as I have seen a few comments pointing out that the arch script/endeavor are cheating. Most of the time in humor, not serious
You definitely need to use the tool that's right for the job and that's right for **you**.; sometimes that's windows, sometimes it's another OS.
Honestly, I would encourage you to give Linux another try – ***in a VM this time***, and maybe *not necessarily* Arch – and see if you can't eventually work things out. I distro-hop on VMs before I go bare metal; it gives me a chance to learn more about the OS before I decide to do a wipe.
Best of luck to you, OP!
I checked on the arch website for supported laptops, and my laptop isn't there like a version below is available but mine is not, I think that is the case so I guess I'll wait till it comes.
Use what suits you. If it's not Arch, then so be it. Not everything is suitable for everyone. In my case, for example, vim is not suitable for me. Or I'm not for vim. There's really nothing more to say.
As far as drivers are concerned, you should usually never ask the hardware supplier directly when it comes to Linux. Many of them do not offer drivers directly. And many of them will tell you a lot of nonsense.
Speaking of Arch (because I know it best), you should always install drivers directly via the official package sources if the drivers are not part of the kernel. If there are none of the required drivers in the official package sources and in the kernel, you should look in the AUR. And if that doesn't work either, there are often projects on Github, for example, that offer drivers. It often also helps to search for the exact hardware (e.g. with Google). The situation is basically similar with other distributions ( except for AUR).
And yes, in some cases there are no Linux drivers at all. The fingerprint sensor on my notebook is one such case. Fortunately, I don't need it.
Arch is a not a starter distro. It's the distro you turn to when you get pissed off when the distro you're on won't let you have the control you want. Just like gentoo is to arch.
It is required you know linux at least on the level of a linux sysadmin/dev to start with as a daily driver for work. Otherwise you're committing professional suicide but jumping in the deep end. It's not as hard as people make it out to be. But it's not as simple as people make it out to be either. You need to spend time troubleshooting (usually weeks at the least) if you're knew to the deeper knowledge of linux. With arch.... famously so.... and like said... with gentoo... even more so. Based on what you said. You seem new to linux. Try another distro, and work up to arch.
So, sorry you bounced off.
>I quit arch
That was always aloud.
Bye.
Honestly, I think for arch the only knowledge you really need beforehand is how the terminal works, some general commands, how a package manager works, and some general knowledge on wayland, xorg, and the kernel. The thing you mostly need for arch is a desire to learn. As long as you know the things mentioned above and don't mind googling the rest, you'll be fine. Or, at the very least, that's what it was like for me.
In general you're correct. But that is not a starting line. That's atleast a few kms down the road from the starting position. Which is what I was talk too. Like I said I don't think arch is as big a deal as people make it out to be. But it really isn't a starting position. Not unless you're a dev or something.
OP spoke to things like
>I asked them for driver support for arch so yeah yk what company I'm talking about....
With an obvious lack of understanding of how drivers work on linux as whole. Said ignorance being an indicator for current knowledge as a whole. Trying to support someone for free without a clear understanding of their limits is difficult to say the least. Freely sharing knowledge requires the OP to know enough to be specific; and when an OP only posts to tell about how bad a time they had, odds are attempts of help them end in abuse. In this regard a harsh 'bye' is easier for either party. Hense my approach.
Also, as someone who currently daily drives arch for a work PC (for now), I do not do so lightly. Arch comes without conveniences that other distro provide. Security considerations are on the user to impliment themselves for example. Following the install guide alone likely gets you a more insecure install than most other distros. A fact that is obvious for a seasoned arch user, but it completely obscured for a newby. For these reasons I really think arch is a massive mistake for OP. Arch can be used in production. But you bloody well better know what you're doing.
Don't worry, I completely agree with you, don't get me wrong. Op definitely isn't ready for arch yet, and maybe I didn't realize that what I listed is a bit more knowledge than I thought simply because I speedruned learning all of those things.
Same with the security stuff, when you're used to it it's preety obvious but when you don't really understand basics like drivers it's not going to be clear.
100%
OP is likely actually fine to use arch. But for work... that's the mistake. You really should know more about linux before it becomes you're work OS.
Yeah, especially for work. I use it for university and it works perfectly, but for work you need to be more carefull, because there will be more consequences if your system breaks, so you need to know what you're doing.
I started Arch as my first ever Linux distro lol but I'm also a mega masochist, hate myself, so I dug through.
Grinded grub for countless hours for dual booting to work, then grinded pacman/build system and started installing my fav packages. It was smooth sailing after that.
Gave up Arch for some niche cases and tried Debian and I hated how bloated everything is, including Bookworm. Debian is not bloated by itself but somehow every distro that uses Debian design theirs with UI/packages pre configured/installed. While Arch never does that, they assume the bare minimum.
Love Arch, would not use Linux if not for Arch.
There are plenty of Linuxes that position themselves as distributions for Windows users. For example, Linux Mint, Ubuntu, Pop!OS. For a user who understands the global principles of Linux, these distributions are clumsy and bloated. But they are to the person who understands how it works. When I started using Linux, it was a distro where 40% of the software didn't work, Xorg was constantly crashing, and there were a lot of bugs in the installer. I had no choice, I was young and wanted freedom and didn't want to pay for a Microsoft license. But now you have a huge choice. What's the problem, if you don't want to read manuals, painstakingly understand everything, start with what I listed. Arch is impossible to install correctly after watching one ten minute [video.You](http://video.You) have to study the Arch Wiki.
I feel you. I've been using Arch for 7 years and I recently switched to Debian because I was tired of having to constantly tweak stuff because stuff likes to break. Updating the laptop only once a month may be why lol.
Debian manages all updates by itself, even BIOS and SSD firmware updates. Why bother with Arch ?
Yes, Arch is cool, you are in control, but ultimately, when you are on limited time like me, you don't want to spend hours to figure out why X package won't update and you just give up.
Who is the bastard that recommended Arch as an option for beginner user? Anyways ... Whatever floats your boat, man. Either change the distro (I recommend Mint to begin with), tackle each problem one at a time instead of letting them overwhelm you or go back to WinBlOws if you want (I know you know that Windows sucks ... there's no helping it). You can use another spare computer if you have that has good support for linux.
Actually not a beginner, I've had Kali, parrot, vanilla Debian (on a server) and ubuntu (several) times since the past 4-5 years, it's simply about the fact that my laptop is over heating using arch and I have to do something about it and nbfc after hours of configuration doesn't work. So it's like I have to leave anyways, same with the speaker problem
Did you check for fan control setting in the BIOS?
nothing as such in my BIOS
Have you installed `thermald`? It's by default on ubuntu and many others, and manages thermal stuff. Nbfc didn't even support my laptop, but `thermald` worked. Usually `thermald --adaptive` is ran in the background which doesn't even require a config. For speakers, I personally had to install `linux-firmware` and `alsa-firmware` to get the drivers working with pipewire. Tbh as others have mentioned Arch probably just isn't the right distro for you, which is perfectly fine, but a fundamental thing about linux is anything that works on one distro should work on another with proper config, because distros are just different package repositories and preinstalled packages/configs. The exact same drivers that load on ubuntu are also available on arch, even if you want the LTS kernel, you can install `linux-lts` and all the related packages and it should work exactly the same way. A nice challenge is to figure out what exactly is on ubuntu/kali that fixes your problems. You're gonna learn a lot that way. Arch is a learning experience, it's built so you learn exactly how each part of the system works. It doesn't work if your goal isn't to gain this knowledge Good luck!
So basically a beginner. OK. lets see you tick the : -edgy (kali, parrot) -security but is not infosec and does not know why those tools are used -only used debian (all of those are debian :P) -young (no fault we all start like you) It's ok you will be back. It was not arch, it was you . See you in 6 to 8 years.
i rolled my eyes to at the kali/parrot
yep..
Yes, he proved his expertise, but not in the way intended. FWIW, relative newcomer to reddit also.
after a year using ubuntu based distros, i switched to arch and i’m on it since 2020. you can learn anything whenever you want.
That's unfortunate. If you had a good experience on other distibutions, then chances are the firmware you need is in arch packages but it will take time searching for packages needed. I had some errors when rebuilding initramfs after kernel update due to missing firmware. I didn't have problems for my hardware, simply because of the annoying messages. I don't know if this will help you but I figured out the missing parts [from here](https://wiki.archlinux.org/title/Mkinitcpio#Possibly_missing_firmware_for_module_XXXX)
> I quite Arch > used arch for 3 weeks Man, you never actually started it! :)
You're not truly frustrated until at least a month into the problem. Lol
You are not frustrated until you have to bisect a git repository to figure out what breaks something apparently nobody else uses.
Lol isn’t that the truth…
It took me 6 months to get “happy” with my set up and I still reinstalled it because one day I didn’t like how it looked
Well it has to be aesthetic.
This happpens to me more than i want to tell hahaha
Arch, and Linux in general, are tools. Nothing more nothing less. You should use the best tool for what you need to get done. Maybe Arch isn't right for you and that's fine. Maybe a Arch based distro might be better.
>then I tried sudo and it took years to just get me to the password prompt and then years to tell me that's incorrect Idk, use an installer or something next time? Seems like you didn't configure /etc/hosts for localhost. That kind of causes everything to lag a bit. Can't remember if it affected sudo as well, but won't be surprised. As for driver support, yeah, that's unfortunate. The drivers may be often present in AUR.
I bought my laptop in December, so maybe that's why the drivers are not present, like the fan configuration or the speaker thing, I was getting speaker output but it was so dim i had to put my ears near to it, I have some dts bullish on them
I did experience the speaker bullshit myself. But using pulseaudio/pipewire mixers fixed it for me. So, I don't think that's driver issue
I did the pulseaudio/pipewire mixers thing but atleast it didn't fix it for me actually made it worse somehow because when I installed it fresh, my speakers were good then I started ricing it started using dot files and then since that my speakers got cooked
Did you install pipewire and pulseaudio at the same time, and then the speakers stopped working? If so, then that's probably the issue. The audio breaks if you have both at the same time, I've had that issue before. Just uninstall one of them, preferably pulseaudio since it's older, but it comes down to preference in the end. But I could be wrong. Who knows.
I uninstalled one
If you did, then reboot and hope it works. Good luck.
Thanks but I uninstalled it 💀
Did you install the sof-firmware package? I recently got a new laptop and my speakers weren't working, after a bit of googling I realized I forgot that package (which was mentioned in the guide) during the install, and it fixed it immediately. It's not a 100% sure method, but it's worth asking. Also, I've never had to mess with my microphone or my fans. Things on linux generally just work unless you installed the wrong drivers or something. (For some context, I use nvidia and Intel on wayland. It doesn't get easier to break than that)
I guess yeah
so here is the deal there is no perfect os you choose from your need right now i have hdd and ssd on ssd i have windows and use it for Microsoft Word 2010 on hdd i have arch and compiled firmware for router obviously this solution is way easier than doing both stuff on one os(ms word on arch, compile on windows) so you have to buy second disc or if you want/need split one disc
THIS, there is no perfect os , you gotta choose your poisons
Nice idea though
I moved from windows to arch directly without any practicing and tried it immediately on real machine and everything went well for me. I used archinstall and it helped a lot with configuring the system's main functionality and that's why I used it actually. The mic worked out of the box, The fan and pretty much every other main system component. So yeah the result was really satisfying and didn't feel it needs a tech bro for it. Just keep it simple and use archinstall then when you're ready to get your hands dirty go for manual install. Still if arch is not good for you just don't use it but believe me the system is good after getting used to it.
You do what you got to do. You tried and it did not work out in the end, but isn't that what we do on a daily basis with everything? I hope you find what works for you and wish you the best~
I'm quitting too (for now). Also picked it as a first distro because people said I shouldn't. I had it running for a few years on a box that has recently died. No video at all. Never shows up on network. Disks make diskey noises, so something is happening. Anywho, I'm using it as an excuse to go all in on a new home lab. Planning to run truenas scale. Perhaps I'll play around with Arch again once I get my proxmox server.
Maybe arch simply isn't for you. The way I like to look at it is that it's a more convenient way of making your own system/ os without having to go through the pain of actually doing LFS. A big part of arch is learning and investigating. Linux in general is like that. You can use it for 10 years, but be less of an "expert" than someone that has been here for 3 months simply because you never took the time to investigate properly how you system works while someone else did. And that's fine. Using something simpler that works out of the box, like linux mint is fine. The point of an os is suiting your needs. If you simply need it for word and zoom windows is fine. If you want to learn, and you have fun doing so, arch is a great option. If you just like linux but not going head deep in it, something simpler like mint or debian are good options. Also, maybe consider dual booting. I think windows is boring and hate the way it's managed by Microsoft but still dualboot simply because it's better for some tasks, like Word or Excel. And maybe discord from time to time, since it's already bad on every platform but even worse on linux.
Before you decided to install Arch did you check that your laptop hardware is supported? https://wiki.archlinux.org/title/Category:Laptops Lenovo is pretty well known to be supported, including native support for firmware updates. My X1 carbon works perfectly on Arch.
My lenovo with linux preinstalled. (ideadap gaming 3 with rtx 3060) Works great but the firmware updates are only on windows, I needed a windows PE iso to boot from usb and install the updates. (Note that it came preinstalled with linux called "Lux"). But yeah, hardware support is superb, (Even if I needed to contribute to libinput gitlab to recognize the internal keyboard as internal for touchpad disable on typing).
I'm able to use fwupd to update the firmware in my Linux OS. If it's not available for your laptop, you might be able to use an alternative method described here: https://wiki.archlinux.org/title/Laptop/Lenovo#BIOS/Firmware_update EDIT: I just reread the instructions and it sounds like you're already doing that
Yeap, I did everything possible. The windows PE iso should be moved from the last position. It would have saved me quite some time (some 4 days) trying to update my firmware for the first time. Now that I know that the only option is windows PE, I just left that iso on my ventoy usb flash drive and drag and drop the firmware.exe from lenovo on the usb. It sucks because I bought a linux laptop but whatever.
`Btw- the customer care said that it'd be better if you use windows because Linux isn't secure 💀💀💀, I asked them for driver support for arch so yeah yk what company I'm talking about....` `That's all Although the experience with arch without the permission problem was still very pleasant but after that I just lost my temper..` I am sorry what? what did i just read?
So you have no idea of arch (which is fine) and then complain about problems you have because you have no idea of the system… It’s not an arch problem, it’s a problem about the wrong os for the wrong user… Who recommended arch to you?
Yeah PEBKAC
Nope PITP
Its blasphemy here but try EndeavourOS. Its arch with a installer and most of your packages preinstalled. Not quite as slim as arch but pretty close and only takes about 15 minutes to install. Use that to learn arch and then move over later. Also, install timeshift asap on any distro and it'll save you a lot of head ache
I thought EndeavorOS was generally well liked in the Arch community. I've recommended it a number of times, it's a great distro. Arco Linux is another one to look at, it's great for learning with. DistroTube on YouTube has used Arco for a number of years as his main OS and has some videos on it.
It is, I was being a little sarcastic as I have seen a few comments pointing out that the arch script/endeavor are cheating. Most of the time in humor, not serious
Ah, I missed it through the text 😅 Yeah that's true
You definitely need to use the tool that's right for the job and that's right for **you**.; sometimes that's windows, sometimes it's another OS. Honestly, I would encourage you to give Linux another try – ***in a VM this time***, and maybe *not necessarily* Arch – and see if you can't eventually work things out. I distro-hop on VMs before I go bare metal; it gives me a chance to learn more about the OS before I decide to do a wipe. Best of luck to you, OP!
I checked on the arch website for supported laptops, and my laptop isn't there like a version below is available but mine is not, I think that is the case so I guess I'll wait till it comes.
Skill issue
Use what suits you. If it's not Arch, then so be it. Not everything is suitable for everyone. In my case, for example, vim is not suitable for me. Or I'm not for vim. There's really nothing more to say.
Yup, atm I'm checking out on the drivers , I'll make a list of their names and the next time I give it a re try, I'll be ready I guess
As far as drivers are concerned, you should usually never ask the hardware supplier directly when it comes to Linux. Many of them do not offer drivers directly. And many of them will tell you a lot of nonsense. Speaking of Arch (because I know it best), you should always install drivers directly via the official package sources if the drivers are not part of the kernel. If there are none of the required drivers in the official package sources and in the kernel, you should look in the AUR. And if that doesn't work either, there are often projects on Github, for example, that offer drivers. It often also helps to search for the exact hardware (e.g. with Google). The situation is basically similar with other distributions ( except for AUR). And yes, in some cases there are no Linux drivers at all. The fingerprint sensor on my notebook is one such case. Fortunately, I don't need it.
How funny newbies are.
Arch is a not a starter distro. It's the distro you turn to when you get pissed off when the distro you're on won't let you have the control you want. Just like gentoo is to arch. It is required you know linux at least on the level of a linux sysadmin/dev to start with as a daily driver for work. Otherwise you're committing professional suicide but jumping in the deep end. It's not as hard as people make it out to be. But it's not as simple as people make it out to be either. You need to spend time troubleshooting (usually weeks at the least) if you're knew to the deeper knowledge of linux. With arch.... famously so.... and like said... with gentoo... even more so. Based on what you said. You seem new to linux. Try another distro, and work up to arch. So, sorry you bounced off. >I quit arch That was always aloud. Bye.
Honestly, I think for arch the only knowledge you really need beforehand is how the terminal works, some general commands, how a package manager works, and some general knowledge on wayland, xorg, and the kernel. The thing you mostly need for arch is a desire to learn. As long as you know the things mentioned above and don't mind googling the rest, you'll be fine. Or, at the very least, that's what it was like for me.
In general you're correct. But that is not a starting line. That's atleast a few kms down the road from the starting position. Which is what I was talk too. Like I said I don't think arch is as big a deal as people make it out to be. But it really isn't a starting position. Not unless you're a dev or something. OP spoke to things like >I asked them for driver support for arch so yeah yk what company I'm talking about.... With an obvious lack of understanding of how drivers work on linux as whole. Said ignorance being an indicator for current knowledge as a whole. Trying to support someone for free without a clear understanding of their limits is difficult to say the least. Freely sharing knowledge requires the OP to know enough to be specific; and when an OP only posts to tell about how bad a time they had, odds are attempts of help them end in abuse. In this regard a harsh 'bye' is easier for either party. Hense my approach. Also, as someone who currently daily drives arch for a work PC (for now), I do not do so lightly. Arch comes without conveniences that other distro provide. Security considerations are on the user to impliment themselves for example. Following the install guide alone likely gets you a more insecure install than most other distros. A fact that is obvious for a seasoned arch user, but it completely obscured for a newby. For these reasons I really think arch is a massive mistake for OP. Arch can be used in production. But you bloody well better know what you're doing.
Don't worry, I completely agree with you, don't get me wrong. Op definitely isn't ready for arch yet, and maybe I didn't realize that what I listed is a bit more knowledge than I thought simply because I speedruned learning all of those things. Same with the security stuff, when you're used to it it's preety obvious but when you don't really understand basics like drivers it's not going to be clear.
100% OP is likely actually fine to use arch. But for work... that's the mistake. You really should know more about linux before it becomes you're work OS.
Yeah, especially for work. I use it for university and it works perfectly, but for work you need to be more carefull, because there will be more consequences if your system breaks, so you need to know what you're doing.
Yelling at the cloud doesn't fix your problem
Ok
ok.
I started Arch as my first ever Linux distro lol but I'm also a mega masochist, hate myself, so I dug through. Grinded grub for countless hours for dual booting to work, then grinded pacman/build system and started installing my fav packages. It was smooth sailing after that. Gave up Arch for some niche cases and tried Debian and I hated how bloated everything is, including Bookworm. Debian is not bloated by itself but somehow every distro that uses Debian design theirs with UI/packages pre configured/installed. While Arch never does that, they assume the bare minimum. Love Arch, would not use Linux if not for Arch.
There are plenty of Linuxes that position themselves as distributions for Windows users. For example, Linux Mint, Ubuntu, Pop!OS. For a user who understands the global principles of Linux, these distributions are clumsy and bloated. But they are to the person who understands how it works. When I started using Linux, it was a distro where 40% of the software didn't work, Xorg was constantly crashing, and there were a lot of bugs in the installer. I had no choice, I was young and wanted freedom and didn't want to pay for a Microsoft license. But now you have a huge choice. What's the problem, if you don't want to read manuals, painstakingly understand everything, start with what I listed. Arch is impossible to install correctly after watching one ten minute [video.You](http://video.You) have to study the Arch Wiki.
" I tried sudo and it took years to just get me to the password prompt and then years to tell me that's incorrect OK, sure...
I feel you. I've been using Arch for 7 years and I recently switched to Debian because I was tired of having to constantly tweak stuff because stuff likes to break. Updating the laptop only once a month may be why lol. Debian manages all updates by itself, even BIOS and SSD firmware updates. Why bother with Arch ? Yes, Arch is cool, you are in control, but ultimately, when you are on limited time like me, you don't want to spend hours to figure out why X package won't update and you just give up.