Memory stick volume does not appear in file manager

parmenide · 10-09-2008, 07:24 AM

After an upgrade from kde 3.5 to kde 4.1, I have the following problem:
when I plug in a memory stick, the volume of the memory stick does not appear in Dolphin or Konqueror as before. I have a laptop wit debian etch/lenny and kernel 2.6.22.
When I insert the stick, /var/log/messages gives the following:

Code:

Oct  9 13:02:58 parmenide kernel: [13336.988000] usb 4-2: new high speed USB device using ehci_hcd and address 5
Oct  9 13:02:58 parmenide kernel: [13337.120000] usb 4-2: configuration #1 chosen from 1 choice
Oct  9 13:02:58 parmenide kernel: [13337.120000] scsi7 : SCSI emulation for USB Mass Storage devices
Oct  9 13:03:03 parmenide kernel: [13342.120000] scsi 7:0:0:0: Direct-Access     S3+                       0.00 PQ: 0 ANSI: 2
Oct  9 13:03:03 parmenide kernel: [13342.124000] sd 7:0:0:0: [sdb] 4030463 512-byte hardware sectors (2064 MB)
Oct  9 13:03:03 parmenide kernel: [13342.124000] sd 7:0:0:0: [sdb] Write Protect is off
Oct  9 13:03:03 parmenide kernel: [13342.128000] sd 7:0:0:0: [sdb] 4030463 512-byte hardware sectors (2064 MB)
Oct  9 13:03:03 parmenide kernel: [13342.128000] sd 7:0:0:0: [sdb] Write Protect is off
Oct  9 13:03:03 parmenide kernel: [13342.128000]  sdb: sdb1
Oct  9 13:03:03 parmenide kernel: [13342.236000] sd 7:0:0:0: [sdb] Attached SCSI removable disk
Oct  9 13:03:03 parmenide kernel: [13342.236000] sd 7:0:0:0: Attached scsi generic sg1 type 0

Of course, I have no problem to manually mount the volume, but I would like it automatically appearing in the file manager.
The funny thing is that I can actually get the volume appear in the file manager by unloading and then reloading the module usb_storage: indeed, the only way I have to get the volume in the file manager is to do the following steps:
1) insert the stick;
2) rmmod usb_storage;
3) modprobe usb_storage.
I cannot figure out what exact package handle this stuff. I do not have hotplug as it is no longer included in the last version of debian. Of course I have both udevd and hald installed.
Any help?

jschiwal · 10-09-2008, 08:59 AM

A quick thing to check is that you don't use the "noacpi" kernel boot option. These will prevent hald and dbusd from running. There is a service that runs in kde that hald signals when a device is inserted. I'm sorry but I can't remember which it is or the gnome helper program is.

Are the udevd, dbusd and hald daemons running?

Look at lsmod. I'm wondering if you have both the ohci and uhci kernel modules loaded. If so, one or the other may be a mistake. Which one you want depends on the vendor of your controller chip.

Code:

lsmod | grep usb
usb_storage           112928  1
usbhid                 65488  0
hid                    59296  1 usbhid
ff_memless             23176  1 usbhid
usbcore               188376  7 usb_storage,uvcvideo,usbhid,ehci_hcd,uhci_hcd
scsi_mod              195032  5 usb_storage,sr_mod,sg,sd_mod,libata

Does /dev/sdb exist? How about /dev/sdb1?

If the pendrive doesn't have a label, try the generic disk name with:
halmount /media/disk

or try:
halmount /dev/sdb1

Look at:
udevinfo -q env -n /dev/sdb1

Hal may be configured to ignore devices if they exist in /etc/fstab. Is there an entry for /dev/sdb1 in /etc/fstab?

Before inserting the pendrive, run:
lshal -m

parmenide · 10-09-2008, 09:59 AM

First of all, thank you very much for your help. I try to respond to all of your questions.

1) I do not have the "noacpi" kernel boot option.
2) yes, udevd, dbusd and hald daemons are running:

Code:

