SOLVED Re: dmesg reports connection of mass storage device but no kde pop-up nor device file created

Florian Kulzer wrote, on 2008-04-01 04:39:
On Mon, Mar 31, 2008 at 23:08:32 +1030, Arthur Marsh wrote:
I plugged in a USB mass storage device into my pc running Debian Unstable and unlike several months ago, did not get a notification from KDE that the device had been discovered.

Did you choose a default action for that type of device when the
notification first appeared? AFAIK, KDE will not pop up the notification
again once the user has selected a default action (and this default
action can be "do nothing").

dmesg reported:

usb 2-2: new full speed USB device using ohci_hcd and address 4
usb 2-2: configuration #1 chosen from 1 choice
usb 2-2: New USB device found, idVendor=0944, idProduct=0001
usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 2-2: Product: PXR4
usb 2-2: Manufacturer: KORG INC.

Is that the complete output? It seems that no device node(s) was/were
created.

Is any customisation needed for udev / HAL to create a device file when this device is discovered? I'd like it to auto-mount as /mnt/usbdrive

Normally this should "just work". I run KDE on Sid/amd64 and I have not
noticed a problem with this in ages; I don't have the same storage
device, though. Can you post the output that you get when you run

lshal --monitor

and plug in the device? (CTRL-C to stop, but wait for at least 10
seconds after you plug in the device.)


dmesg reported:

usb 2-2: new full speed USB device using ohci_hcd and address 5
usb 2-2: configuration #1 chosen from 1 choice
usb 2-2: New USB device found, idVendor=0944, idProduct=0001
usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 2-2: Product: PXR4
usb 2-2: Manufacturer: KORG INC.

but nothing was reported:

lshal --monitor

Start monitoring devicelist:
-------------------------------------------------
^C

Looking further, I found the package hal-device-manager still installed but aptitude was unable to find it in current unstable/testing/stable archives. I marked it as automatic, and aptitude marked it for deletion. I then marked it for purging and also reinstalled hal and hal-info, but the USB device was still not detected by lshal --monitor.

I then restarted the machine and saw the following when I added and removed the USB device:

Start monitoring devicelist:
-------------------------------------------------
19:27:45.987: usb_device_944_1_noserial added
19:27:51.736: usb_device_944_1_noserial_if0 added
19:27:51.813: usb_device_944_1_noserial_usbraw added
19:27:56.732: usb_device_944_1_noserial_if0_scsi_host added
19:27:56.804: usb_device_944_1_noserial_if0_scsi_host_scsi_device_lun0 added
19:27:58.536: storage_serial_KORG_PXR4_R_W_0_0 added
19:27:58.543: storage_serial_KORG_PXR4_R_W_0_0 property info.interfaces = {'org.freedesktop.Hal.Device.Storage.Removable'} (new)
19:27:59.638: volume_part1_size_131047936 added
19:29:15.131: volume_part1_size_131047936 property volume.mount_point = '/mnt/usbdrive'
19:29:15.142: volume_part1_size_131047936 property volume.is_mounted = true
19:29:29.865: volume_part1_size_131047936 property volume.mount_point = ''
19:29:30.133: volume_part1_size_131047936 property volume.is_mounted = false
19:29:52.218: storage_serial_KORG_PXR4_R_W_0_0 removed
19:29:52.219: usb_device_944_1_noserial_if0_scsi_host_scsi_device_lun0 removed
19:29:52.219: usb_device_944_1_noserial_if0_scsi_host removed
19:29:52.219: volume_part1_size_131047936 removed
19:29:52.219: usb_device_944_1_noserial_if0 removed
19:29:52.219: usb_device_944_1_noserial_usbraw removed

KDE also detected the drive and my old /etc/fstab entry for it worked (all on one line):

/dev/sda1 /mnt/usbdrive vfat defaults,uid=65534,gid=65534,umask=000,iocharset=utf8 0 0


If one shouldn't need to restart debian for the purging of hal-device-manager to take effect, should I have run /etc/init.d/hal restart ?

Thanks very much for your help!

Arthur.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx

Relevant Pages

  • Re: dmesg reports connection of mass storage device but no kde pop-up nor device file created
    ... I plugged in a USB mass storage device into my pc running Debian ... Unstable and unlike several months ago, did not get a notification from ... KDE that the device had been discovered. ...
    (Debian-User)
  • USB RNDIS and no Device Notifications
    ... Notification queue to "listen to" all the devices that get plugged/ ... removed from the machine, it's working great for USB printers, USB / ... receive any notification in my listening queue. ... usual notifications system when creating the network interface. ...
    (microsoft.public.windowsce.platbuilder)
  • RE: USB Device Interface
    ... I also need other's help on this because i dont have all kinds of USB flash ... 1> monitor for registry changes under the registry key: ... or ur service app will have DBT_DEVICEARRIVAL notification. ... to produce the drive letter assignment. ...
    (microsoft.public.development.device.drivers)
  • Re: USB Device Interface
    ... is absolutely no reason to play with the registry. ... I also need other's help on this because i dont have all kinds of USB flash storage device to test my service application. ... or ur service app will have DBT_DEVICEARRIVAL notification. ... to produce the drive letter assignment. ...
    (microsoft.public.development.device.drivers)
  • STRANGE NOTIFICATION
    ... have a wireless network adapter plugged into my 1st USB ... a notification appears on my taskbar next to the ... USB port. ...
    (microsoft.public.windowsxp.hardware)