You are not logged in.
I'm doing a install of Arch and I need to setup my WLAN.
So the wiki says:
"After finishing the rest of this installation and rebooting, you can connect to the network with wifi-menu interface_name (where interface_name is the interface of your wireless chipset). "
How do I find out the name of my interface?
Last edited by psycho_tea_drinker (2013-07-03 12:36:40)
Offline
ip link
It should be the one starting with "w".
"...one cannot be angry when one looks at a penguin." - John Ruskin
"Life in general is a bit shit, and so too is the internet. And that's all there is." - scepticisle
Offline
Output of ip link gives me 2 bullet points.
1: lo: <LOOPBACK,UP,LOWERUP> ....
2: enpOs3: <BROADCAST,MULTICAST> ...
Am I missing something?
Offline
Well, it is possible it's the enxxx one, but that is normally the ethernet device. If you don't have one of those it'll be that one, otherwise I'd check out this page:
"...one cannot be angry when one looks at a penguin." - John Ruskin
"Life in general is a bit shit, and so too is the internet. And that's all there is." - scepticisle
Offline
Check your chipset (lspci), see if the corresponding kernel module got loaded. Look for dmesg errors. Another way to check device names (from the wiki):
$ ls /sys/class/net
Offline
Check your chipset (lspci), see if the corresponding kernel module got loaded. Look for dmesg errors. Another way to check device names (from the wiki):
$ ls /sys/class/net
How do I check if the kernal module got loaded?
lspci | grep net
> only shows my ethernet controller
lsusb
> does not show it ethier
I forget to mention that it is a USB wifi dongle (Tplink TL-WN722N). And I'm also running within virtualbox - I hope that does not complicate matters?
Offline
hokasch wrote:Check your chipset (lspci), see if the corresponding kernel module got loaded. Look for dmesg errors. Another way to check device names (from the wiki):
$ ls /sys/class/net
How do I check if the kernal module got loaded?
lspci | grep net
> only shows my ethernet controllerlsusb
> does not show it ethierI forget to mention that it is a USB wifi dongle (Tplink TL-WN722N). And I'm also running within virtualbox - I hope that does not complicate matters?
Probably. You'll need to make sure that VB guest can see your USB ports. You'll need the VB wiki pages for that though.
I don't use it, so can't help, sorry.
Last edited by skanky (2013-07-03 13:12:46)
"...one cannot be angry when one looks at a penguin." - John Ruskin
"Life in general is a bit shit, and so too is the internet. And that's all there is." - scepticisle
Offline
I forget to mention that it is a USB wifi dongle (Tplink TL-WN722N). And I'm also running within virtualbox - I hope that does not complicate matters?
It changes matters - please mention such things in the original post.
Is the usb device being handed through into the virtual machine (ctrl+home -> usb devices)? You need it to show up in lsusb, then load the kernel modules if needed. <-- stupidity.. see the reply below.
Last edited by hokasch (2013-07-03 17:39:54)
Offline
Check the Networksection on Virtual box. It creates one virtual NIC by default.
That would be in your case enp0s3.
Last edited by henk (2013-07-03 17:03:49)
Offline
Check the Networksection on Virtual box. It creates one virtual NIC by default.
That would be in your case enp0s3.
Yes of course, sorry I was being stupid. Sorry.
"...one cannot be angry when one looks at a penguin." - John Ruskin
"Life in general is a bit shit, and so too is the internet. And that's all there is." - scepticisle
Offline