You are not logged in.
Hi! I've tried to follow the beginner's guide to install Arch but I always get stuck at the Network configuration part. This time I'm on a laptop, installing Arch in VirtualBox with Windows XP as the host. After searching through the "hardware list" site, Ubuntu's own list and some other it seems the firmware I need for my network card isn't supported, or at least not included on the Arch .iso. I have the actual firmware files, a map with several of them, of course only on is needed but I don't know which one it is - all I know is that when I install Ubuntu or Debian, it asks for the firmware and I plug in my usb-stick with the 13 UCODE files and a moment later the installation continues and I can connect to wireless networks. It's not that simple now, Arch doesn't ask for the firmware in that way and I don't know where to put it so that I can modprobe it. Even if I knew the folder I wouldn't be able to do anything because I don't know how to move the files from my host to the Arch system on VirtualBox. I've read some about shared folders and tried a few commands that seemed appropriate but it didn't work. I'd really like it if someone could help me. I like the Arch way of doing it yourself, and I will do it myself if only I knew what to do, most of time I do know, this time I don't.
The firmware files, one of which is the right one, are named:
iwlwifi-1000-3,
iwlwifi-3945-1,
iwlwifi-3945-2,
iwlwifi-4965-1,
iwlwifi-4965-2,
iwlwifi-5000-1,
iwlwifi-5000-2,
iwlwifi-5150-2,
iwlwifi-6050-4,
iwlwifi-6050-5,
iwlwifi-6000g2b-5,
iwlwifi-6000g2a-5,
iwlwifi-6000-4,
all .ucode.
Offline
You don't need wireless firmware on VirtualBox. Just set it to NAT and you're off. If you're connected to the internet on your host OS, you should be connected to the internet on your guest OS. The new releases load the dhcpcd daemon by default, so just try pinging Google.
Alternatively: https://wiki.archlinux.org/index.php/Be … de#Mirrors
Note: [...] When installing Arch Linux as a guest OS in VirtualBox, this issue has also been addressed by using "Host interface" instead of "NAT" in the machine properties.
I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).
Offline
When you're running inside of a virtual machine, you need to address the hardware of the VM, not of your actual system. VirtualBox uses a wired controller, so that's what you need to use. The Arch kernel should already be setup for it, so you just have to bring up the interface.
Offline
It's true that the virtual machine uses different (emulated) hardware, but like I said, "dhcpcd" runs automatically. So there's no need to bring up any interface.
Cosmosn, if the issues is now clear, please mark the topic as solved (by editing the first post).
I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).
Offline