-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WinTV-quadHD mpeg risc op code error / dvb-t2 scan not working #69
Comments
|
Did you try setting the kernel parameter to force the amd fix? |
|
Forcing the AMD fix seems to fix the issue. Recorded some stuff via timers and I didnt see any of these strange log messages during the 2 weeks it was running. regarding those - Is this because I am using as Kernel parameter aka IOMMU/Virtualization VT-D with device passthrough / PCI or PCIe - passthrough ? PS: my use case I sometimes spin up a Windows 7/8 VM with DVB Viewer (with another DVB device) - now splitting 4 Tuners the of winTV QuadHD between Windows VM and Linux Host OS seems to work now too. So this "bug" is either IOMMU - iirc that was mentioned on the linux-media mailing list or an issue with Mainboard/Chipset/IOMMU environment (Intel Z77: DZ77RE-75K) |
|
Glad that option fixed you up. If the root cause is indeed the IOMMU like is suspected, then unfortunately it's outside of my realm of expertise. I'm going to close this issue for now. |
Reading #17 and #51 suggest that non-AMD platforms and mainline kernel should not exhibit "mpeg risc op code error" anymore
dvbv5-scan -C de simple.confwith content
fails.
The error goes away with
options cx23885 debug=7in /etc/modprobe.d/cx23885.conf - as is suggested in the other issue and the scan is successful.
VLC works without any error in syslog via cmdline / tuning seems fine
vlc dvb-t2://frequency=506000000:bandwidth=8A short test with tvheadend shows similar errors but recording seems to work.
System:
Intel i7-3770, Intel Z77 Mainboard
OS: Archlinux 5.0.4-arch1-1-ARCH
Location: Berlin, Germany DVB-T2
error:
The text was updated successfully, but these errors were encountered: