18:10 <nta> <jhovold> "nta: we currently don't know how..." <- as to 'where the device address comes from on x13s', i just poked around the windows driver a bit and it appears to be the case that... the windows driver just generates a mostly-random address on first init and saves it in the registry (the inf has a value named `RandomBTAddrEnabled` set)

18:10 <nta> there's a log print in there that says "Registry/Randomly generate BT address 0x[%x %x %x %x 03 01]." in this case

18:10 <nta> i guess this is a thing that userspace should configure on devices i suppose

19:08 <jhovold> nta: that's really interesting, not sure if it applies generally though as my X13s had a Wistron allocated address

19:08 <jhovold> that's a preproduction machine, but still

19:09 <konradybcio> @nta any chance you have some mac addr randomization turned on?

19:39 <nta> jhovold, i just looked at the windows driver bundle from the site as i broke my actual install- could be a code path that's not actually being hit in practice (e.g. firmware customizations), whoops :D

19:40 <nta> could also be factory installs set an actual mac in the registry in some deployment flow.. hmm

20:00 <nta> i just checked an image of the last Windows install i booted on there and it did have the randomly-generated BdAddr field set by the driver at least, but it could be firmware has ignored it and used it from somewhere else of course (e.g. one of many nvram things)

20:00 <nta> .. or whatever these nvm* files are, at least

20:02 <nta> can't currently boot Windows on there easily to double-check if it is this random MAC or not, sadly :(

23:20 <konradybcio> nta you can easily restore with the volterra BMR

23:20 <konradybcio> been there..

23:38 <steev> nta: does it include a bsrc_bt.bin file?

23:41 <steev> oh, nevermind that's the pep file