Building bluez-firmware-1.2.txz (origin /buildshare/ports/355755/comms/bluez-firmware) for powerpc-10-0 on XXX slot2: created x distfiles/ x distfiles/bluez-firmware-1.2.tar.gz x packages/ x packages/pkg-1.2.7_2.txz ELF ldconfig path: /lib /usr/lib /usr/lib/compat Make depends ===> bluez-firmware-1.2 depends on file: /usr/local/sbin/pkg - not found ===> Verifying install for /usr/local/sbin/pkg in /buildshare/ports/355755/ports-mgmt/pkg ===> Installing existing package /packages/pkg-1.2.7_2.txz Installing pkg-1.2.7_2... done If you are upgrading from the old package format, first run: # pkg2ng ===> Returning to build of bluez-firmware-1.2 Make install ===> bluez-firmware-1.2 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by bluez-firmware-1.2 for building ===> Extracting for bluez-firmware-1.2 => SHA256 Checksum OK for bluez-firmware-1.2.tar.gz. ===> Patching for bluez-firmware-1.2 ===> Configuring for bluez-firmware-1.2 ===> FreeBSD 10 autotools fix applied to /obj/buildshare/ports/355755/comms/bluez-firmware/work/bluez-firmware-1.2/aclocal.m4 ===> FreeBSD 10 autotools fix applied to /obj/buildshare/ports/355755/comms/bluez-firmware/work/bluez-firmware-1.2/configure configure: loading site script /buildshare/ports/355755/Templates/config.site checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking whether build environment is sane... yes checking for gawk... (cached) /usr/bin/awk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel configure: creating ./config.status config.status: creating Makefile ===> Building for bluez-firmware-1.2 ===> Staging for bluez-firmware-1.2 ===> Generating temporary packing list /bin/sh ./mkinstalldirs /obj/buildshare/ports/355755/comms/bluez-firmware/work/stage/usr/local/lib/firmware mkdir -p -- /obj/buildshare/ports/355755/comms/bluez-firmware/work/stage/usr/local/lib/firmware install -o root -g wheel -m 444 broadcom/BCM2033-MD.hex /obj/buildshare/ports/355755/comms/bluez-firmware/work/stage/usr/local/lib/firmware/BCM2033-MD.hex install -o root -g wheel -m 444 broadcom/BCM2033-FW.bin /obj/buildshare/ports/355755/comms/bluez-firmware/work/stage/usr/local/lib/firmware/BCM2033-FW.bin install -o root -g wheel -m 444 broadcom/BCM-LEGAL.txt /obj/buildshare/ports/355755/comms/bluez-firmware/work/stage/usr/local/lib/firmware/BCM-LEGAL.txt install -o root -g wheel -m 444 st/STLC2500_R4_00_03.ptc /obj/buildshare/ports/355755/comms/bluez-firmware/work/stage/usr/local/lib/firmware/STLC2500_R4_00_03.ptc install -o root -g wheel -m 444 st/STLC2500_R4_00_06.ssf /obj/buildshare/ports/355755/comms/bluez-firmware/work/stage/usr/local/lib/firmware/STLC2500_R4_00_06.ssf install -o root -g wheel -m 444 st/STLC2500_R4_02_02_WLAN.ssf /obj/buildshare/ports/355755/comms/bluez-firmware/work/stage/usr/local/lib/firmware/STLC2500_R4_02_02_WLAN.ssf install -o root -g wheel -m 444 st/STLC2500_R4_02_04.ptc /obj/buildshare/ports/355755/comms/bluez-firmware/work/stage/usr/local/lib/firmware/STLC2500_R4_02_04.ptc NOTICE ====== You need to have the ubtbcmfw(8) and ng_ubt(8) kernel modules in our kernel. This can be accomplished by adding the following lines to /boot/loader.conf: ubtbcmfw_load=yes ng_ubt_load=yes Furthermore you need to ensure that the bcmfw(1) utility downloads the firmware into the dongle on insertion. This can be done by adding the followign lines to /etc/devd.conf (devd(8) should run by default): # Requires the port BCM2033 to be installed # and the ubtbcmfw(8) and ng_ubt(8) kernel modules # to be loaded prior to insertion. # attach 100 { match "vendor" "0x0a5c"; match "product" "0x2033"; action "if test -d /usr/local/lib/firmware; then bcmfw -n $device-name -m /usr/local/lib/firmware/BCM2033-MD.hex -f /usr/local/lib/firmware/BCM2033-FW.bin; fi"; } Or alternatively load these files manually with: cd /usr/local/lib/firmware bcmfw -n ubtbcmfw0 -m BCM2033-MD.hex -f BCM2033-FW.bin you should then see the following lines in your dmesg(8): ubtbcmfw0: on uhub0 ubtbcmfw0: at uhub0 port 2 (addr 7) disconnected ubtbcmfw0: detached ubt0: on uhub0 ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 ubt0: Interface 1 (alt.config 4) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=64; nframes=5, buffer size=320 ====> Compressing man pages (compress-man) ===> Installing for bluez-firmware-1.2 ===> Checking if comms/bluez-firmware already installed ===> Registering installation for bluez-firmware-1.2 Installing bluez-firmware-1.2... done NOTICE ====== You need to have the ubtbcmfw(8) and ng_ubt(8) kernel modules in our kernel. This can be accomplished by adding the following lines to /boot/loader.conf: ubtbcmfw_load=yes ng_ubt_load=yes Furthermore you need to ensure that the bcmfw(1) utility downloads the firmware into the dongle on insertion. This can be done by adding the followign lines to /etc/devd.conf (devd(8) should run by default): # Requires the port BCM2033 to be installed # and the ubtbcmfw(8) and ng_ubt(8) kernel modules # to be loaded prior to insertion. # attach 100 { match "vendor" "0x0a5c"; match "product" "0x2033"; action "if test -d /usr/local/lib/firmware; then bcmfw -n $device-name -m /usr/local/lib/firmware/BCM2033-MD.hex -f /usr/local/lib/firmware/BCM2033-FW.bin; fi"; } Or alternatively load these files manually with: cd /usr/local/lib/firmware bcmfw -n ubtbcmfw0 -m BCM2033-MD.hex -f BCM2033-FW.bin you should then see the following lines in your dmesg(8): ubtbcmfw0: on uhub0 ubtbcmfw0: at uhub0 port 2 (addr 7) disconnected ubtbcmfw0: detached ubt0: on uhub0 ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 ubt0: Interface 1 (alt.config 4) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=64; nframes=5, buffer size=320 Make package ===> Building package for bluez-firmware-1.2 slot2: removed