home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
HTPC Projects
Hardware
TV-Cards
TT S2-1600 on W10 - Problems on HD
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Joutungwu" data-source="post: 1192547" data-attributes="member: 147600"><p>Hi Bastian,</p><p>i had exactly the same issue with my Nova-S PCI and Windows 10 after installing both on newer hardware (system info: MediaPortal Guest PC (new)). I tried Kanotix 2013 (Linux live system) and was very surprised as i watched SD- and HDTV with Kaffeine without these errors. This showed me that there was neither a reception problem nor a hardware failure. I also thought about IRQ conflicts first, but the BIOS were set to share the IRQs and i saw the card sharing its IRQ with the same devices in Linux as well as in Windows 10. I was more surprised as i saw the card runnig well after Windows 10 reboot but that was not for a long time. After shutting the PC down and starting it after several hours, the picture errors returned more and more. I found out, that i could trigger this by resetting the PSU (PC shutdown > power cord unplugged > ON/OFF button pressed and held for at least 15 seconds). I found also that the PCI interfaces on the Asus P5K deluxe are controlled by the PCI express controller. I guess, this could be meant by "not natively supported anymore". These picture errors weren't limited to MediaPortal but also occured with other DVB software.</p><p></p><p>I tried a lot to get the Nova-S to work with Windows 10:</p><p>- Changing BIOS ACPI settings</p><p>- CMOS Resets</p><p>- PCI slot change</p><p>- BIOS reflashing and downgrades</p><p>- Changing <a href="https://msdn.microsoft.com/en-us/library/windows/hardware/ff542202(v=vs.85).aspx" target="_blank">boot entry options</a> belonging to PCI or PCIex</p><p>Nothing worked. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown :(" loading="lazy" data-shortname=":(" /></p><p></p><p>Recently i took a deeper look into the BIOS options. I found Advanced > JumperFree Configuration > Ai Ocerclock Tuner, which was set to [Auto] by default. When changing the Ai Overclock Tuner to [Manual], the option PCIE Frequency occurs, which is also set to [Auto] by default. Knowing that the PCI interfaces are controlled by the PCI Express controller, i changed the PCIE Frequency value to 125 at first (allowed input values: 100-150), but the system did not start (boot device not found). After reading a little bit about PCI overclocking, it seems that choosing such a high value was not a good idea at all. So please don't copy this! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite27" alt=":whistle:" title="Whistling :whistle:" loading="lazy" data-shortname=":whistle:" /> Then i changed it to 110 and to 105. The system was able to boot with both values, but it didn't effect anything about the errors. After that, i returned the PCIE Frequency and Ai Ocerclock Tuner back to [Auto] and rebooted. I was very surprised watching TV without the errors now. I did at least five PSU resets, but TV was still working. I have no explanation about this curiosity but after two days with shutdowns of several hours in between (similiar effect as PSU resets) it still works. Problem solved... <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite12" alt="o_O" title="Er... what? o_O" loading="lazy" data-shortname="o_O" /><img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite5" alt=":confused:" title="Confused :confused:" loading="lazy" data-shortname=":confused:" /><img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /><img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin :D" loading="lazy" data-shortname=":D" /></p><p></p><p>So, if you still have the TT-budget S2-1600, you may try the same as i did: Start the PC with <a href="https://kanotix.com/module-Downloads.html" target="_blank">Kanotix spitfire 2016</a>, which should have the driver of your card on board (Kernel 2.6.36 and above). Start Kaffeine, search for some free HD channels, put them to the channel list and check if the errors occur or not. If that works without errors, look into your BIOS/UEFI to set PCIE Frequency to other values than [Auto]. Try a low value between 100 and 105, save the settings and reboot Windows 10. Then go to BIOS again and set PCIE Frequency back to [AUTO]. Save settings and check if this works for your PCI DVB card as well.</p><p></p><p>Good luck!</p><p></p><p>Joutungwu</p></blockquote><p></p>
[QUOTE="Joutungwu, post: 1192547, member: 147600"] Hi Bastian, i had exactly the same issue with my Nova-S PCI and Windows 10 after installing both on newer hardware (system info: MediaPortal Guest PC (new)). I tried Kanotix 2013 (Linux live system) and was very surprised as i watched SD- and HDTV with Kaffeine without these errors. This showed me that there was neither a reception problem nor a hardware failure. I also thought about IRQ conflicts first, but the BIOS were set to share the IRQs and i saw the card sharing its IRQ with the same devices in Linux as well as in Windows 10. I was more surprised as i saw the card runnig well after Windows 10 reboot but that was not for a long time. After shutting the PC down and starting it after several hours, the picture errors returned more and more. I found out, that i could trigger this by resetting the PSU (PC shutdown > power cord unplugged > ON/OFF button pressed and held for at least 15 seconds). I found also that the PCI interfaces on the Asus P5K deluxe are controlled by the PCI express controller. I guess, this could be meant by "not natively supported anymore". These picture errors weren't limited to MediaPortal but also occured with other DVB software. I tried a lot to get the Nova-S to work with Windows 10: - Changing BIOS ACPI settings - CMOS Resets - PCI slot change - BIOS reflashing and downgrades - Changing [URL='https://msdn.microsoft.com/en-us/library/windows/hardware/ff542202(v=vs.85).aspx']boot entry options[/URL] belonging to PCI or PCIex Nothing worked. :( Recently i took a deeper look into the BIOS options. I found Advanced > JumperFree Configuration > Ai Ocerclock Tuner, which was set to [Auto] by default. When changing the Ai Overclock Tuner to [Manual], the option PCIE Frequency occurs, which is also set to [Auto] by default. Knowing that the PCI interfaces are controlled by the PCI Express controller, i changed the PCIE Frequency value to 125 at first (allowed input values: 100-150), but the system did not start (boot device not found). After reading a little bit about PCI overclocking, it seems that choosing such a high value was not a good idea at all. So please don't copy this! :whistle: Then i changed it to 110 and to 105. The system was able to boot with both values, but it didn't effect anything about the errors. After that, i returned the PCIE Frequency and Ai Ocerclock Tuner back to [Auto] and rebooted. I was very surprised watching TV without the errors now. I did at least five PSU resets, but TV was still working. I have no explanation about this curiosity but after two days with shutdowns of several hours in between (similiar effect as PSU resets) it still works. Problem solved... o_O:confused::):D So, if you still have the TT-budget S2-1600, you may try the same as i did: Start the PC with [URL='https://kanotix.com/module-Downloads.html']Kanotix spitfire 2016[/URL], which should have the driver of your card on board (Kernel 2.6.36 and above). Start Kaffeine, search for some free HD channels, put them to the channel list and check if the errors occur or not. If that works without errors, look into your BIOS/UEFI to set PCIE Frequency to other values than [Auto]. Try a low value between 100 and 105, save the settings and reboot Windows 10. Then go to BIOS again and set PCIE Frequency back to [AUTO]. Save settings and check if this works for your PCI DVB card as well. Good luck! Joutungwu [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
HTPC Projects
Hardware
TV-Cards
TT S2-1600 on W10 - Problems on HD
Contact us
RSS
Top
Bottom
