From: Larry Finger <Larry.Finger@lwfinger.net>
To: poma <pomidorabelisima@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Hans de Goede <hdegoede@redhat.com>
Subject: Re: RTL8189ETV
Date: Mon, 31 Aug 2015 12:51:17 -0500 [thread overview]
Message-ID: <55E49415.7090807@lwfinger.net> (raw)
In-Reply-To: <55E48988.1000803@gmail.com>
On 08/31/2015 12:06 PM, poma wrote:
> On 31.08.2015 18:00, poma wrote:
>>
>> Hi Fi,
>>
>> What is this device, is it supported by
>> https://github.com/orangepi-xunlong/linux-sunxi/tree/orangepi-3.4/drivers/net/wireless/rtl8189es
>>
>> $ modinfo rtl8189es
>> modinfo: ERROR: Module rtl8189es not found.
>>
>
> or is it supported by
> https://github.com/orangepi-xunlong/linux-sunxi/tree/orangepi-3.4/drivers/net/wireless/rtl8188eu
> https://github.com/lwfinger/rtl8188eu
> as RTL8188ETV is
>
> $ modinfo rtl8188eu
> modinfo: ERROR: Module rtl8188eu not found.
>
>
> However RTL8188ETV is USB 2.0 device,
> eeeeeeeeeeeeeeeeeee not again!
That last comment does not help.
If rtl8188eu is not available, that is the fault of your distro, not anything
that driver maintainers can help. That driver is in the staging directory, and
some distros do not include any of those drivers in their kernels.
eeeeeeeeeeeeeeeeeee not again! Someone posts about a USB device not found, and
they refuse/fail to provide the USB ID. Why, I do not know when the lsusb
command provides this info so easily.
Larry
next prev parent reply other threads:[~2015-08-31 17:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 16:00 RTL8189ETV poma
2015-08-31 17:06 ` RTL8189ETV poma
2015-08-31 17:51 ` Larry Finger [this message]
2015-08-31 20:31 ` RTL8189ETV poma
2015-08-31 21:25 ` RTL8189ETV Larry Finger
2015-09-01 11:27 ` RTL8189ETV poma
2015-09-01 8:43 ` RTL8189ETV Hans de Goede
2015-09-01 11:16 ` RTL8189ETV poma
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=55E49415.7090807@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=hdegoede@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=pomidorabelisima@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).