The device doesn't need special drivers (apparently it uses the mass storage device usb standard) and this is where I'm at now:
This is the output:
[root@localhost jason]# /sbin/lsmod
Module Size Used by Not tainted
sr_mod 15096 0 (autoclean) (unused)
floppy 49244 0 (autoclean)
ppp_deflate 3384 0 (autoclean)
zlib_inflate 18468 0 (autoclean) [ppp_deflate]
zlib_deflate 18392 0 (autoclean) [ppp_deflate]
bsd_comp 4312 0 (autoclean)
lp 6752 0
parport_pc 21736 1
parport 23808 1 [lp parport_pc]
ppp_async 7456 1
ppp_generic 20092 3 [ppp_deflate bsd_comp ppp_async]
slhc 5072 1 [ppp_generic]
af_packet 13000 0 (autoclean)
ip_vs 74424 0 (autoclean)
supermount 14308 2 (autoclean)
nls_iso8859-1 2844 2 (autoclean)
nls_cp850 3580 2 (autoclean)
vfat 9580 2 (autoclean)
fat 31864 0 (autoclean) [vfat]
ide-cd 28680 0
cdrom 27008 0 [sr_mod ide-cd]
ide-scsi 8276 0
sb 7636 1
sb_lib 34830 0 [sb]
uart401 6660 0 [sb_lib]
sound 55636 1 [sb_lib uart401]
soundcore 3684 0 [sb_lib sound]
usb-storage 66552 0
scsi_mod 91412 3 [sr_mod ide-scsi usb-storage]
usb-uhci 21804 0 (unused)
usbcore 58144 1 [usb-storage usb-uhci]
rtc 6524 0 (autoclean)
ext3 60076 6
jbd 38908 6 [ext3]
[root@localhost jason]#
I am also running the latest libusb and kernel from cooker.
**Jason banging head against wall**
Ideas??
Cheers
Jason
[EMAIL PROTECTED] wrote:
On Fri, 27 Dec 2002 13:52:10 +1300
Jason <[EMAIL PROTECTED]> wrote:
Now that sounds like what might be going on in my case. How did you doIf you have the driver modules for the device compiled, new hotplug
it?? Step by step please ;) I find it strange that usbview sees it but
the dynamic devfs entry is not created on plugin....
support and the correct modutils version all you have to do is
# depmod -a
Ehm... I have a self compiled linux sys using the new
hotplug scheme http://linux-hotplug.sourceforge.net/ I dunno what mdk
does about hotplugging (should be the same, tho) ... sorry ^^;
Cut&paste from Hotplug site:
Driver Information Database
In order for the hotplug policy agent to be able to figure out what
driver to load, it needs access to some kind of driver information
database. Different kinds of busses provide different kinds of
information, and need different driver selection algorithms.
Maintaining those databases can be a problem in its own right.
Linux delegates that problem to the driver developers, by persuading
them to keep MODULE_DEVICE_TABLE entries up to date. The "modutils"
package then exports that information in the form of text databases
(modules.usbmap, modules.pcimap, and so forth) where it
can be used to figure out what modules hold drivers for what devices. That same text database syntax is used for user mode drivers, using
files like usb.handmap associating shell scripts with devices
that had no kernel mode drivers.
(If you're coming to Linux with much MS-Win32 background,
you can think of that as analagous to the parts of the registry
used to map bus-specific device IDs to drivers.
One difference is that the IDs are part of the driver source and object
code, rather than a separate registry info file. The Linux approach is
simpler and less error prone.)
______________________________________________
So if you have the correct hotplug sys in place and it doesnt even try
to load the modules, one possibility is that the driver do not list your
device...
Anyway more important than usbview is the log of hotplug agent when you
plug in the device: it should say if it can find the device
definition or not etc...
Cheers
--
Delio
