From: PGNet Dev <pgnet.dev@gmail.com>
To: samuel@sieb.net, linux-wireless@vger.kernel.org
Subject: Re: wifi dongle connected to USB/pci card, seen in hardware, but no wl* device created; udev, driver, &/or config?
Date: Sat, 5 Dec 2020 15:47:53 -0800 [thread overview]
Message-ID: <27d25649-2f5a-5818-6b2c-ef134cb3394b@gmail.com> (raw)
In-Reply-To: <79883ce0-9313-10b4-214a-27be35888bee@sieb.net>
On 12/5/20 1:51 PM, Samuel Sieb wrote:
> On 12/5/20 1:25 PM, PGNet Dev wrote:
>> lsusb | grep 008
>> Bus 008 Device 003: ID 0bda:b812 Realtek Semiconductor Corp. RTL88x2bu [AC1200 Techkey]
>
> There are a couple of available options:
> https://github.com/cilynx/rtl88x2bu
> https://github.com/RinCat/RTL88x2BU-Linux-Driver
>
>> existing default udev rules aren't creating a wlan device; I'd expected that they would ...
>
> The device can only be created if there's a driver to create it.
::facepalm::
well, it certainly help if I'd not just googled for ac1200 but ALSO paid attention to the fact I'd installed 88x2*a*u!
> https://github.com/aircrack-ng/rtl8812au
with CORRECT driver
> https://github.com/RinCat/RTL88x2BU-Linux-Driver
dkms-installed, on boot
dmesg | grep wl
[ 22.083177] RTW: rtw_ndev_init(wlan0) if1 mac_addr=44:01:bb:33:c4:1c
[ 22.318059] rtl88x2bu 8-4:1.0 wlp2s0u4: renamed from wlan0
iw dev
phy#0
Interface wlp2s0u4
ifindex 3
wdev 0x1
addr 44:01:bb:33:c4:1c
type managed
txpower 42949572.96 dBm
hwinfo --wlan | egrep "Device:|Modules:|File:"
Device: usb 0xb812 "802.11ac NIC"
Driver Modules: "88x2bu"
Device File: wlp2s0u4
pebkac. again.
thx o/
prev parent reply other threads:[~2020-12-05 23:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-05 21:25 wifi dongle connected to USB/pci card, seen in hardware, but no wl* device created; udev, driver, &/or config? PGNet Dev
2020-12-05 21:51 ` Samuel Sieb
2020-12-05 23:47 ` PGNet Dev [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=27d25649-2f5a-5818-6b2c-ef134cb3394b@gmail.com \
--to=pgnet.dev@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=samuel@sieb.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox