DJA wrote:

DJA wrote:

[EMAIL PROTECTED] wrote:

The pc won't even see the device /dev/sda anymore.

"# fdisk /dev/sda" reports "Unable to open /dev/sda".

"mount /dev/sda2 /mnt/ipod" reports "mount: special device /dev/sda2 does not exist".

"cat /proc/bus/usb/devices" does not show it.

kudzu did not report its appearance (upon reboot).

It *is* plugged into the usb port. The ipod is charging. I switched it to the other usb port where the scanner was just removed from (and detected on) but no change (except that the scanner was no longer detected since it was no longer
plugged in).

Why can I no longer even see the ipod out there? Is the seLinux of fc3 somehow
getting in the way?  (if fc3 even has seLinux)



Have you updated FC3 to the latest and greatest? A fully updated FC2 has problems with USB storage devices, and a virgin FC3 may not be much better.

FC4 is _much_ better at handling hardware detection, including USB. I would have recommended moving from RH9 directly to FC4.


And here is a duh! on my part: FC3 now mounts removable media at /media/device_name.

Mounting my 1 GB SanDisk Cruzer looks like this after being automounted in FC3:

Sep 16 21:55:45 proteus kernel: usb 1-3: new full speed USB device using ohci_hcd and address 5
Sep 16 21:55:46 proteus kernel: Initializing USB Mass Storage driver...
Sep 16 21:55:46 proteus kernel: scsi2 : SCSI emulation for USB Mass Storage devices Sep 16 21:55:46 proteus kernel: usbcore: registered new driver usb-storage
Sep 16 21:55:46 proteus kernel: USB Mass Storage support registered.
Sep 16 21:55:51 proteus kernel: Vendor: SanDisk Model: Cruzer Micro Rev: 0.4 Sep 16 21:55:51 proteus kernel: Type: Direct-Access ANSI SCSI revision: 02 Sep 16 21:55:51 proteus kernel: SCSI device sdc: 2001888 512-byte hdwr sectors (1025 MB)
Sep 16 21:55:51 proteus kernel: sdc: Write Protect is off
Sep 16 21:55:51 proteus kernel: sdc: assuming drive cache: write through
Sep 16 21:55:51 proteus kernel: SCSI device sdc: 2001888 512-byte hdwr sectors (1025 MB)
Sep 16 21:55:51 proteus kernel: sdc: Write Protect is off
Sep 16 21:55:51 proteus kernel: sdc: assuming drive cache: write through
Sep 16 21:55:51 proteus kernel:  sdc: sdc1
Sep 16 21:55:51 proteus kernel: Attached scsi removable disk sdc at scsi2, channel 0, id 0, lun 0 Sep 16 21:55:51 proteus scsi.agent[7139]: disk at /devices/pci0000:00/0000:00:07.4/usb1/1-3/1-3:1.0/host2/target2:0:0/2:0:0:0 Sep 16 21:55:51 proteus fstab-sync[7174]: added mount point /media/usbdisk1 for /dev/sdc1


I still have to 'mount /media/usbdisk1' to read the drive, of course.

And yes, FC3 does install SELinux by default, although I have it in warning mode only because I don't know how to use it effectively yet.

I'm having a little bit of a problem under FC4 with USB devices too...

The first question I have though is this...
Is there a better/different way to detect the initialization of a USB device and the /dev file it is associated with besides doing a combination of tail/grep on dmesg or messages? Manual searching works fine for me once I know what the device will be recognized as then doing a grep for vendor, etc or just eyeballing a tail on messages but is that info somewhere else together?

I don't think I have ever seen anything that tells you the stuff about the USB device you can find out in /proc (e.g. KDE Info Center) but also what /dev file a given USB device is associated with...

TIA,
RBW


--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list

Reply via email to