Greetings! I'm sure I must be doing something wrong, but I simply cannot get my USB flash drive to work on 9.1 Pro. If I plug it in, the following directories are created: usb-storage-odd-SuperTalentFlashInc-USBMassStorageDevice:0:0:0p1 usb-storage-odd-SuperTalentFlashInc-USBMassStorageDevice:0:0:0p2 usb-storage-odd-SuperTalentFlashInc-USBMassStorageDevice:0:0:0p3 usb-storage-odd-SuperTalentFlashInc-USBMassStorageDevice:0:0:0p4 However, none of them will mount. Any thoughts? Thanks for any help, Ken
On Thursday 03 June 2004 21:01, Ken Hughes wrote:
Greetings!
I'm sure I must be doing something wrong, but I simply cannot get my USB flash drive to work on 9.1 Pro. If I plug it in, the following directories are created:
usb-storage-odd-SuperTalentFlashInc-USBMassStorageDevice:0:0:0p1 usb-storage-odd-SuperTalentFlashInc-USBMassStorageDevice:0:0:0p2 usb-storage-odd-SuperTalentFlashInc-USBMassStorageDevice:0:0:0p3 usb-storage-odd-SuperTalentFlashInc-USBMassStorageDevice:0:0:0p4
However, none of them will mount. Any thoughts?
Thanks for any help,
Ken I installed Suse 9.1 onto a new HD and mounted the one containing the 9.0 installation into a USB adapter. What nags me is that Suse 9.1 can read and write to DOS/Windows partitions, but not my old installation of Suse. I chose exactly the same passwords for 9.1 to no avail, as the system notified me that it could not mount the Linux partitions.
On Thursday 03 June 2004 02:08 pm, Niels Stenhøj wrote:
I installed Suse 9.1 onto a new HD and mounted the one containing the 9.0 installation into a USB adapter. What nags me is that Suse 9.1 can read and write to DOS/Windows partitions, but not my old installation of Suse. I chose exactly the same passwords for 9.1 to no avail, as the system notified me that it could not mount the Linux partitions.
SUSE 9.1 started UID numbering at 1000 versus 500 for prior versions. If you kept the same user name for both 9.0 and 9.1 then your 9.1 UID 1000 does not have permission to write your 9.0 UID 500 devices. Same name, same password but different UID != the same user. Cure is to change the old UID 500 on the 9.0 devices to the new UID 1000 of 9.1... or verse vice Stan
Maybe they auto-mount? Can you see anything about them in "My Computer"? On Thursday 03 June 2004 15:01, Ken Hughes wrote:
Greetings!
I'm sure I must be doing something wrong, but I simply cannot get my USB flash drive to work on 9.1 Pro. If I plug it in, the following directories are created:
usb-storage-odd-SuperTalentFlashInc-USBMassStorageDevice:0:0:0p1 usb-storage-odd-SuperTalentFlashInc-USBMassStorageDevice:0:0:0p2 usb-storage-odd-SuperTalentFlashInc-USBMassStorageDevice:0:0:0p3 usb-storage-odd-SuperTalentFlashInc-USBMassStorageDevice:0:0:0p4
However, none of them will mount. Any thoughts?
Thanks for any help,
Ken
On Thu, 2004-06-03 at 21:01, Ken Hughes wrote:
Greetings!
I'm sure I must be doing something wrong, but I simply cannot get my USB flash drive to work on 9.1 Pro. If I plug it in, the following directories are created:
usb-storage-odd-SuperTalentFlashInc-USBMassStorageDevice:0:0:0p1 usb-storage-odd-SuperTalentFlashInc-USBMassStorageDevice:0:0:0p2 usb-storage-odd-SuperTalentFlashInc-USBMassStorageDevice:0:0:0p3 usb-storage-odd-SuperTalentFlashInc-USBMassStorageDevice:0:0:0p4
However, none of them will mount. Any thoughts?
Make sure you have the latest kernel, it works for me, it takes a few seconds but when I plug the USB key I end up getting valid listings in /media. My PC has one external 200GB USB2 MAXTOR 5000DV (with one FAT and one ext3 partition) and I often plug/unplug a "noname" 256MB USB key between home and work (FAT). Since the automatically generated names are not that user-friendly, I made symbolic links (maxtor1,maxtor2,key1). May be it would be useful to add an option to Yast2 to give symbolic names to currently mounted devices and to have the tools automatically create them when a device is mounted (may be it's even already possible but I could not find it). Hope this helps, Laurent pc:/media # cat /proc/version Linux version 2.6.4-54.5-default (geeko@buildhost) (gcc version 3.3.3 (SuSE Linux)) #1 Fri May 7 21:43:10 UTC 2004 pc:/media # ls -l /media total 8 drwxr-xr-x 8 root root 4096 Jun 3 21:36 . drwxr-xr-x 20 root root 4096 May 29 17:02 .. drwxrwxrwx 1 root root 0 May 29 17:02 cdrecorder drwxrwxrwx 1 root root 0 May 29 17:02 dvd drwxrwxrwx 1 root root 0 May 29 17:02 floppy lrwxrwxrwx 1 root root 41 Jun 3 21:36 key1 -> usb-storage-odd-ACGTek-uflashdisk:0:0:0p1 lrwxrwxrwx 1 root root 28 May 29 17:09 maxtor1 -> usb-storage-Y60AL6PE:0:0:0p1 lrwxrwxrwx 1 root root 28 May 29 17:09 maxtor2 -> usb-storage-Y60AL6PE:0:0:0p2 drwxrwxrwx 1 root root 0 May 29 17:03 usb-storage-Y60AL6PE:0:0:0p1 drwxrwxrwx 1 root root 0 May 29 17:03 usb-storage-Y60AL6PE:0:0:0p2 drwxrwxrwx 1 root root 0 Jun 3 21:34 usb-storage-odd-ACGTek-uflashdisk:0:0:0p1 pc:/media # ls -l /media/key1/ total 76316 drwxr-xr-x 2 root root 16384 Jan 1 1970 . drwxr-xr-x 8 root root 4096 Jun 3 21:36 .. -rwxr-xr-x 1 root root 0 May 20 15:16 guerby -rwxr-xr-x 1 root root 3996 Apr 21 14:18 long-branch.patch -rwxr-xr-x 1 root root 25796274 Apr 20 21:34 version-apple-20040420.tar.bz2 -rwxr-xr-x 1 root root 26008084 Apr 20 21:34 version-head-20040420.tar.bz2 -rwxr-xr-x 1 root root 26314421 Apr 25 23:13 version-head-20040425.tar.bz2 pc:/media # ls -l /media/maxtor2/ total 28 drwxr-xr-x 4 root root 4096 May 29 00:06 . drwxr-xr-x 8 root root 4096 Jun 3 21:36 .. -rw-r--r-- 1 root root 0 Nov 25 2003 MAXTOR2 drwxr-xr-x 6 guerby users 4096 May 29 00:24 guerby drwx------ 2 root root 16384 Aug 15 2003 lost+found
Simon Thornton solved this for me. The problem seems to occur because the manufacturers do not create correct partion tables on some flash drives. Microsoft operating systems seem to ignore faulty flash drive partition tables. Simon's advice (which worked for me) was to delete the existing partitions and re-format the drive using fdisk. I have also noticed on two separate machines running SuSE 9.1 that transferring large amounts of data from flash drives or zip disks will cause the machines to hang. I've had to abandon using removable magnetic media with my SuSE 9.1 machines. Regards, Steve On Fri, 4 Jun 2004 04:31 am, Ken Hughes wrote:
I'm sure I must be doing something wrong, but I simply cannot get my USB flash drive to work on 9.1 Pro. If I plug it in, the following directories are created:
usb-storage-odd-SuperTalentFlashInc-USBMassStorageDevice:0:0:0p1 usb-storage-odd-SuperTalentFlashInc-USBMassStorageDevice:0:0:0p2 usb-storage-odd-SuperTalentFlashInc-USBMassStorageDevice:0:0:0p3 usb-storage-odd-SuperTalentFlashInc-USBMassStorageDevice:0:0:0p4
Steve Reynolds wrote:
Simon Thornton solved this for me. The problem seems to occur because the manufacturers do not create correct partion tables on some flash drives. Microsoft operating systems seem to ignore faulty flash drive partition tables.
Simon's advice (which worked for me) was to delete the existing partitions and re-format the drive using fdisk.
Thanks a bunch Steve, this worked for me as well. It seems odd that KDE used to mount /dev/sda automagically upon inserting the flash drive, but now it must be done manually. Thanks again to everyone who offered help, Ken
On Thursday 03 June 2004 21:21, Steve Reynolds wrote: which i guess is fine... however, mine used to (and still does) work fine with SuSE 9.0 Pro. It only has a problem on the SuSE 9.1 installation. Has SuSE done something different with the USB 2.0 drivers? I'll try your suggestion, I just dont want to destroy my drive entirely. My USB drive is an Integral USB 2.0 Flash Memory 256M?
Simon Thornton solved this for me. The problem seems to occur because the manufacturers do not create correct partion tables on some flash drives. Microsoft operating systems seem to ignore faulty flash drive partition tables.
Simon's advice (which worked for me) was to delete the existing partitions and re-format the drive using fdisk.
I have also noticed on two separate machines running SuSE 9.1 that transferring large amounts of data from flash drives or zip disks will cause the machines to hang.
I've had to abandon using removable magnetic media with my SuSE 9.1 machines.
Regards, Steve
On Fri, 4 Jun 2004 04:31 am, Ken Hughes wrote:
I'm sure I must be doing something wrong, but I simply cannot get my USB flash drive to work on 9.1 Pro. If I plug it in, the following directories are created:
usb-storage-odd-SuperTalentFlashInc-USBMassStorageDevice:0:0:0p1 usb-storage-odd-SuperTalentFlashInc-USBMassStorageDevice:0:0:0p2 usb-storage-odd-SuperTalentFlashInc-USBMassStorageDevice:0:0:0p3 usb-storage-odd-SuperTalentFlashInc-USBMassStorageDevice:0:0:0p4
On Friday 04 June 2004 15:08, Tom Corr wrote:
On Thursday 03 June 2004 21:21, Steve Reynolds wrote: which i guess is fine... however, mine used to (and still does) work fine with SuSE 9.0 Pro. It only has a problem on the SuSE 9.1 installation. Has SuSE done something different with the USB 2.0 drivers? I'll try your suggestion, I just dont want to destroy my drive entirely. My USB drive is an Integral USB 2.0 Flash Memory 256M?
Go search the Suse Knowledge base. This is a known issue with ehci_hcd. -- _____________________________________ John Andersen
On Saturday 05 June 2004 01:46, John Andersen wrote: thank you... that did help/solve one problem. i can now reboot the box with the usb flash stick plugged in (i couldnt do that before... it would just hang). i guess what still puzzles me about this whole thing is that the stick works just fine on my Suse 9 box, and is now broken on my suse 9.1 box. i've also tried the stick on a fedora core 2 box and it worked there as well.
On Friday 04 June 2004 15:08, Tom Corr wrote:
On Thursday 03 June 2004 21:21, Steve Reynolds wrote: which i guess is fine... however, mine used to (and still does) work fine with SuSE 9.0 Pro. It only has a problem on the SuSE 9.1 installation. Has SuSE done something different with the USB 2.0 drivers? I'll try your suggestion, I just dont want to destroy my drive entirely. My USB drive is an Integral USB 2.0 Flash Memory 256M?
Go search the Suse Knowledge base. This is a known issue with ehci_hcd.
-- _____________________________________ John Andersen
On Saturday 05 June 2004 04:47, Tom Corr wrote:
On Saturday 05 June 2004 01:46, John Andersen wrote: thank you... that did help/solve one problem. i can now reboot the box with the usb flash stick plugged in (i couldnt do that before... it would just hang).
i guess what still puzzles me about this whole thing is that the stick works just fine on my Suse 9 box, and is now broken on my suse 9.1 box. i've also tried the stick on a fedora core 2 box and it worked there as well.
Well its a whole new kernel, and it was known that not everything was perfect yet. AFAIK 2.4 kernels did not support USB 2.0 very well (or at all) and perhaps your USB device always defaulted to 1.1. (Is it a dual standard device: 2.0 and 1.1?). Now in the 2.6 kernel it tries to access it with the 2.0 modules ehci-hcd, but the load order prevented that from working. I'm guessing here, all I know is it worked for me. BTW: for otheres, here is the page reference: http://portal.suse.com/sdb/en/2004/01/USB_2_0.html -- _____________________________________ John Andersen
On Saturday 05 June 2004 15:29, John Andersen wrote: Which memory stick do you use? I've heard mixed reports about SanDisk Cruzers and am wondering which one I should try next, if i give up on mine. thanks again. tom
On Saturday 05 June 2004 04:47, Tom Corr wrote:
On Saturday 05 June 2004 01:46, John Andersen wrote: thank you... that did help/solve one problem. i can now reboot the box with the usb flash stick plugged in (i couldnt do that before... it would just hang).
i guess what still puzzles me about this whole thing is that the stick works just fine on my Suse 9 box, and is now broken on my suse 9.1 box. i've also tried the stick on a fedora core 2 box and it worked there as well.
Well its a whole new kernel, and it was known that not everything was perfect yet. AFAIK 2.4 kernels did not support USB 2.0 very well (or at all) and perhaps your USB device always defaulted to 1.1. (Is it a dual standard device: 2.0 and 1.1?). Now in the 2.6 kernel it tries to access it with the 2.0 modules ehci-hcd, but the load order prevented that from working. I'm guessing here, all I know is it worked for me.
BTW: for otheres, here is the page reference:
http://portal.suse.com/sdb/en/2004/01/USB_2_0.html
-- _____________________________________ John Andersen
Tom Corr wrote:
On Saturday 05 June 2004 15:29, John Andersen wrote: Which memory stick do you use? I've heard mixed reports about SanDisk Cruzers and am wondering which one I should try next, if i give up on mine.
thanks again. tom
On Saturday 05 June 2004 04:47, Tom Corr wrote:
On Saturday 05 June 2004 01:46, John Andersen wrote: thank you... that did help/solve one problem. i can now reboot the box with the usb flash stick plugged in (i couldnt do that before... it would just hang).
i guess what still puzzles me about this whole thing is that the stick works just fine on my Suse 9 box, and is now broken on my suse 9.1 box. i've also tried the stick on a fedora core 2 box and it worked there as well.
Well its a whole new kernel, and it was known that not everything was perfect yet. AFAIK 2.4 kernels did not support USB 2.0 very well (or at all) and perhaps your USB device always defaulted to 1.1. (Is it a dual standard device: 2.0 and 1.1?). Now in the 2.6 kernel it tries to access it with the 2.0 modules ehci-hcd, but the load order prevented that from working. I'm guessing here, all I know is it worked for me.
BTW: for otheres, here is the page reference:
http://portal.suse.com/sdb/en/2004/01/USB_2_0.html
-- _____________________________________ John Andersen
I had problems with a SanDisk Cruzer 256MB Thumbdrive and switched to a Lexar JumpDrive and it works great. No tweeking needed. I'm running SuSE 9.1 Pro. -- Brian Craft Yahoo Instant Messenger ID: bcraft67 AIM: linuxman67 Website: http://userdata.acd.net/javaman67/ Linux Counter id: 97873 Linux......the OS of Choice!
participants (9)
-
Brian Craft -
Doug McGarrett -
John Andersen -
Ken Hughes -
Laurent GUERBY -
Niels Stenhøj -
SRGlasoe -
Steve Reynolds -
Tom Corr