I have downloaded a linux driver for a tp-link wireless adapter. It is in the form of a compressed zip folder. What is the best method to install when it is in this form and not the typical rpm package. Thanks for any help I can get.
USB-Wireless Lan?
Open an Terminal / Konsole and post the Output of:
lsusb
Yes AC 1300 Wireless Dual Band USB Adapter
**linux-fxo6:~ #** lsusb
Bus 005 Device 002: ID 2357:010d
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 002: ID 0686:3006 Minolta Co., Ltd PagePro 1250W
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 090c:b370 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Cor
p.) Silicon Motion SM370 Camera
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 002: ID 1267:0214 Logic3 / SpectraVideo plc
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Adapter is not recognized so it is not reported here. I have run this command with it plugged in and not plugged in. No difference.
Bus 005 Device 002: ID 2357:010d
This is your TP-Link.
Maybe Axel can say more, if it is in the rtl8812au Package.
I thought it would be identified by Company name. Sorry for wrong information.
Mostly yes, but in Linux, you need the ID to see, which Chip is working, so this is an Realtek-Chip…
And this might be the Driver, but Axel can say more.
https://build.opensuse.org/package/show/home:Akoellh:Kernelmodules/rtl8812AU_8821AU
The id (the numbers) are read from the device. The names can then be found in a list. That list is somewhere on your system and it is as up to date as possible. But it can always happen that an id is not (yet) in the list. A future update of your system could add that entry though. The list is only to make human understanding easier.
Am Wed, 28 Jun 2017 17:56:01 GMT
schrieb Sauerland <Sauerland@no-mx.forums.microfocus.com>:
> Mostly yes, but in Linux, you need the ID to see, which Chip is working,
> so this is an Realtek-Chip…
>
> And this might be the Driver, but Axel can say more.
> http://tinyurl.com/yc7purce
>
>
Well, at least the ID 2357:101d seems to be covered by that driver.
modinfo 8812au | grep 101d
alias: usb:v2357p0101ddcdscdpiciscipin
If/how well that driver works, no idea, I don’t have any matching hardware, I
just packaged stuff up, but certainly worth a shot.
AK
Never attribute to malice that which can be adequately explained by stupidity.
(R.J. Hanlon)
Am Wed, 28 Jun 2017 19:39:32 GMT
schrieb AK <Akoellh@no-mx.forums.microfocus.com>:
> Am Wed, 28 Jun 2017 17:56:01 GMT
> schrieb Sauerland <Sauerland@no-mx.forums.microfocus.com>:
>
> > Mostly yes, but in Linux, you need the ID to see, which Chip is working,
> > so this is an Realtek-Chip…
> >
> > And this might be the Driver, but Axel can say more.
> > http://tinyurl.com/yc7purce
> >
> >
>
> Well, at least the ID 2357:101d seems to be covered by that driver.
>
> modinfo 8812au | grep 101d
> alias: usb:v2357p0101ddcdscdpiciscipin
>
> If/how well that driver works, no idea, I don’t have any matching hardware, I
> just packaged stuff up, but certainly worth a shot.
>
> AK
Addendum:
I just had a look to the respective github repo I pulled the sources from and
it has been a little more active the last few weeks/months. So I will update
the package and push it to OBS ASAP. So maybe waiting for a few hours is a good
idea.
If everything works as expected, the new version to be published should contain
“20170613” instead of some date from 2016.
AK
–
Never attribute to malice that which can be adequately explained by stupidity.
(R.J. Hanlon)
>
> If everything works as expected, the new version to be published should
> contain “20170613” instead of some date from 2016.
OBS is in a “good mood” today -> done.
AK
P.S.: Amongst some other changes like bug fixes and new device IDs the
module has also been renamed to "rtl8812au.
/sbin/modinfo rtl8812au | grep 101d
alias: usb:v2357p0101ddcdscdpiciscipin
–
Never attribute to malice that which can be adequately explained by stupidity.
(R.J. Hanlon)
I am using my iphone as a router (4g lte) to connect a windows 10 laptop, and my Opensuse Leap desktop. With Windows 10 it is working flawlessly. That is also my hopes for my Opensuse desktop. I think once I get my new adapter set up I stand a good chance of getting good performance with this Opensuse system. I hope so because I have invested some time with Opensuse, although I still feel like a beginner. I am hoping that someone can help me get the driver installed without messing anything up. LOL Thanks for your help.
Can you give me explicit instructions on how to install the driver from AK’s compilation?
Do you have Internet with this openSUSE System , yes or no.
Yes. I can connect with NetworkManager, although sometimes the connection is flakey.
Ok.
As root (su not sudo):
zypper ar -f http://download.opensuse.org/repositories/home:/Akoellh:/Kernelmodules/openSUSE_Leap_42.2/ TP-Link
zypper in rtl8812AU_8821AU-kmp-default
modprobe rtl8812au
systemctl restart network.service
After that you should be able to get Internet with that Stick. Or reboot your System.
BUT
The above Repo is only for the Kernel shipped with openSUSE Leap 42.2.
After updateing the System you will get another Kernel and the above rpm will not work anymore.
So you have to enable another Repo to get the updated rpm:
zypper ar -f http://download.opensuse.org/repositories/home:/Akoellh:/Kernelmodules/openSUSE_Leap_42.2_Update/ TP-Link-Update
Now you will get with every Kernel Update a new (TP-Link) Kernel-Module Update.
Much thanks to you Sauerland. This would have been difficult for me without your help. Stick is working and is much better performing than my RTL8187 stick. No doubt about that. But here is the catch. This stick is behaving with Wicked exactly as my RTL8187. I cannot get it to run on Wicked. This has me sooooo puzzled. So I will take this information back to the Wireless forum. Do you have any ideas why? Again thanks.
Thank Axel for building…
back to topic.
Why will you configure your Wlan with Wicked?
Networkmanager is easier to configure.
Yes, much thanks to Axel. From what I can tell at this point it is working flawlessly. I would highly recommend this adapter to anyone who wants great performing wireless.
I will no longer worry about Wicked. I wanted to see if it might give my former adapter RTL8187 better performance, but I think that was an ill-found hope. That adapter was simply out of date.