freebsd-wifibox: wifibox on a Dell XPS with Atheros not starting

Hello,

I saw wifibox in the latest FreeBSD Quarterly Report and and excited to use it!

I’m on:

FreeBSD bsdell 14.0-CURRENT FreeBSD 14.0-CURRENT #67 main-n255572-bf46c0a9ae4e: Tue May 10 21:23:49 EDT 2022 root@bsdell:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64

With:

none3@pci0:2:0:0:       class=0x028000 rev=0x32 hdr=0x00 vendor=0x168c device=0x003e subvendor=0x1a56 subdevice=0x143a
    vendor     = 'Qualcomm Atheros'
    device     = 'QCA6174 802.11ac Wireless Network Adapter'
    class      = network

And I installed wifibox-alpine-ath10k-20220430 (I’m pretty sure it’s an ath10k)

I configured bhyve.confg with:

passthru=2/0/0

I then did sudo service wifibox onestart.

I see the following every few seconds:

2022-06-11T18:23:56-0400 WARN The PPT device could not be destroyed

I’m unable to ping anything (not sure if I should be able to ping anything).

I looked in /var/run/wifibox/appliance/log and there are no logs. I also did ps auxww | grep bhy and there are not running bhyve instances.

In /var/log/messages I see:

Jun 11 18:23:41 bsdell kernel: ppt0 mem 0xdc000000-0xdc1fffff irq 18 at device 0.0 on pci2
Jun 11 18:23:42 bsdell kernel: ppt0: detached
Jun 11 18:23:42 bsdell kernel: pci2: <network> at device 0.0 (no driver attached)
Jun 11 18:23:48 bsdell kernel: ppt0 mem 0xdc000000-0xdc1fffff irq 18 at device 0.0 on pci2
Jun 11 18:23:49 bsdell kernel: ppt0: detached
Jun 11 18:23:49 bsdell kernel: pci2: <network> at device 0.0 (no driver attached)
Jun 11 18:23:55 bsdell kernel: ppt0 mem 0xdc000000-0xdc1fffff irq 18 at device 0.0 on pci2
Jun 11 18:23:56 bsdell kernel: ppt0: detached
Jun 11 18:23:56 bsdell kernel: pci2: <network> at device 0.0 (no driver attached)

One thing to note is that I currently use a USB dongle for my wifi, and I started the machine with the dongle installed and then unplugged it before starting wifibox.

Any thoughts on what’s going on? Can I acquire any more details for you or try anything?

Thank you.

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 42 (20 by maintainers)

Most upvoted comments

@pgj I closed the issue for the main problem: getting it working. I’ll do some testing with turning console back off and see if it has trouble starting again. I’m not sure why the console setting change that behaviour, though. Note: this happened even during bootup, now that I have wifibox enabled on startup.

Will get back to you with what happens when I flip console back off.

IT’S WOOOORKIIIIIIIIIIIIIIIIING! Wooo, thank you!

I’m still not sure why I need to run wifibox rather than via the service.