parmenide:/home/na# ps ux|grep dbus
root      4005  0.0  0.0   2476   472 ?        Ss   16:33   0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
root      4041  0.0  0.0   3024   740 pts/2    R+   16:37   0:00 grep dbus
root      4910  0.0  0.0   2960   676 ?        S    15:55   0:00 dbus-launch --autolaunch cc503d390be2876e07e2960046e5b98f --binary-syntax --close-stderr
root      4911  0.0  0.0   2480   864 ?        Ss   15:55   0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
parmenide:/home/na# ps ux|grep had
root      4078  0.0  0.0   3020   744 pts/2    R+   16:40   0:00 grep had
parmenide:/home/na# ps ux|grep hald
root      4080  0.0  0.0   3024   744 pts/2    R+   16:40   0:00 grep hald
root      4743  0.0  0.0   3308  1192 ?        S    15:55   0:00 hald-runner
root      4767  0.0  0.0   3372  1152 ?        S    15:55   0:00 hald-addon-input: Listening on /dev/input/event4 /dev/input/event3 /dev/input/event2 /dev/input/event1 /dev/input/event0
root      4771  0.0  0.0   3384  1216 ?        S    15:55   0:00 /usr/lib/hal/hald-addon-cpufreq
root      4775  0.0  0.0   3372  1164 ?        S    15:55   0:00 hald-addon-storage: polling /dev/hda (every 2 sec)
parmenide:/home/na# ps ux|grep udevd
root      2042  0.0  0.0   2592  1324 ?        S<s  15:54   0:00 udevd --daemon
root      4084  0.0  0.0   3024   748 pts/2    R+   16:41   0:00 grep udevd

3) I have both ehci_hcd and uhci_hcd. Here is the full output of lsmod:

Code:

Module                  Size  Used by
usb_storage            73280  0      
libusual               17680  1 usb_storage
snd_hda_intel         341528  1            
af_packet              19208  6            
i915                   24832  2            
capability              5512  0            
commoncap               7936  1 capability 
ipv6                  254500  25           
iptable_nat             8196  0            
nf_nat                 19116  1 iptable_nat
nf_conntrack_ipv4      17420  2 iptable_nat
nf_conntrack           62472  3 iptable_nat,nf_nat,nf_conntrack_ipv4
nfnetlink               6296  3 nf_nat,nf_conntrack_ipv4,nf_conntrack
iptable_mangle          3584  0                                      
iptable_filter          3712  0                                      
ip_tables              13156  3 iptable_nat,iptable_mangle,iptable_filter
x_tables               14596  2 iptable_nat,ip_tables                    
r5u870                 68420  0                                          
video_buf              24836  1 r5u870                                   
autofs4                19460  0                                          
acpi_cpufreq            8648  1                                          
cpufreq_userspace       4640  0                                          
cpufreq_stats           6080  0                                          
cpufreq_powersave       2688  0                                          
cpufreq_ondemand        7820  1                                          
freq_table              5792  3 acpi_cpufreq,cpufreq_stats,cpufreq_ondemand
cpufreq_conservative     6920  0                                           
i810                   20096  0
i830                   24704  0
eth1394                18180  0
drm                    80148  5 i915,i810,i830
sbp2                   22024  0
loop                   15364  0
snd_pcm_oss            41760  0
snd_mixer_oss          17152  1 snd_pcm_oss
pcmcia                 37012  0
ipw3945               199456  1
snd_pcm                77444  2 snd_hda_intel,snd_pcm_oss
joydev                  9664  0
snd_timer              22532  1 snd_pcm
snd_page_alloc          9608  2 snd_hda_intel,snd_pcm
snd_hwdep               9604  1 snd_hda_intel
tifm_7xx1               7168  0
usbhid                 26848  0
tsdev                   7616  0
ieee80211              51180  1 ipw3945
serio_raw               6532  0
hid                    31616  1 usbhid
snd                    55844  8 snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer,snd_hwdep
ieee80211_crypt         7296  1 ieee80211
tifm_core               9348  1 tifm_7xx1
yenta_socket           24844  1
rsrc_nonstatic         11008  1 yenta_socket
pcmcia_core            37268  3 pcmcia,yenta_socket,rsrc_nonstatic
i2c_i801                9104  0
psmouse                37648  0
intel_agp              23956  1
agpgart                33224  3 drm,intel_agp
evdev                   8960  7
ohci1394               33840  0
ieee1394               92344  3 eth1394,sbp2,ohci1394
ide_cd                 37280  0
sky2                   40072  0
ehci_hcd               33548  0
uhci_hcd               24464  0
usbcore               127752  7 usb_storage,libusual,r5u870,usbhid,ehci_hcd,uhci_hcd

