Date: Wed, 5 Nov 2008 11:13:41 -0500 (EST)
From: Alan Stern <stern@rowland.harvard.edu>
To: Norbert Preining <preining@logic.at>
cc: Mattia Dongili <malattia@linux.it>,
       Kernel development list <linux-kernel@vger.kernel.org>,
       USB list <linux-usb@vger.kernel.org>
Subject: Re: usb device not showing up
In-Reply-To: <20081104215829.GA2880@gamma.logic.tuwien.ac.at>
Message-ID: <Pine.LNX.4.44L0.0811051102010.2573-100000@iolanthe.rowland.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1300
Lines: 33

On Tue, 4 Nov 2008, Norbert Preining wrote:

> On Di, 04 Nov 2008, Alan Stern wrote:
> > > > If you can't boot with the modem off, then try this instead: Unload 
> > > > ehci-hcd, uhci-hcd, and ohci-hcd, then start up usbmon (copy the 0u 
> > > > file) and reload whichever driver the modem attaches to.
> 
> Ok, here it is. Booted with init=/bin/bash, no modules loaded, mounted
> /sys and debugfs, cat u0 > usbmon.txt. Then load uhci-hcd, then load hso
> modules.
> 
> Finally, kill the cat process.
> 
> Output is the attached usmon.txt file. 

Well, this is a little odd.  The trace shows the modem was detected and
enumerated correctly.  But there's nothing corresponding to when you
loaded the hso driver.  In fact, there's nothing after uhci-hcd 
finished starting up and the unconnected root hubs were suspended.

Did you look in /proc/bus/usb/devices at this point?  And what about
the files in /sys/bus/usb/drivers/hso/?

This suggests the problem may lie in the hso driver itself, or in a
failure to bind the driver to the device.

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/