Automount of USB Devices is not working

[spamllama2000]

Hey, I'm a bit of a newb, but I've been using Fedora for about 4 months as my main system's OS, so I'm not totally in the dark.

I have a problem where I can't seem to mount USB devices automagically. I have my old Fedora build (also FC6) on an 5 GB drive that's slaved and still in the machine.

When I boot up to that, and plug in my Flash drive and my Sansa m240, they pop right up. Icons on the desktop, they're listed in places, you can open the flash drive and it comes up correctly... all works the way it seems it should by default.

However, on my 160GB drive with my main load, I can mount them manually, but they don't just automatically pop up when I plug them in.

A check to /media/.hal-mtab on each machine reveals pretty much the same.
5GB drive - /dev/sda1 and /dev/sdb1 are both listed and mapped to /media/*** directories.
160GB drive - nada, nothing, blank.

fstab on both machines looks about the same, neither lists the fd0 or usb devices, as expected.

I installed hal-gnome and it does list both the flash drive and the sansa, plugged in under the UHCI USB 1.1 controller.

Soooooo.... any idea how I get from point a to point b?

Thanks,
Derrick

[Seve]

Hello:
When you plug in your USB drive in FC6.... what entry, if any, is created in your /etc/mtab file ?

Seve

[spamllama2000]

Hey Seve,

On the FC6 build on the 5GB ddrive, I get an entry that says:

/dev/sdb1 500 0 vfat noexec,nosuid,nodev,shortname=winnt,uid=500 /nedia/disk

One the FC6 build on the 160, I don't get anything. Its blank like its not seeing it. However, hal-gnome does show it connected to the USB controller.

That's what has me perplexed.

Thanks,
Derrick

[spamllama2000]

Hey, I've been trying to contune looking into this... I seem to have found more info on the sympton, however no resolution. Could this be an SELinux problem?

I pulled a dmesg on each build... here are the differences:

On FC6 build on 160gb drive:

usbcore: registered new device driver usb
ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
scsi 0:0:0:0: Direct-Access SanDisk Sansa m240 1.30 PQ: 0 ANSI: 0
scsi 1:0:0:0: Direct-Access ChipsBnk Flash Disk 2.00 PQ: 0 ANSI: 2
scsi 0:0:0:0: Attached scsi generic sg0 type 0
scsi 1:0:0:0: Attached scsi generic sg1 type 0


On FC6 build on 5gb drive:

Initializing Cryptographic API
PCI: VIA IRQ fixup for 0000:00:11.1, from 255 to 0

ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
Vendor: SanDisk Model: Sansa m240 Rev: 1.30
Type: Direct-Access ANSI SCSI revision: 00
Vendor: ChipsBnk Model: Flash Disk Rev: 2.00
Type: Direct-Access ANSI SCSI revision: 02
usb-storage: device scan complete
scsi 0:0:0:0: Attached scsi generic sg0 type 0
scsi 1:0:0:0: Attached scsi generic sg1 type 0

SELinux: initialized (dev sdb1, type vfat), uses genfs_contexts
SELinux: initialized (dev sda1, type vfat), uses genfs_contexts

Note that the USB driver is older... just as an FYI, the old build that I quit updating has kernel 2849. The new one is 2895. What I found interesting was that when usb-storage did a device scan, it came up with these lines:

Vendor: SanDisk Model: Sansa m240 Rev: 1.30
Type: Direct-Access ANSI SCSI revision: 00
Vendor: ChipsBnk Model: Flash Disk Rev: 2.00
Type: Direct-Access ANSI SCSI revision: 02

while the build on my 160GB drive came up with:

scsi 0:0:0:0: Direct-Access SanDisk Sansa m240 1.30 PQ: 0 ANSI: 0
scsi 1:0:0:0: Direct-Access ChipsBnk Flash Disk 2.00 PQ: 0 ANSI: 2

Not sure if that's just a difference in versions or what's causing it.

Thanks,
Derrick