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.
/dev/hda3 on / type reiserfs (rw)
proc on /proc type proc (rw)
/dev/hda4 on /home type reiserfs (rw)
/dev/hda5 on /wind type vfat (rw,umask=000)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
usbfs on /proc/bus/usb type usbfs (rw)
When doing mount /mnt/muvo I get an "mount: /dev/sr1: unknown device" error. Apprently the device is not located at where I thought. How do I figure out where it is?
you can change the numbers
it's possible to find the right one if you connect your device and power it on.
after type dmesg and you could receive something like:
hub.c: new USB device 00:14.2-2, assigned address 2
usb.c: USB device 2 (vend/prod 0x3579/0x6901) 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: DM 334 Model: USB Reader Rev: 3.36
Type: Direct-Access ANSI SCSI revision: 02
Attached scsi removable disk sda at scsi1, channel 0, id 0, lun 0
SCSI device sda: 29440 512-byte hdwr sectors (15 MB)
sda: Write Protect is off
sda: sda1
also try with auto for the file system
mount this way
mkdir /mnt/usbdevice
mount -t auto /dev/sda1 /mnt/usbdevice
do it as root firstly
if you achieve a success, put in fstab
/dev/sda1 /mnt/usbdevice auto defaults,noauto,user 0 0
and later you'll be able to mount just typing mount /mnt/usbdevice or if you're using gnome with right mouse click on the desktop, disks, usbdevice
there is a possibility that there is no filesystem - you should create it
From dmesg when pugging the muvo in (not sure how much of it is relevant, so pasted all that appeared to concern usb):
usb-ohci.c: USB OHCI at membase 0xe0f57000, IRQ 11
usb-ohci.c: usb-00:02.3, Silicon Integrated Systems [SiS] USB 1.0 Controller (#2)
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 3 ports detected
PCI: Found IRQ 11 for device 00:02.2
usb-ohci.c: USB OHCI at membase 0xe0f59000, IRQ 11
usb-ohci.c: usb-00:02.2, Silicon Integrated Systems [SiS] USB 1.0 Controller
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 3 ports detected
uhci.c: USB Universal Host Controller Interface driver v1.1
usb-uhci.c: $Revision: 1.275 $ time 17:55:05 Jun 13 2004
usb-uhci.c: High bandwidth mode enabled
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
eth0: Media Link On 100mbps full-duplex
spurious 8259A interrupt: IRQ7.
hub.c: new USB device 00:02.3-1, assigned address 2
usb.c: USB device 2 (vend/prod 0x41e/0x4116) 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: CREATIVE Model: MuVo^2 (uHDD) Rev: 0001
Type: Direct-Access ANSI SCSI revision: 02
Attached scsi removable disk sda at scsi1, channel 0, id 0, lun 0
SCSI device sda: 7958527 512-byte hdwr sectors (4075 MB)
sda: Write Protect is off
sda: sda1 sda2 sda4
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 2
USB Mass Storage support registered.
When mounting it as you suggested (as root, well I su'ed, does it make any difference?) I get this error.
/dev/sda1: Input/output error
mount: you must specify the filesystem type
Quote:
there is a possibility that there is no filesystem - you should create it
There ought to be as I already have transfered files to it from windows. Btw., I'm using the default kernel from the Slackware 10 install, could this be part of the issue?
mount: wrong fs type, bad option, bad superblock on /dev/sdax,
or too many mounted file systems
where x=3 I get this (same if filsystem is set to auto instead of vfat):
Code:
mount: /dev/sda3 is not a valid block device
If filssystem is set to auto and x={1,2,4} I get:
Code:
/dev/sdax: Input/output error
mount: you must specify the filesystem type
I have 4 usb ports and only one is in use (by the muvo2) which leads me to think that it might be located at sda3. Or am I assumeing wrongly? What's with this warning I get in the dmesg when plugging it in?:
Code:
WARNING: USB Mass Storage data integrity not assured
I'd really appreciate it if someone could figure this out, I'm almost getting desperate here and I'm obviously in over my head....
what kind of windows?
Im not relevant with ntfs, but it is possible if you're using XP or 2000 the filesystem to be ntfs
let us try
mount -t ntfs /dev/sda1 /mnt/muvo
I'm useing win2k as well. I suppose it has to be some kind af fat as it's supposed to work under win98 (posts here and there suggests it is fat16). Anyway, results were the same. I've done a little googling and others have reported it to work under linux with the vfat option. Somewhere I read that in order for this to work then:
# Linux users will need the libusb package, which provides user-level USB. Note that libusb also requiress that users mount the usbdevfs filesystem.
and:
must have usb storage enabled as a module or in the kernel
I do have libusb. I do not know if usbdevfs is mounted, what to I need to do in order to find out? I do not know if I have usb storage enabled as a module or in the kernel, either (could it be the usbcore module listed below?). Again, what do I need to do? Here is the output from lsmod:
1) The sdXY stuff is unrelated to the usb port, they are simply nodes created when the device is plugged in.
2) Slackware has all the necessary tools you need to mount it, and 'USB Storage' is enabled as a module in the default 2.4.26 kernel with Slackware 10.0 (and also appears to be loaded from what you're showing). If you're not certain it's loaded, then 'su' and run 'modprobe usb_storage' before trying to mount the device.
Then mount it as:
mount -t vfat /dev/sda /mnt/muvo -o noauto, users, rw, sync
(The sync option is there because if you manipulate files on the Muvo without it set, it doesn't update the Muvo until you've unmounted it, and discovering it's done nothing will drive you up the wall...
I also actually have udev create a symlink from /dev/sda to /dev/muvo, but we can go onto that later. For the moment, try the above command, with *no* 0,1,2 etc following the sda.
Alternately, I notice you have a CD-RW there trying to use the SCSI interface? If that's being seen as the first SCSI device, perhaps the muvo is being seen as /dev/sdbY. Go to /dev, type 'ls -dl sd*' and post the output if you still have problems.)
3) As far as I can see with my Muvo2, the filesystem is Fat32.
Apologies, I believe the correct module name is usb-storage (I have it compiled directly into the kernel, so I'm not used to loading it separately)
EDIT: Evil devfs... (udev with the 2.6 kernels creates the sdXY nodes when the device is plugged in, devfs just has them all anyway...)
However, based on my Muvo, I'm fairly certain that the device *doesn't* use the kernel number (e.g. /dev/sdX instead of /dev/sdXY). Therefore, try my mount command, but with '/dev/sdX' as the device, and substitute X for the different letters shown (A through to H).
Let see if I got this right, when issueing "modprobe usb-storage" in a terminal, nothing happens. Is that the way it is supposed to be? When mounting the device as you suggested:
mount -t vfat /dev/sda /mnt/muvo -o noauto, users, rw, sync
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
