I have a USB 2.0 CF reader that sometimes causes a spike in proc usage; that is, I plug it in, try to mount it, and the process freezes for a couple minutes. I can still use the computer (it doesn't lock up), but trying to kill the process (either with Ctrl-C or 'kill') takes a long time to execute. This has happened on both USB 1.1 and 2.0 ports. This is not a problem, however, when I start the computer with the CF reader in the port. (It's not mounted on boot, mind you, but when I mount it later, I don't have any problems with it.) What could be causing this, and what's the fix? The second issue is that I also have one of those USB flash drives. If the CF reader has already been mounted and unmounted, then try to mount the flash drive (as sda1), it says that it's not a valid block device. Doing things the manual way, it sometimes is under /dev/sdb1, sometimes under /sdc1, etc. And once I find out what device it is under, mount it, then unmount it, I have no luck remounting the CF reader (I tried up to /sdh1 with no luck). Since I always connect these two devices to the same port, is there some way to force their device to _always_ be sda1? Thanks, :Peter -- Oh what a tangled web they weave who try a new word to conceive! _______________________________________________ TCLUG Mailing List - Minneapolis/St. Paul, Minnesota http://www.mn-linux.org tclug-list at mn-linux.org https://mailman.real-time.com/mailman/listinfo/tclug-list