Re: usb flash drive problem - module problem?
I am having a similar problem ..
tail -f /var/log/syslog shows this when I insert a flash card,
or plug in the reader:
===============
May 23 01:23:54 spiff kernel: hub.c: USB new device connect on
bus1/1, assigned device number 6
May 23 01:23:54 spiff kernel: usb-storage: act_altsettting is 0
May 23 01:23:54 spiff kernel: usb-storage: id_index calculated
to be: 81
May 23 01:23:54 spiff kernel: usb-storage: Array length appears
to be: 83
May 23 01:23:54 spiff kernel: usb-storage: USB Mass Storage
device detected
May 23 01:23:54 spiff kernel: usb-storage: Endpoints: In:
0xcfc51da0 Out: 0xcfc51db4 Int: 0x00000000 (Period 0)
May 23 01:23:54 spiff kernel: usb-storage: Found existing GUID
05dcb0020000000000000000
May 23 01:23:54 spiff kernel: WARNING: USB Mass Storage data
integrity not assured
May 23 01:23:54 spiff kernel: USB Mass Storage device found at 6
May 23 01:23:55 spiff /etc/hotplug/usb.agent: Setup usb-storage
for USB product 5dc/b002/113
May 23 01:23:55 spiff /etc/hotplug/usb.agent: missing kernel or
user mode driver usb-storage
==================
I think the last line "missing kernel ... " is significant.
cat /proc/modules shows ....
=================
serial_cs 5440 0 (unused)
pcnet_cs 12708 1
8390 5888 0 [pcnet_cs]
ds 6624 2 [serial_cs pcnet_cs]
i82365 22416 2
pcmcia_core 41408 0 [serial_cs pcnet_cs ds i82365]
apm 9148 2 (autoclean)
maestro 27456 0 (unused)
soundcore 3236 2 [maestro]
usb-storage 97152 0
ide-scsi 7488 0
keybdev 1664 0 (unused)
usbkbd 2848 0 (unused)
input 3072 0 [keybdev usbkbd]
usb-uhci 20708 0 (unused)
usbcore 48032 1 [usb-storage usbkbd usb-uhci]
====================
I see that usb-storage is there ....
cat /proc/devices shows ....
===============
(Character devices omitted)
Block devices:
1 ramdisk
2 fd
3 ide0
7 loop
11 sr
22 ide1
114 ataraid
===============
Note that there isn't a #8.
I think this is the problem, but how do I change it?
The system is a laptop, running woody, 2.4.18-bf2.4
It works with Knoppix (2.4.20-xfs)
I have another system, a desktop running sid 2.4.20-bf2.4 , that
works. As I recall, it just worked, with the same reader.
Reply to: