Re: initialize msdosfs on memory stick?
On 09/12/13 20:58, Warren Block wrote: > On Thu, 12 Sep 2013, Gary Aitken wrote: > >> On 09/12/13 17:52, Warren Block wrote: >>> On Thu, 12 Sep 2013, Gary Aitken wrote: >>> >>>> I can't seem to find how to do this in the handbook or man pages. I >>>> need to initialize a usb memory stick with an msdos file system. Is >>>> it possible, or do I have to find a windoze system? >>> >>> Sure, it's possible. For maximum compatibility, I'd suggest creating >>> an MBR layout on it. Some devices expect that. Assuming it is da0 >>> (make sure) and that everything on it has been backed up... >>> >>> # gpart destroy -F da0 >>> # gpart create -s mbr da0 >>> # gpart add -t \!12 da0 >>> # newfs_msdos -F32 /dev/da0s1 >> >> That worked, thanks. >> >> Where is the magic file type !12 described? >> I don't see it as one of the possibilities in man gpart. > > It's one of the many MS-DOS FAT variations: > http://en.wikipedia.org/wiki/Partition_type Not fair, that makes it really magic ;-) Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: initialize msdosfs on memory stick?
On Thu, 12 Sep 2013, Gary Aitken wrote: On 09/12/13 17:52, Warren Block wrote: On Thu, 12 Sep 2013, Gary Aitken wrote: I can't seem to find how to do this in the handbook or man pages. I need to initialize a usb memory stick with an msdos file system. Is it possible, or do I have to find a windoze system? Sure, it's possible. For maximum compatibility, I'd suggest creating an MBR layout on it. Some devices expect that. Assuming it is da0 (make sure) and that everything on it has been backed up... # gpart destroy -F da0 # gpart create -s mbr da0 # gpart add -t \!12 da0 # newfs_msdos -F32 /dev/da0s1 That worked, thanks. Where is the magic file type !12 described? I don't see it as one of the possibilities in man gpart. It's one of the many MS-DOS FAT variations: http://en.wikipedia.org/wiki/Partition_type ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: initialize msdosfs on memory stick?
On 09/12/13 17:52, Warren Block wrote: > On Thu, 12 Sep 2013, Gary Aitken wrote: > >> I can't seem to find how to do this in the handbook or man pages. I >> need to initialize a usb memory stick with an msdos file system. Is >> it possible, or do I have to find a windoze system? > > Sure, it's possible. For maximum compatibility, I'd suggest creating > an MBR layout on it. Some devices expect that. Assuming it is da0 > (make sure) and that everything on it has been backed up... > > # gpart destroy -F da0 > # gpart create -s mbr da0 > # gpart add -t \!12 da0 > # newfs_msdos -F32 /dev/da0s1 That worked, thanks. Where is the magic file type !12 described? I don't see it as one of the possibilities in man gpart. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: initialize msdosfs on memory stick?
Gary Aitken wrote: On 09/12/13 16:26, Polytropon wrote: On Thu, 12 Sep 2013 16:13:11 -0600, Gary Aitken wrote: On 09/12/13 15:51, Polytropon wrote: On Thu, 12 Sep 2013 15:39:26 -0600, Gary Aitken wrote: I can't seem to find how to do this in the handbook or man pages. I need to initialize a usb memory stick with an msdos file system. Is it possible, or do I have to find a windoze system? It is possible. The OS provides the newfs_msdos tool. There is no need to deal with "Windows" for this task. Great, thanks. I checked the newfs manpage but didn't look too carefully when the summary line said "construct a new UFS1/UFS2 file system" That's correct: newfs "refers to newfs_ufs" (which obviously initializes a UFS file system), but there are other newfs_* just as there are corresponding (and more) mount_* commands. See "man newfs_msdos" for more details. I see that; but was surprised newfs didn't see-also newfs_msdosfs. Anyhoo... ugh, I think I just screwed it up, not thinking things through. After doing # newfs_msdos -F 32 -S 4096 /dev/da0 newfs_msdos: trim 62 sectors to adjust to a multiple of 63 /dev/da0: 979584 sectors in 30612 FAT32 clusters (131072 bytes/cluster) BytesPerSec=4096 SecPerClust=32 ResSectors=4 FATs=2 Media=0xf0 SecPerTrack=63 Heads=255 HiddenSecs=0 HugeSectors=979650 FATsecs=30 RootCluster=2 FSInfo=1 Backup=2 I can't mount it, and there are no partitions: # ls /dev/da0* /dev/da0 # mount -t msdosfs /dev/da0 /mnt/memstick mount_msdosfs: /dev/da0: Invalid argument Normally there is a /dev/da0s1. I suspect I *should* have used /dev/da0s1 in the newfs_msdos cmd. So, attempting to re-establish the partitions: #gpart create -s MBR da0 da0 created # gpart show -l da0 => 63 7837633 da0 MBR (3.8G) 63 7837633 - free - (3.8G) # gpart add -t mbr da0 gpart: Invalid argument now what? Is mbr the wrong kind of partition type? man gpart indicates the MBR scheme requires the GEOM_PART_MBR kernel option; since the create succeeded, I'm assuming this is present? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" read this how to http://forums.freebsd.org/showthread.php?t=13780 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: initialize msdosfs on memory stick?
On 09/12/13 16:26, Polytropon wrote: > On Thu, 12 Sep 2013 16:13:11 -0600, Gary Aitken wrote: >> On 09/12/13 15:51, Polytropon wrote: >>> On Thu, 12 Sep 2013 15:39:26 -0600, Gary Aitken wrote: >>>> I can't seem to find how to do this in the handbook or man pages. >>>> I need to initialize a usb memory stick with an msdos file system. >>>> Is it possible, or do I have to find a windoze system? >>> >>> It is possible. The OS provides the newfs_msdos tool. >>> There is no need to deal with "Windows" for this task. >>> >> >> Great, thanks. >> I checked the newfs manpage but didn't look too carefully when the summary >> line said "construct a new UFS1/UFS2 file system" > > That's correct: newfs "refers to newfs_ufs" (which obviously > initializes a UFS file system), but there are other newfs_* > just as there are corresponding (and more) mount_* commands. > > See "man newfs_msdos" for more details. I see that; but was surprised newfs didn't see-also newfs_msdosfs. Anyhoo... ugh, I think I just screwed it up, not thinking things through. After doing # newfs_msdos -F 32 -S 4096 /dev/da0 newfs_msdos: trim 62 sectors to adjust to a multiple of 63 /dev/da0: 979584 sectors in 30612 FAT32 clusters (131072 bytes/cluster) BytesPerSec=4096 SecPerClust=32 ResSectors=4 FATs=2 Media=0xf0 SecPerTrack=63 Heads=255 HiddenSecs=0 HugeSectors=979650 FATsecs=30 RootCluster=2 FSInfo=1 Backup=2 I can't mount it, and there are no partitions: # ls /dev/da0* /dev/da0 # mount -t msdosfs /dev/da0 /mnt/memstick mount_msdosfs: /dev/da0: Invalid argument Normally there is a /dev/da0s1. I suspect I *should* have used /dev/da0s1 in the newfs_msdos cmd. So, attempting to re-establish the partitions: #gpart create -s MBR da0 da0 created # gpart show -l da0 => 63 7837633 da0 MBR (3.8G) 63 7837633 - free - (3.8G) # gpart add -t mbr da0 gpart: Invalid argument now what? Is mbr the wrong kind of partition type? man gpart indicates the MBR scheme requires the GEOM_PART_MBR kernel option; since the create succeeded, I'm assuming this is present? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: initialize msdosfs on memory stick?
On Thu, 12 Sep 2013, Gary Aitken wrote: I can't seem to find how to do this in the handbook or man pages. I need to initialize a usb memory stick with an msdos file system. Is it possible, or do I have to find a windoze system? Sure, it's possible. For maximum compatibility, I'd suggest creating an MBR layout on it. Some devices expect that. Assuming it is da0 (make sure) and that everything on it has been backed up... # gpart destroy -F da0 # gpart create -s mbr da0 # gpart add -t \!12 da0 # newfs_msdos -F32 /dev/da0s1 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: initialize msdosfs on memory stick?
On 09/12/13 15:51, Polytropon wrote: > On Thu, 12 Sep 2013 15:39:26 -0600, Gary Aitken wrote: >> I can't seem to find how to do this in the handbook or man pages. >> I need to initialize a usb memory stick with an msdos file system. >> Is it possible, or do I have to find a windoze system? > > It is possible. The OS provides the newfs_msdos tool. > There is no need to deal with "Windows" for this task. > Great, thanks. I checked the newfs manpage but didn't look too carefully when the summary line said "construct a new UFS1/UFS2 file system" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: initialize msdosfs on memory stick?
On Thu, 12 Sep 2013 15:39:26 -0600, Gary Aitken wrote: > I can't seem to find how to do this in the handbook or man pages. > I need to initialize a usb memory stick with an msdos file system. > Is it possible, or do I have to find a windoze system? It is possible. The OS provides the newfs_msdos tool. There is no need to deal with "Windows" for this task. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: initialize msdosfs on memory stick?
On Thu, 12 Sep 2013 16:13:11 -0600, Gary Aitken wrote: > On 09/12/13 15:51, Polytropon wrote: > > On Thu, 12 Sep 2013 15:39:26 -0600, Gary Aitken wrote: > >> I can't seem to find how to do this in the handbook or man pages. > >> I need to initialize a usb memory stick with an msdos file system. > >> Is it possible, or do I have to find a windoze system? > > > > It is possible. The OS provides the newfs_msdos tool. > > There is no need to deal with "Windows" for this task. > > > > Great, thanks. > I checked the newfs manpage but didn't look too carefully when the summary > line said "construct a new UFS1/UFS2 file system" That's correct: newfs "refers to newfs_ufs" (which obviously initializes a UFS file system), but there are other newfs_* just as there are corresponding (and more) mount_* commands. See "man newfs_msdos" for more details. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
initialize msdosfs on memory stick?
I can't seem to find how to do this in the handbook or man pages. I need to initialize a usb memory stick with an msdos file system. Is it possible, or do I have to find a windoze system? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: memory stick
(sorry for top post) Heh, looks like the Alton Brown style of debugging ;D (for anyone that follows his twitter feed) -- Devin On Aug 8, 2013, at 7:34 AM, william benton wrote: > I am trying to mount a memory stick at the command line. I seem to be able to > mount and unmount it but i can't copy files into the stick. please see the > attached image for the commands I used and the results. If you have any > suggestions on what the problem might be I would sure like to know what you > think. I logged in as root on free BSD version 7.0 release 0.0. > > <20130808091209582.pdf>___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: memory stick
On Thu, Aug 8, 2013 at 9:34 AM, william benton wrote: > I am trying to mount a memory stick at the command line. I seem to be able > to mount and unmount it but i can't copy files into the stick. please see > the attached image for the commands I used and the results. If you have any > suggestions on what the problem might be I would sure like to know what you > think. I logged in as root on free BSD version 7.0 release 0.0. > > You have a special character in your path. You will need to escape it, eg cp /usr/home/w\!/foo /mnt/ufs/ -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
memory stick
I am trying to mount a memory stick at the command line. I seem to be able to mount and unmount it but i can't copy files into the stick. please see the attached image for the commands I used and the results. If you have any suggestions on what the problem might be I would sure like to know what you think. I logged in as root on free BSD version 7.0 release 0.0. 20130808091209582.pdf Description: Adobe PDF document ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Unbootable memory stick snapshot?
2011-08-29 19:07, Neil Cafferkey skrev: Hi, I can't boot the FreeBSD-9.0-CURRENT-201107-ia64-memstick.img snapshot. From a hexdump, it doesn't appear to have a boot block. Regards, Neil ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ia64 is for Itanium, if it's an x86_64 you have, you need amd64, even if it's an Intel. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Unbootable memory stick snapshot?
Hi, I can't boot the FreeBSD-9.0-CURRENT-201107-ia64-memstick.img snapshot. >From a hexdump, it doesn't appear to have a boot block. Regards, Neil ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ZFS + GPT with root on memory stick and mirrored SATA drives
On 11 January 2011 09:19, krad wrote: > > > On 11 January 2011 09:09, krad wrote: > >> >> >> On 10 January 2011 21:46, Carl Chave wrote: >> >>> >>> > echo -en "\n\nNow run these two commands to make the changes live, and >>> > reboot >>> > zfs set mountpoint=legacy $zpool/be/$nroot >>> > zpool set bootfs=$zpool/be/$nroot $zpool\n\n" >>> >>> Thanks for the input krad. It would be nice to easily switch back and >>> forth but aren't you still stuck if everything blows up on that first >>> reboot? In order to switch back to the known working dataset you've >>> got to get to a fixit prompt to set the correct bootfs property right? >>> >> >> >> unfortunatly at the moment yes, but all you have to do is reset the bootfs >> property. It would be nice id you could do something from within the boot >> loader similar to variables you can pass in grub with opensolaris >> > > > having said that as long as the loader works you should be able to reset > the rootfs variable > some similar stuff here. http://anonsvn.h3q.com/projects/freebsd-patches/wiki/manageBE ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ZFS + GPT with root on memory stick and mirrored SATA drives
On 11 January 2011 09:09, krad wrote: > > > On 10 January 2011 21:46, Carl Chave wrote: > >> >> > echo -en "\n\nNow run these two commands to make the changes live, and >> > reboot >> > zfs set mountpoint=legacy $zpool/be/$nroot >> > zpool set bootfs=$zpool/be/$nroot $zpool\n\n" >> >> Thanks for the input krad. It would be nice to easily switch back and >> forth but aren't you still stuck if everything blows up on that first >> reboot? In order to switch back to the known working dataset you've >> got to get to a fixit prompt to set the correct bootfs property right? >> > > > unfortunatly at the moment yes, but all you have to do is reset the bootfs > property. It would be nice id you could do something from within the boot > loader similar to variables you can pass in grub with opensolaris > having said that as long as the loader works you should be able to reset the rootfs variable ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ZFS + GPT with root on memory stick and mirrored SATA drives
On 10 January 2011 21:46, Carl Chave wrote: > > > echo -en "\n\nNow run these two commands to make the changes live, and > > reboot > > zfs set mountpoint=legacy $zpool/be/$nroot > > zpool set bootfs=$zpool/be/$nroot $zpool\n\n" > > Thanks for the input krad. It would be nice to easily switch back and > forth but aren't you still stuck if everything blows up on that first > reboot? In order to switch back to the known working dataset you've > got to get to a fixit prompt to set the correct bootfs property right? > unfortunatly at the moment yes, but all you have to do is reset the bootfs property. It would be nice id you could do something from within the boot loader similar to variables you can pass in grub with opensolaris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ZFS + GPT with root on memory stick and mirrored SATA drives
> echo -en "\n\nNow run these two commands to make the changes live, and > reboot > zfs set mountpoint=legacy $zpool/be/$nroot > zpool set bootfs=$zpool/be/$nroot $zpool\n\n" Thanks for the input krad. It would be nice to easily switch back and forth but aren't you still stuck if everything blows up on that first reboot? In order to switch back to the known working dataset you've got to get to a fixit prompt to set the correct bootfs property right? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ZFS + GPT with root on memory stick and mirrored SATA drives
On 10 January 2011 04:58, Carl Chave wrote: > Posting the below for input. The bulk of this is from a guide that > Morgan Wesström posted to this list. Some of it is taken from the > root on ZFS wiki entries on freebsd.org. Some from a pjd post here: > > http://blogs.freebsdish.org/pjd/2010/08/06/from-sysinstall-to-zfs-only-configuration/ > > And then there's this that Svein Skogen posted to the list: > > I usually (today) set up something similar. I sysinstall FreeBSD onto a > CF card with the "one-big-root" method, then create a zpool (on > spinning-metal-storage) where I create the usr, tmp, var fs'es, tar|tar > the originals over and fix the mountpoint info on the zfs'es. Then I add > swap on a zvol (since I don't know how to properly use a kernel dump, I > don't need swap to store it). > > I'm setting up a new home server and I always agonize over > partitioning. So the steps below install the base system with zfs > root on a usb stick and /tmp /usr /var and swap on mirrored sata > drives. > I've tested these steps and everything works but before I press on > with actually configuring and using the server, does anybody have any > input on whether I should or shouldn't do it this way? ZFS best > practices suggests that having elements of the root filesystem on > different pools is a bad idea. So that might be strike 1. > > Memory Stick > > / > /bin > /boot > /dev > /etc > /lib > /libexec > /media > /mnt > /proc > /rescue > /root > /sbin > /sys --> /usr/src/sys > > Hard disk zpool > --- > /tmp > /usr > /var > swap on zvol > > Separate zfs datasets > - > /tmp > /usr > /usr/home > /usr/local > /usr/obj > /usr/ports > /usr/ports/distfiles > /usr/ports/packages > /usr/src > /var > /var/log > /var/audit > /var/tmp > > Install Procedure (Mostly by Morgan Wesström) > - > Select your country and keyboard layout. > > Enter the Fixit environment and use the live filesystem on your DVD. > > Your usb memory stick will most likely be da0 but you can (and should) > check it with "camcontrol devlist" before you continue. > > Create a new GPT partitioning scheme: > # gpart create -s gpt da0 > > Create a 64KiB partition for the zfs bootcode starting at LBA 1920: > # gpart add -b 1920 -s 128 -t freebsd-boot da0 > > Create a zfs partition spanning the remainder of the usb memory stick > and give it a label we can refer to: > # gpart add -t freebsd-zfs -l FreeBSDonUSB da0 > > (The starting LBA for the first partition is there to align the > partitions to the flash memory's erase block size. This is > particularly important for the main zfs partition. The main partition > above will start at exactly 1MiB (LBA 2048) which will align it to any > erase block size used today. This alignment is also of great > importance if you use this guide to install FreeBSD to one of the > newer harddrives using 4096 byte sectors.) > > Install the protective MBR to LBA 0 and the zfs bootcode to the first > partition: > # gpart bootcode -b /dist/boot/pmbr -p /dist/boot/gptzfsboot -i 1 da0 > > Create /boot/zfs (for zpool.cache) and load the zfs kernel modules: > # mkdir /boot/zfs > # kldload /dist/boot/kernel/opensolaris.ko > # kldload /dist/boot/kernel/zfs.ko > > Create a zfs pool and set its bootfs property: > # zpool create zrootusb /dev/gpt/FreeBSDonUSB > # zpool set bootfs=zrootusb zrootusb > > Switch to fletcher4 checksums and turn off access time modifications: > # zfs set checksum=fletcher4 zrootusb > # zfs set atime=off zrootusb > > Create zfs mirrored data pool on SATA disks > # zpool create zdata mirror /dev/ad4 /dev/ad6 > # zfs set canmount=off zdata > # zfs set mountpoint=/zrootusb zdata > # zfs set checksum=fletcher4 zdata > # zfs create zdata/tmp > # zfs create zdata/usr > # zfs create zdata/usr/home > # zfs create zdata/usr/local > # zfs create zdata/usr/obj > # zfs create zdata/usr/ports > # zfs create zdata/usr/ports/distfiles > # zfs create zdata/usr/ports/packages > # zfs create zdata/usr/src > # zfs create zdata/var > # zfs create zdata/var/log > # zfs create zdata/var/audit > # zfs create zdata/var/tmp > > Create swap zvol on zdata pool > # zfs create -V 5G zdata/swap > # zfs set org.freebsd:swap=on zdata/swap > # zfs set checksum=off zdata/swap > > Extract at a minimum, base and the generic kernel: > # cd /dist/8.1-RELEASE/base > # DESTDIR=/zrootusb ./install.sh > # cd ../kernels > # DESTDIR=
ZFS + GPT with root on memory stick and mirrored SATA drives
Posting the below for input. The bulk of this is from a guide that Morgan Wesström posted to this list. Some of it is taken from the root on ZFS wiki entries on freebsd.org. Some from a pjd post here: http://blogs.freebsdish.org/pjd/2010/08/06/from-sysinstall-to-zfs-only-configuration/ And then there's this that Svein Skogen posted to the list: I usually (today) set up something similar. I sysinstall FreeBSD onto a CF card with the "one-big-root" method, then create a zpool (on spinning-metal-storage) where I create the usr, tmp, var fs'es, tar|tar the originals over and fix the mountpoint info on the zfs'es. Then I add swap on a zvol (since I don't know how to properly use a kernel dump, I don't need swap to store it). I'm setting up a new home server and I always agonize over partitioning. So the steps below install the base system with zfs root on a usb stick and /tmp /usr /var and swap on mirrored sata drives. I've tested these steps and everything works but before I press on with actually configuring and using the server, does anybody have any input on whether I should or shouldn't do it this way? ZFS best practices suggests that having elements of the root filesystem on different pools is a bad idea. So that might be strike 1. Memory Stick / /bin /boot /dev /etc /lib /libexec /media /mnt /proc /rescue /root /sbin /sys --> /usr/src/sys Hard disk zpool --- /tmp /usr /var swap on zvol Separate zfs datasets - /tmp /usr /usr/home /usr/local /usr/obj /usr/ports /usr/ports/distfiles /usr/ports/packages /usr/src /var /var/log /var/audit /var/tmp Install Procedure (Mostly by Morgan Wesström) - Select your country and keyboard layout. Enter the Fixit environment and use the live filesystem on your DVD. Your usb memory stick will most likely be da0 but you can (and should) check it with "camcontrol devlist" before you continue. Create a new GPT partitioning scheme: # gpart create -s gpt da0 Create a 64KiB partition for the zfs bootcode starting at LBA 1920: # gpart add -b 1920 -s 128 -t freebsd-boot da0 Create a zfs partition spanning the remainder of the usb memory stick and give it a label we can refer to: # gpart add -t freebsd-zfs -l FreeBSDonUSB da0 (The starting LBA for the first partition is there to align the partitions to the flash memory's erase block size. This is particularly important for the main zfs partition. The main partition above will start at exactly 1MiB (LBA 2048) which will align it to any erase block size used today. This alignment is also of great importance if you use this guide to install FreeBSD to one of the newer harddrives using 4096 byte sectors.) Install the protective MBR to LBA 0 and the zfs bootcode to the first partition: # gpart bootcode -b /dist/boot/pmbr -p /dist/boot/gptzfsboot -i 1 da0 Create /boot/zfs (for zpool.cache) and load the zfs kernel modules: # mkdir /boot/zfs # kldload /dist/boot/kernel/opensolaris.ko # kldload /dist/boot/kernel/zfs.ko Create a zfs pool and set its bootfs property: # zpool create zrootusb /dev/gpt/FreeBSDonUSB # zpool set bootfs=zrootusb zrootusb Switch to fletcher4 checksums and turn off access time modifications: # zfs set checksum=fletcher4 zrootusb # zfs set atime=off zrootusb Create zfs mirrored data pool on SATA disks # zpool create zdata mirror /dev/ad4 /dev/ad6 # zfs set canmount=off zdata # zfs set mountpoint=/zrootusb zdata # zfs set checksum=fletcher4 zdata # zfs create zdata/tmp # zfs create zdata/usr # zfs create zdata/usr/home # zfs create zdata/usr/local # zfs create zdata/usr/obj # zfs create zdata/usr/ports # zfs create zdata/usr/ports/distfiles # zfs create zdata/usr/ports/packages # zfs create zdata/usr/src # zfs create zdata/var # zfs create zdata/var/log # zfs create zdata/var/audit # zfs create zdata/var/tmp Create swap zvol on zdata pool # zfs create -V 5G zdata/swap # zfs set org.freebsd:swap=on zdata/swap # zfs set checksum=off zdata/swap Extract at a minimum, base and the generic kernel: # cd /dist/8.1-RELEASE/base # DESTDIR=/zrootusb ./install.sh # cd ../kernels # DESTDIR=/zrootusb ./install.sh generic Delete the empty, default kernel directory and move the generic kernel into its place: # rmdir /zrootusb/boot/kernel # mv /zrootusb/boot/GENERIC /zrootusb/boot/kernel Make sure the zfs modules are loaded at boot: # cat > /zrootusb/boot/loader.conf zfs_load="YES" vfs.root.mountfrom="zfs:zrootusb" kern.cam.boot_delay=1 ^d Create /etc/rc.conf. Adjust and add to your own needs: # cat > /zrootusb/etc/rc.conf hostname="sodserve" sshd_enable="YES" zfs_enable="YES" ^d Setup your time zone: # cp /zrootusb/usr/share/zoneinfo/EST5EDT /zrootusb/etc/localtime Create an empty fstab to avoid start
Re: USB-boot flash memory stick - Fixit mode do not start
In freebsd-questions Digest, Vol 316, Issue 8, Message: 18
On Fri, 25 Jun 2010 12:12:28 +0400 Alexender wrote:
> I try both 8.0-RELEASE and 8.1-RC official memstick images. I try
> write them to memory stick by that commands:
> # dd if=memstick.img of=/dev/da0 bs=10240
> # dd if=memstick.img of=/dev/da0 bs=512
> I also try to write image from Windows by
> win32diskimager-RELEASE-0.2-r23-win32
>
> I think all was writen well in all cases - in /dev appear /dev/da0a -
> i try to mount it - all was fine. I try to boot from it - all was
> fine too - appear sysinstall.
Looks good.
> But when I try to go to Fixit mode and choose USB - sysinstall tell
> me that there is no USB-device. I try that on 3 different PC - all
> the same. What I did wrong?
This is a known bug that only happens with some, mostly older systems,
and/or with some (slower?) types of USB stick, including mine. I don't
know if this just-informational patch might make it into 8.1-RELEASE ..
--- media.c.1.128 Mon Dec 14 20:04:38 2009
+++ media.c Mon Dec 14 20:50:14 2009
@@ -241,7 +241,8 @@
cnt = deviceCount(devs);
if (!cnt) {
- msgConfirm("No USB devices found!");
+ msgConfirm("No USB devices found!\n"
+ "(try Options menu: Rescan devices)");
return DITEM_FAILURE | DITEM_CONTINUE;
}
else if (cnt > 1) {
.. ie running 'Options menu: Rescan devices' fixes this issue for some.
cheers, Ian
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
USB-boot flash memory stick - Fixit mode do not start
I try both 8.0-RELEASE and 8.1-RC official memstick images. I try write them to memory stick by that commands: # dd if=memstick.img of=/dev/da0 bs=10240 # dd if=memstick.img of=/dev/da0 bs=512 I also try to write image from Windows by win32diskimager-RELEASE-0.2-r23-win32 I think all was writen well in all cases - in /dev appear /dev/da0a - i try to mount it - all was fine. I try to boot from it - all was fine too - appear sysinstall. But when I try to go to Fixit mode and choose USB - sysinstall tell me that there is no USB-device. I try that on 3 different PC - all the same. What I did wrong? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: how do i use a memory stick on freebsd?
On Sat, May 22, 2010 at 12:33 AM, Gary Kline wrote: > > guys, > > my wife emptied a bunch of files onto her memory stick; the pc > is not here. i have never used one of these devices before and > want to know how, if it is possible, to read her dos/lose > material from my bsd system. 7.3, dell, plenty of disk, and yes, > i know where the usb slot it! > > do i need to put something in /usr/rc.conf? build a driver or > utility? or what? > > tia, Y'all! > > clueless in king county. > > In case you use GNOME, see http://www.freebsd.org/gnome/docs/halfaq.html#q3. If this was a fresh install of 7.3 (GNOME 2.28), just do steps 1 and 2, ignore the instructions before and after, restart GNOME and then plug the drive in. It should get mounted and appear on our desktop (well, it worked for me !) -- Gautham Ganapathy http://lisphacker.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: how do i use a memory stick on freebsd?
On Fri, May 21, 2010 at 12:03:42PM -0700, Gary Kline wrote: > > guys, > > my wife emptied a bunch of files onto her memory stick; the pc > is not here. i have never used one of these devices before and > want to know how, if it is possible, to read her dos/lose > material from my bsd system. 7.3, dell, plenty of disk, and yes, > i know where the usb slot it! > > do i need to put something in /usr/rc.conf? build a driver or > utility? or what? You can mount it as root without having to do anything special. Plug in the USB stick, and watch dmesg output to see which device appears. Say you see a device 'da0' appear. Then look in /dev/ to see if there are any slices on it; 'ls /dev/da0*'. You'll probably see one slice, e.g. /dev/da0s1. Then use mount_msdosfs(8) to mount it somewhere. If you want to mount as a regular user, things are somewhat more involved. First, you have to set the sysctl 'vfs.urermount=1'. This has to be done as root, of course. Then you have to make sure that the user in question has read/write access to the devices. Generally, I do that by creating a group called 'usb' with the pw(8) utility, and making users that need access to USB devices a member of that group. Then I add some lines to /etc/devfs.rules to make the usb and related devices accessible to that group; [my_rules=10] add path 'da*' mode 0660 group usb add path 'msdosfs/*' mode 0660 group usb add path 'usb/*' mode 0660 group usb add path 'ugen*' mode 0660 group usb The latter two lines are to make e.g. digital cameras and scanners accessible. This ruleset has to be activated in /etc/rc.conf; devfs_system_ruleset="my_rules" You'll need to reboot the system or restart devfs for this to take effect. With these adaptations, you can mount USB drives as a normal user. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpvBv1KyT0X1.pgp Description: PGP signature
Re: how do i use a memory stick on freebsd?
On Fri, 21 May 2010 12:03:42 -0700, Gary Kline wrote: > > guys, > > my wife emptied a bunch of files onto her memory stick; the pc > is not here. i have never used one of these devices before and > want to know how, if it is possible, to read her dos/lose > material from my bsd system. It IS possible, and quite easy. > 7.3, dell, plenty of disk, and yes, > i know where the usb slot it! It's right beneath the "4X" cup holder, I know. :-) > do i need to put something in /usr/rc.conf? You mean /etc/rc.conf? Usually not. The /etc/fstab file is where you can add a default mountpoint and mount options for the USB stick. Usually, the device used to access USB sticks is /dev/da (Direct Access), and I think it will be /dev/da0. Check the output of dmesg or the last lines in the system log which will reveal the correct device. FAT file systems correspond to a slice on the device, /dev/da0s1 for example. You can mount this device. If it is your first time, play with it, e. g. # mount_msdosfs -o ro /dev/da0s1 /mnt # ls /mnt Is the intended content there? Good. # umount /mnt Now add a rule to your file system table, making mount attempts more easy. /dev/da0s1 /media/stick msdosfs rw,noauto,noatime 0 0 This could be a valid entry, depending on the existance of the directory. Keep in mind: In order to mount USB sticks as a user you need sufficient permissions to the involved files, as well as to own the mount directory, and finally have vfs.usermount=1 in /etc/sysctl.conf. In case you mount as root (or prefix the mount command with sudo, ur use the system's su), you don't need to pay this attention. You should also read man mount_msdosfs and see if you want to use -m and -M: The old-fashioned FAT file systems don't know file permissions, so files on the USB stick will have the +x attribute, pretending they were executables (which they usually aren't); -m and -M apply masks to "cut away" this mis-information. It can also be possible that you need the "large" option -o large. Feel free to also read this: http://www.freebsd.org/doc/en/books/handbook/mount-unmount.html http://www.freebsd.org/doc/en/books/handbook/usb-disks.html In any case, keep an eye on umounting the USB stick before removing it. PCs are bad at hot plug operations. :-) > build a driver or > utility? This is FreeBSD, not "Windows". :-) > or what? Or nothing. :-) If you want "nothing", KDE and Gnome (and Xfce, too) allow the use of automounting USB devices (if sufficient permissions allow this), through the means of HAL, DBUS and PolicyKit. But that's too complicated to be explained in a man's life. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: how do i use a memory stick on freebsd?
On Fri, May 21, 2010 at 12:03:42PM -0700, Gary Kline wrote: > > guys, > > my wife emptied a bunch of files onto her memory stick; the pc > is not here. i have never used one of these devices before and > want to know how, if it is possible, to read her dos/lose > material from my bsd system. 7.3, dell, plenty of disk, and yes, > i know where the usb slot it! > > do i need to put something in /usr/rc.conf? build a driver or > utility? or what? > > tia, Y'all! > > clueless in king county. > I have the following line in my /etc/fstab and it works just fine. /dev/da1s1 /stick msdosfs rw,noauto You have to mount after and umount before plugging the stick in or pulling it out. At least that version of FreeBSD does not automount/umount. I don't know about a driver. I didn't have to do anything extra for a driver. That machine currently has FreeBSD 7.1 on a Dell desktop of some sort (I don't even remember), probably an Optiplex. Of course, the above assumes you have a FATnnn (FAT32) MessyDOS filesystem on it.I think you can put a UFS on it, but then MS won't know how to read/write it. jerry > > -- > Gary Kline kl...@thought.org http://www.thought.org Public Service Unix > The 7.83a release of Jottings: http://jottings.thought.org/index.php >http://journey.thought.org 99 44/100% Guaranteed Novel > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
how do i use a memory stick on freebsd?
guys, my wife emptied a bunch of files onto her memory stick; the pc is not here. i have never used one of these devices before and want to know how, if it is possible, to read her dos/lose material from my bsd system. 7.3, dell, plenty of disk, and yes, i know where the usb slot it! do i need to put something in /usr/rc.conf? build a driver or utility? or what? tia, Y'all! clueless in king county. -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix The 7.83a release of Jottings: http://jottings.thought.org/index.php http://journey.thought.org 99 44/100% Guaranteed Novel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Custom Kernel to Memory Stick
On Mon, 29 Mar 2010 10:49:08 -0500, Jay Hall wrote: > Ladies and Gentlemen, > > I have been asked to explore the possibility of booting FreeBSD from a > memory stick. This was not a problem; worked great when installed from > the distribution CD. > > What would be the best way to get our custom configuration onto the > memory stick? The fastest way I know is to create an image to an 'image' file stored on disk or ramdisk and then dd the image to the USB disk. You can create a suitably large image with truncate(1), e.g.: truncate -s 1g /var/tmp/image.bin Then attach the image to an mdconfig device: mdconfig -a -t vnode -u 20 -f /var/tmp/image.bin Create a filesystem on it, and install everything from your buildworld and buildkernel run: fdisk -BI /dev/md20 bsdlabel -w -B /dev/md20s1 newfs -U /dev/md20s1a Mount the new image partition before installkernel+installworld: mount -t ufs /dev/md20s1a /mnt Then you sould be able to install with DESTDIR pointing to the image partition: cd /usr/src env DESTDIR=/mnt make installkernel installworld Don't forgte to use mergemaster with -D /mnt to install the /mnt/etc files from /usr/src/etc. Then tweak the /mnt/etc/fstab file to point at the USB disk as the root filesystem. Finally detach the image and write it on a USB disk: umount /mnt mdconfig -du 20 dd if=/var/tmp/image.bin of=/dev/da0 bs=4m One of the nice tricks you can use for the root filesystem of the USB disk is to add a UFS label to the USB root filesystem. This way you don't have to assume that the USB root filesystem is called da0s1a but you can use /dev/ufs/LABELNAME in the fstab file of the image partition. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Custom Kernel to Memory Stick
On Mar 29, 2010, at 6:30 PM, Aiza wrote: This is the procedure you want to follow. http://forums.freebsd.org/showthread.php?t=11680 And for greater detail http://forums.freebsd.org/showthread.php?t=11715 Thanks for the links. I will give them a try. Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Custom Kernel to Memory Stick
Jay Hall wrote: Ladies and Gentlemen, I have been asked to explore the possibility of booting FreeBSD from a memory stick. This was not a problem; worked great when installed from the distribution CD. What would be the best way to get our custom configuration onto the memory stick? This is the procedure you want to follow. http://forums.freebsd.org/showthread.php?t=11680 And for greater detail http://forums.freebsd.org/showthread.php?t=11715 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Custom Kernel to Memory Stick
On Mar 29, 2010, at 10:49 AM, Jay Hall wrote: What would be the best way to get our custom configuration onto the memory stick? OK, I managed t get our custom configuration on to the memory stick using dump. After getting everything configured, what I thought was correctly, I am able to boot from the memory stick until it is time to mount the root partition. When mounting the root partition from /dev/da0s1a, I receive the following message: Trying to mount root from ufs:/dev/da0s1a ROOT MOUNT ERROR: If you have invalid mount options, reboot and first try the following from the loader prompt: I have tried the suggested courses of action without any success. If I type ufs:/dev/da0s1a I receive the ROOT MOUNT ERROR again. Following is what I have done to create the bootable memory stick. Created two partitions on the memory stick each about 2 GB. sysinstall was used for this. Used bsdlabel to create the necessary labels on the memory stick. sysinstall was used for this. Ran newfs as on all of the labels. This was done from the command prompt. Once everything was created, I mounted the memory stick and created an image of my working installation using dump. boot0cfg was run on the memory stick. boot0cfg -v -B -o noupdate da0 Modified the fstab on the memory stick as follows /dev/da0s1a / rw,noatime 0 0 Everything other than the operating system was left on the hard drive. If anyone has any suggestions how to fix this, please let me know. I am out of ideas. Or, if you can direct me to a howto, that would be fine also. Thanks for all your help and patience. Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Custom Kernel to Memory Stick
On Mar 29, 2010, at 10:49 AM, Jay Hall wrote: What would be the best way to get our custom configuration onto the memory stick? Ladies and Gentlemen, This is what I have done, but now I cannot mount the memory stick. I create an image of the s1a partition where the kernel I want to copy resides dd if=/dev/ad0s1a of=/home/hallja/s1aimage bs=2048k After preparing the memory stick I use the following command to transfer the image to the memory stick dd if=/home/hallja/ s1aimage of=/dev/da0s1a bs=2048k I am able to mount the memory stick without any problem before I add the image. After adding the image, I try to mount the memory stick using mount /dev/da0s1a /mnt1 And, I receive the following message mount: /dev/da0s1a : Operation not permitted Any suggestions would be greatly appreciated. Thanks, Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Custom Kernel to Memory Stick
Ladies and Gentlemen, I have been asked to explore the possibility of booting FreeBSD from a memory stick. This was not a problem; worked great when installed from the distribution CD. What would be the best way to get our custom configuration onto the memory stick? Thanks, Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
USB Flash Memory stick not bootable
Have problem with being able to boot off an new 8GB USB Flash Memory stick. When I load the 8.0 disc1.iso to an 2GB USB Flash Memory stick it will boot fine. But when I do the same thing to the new 8GB USB Flash Memory stick it’s not recognized as bootable. I can access the installed partitions manually by mounting then on the 7.2 system. So I know the 8GB stick has been loaded correctly. I am doing this on a 7.2 release. Below are the console messages that get displayed when I plug in each of the USB Flash Memory stick. You can see a great difference between the first set of messages for the 8GB stick versus the 2GB stick that follows. I want to boot off the 8GB stick just like I do with the 2GB stick. What is going on here? They should be handled the same way. Brand new 8GB Kingston DataTraveler 120 purchased 7/16/09 umass0: on uhub1 (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition (probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 (probe0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed (probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data) da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-2 device da0: 1.000MB/s transfers da0: 7643MB (15654848 512 byte sectors: 255H 63S/T 974C) GEOM_LABEL: Label for provider da0a is ufsid/4a615a2cc673eb3d. # 3 year old 2GB Kingston DataTraveler umass1: on uhub1 da1 at umass-sim1 bus 1 target 0 lun 0 da1: < USB Flash Memory 6.50> Removable Direct Access SCSI-0 device da1: 1.000MB/s transfers ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Sony Memory Stick Pro Duo 8 GB
Hi, I'm trying to get my 8 GB Sony MS card recognised by my fbsd 7.0-stable. But when I'm putting the memory card in the reader, it doesn't even show up in dmesg and there is no mention in /var/log/messages either. Reader and card are working fine under windows. Any pointers on how to get access to my memory card ? Thanks ! -- Beni. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to mount memory stick on sony vaio laptop?
Andrei Flame wrote: pci10: at device 3.2 (no driver attached) This is, I am afraid, your card reader device :( You're right about the device, thanks! My pciconf -lv says: [EMAIL PROTECTED]:10:3:2: class=0x018000 card=0x81ef104d chip=0x803b104c rev=0x00 hdr=0x00 vendor = 'Texas Instruments (TI)' device = 'PCIxx12 Integrated Flash Media Controller' class = mass storage Any further suggestions? AFAIK, there is no driver for this flash reader at the moment. As a workaround you could purchase one of these cheap usb card readers. These should work like usb flash drives. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to mount memory stick on sony vaio laptop?
> > pci10: at device 3.2 (no driver > > attached) > > > > > > This is, I am afraid, your card reader device :( You're right about the device, thanks! My pciconf -lv says: [EMAIL PROTECTED]:10:3:2: class=0x018000 card=0x81ef104d chip=0x803b104c rev=0x00 hdr=0x00 vendor = 'Texas Instruments (TI)' device = 'PCIxx12 Integrated Flash Media Controller' class = mass storage Any further suggestions? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to mount memory stick on sony vaio laptop?
Andrei Flame wrote: I've just installed FreeBSD 7.0-RELEASE on my Sony Vaio VGN-FE31ZR laptop with built-in memory stick duo pro slot. The problem is that I can't get memory stick card detected and mounted. When I'm inserting a card, nothing happens - no new messages in dmesg and /var/log/messages, no /dev/da0 device. Here is my dmesg output: Copyright (c) 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 pci10: at device 3.2 (no driver attached) This is, I am afraid, your card reader device :( I happen to have an Acer laptop where the card reader is not supported either. These readers work in a different way, they are not a standard (internally connected) USB device as you may have thought. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
How to mount memory stick on sony vaio laptop?
I've just installed FreeBSD 7.0-RELEASE on my Sony Vaio VGN-FE31ZR laptop with built-in memory stick duo pro slot. The problem is that I can't get memory stick card detected and mounted. When I'm inserting a card, nothing happens - no new messages in dmesg and /var/log/messages, no /dev/da0 device. Here is my dmesg output: Copyright (c) 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 CPU T5600 @ 1.83GHz (1828.76-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6f6 Stepping = 6 Features=0xbfebfbff Features2=0xe3bd AMD Features=0x2010 AMD Features2=0x1 Cores per package: 2 real memory = 2145976320 (2046 MB) avail memory = 2090356736 (1993 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 1 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) hptrr: HPT RocketRAID controller driver v1.1 (Feb 24 2008 19:59:27) acpi0: on motherboard acpi0: [ITHREAD] Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 acpi_ec0: port 0x62,0x66 on acpi0 cpu0: on acpi0 est0: on cpu0 p4tcc0: on cpu0 cpu1: on acpi0 est1: on cpu1 p4tcc1: on cpu1 acpi_acad0: on acpi0 battery0: on acpi0 acpi_lid0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 16 at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0x2000-0x207f mem 0xd100-0xd1ff,0xb000-0xbfff,0xd000-0xd0ff irq 16 at device 0.0 on pci1 pcm0: mem 0xd230-0xd2303fff irq 22 at device 27.0 on pci0 pcm0: [ITHREAD] pcib2: irq 17 at device 28.0 on pci0 pci2: on pcib2 pcib3: irq 16 at device 28.1 on pci0 pci4: on pcib3 pcib4: irq 18 at device 28.2 on pci0 pci6: on pcib4 pci6: at device 0.0 (no driver attached) pcib5: irq 21 at device 28.3 on pci0 pci8: on pcib5 uhci0: port 0x1800-0x181f irq 23 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x1820-0x183f irq 17 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0x1840-0x185f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: on uhci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered uhci3: port 0x1860-0x187f irq 16 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] uhci3: [ITHREAD] usb3: on uhci3 usb3: USB revision 1.0 uhub3: on usb3 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0xd2304000-0xd23043ff irq 23 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: on usb4 uhub4: 8 ports with 8 removable, self powered ugen0: on uhub4 pcib6: at device 30.0 on pci0 pci10: on pcib6 cbb0: at device 3.0 on pci10 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 cbb0: [ITHREAD] fwohci0: <1394 Open Host Controller Interface> mem 0xd2006000-0xd20067ff,0xd200-0xd2003fff irq 16 at device 3.1 on pci10 fwohci0: [FILTER] fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 08:00:46:03:02:2e:83:41 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 0a:00:46:2e:83:41 fwe0: Ethernet address: 0a:00:46:2e:83:41 fwip0: on firewire0 fwip0: Firewire address: 08:00:46:03:02:2e:83:41 @ 0xfffe, S400, maxrec 2048 sbp0: on firewire0 dcons_crom0: on firewire0 dcons_crom0: bus_addr 0x7d948000 fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0xc000ffc0, gen=1, CYCLEMASTER mode pci10: at device 3.2 (no driver attached) fxp0: port 0x7000-0x703f mem 0xd2005000-0xd2005fff irq 20 at device 8.0 on pci10 miibus0: on fxp0 inphy0: PHY 1 on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:13:a9:48:9a:91 fxp0: [ITHREAD] isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1880-0x188f at device 31.1 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] atapci1: port 0x18c8-0x18cf,0x18ac-0x18af,0x18c0-0x18c7,0x18a8-0x18ab,0x18b0-0x18bf
Re: Transfer CD image to USB memory stick?
Per olof Ljungmark <[EMAIL PROTECTED]> writes: > Could someone please point me to information how to achieve this? Have > new hardware that lacks CD/floppy and want to install FreBSD... I have a script that makes a disk image from a bootonly FreeBSD install image. I usually install grub on the USB memory stick and use memdisk from the syslinux package to load the image. A sample menu entry for grub is included in the script. http://borderworlds.dk/~xi/iso2diskimage.pl -- Christian Laursen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Transfer CD image to USB memory stick?
Hi, Could someone please point me to information how to achieve this? Have new hardware that lacks CD/floppy and want to install FreBSD... Thanks, --per ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Booting from Memory Stick
On Sun, Mar 2, 2008 at 11:37 AM, Walker <[EMAIL PROTECTED]> wrote:
> # set root password and timezone (optionally add users here as well)
> chroot ${USBMNT} /bin/sh
> passwd root
> tzsetup
One error, the above should be:
# set root password and timezone (optionally add users here as well)
chroot ${USBMNT} /bin/sh
passwd root
tzsetup
exit
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Booting from Memory Stick
On Sat, Mar 1, 2008 at 4:23 PM, <[EMAIL PROTECTED]> wrote:
> I am working on getting a FreeBSD system to boot from a USB memory stick.
FWIW, my cut/paste script for installing 7.0 to a USB flash drive.
This is adapted from a post by Ceri Davies (thank you!).
** This assumes the drive is at /dev/da0 and that /dev/md0 is not in use **
# set these; the two mount points should not exist
export ISOFILE='/tmp/7.0-RELEASE-i386-disc1.iso'
export ISOMNT='/a'
export USBMNT='/b'
# zero the device for better compression when were done (optional)
dd bs=10m if=/dev/zero of=/dev/da0
# mdconfig and mount the media
mkdir -m 555 ${ISOMNT} ${USBMNT}
mdconfig -a -t vnode -u 0 -f ${ISOFILE}
mount -t cd9660 /dev/md0 ${ISOMNT}
# label and newfs the flash drive
fdisk -BI /dev/da0
bsdlabel -B -w da0s1
newfs -U -L FBSDusb /dev/da0s1a
mount /dev/da0s1a ${USBMNT}
# install the OS
cd ${ISOMNT}/*RELEASE/base
DESTDIR=${USBMNT} ./install.sh
# install the generic kernel
cd ${ISOMNT}/*RELEASE/kernels
DESTDIR=${USBMNT} ./install.sh generic
rmdir ${USBMNT}/boot/kernel
mv ${USBMNT}/boot/GENERIC ${USBMNT}/boot/kernel
# set boot0 options
boot0cfg -v -B -o noupdate -t 90 da0
# install a fstab; adjust as needed (like /tmp size)
cat >> ${USBMNT}/etc/fstab << EOF
# Device Mountpoint FStype Options Dump Pass
/dev/ufs/FBSDusb / ufs rw,noatime 1 1
md /tmp mfs rw,-s150M,nosuid,noatime 0 0
md /var/run mfs rw,-s4M,nosuid,noatime 0 0
md /var/log mfs rw,-s16M,nosuid,noatime 0 0
/dev/acd0 /cdrom cd9660 ro,noauto,nosuid 0 0
/proc /proc procfs rw,noauto 0 0
/tmp /var/tmp nullfs rw 0 0
EOF
# install an rc.conf
cat >> ${USBMNT}/etc/rc.conf << EOF
ifconfig_DEFAULT="DHCP"
ifconfig_fwe0="NOAUTO"
ifconfig_plip0="NOAUTO"
sshd_enable="YES"
syslogd_flags="-vv"
sendmail_enable="NONE"
EOF
# set root password and timezone (optionally add users here as well)
chroot ${USBMNT} /bin/sh
passwd root
tzsetup
# clean up
cd /
umount ${ISOMNT} ${USBMNT}
rmdir ${ISOMNT} ${USBMNT}
mdconfig -d -u 0
# backup and compress (~ 84MB) (optional)
dd bs=10m if=/dev/da0 of=usbflash-freebsd_7.0.img
nice bzip2 usbflash-freebsd_7.0.img
# done
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Booting from Memory Stick
On Saturday 01 March 2008 04:23:24 pm [EMAIL PROTECTED] wrote: > I am working on getting a FreeBSD system to boot from a USB memory > stick. > > Would it be possible to install the operating system using the > following: > > cd /usr/src > make DESTDIR=/mnt/usbdisk world > boot0cfg -v -B -o noupdate da0 > > Or, is there an easier way to do this? I know you've gotten some other responses, but I wanted to chime in and say that I've done this (just today, actually) using an approach similar to what you're outlining. In a nutshell: (assuming USB stick is da0, you don't care about what's on it, and you want to use the whole thing with one partition and no swap) ##prepare the destination disk, including boot blocks, and mount fdisk -BI /dev/da0 #ignore the GEOM not found message bsdlabel -wB /dev/da0s1 newfs -U -L mystick /dev/da0s1a #optional flags for softupdates and label mount /dev/ufs/mystick /mnt ##prepare obj tree (skip if you already have one with the kernel you want) cd /usr/src make buildworld make KERNCONF=MYUSBKERNEL #or GENERIC, whatever ##install to the stick cd /usr/src make KERNCONF=MYUSBKERNEL DESTDIR=/mnt installkernel make DESTDIR=/mnt installworld mergemaster -i -D /mnt #review list, answer yes to followup ?'s ##The only other thing that's required is an fstab file: echo "/dev/ufs/mystick / ufs rw 1 1" >> /mnt/etc/fstab ##and don't forget to un-mount the stick when you're done umount /mnt That's a bit quick and dirty, obviously, but you can boot from the stick and have a complete system at this point. Setup of the root password, users, groups, hostname, interfaces, timezone, etc not included. Sysinstall or manual config (either from the initial host or after booting from the stick) can get you the rest of the way. Or you may discover that one of the other approaches suggested is easier. :) JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Booting from Memory Stick
Hi, On Sat, Mar 1, 2008 at 10:23 PM, <[EMAIL PROTECTED]> wrote: > I am working on getting a FreeBSD system to boot from a USB memory stick. > > Would it be possible to install the operating system using the following: > > cd /usr/src > make DESTDIR=/mnt/usbdisk world > boot0cfg -v -B -o noupdate da0 > > Or, is there an easier way to do this? Yes, the freesbie2 toolkit (http://www.freesbie.org/) does the job very well. Hope this helps. > Thanks, > > > Jay > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > Regards. -- There's this old saying: "Give a man a fish, feed him for a day. Teach a man to fish, feed him for life." ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Booting from Memory Stick
I made a bootable system on a stick a few months ago. I used it to dd clone a WinXP image to some Gateway desktops in a lab. I think I just plugged the stick into my FreeBSD laptop fired up sysinstall and treated the stick as a da drive that needed a full install. Tim Derek Ragona wrote: At 03:23 PM 3/1/2008, [EMAIL PROTECTED] wrote: I am working on getting a FreeBSD system to boot from a USB memory stick. Would it be possible to install the operating system using the following: cd /usr/src make DESTDIR=/mnt/usbdisk world boot0cfg -v -B -o noupdate da0 Or, is there an easier way to do this? Thanks, Jay I don't know how to do this myself, but know it is available using FreeNAS, which is based on FreeBSD. FreeNAS information is at: www.freenas.org -Derek ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Booting from Memory Stick
At 03:23 PM 3/1/2008, [EMAIL PROTECTED] wrote: I am working on getting a FreeBSD system to boot from a USB memory stick. Would it be possible to install the operating system using the following: cd /usr/src make DESTDIR=/mnt/usbdisk world boot0cfg -v -B -o noupdate da0 Or, is there an easier way to do this? Thanks, Jay I don't know how to do this myself, but know it is available using FreeNAS, which is based on FreeBSD. FreeNAS information is at: www.freenas.org -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Booting from Memory Stick
I am working on getting a FreeBSD system to boot from a USB memory stick. Would it be possible to install the operating system using the following: cd /usr/src make DESTDIR=/mnt/usbdisk world boot0cfg -v -B -o noupdate da0 Or, is there an easier way to do this? Thanks, Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Odd memory stick formatting
On Nov 16, 2007, at 10:31 AM, RW wrote: I have a couple of USB devices that I mount as /dev/da0s1, which what I would expect. I've just got a memory stick that's showing as /dev/da0 & /dev/da0s4. and only /dev/da0 mounts. The output of fdisk is garbage, showing four unfeasibly large partitions with unknown sysid values. On the other hand it seems to work fine as da0. Is this normal, or should I repartition. If the latter is there anything particular I need to do to maintain Windows compatibility - I've a vague recollection that Windows leave a gap before the first partition, or something. I've seen some usb flash drives that under windows, mounts as two separate and independent filesystems, one of which is a cd-rom. Try mounting the other partition as cd9660 and see if that works and you get to see all the software they preload onto the drives. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Odd memory stick formatting
I have a couple of USB devices that I mount as /dev/da0s1, which what I would expect. I've just got a memory stick that's showing as /dev/da0 & /dev/da0s4. and only /dev/da0 mounts. The output of fdisk is garbage, showing four unfeasibly large partitions with unknown sysid values. On the other hand it seems to work fine as da0. Is this normal, or should I repartition. If the latter is there anything particular I need to do to maintain Windows compatibility - I've a vague recollection that Windows leave a gap before the first partition, or something. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem booting from memory-stick with ASUS A7V-133
Hi Steve, > > I have a problem with booting from a 128MB USB-memory-stick with the ASUS > > A7V-133 motherboard. I downloaded the boot-floppy-image"boot.flp" (version > > 6.2) from the FreeBSD-FTP-server and "dd"-ed it to a memory stick. Booting > > from this stick works fine with every other computer I have (a notebook and > > a newer workstation also with an ASUS-board). But trying to boot from the > > stick with the A7V gives me the following output: > > > > <- 8< ---> > > Not ufs > > Not ufs > > No /boot/loader > > FreeBSD/i386 boot > > Default: 0:fd(0,a)/boot/kernel/kernel > > boot: > > Not ufs > > No /boot/kernel/kernel > > <- 8< ---> > > > > What happens if you enter: > > 0:da(0,a)/boot/kernel/kernel > > ...at the boot: prompt (as opposed to fd(0,a)? first of all: Thanks a lot for you very quick response. Entering this at the prompt gives me the following output (includes the entered data): <- 8< ---> boot: 0:da(0,a)/boot/kernel/kernelerror 1 lba 0 No /boot/kernel/kernel <- 8< ---> Any other things I should try? Best regards, Stefan _ Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! http://smartsurfer.web.de/?mc=100071&distributionid=0066 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem booting from memory-stick with ASUS A7V-133
[EMAIL PROTECTED] wrote: > Hi all, > > hope this is the right list. > > I have a problem with booting from a 128MB USB-memory-stick with the ASUS > A7V-133 motherboard. I downloaded the boot-floppy-image"boot.flp" (version > 6.2) from the FreeBSD-FTP-server and "dd"-ed it to a memory stick. Booting > from this stick works fine with every other computer I have (a notebook and a > newer workstation also with an ASUS-board). But trying to boot from the stick > with the A7V gives me the following output: > > <- 8< ---> > Not ufs > Not ufs > No /boot/loader > FreeBSD/i386 boot > Default: 0:fd(0,a)/boot/kernel/kernel > boot: > Not ufs > No /boot/kernel/kernel > <- 8< ---> > What happens if you enter: 0:da(0,a)/boot/kernel/kernel ...at the boot: prompt (as opposed to fd(0,a)? Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Problem booting from memory-stick with ASUS A7V-133
Hi all, hope this is the right list. I have a problem with booting from a 128MB USB-memory-stick with the ASUS A7V-133 motherboard. I downloaded the boot-floppy-image"boot.flp" (version 6.2) from the FreeBSD-FTP-server and "dd"-ed it to a memory stick. Booting from this stick works fine with every other computer I have (a notebook and a newer workstation also with an ASUS-board). But trying to boot from the stick with the A7V gives me the following output: <- 8< ---> Not ufs Not ufs No /boot/loader FreeBSD/i386 boot Default: 0:fd(0,a)/boot/kernel/kernel boot: Not ufs No /boot/kernel/kernel <- 8< ---> So it seems to me that the BIOS reads the first sector of the memory-stick (the MBR) executes the code but then the bootloader seems to have problems with the drive geometry or something like this. So does anybody on this list have had similar problems or can give me a hint what to do to solve this problem? BTW: I know that the used floppy-image is just for installation and I'm not able to boot a fully running system from it. But it seems to me the best/fastest way to test whether booting from the stick works or not. Thanks a lot in advance Stefan _ Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! http://smartsurfer.web.de/?mc=100071&distributionid=0066 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Getting rid of /dev and mount entry after unplugging mounted USB memory stick
Hans Nieser <[EMAIL PROTECTED]> writes: > Is there a way I can get rid of the bogus mount / device entry other > than rebooting, or will I really have to teach myself to unmount my > USB device everytime before I unplug it? > > Note that integrity of the data or data-transfer speed of the USB > device is not critical as it is actually an MP3 player that I copy a > bunch of mp3s to every now and then. So sacrifices can be made if > neccesary. I use the mtools port for the purpose, so that removable devices don't have to be mounted at all... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Getting rid of /dev and mount entry after unplugging mounted USB memory stick
Hi list, Every now and then I forget to unmount my USB memory stick. This becomes a problem because every time I do it, I am left with a bogus mount and device entry. "umount -f" makes the whole machine reboot instantly. From the googling that I have done, I have concluded that this is normal. (But just to be sure, I will paste my dmesg output below). Is there a way I can get rid of the bogus mount / device entry other than rebooting, or will I really have to teach myself to unmount my USB device everytime before I unplug it? Note that integrity of the data or data-transfer speed of the USB device is not critical as it is actually an MP3 player that I copy a bunch of mp3s to every now and then. So sacrifices can be made if neccesary. Below is the dmesg output of all USB-related devices (da0 through da3 are flashcard readers, haven't actually done anything with those so they can probably be ignored). Output from plugging in the mp3player is at the bottom. ohci0: mem 0xc9003000-0xc9003fff irq 21 at device 2.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 10 ports with 10 removable, self powered ehci0: mem 0xfeb0-0xfeb000ff irq 22 at device 2.1 on pci0 ehci0: [GIANT-LOCKED] usb1: EHCI version 1.0 usb1: companion controller, 4 ports each: usb0 usb1: on ehci0 usb1: USB revision 2.0 uhub1: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub1: 10 ports with 10 removable, self powered uhub2: vendor 0x03eb Standard USB Hub, class 9/0, rev 1.10/3.00, addr 2 uhub2: 4 ports with 4 removable, self powered umass0: ICSI IC1100 V2.5b, rev 1.10/2.5b, addr 3 ums0: Logitech USB-PS/2 Optical Mouse, rev 2.00/21.00, addr 4, iclass 3/1 ums0: 7 buttons and Z dir. da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present da1 at umass-sim0 bus 0 target 0 lun 1 da1: Removable Direct Access SCSI-0 device da1: 1.000MB/s transfers da1: Attempt to query device size failed: NOT READY, Medium not present da2 at umass-sim0 bus 0 target 0 lun 2 da2: Removable Direct Access SCSI-0 device da2: 1.000MB/s transfers da2: Attempt to query device size failed: NOT READY, Medium not present da3 at umass-sim0 bus 0 target 0 lun 3 da3: Removable Direct Access SCSI-0 device da3: 1.000MB/s transfers da3: Attempt to query device size failed: NOT READY, Medium not present (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): NOT READY asc:3a,0 (da0:umass-sim0:0:0:0): Medium not present (da0:umass-sim0:0:0:0): Unretryable error Opened disk da0 -> 6 (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): NOT READY asc:3a,0 (da0:umass-sim0:0:0:0): Medium not present (da0:umass-sim0:0:0:0): Unretryable error Opened disk da0 -> 6 (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): NOT READY asc:3a,0 (da0:umass-sim0:0:0:0): Medium not present (da0:umass-sim0:0:0:0): Unretryable error Opened disk da0 -> 6 (da1:umass-sim0:0:0:1): READ CAPACITY. CDB: 25 20 0 0 0 0 0 0 0 0 (da1:umass-sim0:0:0:1): CAM Status: SCSI Status Error (da1:umass-sim0:0:0:1): SCSI Status: Check Condition (da1:umass-sim0:0:0:1): NOT READY asc:3a,0 (da1:umass-sim0:0:0:1): Medium not present (da1:umass-sim0:0:0:1): Unretryable error Opened disk da1 -> 6 (da1:umass-sim0:0:0:1): READ CAPACITY. CDB: 25 20 0 0 0 0 0 0 0 0 (da1:umass-sim0:0:0:1): CAM Status: SCSI Status Error (da1:umass-sim0:0:0:1): SCSI Status: Check Condition (da1:umass-sim0:0:0:1): NOT READY asc:3a,0 (da1:umass-sim0:0:0:1): Medium not present (da1:umass-sim0:0:0:1): Unretryable error Opened disk da1 -> 6 (da1:umass-sim0:0:0:1): READ CAPACITY. CDB: 25 20 0 0 0 0 0 0 0 0 (da1:umass-sim0:0:0:1): CAM Status: SCSI Status Error (da1:umass-sim0:0:0:1): SCSI Status: Check Condition (da1:umass-sim0:0:0:1): NOT READY asc:3a,0 (da1:umass-sim0:0:0:1): Medium not present (da1:umass-sim0:0:0:1): Unretryable error Opened disk da1 -> 6 (da2:umass-sim0:0:0:2): READ CAPACITY. CDB: 25 40 0 0 0 0 0 0 0 0 (da2:umass-sim0:0:0:2): CAM Status: SCSI Status Error (da2:umass-sim0:0:0:2): SCSI Status: Check Condition (da2:umass-sim0:0:0:2): NOT READY asc:3a,0 (da2:umass-sim0:0:0:2): Medium not present (da2:umass-sim0:0:0:2): Unretryable error Opened disk da2 -> 6 (da2:umass-sim0:0:0:2): READ CAPACITY. CDB: 25 40 0 0 0 0 0 0 0 0 (da2:umass-sim0:0:0:2): CAM Status: SCSI Statu
Re: Solutions for memory stick name!
In the last episode (Sep 26), Carstea Catalin said: > What is the simple way to know my memory stick name? > > With dmesg i know if my memory stick is mount but i want to know the > complete name. > Ex.: da0s1 > ... One way is by loading the geom_label module. Then you will get a /dev/msdosfs/### entry, one for each labelled fat filesystem. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Solutions for memory stick name!
What is the simple way to know my memory stick name? With dmesg i know if my memory stick is mount but i want to know the complete name. Ex.: da0s1 ... -- Any help would be greatly appreciated. regards, Carstea Catalin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
5-Stable: USB "LG XTICK" 1GB memory stick fails
Hello, I can't get my LG XTICK 1GB USB memory stick working with 5-Stable (as of Sept. 25, 2005). Also, when I plug it in, my mouse pointer in X disappears; I get it back by restarting the moused daemon. Various outputs are listed below. Any idea what's the problem here? Is there a way to get it work? Thanks, Rob. - ls /dev/da* /dev/da0 --- - camcontrol devlist -v -- scbus0 on umass-sim0 bus 0: at scbus0 target 0 lun 0 (pass0,da0) scbus-1 on xpt0 bus 0: < > at scbus-1 target -1 lun -1 (xpt0) --- - usbdevs -d -v -- Controller /dev/usb0: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 uhub0 port 1 powered port 2 powered Controller /dev/usb1: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 uhub1 port 1 addr 2: full speed, power 500 mA, config 1, XTICK(0x2168), LG(0x0ea0), rev 2.00 umass0 port 2 powered Controller /dev/usb2: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 uhub2 port 1 powered port 2 powered Controller /dev/usb3: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 uhub3 port 1 powered port 2 powered --- - dmesg output --- (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 (da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed (da0:umass-sim0:0:0:0): Retrying Command (per Sense Data) (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 (da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed (da0:umass-sim0:0:0:0): Retrying Command (per Sense Data) (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 (da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed (da0:umass-sim0:0:0:0): Retrying Command (per Sense Data) (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 (da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed (da0:umass-sim0:0:0:0): Retrying Command (per Sense Data) (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 (da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed (da0:umass-sim0:0:0:0): Retries Exhausted Opened disk da0 -> 6 --- __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to use USB memory-stick for booting FreeBSD?
> > I suppose one GigaByte should be enough for the base system of 5.4, > > isn't it? > > Definitely. The full base system (as I mentioned above) takes about > 170 MB of disk space on i386 installations. hi! i would just like to add that it's a good idea to put rapidly changing filesystems/directories (/var/log, /tmp and so on) on memory- filesystems because usbdrives don't survive as many writeoperations as HDs do. cya, jonas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to use USB memory-stick for booting FreeBSD?
On 2005-09-25 22:32, Rob <[EMAIL PROTECTED]> wrote: >Giorgos Keramidas wrote: >> By installing a FreeBSD base system on it (approx. 170 MB) and a >> boot loader, and setting your BIOS to boot from "USB legacy device". > > Hmmm, how do I do that? > After a system and kernel build, is it then something like 'make > installworld' and 'make installkernel' into non-default destinations > (i.e. mount-point of the USB stick) ? First of all, you format and mount the USB disk somewhere. Let's say, under ``/mnt/usbdisk''. Then, after you complete a buildworld and buildkernel process, you can install the FreeBSD base system on the USB disk by: # cd /usr/src # make DESTDIR=/mnt/usbdisk installkernel # make DESTDIR=/mnt/usbdisk installworld This doesn't install a full /etc hierarchy in the USB disk, so you'll have to run something like this too: # cd /usr/src/etc # make DESTDIR=/mnt/usbdisk distrib-dirs # make DESTDIR=/mnt/usbdisk distribution Finally, you should create at least an /etc/fstab under the new root, and you should be more or less set to go. > I suppose one GigaByte should be enough for the base system of 5.4, > isn't it? Definitely. The full base system (as I mentioned above) takes about 170 MB of disk space on i386 installations. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to use USB memory-stick for booting FreeBSD?
Giorgos Keramidas wrote: > On 2005-09-25 22:06, Rob wrote: > >>I have a USB memory stick of one GigaByte. >> I learned that on some PCs, the BIOS allows >> booting from USB memory-stick. >> >>Is this possible with FreeBSD? > > > Yes. Great! >>If yes, then how do I install FreeBSD on such a >> USB memory stick, so that it becomes a 'bootable >> USB'? > > By installing a FreeBSD base system on it (approx. > 170 MB) and a boot loader, and setting your BIOS > to boot from "USB legacy device". Hmmm, how do I do that? After a system and kernel build, is it then something like 'make installworld' and 'make installkernel' into non-default destinations (i.e. mount-point of the USB stick) ? I suppose one GigaByte should be enough for the base system of 5.4, isn't it? Rob. __ Yahoo! for Good Donate to the Hurricane Katrina relief effort. http://store.yahoo.com/redcross-donate3/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to use USB memory-stick for booting FreeBSD?
On 2005-09-25 22:06, Rob <[EMAIL PROTECTED]> wrote: > I have a USB memory stick of one GigaByte. I learned that on some > PCs, the BIOS allows booting from USB memory-stick. > > Is this possible with FreeBSD? Yes. > If yes, then how do I install FreeBSD on such a USB memory stick, so > that it becomes a 'bootable USB'? By installing a FreeBSD base system on it (approx. 170 MB) and a boot loader, and setting your BIOS to boot from "USB legacy device". The details evade me right now, but if you meet any problem along the way I can go back and look at my notes. If you want to trim the base system down to an absolute minimum, it may also be worth to try "nanobsd" (which is part of the sources too). See the /usr/src/tools/tools/nanobsd hierarchy for more information about the "nanobsd" build process. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
How to use USB memory-stick for booting FreeBSD?
Hi, I have a USB memory stick of one GigaByte. I learned that on some PCs, the BIOS allows booting from USB memory-stick. Is this possible with FreeBSD? If yes, then how do I install FreeBSD on such a USB memory stick, so that it becomes a 'bootable USB'? Thanks, Rob. __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: take MS memory stick
Lowell Gilbert <[EMAIL PROTECTED]> wrote: writes: > I use FreeBsd 5 generic Kernel. I have a takeMS mem drive 2.0 , 1G > capacity , for USB . The system recognizes the USB port but when i > plug the device in i get an error message after 20-30 seconds. The > device is not listed within the hardware compatibility list of the > USB Mass-Storage daemon ( umass) and i guess this is the > problem. The support cdrom that came with the device doesn't mention > anything about BSD drivers. In fact it is recognized by the linux > kernel and Win 2k etc. so there only is an install pack for Win > 98. The drivers download page at takeMS homepage is hyronicaly under > construction.What can i do ? What version of FreeBSD are you running exactly? "Quirks" of specific devices are understood and better handled all the time, and it's quite likely that updating your system would get a specific memory "disk" working... I use 5.3 i think i'll move to 5.4 thou i checked the list of improvements and there's no takeMS included. - Yahoo! for Good Click here to donate to the Hurricane Katrina relief effort. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: take MS memory stick
<[EMAIL PROTECTED]> writes: > I use FreeBsd 5 generic Kernel. I have a takeMS mem drive 2.0 , 1G > capacity , for USB . The system recognizes the USB port but when i > plug the device in i get an error message after 20-30 seconds. The > device is not listed within the hardware compatibility list of the > USB Mass-Storage daemon ( umass) and i guess this is the > problem. The support cdrom that came with the device doesn't mention > anything about BSD drivers. In fact it is recognized by the linux > kernel and Win 2k etc. so there only is an install pack for Win > 98. The drivers download page at takeMS homepage is hyronicaly under > construction.What can i do ? What version of FreeBSD are you running exactly? "Quirks" of specific devices are understood and better handled all the time, and it's quite likely that updating your system would get a specific memory "disk" working... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
take MS memory stick
I use FreeBsd 5 generic Kernel. I have a takeMS mem drive 2.0 , 1G capacity , for USB . The system recognizes the USB port but when i plug the device in i get an error message after 20-30 seconds. The device is not listed within the hardware compatibility list of the USB Mass-Storage daemon ( umass) and i guess this is the problem. The support cdrom that came with the device doesn't mention anything about BSD drivers. In fact it is recognized by the linux kernel and Win 2k etc. so there only is an install pack for Win 98. The drivers download page at takeMS homepage is hyronicaly under construction.What can i do ? __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Respuesta: Re: USB memory stick hotswap problems
- Mensaje original -
De: Julian Stacey <[EMAIL PROTECTED]>
Fecha: Miércoles, Septiembre 29, 2004 4:34 am
Asunto: Re: USB memory stick hotswap problems
> Very telling mail that. Hopefully someone may find time to solve it.
Yes, I agree, basically because Micro$oft has users accustomed to transparently access
and removal of floppies and cd's, if not my icons wouldn't look like a hack.
>
> What's a PITA by the way ?
Pain in the ass :)
Have a great day,
ed
>
> Reference:
> > From: edwinculp <[EMAIL PROTECTED]>
> > Date: Mon, 27 Sep 2004 10:56:17 -0500
> > Message-id: <[EMAIL PROTECTED]>
>
> edwinculp wrote:
> > Quoting Ivan Voras <[EMAIL PROTECTED]>:
> >
> > > Daniel O'Connor wrote:
> > >> One possibility would be to add a facility to mark all the
> data for
> > >> a certain device to be non-critical so it will throw it away
> when it
> > >> tries to flush it and fails instead of panicing.
> > >
> > > That (and a message in syslog) would be just fine. ("Windows
> does it, so
> > > it's normal".) I know (and I think other USB drive users know
> too) that
> > > I need to wait for the little LED on the device to stop
> blinking before
> > > unplugging it.
> > >
> > > IIRC, Windows mounts removable drives with write caching
> disabled, so it
> > > should probably be the same in FreeBSD.
> >
> > Would it not be a good idea to do something like this for cd's
> and floppies?
> >
> > I'm substituting FreeBSD for windows in some internet cafes. Not
> automatical> ly recovering from unmounted cd's, floppies and
> usbdev's, is probably the big
> > gest PITA that I've found and haven't been able to solve cleanly.
> I've had t
> > o put icons on the kde-desktop for accessing and removing them
> that many just
> > ignore. This is also the case in a corporate environment where
> I have had t
> > he same problem but they are a little better at using the
> > icon because it is their pc that crashes :)
> >
> > Thanks,
> >
> > ed
> >
> > ___
> > [EMAIL PROTECTED] mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to "freebsd-current-
> [EMAIL PROTECTED]">
> >
>
> -
> Julian Stacey. Unix,C,Net & Sys. Eng. Consultant, Munich.
> http://berklix.comMail in Ascii, Html dumped as Spam. Ihr Rauch =
> mein allergischer Kopfschmerz.
>
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB memory stick
* Michael L. Hostbaek: > I have just purchased a MP3 player - which basically consists of a USB > 128MB memory stick, with some audio hardware.. Anyways, when I plug > the USB stick into my 5.1-RELEASE-p3 box, I am seeing the following in > /var/log/messages: > > Oct 2 15:31:27 kernel: umass0: SigmaTel, Inc. USBMSC Audio Player, rev 1.10/0.01, > addr 2 > Oct 2 15:31:27 kernel: umass0: Get Max Lun not supported (IOERROR) > Oct 2 15:31:27 kernel: da0 at umass-sim0 bus 0 target 0 lun 0 > Oct 2 15:31:27 kernel: da0: Removable Direct Access SCSI-4 > device > Oct 2 15:31:27 kernel: da0: 1.000MB/s transfers > Oct 2 15:31:27 kernel: da0: 123MB (251904 512 byte sectors: 64H 32S/T 123C) > > [...] > > Oct 2 15:32:22 kernel: (da0:umass-sim0:0:0:0): Synchronize cache failed, status == > 0x4, scsi status == 0x0 > > [...] > > If I try and mount it, the box just freezez until I remove the device. > > Any ideas ? The relevant info in the logs is that the device does not recognize the « Synchronize cache » command. You may want to add a « kernel quirk » in scsi_da.c, it consists of adding an entry for your memory stick and telling that it does not support that command. You can use the following PR as a model for chaning the kernel, it's a PR I wrote for my own memory stick: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/54786 But first, be sure to upgrade your system to the latest current FreeBSD sources (checkout HEAD). Most quirks are now no more needed due to a recent refactoring of USB mass storage drivers. Cheers, -- Jean-Baptiste Quenot http://caraldi.com/jbq/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
USB memory stick
I have just purchased a MP3 player - which basically consists of a USB 128MB memory stick, with some audio hardware.. Anyways, when I plug the USB stick into my 5.1-RELEASE-p3 box, I am seeing the following in /var/log/messages: Oct 2 15:31:27 kernel: umass0: SigmaTel, Inc. USBMSC Audio Player, rev 1.10/0.01, addr 2 Oct 2 15:31:27 kernel: umass0: Get Max Lun not supported (IOERROR) Oct 2 15:31:27 kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Oct 2 15:31:27 kernel: da0: Removable Direct Access SCSI-4 device Oct 2 15:31:27 kernel: da0: 1.000MB/s transfers Oct 2 15:31:27 kernel: da0: 123MB (251904 512 byte sectors: 64H 32S/T 123C) Oct 2 15:31:32 kernel: umass0: BBB reset failed, IOERROR Oct 2 15:31:32 kernel: umass0: BBB bulk-in clear stall failed, IOERROR Oct 2 15:31:32 kernel: umass0: BBB bulk-out clear stall failed, IOERROR Oct 2 15:31:37 kernel: umass0: BBB reset failed, IOERROR Oct 2 15:31:37 kernel: umass0: BBB bulk-in clear stall failed, IOERROR Oct 2 15:31:37 kernel: umass0: BBB bulk-out clear stall failed, IOERROR Oct 2 15:31:42 kernel: umass0: BBB reset failed, IOERROR Oct 2 15:31:42 kernel: umass0: BBB bulk-in clear stall failed, IOERROR Oct 2 15:31:42 kernel: umass0: BBB bulk-out clear stall failed, IOERROR Oct 2 15:31:47 kernel: umass0: BBB reset failed, IOERROR Oct 2 15:31:47 kernel: umass0: BBB bulk-in clear stall failed, IOERROR Oct 2 15:31:47 kernel: umass0: BBB bulk-out clear stall failed, IOERROR Oct 2 15:31:52 kernel: umass0: BBB reset failed, IOERROR Oct 2 15:31:52 kernel: umass0: BBB bulk-in clear stall failed, IOERROR Oct 2 15:31:52 kernel: umass0: BBB bulk-out clear stall failed, IOERROR Oct 2 15:31:57 kernel: umass0: BBB reset failed, IOERROR Oct 2 15:31:57 kernel: umass0: BBB bulk-in clear stall failed, IOERROR Oct 2 15:31:57 kernel: umass0: BBB bulk-out clear stall failed, IOERROR Oct 2 15:32:02 kernel: umass0: BBB reset failed, IOERROR Oct 2 15:32:02 kernel: umass0: BBB bulk-in clear stall failed, IOERROR Oct 2 15:32:02 kernel: umass0: BBB bulk-out clear stall failed, IOERROR Oct 2 15:32:07 kernel: umass0: BBB reset failed, IOERROR Oct 2 15:32:07 kernel: umass0: BBB bulk-in clear stall failed, IOERROR Oct 2 15:32:07 kernel: umass0: BBB bulk-out clear stall failed, IOERROR Oct 2 15:32:12 kernel: umass0: BBB reset failed, IOERROR Oct 2 15:32:12 kernel: umass0: BBB bulk-in clear stall failed, IOERROR Oct 2 15:32:12 kernel: umass0: BBB bulk-out clear stall failed, IOERROR Oct 2 15:32:17 kernel: umass0: BBB reset failed, IOERROR Oct 2 15:32:17 kernel: umass0: BBB bulk-in clear stall failed, IOERROR Oct 2 15:32:17 kernel: umass0: BBB bulk-out clear stall failed, IOERROR Oct 2 15:32:22 kernel: umass0: BBB reset failed, IOERROR Oct 2 15:32:22 kernel: (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi sta tus == 0x0 Oct 2 15:32:27 kernel: umass0: BBB reset failed, IOERROR Oct 2 15:32:28 kernel: umass0: BBB bulk-in clear stall failed, IOERROR Oct 2 15:32:28 kernel: umass0: BBB bulk-out clear stall failed, IOERROR Oct 2 15:32:32 kernel: umass0: BBB reset failed, IOERROR Oct 2 15:32:33 kernel: umass0: BBB bulk-in clear stall failed, IOERROR Oct 2 15:32:33 kernel: umass0: BBB bulk-out clear stall failed, IOERROR Oct 2 15:32:37 kernel: umass0: BBB reset failed, IOERROR Oct 2 15:32:37 kernel: umass0: BBB bulk-in clear stall failed, IOERROR Oct 2 15:32:37 kernel: umass0: BBB bulk-out clear stall failed, IOERROR Oct 2 15:32:37 kernel: umass0: BBB reset failed, IOERROR Oct 2 15:32:37 kernel: umass0: BBB bulk-in clear stall failed, IOERROR Oct 2 15:32:38 kernel: umass0: BBB bulk-out clear stall failed, IOERROR Oct 2 15:32:38 kernel: umass0: BBB reset failed, IOERROR Oct 2 15:32:38 kernel: umass0: BBB bulk-in clear stall failed, IOERROR Oct 2 15:32:38 kernel: umass0: BBB bulk-out clear stall failed, IOERROR Oct 2 15:32:38 kernel: umass0: BBB reset failed, IOERROR Oct 2 15:32:38 kernel: umass0: BBB bulk-in clear stall failed, IOERROR Oct 2 15:32:38 kernel: umass0: BBB bulk-out clear stall failed, IOERROR Oct 2 15:32:38 kernel: Opened disk da0 -> 5 Oct 2 15:32:38 kernel: umass0: at uhub0 port 1 (addr 2) disconnected Oct 2 15:32:38 kernel: (da0:umass-sim0:0:0:0): lost device Oct 2 15:32:38 kernel: (da0:umass-sim0:0:0:0): removing device entry Oct 2 15:32:38 kernel: umass0: detached If I try and mount it, the box just freezez until I remove the device. Any ideas ? /mich ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Mount a Sony Memory stick
On Sun, Jul 20, 2003 at 09:31:03PM -0600, Sean Countryman wrote: > I'm trying to mount a 64MB Sony memory stick via a USB cable and need a > bit of help. > > I recompiled my kernel and upgraded to 4.8 RELEASE and now, if I boot > with the camera connected, it finds it as a SCSI device, but it > conflicts with my da0 device which has my / partition on it. > > I've got 4 SCSI disks already installed (devices da0 thru da3), and > there is not a da4 in the /dev directory. > > All I'd like is to be able to plug the camera in without rebooting and > be able to manually mount it, grab the photos, unmount it, and remove > it. You need to do two things: first of all, build yourself a custom kernel with your boot drive da0, and any other fixed disks you mount partitions from wired down -- that means the device will always appear at a fixed bus, target and LUN whenever you reboot. See the section on 'SCSI DEVICE CONFIGURATION' in /usr/src/sys/i386/conf/LINT Secondly, create the device nodes you need --- you get da0, da1, da2 and da3 by default. You need to run: # cd /dev # ./MAKEDEV da4 This should create /dev/da4, /dev/da4s1, /dev/da4s1a ... /dev/da4s1h amongst others. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
Mount a Sony Memory stick
I'm trying to mount a 64MB Sony memory stick via a USB cable and need a bit of help. I recompiled my kernel and upgraded to 4.8 RELEASE and now, if I boot with the camera connected, it finds it as a SCSI device, but it conflicts with my da0 device which has my / partition on it. I've got 4 SCSI disks already installed (devices da0 thru da3), and there is not a da4 in the /dev directory. All I'd like is to be able to plug the camera in without rebooting and be able to manually mount it, grab the photos, unmount it, and remove it. Ideas? Thanks, Sean J Countryman ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[doc pointer] 2 questions about usb memory stick ...
roland Mathieu <[EMAIL PROTECTED]> writes:
> I've got a 128MB usb memory stick (pmi memory). It works very well since
> I've modified file /usr/src/sys/cam/scsi/scsi_da.c by adding lines:
>
> {
> /*
> * Pmi / 128MB
> */
> {T_DIRECT, SIP_MEDIA_REMOVABLE, "Generic*", "USB Flash Disk*",
> "*"},
> /*quirks*/ DA_Q_NO_6_BYTE|DA_Q_NO_SYNC_CACHE
> },
>
> in the da_quirk_table structure.
>
> First question : who contact to add definitively these lines to scsi_da.c ?
"man send-pr"
> Second question: if memory stick is plugged when my computer boots up it is
> detected before my scsi disks. how to avoid that ?
> ( I must unplug it if I want my computer to boot because da0 is normally
> used by the first scsi disk :( )
[before 5.x; you didn't mention, so I assume you're using a recent 4.x release]
See the LINT file for information on "wiring down" your disk devices.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
2 questions about usb memory stick ...
I've got a 128MB usb memory stick (pmi memory). It works very well since
I've modified file /usr/src/sys/cam/scsi/scsi_da.c by adding lines:
{
/*
* Pmi / 128MB
*/
{T_DIRECT, SIP_MEDIA_REMOVABLE, "Generic*", "USB Flash Disk*",
"*"},
/*quirks*/ DA_Q_NO_6_BYTE|DA_Q_NO_SYNC_CACHE
},
in the da_quirk_table structure.
First question : who contact to add definitively these lines to scsi_da.c ?
Second question: if memory stick is plugged when my computer boots up it is
detected before my scsi disks. how to avoid that ?
( I must unplug it if I want my computer to boot because da0 is normally
used by the first scsi disk :( )
Any suggestions are welcome!
Thanks,
roland.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB memory stick
Louis LeBlanc wrote: On 01/05/03 01:24 PM, Flemming Froekjaer sat at the `puter and typed: I have a 128 MB USB memory stick from ez-memory. When I connect it to my FreeBSD 4.7 box it is recognized, but I can't mount it. Any hints? \Flemming Jan 5 12:56:53 athlon /kernel: umass0: USB Solid state disk, rev 1.10/1.00, addr 2 Jan 5 12:57:03 athlon /kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Jan 5 12:57:03 athlon /kernel: da0: Removable Direct Access SCSI-2 device Jan 5 12:57:03 athlon /kernel: da0: 650KB/s transfers Jan 5 12:57:03 athlon /kernel: da0: 126MB (258048 512 byte sectors: 64H 32S/T 126C) Jan 5 12:58:43 athlon /kernel: da0: reading primary partition table: error reading fsbn 0 How are you trying to mount it? Make sure you use the right filesystem spec. HTH Lou It must have been a pilot error, because now it's working now and I have no ide what I did different before :-o mount_msdos /dev/da0s1 /cam witch is exactly the same I use for my Olympus camera, works perfectly. Thanks for the hint. \Flemming To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: USB memory stick
On 01/05/03 01:24 PM, Flemming Froekjaer sat at the `puter and typed: > I have a 128 MB USB memory stick from ez-memory. > When I connect it to my FreeBSD 4.7 box it is recognized, but I can't mount it. > Any hints? > > \Flemming > > Jan 5 12:56:53 athlon /kernel: umass0: USB Solid state disk, rev 1.10/1.00, addr 2 > Jan 5 12:57:03 athlon /kernel: da0 at umass-sim0 bus 0 target 0 lun 0 > Jan 5 12:57:03 athlon /kernel: da0: Removable Direct > Access SCSI-2 device > Jan 5 12:57:03 athlon /kernel: da0: 650KB/s transfers > Jan 5 12:57:03 athlon /kernel: da0: 126MB (258048 512 byte sectors: 64H 32S/T 126C) > Jan 5 12:58:43 athlon /kernel: da0: reading primary partition table: error > reading fsbn 0 How are you trying to mount it? Make sure you use the right filesystem spec. HTH Lou -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://www.keyslapper.org ԿԬ Occam's eraser: The philosophical principle that even the simplest solution is bound to have something wrong with it. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
USB memory stick
I have a 128 MB USB memory stick from ez-memory. When I connect it to my FreeBSD 4.7 box it is recognized, but I can't mount it. Any hints? \Flemming Jan 5 12:56:53 athlon /kernel: umass0: USB Solid state disk, rev 1.10/1.00, addr 2 Jan 5 12:57:03 athlon /kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Jan 5 12:57:03 athlon /kernel: da0: Removable Direct Access SCSI-2 device Jan 5 12:57:03 athlon /kernel: da0: 650KB/s transfers Jan 5 12:57:03 athlon /kernel: da0: 126MB (258048 512 byte sectors: 64H 32S/T 126C) Jan 5 12:58:43 athlon /kernel: da0: reading primary partition table: error reading fsbn 0 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
