Solved! Well, after searching for a while and reading HAL Specification I decided to create a fdi file in /etc/hal/fdi/policy containing: #Sansa e200 Series <match key="usb_device.vendor_id" int="0x0781"> <match key="usb_device.product_id" int="0x7421"> <merge key="volume.ignore" type="bool">false</merge> </match> </match> And it worked! But I still don't understand why! In HAL Specs it says: "This is a hint to software higher in the stack that this volume should be ignored. If TRUE, the volume should be invisible in the UI and mount wrappers should refuse to mount it on behalf on an unprivileged user. " Also I read somewhere (forgot where,now) that HAL sets this to true for fixed drives. Is it possible that Sansa was being recognized as a fixed drive? I don't think so. Well, continuing... After restarting hal with this fdi file, sansa was recognized fine. I decided to remove that file and restart hal, just to see if the problem still occurred. No, it didn't. My guess is that once hal had all the information about the device the initial problem of "assuming" something disappeared. I still need to reboot and check if everything is fine now. Anyway, thanks for your help guys! On Tue, Jun 23, 2009 at 9:44 PM, Slash <demodevil@gmail.com> wrote:
It shows it as being assigned to /dev/sdc. What's the output if you try to mount it manually? Does fdisk -l /dev/sdc show the partitions?
Actually, I have a microSD card in it, so /dev/sdb is the internal flash storage and /dev/sdc is the card.
Are you using rockbox? It's a pretty nice open source replacement software for that player (http://www.rockbox.org/ http://aur.archlinux.org/packages.php?ID=26864) :)
Yes, I'm using it =] That's one of the reason I bought sansa, and the reason I was plugging the player in the first place was to update rockbox. -- Malformed message exception => Guilherme M. Nogueira => http://nirev.org/