Memory stick volume does not appear in file manager
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Memory stick volume does not appear in file manager
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?
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.
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:
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?
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?
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?
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:
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:
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:
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?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.