[ILUG] Tech help needed - udev problem

[Tony Groves]

On Thu, March 27, 2008 10:25 am, Tony Groves wrote:
>> After switching over from hotplug to udev, I now find that my system is
>> not recognising USB storage devices that I connect. Whenever I connect
>> a (any) USB memory stick, dmesg logs the message "new high speed USB
>> device using address x", and stops there instead of proceeding to
>> recognise the device.
>>
>> I'm using Debian Etch AMD64; udev 0.105-4, kernel 2.6.18-6.
>
> On Thu, 2008-03-27 at 14:41 +0000, David Howe wrote:
>> Do you get anything from the lsusb command?
>
> On Fri, Mar 28, 2008 at 11:36 AM, Tony Groves <tongro at eircom.net> wrote:
>
>> Here's the lsusb output after a USB stick has been plugged in:
>> Bus 005 Device 005: ID 08ec:2038 M-Systems Flash Disk Pioneers
>> Bus 005 Device 001: ID 0000:0000
>> Bus 004 Device 001: ID 0000:0000
>> Bus 003 Device 001: ID 0000:0000
>> Bus 002 Device 001: ID 0000:0000
>> Bus 001 Device 001: ID 0000:0000
>>
>> It's something similar for other devices/sockets.
>
> On Fri, 2008-03-28 at 16:08 +0000, Conor Wynne wrote:
>> Make a rule in /etc/udev/rules.d/75-usbkey.rules
>> (or whatever the location is under debian)... dont use deb any more...
>> or *buntu ...
>>
>> I suppose something like this :
>>
>> First of all, determine what the device is using 'dmesg'
>> Then determine what the serial number of said device is with -- I'll
>> assume /dev/sda for this example:
>>
>> # udevinfo -a -p $(udevinfo -q path -n /dev/sda) |grep -i serial
>> let's say its xyz123, and the user will be 'tonyg' in the group
>> 'users'
>>
>> # vi /etc/udev/rules.d/75.usbkey.rules
>>
>> KERNEL=="sd*", DRIVER=="usb-storage" \
>> SYSFS{serial}=="xyz123", \
>> SYMLINK+="M-Systems Flash Disk Pioneers", OWNER="tonyg",
>> GROUP="users", \
>> MODE="0600"
>>
>> Don't remember if you need to re-spawn any daemons, think its
>> dynamic... suck am and see....
>
> On Fri, 2008-03-28 at 19:52 +0000, Tony Groves wrote:
>> Thanks for that. I don't think it's a matter of udev configuration, as
>> the device never gets assigned to a node in the first place. dmesg logs
>> the message "new high speed USB device using address x", and stops there
>> instead of proceeding to recognise the device.
>
> On Sat, 2008-03-29 at 14:25 +0000, Conor Wynne wrote:
>> Your usbkey could be bollixed. Does it work under windows/other
>> linux/whatever OS
>
> It happens with any USB device on any socket on that machine, since I
> swapped hotplug for udev. My home Debian machine (i386), on which I'm
> scribing this missive, has no such problems.
>
> From: Brian Foster <blf at utvinternet.ie>
>>  I found that udevmonitor(8 ?), in addition to David's
>>  lsusb(8) suggestion, along with some good old sit down
>>  and RFTM, plus a few carefully considered experiments,
>>  greatly assisted in tracking down the problem.
>>  (the problem I had is not the problem you report,
>>  so I've no idea what is going on in yer case.)
>
> I tried udevmonitor, but it produces no output at all when a USB device
> is plugged in or out. In my novice mind, it looks like the kernel is not
> giving udev a chance to get involved at all. Could I be missing some
> kernel module? I've already RTFM and STFW and MTFILUG, but still no
> closer to solving it.
>
On Wed, 2008-04-09 at 11:23 +0100, David Howe wrote:
> I had similar problems with Ubuntu 7.10 and udev. In my case the USB
> controller was from Intel. I installed a VIA PCI USB 2.0 card and this
> fixed the problem (€20 approx for the card).

David, Thanks for the reply. It turns out I was missing the usb_storage
kernel module. I loaded that and now the devices are being detected. My
udev rules still aren't being applied, but that's another story which I
haven't seriously investigated yet.

Tony.