On 23-Oct-2001 [EMAIL PROTECTED] wrote: > Send Linux-usb-users mailing list submissions to > [EMAIL PROTECTED] > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/linux-usb-users > or, via email, send a message with subject or body 'help' to > [EMAIL PROTECTED] > > You can reach the person managing the list at > [EMAIL PROTECTED] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Linux-usb-users digest..." > > > Today's Topics: > > 1. Re: USB-Joystick doesn't work (Vojtech Pavlik) > 2. Re: USB-Joystick doesn't work (Dirk Vornheder) > 3. Re: "usb_control/bulk_msg: timeout" with se401 (Jeroen Vreeken) > 4. Re: Booting a USB disk (Matthew Dharm) > 5. Re: "usb_control/bulk_msg: timeout" with se401 (Mark R. Rubin) > 6. Intel Easy PC Camera (Shane Hickey) > 7. USB cable modem with ECM ([EMAIL PROTECTED]) > 8. Re: Getting assigned /dev/ttyUSB* device (ming deng) > 9. Re: Re: Getting assigned /dev/ttyUSB* device (Greg KH) > 10. Re: Aarrrgghh, **$#%* modem!!! (Greg KH) > > --__--__-- > > Message: 1 > Date: Tue, 23 Oct 2001 12:25:39 +0200 > From: Vojtech Pavlik <[EMAIL PROTECTED]> > To: Dirk Vornheder <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] > Subject: Re: [Linux-usb-users] USB-Joystick doesn't work > > On Tue, Oct 23, 2001 at 12:33:38AM +0200, Dirk Vornheder wrote: >> Hi ! >> >> I can't use my usb joystick "Digital Raider Pro" under linux. >> >> usbview shows it as "Interacting gaming device": >> >> Interact Gaming Device >> Speed: 1.5Mb/s (low) >> USB Version: 1.00 >> Device Class: 00(>ifc ) >> Device Subclass: 00 >> Device Protocol: 00 >> Maximum Default Endpoint Size: 8 >> Number of Configurations: 1 >> Vendor Id: 05fd >> Product Id: 0251 >> Revision Number: 11.00 >> >> Config Number: 1 >> Number of Interfaces: 1 >> Attributes: 80 >> MaxPower Needed: 90mA >> >> Interface Number: 0 >> Name: hid >> Alternate Number: 0 >> Class: 03(HID ) >> Sub Class: 0 >> Protocol: 0 >> Number of Endpoints: 1 >> >> Endpoint Address: 81 >> Direction: in >> Attribute: 3 >> Type: Int. >> Max Packet Size: 8 >> Interval: 20ms >> >> cat /proc/bus/usb/devices shows: >> >> T: Bus=01 Lev=02 Prnt=03 Port=00 Cnt=01 Dev#= 4 Spd=1.5 MxCh= 0 >> D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 >> P: Vendor=05fd ProdID=0251 Rev=11.00 >> S: Product=Interact Gaming Device >> C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr= 90mA >> I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=hid >> E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl= 20ms >> >> I find in /var/log/messages: >> >> input0: USB HID v1.00 Joystick [05fd:0251] on usb1:4.0 >> >> But if i try to use it the joystick doesn't work: >> >> jstest /dev/input/js0 >> >> jstest: No such device >> >> My config: SuSE 7.3, Kernel 2.4.13pre6, KDE 2.2.1, XFree 4.1.0 > > You need to load the joydev module. > > -- > Vojtech Pavlik > SuSE Labs > > > --__--__-- > > Message: 2 > From: [EMAIL PROTECTED] (Dirk Vornheder) > To: Vojtech Pavlik <[EMAIL PROTECTED]> > Subject: Re: [Linux-usb-users] USB-Joystick doesn't work > Date: Tue, 23 Oct 2001 12:38:35 +0200 > Cc: [EMAIL PROTECTED] > > >> > I find in /var/log/messages: >> > >> > input0: USB HID v1.00 Joystick [05fd:0251] on usb1:4.0 >> > >> > But if i try to use it the joystick doesn't work: >> > >> > jstest /dev/input/js0 >> > >> > jstest: No such device >> > >> > My config: SuSE 7.3, Kernel 2.4.13pre6, KDE 2.2.1, XFree 4.1.0 >> >> You need to load the joydev module. > > This helps. > > Thanks, > > Dirk > > > --__--__-- > > Message: 3 > Date: Tue, 23 Oct 2001 18:14:52 +0200 > From: Jeroen Vreeken <[EMAIL PROTECTED]> > To: "Mark R . Rubin" <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED], [EMAIL PROTECTED] > Subject: Re: [Linux-usb-users] "usb_control/bulk_msg: timeout" with se401 > > On 2001.10.23 01:47:18 +0200 Mark R. Rubin wrote: >> joey tsai <[EMAIL PROTECTED]> writes: >> >> > My camera: Kensington VideoCAM 67016 >> > My kernel: 2.4.12 >> > My usb: usb-uhci >> > >> > USB recognizes the new device when I plug the camera in. The se401 >> > module recognizes the correct camera. When I use gqcam or vidcat, the >> > light on the camera goes on. But I never get any pictures. Instead, I >> > get this repeating message in my log: >> > Oct 22 15:38:14 corban kernel: usb_control/bulk_msg: timeout >> > >> > Any hints or suggestions? I would really appreciate it. >> >> o I had the same or similar problem with a 67016 on 2.4.9-ac12. >> >> o I got the camera to (mostly) work by replacing the 0.23 revision of >> the se401 driver with an older, 0.20, version. I have no idea >> what's going on, and received no response from the maintainer to a >> posting in linux-usb-users. > > Sorry for the long delay, I have been very busy with school lately.... > > The problem I have is that I haven't been able to reproduce this. > I will look into it this week. > Does it happen with the camera in all resolutions? (can you try some > resolutions reported by the camera on detection?) > > Jeroen > > > > > --__--__-- > > Message: 4 > Date: Tue, 23 Oct 2001 10:13:11 -0700 > From: Matthew Dharm <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Re: [Linux-usb-users] Booting a USB disk > Organization: One Eyed Alien Networks > > > --v9Ux+11Zm5mwPlX6 > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > Some people have reported success by hacking the kernel to pause for a few > seconds to allow full enumeration of USB device before trying to mount the > root filesystem. > > There are some patches floating around -- I don't have them tho. > > Matt > > On Tue, Oct 23, 2001 at 12:57:49PM +0100, [EMAIL PROTECTED] wrote: >>=20 >> I want to run linux installed on a partition on a USB disk. >>=20 >> In the past, I achieve that with a parallel-port to IDE >> adapter box with a common IDE hard disk inside, as well as >> with a parallel iomega ZIP. It works well. >>=20 >> In either case I used a floppy that boots the kernel, >> telling it where the root filesystem is. That worked >> because the kernel _does_ detect the devices and partitions >> _BEFORE_ VFS tries to mount the root file system. >>=20 >> My problem with the USB disk, is that the device gets >> detected _after_ VFS tries to mount the root file system, >> and therefore it can't mount it. >> I assume this behaviour is due to the plug-and-play >> nature of USB devices. >>=20 >> The question: >>=20 >> does anybody knows a way to force the kernel >> to detect USB disks before mounting =20 >> the root device? >>=20 >> BTW: Of course the drivers for USB and USB >> mass storage support are compiled into the kernel. >>=20 >> Thanks in advace, and thanks to those who told me >> last week to use kernel 2.4 to support USB disks. >>=20 >> jordi bataller >> Gandia >> SPAIN >>=20 >> _______________________________________________ >> [EMAIL PROTECTED] >> To unsubscribe, use the last form field at: >> https://lists.sourceforge.net/lists/listinfo/linux-usb-users > > --=20 > Matthew Dharm Home: mdharm-usb@one-eyed-alien.= > net=20 > Maintainer, Linux USB Mass Storage Driver > > S: Another stupid question? > G: There's no such thing as a stupid question, only stupid people. > -- Stef and Greg > User Friendly, 7/15/1998 > > --v9Ux+11Zm5mwPlX6 > Content-Type: application/pgp-signature > Content-Disposition: inline > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.6 (GNU/Linux) > Comment: For info see http://www.gnupg.org > > iD8DBQE71aUnz64nssGU+ykRAjF1AKDLtcnL8wGDD+licN1Yb1K8FFepTwCglTQG > LhUTOFzYk69Gofou8o5uG48= > =kXFj > -----END PGP SIGNATURE----- > > --v9Ux+11Zm5mwPlX6-- > > > --__--__-- > > Message: 5 > Date: Tue, 23 Oct 2001 10:15:39 -0700 > From: "Mark R. Rubin" <[EMAIL PROTECTED]> > Subject: Re: [Linux-usb-users] "usb_control/bulk_msg: timeout" with se401 > To: Jeroen Vreeken <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED], [EMAIL PROTECTED] > Organization: None to speak of > > Jeroen Vreeken <[EMAIL PROTECTED]> writes: > >> Sorry for the long delay, I have been very busy with school lately.... >> >> The problem I have is that I haven't been able to reproduce this. >> I will look into it this week. >> Does it happen with the camera in all resolutions? (can you try some >> resolutions reported by the camera on detection?) > > o No problem. Thanks for all your work on the driver. Whenever you > get the time, tell me what I can do to help. > > o Note that Joey Tsai sent me email saying that 0,20 works for him. > > o I just tested, and got the same problem with 0.23 at all standard > resolutions: > > "qsif" 160x120 > "sif" 320x240 > "cif" 352x288 > "vga" 640x480 > "svga" 800x600 > > in the range the camera claims to support. My code currently doesn't > support the other Kensington resolutions. > > > o I get the same message: > > usb_control/bulk_msg: timeout > > (these messages repeat many times) whether I use my own code or other > applications (e.g. `camstream`, http://www.smcc.demon.nl/camstream/) > > Applications freezes at this point. Sending them an interrupt takes > a long time before the process exits. > > > o In my own code, I've traced the hang to one of two places. If I > use mmap I/O, it happens at: > > ioctl(_file_desc, VIDIOCMCAPTURE, &_mmap) > > o If I use normal I/O, it happens at: > > read(_file_desc, _read_buffer, _read_buffer_size > > > o Following are the logs when I `modprobe usb-uhci`. (I've had the > same hang using "uhci".) Thanks again for the se401 driver. > > usb-uhci.c: $Revision: 1.259 $ time 20:17:08 Sep 25 2001 > usb-uhci.c: High bandwidth mode enabled > PCI: Found IRQ 12 for device 00:07.2 > PCI: Sharing IRQ 12 with 00:07.3 > usb-uhci.c: USB UHCI at I/O 0xc800, IRQ 12 > usb-uhci.c: Detected 2 ports > usb.c: new USB bus registered, assigned bus number 1 > Product: USB UHCI Root Hub > SerialNumber: c800 > hub.c: USB hub found > hub.c: 2 ports detected > PCI: Found IRQ 12 for device 00:07.3 > PCI: Sharing IRQ 12 with 00:07.2 > usb-uhci.c: USB UHCI at I/O 0xcc00, IRQ 12 > usb-uhci.c: Detected 2 ports > invoke /etc/hotplug/usb.agent > ... no drivers for USB product 0/0/0 > hub.c: USB new device connect on bus1/2, assigned device number 2 > usb.c: new USB bus registered, assigned bus number 2 > Product: USB UHCI Root Hub > SerialNumber: cc00 > hub.c: USB hub found > hub.c: 2 ports detected > hub.c: USB hub found > hub.c: 4 ports detected > usb-uhci.c: v1.251:USB Universal Host Controller Interface driver > invoke /etc/hotplug/usb.agent > ... no drivers for USB product 0/0/0 > invoke /etc/hotplug/usb.agent > ... no drivers for USB product 451/2046/125 > hub.c: USB new device connect on bus1/2/3, assigned device number 3 > usb-uhci.c: interrupt, status 2, frame# 1017 > usb-uhci.c: interrupt, status 3, frame# 1018 > Manufacturer: KTG > Product: VideoCAM > usb.c: USB device 3 (vend/prod 0x47d/0x5003) is not claimed by any active > driver. > Length = 18 > DescriptorType = 01 > USB version = 1.00 > Vendor:Product = 047d:5003 > MaxPacketSize0 = 8 > NumConfigurations = 1 > Device version = 0.46 > Device Class:SubClass:Protocol = ff:00:00 > Vendor class > Configuration: > bLength = 9 > bDescriptorType = 02 > wTotalLength = 00ca > bNumInterfaces = 01 > bConfigurationValue = 01 > iConfiguration = 00 > bmAttributes = 80 > MaxPower = 500mA > > Interface: 0 > Alternate Setting: 0 > bLength = 9 > bDescriptorType = 04 > bInterfaceNumber = 00 > bAlternateSetting = 00 > bNumEndpoints = 02 > bInterface Class:SubClass:Protocol = 00:00:00 > iInterface = 00 > Endpoint: > bLength = 7 > bDescriptorType = 05 > bEndpointAddress = 81 (in) > bmAttributes = 02 (Bulk) > wMaxPacketSize = 0040 > bInterval = 00 > Endpoint: > bLength = 7 > bDescriptorType = 05 > bEndpointAddress = 82 (in) > bmAttributes = 01 (Isochronous) > wMaxPacketSize = 0040 > bInterval = 01 > Alternate Setting: 1 > bLength = 9 > bDescriptorType = 04 > bInterfaceNumber = 00 > bAlternateSetting = 01 > bNumEndpoints = 02 > bInterface Class:SubClass:Protocol = 00:00:00 > iInterface = 00 > Endpoint: > bLength = 7 > bDescriptorType = 05 > bEndpointAddress = 81 (in) > bmAttributes = 01 (Isochronous) > wMaxPacketSize = 0100 > bInterval = 01 > Endpoint: > bLength = 7 > bDescriptorType = 05 > bEndpointAddress = 82 (in) > bmAttributes = 01 (Isochronous) > wMaxPacketSize = 0040 > bInterval = 01 > Alternate Setting: 2 > bLength = 9 > bDescriptorType = 04 > invoke /etc/hotplug/usb.agent > bInterfaceNumber = 00 > bAlternateSetting = 02 > bNumEndpoints = 02 > bInterface Class:SubClass:Protocol = 00:00:00 > iInterface = 00 > Endpoint: > bLength = 7 > bDescriptorType = 05 > bEndpointAddress = 81 (in) > bmAttributes = 01 (Isochronous) > wMaxPacketSize = 0180 > bInterval = 01 > Endpoint: > bLength = 7 > bDescriptorType = 05 > bEndpointAddress = 82 (in) > bmAttributes = 01 (Isochronous) > wMaxPacketSize = 0040 > bInterval = 01 > Alternate Setting: 3 > bLength = 9 > bDescriptorType = 04 > bInterfaceNumber = 00 > bAlternateSetting = 03 > bNumEndpoints = 02 > bInterface Class:SubClass:Protocol = 00:00:00 > iInterface = 00 > Endpoint: > bLength = 7 > bDescriptorType = 05 > bEndpointAddress = 81 (in) > bmAttributes = 01 (Isochronous) > Modprobe and setup se401 for USB product 47d/5003/46 > wMaxPacketSize = 0200 > bInterval = 01 > Endpoint: > bLength = 7 > bDescriptorType = 05 > bEndpointAddress = 82 (in) > bmAttributes = 01 (Isochronous) > wMaxPacketSize = 0040 > bInterval = 01 > Alternate Setting: 4 > bLength = 9 > bDescriptorType = 04 > bInterfaceNumber = 00 > bAlternateSetting = 04 > bNumEndpoints = 02 > bInterface Class:SubClass:Protocol = 00:00:00 > iInterface = 00 > Endpoint: > bLength = 7 > bDescriptorType = 05 > bEndpointAddress = 81 (in) > bmAttributes = 01 (Isochronous) > wMaxPacketSize = 0280 > bInterval = 01 > Endpoint: > bLength = 7 > bDescriptorType = 05 > bEndpointAddress = 82 (in) > bmAttributes = 01 (Isochronous) > wMaxPacketSize = 0040 > bInterval = 01 > Alternate Setting: 5 > bLength = 9 > bDescriptorType = 04 > bInterfaceNumber = 00 > bAlternateSetting = 05 > bNumEndpoints = 02 > bInterface Class:SubClass:Protocol = 00:00:00 > iInterface = 00 > Endpoint: > bLength = 7 > bDescriptorType = 05 > bEndpointAddress = 81 (in) > bmAttributes = 01 (Isochronous) > wMaxPacketSize = 0300 > bInterval = 01 > Endpoint: > bLength = 7 > bDescriptorType = 05 > bEndpointAddress = 82 (in) > bmAttributes = 01 (Isochronous) > wMaxPacketSize = 0040 > bInterval = 01 > Alternate Setting: 6 > bLength = 9 > bDescriptorType = 04 > bInterfaceNumber = 00 > bAlternateSetting = 06 > bNumEndpoints = 02 > bInterface Class:SubClass:Protocol = 00:00:00 > iInterface = 00 > Endpoint: > bLength = 7 > bDescriptorType = 05 > bEndpointAddress = 81 (in) > bmAttributes = 01 (Isochronous) > wMaxPacketSize = 0380 > bInterval = 01 > Endpoint: > bLength = 7 > bDescriptorType = 05 > bEndpointAddress = 82 (in) > bmAttributes = 01 (Isochronous) > wMaxPacketSize = 0040 > bInterval = 01 > Alternate Setting: 7 > bLength = 9 > bDescriptorType = 04 > bInterfaceNumber = 00 > bAlternateSetting = 07 > bNumEndpoints = 02 > bInterface Class:SubClass:Protocol = 00:00:00 > iInterface = 00 > Endpoint: > bLength = 7 > bDescriptorType = 05 > bEndpointAddress = 81 (in) > bmAttributes = 01 (Isochronous) > wMaxPacketSize = 0400 > bInterval = 01 > Endpoint: > bLength = 7 > bDescriptorType = 05 > bEndpointAddress = 82 (in) > bmAttributes = 01 (Isochronous) > wMaxPacketSize = 0040 > bInterval = 01 > Alternate Setting: 8 > bLength = 9 > bDescriptorType = 04 > bInterfaceNumber = 00 > bAlternateSetting = 08 > bNumEndpoints = 00 > bInterface Class:SubClass:Protocol = 00:00:00 > iInterface = 00 > se401.c: SE401 usb camera driver version 0.23 registering > usb.c: registered new driver se401 > se401.c: SE401 camera found: Kensington VideoCAM 67016 > se401.c: firmware version: 46 > se401.c: ExtraFeatures: 0 Sizes: 160x120 200x152 176x144 320x240 352x288 > 400x300 640x480 704x576 800x600 > se401.c: registered new video device: video0 > > -- > MARK > [EMAIL PROTECTED] > > > --__--__-- > > Message: 6 > From: Shane Hickey <[EMAIL PROTECTED]> > Organization: How's your network? > To: [EMAIL PROTECTED] > Date: Tue, 23 Oct 2001 11:42:47 -0600 > Subject: [Linux-usb-users] Intel Easy PC Camera > > O.k. I know, with a name like Easy PC, that I'm prolly pressing my luck. > But I got this here camera from a friend and was wondering if I can set it up > under linux. I have a feeling that its guts are another type of camera, but > I don't know for sure. > > When I plug it into my hub, I get the following. > > Oct 23 11:26:43 devo kernel: hub.c: USB new device connect on bus1/2/1, > assigned device number 6 > Oct 23 11:26:43 devo kernel: usb.c: USB device 6 (vend/prod 0x8086/0x110) is > not claimed by any active driver. > > I searched the archives for the string 'vend/prod 0x8086/0x110' and got > nothing, so I apologize if this has been covered already. > > Thanks, > > Shane > > > --__--__-- > > Message: 7 > From: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > Date: Tue, 23 Oct 2001 10:50:06 -0700 > Subject: [Linux-usb-users] USB cable modem with ECM > > Hi, > > Can any one suggest a model of the cable modem which works with CDC ECM > driver > in linux (CDCEther.c). > > Regards, > Muni Reddy Anda > > > > > > > --__--__-- > > Message: 8 > Date: Tue, 23 Oct 2001 14:22:49 -0400 > From: ming deng <[EMAIL PROTECTED]> > Reply-To: [EMAIL PROTECTED] > Organization: www.oeone.com > To: [EMAIL PROTECTED] > Subject: [Linux-usb-users] Re: Getting assigned /dev/ttyUSB* device > > [EMAIL PROTECTED] wrote: > >> >> >>-- __--__-- >> >>Message: 5 >>Date: Sat, 20 Oct 2001 08:40:50 -0700 (PDT) >>From: Carlos Prados <[EMAIL PROTECTED]> >>To: [EMAIL PROTECTED] >>Subject: [Linux-usb-users] Getting assigned /dev/ttyUSB* device >> >>Hi, >> >>I'm writting a library that needs to open a >>/dev/ttyUSB[n] device when a USB serial smartcard >>reader is plugged. >> >>To do so there is a daemon (pcscd daemon from >>www.linuxnet.com) that polls /proc/bus/usb every few >>seconds and calls the library when a specific device >>is attached (mine is a PL2303). >> > Why I never seen /proc/bus/usb in my system? But the USB printer works > perfectly under kernel 2.4.9 and 2.4.12. > > thanks, > > Ming > > > > --__--__-- > > Message: 9 > Date: Tue, 23 Oct 2001 11:46:48 -0700 > From: Greg KH <[EMAIL PROTECTED]> > To: ming deng <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] > Subject: Re: [Linux-usb-users] Re: Getting assigned /dev/ttyUSB* device > > On Tue, Oct 23, 2001 at 02:22:49PM -0400, ming deng wrote: >> Why I never seen /proc/bus/usb in my system? But the USB printer works >> perfectly under kernel 2.4.9 and 2.4.12. > > See http://www.linux-usb.org/FAQ.html#gs3 > > > greg k-h > > > --__--__-- > > Message: 10 > Date: Tue, 23 Oct 2001 11:49:37 -0700 > From: Greg KH <[EMAIL PROTECTED]> > To: Tom Barnes-Lawrence <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] > Subject: Re: [Linux-usb-users] Aarrrgghh, **$#%* modem!!! > > On Tue, Oct 23, 2001 at 12:57:59AM +0100, Tom Barnes-Lawrence wrote: >> Using the ACM driver, it is not recognised, and it is listed as being the >> "Vendor-supplied driver" type, and uses (vend/prod 0x572/0x1232). I've >> looked at various sites, but not found much out. > > What is the output of /proc/bus/usb/devices with the device plugged in. > >> Now, I know that (most) software modems aren't supported under linux, BUT: >> Rockwell's chipsets for *serial* modems use the software drivers just to >> do data compression, and if you try to use them as plain serial modems, they >> then work fine, but without the data compression. > > If the manufacturer doesn't make their device to match the USB published > specs, then they are using a vendor specific protocol. You need to > either get that protocol from the vendor or reverse engineer it to get a > driver for Linux. > > thanks, > > greg k-h > > > > --__--__-- > > _______________________________________________ > [EMAIL PROTECTED] > To unsubscribe, use the last form field at: > https://lists.sourceforge.net/lists/listinfo/linux-usb-users > > > End of Linux-usb-users Digest
-- ---------------------------------- Linux: OS for the people by the people. E-Mail: Matt Aylward <[EMAIL PROTECTED]> Date: 24-Oct-2001 Time: 15:49:41 This message was sent by XFMail ---------------------------------- _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
