Ok... I managed to get wifi working ... The steps I took after booting from the initial image: # rkill unblock wlan # copy /etc/netctl/examples/wireless-wpa /etc/netctl/mywifi <edit /etc/netctl/mywifi and replace MyNetwork with the correct networkname and fill in the correct WirelessKey # cd /etc/netctl # netctl start mywifi # netctl enable mywifi # ping 8.8.8.8 Now I can continue with the installation :0 Thanks all for the 'nudges' in the right direction Leo On Thu, Dec 5, 2019 at 10:59 PM David C. Rankin < drankinatty@xxxxxxxxxxxxxxxxxx> wrote: > On 12/05/2019 01:50 PM, L. Rose wrote: > > did you check "ip l" when booting the arch live image, to see if the > interface > > is really not detected? Did you try unblocking it with rfkill? Maybe > there is > > a hardware switch on your device, or a key combination with fn + f8 or > similar? > > I would second this. Many newer laptops have soft-buttons for > wifi/sound/etc.. > that traditionally would just save states between boots. I have 2 SSDs in > my > laptop, one with the original W10, the other with Arch. I've noticed the > soft-buttons are configured differently depending on whether I boot windows > (once a month for updates) or a normal boot of Arch. (behaves the same with > openSUSE as well) I wouldn't be surprised if the wifi soft-button defaults > to > off. I have a light within 4 independent buttons that show the state of > wifi, > sound, etc... Double-check yours when you boot the Arch installer. > > With the arch installer, if the wifi chip is enable, it should be picked up > and enabled automatically. As others have said, save the output of > > lspci -v > > (write it to a usb drive or something) and post the output just to confirm > that there isn't some left-field chipset used (doubt it, but that would > confirm) > > If you have a RJ45 connection for a wired connection, that's always an > option. > > -- > David C. Rankin, J.D.,P.E. >
