I receive:
Grub stage 2 errors as follows:
usb 2-2 dev descriptor read/64 , error -71

usb 2-2 device not accepting address 4, error -71
" " 5, " "

I am using Fedora core 6 and on boot select kernel 2.6.19
also tried kernel 2.6.18

have done the yum -y update

*****
These errors occur when after I physically installed (plugged in) an all-in-1 usb card reader to my usb2 port on my abit kt7a
motherboard. I checked the pinouts and they are correct (pin 1 is plugged into pin 1)..

One note, the usb memory stick and the sd flash I plug into the all-in-one do operate properly on the same system(hardware and software) if I plug them into the rear external usb ports via separate cables....and remove the all-in-one usb card reader...

Any help would be appreciated...

Hi Ceramicbrad,

You're probably best to start a new thread in general and link to this one just to keep it fairly clear.

However, your problem is related and I had exactly the same message. The first thing I would check when you are getting those messages is to unplug the cable that goes into the motherboard, wait a few secs and then plug it back in. Also remove the ehci-hcd driver. Then do a dmesg to check for any messages.

I think it comes down to a power initialisation problem within linux somewhere. I discussed it at length with a friend yesterday. I'm currently researching the issue. He hinted at the issue of usb devices that guess the amount of power that is required to power the device and then drawing that current. Something like that.

I'll post more when I know.

Multicard readers are a black art at times on linux. Windows, no issue, but here... well we wait a longer longer or learn work arounds sometimes.

Hey my all-in-one usb reader now works.
But only after I unplug and plug it back in while logged into linux. Obviously I would not like to have to do this every boot, especially with the cover off.
Thanks so much Sausagejohnson for the valuable information.

For anyone who is interested
Here is the dmesg:
10
[drm] Initialized savage 2.4.1 20050313 on minor 0
mtrr: 0xe0000000,0x8000000 overlaps existing 0xe0000000,0x1000000
mtrr: 0xe0000000,0x2000000 overlaps existing 0xe0000000,0x1000000
mtrr: base(0xe2000000) is not aligned on a size(0x5000000) boundary
agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode
ISO 9660 Extensions: Microsoft Joliet Level 3
ISOFS: changing to secondary root
SELinux: initialized (dev hdd, type iso9660), uses genfs_contexts
usb 2-2: new low speed USB device using uhci_hcd and address 10
usb 2-2: device descriptor read/64, error -71
usb 2-2: device descriptor read/64, error -71
usb 2-2: new low speed USB device using uhci_hcd and address 11
usb 2-1: new low speed USB device using uhci_hcd and address 13
usb 2-1: device descriptor read/64, error -71
usb 2-1: device descriptor read/64, error -71
usb 2-2: new full speed USB device using uhci_hcd and address 15
usb 2-2: configuration #1 chosen from 1 choice
SCSI subsystem initialized
Initializing USB Mass Storage driver...
usb 2-1: new full speed USB device using uhci_hcd and address 16
usb 2-1: configuration #1 chosen from 1 choice
scsi0 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 15
usb-storage: waiting for device to settle before scanning
scsi1 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 16
usb-storage: waiting for device to settle before scanning
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
scsi 0:0:0:0: Direct-Access Generic STORAGE DEVICE 1.25 PQ: 0 ANSI: 0
scsi 1:0:0:0: Direct-Access Generic USB SD Reader 1.00 PQ: 0 ANSI: 0
scsi 1:0:0:1: Direct-Access Generic USB CF Reader 1.01 PQ: 0 ANSI: 0
usb-storage: device scan complete
scsi 1:0:0:2: Direct-Access Generic USB SM Reader 1.02 PQ: 0 ANSI: 0
scsi 1:0:0:3: Direct-Access Generic USB MS Reader 1.03 PQ: 0 ANSI: 0
usb-storage: device scan complete
scsi 0:0:0:0: Attached scsi generic sg0 type 0
scsi 1:0:0:0: Attached scsi generic sg1 type 0
scsi 1:0:0:1: Attached scsi generic sg2 type 0
scsi 1:0:0:2: Attached scsi generic sg3 type 0
scsi 1:0:0:3: Attached scsi generic sg4 type 0
SCSI device sda: 512000 512-byte hdwr sectors (262 MB)
sda: Write Protect is off
sda: Mode Sense: 02 00 00 00
sda: assuming drive cache: write through
SCSI device sda: 512000 512-byte hdwr sectors (262 MB)
sda: Write Protect is off
sda: Mode Sense: 02 00 00 00
sda: assuming drive cache: write through
sda: sda2
sd 0:0:0:0: Attached scsi removable disk sda
sd 1:0:0:0: Attached scsi removable disk sdb
SCSI device sdc: 2001888 512-byte hdwr sectors (1025 MB)
sdc: Write Protect is off
sdc: Mode Sense: 03 00 00 00
sdc: assuming drive cache: write through
SCSI device sdc: 2001888 512-byte hdwr sectors (1025 MB)
sdc: Write Protect is off
sdc: Mode Sense: 03 00 00 00
sdc: assuming drive cache: write through
sdc: sdc1
sd 1:0:0:1: Attached scsi removable disk sdc
sd 1:0:0:2: Attached scsi removable disk sdd
sd 1:0:0:3: Attached scsi removable disk sde
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
SELinux: initialized (dev sdc1, type ext2), uses xattr
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
SELinux: initialized (dev sda2, type ext2), uses xattr
*******

