*BSDThis forum is for the discussion of all BSD variants.
FreeBSD, OpenBSD, NetBSD, etc.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have been using FreeBSD 5.4, GENERIC kernel for two weeks now. I am very satisfied with it.
However I have an irritating problem: I cannot mount my USB storage drive (Iomega 256Mb) which has data from my work (Win 2000) on it.
/dev/usbx (/dev/usb0, etc) is probably not what you want, it is the device attached to the /dev/usbx device that you are looking for, and not the usb device. The /dev/umass0 device means that (AFAIK) freebsd communicates with your device; in fact, your device does identify itself. So, you are looking for the device that you can mount. Do an ls /dev before you plug the device in. Then do an ls /dev after you plug in the device and see if there is another device (like /da0, or da1, etc) that gets created. If there is, then try to mount the first slice. Suppose you created this mount point: /mnt/iomega, and /dev shows a /da0 device. Try this:
I tried what you said but unfortunately got no new device in /dev, especially no /da* (0, 1 ...) created when I plug in my USB drive.
Could it be a problem of USB2 (my USB drive) versus USB1 port (it's an old computer it should not have all this modern hardware)?
Thanks for the thread, it was very useful: I am in the same situation, ehci is commented out in the config file of the generic kernel.
I have made the following experience: I have tried another USB pen drive and it worked: I was able to mount it using mount -t msdosfs /dev/da0s1 /mnt/usbdrive and to read and copy data. So, *big success*.
I retried the initial pendrive and no success (no appearance of /dev/da*) and a third one with the same failure. Both USB drives work perfectly on win2000 (at work) and debian sarge (at home).
Would my FreeBSD box be able to mount and use only certain types of USB pen drives, and not others? Is it related to the type of USB key (version 1. or 2.0) or USB port? What could I do to use all types?
Please, advise. And thanks for your help, I think that I am learning a lot through my difficulties.
My FreeBSD system can mount certain USB drives (e.g. Intuix 128MB) and not others (Iomega 256MB) (but the latter works with win2000 and debian sarge). I think that both are USB 2.0 drives. My computer is an old one (1998) and I'm almost sure that in 1998 computers had only USB 1.1 ports I don't have the data of the computer: is there a software in FreeBSD which could tell me type of USB ports the computer has?