4) Both /dev/sdb and /dev/sdb1 exist. Indeed, as I mentioned in my first post I have no problem in mounting the device manually. But I would like the volume to appear automatically in the file manager.
5) Unfortunately I have no command like "halmount".
6) udevinfo -q env -n /dev/sdb1 gives me the following:

Code:

DEVTYPE=partition
ID_VENDOR=S3+
ID_MODEL=USB_Mass_Storage_Device
ID_REVISION=0.00
ID_SERIAL=S3+_USB_Mass_Storage_Device_00000000000025-0:0
ID_SERIAL_SHORT=00000000000025
ID_TYPE=disk
ID_INSTANCE=0:0
ID_BUS=usb
ID_PATH=pci-0000:00:1d.7-usb-0:2:1.0-scsi-0:0:0:0
ID_FS_USAGE=filesystem
ID_FS_TYPE=vfat
ID_FS_VERSION=FAT32
ID_FS_UUID=46E5-757B
ID_FS_UUID_ENC=46E5-757B
ID_FS_LABEL=
ID_FS_LABEL_ENC=
ID_FS_LABEL_SAFE=

7) I have no entry for /dev/sdb1 in /etc/fstab.
8) If I do lshal -m and then I insert the pendrive, I get:

Code:

Start monitoring devicelist:
-------------------------------------------------
16:54:24.090: usb_device_19b6_2048_00000000000025 added
16:54:24.195: usb_device_19b6_2048_00000000000025_if0 added
16:54:24.196: usb_device_19b6_2048_00000000000025_usbraw added
16:54:29.144: usb_device_19b6_2048_00000000000025_if0_scsi_host added
16:54:29.150: usb_device_19b6_2048_00000000000025_if0_scsi_host_scsi_device_lun0 added
16:54:29.244: usb_device_19b6_2048_00000000000025_if0_scsi_host_scsi_device_lun0_scsi_generic added

Everything seems ok to me, but I can't see the volume appearing in the file manager. I repeat that the only way to get it, at the moment, is to unload and then reload the usb_storage module. Why?

jschiwal · 10-09-2008, 11:37 AM

Can you try with another pen drive? Is this a U3 pendrive that presents itself as a cdrom device? That might cause problems.

For comparison, here is what I see inserting a 2GB usb pendrive:

Code:

Start monitoring devicelist:
-------------------------------------------------
10:42:13.677: usb_device_930_6544_0802192214010 added
10:42:13.720: usb_device_1d6b_2_0000_00_1d_7_if0_0 added
10:42:14.725: usb_device_1d6b_2_0000_00_1d_7_if0_0_scsi_host added
10:42:14.738: usb_device_1d6b_2_0000_00_1d_7_if0_0_scsi_host_scsi_device_lun0 added
10:42:14.864: storage_serial__USB_Flash_Memory_0802192214010_0_0 added
10:42:14.870: storage_serial__USB_Flash_Memory_0802192214010_0_0 property info.interfaces = {'org.freedesktop.Hal.Device.Storage.Removable'} (new)
10:42:14.961: volume_uuid_2691_0786 added
10:42:14.974: usb_device_1d6b_2_0000_00_1d_7_if0_0_scsi_host_scsi_device_lun0_scsi_generic added
10:42:15.113: volume_uuid_2691_0786 property volume.mount_point = '/media/disk'
10:42:15.114: volume_uuid_2691_0786 property volume.is_mounted = true

This all occurs before I see the kde popup. You are seeing both the device and the partition and the device nodes are being created. So your udev configuration is probably ok.

