trouble with samsung drive

trouble with samsung drive

[dima]

Hello!
I got the Samsung flash drive last weekend. It looks like a noname one 
marked as "Samsung 128MB, Made in Korea" only. It might be something of 
the K9F28XXX0C series 
(http://www.samsung.com/Products/Semiconductor/Flash/NAND/128Mbit/K9F2816Q0C/K9F2816Q0C.htm).
I tried to get it working on my old laptop on Sunday but failed. It 
could be a problem with the USB hub since it is USB 1.1 & the flash 
drive is reported to be USB 2.0. I searched the web & figured out that 
Samsung chips must be NAND-compatible. I used DiskOnChip 2000 driver 
first, but it failed to probe the device (btw, USB hub didn't report any 
unclaimed devices). Then I tried almost all MTD drivers availble in the 
standard (kernel.org) kernel distribution (v2.4.20) -- none of them 
seemed to probe the device successfully.
So I have 3 questions:
1) Is this a problem with my old USB hub?
2) Which driver should I use if no?
3) I didn't enable SCSI emulation support in the kernel yet (I decided 
to leave it for the next step since the device hadn't been detected). 
Can it be the problem?

Re: trouble with samsung drive

[Matthew Dharm]

USB Mass Storage devices aren't handled via the MTD driver, generally.
They are handled by the usb-storage driver via SCSI emulation.

If the device shows up in /proc/bus/usb/devices with class code 8, then the
USB low-level is working and it's time to move on to enabling the
usb-storage driver.

The place for usb-storage help is linux-usb-users@lists.sf.net

Matt

On Mon, Sep 01, 2003 at 11:54:48AM +0400, dima wrote:
> Hello!
> I got the Samsung flash drive last weekend. It looks like a noname one 
> marked as "Samsung 128MB, Made in Korea" only. It might be something of 
> the K9F28XXX0C series 
> (http://www.samsung.com/Products/Semiconductor/Flash/NAND/128Mbit/K9F2816Q0C/K9F2816Q0C.htm).
> I tried to get it working on my old laptop on Sunday but failed. It 
> could be a problem with the USB hub since it is USB 1.1 & the flash 
> drive is reported to be USB 2.0. I searched the web & figured out that 
> Samsung chips must be NAND-compatible. I used DiskOnChip 2000 driver 
> first, but it failed to probe the device (btw, USB hub didn't report any 
> unclaimed devices). Then I tried almost all MTD drivers availble in the 
> standard (kernel.org) kernel distribution (v2.4.20) -- none of them 
> seemed to probe the device successfully.
> So I have 3 questions:
> 1) Is this a problem with my old USB hub?
> 2) Which driver should I use if no?
> 3) I didn't enable SCSI emulation support in the kernel yet (I decided 
> to leave it for the next step since the device hadn't been detected). 
> Can it be the problem?
> 
> 
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/

-- 
Matthew Dharm                              Work: mdharm@momenco.com
Senior Software Designer, Momentum Computer

Re: trouble with samsung drive

[dima]

Matthew Dharm wrote:

>USB Mass Storage devices aren't handled via the MTD driver, generally.
>They are handled by the usb-storage driver via SCSI emulation.
>
Yeah, I figured out that it's an USB mass storage device when plugged it 
into my FreeBSD desktop at work. It was successfully detected as "Lexar 
Jumpshot".

>If the device shows up in /proc/bus/usb/devices with class code 8, then the
>USB low-level is working and it's time to move on to enabling the
>usb-storage driver.
>
/proc/bus/usb is empty. So, is this a problem with my USB hub? USB 
driver loads ok and detects the hub successfully though. My 1st question 
is still actual then: can USB 1.1 hub cooperate with USB 2.0 devices? 
The USB driver doesn't report any unclaimed devices as I mentioned in 
the previous post.

>The place for usb-storage help is linux-usb-users@lists.sf.net
>  
>
Thanks, I'll try this list.