[QUOTE]Originally posted by Vlad-A
[B]P.S
1) when you run lsusb then the device is displayed.
We need to know if the class and the subclass of the device is drecognized properly.
output of lsusb:
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 007: ID 05dc:0001 Lexar Media, Inc.
Bus 001 Device 006: ID 045e:0040 Microsoft Corp. Wheel Mouse Optical
Bus 001 Device 004: ID 03f0:020c Hewlett-Packard Multimedia Keyboard
Bus 001 Device 003: ID 03f0:010c Hewlett-Packard Multimedia Keyboard Hub
Bus 001 Device 002: ID 03f0:0211 Hewlett-Packard
Bus 001 Device 001: ID 0000:0000



1-a) run lsusb
You will get an output similar to this
.....
Bus 004 Device 003: ID 0402:5634 ALi Corp.
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 003: ID 03f0:2311 Hewlett-Packard
Bus 002 Device 002: ID 046d:08f0 Logitech, Inc.
.....

1-b) In my case the device ALi Corp. is a USB storage
Now run lsusb -v -d against the ID of the device

In my case:
lsusb -v -d 0402:5634

The output is

Bus 004 Device 003: ID 0402:5634 ALi Corp.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 Interface
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0402 ALi Corp.
idProduct 0x5634
bcdDevice 0.50
iManufacturer 1
iProduct 2 Pen Drive 2.0
iSerial 3 5745160003DA
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk (Zip)
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type none
wMaxPacketSize 512
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type none
wMaxPacketSize 512
bInterval 0
Language IDs: (length=4)
0409 English(US)


So:
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI

means it's a storage device with SCSI subclass.
USB attached storage is handled in Linux as SCSI storage.

ok...here is the output of lsusb and id numbers:

linux:/home/annette # lsusb -v -d 05dc:0001

Bus 001 Device 007: ID 05dc:0001 Lexar Media, Inc.
Language IDs: none (invalid length string descriptor 04; len=256)
Device Descriptor:
bLength 32
bDescriptorType 1
bcdUSB 1.00
bDeviceClass 0 Interface
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x05dc Lexar Media, Inc.
idProduct 0x0001
bcdDevice 0.01
iManufacturer 14 LEXAR MEDIA
iProduct 14 LEXAR MEDIA
iSerial 4 1.00
bNumConfigurations 1
junk at descriptor end: 30 30 37 00 14 40 ff ff 0f 00 51 00 00 00
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 68
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
MaxPower 90mA
string descriptor 3 invalid (04 0a; len=256)
Interface Descriptor:
bLength 45
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 4
iInterface 3
junk at descriptor end: 09 04 0a 03 31 00 2e 00 30 00 30 00 18 03 4c 00 45 00 58 00 41 00 52 00 20 00 4d 00 45 00 44 00 49 00 41 00
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type none
wMaxPacketSize 64
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type none
wMaxPacketSize 64
bInterval 0
Language IDs: none (invalid length string descriptor 04; len=256)
linux:/home/annette #
seems it doesnt even have the right id stuff?? what is this?
2) You may also try to boot with the flash Card pluged in. Does this change something ?
changes nothing...

any other suggestions?? i am thinking of calling suse and getting support, i bought the pro version and i could call them...do u think its worth it?
Annette

Hello Annette,

it looks like SuSE does *not* recognize your flash-card as mass storage device.
You can see this in your lsusb -v -d XXXX:XXXX output. The Card is not recognized
as a mass storage device.

You for sure can contact SuSE. However, when you bought the Pro Version, you bought Installation Support.
This means that if you have some troubles installing SuSE Linux (e.g. Keyboard not recognized, you can not
install SuSE at all, etc.) then SuSE will help you.

Now, since your system is up and running and you have a problem getting a flash-card to work,
I am afraid that this is not covered by the installation support and that you will be very likely
asked to contact SuSE's advanced or premium support. This means you need to pay for it.

Anyway, try to contact them.
http://portal.suse.com/sdb/en/index.html

If nothing helps, send SuSE a technical feedback.
http://www.suse.com/cgi-bin/feedback.cgi

Include the lsusb and lsusb -v -d XXXX:XXXX output.

As I can seee your Card is USB 1.0 standard. Most common today are USB 1.1 and USB 2.0.

