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 used many other distros from RH/FC, Mandriva, Ubuntu, knoppix and others and I have had no problem getting my USB flashdrive to work. If it has not worked from install then I've been able to tweak /etc/fstab and get the device mounted.
This is not working in Slackware 11 though (2.4.33.3 Kernel).
I have tried using:
Code:
/dev/sda1 /media/flashdrive auto defaults,users,noauto 0 0
and then
Code:
/dev/sda2 /media/flashdrive auto defaults,users,noauto 0 0
in /etc/fstab. This doesn't seem to work/mount.
Here is some output from a manual mount:
Code:
root@holly-desktop:~# mount -t auto /dev/sda2 /media/flashdrive
mount: /dev/sda2 is not a valid block device
root@holly-desktop:~# mount -t auto /dev/sda1 /media/flashdrive
mount: /dev/sda1 is not a valid block device
root@holly-desktop:~#
How does Slack recognise this device?
Also here is the (end part) output of dmesg:
Code:
hub.c: new USB device 00:07.4-2, assigned address 2
usb.c: USB device 2 (vend/prod 0xea0/0x2168) is not claimed by any active driver.
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
scsi1 : SCSI emulation for USB Mass Storage devices
Vendor: Generic Model: USB Flash Disk Rev: 2.00
Type: Direct-Access ANSI SCSI revision: 02
Attached scsi removable disk sda at scsi1, channel 0, id 0, lun 0
SCSI device sda: 511488 512-byte hdwr sectors (262 MB)
sda: Write Protect is off
sda: unknown partition table
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 2
USB Mass Storage support registered.
I have found handling of flash drives more reliable in 2.6 than 2.4. The upgrade is simply a matter of installing packkages from /extras/ in the installation disc.
I have used many other distros from RH/FC, Mandriva, Ubuntu, knoppix and others and I have had no problem getting my USB flashdrive to work. If it has not worked from install then I've been able to tweak /etc/fstab and get the device mounted.
This is not working in Slackware 11 though (2.4.33.3 Kernel).
I have tried using:
Code:
/dev/sda1 /media/flashdrive auto defaults,users,noauto 0 0
and then
Code:
/dev/sda2 /media/flashdrive auto defaults,users,noauto 0 0
in /etc/fstab. This doesn't seem to work/mount.
Here is some output from a manual mount:
Code:
root@holly-desktop:~# mount -t auto /dev/sda2 /media/flashdrive
mount: /dev/sda2 is not a valid block device
root@holly-desktop:~# mount -t auto /dev/sda1 /media/flashdrive
mount: /dev/sda1 is not a valid block device
root@holly-desktop:~#
How does Slack recognise this device?
Also here is the (end part) output of dmesg:
Code:
hub.c: new USB device 00:07.4-2, assigned address 2
usb.c: USB device 2 (vend/prod 0xea0/0x2168) is not claimed by any active driver.
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
scsi1 : SCSI emulation for USB Mass Storage devices
Vendor: Generic Model: USB Flash Disk Rev: 2.00
Type: Direct-Access ANSI SCSI revision: 02
Attached scsi removable disk sda at scsi1, channel 0, id 0, lun 0
SCSI device sda: 511488 512-byte hdwr sectors (262 MB)
sda: Write Protect is off
sda: unknown partition table
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 2
USB Mass Storage support registered.
Filesystem type(s): We'll assume that a USB device can have either a Linux ext3 or a DOS/Windows FAT filesystem. (You could've set the filesystem type to auto, but on certain systems this seems to prevent normal users from mounting USB devices with FAT filesystems. If you have the need to use a USB device with something other than ext3 and FAT, just add the type to the list – but it's rather unlikely you'll encounter anything like that.)
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 2
seems like the device is /dev/sda2,
first try $mount and c what all are mounted. since you have an entry in fstab you dont need to type all teh commands," mount /media/flashdrive " is enough. make sure /media/flashdrive exists.
after plugging in usb, do "rescan-scsi-bus -l "
I have found handling of flash drives more reliable in 2.6 than 2.4. The upgrade is simply a matter of installing packkages from /extras/ in the installation disc.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.