[Info] modprobe force_pid_filter_usage may cause issues
Posted: Wed Apr 18, 2012 6:14 amHey all.
I have multiple DVB-T dongles (None TBS) and the 5922 connected to my microserver, I was having reception issues on one of my DVB-T dongles and in an attempt to fix it I'd enabled the force_pid_filter_usage in my modprobe config, which sadly made no difference but anyway...
With force_pid_filter_usage enabled, I noticed the 5922 during scanning would get stuck & completely freeze TVheadend and w_scan, the microserver was still responding but just those apps hanged, requiring a reboot, I removed force_pid_filter_usage from my config and all is well again!
I'm not sure why it would make such a difference, but I thought I'd post anyway in case someone else thought that using force_pid_filter_usage would be a good idea
Also the latest drivers v120412 are very stable on my system (without the force_pid_filter_usage enabled obviously
), so kudos to whoever writes them!
I have multiple DVB-T dongles (None TBS) and the 5922 connected to my microserver, I was having reception issues on one of my DVB-T dongles and in an attempt to fix it I'd enabled the force_pid_filter_usage in my modprobe config, which sadly made no difference but anyway...
With force_pid_filter_usage enabled, I noticed the 5922 during scanning would get stuck & completely freeze TVheadend and w_scan, the microserver was still responding but just those apps hanged, requiring a reboot, I removed force_pid_filter_usage from my config and all is well again!
I'm not sure why it would make such a difference, but I thought I'd post anyway in case someone else thought that using force_pid_filter_usage would be a good idea
Also the latest drivers v120412 are very stable on my system (without the force_pid_filter_usage enabled obviously
), so kudos to whoever writes them!