Frank

Frank

[Pastor Frank Ernesto Ramírez Torres]

[-- Attachment #1.1: Type: text/plain, Size: 672 bytes --]

Hi, I downloaded the Linux 5.2.5 kernel from your website. I have a tplink
t2uh that I would like to operate on the Debian 9.0 system that I have
installed. Note that there is an option in the configuration to compile the
mt7610u driver. But after enabling it in .config, compile it, install it
and connect the t2uh nothing happens. The dmesg tells me that it tries to
load the mt7610e first but he does not find it. It changes for mt7610u and
when trying to load it, error -2 occurs. Please, I am completely new
compiling the Linux kernel, I would appreciate if someone taught me how to
compile this driver correctly and see it work fine. Thank you very much in
advance.

[-- Attachment #1.2: Type: text/html, Size: 695 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Driver for t2uh mt7610e/mt7610e (was Re: Frank

[Valdis Klētnieks]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.1: Type: text/plain; charset=utf-8, Size: 1147 bytes --]

On Sat, 03 Aug 2019 10:57:15 -0400, Pastor Frank Ernesto Ramírez Torres said:

> Hi, I downloaded the Linux 5.2.5 kernel from your website. I have a tplink
> t2uh that I would like to operate on the Debian 9.0 system that I have
> installed. Note that there is an option in the configuration to compile the
> mt7610u driver. But after enabling it in .config, compile it, install it
> and connect the t2uh nothing happens. The dmesg tells me that it tries to
> load the mt7610e first but he does not find it. It changes for mt7610u and
> when trying to load it, error -2 occurs

The first thing missing from this info is any messages from dmesg from when the
driver loads and tries to initialize.

Also, if this is a USB device, plug it in and do an 'lsusb' and provide the
output so we can see what the USB device ID is.  There's a very real
possibility that one of the mt7610 drivers supports the chipset in the device,
but nothing tries to claim it because none of the drivers have that device ID
in their tables.

Also, I fixed the Subject: line for you - the original was uninformative to the
point of looking spammy...


[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies