In a previous message, Joe Morris (NTM) wrote:
OK, I've removed the 2.4.20-31 kernel I was running and reinstated the SuSE default k_athlon 2.4.19-4GB. This has made *some* difference - now, when I plug the device in, I get extra messages: After plugging it in, try fdisk -l to see what exactly you have, use mount with the correct partition and fstype and a viable mount point. HTH
This was very useful - but not only for the obvious reasons! I connected the device and gave it a few seconds, checked /var/log/messages to see that it had been detected, then tried fdisk -l. No joy - the only drives listed were the IDE ones. However, while I was puzzling about this, i heard the USB-hotplug beep and thought "Aha!". A new fdisk -l showed that I now had a drive at /dev/sda1, and mounting this worked! I've no idea why it seemed to take over a minute to recognise this device the first time, but it's now working as it should (i.e. it's now being recognised almost instantly after being plugged in). Hotplug has inserted the relevant line into my fstab and I can now mount the device as a normal user and use it :-) Thanks to all for the help - it looks like the two things needed were (1) revert to the SuSE-supplied 2.4.19 kernel and (2) wait for a *long* time the first time the device was connected for the system to recognise it. John -- John Pettigrew Headstrong Games john@headstrong-games.co.uk Fun : Strategy : Price http://www.headstrong-games.co.uk/ Board games that won't break the bank Valley of the Kings: ransack an ancient Egyptian tomb but beware of mummies!