You may be missing a .fdi file. The particular device may be listed as "broken". A Polkit policy may not allow automounting.
What does this show?

Code:

 polkit-action --action org.freedesktop.hal.storage.mount-removable

Look at:

Code:

jschiwal@qosmio:/usr/share/hal/fdi/preprobe> ls 10osvendor/
10-ide-drives.fdi  20-broken-usb-sticks.fdi

My kernel messages include "device scan complete" before a hald message about mounting the device. Is the device scan not completing I wonder?

Look at "ps -u root". Is there a "hald-addon-storage" process running?

---

Debian may use hal differently then SuSE. Plus I don't have the full picture of how udev/hal/Polkit/(KDE|Gnome) fit together. Some distro's use hal and hotplug together. Mine doesn't. Mine uses programs and scripts in /usr/lib64/hal/ to perform actions. Possible reasons for the problem: a .fdi config file is missing. Your device is listed as broken. A Policykit policy denies it. KDE or Gnome is misconfigured.

---
If you use KDE 3.5, enable "Behavior -> Device Icons -> Unmounted Removable Media" and "Mounted Removable Media". Right click on the icon on the desktop.
In Properties -> Mounting, is "Mount Automatically" selected. How about the options on the bottom?

parmenide · 10-10-2008, 08:28 AM

I tried with another pendrive, but unfortunately there was no difference.
I checked your output about "lshal -m" and I noticed that the difference with my case is that you get also the following two final rows:

Code:

10:42:15.113: volume_uuid_2691_0786 property volume.mount_point = '/media/disk'
10:42:15.114: volume_uuid_2691_0786 property volume.is_mounted = true

This is what I miss! Now the question is: who is responsible for these two rows to appear? I have no idea.
Since, as I previously mentioned, I can get the volume folder in the file manager by doing:

Code:

parmenide:/home/na# rmmod usb_storage
parmenide:/home/na# modprobe usb_storage

I was curious to see what happens in "lshal -m" when I give the two commands above. The result was the following:

Code:

15:05:36.454: storage_serial_S3__USB_Mass_Storage_Device_00000000000025_0_0 added
15:05:36.460: storage_serial_S3__USB_Mass_Storage_Device_00000000000025_0_0 property info.interfaces = {'org.freedesktop.Hal.Device.Storage.Removable'} (new)
15:05:36.574: volume_uuid_46E5_757B added

So the messages that you get automatically in "lshal -m" just after inserting the pendrive, I can get only if I unload and then reload the usb_storage module. It seems that in my case who is responsible for the volume_uuid_ to appear, acts only when I unload and reload the module. So the key of the solution should be in determining the process responsible for that. It could be a package of kde that has been removed during the upgrade from kde 3.5 to kde 4.1. It seems that the settings of the new kde 4.1 do not allow me to implement your last suggestions:
Enable "Behavior -> Device Icons -> Unmounted Removable Media" and "Mounted Removable Media" and Properties -> Mounting, is "Mount Automatically". So maybe the problem is related to kde 4.1. Who knows?

Coming to the other questions, I cannot check polkit-action because I don't have such a command available. I can't see the "device scan complete" message from the kernel, so something is missing here. (By the way, it cannot be a kernel related problem because I did not change the kernel.) Hotplug is no longer included in the last debian, so I don't have it.
I also checked ps -u root:

Code:

parmenide:/home/na# ps -u root|grep hald
 4753 ?        00:00:00 hald-runner
 4777 ?        00:00:00 hald-addon-inpu
 4779 ?        00:00:00 hald-addon-cpuf
 4785 ?        00:00:00 hald-addon-stor
 6730 ?        00:00:00 hald-addon-stor

ich666 · 10-26-2008, 05:31 AM

i am having exactly the same problem here recently on gentoo amd64.
lshal -m does only show the new usb device, not the volumes when plugging in the usb bar.
Any ideas?

ich666 · 10-27-2008, 11:39 AM

actually upgrading to a newer kernel (2.6.25 in my case) seems to help for me.