Re: Help with Sabrent TV-USBHD (Syntek Teledongle) on Ubuntu Karmic
On Fri, Nov 13, 2009 at 1:01 PM, Devin Heitmueller wrote: > On Fri, Nov 13, 2009 at 12:01 PM, James Klaas > wrote: >> I recently updated my play/work/fiddle with workstation and I wanted >> to see if my USB card still worked (OK, it never really worked). >> >> Previously, I was running Ubuntu 9.04 with a version retrieved from >> mercurial with the patch from >> http://linuxtv.org/hg/~mkrufky/teledongle/raw-rev/676e2f4475ed. It >> patched without error, compiled without error and installed against >> the stock kernel without error. When I loaded it, it complained about >> not being the right kind of firmware (which was noted in the >> discussion on the device) but otherwise it seemed to load fine >> (unfortunately, I don't seem to have a dmesg from that). When I tried >> using it to tune anything, it would tune a couple things, but put them >> on channels that were far different than the ones found by other dvb >> cards. It did however manage to pick up the SCTE-65 data using the >> scte65scan utility. >> >> Now that I've upgraded to 9.10, it no longer seems to find the tuner. >> I retrieved v4l-dvb via mercurial yesterday (12 Nov, 2009) applied the >> patch (which applied with a couple of offsets but no errors) and built >> the source. I had to disable the FireDTV driver, but other than that, >> it compiled with some warnings but no errors. It installed fine over >> the stock kernel. However, when I load it, I now get the following >> errors in dmesg: >> >> [ 93.770329] au0828 driver loaded >> [ 94.160154] au0828: i2c bus registered >> [ 94.201922] tveeprom 1-0050: Huh, no eeprom present (err=-5)? >> [ 94.204976] tuner 1-: chip found @ 0x0 (au0828) >> [ 94.271442] tuner-simple 1-: unable to probe Temic PAL (4002 >> FH5), proceeding anyway. >> [ 94.271452] tuner-simple 1-: creating new instance >> [ 94.271459] tuner-simple 1-: type set to 0 (Temic PAL (4002 FH5)) >> [ 94.313325] tuner-simple 1-: i2c i/o error: rc == -5 (should be 4) >> [ 94.340407] au8522 1-0047: creating new instance >> [ 94.383357] au8522_writereg: writereg error (reg == 0xa4, val == >> 0x0020, ret == -5) >> [ 94.424364] au8522_writereg: writereg error (reg == 0x106, val == >> 0x0001, ret == -5) >> [ 94.465503] au8522_writereg: writereg error (reg == 0x106, val == >> 0x0001, ret == -5) >> [ 94.501336] tda18271 1-0060: creating new instance >> [ 94.543412] au8522_writereg: writereg error (reg == 0x106, val == >> 0x0001, ret == -5) >> [ 94.666327] au8522_writereg: writereg error (reg == 0x106, val == >> 0x, ret == -5) >> [ 94.666339] tda18271_read_regs: [1-0060|M] ERROR: i2c_transfer returned: >> -5 >> [ 94.666347] Unknown device detected @ 1-0060, device not supported. >> [ 94.707712] au8522_writereg: writereg error (reg == 0x106, val == >> 0x0001, ret == -5) >> [ 94.789369] au8522_writereg: writereg error (reg == 0x106, val == >> 0x, ret == -5) >> [ 94.789376] tda18271_read_regs: [1-0060|M] ERROR: i2c_transfer returned: >> -5 >> [ 94.789381] Unknown device detected @ 1-0060, device not supported. >> [ 94.789387] tda18271_attach: [1-0060|M] error -22 on line 1272 >> [ 94.789393] tda18271 1-0060: destroying instance >> [ 94.853137] mt2131 I2C read failed >> [ 94.853350] DVB: registering new adapter (au0828) >> [ 94.853359] DVB: registering adapter 1 frontend 0 (Auvitek AU8522 >> QAM/8VSB Frontend)... >> [ 94.853943] Registered device AU0828 [Syntek Teledongle [EXPERIMENTAL]] >> >> Did something not patch correctly? The patch from mkrufky is now >> nearly a year old. I'd really like to contribute somehow, but I have >> no idea where I should start. >> >> Thank you for taking a look at this. > > I would start by reviewing the previous thread/discussion on this > particular topic with subject line: "au0828: experimental support for > Syntek Teledongle [05e1:0400]" > > http://linuxtv.org/pipermail/linux-dvb/2009-August/032306.html > > Devin > > -- > Devin J. Heitmueller - Kernel Labs > http://www.kernellabs.com > Ah, thanks. I somehow missed that thread. James -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Help with Sabrent TV-USBHD (Syntek Teledongle) on Ubuntu Karmic
On Fri, Nov 13, 2009 at 12:01 PM, James Klaas wrote: > I recently updated my play/work/fiddle with workstation and I wanted > to see if my USB card still worked (OK, it never really worked). > > Previously, I was running Ubuntu 9.04 with a version retrieved from > mercurial with the patch from > http://linuxtv.org/hg/~mkrufky/teledongle/raw-rev/676e2f4475ed. It > patched without error, compiled without error and installed against > the stock kernel without error. When I loaded it, it complained about > not being the right kind of firmware (which was noted in the > discussion on the device) but otherwise it seemed to load fine > (unfortunately, I don't seem to have a dmesg from that). When I tried > using it to tune anything, it would tune a couple things, but put them > on channels that were far different than the ones found by other dvb > cards. It did however manage to pick up the SCTE-65 data using the > scte65scan utility. > > Now that I've upgraded to 9.10, it no longer seems to find the tuner. > I retrieved v4l-dvb via mercurial yesterday (12 Nov, 2009) applied the > patch (which applied with a couple of offsets but no errors) and built > the source. I had to disable the FireDTV driver, but other than that, > it compiled with some warnings but no errors. It installed fine over > the stock kernel. However, when I load it, I now get the following > errors in dmesg: > > [ 93.770329] au0828 driver loaded > [ 94.160154] au0828: i2c bus registered > [ 94.201922] tveeprom 1-0050: Huh, no eeprom present (err=-5)? > [ 94.204976] tuner 1-: chip found @ 0x0 (au0828) > [ 94.271442] tuner-simple 1-: unable to probe Temic PAL (4002 > FH5), proceeding anyway. > [ 94.271452] tuner-simple 1-: creating new instance > [ 94.271459] tuner-simple 1-: type set to 0 (Temic PAL (4002 FH5)) > [ 94.313325] tuner-simple 1-: i2c i/o error: rc == -5 (should be 4) > [ 94.340407] au8522 1-0047: creating new instance > [ 94.383357] au8522_writereg: writereg error (reg == 0xa4, val == > 0x0020, ret == -5) > [ 94.424364] au8522_writereg: writereg error (reg == 0x106, val == > 0x0001, ret == -5) > [ 94.465503] au8522_writereg: writereg error (reg == 0x106, val == > 0x0001, ret == -5) > [ 94.501336] tda18271 1-0060: creating new instance > [ 94.543412] au8522_writereg: writereg error (reg == 0x106, val == > 0x0001, ret == -5) > [ 94.666327] au8522_writereg: writereg error (reg == 0x106, val == > 0x, ret == -5) > [ 94.666339] tda18271_read_regs: [1-0060|M] ERROR: i2c_transfer returned: -5 > [ 94.666347] Unknown device detected @ 1-0060, device not supported. > [ 94.707712] au8522_writereg: writereg error (reg == 0x106, val == > 0x0001, ret == -5) > [ 94.789369] au8522_writereg: writereg error (reg == 0x106, val == > 0x, ret == -5) > [ 94.789376] tda18271_read_regs: [1-0060|M] ERROR: i2c_transfer returned: -5 > [ 94.789381] Unknown device detected @ 1-0060, device not supported. > [ 94.789387] tda18271_attach: [1-0060|M] error -22 on line 1272 > [ 94.789393] tda18271 1-0060: destroying instance > [ 94.853137] mt2131 I2C read failed > [ 94.853350] DVB: registering new adapter (au0828) > [ 94.853359] DVB: registering adapter 1 frontend 0 (Auvitek AU8522 > QAM/8VSB Frontend)... > [ 94.853943] Registered device AU0828 [Syntek Teledongle [EXPERIMENTAL]] > > Did something not patch correctly? The patch from mkrufky is now > nearly a year old. I'd really like to contribute somehow, but I have > no idea where I should start. > > Thank you for taking a look at this. I would start by reviewing the previous thread/discussion on this particular topic with subject line: "au0828: experimental support for Syntek Teledongle [05e1:0400]" http://linuxtv.org/pipermail/linux-dvb/2009-August/032306.html Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Help with Sabrent TV-USBHD (Syntek Teledongle) on Ubuntu Karmic
I recently updated my play/work/fiddle with workstation and I wanted to see if my USB card still worked (OK, it never really worked). Previously, I was running Ubuntu 9.04 with a version retrieved from mercurial with the patch from http://linuxtv.org/hg/~mkrufky/teledongle/raw-rev/676e2f4475ed. It patched without error, compiled without error and installed against the stock kernel without error. When I loaded it, it complained about not being the right kind of firmware (which was noted in the discussion on the device) but otherwise it seemed to load fine (unfortunately, I don't seem to have a dmesg from that). When I tried using it to tune anything, it would tune a couple things, but put them on channels that were far different than the ones found by other dvb cards. It did however manage to pick up the SCTE-65 data using the scte65scan utility. Now that I've upgraded to 9.10, it no longer seems to find the tuner. I retrieved v4l-dvb via mercurial yesterday (12 Nov, 2009) applied the patch (which applied with a couple of offsets but no errors) and built the source. I had to disable the FireDTV driver, but other than that, it compiled with some warnings but no errors. It installed fine over the stock kernel. However, when I load it, I now get the following errors in dmesg: [ 93.770329] au0828 driver loaded [ 94.160154] au0828: i2c bus registered [ 94.201922] tveeprom 1-0050: Huh, no eeprom present (err=-5)? [ 94.204976] tuner 1-: chip found @ 0x0 (au0828) [ 94.271442] tuner-simple 1-: unable to probe Temic PAL (4002 FH5), proceeding anyway. [ 94.271452] tuner-simple 1-: creating new instance [ 94.271459] tuner-simple 1-: type set to 0 (Temic PAL (4002 FH5)) [ 94.313325] tuner-simple 1-: i2c i/o error: rc == -5 (should be 4) [ 94.340407] au8522 1-0047: creating new instance [ 94.383357] au8522_writereg: writereg error (reg == 0xa4, val == 0x0020, ret == -5) [ 94.424364] au8522_writereg: writereg error (reg == 0x106, val == 0x0001, ret == -5) [ 94.465503] au8522_writereg: writereg error (reg == 0x106, val == 0x0001, ret == -5) [ 94.501336] tda18271 1-0060: creating new instance [ 94.543412] au8522_writereg: writereg error (reg == 0x106, val == 0x0001, ret == -5) [ 94.666327] au8522_writereg: writereg error (reg == 0x106, val == 0x, ret == -5) [ 94.666339] tda18271_read_regs: [1-0060|M] ERROR: i2c_transfer returned: -5 [ 94.666347] Unknown device detected @ 1-0060, device not supported. [ 94.707712] au8522_writereg: writereg error (reg == 0x106, val == 0x0001, ret == -5) [ 94.789369] au8522_writereg: writereg error (reg == 0x106, val == 0x, ret == -5) [ 94.789376] tda18271_read_regs: [1-0060|M] ERROR: i2c_transfer returned: -5 [ 94.789381] Unknown device detected @ 1-0060, device not supported. [ 94.789387] tda18271_attach: [1-0060|M] error -22 on line 1272 [ 94.789393] tda18271 1-0060: destroying instance [ 94.853137] mt2131 I2C read failed [ 94.853350] DVB: registering new adapter (au0828) [ 94.853359] DVB: registering adapter 1 frontend 0 (Auvitek AU8522 QAM/8VSB Frontend)... [ 94.853943] Registered device AU0828 [Syntek Teledongle [EXPERIMENTAL]] Did something not patch correctly? The patch from mkrufky is now nearly a year old. I'd really like to contribute somehow, but I have no idea where I should start. Thank you for taking a look at this. James -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Sabrent TV-USBHD
I recently got one of these and I've been experimenting with it a little. I downloaded the mercurial tree from around June 5, 2009 and patched it using the patches here: http://linuxtv.org/hg/~mkrufky/teledongle/rev/676e2f4475ed I got it to compile fine and the drivers seem to load without complaint. I'm mostly interested in getting the QAM stuff to work. Here's partial output from w_scan - $ w_scan -a1 -A3 -t3 w_scan version 20081106 -_-_-_-_ Getting frontend capabilities-_-_-_-_ frontend Auvitek AU8522 QAM/8VSB Frontend supports FE_CAN_8VSB FE_CAN_QAM_64 FE_CAN_QAM_256 -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ 57000: ... 597000: 603000: 609000: signal ok (ch88 QAM) 615000: 621000: signal ok (ch90 QAM) 627000: 633000: signal ok (ch92 QAM) 639000: ... tune to: --no signal-- tune to: (no signal) --no signal-- ERROR: Sorry - i couldn't get any working frequency/transponder Nothing to scan!! dumping lists (0 services) Done. I'm curious to know why I get some "signal ok"s but when I tries to do a "tune to", nothing seems to be there? Also, this finds a much smaller list of signals than my other cards. I'm not sure where to poke around to try getting this better, but I'm happy to test out code anyone wants to throw my way. James -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
