[Fwd: Re: [SLE] USB mass storage device (SOLVED)]
John Pettigrew wrote:
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 :-)
Would you mind sharing the details of this line? While my USB drive was recognised, there was no automatic insertion of a line in fstab and so I am curious of how this line should read.
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
Cheers. -- Understanding only begins with the act of perception.
In a previous message, Basil Chupin wrote:
John Pettigrew wrote:
Hotplug has inserted the relevant line into my fstab and I can now mount the device as a normal user and use it :-) Would you mind sharing the details of this line?
While my USB drive was recognised, there was no automatic insertion of a line in fstab and so I am curious of how this line should read.
Sorry for the late reply on this, but I hadn't forgotten - just not got round to is :-/ Anyway, the relevant line is: /dev/sdb1 /media/sdb1 auto noauto,user,exec 0 0 #HOTPLUG X2FE.mTI5ZUPfJMA The actual device might be different for you, of course. I find that it works most of the time - occasionally, the little light on the adapter will go out and SuSE will take *ages* to recognise the device (although it seems to do so eventually). One lingering problem is that now, if I've used the cardreader, I can't sync my Tungsten, because it is (for some odd reason) grabbed by the USB mass-storage driver instead of the visor driver. Still, I'm sure I'll sort that soon. 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 Fields of Valour: 2 Norse clans battle on one of 3 different boards
John Pettigrew wrote:
In a previous message, Basil Chupin wrote:
John Pettigrew wrote:
Hotplug has inserted the relevant line into my fstab and I can now mount the device as a normal user and use it :-)
Would you mind sharing the details of this line?
While my USB drive was recognised, there was no automatic insertion of a line in fstab and so I am curious of how this line should read.
Sorry for the late reply on this, but I hadn't forgotten - just not got round to is :-/
Anyway, the relevant line is: /dev/sdb1 /media/sdb1 auto noauto,user,exec 0 0 #HOTPLUG X2FE.mTI5ZUPfJMA
The actual device might be different for you, of course.
I find that it works most of the time - occasionally, the little light on the adapter will go out and SuSE will take *ages* to recognise the device (although it seems to do so eventually). One lingering problem is that now, if I've used the cardreader, I can't sync my Tungsten, because it is (for some odd reason) grabbed by the USB mass-storage driver instead of the visor driver. Still, I'm sure I'll sort that soon.
John
Many thanks for your reply. The information you provided has done the trick for me and now my Jetflash drive appears on the desktop as soon as I plug it in and I can then mount/unmount it with a click of a mouse. Re what you say above about the small problem you are experiencing. You mentioned in an earlier message that your device showed up in fdisk as /dev/sda1 but above you say that in fstab it is being shown as /dev/sdb1. Is this difference a typo on your part or is the sdb1 really the entry in fstab? If it is then more than likely this would be the reason for your problem. After I (manually) installed my USB drive I ended up with - /jetflash /sda1 in my /media directory, and following the info you provided above I have now written into fstab- /dev/sda1 /media/jetflash auto noauto,user,exec 0 0 and my USB device is recognised and mounts/unmounts instantly. Cheers. -- Understanding only begins with the act of perception.
In a previous message, Basil Chupin wrote:
Is this difference a typo on your part or is the sdb1 really the entry in fstab?
This is down to a small problem with my HD, which led me to reinstall linux. This time, when the computer decided to recognise the cardreader, it chose to call it sdb1. I think there's something odd happening in my USB setup but I lack the knowledge to investigate further, and it works most of the time! Glad you got your reader working, though! 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!
participants (2)
-
Basil Chupin -
John Pettigrew