You are not logged in.
Pages: 1
Hello, I have a problem. I loggin into KDE or GNOME as a root to secure that I don't have group problems. On the both Desktops, USB storage devices are not automounted for a few days (maybe 1-2 weeks).
Why? What's the matter and how can I solved it? My system is fully up2date.
Greetings
Only deaths can see the end of battles.
Blog: http://djmartinez.co.cc -> The life of a Computer Engineer
Offline
Start with lsusb and usbview....Then hal as a daemon and the order of daemons. ahead of others
EDIT: Perhaps upgrade hwd to latest since there were problems before 5.2-1....
Last edited by lilsirecho (2007-12-02 23:45:37)
My ailment? Lackatesla!
Tesla fails smog test..no gas!
Favorite song...Tesla On My Mind....
Online
lsusb
[david@helena ~]$ lsusb
Bus 003 Device 001: ID 0000:0000
Bus 005 Device 003: ID 058f:6387 Alcor Micro Corp. Transcend JetFlash Flash Drive
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000I have hwd 5.2, all my system is full updated
hal is on my array:
DAEMONS=(syslog-ng !network hal hwd @alsa ipw3945d dhcdbd networkmanager fam !autofs @laptop-mode !entranced !netfs !gdm 915resolution samba kdm crond)Automounting worked until a few days...
Also kernel detects it, cause I can mount it manually.
Last edited by Davigetto (2007-12-03 07:09:56)
Only deaths can see the end of battles.
Blog: http://djmartinez.co.cc -> The life of a Computer Engineer
Offline
Did you install gparted? Check /usr/share/hal/fdi/policy/ to see if there is a file called something like "gparted-disable-automount.fdi" file. You can remove it, then restart hal and then it should be working again ![]()
Arch on a Thinkpad T400s
Offline
Well I'll be a monkey's uncle! Thanks mintcoffee, that worked!! I noticed that file is not owned by a package. Any idea how it gets there? gparted did crash on me while formatting my usb drive -- maybe the file is only supposed to exist while gparted is running.
Last edited by dmartins (2008-01-11 03:10:46)
-- Dan
Offline
IIRC you are correct dmartins - that rule is supposed to only exist while gParted is doing something to the harddrive. Obviously what happens when gParted crashes is that it sticks around. (on a side note - gParted should check for that rule on startup and remove it...)
"Unix is basically a simple operating system, but you have to be a genius to understand the simplicity." (Dennis Ritchie)
Offline
Pages: 1