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.
Ever since I upgraded my kernel to 2.6.12 I can't read from my chip reader! I'm told that the 'special device sda1 doesn't exist' when it did "exist" on 2.4.26.
Could this be that I installed the wrong chip reader modules?
What does you "dmesg" says? Is the chip reader assigned to "sda1"? Or is the driver find it? Guessing devices will get you nowhere, make sure "sda1" is the correct one before trying to mount.
Originally posted by Half_Elf What does you "dmesg" says? Is the chip reader assigned to "sda1"? Or is the driver find it? Guessing devices will get you nowhere, make sure "sda1" is the correct one before trying to mount.
Well here's the results:
dmesg has nothing related to my chip reader,
I don't know how to assign the chip reader to sda1 and I don't know if it is.
How will I know if the drver finds it?
You can't "assign" your chip reader to sda1 or to any device, it's the driver job to do so.
What are the last few lines of "dmesg" when you plug it? There should be lines saying something like "New usb device found at X" at the very least, otherwise there is something wrong about your kernel (no usb support?).
Here is a sample, from my system, this is what I get when I plug my flash drive :
Quote:
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
scsi0 : SCSI emulation for USB Mass Storage devices
Vendor: Sony Model: Sony DSC Rev: 3.22
Type: Direct-Access ANSI SCSI revision: 02
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 2
USB Mass Storage support registered.
Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sda: 126848 512-byte hdwr sectors (65 MB)
sda: Write Protect is off
/dev/scsi/host0/bus0/target0/lun0: p1
If you see something like the following, then it is possible that the usb-storage driver is missing from your system or it is not activated yet :
Quote:
hub.c: USB new device connect on bus1/1, assigned device number 2
usb.c: USB device 2 is not claimed by any active driver. (The 0x54c/0x10 will be different for different vendors.)
In that case, try to "modprobe usb-storage" then see dmesg again.
If you compiled 2.6.12 yourself, you probably picked USB Block Device or the ub module. The ub module is experimental and there is warnings that it will break usb storage. I enabled it as a I test and the warnining is correct that it breaks or it does not find all partitions on the USB disk. I suggest re-compiling the kernel, but with out this device.
If you see NOTHING about usb, then the USB support is most likely missing from your kernel... Take a look at your options and make sure you haven't forgot something.
Ok I recompiled my kernel without USB Block Device or the ub module.
I also included CONFIG_SCSI_MULTI_LUN=y but still nothing in the output from dmesg.
I rebooted into 2.4 and got output from dmesg.... arrgh!!!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.