Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Yeeps, this seems to be a problem and a half, I wonder if anyone on here can help me!
Right, heres the scenario: I have a USB card reader that reads 6 types of cards (CF/SD etc). It works in Windows, but I need to use it in Linux - because of PsiLinux.
I added the modules I thought I was going to need: (Im running a default redhat kernel as I havent got round to recompiling yet :P)
Right, looks all well and good to me. When I plug the device in I get:
Code:
Initializing USB Mass Storage driver...
scsi0 : SCSI emulation for USB Mass Storage devices
Vendor: Generic Model: USB Storage-SMC Rev: 0207
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 8
USB Mass Storage support registered.
Showing in dmesg and /var/log/messages. I thne used a tool called SCSI enquiry to see which device it was:
Code:
[root@ernie sg_utils-1.02]# ./scsi_inquiry /dev/sda
Generic USB Storage-SMC 0207, byte_7=0x0
Therefore it looks like I have a system that should mount the disk.
Code:
[root@ernie sg_utils-1.02]# mount /dev/sda /mnt/floppy
/dev/sda: Input/output error
mount: you must specify the filesystem type
Attempt 1: Note its the /dev/sda not any partition, also note that there's an input output error specified.
I then tried with vfat specified, this doesnt seem to work either:
Code:
[root@ernie sg_utils-1.02]# mount /dev/sda /mnt/floppy -t vfat
mount: wrong fs type, bad option, bad superblock on /dev/sda,
or too many mounted file systems
This time theres no input/output error... so I checked /var/log/messages again to see
Code:
Dec 31 16:20:23 ernie kernel: Device not ready. Make sure there is a disc in the drive.
Dec 31 16:20:23 ernie kernel: Device 08:00 not ready.
Dec 31 16:20:23 ernie kernel: I/O error: dev 08:00, sector 0
Dec 31 16:20:23 ernie kernel: FAT: unable to read boot sector
Dec 31 16:20:23 ernie kernel: Device not ready. Make sure there is a disc in the drive.
It doesnt think theres a disk in it!
Code:
ec 31 16:11:52 ernie /etc/hotplug/usb.agent: Setup usb-storage for USB product
aec/3050/100
Dec 31 16:11:52 ernie kernel: Initializing USB Mass Storage driver...
Dec 31 16:11:52 ernie kernel: usb.c: registered new driver usb-storage
Dec 31 16:11:52 ernie kernel: scsi0 : SCSI emulation for USB Mass Storage devices
Dec 31 16:11:52 ernie kernel: Vendor: Generic Model: USB Storage-SMC Rev:
0207
Dec 31 16:11:52 ernie kernel: Type: Direct-Access ANSI
SCSI revision: 02
Dec 31 16:11:52 ernie kernel: Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
Dec 31 16:11:52 ernie kernel: sda : READ CAPACITY failed.
Dec 31 16:11:52 ernie kernel: sda : status = 1, message = 00, host = 0, driver = 08
Dec 31 16:11:52 ernie kernel: Current sd00:00: sense key Not Ready
Dec 31 16:11:52 ernie kernel: Additional sense indicates Medium not present
Dec 31 16:11:52 ernie kernel: sda : block size assumed to be 512 bytes, disk size 1GB.
Dec 31 16:11:53 ernie kernel: sda: Write Protect is off
Dec 31 16:11:53 ernie kernel: sda: I/O error: dev 08:00, sector 0
Dec 31 16:11:53 ernie kernel: I/O error: dev 08:00, sector 0
Dec 31 16:11:53 ernie kernel: unable to read partition table
Dec 31 16:11:53 ernie kernel: USB Mass Storage support registered.
Dec 31 16:18:44 ernie kernel: sda : READ CAPACITY failed.
Dec 31 16:18:44 ernie kernel: sda : status = 1, message = 00, host = 0, driver = 08
Dec 31 16:18:44 ernie kernel: Current sd00:00: sense key Not Ready
Dec 31 16:18:44 ernie kernel: Additional sense indicates Medium not present
Dec 31 16:18:44 ernie kernel: sda : block size assumed to be 512 bytes, disk size 1GB.
Dec 31 16:18:44 ernie kernel: sda: Write Protect is off
Dec 31 16:18:44 ernie kernel: sda: I/O error: dev 08:00, sector 0
Dec 31 16:18:44 ernie kernel: I/O error: dev 08:00, sector 0
Dec 31 16:18:44 ernie kernel: unable to read partition table
Dec 31 16:18:44 ernie kernel: Device not ready. Make sure there is a disc in the drive.
Dec 31 16:19:39 ernie kernel: sda : READ CAPACITY failed.
Dec 31 16:19:39 ernie kernel: sda : status = 1, message = 00, host = 0, driver = 08
Dec 31 16:19:39 ernie kernel: Current sd00:00: sense key Not Ready
Dec 31 16:19:39 ernie kernel: Additional sense indicates Medium not present
Dec 31 16:19:39 ernie kernel: sda : block size assumed to be 512 bytes, disk size 1GB.
And also there seems to be a huge problem with detecting its size, do you reckon this just isn't compatible with Linux?
The model number on it says:
Code:
CR-V10-U6
I googled for it, and I cant find much support anywhere!
Its locating the device, its just not registering a media presence, that's the exact same read I get from a zip drive with no disk in it. Maybe there are 2 actual device readers in there and its too stupid to work unless the first one has something in it... or somesuch. What do you have in there now? Also, what kernel? 2.4.18 if its base RH I'de wager. A lot of usb device upgrades have made it in since 18.
Im going to try with .20 and upgrade my kernel, Im just lazy and havent rolled my own, also a mate pointed out that I may need:
CONFIG_SCSI_MULTI_LUN enabled and I dont as that allows multi devs. Between us I think we have deduced that the hardware inside should be 4 different SCSI devs, but is only one.
I have the exact same problem with a 6 in 1 reader, dmesg reports there is no disc in the drive, and fdisk cannot find a partition table for /dev/sda
the deal has 4 places to plug in memory cards, the only ones i have tried are a sony memory stick in the 2nd port and a sd card in the 3rd port, same problem for both, same results if there are no memory cards in the thing.
I have the same problem, using a MBO-CardReader.
The Probleme exists after starting of KDE2. Before starting the device works perfectly, but if I started KDE2 the Reader says "no media found" and gives also the following message - according with the first message on top of this page:
# mount /dev/sda1 /mnt
sda: READ CAPACITY failed.
sda : status = 0, message = 00, host = 7, driver = 00
sda : sense not available
sda : block size assumed to be 512 bytes, disk size 1GB.
sda: I/O error: dev 08:00, sector 0
I/O error: dev 08:00, sector 0
unable to read partition table
mount: no media found
#
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.