Oh well! I commented out the "goto fail_and_release" statement, but I still
have no drivers. The dmesg, lsusb, and usbdevices files are attached.
I appreciate the effort and know the source of the problem.
Thanks again,
Mark
On Fri, Apr 20, 2007 at 09:29:59AM -0700, David Brownell wrote:
> On
On Friday 20 April 2007 8:46 am, Mark Glassberg wrote:
> Applied the patch. It looks like we took a step back. The latest dmesg,
> lsusb, and usbdevices files are attached. I thought you might want to see
> them
Good to see those ... those are expected results, other than the timeouts
one time
Applied the patch. It looks like we took a step back. The latest dmesg,
lsusb, and usbdevices files are attached. I thought you might want to see
them before I comment out the "goto fail_and_release" statement. Just let
me know if you want to see the results of that change.
Thanks again,
Mark
On Thursday 19 April 2007 10:48 am, David Brownell wrote:
> But after Oliver's hack, there was still:
>
> > rndis_host 3-1:1.0: dev can't take 1558 byte packets (max 0)
>
> And that means something else: the device took the RNDIS
> initialization request, but didn't return a sane response.
> So
On Thursday 19 April 2007 5:07 am, Mark Glassberg wrote:
> rndis_host 3-1:1.0: usb_probe_interface
> rndis_host 3-1:1.0: usb_probe_interface - got id
> rndis_host 3-1:1.0: missing cdc header union ether descriptor
> usb 3-1: bad CDC descriptors
One issue is that the CDC descriptors are in the wron
Your cdc_ether.c certainly helped. I am attaching the latest dmesg,
lsusb, and usbdevices files. Unfortunately, as you can see from the
latter file, I only have a driver for the comm side of the device, but
none for the data side.
As always, any assistance would be most welcome.
Thanks again,
Ma
Am Donnerstag, 19. April 2007 15:28 schrieb Mark Glassberg:
> I did EXACTLY as instructed. The compilation ended with this:
> make[3]: *** [drivers/usb/net/cdc_ether.o] Error 1
> make[2]: *** [drivers/usb/net] Error 2
> make[1]: *** [drivers/usb] Error 2
> make: *** [drivers] Error 2
>
> My modif
I did EXACTLY as instructed. The compilation ended with this:
make[3]: *** [drivers/usb/net/cdc_ether.o] Error 1
make[2]: *** [drivers/usb/net] Error 2
make[1]: *** [drivers/usb] Error 2
make: *** [drivers] Error 2
My modified cdc_ether.c is attached.
Sorry,
Mark
On Thu, Apr 19, 2007 at 02:51:1
Am Donnerstag, 19. April 2007 14:07 schrieb Mark Glassberg:
> I installed a 2.6.21-rc7 kernel with USB_DEBUG=y and USB_NET_RNDIS_HOST=y.
> Unfortunately, my dsl modem/router is not yet installed. Attached are the
> dmesg output, the detailed lsusb output, and the related section of the
> /proc/bus
I installed a 2.6.21-rc7 kernel with USB_DEBUG=y and USB_NET_RNDIS_HOST=y.
Unfortunately, my dsl modem/router is not yet installed. Attached are the
dmesg output, the detailed lsusb output, and the related section of the
/proc/bus/usb/devices file. The latter shows no driver for the device,
but d
On Tue, 17 Apr 2007, Mark Glassberg wrote:
> On Tue, Apr 17, 2007 at 12:56:51PM -0400, Alan Stern wrote:
> > There was a fairly recent change in this area of choose_configuration(),
> > having to do with whether or not RNDIS support is present in a module vs.
> > built-in. Mark should try using
Am Dienstag, 17. April 2007 20:21 schrieb Mark Glassberg:
> On Tue, Apr 17, 2007 at 06:13:24PM +0200, Oliver Neukum wrote:
> > OK. Please run two tests.
> >
> > #1 - try the attached patch
> > #2 - compile USB_NET_RNDIS_HOST statically into your kernel
>
> Sorry, but I have two problems. First
On Tue, Apr 17, 2007 at 12:56:51PM -0400, Alan Stern wrote:
> There was a fairly recent change in this area of choose_configuration(),
> having to do with whether or not RNDIS support is present in a module vs.
> built-in. Mark should try using 2.6.21-rc if he isn't using it already.
I'm runnin
On Tuesday 17 April 2007 8:31 am, Oliver Neukum wrote:
> Am Dienstag, 17. April 2007 17:18 schrieb Mark Glassberg:
> > usb 3-1: new full speed USB device using uhci_hcd and address 2
> > usb 3-1: ep0 maxpacket = 8
> > usb 3-1: skipped 4 descriptors after endpoint
> > usb 3-1: default language 0x040
On Tue, Apr 17, 2007 at 06:13:24PM +0200, Oliver Neukum wrote:
> OK. Please run two tests.
>
> #1 - try the attached patch
> #2 - compile USB_NET_RNDIS_HOST statically into your kernel
Sorry, but I have two problems. First the patch seems to for the 2.6.21-rc7
kernel and I'm running 2.6.17.13.
On Tue, Apr 17, 2007 at 05:31:25PM +0200, Oliver Neukum wrote:
> Am Dienstag, 17. April 2007 17:18 schrieb Mark Glassberg:
> > usb 3-1: new full speed USB device using uhci_hcd and address 2
> > usb 3-1: ep0 maxpacket = 8
> > usb 3-1: skipped 4 descriptors after endpoint
> > usb 3-1: default langua
On Tue, 17 Apr 2007, Oliver Neukum wrote:
> Am Dienstag, 17. April 2007 17:18 schrieb Mark Glassberg:
> > usb 3-1: new full speed USB device using uhci_hcd and address 2
> > usb 3-1: ep0 maxpacket = 8
> > usb 3-1: skipped 4 descriptors after endpoint
> > usb 3-1: default language 0x0409
> > usb 3-
Am Dienstag, 17. April 2007 17:50 schrieb Mark Glassberg:
> On Tue, Apr 17, 2007 at 05:31:25PM +0200, Oliver Neukum wrote:
> > Am Dienstag, 17. April 2007 17:18 schrieb Mark Glassberg:
> > > usb 3-1: new full speed USB device using uhci_hcd and address 2
> > > usb 3-1: ep0 maxpacket = 8
> > > usb 3
Am Dienstag, 17. April 2007 17:18 schrieb Mark Glassberg:
> usb 3-1: new full speed USB device using uhci_hcd and address 2
> usb 3-1: ep0 maxpacket = 8
> usb 3-1: skipped 4 descriptors after endpoint
> usb 3-1: default language 0x0409
> usb 3-1: new device strings: Mfr=1, Product=2, SerialNumber=0
Am Dienstag, 17. April 2007 15:15 schrieb Mark Glassberg:
> usb 3-1: new full speed USB device using uhci_hcd and address 2
> usb 3-1: ep0 maxpacket = 8
> usb 3-1: skipped 4 descriptors after endpoint
> usb 3-1: default language 0x0409
> usb 3-1: new device strings: Mfr=1, Product=2, SerialNumber=0
On Tue, Apr 17, 2007 at 04:39:05PM +0200, Oliver Neukum wrote:
> Am Dienstag, 17. April 2007 15:15 schrieb Mark Glassberg:
> > usb 3-1: new full speed USB device using uhci_hcd and address 2
> > usb 3-1: ep0 maxpacket = 8
> > usb 3-1: skipped 4 descriptors after endpoint
> > usb 3-1: default langua
On Sat, 3 Feb 2007, Pete Zaitcev wrote:
> On Sat, 3 Feb 2007 11:43:50 -0500 (EST), Alan Stern <[EMAIL PROTECTED]> wrote:
>
> > Here's an idea for an improvement to the text interface in usbmon which
> > should be easy to implement. I'd like to know for certain when and where
> > events are missi
On Sat, 3 Feb 2007 11:43:50 -0500 (EST), Alan Stern <[EMAIL PROTECTED]> wrote:
> Here's an idea for an improvement to the text interface in usbmon which
> should be easy to implement. I'd like to know for certain when and where
> events are missing from the log. Something as simple as a line con
Am Mittwoch, 31. Januar 2007 20:35 schrieb Alan Stern:
> On Wed, 31 Jan 2007, Oliver Neukum wrote:
>
> > > > + if (sdkp->capacity % 63 || sdkp->capacity % 255)
> > > > + --sdkp->capacity;
> > >
> > > This is a strange computation. You avoid decrementing the ca
On Wed, 31 Jan 2007, Oliver Neukum wrote:
> > > + if (sdkp->capacity % 63 || sdkp->capacity % 255)
> > > + --sdkp->capacity;
> >
> > This is a strange computation. You avoid decrementing the capacity iff it
> > is already divisible both by 63 and by 255. Maybe you really
Am Mittwoch, 31. Januar 2007 17:22 schrieb Alan Stern:
> On Wed, 31 Jan 2007, Oliver Neukum wrote:
> If some other device ends up needing this in the future, what makes you
> think the heuristic you have chosen will be appropriate?
I've checked my disks and asked for counterexamples.
If you have
On Wed, 31 Jan 2007, Oliver Neukum wrote:
> Hi,
>
> could you please test this with your storage device. It tries to implement
> a heuristics which will work with both versions of the firmware.
>
> Regards
> Oliver
If some other device ends up needing this in the future, wha
On Thursday 19 May 2005 9:22 pm, [EMAIL PROTECTED] wrote:
> From: David Brownell [mailto:[EMAIL PROTECTED]
> Sent: Thursday, May 19, 2005 10:25 AM
> To: Borse, Ganesh
>
> > how is it shown in sysfs? In any file?
>
> >>The current device configuration is bConfigurationValue,
> >>matching the USB s
On Thu, May 19, 2005 at 11:22:20PM -0500, [EMAIL PROTECTED] wrote:
> From: David Brownell [mailto:[EMAIL PROTECTED]
> Sent: Thursday, May 19, 2005 10:25 AM
> To: Borse, Ganesh
>
> > how is it shown in sysfs? In any file?
>
> >>The current device configuration is bConfigurationValue,
> >>matching
From: David Brownell [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 19, 2005 10:25 AM
To: Borse, Ganesh
> how is it shown in sysfs? In any file?
>>The current device configuration is bConfigurationValue,
>>matching the USB spec.
No, bConfigurationValue does not give any information about overcurr
On Wednesday 18 May 2005 9:21 pm, [EMAIL PROTECTED] wrote:
> -Original Message-
> From: David Brownell [mailto:[EMAIL PROTECTED]
> Sent: Thursday, May 19, 2005 9:40 AM
> To: [email protected]
> Cc: Borse, Ganesh; [EMAIL PROTECTED]; [EMAIL PROTECTED]
>
> >>in the USB spe
-Original Message-
From: David Brownell [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 19, 2005 9:40 AM
To: [email protected]
Cc: Borse, Ganesh; [EMAIL PROTECTED]; [EMAIL PROTECTED]
>>in the USB spec and the current device configuration as
>>shown in sysfs ... except for
On Wednesday 18 May 2005 8:42 pm, [EMAIL PROTECTED] wrote:
> What I would like to know is: which IOCTL, system call, /proc or /sysfs
> file can provide me the information that certain USB device is causing
> overcurrent condition on an external hub?
Have a look at how "lsusb" fetches port status
-Original Message-
From: Alan Stern [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 18, 2005 7:36 PM
To: Borse, Ganesh
>>If you want to get the information that's in /var/log/messages all you
>>need to do is open /var/log/messages and read the contents of the
file.
>>Various pieces of tha
On Tue, 17 May 2005 [EMAIL PROTECTED] wrote:
> Dear sir,
> I am a developer working on Red Hat Linux with kernels 2.6 and 2.4.
> I am connecting a bus-powered USB 4-port hub with USB floppy (connected on
> this USB external hub) onto USB Root hub.
>
> I found that /var/log/messages file contains
On Wed, Mar 23, 2005 at 03:23:37PM -0800, mohamed rafi wrote:
> Hi,
>
> I have recently bought a M-S Cash Drawer, the new one
> which is a HID Device. It has drivers available for
> Windows only, and not for Linux.
I suggest you ask your vendor for those drivers :)
> Using a USB Transport Analy
On Sat, 4 Dec 2004, Gerd v. Egidy wrote:
> Sorry for the dumb question, but what does that mean for the non
> usb-professional? Will it really spin down my disk or just put the usb
> connection to it in suspend mode?
It only puts the USB connection into suspend mode. If your drive decides
that
> > Cool! I'll have to take a look soon. (And at the hub autosuspend
> > patch too...) It's bigger than I'd have expected. Care to sketch
> > what those three patches do?
>
> It's a little bigger than it needs to be, because I took the opportunity
> to reorder the #include lines in bunch of sou
On Thu, 2 Dec 2004, David Brownell wrote:
> On Thursday 02 December 2004 9:22 am, Alan Stern wrote:
> > Below is a composite of three patches pending for the usb-storage driver.
> > Together they provide support for autosuspend. The inactivity timeout is
> > controlled by a module parameter na
On Thursday 02 December 2004 9:22 am, Alan Stern wrote:
> Below is a composite of three patches pending for the usb-storage driver.
> Together they provide support for autosuspend. The inactivity timeout is
> controlled by a module parameter named "autosuspend"; its value gives the
> timeout i
On Thu, Sep 02, 2004 at 08:43:23PM +0200, Hermann Kneissel wrote:
>
> The current version of my driver to connect a garmin gps receiver
> is available here:
>
> http://cvs.sourceforge.net/viewcvs.py/garmin-gps/kernel/garmin_gps.c
>
> can someone review it and tell, if there are obvious problems
Dave, Alan,
actually in the BIOS there's no way to change anything related to USB.
Therefore I don't know if it's the BIOS to blame or not.
However, we leave it as it is. Nobody else has ever reported any problem
like this, I suspect. Seem to be my personal prob with my ACER aspire
1350. It's
Alan Stern wrote:
On Sat, 7 Feb 2004, Bernd Porr wrote:
If I only load the UHCI driver all external devices get no power at all
(measured with a meter).
To get power to the external bus I have to first load both drivers: ehci
and uhci. When I remove the ehci driver the power is still on.
I di
On Sat, 7 Feb 2004, Guennadi Liakhovetski wrote:
> On Fri, 6 Feb 2004, Alan Stern wrote:
>
> > Can someone who has a VIA-based UHCI controller please try out this patch
> > and let us know if anything goes wrong?
>
> Noticed nothing wrong. Should I have noticed any difference? lspci -v
> reports
On Sat, 7 Feb 2004, Bernd Porr wrote:
> Hi Alan,
>
> let's say: it works with VIA as bad as before. ;-) The UHCI driver
> itself works -- if the ehci driver is/was loaded (before).
That's good to hear.
> If I only load the UHCI driver all external devices get no power at all
> (measured with
Hi Alan,
let's say: it works with VIA as bad as before. ;-) The UHCI driver
itself works -- if the ehci driver is/was loaded (before).
If I only load the UHCI driver all external devices get no power at all
(measured with a meter).
To get power to the external bus I have to first load both dri
On Fri, 6 Feb 2004, Alan Stern wrote:
> Can someone who has a VIA-based UHCI controller please try out this patch
> and let us know if anything goes wrong?
Noticed nothing wrong. Should I have noticed any difference? lspci -v
reports exactly the same information. Or where is the over-current
prot
On Wed, Dec 11, 2002 at 01:34:58PM -0700, Douglas Roberts wrote:
> Yes, they would have needed the spec to build the device. There is may
> be some kind of power play going on between the Chinese manufacturer of
> the device, and the American company who wants to supply us with the
> device. T
Yes, they would have needed the spec to build the device. There is may
be some kind of power play going on between the Chinese manufacturer of
the device, and the American company who wants to supply us with the
device. The Chinese perhaps see some kind of risk (lost software driver
developme
Quick question. How did they built the device? They would have to
understand the specs?
Dwaine.
Douglas Roberts
<[EMAIL PROTECTED]>
50 matches
Mail list logo
