Re: libusb-config missing?
On Sunday 06 February 2011 08:56:44 Daniel O'Connor wrote: On 05/02/2011, at 16:11, Daniel O'Connor wrote: The correct solution is 'USE_LIBUSB=yes' with relevant magic in bsd.port.mk Unfortunately this is unlikely to occur because it's only needed for 7.x which will be dying within the next few years. USE_LIBUSB= would be nice, I will see if I can author such a thing.. I have.. http://www.dons.net.au/~darius/libusb-8.diff I only did a few ports because I wasn't sure if it was the correct approach and it's quite tedious :) FYI: libusb in FreeBSD base depends on libpthread . --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: libusb-config missing?
On 06/02/2011, at 21:41, Hans Petter Selasky wrote: I have.. http://www.dons.net.au/~darius/libusb-8.diff I only did a few ports because I wasn't sure if it was the correct approach and it's quite tedious :) FYI: libusb in FreeBSD base depends on libpthread . OK, easy fixed. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: FTDI device Olimex AVRISP-500 does not show up under FreeBSD. Linux driver source code available, translating this to changes in FreeBSD uftdi kern module?
On Sun, 6 Feb 2011, Hans Petter Selasky wrote:
On Saturday 05 February 2011 22:26:03 Benjamin wrote:
The Olimex is a programmer for AVR microcontrollers. It is apparently an
FTDI device and works under Linux. The product page at
http://www.olimex.com/dev/avr-isp500.html provides source code for a
Linux FTDI kernel module.
I have the looked through the Linux FTDI driver source code and have
even been given a patch by a helpful member at the FreeBSD forums
(wblock) but so far no luck.
Here is what it is identified as when plugged in to USB:
Feb 5 13:30:07 blackbox kernel: ugen1.2: Olimex Ltd. at usbus1
It should ideally show up as cuaU0 or ttyUSB0 as far as I understand.
A quick search through the Linux driver source code to find all
instances of OLIMEX:
grep OLIMEX ftdi_*.[c,h]
ftdi_sio.c: { USB_DEVICE(OLIMEX_VID, OLIMEX_ARM_USB_OCD_PID),
ftdi_sio.c: { USB_DEVICE(OLIMEX_VID, OLIMEX_AVR_ISP500_ISO_PID) },
ftdi_sio_ids.h:#define OLIMEX_VID 0x15BA
ftdi_sio_ids.h:#define OLIMEX_ARM_USB_OCD_PID 0x0003
ftdi_sio_ids.h:#define OLIMEX_AVR_ISP500_ISO_PID0x000B
Note that the above is Linux kernel module source. Myself and wblock
have tried to hack the FreeBSD uftdi kernel module to no avail. He
offered the attached patch which did not seem to work.
The Linux driver source is available here:
http://www.olimex.com/dev/soft/avr/AVR-ISP500/AVR-ISP500_linux_driver.zip
Does this look like something that could easily be changed in the
FreeBSD uftdi kern module?
Your patch looks OK. Can you create a PR so that your patch doesn't get lost?
I was going to also patch the uftdi man page and submit a PR with all
three patches if it worked. But unfortunately, it doesn't. Only vendor
ID seems verified so far.
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: mount and umount large capacity external USB HDD (fstab)
On Sat, 29 Jan 2011 18:24:42 -0500 freebsd_u...@guice.ath.cx wrote: Hope we are posting to the correct list ... We__re using a laptop for our temp mail-server and would like to attach a two (2) or three (3) TB external USB HDD for back-up purposes. Would someone be kind enough to point us to a step-by-step article on what needs to be entered in the /etc/fstab to allow us to leave the drive connected and facilitate auto mount/umount across system reboots; the results Google are presenting isn__t sufficient. Perhaps it__s or search terms that aren__t on point. Thanks. The following link provides a 'recipe' for using gpart to partition the disk. http://scratching.psybermonkey.net/2010/06/freebsd-how-to-format-partition.html If you use the '-L' flag to newfs after creating one or more partitions, e.g. newfs -L image daXp1 This will create a device node in /dev/ufs (/dev/ufs/image). You may then create fstab entries as usual, but using the label device, e.g. /dev/ufs/image/usr/image ufs rw 2 2 Unless you add noauto to the options (rw,noauto) the system will fsck and mount the partition on boot. You can, of course, create several partitions on the disk, using a separate label (-L) for each. Is this what you needed? Thank you for your prompt reply. This appears to be what we were looking for, however, the gpart method has opened up another list of speed-bumps (so to speak), meaning, while reading about 'gpart' on our fbsd-7.3-P1 system; the command 'gpart show' yields no results. We have shelved the gpart suggestion and will try and do this with itemized commands from the CLI; something that we have never needed to do in the past --first time for everything. (smile) - Currently our USB drive is seen as: da0 at umass-sim0 bus 0 target 0 lun 0 da0: Seagate FA GoFlex Desk 0155 Fixed Direct Access SCSI-4 device da0: 40.000MB/s transfers da0: 2861588MB (732566645 4096 byte sectors: 255H 63S/T 45600C) we are considering using the following: # dd if=/dev/zero of=/dev/da0 bs=1k count=1 # fdisk -BI da0 #Initialize your new disk # bsdlabel -B -w da1s1 auto #Label it. # bsdlabel -e da0s1 # Edit the bsdlabel just created and add any partitions. # mkdir -p /mnt/drv-e # mkdir -p /mnt/drv-f # mkdir -p /mnt/drv-g # mkdir -p /mnt/drv-h # newfs /dev/da0s1e # Repeat this for every partition you created. # newfs /dev/da0s1f # newfs /dev/da0s1g # newfs /dev/da0s1h # mount /dev/da1s1e /mnt/drv-e # Mount the partition(s) # mount /dev/da1s1f /mnt/drv-f # mount /dev/da1s1g /mnt/drv-g # mount /dev/da1s1h /mnt/drv-h - # vi /etc/fstab # Add the appropriate entry/entries to your /etc/fstab. Is our thinking 'sane' when doing the above? Initial example taken/borrowed from the FreeBSD Handbook 18.3.2.1 Using Slices. - - Lastly, we don't fully understand, nor have we found an article or man page that explains (in a way we can understand), how to use the 'bs= ' to the 'dd' command. Within the 'man dd' the examples show 'bs=512' however, in the FreeBSD Handbook 18.3.2.1 Using Slices, they demonstrate dd using 'bs=1k'; we continue to be confused. Should we take this confusion to another list? Thanks in advance ... ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: usb/154506: [umass] Copying dir with large files makes FreeBSD load above 4.00 and is rather slow
Old Synopsis: Copying dir with large files makes FreeBSD load above 4.00 and is rather slow New Synopsis: [umass] Copying dir with large files makes FreeBSD load above 4.00 and is rather slow Responsible-Changed-From-To: freebsd-amd64-freebsd-usb Responsible-Changed-By: linimon Responsible-Changed-When: Mon Feb 7 03:32:44 UTC 2011 Responsible-Changed-Why: reclassify. http://www.freebsd.org/cgi/query-pr.cgi?pr=154506 ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: mount and umount large capacity external USB HDD (fstab)
This is a corrected version of my last post -- typo discovered -- On Sat, 29 Jan 2011 18:24:42 -0500 freebsd_u...@guice.ath.cx wrote: Hope we are posting to the correct list ... We__re using a laptop for our temp mail-server and would like to attach a two (2) or three (3) TB external USB HDD for back-up purposes. Would someone be kind enough to point us to a step-by-step article on what needs to be entered in the /etc/fstab to allow us to leave the drive connected and facilitate auto mount/umount across system reboots; the results Google are presenting isn__t sufficient. Perhaps it__s or search terms that aren__t on point. Thanks. The following link provides a 'recipe' for using gpart to partition the disk. http://scratching.psybermonkey.net/2010/06/freebsd-how-to-format-partition.html If you use the '-L' flag to newfs after creating one or more partitions, e.g. newfs -L image daXp1 This will create a device node in /dev/ufs (/dev/ufs/image). You may then create fstab entries as usual, but using the label device, e.g. /dev/ufs/image/usr/image ufs rw 2 2 Unless you add noauto to the options (rw,noauto) the system will fsck and mount the partition on boot. You can, of course, create several partitions on the disk, using a separate label (-L) for each. Is this what you needed? Thank you for your prompt reply. This appears to be what we were looking for, however, the gpart method has opened up another list of speed-bumps (so to speak), meaning, while reading about 'gpart' on our fbsd-7.3-P1 system; the command 'gpart show' yields no results. We have shelved the gpart suggestion and will try and do this with itemized commands from the CLI; something that we have never needed to do in the past --first time for everything. (smile) - Currently our USB drive is seen as: da0 at umass-sim0 bus 0 target 0 lun 0 da0: Seagate FA GoFlex Desk 0155 Fixed Direct Access SCSI-4 device da0: 40.000MB/s transfers da0: 2861588MB (732566645 4096 byte sectors: 255H 63S/T 45600C) we are considering using the following: # dd if=/dev/zero of=/dev/da0 bs=1k count=1 # fdisk -BI da0 #Initialize your new disk # bsdlabel -B -w da0s1 auto #Label it. # bsdlabel -e da0s1 # Edit the bsdlabel just created and add any partitions. # mkdir -p /mnt/drv-e # mkdir -p /mnt/drv-f # mkdir -p /mnt/drv-g # mkdir -p /mnt/drv-h # newfs /dev/da0s1e # Repeat this for every partition you created. # newfs /dev/da0s1f # newfs /dev/da0s1g # newfs /dev/da0s1h # mount /dev/da1s1e /mnt/drv-e # Mount the partition(s) # mount /dev/da1s1f /mnt/drv-f # mount /dev/da1s1g /mnt/drv-g # mount /dev/da1s1h /mnt/drv-h - # vi /etc/fstab # Add the appropriate entry/entries to your /etc/fstab. Is our thinking 'sane' when doing the above? Initial example taken/borrowed from the FreeBSD Handbook 18.3.2.1 Using Slices. - - Lastly, we don't fully understand, nor have we found an article or man page that explains (in a way we can understand), how to use the 'bs= ' to the 'dd' command. Within the 'man dd' the examples show 'bs=512' however, in the FreeBSD Handbook 18.3.2.1 Using Slices, they demonstrate dd using 'bs=1k'; we continue to be confused. Should we take this confusion to another list? Thanks in advance ... ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: mount and umount large capacity external USB HDD (fstab)
I really hope we aren't as ignorant as what these articles are making us appear to be ... We will try and not be long winded on this. OUR GOAL: To add a USB 3TB drive, with a UFS2 fs, to an already running x86 FreeBSD 7.3-p1 system. PROBLEMS The following sections from the FBSD Handbook are erroneous and/or not properly working with this device. 18.3.1 Using sysinstall(8) After all is said and done, we are only left with da0s1, da0s2 and da0s3 within /dev. 18.3.2 Using Command Line Utilities 18.3.2.1 Using Slices some of the commands in this section do not yield positive results and fail. Example, as seen in the handbook: WORKSTATION# dd if=/dev/zero of=/dev/da0 bs=1k count=1 dd: /dev/da0: Invalid argument 1+0 records in 0+0 records out 0 bytes transferred in 0.000108 secs (0 bytes/sec) When we edit the bs=1k to bs=512k this appears to complete successfully. Another example: WORKSTATION# fdisk -BI da0 *** Working on device /dev/da0 *** fdisk: /boot/mbr: length must be a multiple of sector size Honestly, how does this stuff make it in to the handbook? Lets look at a final example from the handbook; how is a novice suppose to know what to do in the resulting file after using the following command, bsdlabel -e da0s1 The system we are working on/with - WORKSTATION# uname -r 7.3-RELEASE-p1 - WORKSTATION# df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/ad4s1a484M412M 33M93%/ devfs 1.0K1.0K 0B 100%/dev /dev/ad4s1f3.4G168K3.2G 0%/tmp /dev/ad4s1d106G 23G 74G23%/usr /dev/ad4s1e 29G4.3G 22G16%/var - USB DEVICE: (3TB) da0 at umass-sim0 bus 0 target 0 lun 0 da0: Seagate FA GoFlex Desk 0155 Fixed Direct Access SCSI-4 device da0: 40.000MB/s transfers da0: 2861588MB (732566645 4096 byte sectors: 255H 63S/T 45600C) Everyone says read the handbook, then when we do, this is what we get. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: mount and umount large capacity external USB HDD (fstab)
- Message from em...@guice.ath.cx - Date: Mon, 7 Feb 2011 00:39:08 -0500 From: em...@guice.ath.cx Subject: Re: mount and umount large capacity external USB HDD (fstab) To: duane.hes...@gmail.com Cc: freebsd-usb@freebsd.org Lastly, we don't fully understand, nor have we found an article or man page that explains (in a way we can understand), how to use the 'bs= ' to the 'dd' command. Within the 'man dd' the examples show 'bs=512' however, in the FreeBSD Handbook 18.3.2.1 Using Slices, they demonstrate dd using 'bs=1k'; we continue to be confused. Should we take this confusion to another list? bs is the block size for the transfers. If you want to fill a harddisk you want to use a big blocksize such as bs=1m. When you have a smaller block size dd will be more busy pushing the blocks around which will only increase CPU load and lower your transfer rate. As for the unit following the number: Where sizes are specified, a decimal, octal, or hexadecimal number of bytes is expected. If the number ends with a ``b'', ``k'', ``m'', ``g'', or ``w'', the number is multiplied by 512, 1024 (1K), 1048576 (1M), 1073741824 (1G) or the number of bytes in an integer, respectively. Two or more numbers may be separated by an ``x'' to indicate a product. - End message from em...@guice.ath.cx - #_ __ _ __ http://www.nagilum.org/ \n icq://69646724 # # / |/ /__ _(_) /_ _ nagi...@nagilum.org \n +491776461165 # # // _ `/ _ `/ / / // / ' \ Amiga (68k/PPC): AOS/NetBSD/Linux # # /_/|_/\_,_/\_, /_/_/\_,_/_/_/_/ Mac (PPC): MacOS-X / NetBSD /Linux # # /___/ x86: FreeBSD/Linux/Solaris/Win2k ARM9: EPOC EV6 # cakebox.homeunix.net - all the machine one needs.. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
