eSata devices not displayed in DeviceNotifier [Solved]

[King_DuckZ]

Hello, I've had this problem in KDE since the first time I tried plugging an eSata device, but a workaround at https://bugs.freedesktop.org/show_bug.cgi?id=12127 helped fixing this.
Now I see they fixed this in HAL (last comment) but... HAL got replaced, no? I don't even have the preferences.fdi file, anyone knows how to fix this problem now?

[Fitzcarraldo]

My guess is it's a ConsoleKit or D-Bus issue. Try fix in Comment #3 in Gentoo Bugzilla Bug Report No. 359155.

[King_DuckZ]

Hey, sorry for the late reaction about this! I tried the fix as you suggested but it didn't work.
I created a new file in /etc/udev/rules.d named 80-esata.rules, the whose content is:

Code: Select all

KERNEL=="sd[b-z]", ATTRS{class}=="0x060400", ENV{UDISKS_SYSTEM_INTERNAL}="0"


but KDE still doesn't give any sign after plugging my esata hard disk. Any other advice?

[Fitzcarraldo]

udisks-1.0.3 makes the modified ebuild obsolete.

This is what you have to put in your udev rules for apps to pick up the newly
added device as removable (adjust to your controller and HD setup accordingly):

KERNEL=="sd[b-z]", ATTRS{class}=="0x060400", ENV{UDISKS_SYSTEM_INTERNAL}="0"

still, this should not be necessary to configure anyway..

You can't just copy the rule verbatim: he tells you that you must adjust it to your controller and HD setup!

Code: Select all

# udevadm info -a -p $(udevadm info -q path -n /dev/sdb1) | grep class

Replace "/dev/sdb1" with whatever your external drive device actually is. Example:

Code: Select all

# udevadm info -a -p $(udevadm info -q path -n /dev/sdb1) | grep class
ATTRS{class}=="0x010601"

[King_DuckZ]

Uhm... sure... I was just checking if you knew the answer... :p
Now it works perfectly, thanks!

[Fitzcarraldo]

Why, and how to add "[Solved]" to your post. Please read.