agners
commented
3 years ago The modprobe binary used in HAOS is not from the busybox package but from the kmod package (BR2_PACKAGE_KMOD). Afaict this gets selected implicitly somehow. This is the tool which comes from kernel.org and I think blacklist is a feature enabled by default.
Are you sure you blacklist the module correctly? From what I can tell the module filename is dvb-usb-rtl28xxu.ko, so I'd guess you need to use blacklist dvb-usb-rtl28xxu to blacklist that module. Although, I read on the Arch Linux Wiki that - and _ can be used interchangeably, so I guess its not that.
asdfghjkai
github-actions[bot]
HarryJHolmes
Hardware Environment
Home Assistant OS release:
System Health
Home Assistant Community Store
GitHub API | ok -- | -- Github API Calls Remaining | 4923 Installed Version | 1.14.1 Stage | running Available Repositories | 953 Installed Repositories | 11Home Assistant Cloud
logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 6.3 -- | -- update_channel | stable supervisor_version | supervisor-2021.09.0 docker_version | 20.10.7 disk_total | 219.4 GB disk_used | 27.2 GB healthy | true supported | true board | rpi4-64 supervisor_api | ok version_api | ok installed_addons | File editor (5.3.3), Check Home Assistant configuration (3.8.0), AirCast (3.1.1), Samba share (9.5.1), Mosquitto broker (6.0.1), Nextcloud Backup (0.16.2), SSH & Web Terminal (9.0.1), Home Panel (2.2.0), Portainer (2.0.0), zigbee2mqttassistant (0.3.157), Zigbee2mqtt (1.21.1-1), Git pull (7.13.1), MariaDB (2.4.0), Grafana (7.0.2), InfluxDB (4.1.1), Wmbusmeters (W-MBus to MQTT) (0.2.19)Lovelace
dashboards | 3 -- | -- resources | 4 views | 17 mode | storageSupervisor logs:
Journal logs:
Lots of these. I think one of my thermostat's is not playing too well with z2m
Kernel logs:
Description of problem: I'm trying to use a dvb tuner as an SDR to communicate (or listen) to responses from my home water meter. The details do not matter too much, the main issue is that the tuner is (correctly) identified by the OS as a DVB tuner and as such loads the appropriate module. Because I do not want it to do this, I followed the instructions here to add an entry to modprobe.d, to blacklist the kernel module in question. For what it's worth, it's dvb_usb_rtl28xxu.
This upon restart had no effect, and I started digging down towards the os build, and busybox, which has a number of configurations around modprobe here including toggles to enable blacklisting. I confirmed I would need to enable CONFIG_MODPROBE as well as CONFIG_FEATURE_MODPROBE_BLACKLIST which I found within the source here
I built a 6.3 image (at the time) from source using the instructions provided, and with this subtle tweak, and then tested on my RPi - the same symptoms.
Question is, what else needs to be changed, is there anyway to integrate this as part of the standard build, or is the idea bust and I should just purchase a proper radio dongle.
I was hoping the above would provide a solution and I could raise a PR, but unfortunately not. Happy to try alternative options and build from source to confirm/deny if any proposed fixes work.