Hi, I have plug in this USB network device:
Bus 001 Device 002: ID 2001:1a02 D-Link Corp.
T: Bus=01 Lev=01 Prnt=01 Port=04 Cnt=01 Dev#= 2 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=2001 ProdID=1a02 Rev= 0.01 S: Manufacturer=D-Link S: Product=DUB-E100 S: SerialNumber=E5ECEB C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=200mA I:* If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=00 Driver=(none) E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=128ms E: Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=03(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
This is the log information:
Oct 24 10:10:56 s-virt kernel: usb 1-5: new high speed USB device number 2 using ehci_hcd Oct 24 10:10:57 s-virt kernel: usb 1-5: New USB device found, idVendor=2001, idProduct=1a02 Oct 24 10:10:57 s-virt kernel: usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 24 10:10:57 s-virt kernel: usb 1-5: Product: DUB-E100 Oct 24 10:10:57 s-virt kernel: usb 1-5: Manufacturer: D-Link Oct 24 10:10:57 s-virt kernel: usb 1-5: SerialNumber: E5ECEB Oct 24 10:10:57 s-virt kernel: usb 1-5: configuration #1 chosen from 1 choice
But, if I run 'ip a' I do not see other new network device (ethX).
It's possible resolve this issue and use this USB network device?
Many thanks
On Tue, Oct 29, 2013 at 7:00 AM, Dario Lesca d.lesca@solinos.it wrote:
Hi, I have plug in this USB network device:
Are you running CentOS 5 or CentOS 6?
Bus 001 Device 002: ID 2001:1a02 D-Link Corp.
T: Bus=01 Lev=01 Prnt=01 Port=04 Cnt=01 Dev#= 2 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=2001 ProdID=1a02 Rev= 0.01 S: Manufacturer=D-Link S: Product=DUB-E100 S: SerialNumber=E5ECEB C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=200mA I:* If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=00 Driver=(none) E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=128ms E: Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=03(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
This is the log information:
Oct 24 10:10:56 s-virt kernel: usb 1-5: new high speed USB device number
2 using ehci_hcd
Oct 24 10:10:57 s-virt kernel: usb 1-5: New USB device found,
idVendor=2001, idProduct=1a02
Oct 24 10:10:57 s-virt kernel: usb 1-5: New USB device strings: Mfr=1,
Product=2, SerialNumber=3
Oct 24 10:10:57 s-virt kernel: usb 1-5: Product: DUB-E100 Oct 24 10:10:57 s-virt kernel: usb 1-5: Manufacturer: D-Link Oct 24 10:10:57 s-virt kernel: usb 1-5: SerialNumber: E5ECEB Oct 24 10:10:57 s-virt kernel: usb 1-5: configuration #1 chosen from 1
choice
But, if I run 'ip a' I do not see other new network device (ethX).
It's possible resolve this issue and use this USB network device?
You need to figure out what chipset your usb ethernet device uses. Maybe it uses ax8817x driver like [0] says? Or D-Link decided to change the chipset without changing the model number. ;)
Run lsusb and locate your device. Use the "Bus" and "Device" numbers in the following command so you get more info on just that device. lsusb -v -s "Bus:Device" | egrep 'id(Vendor|Product)'
If you're lucky there will be some useful information in those two fields, otherwise run the second command without piping it to egrep and read through all the verbose info for clues.
It doesn't appear the ax8817x driver is shipped with stock CentOS 6 kernels (and since 5 kernels are much older, don't expect it's 2.6.18.x kernel to include the driver which came out around 2.6.21 or .23). # find /lib/modules/2.6.32-358.23.2.el6.x86_64/ -iname 'ax88*' -print
And the word is that there's a bug or two [1] for the ax8817x drivers (this Plugable device uses a similar chipset and it appears the same driver as well) that aren't fixed until 3.2 series kernels. You may just have to compile the module manually from source [2] which won't be horrible (since these instructions are for Ubuntu you'll have to adapt them for RHEL/CentOS as necessary).
** Don't hold me to any of this info until you know for sure which chipset _you_ have!
[0] http://www.linux-usb.org/devices.html#net [1] http://plugable.com/products/USB3-E1000/drivers [2] http://plugable.com/2010/10/18/howto-asix-88178-usb-ethernet-adapter-on-ubun...
Many thanks
-- Dario Lesca - sip:dario@solinos.it (Inviato dal mio Linux Fedora19+Gnome3.8)
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Il giorno mar, 29/10/2013 alle 08.48 -0400, SilverTip257 ha scritto:
On Tue, Oct 29, 2013 at 7:00 AM, Dario Lesca d.lesca@solinos.it wrote:
Hi, I have plug in this USB network device:
Are you running CentOS 5 or CentOS 6?
Like subject say, CentOS 6.4
The kernel is last: 2.6.32-358.23.2.el6.x86_64
You need to figure out what chipset your usb ethernet device uses. Maybe it uses ax8817x driver like [0] says? Or D-Link decided to change the chipset without changing the model number. ;)
Run lsusb and locate your device. Use the "Bus" and "Device" numbers in the following command so you get more info on just that device. lsusb -v -s "Bus:Device" | egrep 'id(Vendor|Product)'
If you're lucky there will be some useful information in those two fields, otherwise run the second command without piping it to egrep and read through all the verbose info for clues.
It doesn't appear the ax8817x driver is shipped with stock CentOS 6 kernels (and since 5 kernels are much older, don't expect it's 2.6.18.x kernel to include the driver which came out around 2.6.21 or .23). # find /lib/modules/2.6.32-358.23.2.el6.x86_64/ -iname 'ax88*' -print
And the word is that there's a bug or two [1] for the ax8817x drivers (this Plugable device uses a similar chipset and it appears the same driver as well) that aren't fixed until 3.2 series kernels. You may just have to compile the module manually from source [2] which won't be horrible (since these instructions are for Ubuntu you'll have to adapt them for RHEL/CentOS as necessary).
** Don't hold me to any of this info until you know for sure which chipset _you_ have!
[0] http://www.linux-usb.org/devices.html#net [1] http://plugable.com/products/USB3-E1000/drivers [2] http://plugable.com/2010/10/18/howto-asix-88178-usb-ethernet-adapter-on-ubun...
Thank SilverTip257 for reply, but I have solved rebuild and install the asix driver follow this tread:
http://grinkin.ru/dlink-DUB-E100.html.
I have take the CD's Linux driver (DUB_E100_Linux_v420.zip), unzip it and apply this patch:
--- asix.c.orig 2011-09-19 14:48:58.000000000 +0200 +++ asix.c 2013-10-29 14:15:18.662854310 +0100 @@ -3412,6 +3412,10 @@ USB_DEVICE (0x2001, 0x1a00), .driver_info = (unsigned long) &dlink_dub_e100_info, }, {
- // DLink DUB-E100
- USB_DEVICE (0x2001, 0x1a02),
- .driver_info = (unsigned long) &ax88772b_info,
+}, { // DLink DUB-E100B USB_DEVICE (0x2001, 0x3c05), .driver_info = (unsigned long) &dlink_dub_e100b_info,
Now all work fine.
Thanks
Dario Lesca wrote:
Il giorno mar, 29/10/2013 alle 08.48 -0400, SilverTip257 ha scritto:
On Tue, Oct 29, 2013 at 7:00 AM, Dario Lesca d.lesca@solinos.it wrote:
Hi, I have plug in this USB network device:
<snip>
Thank SilverTip257 for reply, but I have solved rebuild and install the asix driver follow this tread:
http://grinkin.ru/dlink-DUB-E100.html.
I have take the CD's Linux driver (DUB_E100_Linux_v420.zip), unzip it and apply this patch:
--- asix.c.orig 2011-09-19 14:48:58.000000000 +0200 +++ asix.c 2013-10-29 14:15:18.662854310 +0100 @@ -3412,6 +3412,10 @@ USB_DEVICE (0x2001, 0x1a00), .driver_info = (unsigned long) &dlink_dub_e100_info, }, {
- // DLink DUB-E100
- USB_DEVICE (0x2001, 0x1a02),
- .driver_info = (unsigned long) &ax88772b_info,
+}, { // DLink DUB-E100B USB_DEVICE (0x2001, 0x3c05), .driver_info = (unsigned long) &dlink_dub_e100b_info,
Now all work fine.
One thing you *must* remember: you'll have to rebuild it every time you do a kernel upgrade.
mark
Il giorno mar, 29/10/2013 alle 09.45 -0400, m.roth@5-cent.us ha scritto:
One thing you *must* remember: you'll have to rebuild it every time you do a kernel upgrade.
Yes, I know, I will pay attention (with some scripts, I rebuild and install it and restart network via rc.local).
If you (or someone into list) tell me that fill a bug is useful to make sure that this patch will be included in a future kernel ... I do it.
Thanks
On Tue, Oct 29, 2013 at 9:38 AM, Dario Lesca d.lesca@solinos.it wrote:
Il giorno mar, 29/10/2013 alle 08.48 -0400, SilverTip257 ha scritto:
On Tue, Oct 29, 2013 at 7:00 AM, Dario Lesca d.lesca@solinos.it wrote:
Hi, I have plug in this USB network device:
Are you running CentOS 5 or CentOS 6?
Like subject say, CentOS 6.4
The subject was heavily abbreviated "c6.4" and the OS was not contained in the body. I saw the abbreviation after the fact.
The kernel is last: 2.6.32-358.23.2.el6.x86_64
You need to figure out what chipset your usb ethernet device uses. Maybe it uses ax8817x driver like [0] says? Or D-Link decided to change the chipset without changing the model number. ;)
Run lsusb and locate your device. Use the "Bus" and "Device" numbers in the following command so you get
more
info on just that device. lsusb -v -s "Bus:Device" | egrep 'id(Vendor|Product)'
If you're lucky there will be some useful information in those two
fields,
otherwise run the second command without piping it to egrep and read through all the verbose info for clues.
It doesn't appear the ax8817x driver is shipped with stock CentOS 6
kernels
(and since 5 kernels are much older, don't expect it's 2.6.18.x kernel to include the driver which came out around 2.6.21 or .23). # find /lib/modules/2.6.32-358.23.2.el6.x86_64/ -iname 'ax88*' -print
And the word is that there's a bug or two [1] for the ax8817x drivers
(this
Plugable device uses a similar chipset and it appears the same driver as well) that aren't fixed until 3.2 series kernels. You may just have to compile the module manually from source [2] which won't be horrible
(since
these instructions are for Ubuntu you'll have to adapt them for
RHEL/CentOS
as necessary).
** Don't hold me to any of this info until you know for sure which
chipset
_you_ have!
[0] http://www.linux-usb.org/devices.html#net [1] http://plugable.com/products/USB3-E1000/drivers [2]
http://plugable.com/2010/10/18/howto-asix-88178-usb-ethernet-adapter-on-ubun...
Thank SilverTip257 for reply, but I have solved rebuild and install the asix driver follow this tread:
http://grinkin.ru/dlink-DUB-E100.html.
I have take the CD's Linux driver (DUB_E100_Linux_v420.zip), unzip it and apply this patch:
--- asix.c.orig 2011-09-19 14:48:58.000000000 +0200 +++ asix.c 2013-10-29 14:15:18.662854310 +0100 @@ -3412,6 +3412,10 @@ USB_DEVICE (0x2001, 0x1a00), .driver_info = (unsigned long) &dlink_dub_e100_info, }, {
// DLink DUB-E100USB_DEVICE (0x2001, 0x1a02),.driver_info = (unsigned long) &ax88772b_info,+}, { // DLink DUB-E100B USB_DEVICE (0x2001, 0x3c05), .driver_info = (unsigned long) &dlink_dub_e100b_info,
Now all work fine.
Cool.
Thanks
-- Dario Lesca - sip:dario@solinos.it (Inviato dal mio Linux Fedora19+Gnome3.8)
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-
Dario Lesca -
m.roth＠5-cent.us -
SilverTip257