Re: Strange behavior of bluetooth chip

[Vitaly Shevtsov <shev.vt1984%gmail.com@localhost>]

Thank you, that makes sense.

On Fri, Dec 22, 2023 at 9:07 PM Iain Hibbert <plunky%ogmig.net@localhost> wrote:
>
>
>
> On 22 December 2023 14:59:48 GMT, Iain Hibbert <plunky%ogmig.net@localhost> wrote:
> >Hello
> >
> >These Intel Bluetooth chips are unsupported for now. The problem with them is that unfortunately they identify as a Bluetooth device but do not work as one until the firmware is loaded. Alas we don't have a way as yet to provide for device specific initialisations and I've been too busy lately to work on that. I do have one of them in my laptop but have been using an external dongle.
> >
> >The reason it works after Windows initialises it, is a reset doesn't usually take the power away so it remains in firmware loaded state.
> >
> >
> >On 22 December 2023 12:18:15 GMT, Vitaly Shevtsov <shev.vt1984%gmail.com@localhost> wrote:
> >>Hello.
> >>
> >>My wireless chip is defined as: Intel Wireless AC 9260 (different
> >>network, version 0x29) on pci1 dev 0, function 0 not configured.
> >>
> >>When booting the system I always got an error:
> >>CommanComplete opcode failed (003|0003) (status=0x01).
> >>
> >>When I tried to manually raise the interface via `btconfig ubt0 up`, I
> >>received the error:
> >>btconfig: SIOCSBTFLAGS: Resource temporarily unavailable.
> >>
> >>I decided that my chip was not working until I reboot into Windows and
> >>then back into NetBSD, after which the bluetooth worked.
> >>
> >>How so? :) I suspect that the firmware is missing and Windows uploads
> >>it. If so then I don't understand how it survives the reboot.
> >
> >On my phone
> On my phone