You are not logged in.
Pages: 1
Hello everyone,
I decided to finally install Arch Linux and thanks to wiki page I was able to find a driver for my WiFi. Unfortunately, even though I have my files in /dev/sda4 partition. I cannot enter this partition.
I used two commands with some alterations. I mounted the partition:
"mount /dev/sda4 /home"
And when I tried to use command "arch-chroot /home" AI got message
"mount: /home/proc: mount point does not exist.
==> ERROR: failed to setup chroot /home"
I even tried /mnt as a mount point, but I got the same message.
Also, that partition was used as a /home partition so I thought mounting it would do the work, but unfortunately not.
Is there any way to install that driver?
btw I have no idea how to install that driver so if anyone would be kind to tell how do I do it I would be grateful.
I looked at the manual but firstly, in wireless network configuration page there was no mentioning on how to ACTUALLY install the drivers but rather which one to choose, and secondly, it didn't even have my exact WiFi driver (realtek rtl8821ae).
I hope that we can resolve that issue together.
Thank you in advance
Offline
What are you trying to do with this command?
arch-chroot /homeEdit:
Also why are you trying to build a driver for rtl8821ae the linux kernel on the install media contains support for it using the rtl8821ae module.
Last edited by loqs (2019-08-18 22:58:16)
Offline
What files do you have on /dev/sda4? Why are you mounting it on /home? Why are you trying to chroot into it?
Given what you've posted, there seems to be confusion about what arch-chroot does, and about chroots in general. arch-chroot is only used to install packages when setting up Arch from the live install medium. You cannot use it to install packages on the system that you are running. If it is not clear why, then please take some time to read about what a chroot actually is and understand how the installation process uses them.
I'm guessing that the file is the driver that you've found online somewhere. The kernel already includes the rtl8821ae module so there should be no reason for you to have to install it yourself. If you are unable to connect to wi-fi, I suspect that it is due to a configuration error.
Explain in detail what you have done, what you expected to happen, and what actually happened (or didn't happen). Post actual commands and error messages and someone may be able to help you.
modnote: moving to nc
My Arch Linux Stuff • Forum Etiquette • Community Ethos - Arch is not for everyone
Offline
What are you trying to do with this command?
arch-chroot /homeEdit:
Also why are you trying to build a driver for rtl8821ae the linux kernel on the install media contains support for it using the rtl8821ae module.
First of all, I tried changing directory to /dev/sda4, the mount point of which I set to /home. I am not sure if that is the correct but I just want to enter this partition as it contains the drivers I copied (in archive).
Secondly, I am trying to build a driver for the kernel, because I cannot get WiFi to work in the live environment. Whenever I try to ping any website I get the message:
"Temporary failure in name resolution"
And when I try open WiFi-menu, no networks are found.
If I do something incorrectly please tell me as I only begin to do stuff in Linux and I don't know much. Not trolling, I will be happy to change what's wrong
EDIT: I will go in full detail in the next post. One sec
EDIT 2: As I retraced my steps I came to a conclusion that I do not need to build any driver and all, so I followed the manual until it was clear to me that my WiFi was either hard or soft blocked, I don't know because I run a command "rfkill unblock wifi" before checking. Anyway, it resolved the issue.
I'm sorry for creating this confusion and thank you for helping me. I greatly appreciate your feedback.
I will surely learn from my mistakes and learn how to change directories too. This thread is closed
Last edited by G01d3n (2019-08-19 00:00:30)
Offline
/dev/sda4 is a partition. The filesystem contained on that partition you mounted to /home.
The mounted filesystem would then be accessible under /home. chroot is not need to access a filesystem.
Building a driver from the live media is not as simple as just obtaining the files for the driver and if unnecessary I would avoid it.
Please work through Wireless_network_configuration#Check_the_driver_status
Posting the commands and their outputs.
Offline
First of all, I tried changing directory to /dev/sda4, the mount point of which I set to /home. I am not sure if that is the correct but I just want to enter this partition as it contains the drivers I copied (in archive).
You can only change directory into a mounted filesystem. Take some time to read up about devices, filesystems and mounting.
Secondly, I am trying to build a driver for the kernel, because I cannot get WiFi to work in the live environment. Whenever I try to ping any website I get the message:
"Temporary failure in name resolution"And when I try open WiFi-menu, no networks are found.
The driver is included in the kernel. Building it will not help. The error is something else.
What is the output of the following command?
lsmod | grep rtlIf you do not see rtl8821ae in the list, try to manually load it with
modprobe rtl8821aeIf that fails, post the error message.
If I do something incorrectly please tell me as I only begin to do stuff in Linux and I don't know much. Not trolling, I will be happy to change what's wrong
Many Arch users were completely new to Linux when they started, even through Arch isn't a beginner-friendly distro (it's aimed at "competent Linux users"). If you really want to install and run it, you will need to go slowly and take the time to read up on different topics that are unfamiliar to you.
My Arch Linux Stuff • Forum Etiquette • Community Ethos - Arch is not for everyone
Offline
In your previous thread you stated that networking worked fine in the live USB, but just failed in your newly installed VM (because you never configured it, presumably). Now in this thread, you seem to be claiming that networking isn't working in the live USB, is this correct?
Most of this is a series of xy problems. You think you need to build something to get your networking to work, and you think to build something you need to chroot into something, and chrooting into that something is failing.
Forget all that. Tell us about the initial problem with actual data: actual commands and output, not your inferences, paraphrasings, or suspicions.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
In your previous thread you stated that networking worked fine in the live USB, but just failed in your newly installed VM (because you never configured it, presumably). Now in this thread, you seem to be claiming that networking isn't working in the live USB, is this correct?
Most of this is a series of xy problems. You think you need to build something to get your networking to work, and you think to build something you need to chroot into something, and chrooting into that something is failing.
Forget all that. Tell us about the initial problem with actual data: actual commands and output, not your inferences, paraphrasings, or suspicions.
As for working just fine in the VM, I could freely install the base packages and couldnt on the real hardware
Offline
Ok, we could speculate that this was due to the VM providing a virtual ethernet link while on real hardware you are using (trying to use) a wireless link. But this is just yet more speculation as you haven't actually told us anything concrete yet.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
The installation media sets up dhcpcd so in the VM you had network connectivity under the installation media but not the installed system as you did not setup dhcpcd.
Offline
Pages: 1