I have a USB card reader that handles various card media, like SD cards, Sony Memory Sticks, and two other formats that I can't even remember what they are. I pretty much exclusively use it for SD cards.
With Fedora, when I plugged the card reader into the USB port, and then inserted an SD card, it would automatically come up on the desk top. However, this is not the case with CentOS. Nothing comes up.
Naturally, I searched Google for information, hoping that maybe it was just a matter of downloading an RPM or something. But I did not come across any information that helped.
Is there a setting that I need to activate in order for CentOS to recognize SD Cards and/or the USB card reader?
Dave
On Thu, 2005-07-28 at 21:10 +0900, Dave Gutteridge wrote:
I have a USB card reader that handles various card media, like SD cards, Sony Memory Sticks, and two other formats that I can't even remember what they are. I pretty much exclusively use it for SD cards.
With Fedora, when I plugged the card reader into the USB port, and then inserted an SD card, it would automatically come up on the desk top. However, this is not the case with CentOS. Nothing comes up.
Naturally, I searched Google for information, hoping that maybe it was just a matter of downloading an RPM or something. But I did not come across any information that helped.
Is there a setting that I need to activate in order for CentOS to recognize SD Cards and/or the USB card reader?
Is the usb-storage module loaded?
On Thu, 2005-07-28 at 21:24 +0900, Dave Gutteridge wrote:
Is the usb-storage module loaded?
I don't know. How do I tell?
lsmod | grep ^usb_storage
If not, then 'modprobe usb-storage' should load it.
On Thu, Jul 28, 2005 at 08:33:51AM -0400, Ignacio Vazquez-Abrams enlightened us:
Is the usb-storage module loaded?
I don't know. How do I tell?
lsmod | grep ^usb_storage
If not, then 'modprobe usb-storage' should load it.
You might also try running the dmesg command after plugging an SD card in to see if it is recognized by the system at all.
Matt
You might also try running the dmesg command after plugging an SD card in to see if it is recognized by the system at all.
This is the result of dmesg:
Initializing USB Mass Storage driver... usbcore: registered new driver usb-storage USB Mass Storage support registered. usb 1-1.1: new full speed USB device using address 7 scsi0 : SCSI emulation for USB Mass Storage devices Vendor: BUFFALO Model: CF CARD Reader Rev: 3.06 Type: Direct-Access ANSI SCSI revision: 02 USB Mass Storage device found at 7 Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0 Device not ready. Make sure there is a disc in the drive.
Dave
On Thu, Jul 28, 2005 at 09:45:53PM +0900, Dave Gutteridge enlightened us:
You might also try running the dmesg command after plugging an SD card in to see if it is recognized by the system at all.
This is the result of dmesg:
Initializing USB Mass Storage driver... usbcore: registered new driver usb-storage USB Mass Storage support registered. usb 1-1.1: new full speed USB device using address 7 scsi0 : SCSI emulation for USB Mass Storage devices Vendor: BUFFALO Model: CF CARD Reader Rev: 3.06 Type: Direct-Access ANSI SCSI revision: 02 USB Mass Storage device found at 7 Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0 Device not ready. Make sure there is a disc in the drive.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Looks like that's the root of your problem. Why that's the case, I'm not sure. I don't have any external readers like that, so perhaps someone else with a little more experience with them can point you in the right direction. Googling the error might help as well.
Matt
On Jul 28, 2005, at 8:45 AM, Dave Gutteridge wrote:
Initializing USB Mass Storage driver... usbcore: registered new driver usb-storage USB Mass Storage support registered. usb 1-1.1: new full speed USB device using address 7 scsi0 : SCSI emulation for USB Mass Storage devices Vendor: BUFFALO Model: CF CARD Reader Rev: 3.06 Type: Direct-Access ANSI SCSI revision: 02 USB Mass Storage device found at 7 Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0 Device not ready. Make sure there is a disc in the drive.
good! this is the system telling you that it sees the card reader as /dev/sda (you get that from "scsi removable disk sda").
try inserting a SD card and then running a command like "fdisk -l / dev/sda" (which should, ideally, give you a listing of the partition table on the SD card). individual partitions on the card will be referenced as /dev/sda1, /dev/sda2 etc. hopefully there'll be only one partition, so you can try the following set of commands:
# mkdir /mnt/sdcard # mount /dev/sdaX /mnt/sdcard (replace "X" with the partition number you gleaned from fdisk)
if you get an error about filesystem type, try again:
# mount -t auto /dev/sdaX /mnt/sdcard
then do a "df" to see if the system sees a volume mounted on /mnt/ sdcard.
if all this works, you can start configuring your system to automatically mount SD cards when they are inserted, but that's a topic beyond the scope of this message.
-steve
--- If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v
I did the following:
[root@localhost codecs]# modprobe usb-storage [root@localhost codecs]# lsmod | grep ^usb_storage usb_storage 61193 0 [root@localhost codecs]#
And now when I plug in the card reader, I can hear the hard drive make some noises indicating that some kind of response is happening.
However, when I put a card into the card reader, nothing happens. I tried putting the card in after connecting the USB cable, and also after, just for experiments sake. Still, nothing happens.
Dave
On Thursday 28 July 2005 08:38, Dave Gutteridge wrote:
However, when I put a card into the card reader, nothing happens. I tried putting the card in after connecting the USB cable, and also after, just for experiments sake. Still, nothing happens.
I think it's up to *you* to make stuff happen then.
When I insert a CDROM, nothing happens unless I make it happen. For example, when I try to browse it, stuff happens.
I think it's up to *you* to make stuff happen then.
When I insert a CDROM, nothing happens unless I make it happen. For example, when I try to browse it, stuff happens.
How do I do that if no icon comes up, or there is no place to browse within the file system? If there is some location that I'm supposed to know of where the SD card should have shown up, then please let me know where that is.
Dave
Dave Gutteridge dave@tokyocomedy.com wrote:
How do I do that if no icon comes up, or there is no place to browse within the file system? If there is some location that I'm supposed to know of where the SD card should have shown up, then please let me know where that is.
Dave:
This is one area where UNIX and Windows differ, and I must say, UNIX is _much_safer_. I'll explain (to other people: killfile me if you want).
- Buffering, Caching, Commits and Applications ...
With read-only CDs (CD-ROM/R) and DVDs (DVD-ROM/R), this hasn't been much of an issue on Windows. Once you start using rewritable media, it comes a real issue. Some CD rewritable programs mititgate it for CD-RW, DVD-RAM/RW/+RW, but the "old floppy issue" that cost companies billions in lawsuits is starting to plague USB devices again.
It's not the drives or media, but the OS' approach.
When you access a re-writable device in an OS, the OS begins to cache information. As long is it is read-only, it is typically okay. If you're just copying files, you're typically okay.
Once you start writing to the device, buffers are filled in memory before the data is actually committed to the device. If there is advanced caching operations, this can be even dozens of seconds, especially on slow Electrically Erasable Programmable Read-Only Memory (EEPROM aka "Flash"). If we didn't do that, you're system would _crawl_ as it would have to commit data continuously -- especially to slow floppies, EEPROM and, although to lesser extent in newer products, optical drives.
The problem with most Windows applications, as Visual Studio creates them by default (among other development suites), is that they believe they always have write access to any location (SIDE NOTE: as well as a "default directory" -- a key difference in UNIX/Windows security, UNIX only assumes write access to a user home directory). So even if you're just reading photos in a viewer, many times it opens the file read/write. It could also be storing temporary files if the developer wasn't paying attention to detail. And Windows itself doesn't have mechnisms to disable some buffering/cache functions (I needed to do so for a military application -- result: we couldn't use Windows NT/2000 at the time).
Like floppy drives before it, Microsoft does _not_ have a formal "unmount" function that guarantees buffers/cache will be flushed. Not only that, but Microsoft _always_ mounts things when they are first inserted as of MS-DOS 7.x (Windows 95+), and _always_ re-write if possible. As such, the filesystem could be left in an inconsistent state. And as we all know, FAT12/16/32 is not very recoverable, and data is typically lost -- sometimes totally corrupted if it is not flushed and consistent.
As such, it's highly recommended you disable "auto-launch" for this reason. Prior to Windows, MS-DOS wasn't too bad because even SMARTDRV.EXE would only "read-cache" for floppy disks, meaning that it _always_ committed to disk immediately. But under MS-DOS 7 (Windows 95/98/Me) and MS-NT (Windows NT/2000/XP), the OSes no longer do this and use the logic as above.
- UNIX formalizes mount/unmount
In the UNIX world, this is why we use a formal mount and unmount. We don't want to mount something until we're ready to use it (and possibly modify it) and, more importantly, we want to make sure that we flush the buffers and leave the disk consistent. UNIX also offers a "read-only" mode, something that Microsoft does not. That way you can guarantee the device is _not_ modified, even if a read/write media.
[ SIDE NOTE: In fact, most Linux distros mount CD/DVD media _explictly_ read-only by default, even rewritable media. If you want otherwise, you have to explictly add another fstab or automounter entry. ]
Now UNIX/Linux _does_ have some "automation" features. There are a few of them (some more "Windows-like" and semi-deadly than others -- especially the GUI services ;-), but in the FC/RHEL/CentOS world, we use the "automounter." It is very useful for many things, but "out-of-the-box," it's typically used for CD/DVDs.
In a nutshell, the automounter (autofs in FC/RHEL/CentOS) is a kernel-level function. When someone enters a directory designated as an automounted directory, the kernel automatically mounts the specified device -- be it a remote network share, a local disk or, in the default cause, the local CD device (if the system has one at install-time).
Automounter also has a "time-out," typically 30 seconds. That means after 30 seconds of inactivity, it will automatically unmount. The device. If you don't want to wait, you can always use the "umount" (no "n") manually, or right click on the icon on your desktop (if it was mounted that way). GNOME (what I use) even has an "applet" on the system trap that let's you "click mount/umount" filesystems (assuming, of course, the user has access to do so in /etc/fstab with the "user" option or another).
Until a device is umount'd, Linux will _not_ allow you to eject it -- at least when the eject is "digital/logical" and not physical. This is also unlike Windows, which gives you the "please put the media back in b'tch" non-sense even when you don't understand why (something UNIX, let alone Macs, avoid nicely ;-).
Unfortunately, that doesn't stop the problem when drives allow you to "physically eject" or "pull out" such as floppy drives (except on a Mac) or EEPROM card readers. If you don't umount, expect corruption, just like Windows users run into regularly. The difference between Windows and UNIX is that there is a formal "umount" function -- be it manual, or automated with something like automounter and its timeout.
For UNIX die-hards, we _hate_ the concept of automatically mounting removable media. That's why I disable the CD recorder for automount -- both at the kernel (via autofs) and GUI levels (GNOME, KDE, etc...).
On Thursday 28 July 2005 10:11, Dave Gutteridge wrote:
How do I do that if no icon comes up, or there is no place to browse within the file system? If there is some location that I'm supposed to know of where the SD card should have shown up, then please let me know where that is.
In KDE there is a nice device icon that automatically appears on the desktop. I just click it and it works automagically. Maybe you're using GNOME because that's the default on CentOS (too bad!), so you should switch to KDE. Just choose KDE in the menu at the bottom of the screen when loggin in.
On Thu, 2005-07-28 at 11:01 -0400, Simon Perreault wrote:
On Thursday 28 July 2005 10:11, Dave Gutteridge wrote:
How do I do that if no icon comes up, or there is no place to browse within the file system? If there is some location that I'm supposed to know of where the SD card should have shown up, then please let me know where that is.
In KDE there is a nice device icon that automatically appears on the desktop. I just click it and it works automagically. Maybe you're using GNOME because that's the default on CentOS (too bad!), so you should switch to KDE. Just choose KDE in the menu at the bottom of the screen when loggin in.
KDE won't help if the device is not seen as being present...
On Thu, 2005-07-28 at 08:05 -0500, Matt Hyclak wrote:
On Thu, Jul 28, 2005 at 09:45:53PM +0900, Dave Gutteridge enlightened us:
You might also try running the dmesg command after plugging an SD
card in
to see if it is recognized by the system at all.
This is the result of dmesg:
Initializing USB Mass Storage driver... usbcore: registered new driver usb-storage USB Mass Storage support registered. usb 1-1.1: new full speed USB device using address 7 scsi0 : SCSI emulation for USB Mass Storage devices Vendor: BUFFALO Model: CF CARD Reader Rev: 3.06 Type: Direct-Access ANSI SCSI revision: 02 USB Mass Storage device found at 7 Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0 Device not ready. Make sure there is a disc in the drive.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Looks like that's the root of your problem. Why that's the case, I'm not sure. I don't have any external readers like that, so perhaps someone else with a little more experience with them can point you in the right direction. Googling the error might help as well.
Had similar problems with a USB external disk a while back. Worked with the FC2 kernel but not with WBEL3 (equivalent to CentOS3). A kernel update finally fixed the problem. Are you up to date with the latest kernel? The CentOSplus kernel might be worth a try:
# yum --enablerepo=centosplus update kernel
To state the obvious (but perhaps not one still undergoing Windows withdrawal :-), you will need to reboot to get the new kernel.
Have rebuilt FC kernels on CentOS to get otherwise unsupported devices working, but hopefully won't have to go there.
Isn't this fun? :-( Too bad it doesn't "just work" [TM]. )-:
Phil
On Fri, 2005-07-29 at 13:55 +0900, Dave Gutteridge wrote:
The CentOSplus kernel might be worth a try
What makes a CentOSplus kernel different? It's not some kind of experimental, bleeding edge version is it? I've had enough of experimentation...
Dave-
It has a lot of additional features enabled. It is the same base kernel with more options enabled. The additional features are detailed in
http://mirror.centos.org/centos/4.1/centosplus/Readme.txt
c'mon Dave, don't give us that s**t, you have picked up linux better than anyone I know in 3 weeks, your experimentation is going to be invaluable to us in the long term :D none of centos is bleeding adge, the developers here are top notch!
tom
Dave Gutteridge wrote:
The CentOSplus kernel might be worth a try
What makes a CentOSplus kernel different? It's not some kind of experimental, bleeding edge version is it? I've had enough of experimentation...
Dave
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
# yum --enablerepo=centosplus update kernel
I tried this, but unfortunately it was unsuccessful:
[root@localhost ~]# yum --enablerepo=centosplus update kernel Repository update already added, not adding again Error getting repository data for centosplus, repository not found
I thought since I added in the whole "dag" repository that I should have a fairly complete set of install options to choose from. To get centosplus, do I have to add more repositories or something?
Dave
On Sun, 2005-07-31 at 16:58 +0900, Dave Gutteridge wrote:
# yum --enablerepo=centosplus update kernel
I tried this, but unfortunately it was unsuccessful:
[root@localhost ~]# yum --enablerepo=centosplus update kernel Repository update already added, not adding again Error getting repository data for centosplus, repository not found
I thought since I added in the whole "dag" repository that I should have a fairly complete set of install options to choose from. To get centosplus, do I have to add more repositories or something?
Dave _______________________________________________
The standard CentOS-Base.repo file in /etc/yum.repos.d/ for CentOS-4 should have the centosplus repo in it, just not enabled.
This would only work on CentOS-4 ...
I just tested that line and it does work on a CentOS-4 install.
I was successful in getting centosplus installed, and it has had some effect. CentOS now recognizes an external hard drive that my friend had lent me, which is nice.
However, it still does not acknowledge my SD card reader.
Is there anything else I can do? There must be some kind of support available, even if it's bleeding edge, as my SD card reader was possible in Fedora Core 4.
Dave
On Tue, 2005-08-02 at 10:15 +0900, Dave Gutteridge wrote:
I was successful in getting centosplus installed, and it has had some effect. CentOS now recognizes an external hard drive that my friend had lent me, which is nice.
However, it still does not acknowledge my SD card reader.
Is there anything else I can do? There must be some kind of support available, even if it's bleeding edge, as my SD card reader was possible in Fedora Core 4.
---- haven't been tracking what you've tried and haven't tried but what does tail /var/log/dmesg output just a few seconds after you insert the SD card? Is there anything on the card of value? Can you reformat it without losing anything of value? Sometimes the vfat partitions are properly created
Craig
On Mon, 2005-08-01 at 20:18 -0700, Craig White wrote:
On Tue, 2005-08-02 at 10:15 +0900, Dave Gutteridge wrote:
I was successful in getting centosplus installed, and it has had some effect. CentOS now recognizes an external hard drive that my friend had lent me, which is nice.
However, it still does not acknowledge my SD card reader.
Is there anything else I can do? There must be some kind of support available, even if it's bleeding edge, as my SD card reader was possible in Fedora Core 4.
Well, could try building the latest FC3 or FC4 kernel under CentOS. I ran a rebuild generic kernel, then later an FC3 kernel, for a few months on one machine to get support for a too-new SATA controller until the RHEL4 kernel caught up.
haven't been tracking what you've tried and haven't tried but what does tail /var/log/dmesg output just a few seconds after you insert the SD card?
For some reason that doesn't give anything just after inserting a USB device, but just the command "dmesg" does.
Can also try (as root):
# tail -f /var/log/messages
then insert card. (Ctrl-C to exit - otherwise runs "forever".)
If something shows up in the output, try
# fdisk -l
and (think I suggested this earlier, but the centosplus kernel man yave made a difference)
# tail /etc/fstab
and report results. If there is a new entry try mounting it as a user or as root.
Is there anything on the card of value? Can you reformat it without losing anything of value? Sometimes the vfat partitions are properly created
That may be worth a try if other things fail, but the fact that you could use it under FC4 would tend to indicate a driver rather than a format problem.
Phil
Well, could try building the latest FC3 or FC4 kernel under CentOS.
Hmm... I'm wary of that since there were so many other issues with Fedora that I encountered which motivated me to come to CentOS in the first place.
Can also try (as root): # tail -f /var/log/messages then insert card. (Ctrl-C to exit - otherwise runs "forever".)
Nothing happens if I run the command and then insert a card. However, if I remove the card reader from the USB Port and put it back in, I get this:
Aug 2 19:34:51 localhost kernel: usb 1-1.1: new full speed USB device using address 9 Aug 2 19:34:51 localhost kernel: scsi2 : SCSI emulation for USB Mass Storage devices Aug 2 19:35:03 localhost kernel: Vendor: BUFFALO Model: CF CARD Reader Rev: 3.06 Aug 2 19:35:03 localhost kernel: Type: Direct-Access ANSI SCSI revision: 02 Aug 2 19:35:03 localhost kernel: Attached scsi removable disk sdb at scsi2, channel 0, id 0, lun 0 Aug 2 19:35:04 localhost scsi.agent[4367]: disk at /devices/pci0000:00/0000:00:1f.2/usb1/1-1/1-1.1/1-1.1:1.0/host2/target2:0:0/2:0:0:0 Aug 2 19:35:06 localhost kernel: Device not ready. Make sure there is a disc in the drive.
Judging by that last line, it might seem as though something is wrong with the card. So I tested other cards, and also verified that the cards could be read by both Windows and my Palm Pilot. The cards definitely have data on them. It's CentOS that can not read them.
If something shows up in the output, try
# fdisk -l
Here is the output from that:
[root@localhost dave]# fdisk -l Disk /dev/hda: 30.0 GB, 30020272128 bytes 255 heads, 63 sectors/track, 3649 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 3649 29310561 7 HPFS/NTFS Disk /dev/hdb: 30.7 GB, 30738677760 bytes 255 heads, 63 sectors/track, 3737 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdb1 * 1 3644 29270398+ 83 Linux /dev/hdb2 3645 3737 747022+ f W95 Ext'd (LBA) Disk /dev/sda: 40.0 GB, 40007761920 bytes 255 heads, 63 sectors/track, 4864 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 1 4864 39070048+ c W95 FAT32 (LBA)
and (think I suggested this earlier, but the centosplus kernel man yave made a difference) # tail /etc/fstab
[root@localhost dave]# tail /etc/fstab LABEL=/ / ext3 defaults 1 1 none /dev/pts devpts gid=5,mode=620 0 0 none /dev/shm tmpfs defaults 0 0 none /proc proc defaults 0 0 none /sys sysfs defaults 0 0 /dev/VolGroup00/LogVol01 swap swap defaults 0 0 /dev/hdd /media/cdrom auto pamconsole,exec,noauto,managed 0 0 /dev/hdc /media/cdrecorder auto pamconsole,exec,noauto,managed 0 0 /dev/sda1 /media/HD_40GB vfat pamconsole,exec,noauto,managed 0 0 /dev/fd0 /media/floppy auto pamconsole,exec,noauto,managed 0 0
It's all Greek to me. But I don't see anything that looks like an SD card in there.
Dave
On Tue, 2005-08-02 at 19:40 +0900, Dave Gutteridge wrote:
Well, could try building the latest FC3 or FC4 kernel under CentOS.
Hmm... I'm wary of that since there were so many other issues with Fedora that I encountered which motivated me to come to CentOS in the first place.
Can also try (as root): # tail -f /var/log/messages then insert card. (Ctrl-C to exit - otherwise runs "forever".)
Nothing happens if I run the command and then insert a card. However, if I remove the card reader from the USB Port and put it back in, I get this:
Aug 2 19:34:51 localhost kernel: usb 1-1.1: new full speed USB device using address 9 Aug 2 19:34:51 localhost kernel: scsi2 : SCSI emulation for USB Mass Storage devices Aug 2 19:35:03 localhost kernel: Vendor: BUFFALO Model: CF CARD Reader Rev: 3.06 Aug 2 19:35:03 localhost kernel: Type: Direct-Access ANSI SCSI revision: 02 Aug 2 19:35:03 localhost kernel: Attached scsi removable disk sdb at scsi2, channel 0, id 0, lun 0 Aug 2 19:35:04 localhost scsi.agent[4367]: disk at /devices/pci0000:00/0000:00:1f.2/usb1/1-1/1-1.1/1-1.1:1.0/host2/target2:0:0/2:0:0:0 Aug 2 19:35:06 localhost kernel: Device not ready. Make sure there is a disc in the drive.
Judging by that last line, it might seem as though something is wrong with the card. So I tested other cards, and also verified that the cards could be read by both Windows and my Palm Pilot. The cards definitely have data on them. It's CentOS that can not read them.
If something shows up in the output, try
# fdisk -l
Here is the output from that:
[root@localhost dave]# fdisk -l Disk /dev/hda: 30.0 GB, 30020272128 bytes 255 heads, 63 sectors/track, 3649 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 3649 29310561 7 HPFS/NTFS Disk /dev/hdb: 30.7 GB, 30738677760 bytes 255 heads, 63 sectors/track, 3737 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdb1 * 1 3644 29270398+ 83 Linux /dev/hdb2 3645 3737 747022+ f W95 Ext'd (LBA) Disk /dev/sda: 40.0 GB, 40007761920 bytes 255 heads, 63 sectors/track, 4864 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 1 4864 39070048+ c W95 FAT32 (LBA)
---- unless /dev/sda1 was something else, it appears that this was your card and thus when you pushed it in, then pulled it out - it then saw that /dev/sda was already in use so the second time, it tried to assign it /dev/sdb where it failed.
You might simply want to reboot...
mkdir /home/sdcard # insert the card/card reader mount /dev/sda1 /home/sdcard ls -l /home/sdcard
and I would guess that you would see something there.
of course this is as root and if you got that far, you could then create the entry to /etc/fstab to allow mounting (or automount) as a user.
Craig
On Tue, 2005-08-02 at 05:23 -0700, Craig White wrote:
On Tue, 2005-08-02 at 19:40 +0900, Dave Gutteridge wrote:
Well, could try building the latest FC3 or FC4 kernel under CentOS.
Hmm... I'm wary of that since there were so many other issues with Fedora that I encountered which motivated me to come to CentOS in the first place.
Yes - understood.
Can also try (as root): # tail -f /var/log/messages then insert card. (Ctrl-C to exit - otherwise runs "forever".)
Nothing happens if I run the command and then insert a card. However, if I remove the card reader from the USB Port and put it back in, I get this:
Aug 2 19:34:51 localhost kernel: usb 1-1.1: new full speed USB device using address 9 Aug 2 19:34:51 localhost kernel: scsi2 : SCSI emulation for USB Mass Storage devices Aug 2 19:35:03 localhost kernel: Vendor: BUFFALO Model: CF CARD Reader Rev: 3.06 Aug 2 19:35:03 localhost kernel: Type: Direct-Access ANSI SCSI revision: 02 Aug 2 19:35:03 localhost kernel: Attached scsi removable disk sdb at scsi2, channel 0, id 0, lun 0 Aug 2 19:35:04 localhost scsi.agent[4367]: disk at /devices/pci0000:00/0000:00:1f.2/usb1/1-1/1-1.1/1-1.1:1.0/host2/target2:0:0/2:0:0:0 Aug 2 19:35:06 localhost kernel: Device not ready. Make sure there is a disc in the drive.
Looks familiar - so, presuming you are running the centosplus unsupported kernel, it is no help.
Judging by that last line, it might seem as though something is wrong with the card. So I tested other cards, and also verified that the cards could be read by both Windows and my Palm Pilot. The cards definitely have data on them. It's CentOS that can not read them.
Yes - still looks like a kernel-driver problem.
If something shows up in the output, try
# fdisk -l
Here is the output from that:
[root@localhost dave]# fdisk -l Disk /dev/hda: 30.0 GB, 30020272128 bytes 255 heads, 63 sectors/track, 3649 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 3649 29310561 7 HPFS/NTFS Disk /dev/hdb: 30.7 GB, 30738677760 bytes 255 heads, 63 sectors/track, 3737 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdb1 * 1 3644 29270398+ 83 Linux /dev/hdb2 3645 3737 747022+ f W95 Ext'd (LBA) Disk /dev/sda: 40.0 GB, 40007761920 bytes 255 heads, 63 sectors/track, 4864 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 1 4864 39070048+ c W95 FAT32 (LBA)
unless /dev/sda1 was something else, it appears that this was your card and thus when you pushed it in, then pulled it out - it then saw that /dev/sda was already in use so the second time, it tried to assign it /dev/sdb where it failed.
I thought that could be it until noticing the 40.0 GB capacity.
You might simply want to reboot...
mkdir /home/sdcard # insert the card/card reader mount /dev/sda1 /home/sdcard ls -l /home/sdcard
and I would guess that you would see something there.
of course this is as root and if you got that far, you could then create the entry to /etc/fstab to allow mounting (or automount) as a user.
Don't think so - the device is not showing up, so it can't be mounted.
Should have asked before: What does "lsusb" show? Might find something by googling the USB device information.
Phil
I thought that could be it until noticing the 40.0 GB capacity.
Correct, the 40GB thing is not my card reader, but it's an external hard drive connected by firewire.
Should have asked before: What does "lsusb" show? Might find something by googling the USB device information.
[root@localhost dave]# lsusb Bus 001 Device 008: ID 0b28:1002 Kenwood Corp. Bus 001 Device 007: ID 0b28:1001 Kenwood Corp. Bus 001 Device 006: ID 04a9:2207 Canon, Inc. CanoScan 1220U Bus 001 Device 005: ID 056a:0013 Wacom Co., Ltd Bus 001 Device 004: ID 0411:0059 MelCo., Inc. Bus 001 Device 003: ID 03eb:3301 Atmel Corp. 4-port Hub Bus 001 Device 002: ID 0451:1446 Texas Instruments, Inc. TUSB2040/2070 Hub Bus 001 Device 001: ID 0000:0000
I think the card reader is listed under "Melco". My card reader is a "Buffalo" brand card reader, but I looked Melco up on the net, and it seems like the two brands are the same company.
There's one other oddity here: Why is my Kenwood Audio device (a stereo that I can play computer audio with) showing up twice?
Anyway, the Kenwood is working fine, so if it ain't broke... More importantly, is there anything I can do with this information about the Melco thing?
Dave
On Wed, 2005-08-03 at 11:52 +0900, Dave Gutteridge wrote:
I thought that could be it until noticing the 40.0 GB capacity.
Correct, the 40GB thing is not my card reader, but it's an external hard drive connected by firewire.
Should have asked before: What does "lsusb" show? Might find something by googling the USB device information.
[root@localhost dave]# lsusb Bus 001 Device 008: ID 0b28:1002 Kenwood Corp. Bus 001 Device 007: ID 0b28:1001 Kenwood Corp. Bus 001 Device 006: ID 04a9:2207 Canon, Inc. CanoScan 1220U Bus 001 Device 005: ID 056a:0013 Wacom Co., Ltd Bus 001 Device 004: ID 0411:0059 MelCo., Inc. Bus 001 Device 003: ID 03eb:3301 Atmel Corp. 4-port Hub Bus 001 Device 002: ID 0451:1446 Texas Instruments, Inc. TUSB2040/2070 Hub Bus 001 Device 001: ID 0000:0000
I think the card reader is listed under "Melco". My card reader is a "Buffalo" brand card reader, but I looked Melco up on the net, and it seems like the two brands are the same company.
Yup - my "Memorex" USB key shows up as "Trek Technology (S) PTE, Ltd"
There's one other oddity here: Why is my Kenwood Audio device (a stereo that I can play computer audio with) showing up twice?
Dunno - Perhaps command and data channels?
Anyway, the Kenwood is working fine, so if it ain't broke... More importantly, is there anything I can do with this information about the Melco thing?
Googling with the additional info got me nothing definitive. Only thing so far that seemed potentially relevant was about a memory card in an 8- in-1 card reader:
So in short: Try adding this line to your /etc/modprobe.conf file:
options scsi_mod max_luns=8
Worth a shot.
Phil
So in short: Try adding this line to your /etc/modprobe.conf file: options scsi_mod max_luns=8 Worth a shot.
I missed that suggestion when it first came around. I did that... and it works!! Nice.
Now, the thing is I can access the SD Card by browsing for it in Konquerer (Is that what the file explorer is called in KDE?). But it doesn't come up on the desktop. To make it show up on the desktop automatically when I put a card in, is there a setting I can do for that?
Which actually brings me to a related question. In KDE, when I log in, I have my two DVD drives already on the desktop (as disk icons), regardless of whether or not there are disks in the drive. Is there a way I can have them not be there, and only appear on the desktop when I put in a disc?
Dave
Dave Gutteridge wrote:
So in short: Try adding this line to your /etc/modprobe.conf file: options scsi_mod max_luns=8 Worth a shot.
I missed that suggestion when it first came around. I did that... and it works!! Nice.
Now, the thing is I can access the SD Card by browsing for it in Konquerer (Is that what the file explorer is called in KDE?). But it doesn't come up on the desktop. To make it show up on the desktop automatically when I put a card in, is there a setting I can do for that?
Which actually brings me to a related question. In KDE, when I log in, I have my two DVD drives already on the desktop (as disk icons), regardless of whether or not there are disks in the drive. Is there a way I can have them not be there, and only appear on the desktop when I put in a disc?
Dave
Thanks to all involved in this thread for answering my questions a week before I asked.
As far as icons on the desktop... When I was doing battle with my Lexar multi-card reader I tried it on another box I have, running FC4 -- kernel 2.6.12-1.1398_FC4 and KDE 3.4.0-6 Red Hat. KDE did, indeed, display an icon when the reader was connected and removed the icon when the reader was unplugged.
I do not get the icon on this CentOS machine, running kernel 2.6.9-11.EL and KDE 3.3.1-3.10 Red Hat. Personally, I don't care 'cause I'm gonna write a script to find the reader, mount it, mv the images to hard drive and umount when finished.
-
Bryan J. Smith -
Craig White -
Dave Gutteridge -
Ignacio Vazquez-Abrams -
Johnny Hughes -
Matt Hyclak -
Phil Schaffner -
Phil Schaffner -
Robert -
Sean O'Connell -
Simon Perreault -
Steve Huff -
Tom