SlackwareThis Forum is for the discussion of Slackware 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 have a 6 in 1 internal usb 2.0 card reader, and upon boot, my stem finds the device fine, and it is also listed on /proc/bus/usb/devices as 1 device, and shows up with sg3 utils as 1 device, but when i try to mount it i get mount: /dev/sda1 is not a valid block device
i am assuming that it should be showing up as 4 seperate devices for the 4 seperate slots, but i am not positive on that. also i have read stuff about multiple luns, but that requires recompiling the kernal as i am led to believe, is there anyway to access the sd slot on this reader without compiling a new kernal?
still no worky, my thumb drive works fine, though i have to manually mount it myself, but when i try to manually mount the sd card, i get this:
root@Orion:/home/orion# mount -t vfat /dev/sda1 /mnt/sd
mount: /dev/sda1 is not a valid block device
my lilo.conf looks like this:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
append="hdc=ide-scsi hdd=ide-scsi max_scsi_luns=6"
boot = /dev/hda
message = /boot/boot_message.txt
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# VESA framebuffer console @ 1024x768x256
vga = 773
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda3
label = Linux
read-only
# Linux bootable partition config ends
# Windows bootable partition config begins
other = /dev/hda1
label = windows
table = /dev/hda
# Windows bootable paritition config ends
and my dmesg is this:Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
scsi1 : SCSI emulation for USB Mass Storage devices
Vendor: Model: USB 2.0 Reader Rev: 1.05
Type: Direct-Access ANSI SCSI revision: 02
Attached scsi removable disk sda at scsi1, channel 0, id 0, lun 0
sda: Unit Not Ready, sense:
Current 00:00: sns = 70 2
ASC=3a ASCQ= 0
Raw sense data:0x70 0x00 0x02 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x3a 0x00 0x00 0x00 0x00 0x00
sda : READ CAPACITY failed.
sda : status = 1, message = 00, host = 0, driver = 08
Current sd00:00: sns = 70 2
ASC=3a ASCQ= 0
Raw sense data:0x70 0x00 0x02 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x3a 0x00 0x00 0x00 0x00 0x00
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
ldm_validate_partition_table(): Disk read failed.
I/O error: dev 08:00, sector 0
unable to read partition table
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 2
USB Mass Storage support registered.
usb.c: registered new driver usbmouse
input0: Logitech USB Receiver on usb2:2.0
usbmouse.c: v1.6:USB HID Boot Protocol mouse driver
usb.c: registered new driver hiddev
usb.c: registered new driver hid
input: USB HID v1.10 Keyboard [045e:001d] on usb2:4.0
input: USB HID v1.10 Device [045e:001d] on usb2:4.1
hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <vojtech@suse.cz>
hid-core.c: USB HID support drivers
mice: PS/2 mouse device common for all mice
usbdevfs: USBDEVFS_CONTROL failed dev 4 rqt 128 rq 6 len 9 ret -6
usb.c: registered new driver usbkbd
usbkbd.c: :USB HID Boot Protocol keyboard driver
usbdevfs: USBDEVFS_CONTROL failed dev 4 rqt 128 rq 6 len 18 ret -6
usbdevfs: USBDEVFS_CONTROL failed dev 4 rqt 128 rq 6 len 18 ret -6
parport0: PC-style at 0x378 [PCSPP,TRISTATE]
lp0: using parport0 (polling).
[fglrx] Maximum main memory to use for locked dma buffers: 803 MBytes.
[fglrx] module loaded - fglrx 3.7.0 [Dec 18 2003] on minor 0
Fire GL built-in AGP-support
Based on agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 816M
agpgart: Detected an Intel 845G Chipset, no integrated grapics found.
agpgart: Detected Intel i845 G/GL/GV/GE/PE chipset
agpgart: AGP aperture is 64M @ 0xe0000000
Power management callback for AGP chipset installed
[fglrx] AGP detected, AgpState = 0x1f000217 (hardware caps of chipset)
AGP: Found 2 AGPv2 devices
AGP: Doing enable for AGPv2
[fglrx] AGP enabled, AgpCommand = 0x1f000314 (selected caps)
[fglrx] free AGP = 54800384
[fglrx] max AGP = 54800384
[fglrx] free LFB = 116391936
[fglrx] max LFB = 116391936
[fglrx] free Inv = 0
[fglrx] max Inv = 0
[fglrx] total Inv = 0
[fglrx] total TIM = 0
[fglrx] total FB = 0
[fglrx] total AGP = 16384
sda: Unit Not Ready, sense:
Current 00:00: sns = 70 2
ASC=3a ASCQ= 0
Raw sense data:0x70 0x00 0x02 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x3a 0x00 0x00 0x00 0x00 0x00
sda : READ CAPACITY failed.
sda : status = 1, message = 00, host = 0, driver = 08
Current sd00:00: sns = 70 2
ASC=3a ASCQ= 0
Raw sense data:0x70 0x00 0x02 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x3a 0x00 0x00 0x00 0x00 0x00
sda : block size assumed to be 512 bytes, disk size 1GB.
sda: Write Protect is off
sda: I/O error: dev 08:00, sector 0
I/O error: dev 08:00, sector 0
ldm_validate_partition_table(): Disk read failed.
I/O error: dev 08:00, sector 0
unable to read partition table
hub.c: new USB device 00:1d.2-2, assigned address 2
scsi2 : SCSI emulation for USB Mass Storage devices
Vendor: Mobile Model: Drive Rev: 1.11
Type: Direct-Access ANSI SCSI revision: 02
Attached scsi removable disk sdb at scsi2, channel 0, id 0, lun 0
SCSI device sdb: 129024 512-byte hdwr sectors (66 MB)
sdb: Write Protect is off
sdb: sdb1
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 2
where sdb1 is my thumb drive that was plugged in after the system was booted, i will also add that i have tried this by inserting the card both pre and post boot and get the same results. let me know if you need anything else from me to figure this out, im baffled
slack 9.1, stock 2.4xx kernal, and i have the pen drive off for all of this, i just put it in to test it once then took it back out, and its an apacer 6 in 1 reader
Well, sorry for the delay, but yesterday was Valentine's...
Since neither of my Slack boxes have USB, I just installed Slackware 9.0 to my USB-enabled Knoppix box. Using the max_scsi_luns boot option, Slack detected every LUN device on my Acomdata USB 6-in-1 card reader, but failed to mount /dev/sdc1 (my Smartmedia card).
As I wrote in my knoppix.net post, Knoppix detects and mounts (read/write) the USB card reader perfectly. You should try booting Knoppix 3.3 (don't use the early Knoppix 3.4 release yet) and testing your Apacer drive. At the Knoppix CD boot prompt, use the boot option knoppix max_scsi_luns=6 lang=en keyboard=us xkeyboard=us.
Both Knoppix and Slackware load the usbcore, usb-uhci and usb-storage modules by default. I tried fooling around with /etc/rc.d/rc.module in Slack, with no success.
I compared the two kernel config files; the only relevant differences I see are that the options CONFIG_SCSI_CONSTANTS and CONFIG_BLK_DEV_SR_VENDOR are enabled in Knoppix, but disabled in Slackware by default. After googling these options, my guess is that they are needed for vendor-specific SCSI extensions to mount the additional LUNs on the SCSI device.
I checked out the Apacer support site, and your drive is advertised as working with Linux out-of-the-box. Unfortunately, the user manual wasn't available for download. Any insights from that?
Sorry, but I'm not expert enough to provide more advice than the following:
1) Recompile your Slackware kernel and enable the SCSI option "Probe all LUNs"; or
2) Install Knoppix instead. If you choose this option, then do not install the latest Knoppix 3.3 or 3.4. The hard-drive install of Knoppix 3.4 is tricky, and there seems to be a problem with the XFree86 server in the 2004-02-09 version of Knoppix 3.3. I suggest installing the 2003-11-19 version of Knoppix 3.3 or even the 2003-07-26 version of Knoppix 3.2 (which is what I am currently using and it's stable as a rock).
Both Knoppix and Slackware load the usbcore, usb-uhci and usb-storage modules by default. I tried fooling around with /etc/rc.d/rc.module in Slack, with no success.
that statement caught my eye, when i turn on my virtual machine in vmware i get this error:
VMware Workstation has detected the alternate UHCI host controller driver ("uhci") for USB.
Using USB devices within a virtual machine is unsupported with this driver loaded.
Please use the "usb-uhci" UHCI driver instead.
Could that be why this isnt working? and how do i change that? sorry noob to this usb stuff
:
and i understand it was valentines, sorry for makin it look like i was jumpy
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.