Error while receiving via netlink: Object busy about owl

[Atemu]

In my case the interface was not managed by NetworkManager, dhcpd etc. or connected to anything. What fixed the issue was simply setting the link down via ip link set <devicename> down.

[schmittner]

Have a look here: seemoo-lab/opendrop#21 (comment)

[Gal-Schwietzer]

I am a bit of a linux beginner so can you please tell me how to do those things(kill NetworkManager...)?

[Titaniumtown]

run this:
sudo iw phy phy0 interface add mon0 type monitor flags active

[Titaniumtown]

And then do:
sudo iw dev wlan0 del

[xyx0826]

I ran into this issue on Ubuntu. I use a separate adapter for owl, so I was able to fix it by telling NetworkManager to unmanage the adapter: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_networking/configuring-networkmanager-to-ignore-certain-devices_configuring-and-managing-networking

[mcr-ksh]

on Rasberian with an external card:

1. rmmod mt76x2u (in my case the driver)
2. limit wpa_supplicant to internal interface -> name wpa_supplicant.conf -> wpa_supplicant-wlan0.conf
3. systemctl stop dhcpcd
4. modprobe mt76x2u
5. start owl
6. systemctl restart dhcpcd wpa_supplicant

[Binozo]

I got it running by running sudo systemctl stop dhcpcd on a Raspberry Pi 4 with Up-to-date Raspberry Pi OS :)