El día sábado, abril 20, 2019 a las 02:16:49p. m. +0300, Serge Semenenko escribió:
> Hi > > It works for me with such section in devd.conf > > attach 200 { > device-name "ubt[0-9]+"; > match "vendor" "0x0cf3"; > match "product" "0xe006"; > action "sleep 2 && /usr/sbin/ath3kfw -d $ugen && sleep 2 && > /etc/rc.d/bluetooth quietstart $device-name"; > }; I have added the above lines to /etc/devd.conf, ofc with the vendor and product ID of my chip: $ usbconfig ... ugen0.3: <vendor 0x0489 product 0xe056> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) and place the firmware in the directory where /usr/sbin/ath3kfw is looking for it, into /usr/share/firmware/ath3k/ar3k/ The problem remains: no device /dev/ubt0 gets created (and the attach rule does not apply. When I change 'attach 200' to 'notify 100', /usr/sbin/ath3kfw gets called and the firmware gets loaded into the chip. But nothing of BT does work. I think some of the nd_*.ko modules do not attach and due to this the device is not created. matthias -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub N € I N zur EU! "Gegen das EU-Europa der Banken, Konzerne und Kriegstreiber. Für ein soziales und friedliches Europa der Völker." DKP _______________________________________________ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"