Date: Tue, 23 Apr 2019 12:39:20 -0700 From: Adrian Chadd <adrian.chadd@gmail.com> To: Serge Semenenko <serge.a1@gmail.com> Cc: Matthias Apitz <guru@unixarea.de>, "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org> Subject: Re: Atheros AR5B22 WLAN+Bluetooth support on FreeBSD Message-ID: <CAJ-Vmok4amtPoN0-p=47jnhP6j4Vx=F%2BAx6aNz4rHyq30pjRCQ@mail.gmail.com> In-Reply-To: <CAFOmZk0pMHmHbfmeHE1QMcwKNALJPQFJe9Ygqq%2B5aWdu369e8w@mail.gmail.com> References: <CAFOmZk2kVqhfsfTfmyaF7aZPmLjPmgtNk7DZoA=GteZvVPmJJA@mail.gmail.com> <20190421071938.GA59008@c720-r342378> <CAFOmZk0pMHmHbfmeHE1QMcwKNALJPQFJe9Ygqq%2B5aWdu369e8w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Do you have the kernel environment variable setup to say it's a WB222? -a On Tue, 23 Apr 2019 at 12:37, Serge Semenenko <serge.a1@gmail.com> wrote: > Could it matter that I load modules from rc.conf? > > kld_list=3D"if_ath if_ath_pci linux linsysfs linprocfs xhci umass ums > snd_hda /boot/modules/i915kms.ko /boot/modules/acpi_call.ko" > > =D0=B2=D1=81, 21 =D0=B0=D0=BF=D1=80. 2019 =D0=B3. =D0=B2 11:05, Matthias = Apitz <guru@unixarea.de>: > >> El d=C3=ADa s=C3=A1bado, abril 20, 2019 a las 02:16:49p. m. +0300, Serge= Semenenko >> escribi=C3=B3: >> >> > 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=3D0 md=3DHOST spd= =3DFULL >> (12Mbps) pwr=3DON (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 doe= s >> work. >> >> I think some of the nd_*.ko modules do not attach and due to this the >> device is not created. >> >> matthias >> >> -- >> Matthias Apitz, =E2=9C=89 guru@unixarea.de, http://www.unixarea.de/ >> +49-176-38902045 >> Public GnuPG key: http://www.unixarea.de/key.pub >> N =E2=82=AC I N zur EU! >> "Gegen das EU-Europa der Banken, Konzerne und Kriegstreiber. >> F=C3=BCr ein soziales und friedliches Europa der V=C3=B6lker." DKP >> >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmok4amtPoN0-p=47jnhP6j4Vx=F%2BAx6aNz4rHyq30pjRCQ>