On 18/01/14 13:40, Alexey E. Suslikov wrote:
the source tree as part of the regular 'make' call. But this way I
managed to compile the kernel and install it.
you didn't tell us is your urtwn(4) variant working or not after installing
new kernel. new dmesg wouldn't hurt.
Sorry for the late
On Wed, Jan 22, 2014 at 08:37:53PM +, Bernte wrote:
On 18/01/14 13:40, Alexey E. Suslikov wrote:
the source tree as part of the regular 'make' call. But this way I
managed to compile the kernel and install it.
you didn't tell us is your urtwn(4) variant working or not after installing
Bernte bernte at fams.de writes:
the source tree as part of the regular 'make' call. But this way I
managed to compile the kernel and install it.
you didn't tell us is your urtwn(4) variant working or not after installing
new kernel. new dmesg wouldn't hurt.
On 17/01/14 06:45, Jonathan Gray wrote:
A device attaching as ugen means no driver has claimed it.
Support for your device and many other urtwn devices was added
after 5.4.
Here is an untested patch against 5.4 that should work:
Hi Jonathan,
Thank you very much for the help, this was
Hello,
I was hoping that my TP-Link TL-WN8200ND works in 5.4, but it looks like
it is only detected as an unsupported USB device.
ugen0 at uhub0 port 2 Realtek 802.11n WLAN Adapter rev 2.00/2.00 addr 2
While the documentation from the provider is not verbose about the
chipset used
On Thu, Jan 16, 2014 at 08:09:00PM +, Bernte wrote:
Hello,
I was hoping that my TP-Link TL-WN8200ND works in 5.4, but it looks like
it is only detected as an unsupported USB device.
ugen0 at uhub0 port 2 Realtek 802.11n WLAN Adapter rev 2.00/2.00 addr 2
While the documentation from
6 matches
Mail list logo