There is also one another option. Start
usbview

This will give you a graphical view of the attached USB devices.

Now in what color is the name of the Lexar Flashcard displayed (red or black) ?
If in red, then it means that SuSE does not have a driver for your card, or more precise
SuSE "thinks" it needs a driver for your card, and that this driver is missing.

Check also:
http://www.linux-usb.org

well, vlad,

that stinks about suse support! not much i can do then. my hp all in one scanner wont work either. suse does not recognize it as a usb scanner. great!! it seems that usb and suse are not as compatible. i tried usbview and here is the output:
inux:/home/annette # usbview
bash: usbview: command not found
dont know what that means exactly. i can use it on my mac, so i guess i will just have to use it that way for a while until i find a solution for it.

thanks for your help and if i find out how to fix this i will post.

Annette

HP all-In-One USB Scanner ?
I have a HP all in one USB Scanner (officejet d145) and it works perfectly. Even better then in Windows.
However, setting it up is a little bit tricky since you should not set-up your printer through YAST but
trough the CUPS Web administration.

Take a look on:
http://hpoj.sourceforge.net/doc.shtml

Supported devices
http://hpoj.sourceforge.net/suplist.shtml

Documentation (how to set up Scanner, etc.)
http://hpoj.sourceforge.net/hpoj-0.91/doc/index.html


as for usbview: it may be that's not in your path.

Log in into KDE as root and run usbview.


Or find the path with

find / -name usbview

i will try to log in as root and see what i can do. and yes the printer works GREAT, better than on fedora, BUT it wont recognize the scanner at all. this was no problem before. i actually had trouble using sane on my cannon scanner and the hp officejet G85 worked just as well, so i ended up using that. no extra configuration or anything...

but, yes the printer is great, now just to get my scanner working!!
annette

Most Canon scanners are useless under Linux. I have one myself and I can only use it under Windows.

Canon just doesn't release enough info for proper drivers to be written. Unless you are lucky enough to have one of the few older ones that people were able to reverse engineer, you're out of luck.

Canon maybe, but we are talking about HP (Hewlett-Packard).
I have much better results in terms of scan quality of pictures with Linux then with Windows.

It *seems* that the Linux drivers are better then the ones for windows.

Ok to get my HP all in one to work(PSC 1315v), I first need to get the right driver installed and the printer working, then restart. Next goto yast, and click on scanners. There should be an options that says, HP OfficeJet all in one. Click that, if its not there then I will Post the instructions to get it to work;

as root run, ptal-init setup
then you must enable the hpoj driver in the file /etc/sane.d/dll.conf
you must uncomment the line, which should be the last one. then just run xsane or xscanimage and it should be working. If not restart and try again.

Ok now I need your help, I have a 256 sandisk mini. Odd thing is before i updated suse 9.1 it worked just fine. It works on my backup computer just fine, but no longer will work on here. I have no idea why. I have tried everything and all I get is the device is not a valid Block device. Funny thing is my other computer shows no line for the usb stick in the fstab or mstab. I can't see the device in my usbview at all, no matter what i do. Restarting with it in does nothing and i've tried all of your examples and everyone i can find. The probem is that the usb can't find the usb stick anymore. What could cause this sudden disapearence? I Really would like to get this to work, as I don't use windows, and don't want to have to plug it into the other computer and transfer the files everytime i need to use them.

I'm not sure it helps, but when I updated SuSE online recently there was a fix for supermount which is supposed to solve problems with memory cards. I haven't tried it yet, though.

Robin

I suffered from similar problems, and found that if I disabled Legacy USB in the BIOS everything worked perfectly afterwards.

Before I changed the legacy usb setting only USB devices with external power would work. Anything like USB sticks which had no power source wouldn't work at all.

wow thank you very much, that actually worked. Makes no sense why it worked before with it on, but now it needs to be off.

Well like many, I got it to work but then it just mysteriously stopped working. I've traced the problem to the fact that supermounting is not turning off, even when settings the option to no. Is there anyway to turn it off besides manually when you boot up? This supermounting is messing up my pendrives ability to be used more than once. If you touch the disk at all, copy or read from its useless until you reboot. I know that its supermount that is messing this thing up, because i never had this problem before on no supermount enabled distros.