driver

driver

[Igor Filippov]

[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]

Hello!

I use the USB2CAN converter i-7565H1 (from ICP CON) and the driver 
installation script from the delivery kit (in the attachment).

And the dmesg comand output is:

[  489.495739] usbcore: registered new interface driver usbserial_generic
[  489.495747] usbserial: USB Serial support registered for generic
[  489.590087] usbserial_generic 3-3:1.0: The "generic" usb-serial 
driver is only for testing and one-off prototypes.
[  489.590088] usbserial_generic 3-3:1.0: Tell linux-usb@vger.kernel.org 
to add your device to a proper driver.
[  489.590090] usbserial_generic 3-3:1.0: device has no bulk endpoints
[  489.590106] usbserial_generic 3-3:1.1: The "generic" usb-serial 
driver is only for testing and one-off prototypes.
[  489.590107] usbserial_generic 3-3:1.1: Tell linux-usb@vger.kernel.org 
to add your device to a proper driver.
[  489.590108] usbserial_generic 3-3:1.1: generic converter detected
[  489.590208] usb 3-3: generic converter now attached to ttyUSB0

Can you solve this problem? Thank You.


[-- Attachment #2: I7565H1H2_install.zip --]
[-- Type: application/zip, Size: 717 bytes --]

Re: driver

[Greg KH]

On Fri, Feb 28, 2020 at 05:26:30PM +0300, Igor Filippov wrote:
> Hello!
> 
> I use the USB2CAN converter i-7565H1 (from ICP CON) and the driver
> installation script from the delivery kit (in the attachment).
> 
> And the dmesg comand output is:
> 
> [  489.495739] usbcore: registered new interface driver usbserial_generic
> [  489.495747] usbserial: USB Serial support registered for generic
> [  489.590087] usbserial_generic 3-3:1.0: The "generic" usb-serial driver is
> only for testing and one-off prototypes.
> [  489.590088] usbserial_generic 3-3:1.0: Tell linux-usb@vger.kernel.org to
> add your device to a proper driver.
> [  489.590090] usbserial_generic 3-3:1.0: device has no bulk endpoints
> [  489.590106] usbserial_generic 3-3:1.1: The "generic" usb-serial driver is
> only for testing and one-off prototypes.
> [  489.590107] usbserial_generic 3-3:1.1: Tell linux-usb@vger.kernel.org to
> add your device to a proper driver.
> [  489.590108] usbserial_generic 3-3:1.1: generic converter detected
> [  489.590208] usb 3-3: generic converter now attached to ttyUSB0
> 
> Can you solve this problem? Thank You.
> 


Can you provide the output of 'lsusb -v' from the command line with the
device plugged in?

thanks,

greg k-h

Re: driver

[Igor Filippov]

[-- Attachment #1: Type: text/plain, Size: 4396 bytes --]

The i-7565H1 device has a driver installation script from the device 
manufacturer. This script contains the instruction "modprobe usbserial". 
If this is not correct, could you tell me which driver we should use? I 
attach the script to the message. The link to where we got the software: 
http://www.icpdas.com/root/product/solutions/industrial_communication/fieldbus/can_bus/converter/i-7565-h1h2.html

thanks,

igor

04.03.2020 12:09, Greg KH пишет:
> On Fri, Feb 28, 2020 at 07:37:40PM +0300, Igor Filippov wrote:
>> I apologize for my carelessness. I will try to send it to everyone...
> You can't send html email to the list, that will cause it to get
> rejected :(
>
> Anyway, I think this is the device, right:
>
>> Bus 002 Device 004: ID 1b5c:0201
>> Couldn't open device, some information will be missing
>> Device Descriptor:
>>    bLength                18
>>    bDescriptorType         1
>>    bcdUSB               2.00
>>    bDeviceClass            2 Communications
>>    bDeviceSubClass         0
>>    bDeviceProtocol         0
>>    bMaxPacketSize0        64
>>    idVendor           0x1b5c
>>    idProduct          0x0201
>>    bcdDevice            1.00
>>    iManufacturer           4
>>    iProduct               38
>>    iSerial                74
>>    bNumConfigurations      1
>>    Configuration Descriptor:
>>      bLength                 9
>>      bDescriptorType         2
>>      wTotalLength           67
>>      bNumInterfaces          2
>>      bConfigurationValue     1
>>      iConfiguration          0
>>      bmAttributes         0x80
>>        (Bus Powered)
>>      MaxPower              250mA
>>      Interface Descriptor:
>>        bLength                 9
>>        bDescriptorType         4
>>        bInterfaceNumber        0
>>        bAlternateSetting       0
>>        bNumEndpoints           1
>>        bInterfaceClass         2 Communications
>>        bInterfaceSubClass      2 Abstract (modem)
>>        bInterfaceProtocol      0 None
>>        iInterface            104
>>        CDC Header:
>>          bcdCDC               1.10
>>        CDC Call Management:
>>          bmCapabilities       0x01
>>            call management
>>          bDataInterface          1
>>        CDC ACM:
>>          bmCapabilities       0x02
>>            line coding and serial state
>>        CDC Union:
>>          bMasterInterface        0
>>          bSlaveInterface         1
>>        Endpoint Descriptor:
>>          bLength                 7
>>          bDescriptorType         5
>>          bEndpointAddress     0x81  EP 1 IN
>>          bmAttributes            3
>>            Transfer Type            Interrupt
>>            Synch Type               None
>>            Usage Type               Data
>>          wMaxPacketSize     0x0010  1x 16 bytes
>>          bInterval              32
>>      Interface Descriptor:
>>        bLength                 9
>>        bDescriptorType         4
>>        bInterfaceNumber        1
>>        bAlternateSetting       0
>>        bNumEndpoints           2
>>        bInterfaceClass        10 CDC Data
>>        bInterfaceSubClass      0 Unused
>>        bInterfaceProtocol      0
>>        iInterface            104
>>        Endpoint Descriptor:
>>          bLength                 7
>>          bDescriptorType         5
>>          bEndpointAddress     0x02  EP 2 OUT
>>          bmAttributes            2
>>            Transfer Type            Bulk
>>            Synch Type               None
>>            Usage Type               Data
>>          wMaxPacketSize     0x0040  1x 64 bytes
>>          bInterval               0
>>        Endpoint Descriptor:
>>          bLength                 7
>>          bDescriptorType         5
>>          bEndpointAddress     0x82  EP 2 IN
>>          bmAttributes            2
>>            Transfer Type            Bulk
>>            Synch Type               None
>>            Usage Type               Data
>>          wMaxPacketSize     0x0040  1x 64 bytes
>>          bInterval               0
>
> Can you confirm that the vendor/product id is 1b5c/0201 for this?
>
> If so, what is wrong with the "normal" cdc driver here?  Why does the
> usb-serial generic driver need to be used instead?
>
> Do you have a pointer to where you got the instructions to usb the
> usb-serial generic driver instead of the built-in kernel driver?
>
> thanks,
>
> greg k-h

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

#!/bin/sh
BLACKLIST=/etc/modprobe.d/blacklist.conf
USB_GENERIC_NEWID=/sys/bus/usb-serial/drivers/generic/new_id
VENDOR='1b5c'
H1_PRODUCT='0201'
H2_PRODUCT='0202'

if [ "$1" = 'help' ]; then
	echo "----------------------------------------"
	echo "usage: ./I7565H1H2_install"
	echo "       Install I7565-H1/H2 module driver automatically"
	echo "usage: ./I7565H1H2_install remove"
	echo "       Remove I7565-H1/H2 driver"
	echo "usage: ./I7565H1H2_install cdc_acm"
	echo "       Remove cdc_acm from blacklist."
	exit
elif [ "$1" = 'remove' ]; then
	modprobe -r usbserial
	exit
elif [ "$1" = 'cdc_acm' ]; then
	sed -i '/cdc_acm/d' $BLACKLIST
	exit
fi

#check i-7565-H1/H2 Vendor ID first
cat `find /sys -name idVendor` | grep $VENDOR > /dev/null 2>&1
RETURN="$?"

if [ "$RETURN" = '1' ]; then
	echo "No i-7565-H1/H2 found!"
	exit;
fi

CDC_ACM=`grep cdc_acm "$BLACKLIST"`

if [ "$CDC_ACM" = "" ]; then
	echo "blacklist cdc_acm" >> $BLACKLIST
	modprobe -r cdc_acm
fi

#install driver "usbserial" first
modprobe usbserial

#check i-7565-H1 Product ID
cat `find /sys -name idProduct` | grep $H1_PRODUCT > /dev/null 2>&1
RETURN="$?"
if [ "$RETURN" = '0' ]; then
	echo "Install driver for i-7565-H1."
	echo "$VENDOR $H1_PRODUCT" > $USB_GENERIC_NEWID
fi

#check i-7565-H2 Product ID
cat `find /sys -name idProduct` | grep $H2_PRODUCT > /dev/null 2>&1
RETURN="$?"
if [ "$RETURN" = '0' ]; then
	echo "Install driver for i-7565-H2."
	echo "$VENDOR $H2_PRODUCT" > $USB_GENERIC_NEWID 
fi

echo "success."

Re: driver

[Greg KH]

On Fri, Feb 28, 2020 at 07:37:40PM +0300, Igor Filippov wrote:
> I apologize for my carelessness. I will try to send it to everyone...

You can't send html email to the list, that will cause it to get
rejected :(

Anyway, I think this is the device, right:

> Bus 002 Device 004: ID 1b5c:0201
> Couldn't open device, some information will be missing
> Device Descriptor:
>   bLength                18
>   bDescriptorType         1
>   bcdUSB               2.00
>   bDeviceClass            2 Communications
>   bDeviceSubClass         0
>   bDeviceProtocol         0
>   bMaxPacketSize0        64
>   idVendor           0x1b5c
>   idProduct          0x0201
>   bcdDevice            1.00
>   iManufacturer           4
>   iProduct               38
>   iSerial                74
>   bNumConfigurations      1
>   Configuration Descriptor:
>     bLength                 9
>     bDescriptorType         2
>     wTotalLength           67
>     bNumInterfaces          2
>     bConfigurationValue     1
>     iConfiguration          0
>     bmAttributes         0x80
>       (Bus Powered)
>     MaxPower              250mA
>     Interface Descriptor:
>       bLength                 9
>       bDescriptorType         4
>       bInterfaceNumber        0
>       bAlternateSetting       0
>       bNumEndpoints           1
>       bInterfaceClass         2 Communications
>       bInterfaceSubClass      2 Abstract (modem)
>       bInterfaceProtocol      0 None
>       iInterface            104
>       CDC Header:
>         bcdCDC               1.10
>       CDC Call Management:
>         bmCapabilities       0x01
>           call management
>         bDataInterface          1
>       CDC ACM:
>         bmCapabilities       0x02
>           line coding and serial state
>       CDC Union:
>         bMasterInterface        0
>         bSlaveInterface         1
>       Endpoint Descriptor:
>         bLength                 7
>         bDescriptorType         5
>         bEndpointAddress     0x81  EP 1 IN
>         bmAttributes            3
>           Transfer Type            Interrupt
>           Synch Type               None
>           Usage Type               Data
>         wMaxPacketSize     0x0010  1x 16 bytes
>         bInterval              32
>     Interface Descriptor:
>       bLength                 9
>       bDescriptorType         4
>       bInterfaceNumber        1
>       bAlternateSetting       0
>       bNumEndpoints           2
>       bInterfaceClass        10 CDC Data
>       bInterfaceSubClass      0 Unused
>       bInterfaceProtocol      0
>       iInterface            104
>       Endpoint Descriptor:
>         bLength                 7
>         bDescriptorType         5
>         bEndpointAddress     0x02  EP 2 OUT
>         bmAttributes            2
>           Transfer Type            Bulk
>           Synch Type               None
>           Usage Type               Data
>         wMaxPacketSize     0x0040  1x 64 bytes
>         bInterval               0
>       Endpoint Descriptor:
>         bLength                 7
>         bDescriptorType         5
>         bEndpointAddress     0x82  EP 2 IN
>         bmAttributes            2
>           Transfer Type            Bulk
>           Synch Type               None
>           Usage Type               Data
>         wMaxPacketSize     0x0040  1x 64 bytes
>         bInterval               0


Can you confirm that the vendor/product id is 1b5c/0201 for this?

If so, what is wrong with the "normal" cdc driver here?  Why does the
usb-serial generic driver need to be used instead?

Do you have a pointer to where you got the instructions to usb the
usb-serial generic driver instead of the built-in kernel driver?

thanks,

greg k-h

driver

[Mohan Baral]

i couldn't turn on my card into monitor mode...
where could I get driver file as my
pci-id 14e4:4315
and chip id BCM4312

Re: Driver

[Rafał Miłecki]

2014-02-16 1:42 GMT+01:00 MHD HA <muhamad_cte@hotmail.com>:
> Can you please send me the download source of the intel PRO/Wireless 2200GB Driver for Linux, the link that attached on the sourceforge.net is not working.

When reporting problem with a page, URL is really helpful.

I guess you meant the firmware, not a driver?
I guess you meant:
http://ipw2200.sourceforge.net/firmware.php
http://ipw2200.sourceforge.net/firmware.php?fid=8
URLs?

The second URL has a link "I Agree" but it doesn't seem to work currently.

-- 
Rafał

Driver

[MHD HA]

Dear/Mr

Can you please send me the download source of the intel PRO/Wireless 2200GB Driver for Linux, the link that attached on the sourceforge.net is not working.

Best Regards

Re: driver

[John W. Linville]

On Sat, Jan 29, 2011 at 08:57:14AM +0100, Sharon Weller wrote:
> 
> Dear Linux
> 
> Is there anyway I can get a driver for the Intel Pro/Wireless 2200BG? I have an old MaxData laptop and am desperately trying to get the wifi to work and I see that the project is no longer maintained.
> 
> Thank you very much for your help
> 
> Sharon Weller--

That device is reasonably well supported for a long time.  Just install
your favorite distro and go.  In fact, I'm using it right now on my
"easy chair" laptop... :-)

John
-- 
John W. Linville                Someday the world will need a hero, and you
linville@tuxdriver.com                  might be all we have.  Be ready.

driver

[Sharon Weller]

Dear Linux

Is there anyway I can get a driver for the Intel Pro/Wireless 2200BG? I have an old MaxData laptop and am desperately trying to get the wifi to work and I see that the project is no longer maintained.

Thank you very much for your help

Sharon Weller

Re: driver

[Pavel Roskin]

Hello!

>    Hi.Could you help me with via ac97 audio driver?
>    Thank you.

I don't know if anybody provides technical support for ALSA.  If somebody
does, maybe it's a good idea to put a link on the website.  Some users are
simply uncapable of writing proper bugreports, but they may be willing to
pay to have their problems solved.

That said, the VIA driver in the CVS version of ALSA works fine for me.  
It was broken for some time, but now it's fixed.

-- 
Regards,
Pavel Roskin



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

driver

[parintele]

   


   Hi.Could you help me with via ac97 audio driver?
   Thank you.




------------------------------
K Free E-mail http://www.k.ro/
by KappaNet http://www.kappa.ro/







-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf