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.
I've had a Jumpdrive Pro 2.0 from Lexar for sometime and had it working
perfectly under the stock 2.4.22 kernel that comes with Slack. I've
downloaded kernel 2.6.4 and configured it as I'd like but for the life
of me can't seem to get the Jumpdrive to work.
I've googled both the web and groups and haven't found anything terribly
helpful though I did find hits regarding others having problems with
their Jumpdrives in the 2.6.x kernels but no solutions along with them.
I know it's just me being a bozo and missing something, so I thought I'd
ask here since I'm kind of at my wits end for discovering the solution
on my own.
When I attempt to mount /dev/sda1 /mnt/hd just as I used to under 2.4.22
I get "/dev/sda1 is not a valid block device".
Below is some info I've captured from my system if it helps. I noticed
that the drive is never assigned a device and "WARNING: USB Mass Storage
data integrity not assured".
If anyone has any idea's or hints to send me in the right directions (or
even a direct fix) I would greatly appreciate it.
Thank you,
Brian
----------
USB Related stuff from dmesg w/ usb debugging turned on:
drivers/usb/core/usb.c: registered new driver usbfs
drivers/usb/core/usb.c: registered new driver hub
USB Universal Host Controller Interface driver v2.2
uhci_hcd 0000:00:11.2: UHCI Host Controller
uhci_hcd 0000:00:11.2: irq 21, io base 0000dc00
uhci_hcd 0000:00:11.2: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
uhci_hcd 0000:00:11.3: UHCI Host Controller
uhci_hcd 0000:00:11.3: irq 21, io base 0000d800
uhci_hcd 0000:00:11.3: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
usb 2-2: new full speed USB device using address 2
Initializing USB Mass Storage driver...
usb-storage: USB Mass Storage device detected
usb-storage: act_altsetting is 0, id_index is 91
usb-storage: -- associate_dev
usb-storage: Transport: Bulk
usb-storage: Protocol: Transparent SCSI
usb-storage: Endpoints: In: 0xdf622d40 Out: 0xdf622d54 Int: 0x00000000
(Period 0)
usb-storage: usb_stor_control_msg: rq=fe rqtype=a1 value=0000 index=00 len=1
usb-storage: GetMaxLUN command result is 1, data is 0
usb-storage: *** thread sleeping.
scsi0 : SCSI emulation for USB Mass Storage devices
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Command INQUIRY (6 bytes)
usb-storage: 12 00 00 00 24 00
usb-storage: Bulk Command S 0x43425355 T 0x1 L 36 F 128 Trg 0 LUN 0 CL 6
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
usb-storage: -- transfer complete
usb-storage: Bulk command transfer result=0
usb-storage: usb_stor_bulk_transfer_buf: xfer 36 bytes
usb-storage: Status code 0; transferred 36/36
usb-storage: -- transfer complete
usb-storage: Bulk data transfer result 0x0
usb-storage: Attempting to get CSW...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
usb-storage: Status code 0; transferred 13/13
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x1 R 0 Stat 0x0
usb-storage: scsi cmd done, result=0x0
usb-storage: *** thread sleeping.
Vendor: LEXAR Model: JUMPDRIVE PRO Rev: 0
Type: Direct-Access ANSI SCSI revision: 02
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad target number (1:0)
usb-storage: scsi cmd done, result=0x40000
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad target number (2:0)
usb-storage: scsi cmd done, result=0x40000
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad target number (3:0)
usb-storage: scsi cmd done, result=0x40000
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad target number (4:0)
usb-storage: scsi cmd done, result=0x40000
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad target number (5:0)
usb-storage: scsi cmd done, result=0x40000
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad target number (6:0)
usb-storage: scsi cmd done, result=0x40000
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad target number (7:0)
usb-storage: scsi cmd done, result=0x40000
usb-storage: *** thread sleeping.
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 2
drivers/usb/core/usb.c: registered new driver usb-storage
USB Mass Storage support registered.
----------
lsmod output with the Jumpdrive connected:
I thought I'd include this quick since I probably should have in the first place. Here is the output of lsusb.
Unknown line at line 1809
Duplicate HUT Usage Spec at line 2650
Bus 002 Device 002: ID 05dc:0200 Lexar Media, Inc.
Bus 002 Device 001: ID 0000:0000 Virtual Hub
Bus 001 Device 001: ID 0000:0000 Virtual Hub
That looks fine besides the "data integrity not assured part", are you sure the drive is ok? Does it work fine with your 2.4 kernel(if you still have it isntalled), or Windows?
It's a strange thing isn't it? The drive works perfectly in Windows XP and in kernel 2.4.25 (using that right now), but not in 2.6.x.
So, to answer your question plainly, I'm certain the drive is in good working order.
I did some googling for a while and found what seems to be others having strange issues with USB Mass Storage devices in general in the 2.6.x kernel. But for all my searching I didn't find a solution.
Just wanted to drop a quick note in here to let everyone know I'm still looking into this on my own. I'm not a programmer, so what I can do is kind of limited. I've been looking on Google and Google groups and still only find people having similar problems, but no solutions. Perhaps a bug? Or maybe I need to update something to be compatible with 2.6.x? I'm not sure yet but if I find out I'll post it here.
Of course, if anyone else knows anything or can simply point me in the proper direction I'd appreciate it.
Here's some stuff that's going to come in handy. From http://www.garloff.de/kurt/linux/ - there's a nifty script that will re-scan the SCSI bus for you. Once you download it you will need to make it executable with 'chmod +x rescan-scsi-bus.sh' and then run it ./rescan-scsi-bus.sh
If all goes well you should be able to see the scsi device listed with 'fdisk -l'. If not then we need to go back to kernel-land and see what happened.
As suggested, I ran the script mentioned above, and then "fdisk -l". But still no scsi device shown. Below is the output of my fdisk -l. Would it help if I posted my kernel config? I'm pretty sure I have what I need to make it work, but not 100% sure.
BTW, I always wondered how to see all the drives available on a system. Never thought of fdisk to do it. Thanks for that inadvertent tip.
Brian
Disk /dev/hda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 9729 78148161 7 HPFS/NTFS
Disk /dev/hdb: 30.7 GB, 30735581184 bytes
255 heads, 63 sectors/track, 3736 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hdb1 * 1 3611 29005326 83 Linux
/dev/hdb2 3612 3736 1004062+ 82 Linux swap
Disk /dev/hdd: 20.0 GB, 20020396032 bytes
255 heads, 63 sectors/track, 2434 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hdd1 1 2434 19551073+ c W95 FAT32 (LBA)
Sure thing. If you need any other sections just let me know. Just FYI, I've tried to duplicate the same choices below in my 2.4.25 kernel and am successfull with the jumpdrive. Though, being relatively new to Linux I could easilly have missed something.
# SCSI device support
#
CONFIG_SCSI=m
CONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=m
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
# CONFIG_BLK_DEV_SR is not set
CONFIG_CHR_DEV_SG=m
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_REPORT_LUNS is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_MEGARAID is not set
CONFIG_SCSI_SATA=y
# CONFIG_SCSI_SATA_SVW is not set
CONFIG_SCSI_ATA_PIIX=y
# CONFIG_SCSI_SATA_PROMISE is not set
# CONFIG_SCSI_SATA_VIA is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_CPQFCTS is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
CONFIG_SCSI_QLA2XXX=m
# CONFIG_SCSI_QLA21XX is not set
# CONFIG_SCSI_QLA22XX is not set
# CONFIG_SCSI_QLA2300 is not set
# CONFIG_SCSI_QLA2322 is not set
# CONFIG_SCSI_QLA6312 is not set
# CONFIG_SCSI_QLA6322 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set
# USB support
#
CONFIG_USB=m
# CONFIG_USB_DEBUG is not set
#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_BANDWIDTH is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
#
# USB Host Controller Drivers
#
# CONFIG_USB_EHCI_HCD is not set
# CONFIG_USB_OHCI_HCD is not set
CONFIG_USB_UHCI_HCD=m
#
# USB Device Class drivers
#
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_BLUETOOTH_TTY is not set
# CONFIG_USB_MIDI is not set
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set
CONFIG_USB_STORAGE=m
CONFIG_USB_STORAGE_DEBUG=y
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_DPCM is not set
# CONFIG_USB_STORAGE_HP8200e is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set
#
# USB Human Interface Devices (HID)
#
# CONFIG_USB_HID is not set
#
# USB HID Boot Protocol drivers
#
# CONFIG_USB_KBD is not set
# CONFIG_USB_MOUSE is not set
# CONFIG_USB_AIPTEK is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_KBTAB is not set
# CONFIG_USB_POWERMATE is not set
# CONFIG_USB_XPAD is not set
#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set
# CONFIG_USB_HPUSBSCSI is not set
#
# USB Multimedia devices
#
# CONFIG_USB_DABUSB is not set
#
# Video4Linux support is needed for USB Multimedia device support
#
#
# USB Network adaptors
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set
#
# USB port drivers
#
# CONFIG_USB_USS720 is not set
#
# USB Serial Converter support
#
# CONFIG_USB_SERIAL is not set
#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_TIGL is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_BRLVGER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_TEST is not set
#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set
hey, I viewed your first post just wehn you posted it, was looking to make a jumpdive sport work on my machine (laptop debian kernel 2.4.18 or so... ) I have had the same error messages (sda1 is not a valid block device) and I found when I went to the linux tty (Ctrl-Alt - F1) that when I plugged it the stick into my usb port that it sometimes wouldn't accept the port that it was offered (some output on the shell) I retried a few time umplug and replug and then would get a message that it had been alocated the sda1 finally... (have you tried that)
I know it is a different kernel, etc. (also actually have a look at newsforge article: http://software/03/12/05/2214256.shtml?tid=79&tid=82
that was helpful for me, too, (I still have to plug-unplug, several times, but at least it works...)
I didn't have that problem. Though I did try unplugging and replugging in while watching my dmesg output.
I did finally just get this to work. But not in a way I suspected.
What I did what I actually sat and thought about it logically for a minute and realized that the problem wasn't with the USB since it was being found by USB just fine. However, dmesg was never waying that it was put on any device. So, I figured I would consentrate on the SCSI settings. Well, I compiled everything I possibly could in SCSI as a module figuring that I only use the pendrive every so often and would rather have the free memory. No matter what it still didn't work. In a fit of frustration I decided to actually compile the SCSI drivers directly into the kernel. And BOOM it worked!
So I boiled it down eventually to needing SCSI disk support and SCSI generic support in the kernel. Modules just didn't work. (They worked fine in 2.4.x but not in 2.6.x).
Later on, I noticed the same thing was happening with the printer. I just couldn't print. But I had all the needed stuff as modules as I usually did for the 2.4.x kernel. Compiling those directly in let me print again.
All other module loading works correctly. And I did make sure I got the latest modutils that support 2.6.x.
I don't know why it behaves this way, but finally, I got it to work.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.