SliTaz Forum
You are not logged in.
Pages: 1
In slitaz stable 3.0 or the latest cooking version of slitaz, I cannot get the system to recognize any flash drives. The usb hardware is listed by the system with the command lspci, but no driver modules seem to be loaded. When I click on Discover PCI/USB devices in the Tazhw box application, only my sound card is listed. There are no USB kernel modules loaded or listed. There is no problem mounting the flash drive with Debian 6.0 live, so it seems like a slitaz system issue. Any comment or help is appreciated. Thanks.
Offline
What do you have the USB flash drives formatted as?
Offline
FAT32
Offline
They should work as you plug them in. Do you go to pcmanfm and click on their icon in the sidebar? That's how you mount drives with SliTaz (if HAL/udev is working properly that is).
Offline
Well, there are no icons for mounted flash drives in pcmanfm to click. Clicking on the mount points does not do anything. As I've mentioned before, the usb hardware is listed with the lspci command, but no usb modules are listed with the lsmod command. In the tazhw box no usb modules are discovered. The only pci device listed is the sound card. There must be some disconnect between hardware recognition and kernel module loading, I guess. If you have any other ideas, please let me know. Thanks for your interest.
Offline
Well, I stand embarassed and corrected. Using pcmanfm there is an entry for the flash drive, and clicking on it mounts it as /dev/sda1, and it can be unmounted and remounted at other mount points. I don't know why it didn't seem to work before. The cdrom also mounts without difficulty. The hard drive does not mount but gives several errors on attempted mounting, including "Error<i>org.freedesktop.Hal.Device.Volume.UnknownFailure</i>",
"Error <i>org.freedesktop.Hal.Device.Volume.UnknownFailure</i>", and
"Directory doesn't exist!". This may be related, as suggested elsewhere before, to an unusual hpfs file format produced by os/2 (ecomstation). Sorry for all the confusion. Thanks for your interest and help.
Offline
Last night after I rebooted from slitaz stable 3.0 (xvesa version) to the latest cooking version of slitaz, I could not boot the usb flash drive in the latest cooking version of slitaz. I was going to report this morning that the flash drive could not be mounted in the latest cooking version, but before I did that, I checked again with pcmanfm, and, lo and behold, an entry for the flash drive had appeared in the left panel, and clicking on it mounted the usb flash drive. I do not understand what happened overnight. Why was the usb flash drive unavailable for booting soon after the system was running and why did it appear and become bootable somewhere about twelve hours or less later? I do not understand this behavior. Could it be related to differences in the way hardware is recognized and utilized between the older slitaz stable 3.0 and the newer latest cooking version of slitaz. Any ideas would be appreciated. Thanks.
Offline
Most likely. Cooking tends to use the more up to date udev method for detection with secondary dependency on HAL so PCManFM can work with it. Stable uses HAL primarily, while not using udev to it's full potential. The difference is pretty obvious if you compare the two versions. Another contributing factor is that Cooking uses the latest BusyBox with an updated mount command and functionality compiled in. Stable still uses a modified version from 2 years ago...
Offline
Yes, I'm going to assume that the apparent delay in recognition of the usb flash drive in slitaz cooking is related to the differences in hardware recognition between slitaz stable and slitaz cooking. Thanks for the information.
Offline
I have a similar problem. The first time I booted Slitaz from my USB, I was able to mount the USB drive using pcmanfm. Since then, I've rebooted 3 or 4 times and it never recognizes the USB drive. What could be causing this - should I just keep rebooting until it can see it again?
Offline
What does it say when you type dmesg in the terminal after you plug in the device? It might provide some hint or supply you with an error as to why.
I have noticed in Linux that if a USB device doesn't work and you get nothing on dmesg, that sometimes you can 'refresh' detection by running the lsusb command (for slitaz 3 it requires installing the usbutils package first, while cooking comes with it).
Offline
It seems to be there in dmesg. It has all the correct info for the usb, and it ends with
sd 6:0:0:0: [sdb] Attached SCSI removable disk
sd 6:0:0:0: Attached scsi generic sg2 type 0
usb-storage: device scan complete.
It still isn't showing up in the pcmanfm, though. Is there another way to attempt to mount it?
Offline
Does any of the devices show in pcmanfm (like your HDD, CD and DVD roms (when you insert a disc into them), etc)? If not, then it might be that HAL/udev are not starting or not working properly. Which version of SliTaz are you using?
Offline
It doesn't show me those things in the sense that I can mount/unmount them like the USB, but I can access the HDD through /mnt/sda1. The cdrom drive is recognized in the mountbox, but I can't access any files from a CD.
I'm running Linux 2.6.29.3-slitaz with cooking, it's the distro on the ophcrack livecd.
Offline
Alright, scratch the cdrom thing. I was able to access it by typing "mount /dev/cdrom /media/cdrom" into the terminal, so the only thing I can't get to is the USB.
Offline
Okay, I was able to mount the USB to media/usbdisk using "mount /dev/sdb1 /media/usbdisk". Thanks for the help!
Offline
Ah, you're running an older version - possibly SliTaz Aircrack-ng. The thing with Aircrack-ng is that it's built on the cooking prior to the SliTaz 3 release, so it lacks some of the fixes and boxes introduced in SliTaz 3. It's also clear that HAL isn't starting right. By default it should show any inserted CD-ROM or USB device in the left-hand panel of pcmanfm, which will allow you to mount them with a click.
Maybe you should try using the SLiTaz 3 or Cooking ISO from the main SliTaz website. It does include an aircrack package for both now, so the Aircrack edition is kind of defunct now.
Offline
I would, but I'm using it for ophcrack, and I don't have the expertise to modify the latest slitaz to put ophcrack on it. The workaround should be enough for me, though.
Offline
hello everyone!
i'm new to linux in general and especially to Slitaz.
i've booted to ophcrack slitaz and my usb ( FAT32, 2GB )
is also is in read only mode.
i'm logged on as root.
tried to change the usb fs to FAT and NTFS.
when formatted as NTFS it's not listed in the PCmanFM
when formatted to FAT , same issue as with FAT32.
without mounting it i can see it's already mounted after boot in the PCmanFM.
when i try to unmount it , the following error is given :
"Error org.freedesktop.Hal.Device.Volume.UnknownFailure"
in the PCmanFM console the usb appears to be in /mnt/sdb1
in the mountBox i can see a mounted fs :
/dev/root 1.8GB ...
in the Umounted dev section nothing appears.
when i ran the "dmesg" command as suggested by you guys,
i got a lot of things but at the end of the output it says :
..
..
usb-storage : device found at 2
..
sdb: sdb1
sd 2:0:0:0: [sdb] Attached SCSI removable disk
sd 2:0:0:0: Attached SCSI generic sg2 type 0
also tried to run :
"mount /dev/sdb1 /media/usbdis"
mount : mounting /dev/sdb1 /media/usbdisk failed: Device or resource busy.
in other forums people suggested to check for information in /etc/fstab
proc /proc proc deafults 0 0
sysfs /sys sysfs deafults 0 0
tmpfs /dev/shm devpts deafults 0 0
#/dev/hfa3 /home ext3 deafults 0 2
#/dev/hdb1 /mnt/data ext3 deafults 0 2
/dev/cdrom /media/cdrom iso9660 user,ro,noauto 0 0
i would really appreciate any help.
thanks,
Pages: 1
[ Generated in 0.037 seconds, 7 queries executed - Memory usage: 1.57 MiB (Peak: 1.77 MiB) ]