[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: usb driver and probe function (is never called)



On Mon, Dec 24, 2001 at 04:32:08AM -0800, Erik Steffl wrote:
>   I realize that this is not strictly debian-devel question but it is
> related to both debian and development so while I don't expect big
> discussion I would appreciate RT _specify_which_one_ FM.

The appropriate list for USB problems is
linux-usb-users@lists.sourceforge.net . You need to have the hotplug
package installed for proper USB support.

>   so far I have read the relevant parts of Linux device drivers, 2nd
> edition (O'Reilly), the info about usb in linux/Documentation, parts of
> some other linux kernel & setup books.
> 
>   I am trying to make the USB work on my debian unstable system, using
> kernel 2.4.14 and it just doesn't work. the specific problem is that the
> function 'probe' (specified when registering driver) is NEVER called and
> therefore driver doesn't manage any usb devices. as far as I can tell
> the system is set up correctly, see below for modules, kernel settings
> etc.

Please try 2.4.17, there have been quite some USB updates in 2.4.15 and
2.4.17.

>   so far I have tried the sample usb driver from linux device driver,
> 2nd edition (o'reilly) and personal jukebox (www.pjbox.com) drivers,
> both behave in exactly the same way - I get a message in syslog that the
> driver was registered and that's it, the message from probe function is
> never printed and the driver doesn't work (cat says No such device)

Try a device with a known-good driver first. A mouse, for example.

> ------------------------------------------------------------
>   settings & messages
> ------------------------------------------------------------
> 
>   here are my kernel config settings related to usb:
> 
> jojda:/usr/src/linux# grep -i usb ./.config | grep -v '^#'
> CONFIG_USB=m
> CONFIG_USB_DEBUG=y
> CONFIG_USB_DEVICEFS=y
> CONFIG_USB_UHCI=m

Also select "CONFIG_USB_UHCI_ALT=m". Quite a lot of USB problems with
UHCI hardware can be solved by using "the other" UHCI driver.


Erik

-- 
J.A.K. (Erik) Mouw, Information and Communication Theory Group, Faculty
of Information Technology and Systems, Delft University of Technology,
PO BOX 5031, 2600 GA Delft, The Netherlands  Phone: +31-15-2783635
Fax: +31-15-2781843  Email: J.A.K.Mouw@its.tudelft.nl
WWW: http://www-ict.its.tudelft.nl/~erik/



Reply to: