Talk:DViCO FusionHDTV7 Dual Express: Difference between revisions
No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
Sometimes, not often, signal strength is 007d compare to fcd0 for ATI. However, 007d is the signal strength that the windows driver reports, but id decimal form of 125. This could simply be a scaling issue and multipling it by 256 may or may not help, but would bring the signal strength up to usable values since 125 to 127 offer perfect reception within windows. |
Sometimes, not often, signal strength is 007d compare to fcd0 for ATI. However, 007d is the signal strength that the windows driver reports, but id decimal form of 125. This could simply be a scaling issue and multipling it by 256 may or may not help, but would bring the signal strength up to usable values since 125 to 127 offer perfect reception within windows. |
||
<pre> |
|||
Further more something is trying to load mt352 |
Further more something is trying to load mt352 |
||
which results in: |
which results in: |
||
| Line 16: | Line 17: | ||
Also trying to load zl10353 resulting in: |
Also trying to load zl10353 resulting in: |
||
zl10353_read_register: readreg error (reg=127, ret==-6) |
zl10353_read_register: readreg error (reg=127, ret==-6) |
||
</pre> |
|||
Whoops!! |
Whoops!! The above is my fault I told "yast2 tv" that I had a DVB-T card instead of autodetecting the correct version of the card. I deleted the DVB-T card, and let linux auto-detect it. |
||
I deleted wrong enteries any above went away. |
|||
Using Kernel 2.6.28.1 the card pretty much works, but still get below sometimes. |
Using Kernel 2.6.28.1 the card pretty much works, but still get below sometimes. |
||
Xine will tune in and watch channels, and mythtv will detect channels. However, mythtv reports that it can't measure the S/N ratio error code 22. |
|||
<pre> |
|||
femon -a 0 |
femon -a 0 |
||
FE: Samsung S5H1411 QAM/8VSB Frontend (ATSC) |
FE: Samsung S5H1411 QAM/8VSB Frontend (ATSC) |
||
| Line 36: | Line 38: | ||
Problem retrieving frontend information: Invalid argument |
Problem retrieving frontend information: Invalid argument |
||
status S | signal 7fff | snr 0000 | ber 00000000 | unc 00000000 | |
status S | signal 7fff | snr 0000 | ber 00000000 | unc 00000000 | |
||
</pre> |
|||
:You should report this on the mailing list--[[User:CityK|CityK]] 02:49, 19 January 2009 (CET) |
:You should report this on the mailing list--[[User:CityK|CityK]] 02:49, 19 January 2009 (CET) |
||
Revision as of 15:21, 26 January 2009
--Cybernard 18:20, 29 December 2008 (CET) User cybernard reports: Using OpenSuSE 11.0 and 11.1 kernel 2.6.27.7-9 I placed the firmware in /lib/firmware, the same location as the ATI HDTV Wonder firmware. I tried to get thd HDTV over the air 8-VSB, I believe, but it doesn't tune. Signal strength is almost always 0 despite being hooked the same antenna as a ATI HDTV Wonder which works just fine. Mythtv see the card, but can't find any channels.
femon -a 0 reports only "S" under status and the ATI HDTV Wonder status says "SCVYL"
Sometimes, not often, signal strength is 007d compare to fcd0 for ATI. However, 007d is the signal strength that the windows driver reports, but id decimal form of 125. This could simply be a scaling issue and multipling it by 256 may or may not help, but would bring the signal strength up to usable values since 125 to 127 offer perfect reception within windows.
Further more something is trying to load mt352 which results in: mt352_read_register: readreg error (reg=127, ret==-6) Also trying to load zl10353 resulting in: zl10353_read_register: readreg error (reg=127, ret==-6)
Whoops!! The above is my fault I told "yast2 tv" that I had a DVB-T card instead of autodetecting the correct version of the card. I deleted the DVB-T card, and let linux auto-detect it.
Using Kernel 2.6.28.1 the card pretty much works, but still get below sometimes. Xine will tune in and watch channels, and mythtv will detect channels. However, mythtv reports that it can't measure the S/N ratio error code 22.
femon -a 0 FE: Samsung S5H1411 QAM/8VSB Frontend (ATSC) Problem retrieving frontend information: Invalid argument status S | signal 7fff | snr 0000 | ber 00000000 | unc 00000000 | Problem retrieving frontend information: Invalid argument status S | signal 7fff | snr 0000 | ber 00000000 | unc 00000000 | Problem retrieving frontend information: Invalid argument status S | signal 7fff | snr 0000 | ber 00000000 | unc 00000000 | Problem retrieving frontend information: Invalid argument status S | signal 7fff | snr 0000 | ber 00000000 | unc 00000000 | Problem retrieving frontend information: Invalid argument status S | signal 7fff | snr 0000 | ber 00000000 | unc 00000000 | Problem retrieving frontend information: Invalid argument status S | signal 7fff | snr 0000 | ber 00000000 | unc 00000000 |
- You should report this on the mailing list--CityK 02:49, 19 January 2009 (CET)
I did report it there also.