Below is the link to where I purchased the card reader:

http://cgi.ebay.com/3-5-Internal-All...QQcmdZViewItem

Hi.
After noting that the usb card reader worked if I unplugged it and then plugged it back in to the motherboard usb socket, the card reader got flakey on reboot.

Having a spare usb cable on hand, I spliced it into the card reader cable so that I could plug the card reader into the external usb port(red wire to red, green to green, white to white and black to black).
After doing this, the card reader recognizes all the memory cards just fine in linux(sd, smartmedia, compact flash)--but will not read the usb slot.
It behaves the same way in a windows 2000 environment even with the driver loaded that came with the card (no usb detected).

Looks like you and I have exactly the same problem. This is so weird. My motherboard is a GigaByte 7N400Pro2. What's yours? Replacing motherboards is NOT a solution because the reader worked perfectly in FC4.

So it is a change in FC6 that is causing this. Exactly what it is, is a mystery.

Now the issue of re-routing a homemade cable into the rear USB ports.... good idea, thinking of trying that but you've confirmed it as a work around.

However, the seperate USB port you said didn't work when fdoing this, I expect not to work if it is anything like mine. My reader has two sets of headers. One (for the cards) to plug into one internal USB socket, and a second header which is nothing more than a USB pass through to the second internal USB socket.

Do you have two sets of 4-pin header blocks or just one? I suspect you have two. Therefore when you wired yours up, it is only for the card reader portion, not the USB pass through section.

My motherboard is an ABIT KT7A board.(built in 1998)
It has two sets of headers(on the motherboard) and so
does the cable interface that came with the multicard
flash reader.
The interface connector that came
with the reader has pin 9 and 10 had no connection whatsoever.
Also, the connector was sealed shut at pin 9(plastic jacket) so in
order for me to plug it into my motherboard, I had to drill a small hole in the connector to allow it to accept the pin 9 from the motherboard (just to get the connector to seat properly so that the other used pins were making connection).
As a side note, I also found that if I booted my multicard reader with just the USB pen drive connected to it that linux and windows recognized the USB pen drive thru the multicard reader.
However, no other memory cards could be recognized if the USB drive was connected and mounted via multicard reader.

So, if I need to copy from other memory cards to the USB drive I have to do it in two passes, unless I use my second USB port for the USB pen drive.