Hi!
The issue is pretty much summarised here:
https://tvheadend.org/boards/5/topics/22310
It appeared fixed in 42.1, then broke again in 42.3. Ie if I just
restart and start TVHeadend it breaks. Reboot, run Wscan then run
TVHeadend, then it works.
Dunno if the suggestions to “options dvb-usb-rtl28xxu adapter_nr=5”
applies here as I have two additional adapters with rtl2832 that I want
to keep?
Any ideas how to fix this permanently?
OK. Digging further…
tvburk:~ # ls /dev/dvb/adapter0
demux0 dvr0 frontend0 frontend1 net0
Problem is that the card only has one demux. When tvh initialises it
starts frontend0, the wrong one, and that grabs the mux. If I run wscan
and tell it to look for DVB-C it skips frontend0 and gones to
frontend1, after that, all is fine.
IS there reallo no nicer way to fix this than to rename frontend0 to
frontend99 and frontend1 to frontend0??
Hi
What about crafting a udev rule to sort all of the adapters out (or run the script to rename as per your link)?
Malcolmlewis,
> What about crafting a udev rule to sort all of the adapters out (or run
> the script to rename as per your link)?
Yes. I tried udev rules and renamed the adapter, but then it would not
work at all. As you say, a script would rely on the adapter number being
the same always, so given that I know the vendor and device id, how would
such a rule look?
On Tue 05 Jun 2018 05:53:16 AM CDT, Anders Gustafsson wrote:
Malcolmlewis,
> What about crafting a udev rule to sort all of the adapters out (or
> run the script to rename as per your link)?
Yes. I tried udev rules and renamed the adapter, but then it would not
work at all. As you say, a script would rely on the adapter number
being the same always, so given that I know the vendor and device id,
how would such a rule look?
- Anders Gustafsson
The Aaland Islands (N60 E20)
Hi
Create a file in /etc/udev/rules.d/60-astrometa.rules with something
like;
SUBSYSTEMS=="usb", ATTRS{idVendor}=="xxxx", ATTRS{idProduct}=="xxxx", MODE:="0NNN", GROUP="????"
ACTION=="add", RUN+="/full/path/to/your/script"
You can then use the command (as root user) udevadm monitor to watch
what’s happening when the device is plugged in and tweak as required.
Have a fgrep through /usr/lib/udev/rules.d for lots of examples 
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
SLES 15 RC4 | GNOME Shell 3.26.2 | 4.12.14-18-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
Thanks. Let me try that!