Re: DM1105: could not attach frontend 195d:1105
Igor wrote:
> Oh, that is wrong. It is registers addresses, Never touch this.
>
> Let's look on that part of code:
>
> /* GPIO's for LNB power control */
> #define DM1105_LNB_MASK 0x // later in
code write it to
> DM1105_GPIOCTR, all GPIO's as OUT
> #define DM1105_LNB_OFF 0x0002 // later in
code write it to
> DM1105_GPIOVAL, set GPIO17 to HIGH
> But you have not to change this.
> Right way is to write another entry in cards structure and so on.
> Better leave it to me.
> Regards
> Igor
Thanks for all your help, I understand better now. I have moved to code
like that at the bottom. It still doesn't work, but feels a lot closer.
Before I keep playing with values, I want to check I'm on the right track.
Does it look right? Specific questions:
1. I see there is a hw_init function. Should I be using that? I put the
logic into fe_attach because there was already card-specific logic in
there. But this feels like hw initialisation.
2. Should I set the control to input or output? I'm assuming input = 1.
3. Would pin 15 be numbered from the left or right - is it 0x4, or 0x2000?
Thanks,
Paul
*** dm1105.c.old2010-01-13 16:15:00.0 +1100
--- dm1105.c2010-01-21 08:13:14.0 +1100
***
*** 51,56
--- 51,57
#define DM1105_BOARD_DVBWORLD_20021
#define DM1105_BOARD_DVBWORLD_20042
#define DM1105_BOARD_AXESS_DM05 3
+ #define DM1105_BOARD_UNBRANDED4
/* --- */
/*
***
*** 171,176
--- 172,181
#define DM05_LNB_13V 0x0002
#define DM05_LNB_18V 0x0003
+ /* GPIO's for demod reset for unbranded 195d:1105 */
+ #define UNBRANDED_DEMOD_MASK 0x8000
+ #define UNBRANDED_DEMOD_RESET 0x8000
+
static unsigned int card[] = {[0 ... 3] = UNSET };
module_param_array(card, int, NULL, 0444);
MODULE_PARM_DESC(card, "card type");
***
*** 206,211
--- 211,219
[DM1105_BOARD_AXESS_DM05] = {
.name = "Axess/EasyTv DM05",
},
+ [DM1105_BOARD_UNBRANDED] = {
+ .name = "Unbranded 195d:1105",
+ },
};
static const struct dm1105_subid dm1105_subids[] = {
***
*** 229,234
--- 237,246
.subvendor = 0x195d,
.subdevice = 0x1105,
.card = DM1105_BOARD_AXESS_DM05,
+ }, {
+ .subvendor = 0x195d,
+ .subdevice = 0x1105,
+ .card = DM1105_BOARD_UNBRANDED,
},
};
***
*** 698,703
--- 710,727
dm1105dvb->fe->ops.set_voltage =
dm1105dvb_set_voltage;
break;
+ case DM1105_BOARD_UNBRANDED:
+ printk(KERN_ERR "Attaching as board_unbranded\n");
+ outl(UNBRANDED_DEMOD_MASK, dm_io_mem(DM1105_GPIOCTR));
+ outl(UNBRANDED_DEMOD_RESET , dm_io_mem(DM1105_GPIOVAL));
+ dm1105dvb->fe = dvb_attach(
+ si21xx_attach, &serit_config,
+ &dm1105dvb->i2c_adap);
+ if (dm1105dvb->fe)
+ dm1105dvb->fe->ops.set_voltage =
+ dm1105dvb_set_voltage;
+
+ break;
case DM1105_BOARD_DVBWORLD_2002:
case DM1105_BOARD_AXESS_DM05:
default:
--
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: DM1105: could not attach frontend 195d:1105
> Well, as I understood, GPIO15 drives reset for demod. > dm1105 driver needs little patching. > > Igor, Not to hassle you, I'm sure you're very busy. Is this something I could undertake myself? If so, which driver would you recommend I copy from - I saw on the list that some drivers do their own GPIO management, and others use a generic GPIO layer. I presume we'd need to use the generic layer? Also, from your explanation it sounds like we need to set GPIO 15 to true before we attempt to attach. Is that correct? From my reading there are two GPIO registers (8 bits each), so we'd be bit masking bit 7 in the second GPIO register to 1, then sending that GPIO to the card? Thanks for any tips, Paul -- 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: DM1105: could not attach frontend 195d:1105
Igor wrote: > Accordingly datasheet possible demod addresses are 0x68, 0x69, 0x6a, 0x6b only. > Possibly there is some DM1105 GPIO drives reset for demod. > I assume it is last (26, top right if you look from card elements side) pin on tuner. > You can visually trace way from can tuner. Or use multimeter. Sorry, that is a bit beyond me. If I understand correctly, I'm looking for the top right pin from the tuner when I'm looking at the side of the card that has all the chips on it. I can see that, and there are a number of traces that run from there to the DM1105, and also a few that run to other components on the card. I'm assuming I need to follow the topmost of the traces that go to the DM1105, and see which pin on the DM1105 it goes to. My eyesight isn't that good...but I have a magnifying glass. If I follow the topmost of the traces it looks to run to the rightmost pin on the top row of pins on the DM1105, when the writing on the DM1105 is the right way up. I didn't find a data sheet for the DM1105, so I can't tell if that is a GPIO pin or not. The next trace down from the top right on the tuner appears to end without connecting. It ends in a small brass circle, and doesn't appear to go through to the back of the board and connect anywhere. The next one below that goes to the fifth pin in from the right hand end of the top row on the DM1105. Am I doing the right thing here - does this make sense? I've drawn on the photo so you can see what I'm doing. Refer: http://planar.id.au/Photos/img_1964%20%28copy%29.jpg. The far right blue line comes from the top most right hand pin on the tuner, runs under the board at the brass circle, and comes out again to join on to the rightmost pin. The next blue line in is the one going to the fifth pin, it is the third track down coming from the tuner. In between the two is a track that appears to go nowhere. I've marked in white roughly where they are coming out of the tuner. Thanks again for all your help, Paul -- 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: DM1105: could not attach frontend 195d:1105
On Sat, 16 Jan 2010 02:49:52 +, wrote: > Ah, I see. The whole thing is a tuner, and the label that I thought said > "ERIT" actually says "SERIT". Yes, it does have a label on it, I should > have given you that up front. I had searched for it on the internet and > decided that it didn't mean anything. Thanks so much for your help. > > The label reads SP1514LHb D0943B > > If I follow your decipher instructions that means: > > 1: DVB-S > 5: 16cc > 1: Unsure, but it has an LNB in and an LNB out, so I guess it does have > loop through? > 4: Si2109 > L: Si labs > H: Horizontal > b: Lead free > > So I'm looking for some code to enable an Si2109 tuner? > > Thanks again, > > Paul I'm looking through the dm1105 code that I have in 2.6.33-rc4. I have a block that reads: dm1105dvb->fe = dvb_attach( si21xx_attach, &serit_config, &dm1105dvb->i2c_adap); if (dm1105dvb->fe) dm1105dvb->fe->ops.set_voltage = dm1105dvb_set_voltage; I have looked through the code for si21xx.c, and I see that you wrote that as well. You have been very busy!! I did rmmod si21xx, then insmod si21xx debug=1. I then rmmod dm1105, insmod dm1105. dmesg reports: [191712.426735] dm1105 :06:00.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20 [191712.426898] DVB: registering new adapter (dm1105) [191712.674945] dm1105 :06:00.0: MAC 00:00:00:00:00:00 [191714.072172] si21xx: si21xx_attach [191714.320219] si21xx: si21_readreg: readreg error (reg == 0x01, ret == -1) [191714.568266] si21xx: si21_writereg: writereg error (reg == 0x01, data == 0x40, ret == -1) [191715.020067] si21xx: si21_readreg: readreg error (reg == 0x00, ret == -1) [191715.020125] dm1105 :06:00.0: could not attach frontend [191715.020297] dm1105 :06:00.0: PCI INT A disabled Does this shed any light on the matter for you? Thanks, Paul -- 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: DM1105: could not attach frontend 195d:1105
Paul wrote: > Is it likely that there is a tuner under the card labelled "ERIT"? To > take it off I have to unsolder some stuff - I can do that, but I reckon > it's only 50% chance the card will work again when I put it back together - > my soldering isn't so good. Igor wrote: > No need to unsolder. I see a Serit can tuner. There is a sticked paper with a label on right side > of the tuner. It must contain something like "sp2636lhb" or "sp2633chb". Please provide me text of > label. Ah, I see. The whole thing is a tuner, and the label that I thought said "ERIT" actually says "SERIT". Yes, it does have a label on it, I should have given you that up front. I had searched for it on the internet and decided that it didn't mean anything. Thanks so much for your help. The label reads SP1514LHb D0943B If I follow your decipher instructions that means: 1: DVB-S 5: 16cc 1: Unsure, but it has an LNB in and an LNB out, so I guess it does have loop through? 4: Si2109 L: Si labs H: Horizontal b: Lead free So I'm looking for some code to enable an Si2109 tuner? Thanks again, Paul -- 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: DM1105: could not attach frontend 195d:1105
On 15 января 2010 11:15:26 pau...@planar.id.au wrote: > I bought a DVB-S card to attach to my mythtv setup. I knew it was perhaps > not going to work, and I only spent $15 on it. However, based on the info > the guy on eBay provided, it had a pci address of 195d:1105, which I could > see some people had cards that were working. > The card itself is a no-name jobby. I can see the DM1105 chip on it, I > can't see any other chips with any significant pin count (lots with 3 - 8 > pins, but nothing with enough to be important). There is a metal case > around the connectors that might be hiding a frontend chip of some sort, > but it doesn't seem to have enough connectors in and out to be doing much > that is important beyond just providing connectivity to the LNB. > Igor wrote: > Hi Paul, > Frontend/tuner must lay under cover. > Subsystem: Device 195d:1105 indicates that there is no EEPROM in card. > If you send some links/pictures/photos then it would helped a lot. > Is there a disk with drivers for Windows? > Also I know about dm1105 based cards with tda10086 demod, those are not supported in the driver yet. > BR > Igor Igor, Photos: 1. Front of card. You can see the DM1105 in the foreground. There are no other significant looking chips on the card. http://planar.id.au/Photos/img_1964.jpg 2. Back of card - as you can see, there aren't a lot of places where a lot of pins are connecting - mainly the DM1105 itself http://planar.id.au/Photos/img_1965.jpg 3. With the top metal plate removed, and with the other end of the card in better focus. http://planar.id.au/Photos/img_1966.jpg Is it likely that there is a tuner under the card labelled "ERIT"? To take it off I have to unsolder some stuff - I can do that, but I reckon it's only 50% chance the card will work again when I put it back together - my soldering isn't so good. Thanks heaps for the assistance. Paul -- 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
DM1105: could not attach frontend 195d:1105
I bought a DVB-S card to attach to my mythtv setup. I knew it was perhaps not going to work, and I only spent $15 on it. However, based on the info the guy on eBay provided, it had a pci address of 195d:1105, which I could see some people had cards that were working. The card itself is a no-name jobby. I can see the DM1105 chip on it, I can't see any other chips with any significant pin count (lots with 3 - 8 pins, but nothing with enough to be important). There is a metal case around the connectors that might be hiding a frontend chip of some sort, but it doesn't seem to have enough connectors in and out to be doing much that is important beyond just providing connectivity to the LNB. I've got the latest kernel (2.6.33-rc4) and I've checked the code and it looks like the latest DM1105 code. When booting I get: [9.766188] dm1105 :06:00.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20 [ 10.047331] dm1105 :06:00.0: MAC 00:00:00:00:00:00 [ 12.464628] dm1105 :06:00.0: could not attach frontend [ 12.479830] dm1105 :06:00.0: PCI INT A disabled With lspci -vv I get: 06:00.0 Ethernet controller: Device 195d:1105 (rev 10) Subsystem: Device 195d:1105 Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- http://vger.kernel.org/majordomo-info.html
RE: Leadtek Winfast DTV-1000S
That is fantastic news. Not only will it be coming soon, but I don't have to do it myself!! How will we know when the test repository is created - will it be announced on this list? Thanks, Paul > Henry Wu did send modified saa7134 files with support for this card on > Tuesday off list. > Mike replied, that he will set up a test repository as soon he gets some > time for doing so. -- 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: Leadtek Winfast DTV-1000S
OK, I've pulled the card and taken a photo, and then removed the other cards in my box so as to see the messages for this card only. It looks to me like it doesn't like the tuner, perhaps because the eeprom information isn't as expected. Further, I probably don't have the right firmware, as I copied the firmware from the Hauppage driver. Information attached here is: 1. Links to everything I've found on the web that is relevant 2. Link to the photo of the card. The chips aren't particularly readable 3. List of every number I can read on the various chips (at least the larger ones) 4. Kernel logs from my boot I'm hoping Mike or someone else can help me with where to go next. I reckon a good start is to get the firmware - I have the windows drivers but no idea how to get firmware out of them. I also reckon I need the eeprom info, but also no idea how I go about setting that up either. Thanks for any advice anyone can give on how to progress from here. I see somewhere I can specify a tuner for the card, but I actually can't work out what tuner this card has - the TDA10048 doesn't seem to be a tuner, and I can't see any other chips that are tuners. Paul 1. Links: Some other guy trying to get this working - prior to TDA10048 support being included http://www.linuxtv.org/pipermail/linux-dvb/2008-April/025586.html The driver version I pulled and used from Mike Krufky http://kernellabs.com/hg/~mk/hvr1110 A thread from a local forum in which I discussed this, may be useful http://forums.whirlpool.net.au/forum-replies-archive.cfm/1212297.html Windows drivers http://drivers.softpedia.com/get/TV-Tuner-Co/LEADTEK/Leadtek-WinFast-DTV1000S-XP-Driver-20070907-WHQL.shtml Instructions for getting firmware for an hvr1200 steventoth.net/linux/hvr1200 2. Link to photo of the card planar.id.au/img_0050.jpg 3. All the numbers from the various chips. Where there are a few spaces between numbers for a given chip, that generally means it runs over multiple lines on the chip itself. I've searched on the web to see what each of them are, and put that info in where I could find it (after the :). Top left (small black) - TDA 10048HN Q617YFD 07 2PGD7062 :Channel receiver Top mid-right (mid black) - AT8PS56SHKECSG752 :Microcontroller Top mid (small black) - HT24LC02 :Memory device Bottom mid (large black) NXP SAA7130HL VL3669.1 17 kS607491 :Video broadcast decoder mid-right (silver oval) - 32.1F7M Far right (small black) - MT11173.30719A :Linear voltage / regulator Bottom mid-left (small black) - MT11173.3.0719A 4. Kernel logs of the boot planar.id.au/dmesg.log Interesting bits from that log copied in here: [ 10.515224] Linux video capture interface: v2.00 [ 10.607398] saa7130/34: v4l2 driver version 0.2.15 loaded [ 10.615508] saa7134 :05:00.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20 [ 10.623719] saa7130[0]: found at :05:00.0, rev: 1, irq: 20, latency: 32, mmio: 0xf910 [ 10.632179] saa7130[0]: subsystem: 107d:6655, board: Hauppauge WinTV-HVR1110r3 DVB-T/Hybrid [card=156,insmod option] [ 10.640920] saa7130[0]: board init: gpio is 22000 [ 10.672049] IRQ 20/saa7130[0]: IRQF_DISABLED is not guaranteed on shared IRQs [ 10.718381] HDA Intel :00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22 [ 10.727458] HDA Intel :00:1b.0: setting latency timer to 64 [ 10.832019] saa7130[0]: i2c eeprom 00: 7d 10 55 66 54 20 1c 00 43 43 a9 1c 55 d2 b2 92 [ 10.832026] saa7130[0]: i2c eeprom 10: 00 ff 82 0e ff 20 ff ff ff ff ff ff ff ff ff ff [ 10.832031] saa7130[0]: i2c eeprom 20: 01 40 01 01 01 ff 01 03 08 ff 00 8a ff ff ff ff [ 10.832037] saa7130[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.832042] saa7130[0]: i2c eeprom 40: ff 35 00 c0 00 10 03 02 ff 04 ff ff ff ff ff ff [ 10.832048] saa7130[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.832053] saa7130[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.832059] saa7130[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.832064] saa7130[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.832070] saa7130[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.832075] saa7130[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.832081] saa7130[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.832087] saa7130[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.832092] saa7130[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.832098] saa7130[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.832103] saa7130[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.832110] tveeprom 1-0050: Encountered bad packet header [ff]. Corrupt or not a Hauppauge eeprom. [ 10.832112] saa7130[0]: warning: unknow
RE: Leadtek Winfast DTV-1000S
OK, I've also tried the firmware from the instructions at steventoth.net/linux/hvr1200, giving me a dvb-fe-tda10048-1.0.fw file. I still cannot tune, it isn't clear to me whether the firmware is the issue, or whether one of the other errors is the problem. Or both I still have the other two cards in the machine, so the dmesg listing isn't clean. I'm extracting what looks relevant. I can post the whole log if something looks to be missing, or if really necessary I can remove the other two cards. That will take me a little longer and it is my production box, so I'd rather not unless there is some doubt about what is going on. The relevant messages in the log look to be: [ 10.232789] saa7130/34: v4l2 driver version 0.2.15 loaded [ 10.241194] saa7134 :05:00.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20 [ 10.249731] saa7130[0]: found at :05:00.0, rev: 1, irq: 20, latency: 32, mmio: 0xfc001000 [ 10.258483] saa7130[0]: subsystem: 107d:6655, board: Hauppauge WinTV-HVR1110r3 DVB-T/Hybrid [card=156,insmod option] [ 10.267477] saa7130[0]: board init: gpio is 122009 [ 10.293131] cx88/0: cx2388x v4l2 driver version 0.0.7 loaded [ 10.302052] IRQ 20/saa7130[0]: IRQF_DISABLED is not guaranteed on shared IRQs [ 10.312626] cx88/2: cx2388x MPEG-TS Driver Manager version 0.0.7 loaded [ 10.353716] cx2388x alsa driver version 0.0.7 loaded [ 10.400854] HDA Intel :00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22 [ 10.410254] HDA Intel :00:1b.0: setting latency timer to 64 [ 10.464031] saa7130[0]: i2c eeprom 00: 7d 10 55 66 54 20 1c 00 43 43 a9 1c 55 d2 b2 92 [ 10.473672] saa7130[0]: i2c eeprom 10: 00 ff 82 0e ff 20 ff ff ff ff ff ff ff ff ff ff [ 10.483379] saa7130[0]: i2c eeprom 20: 01 40 01 01 01 ff 01 03 08 ff 00 8a ff ff ff ff [ 10.492999] saa7130[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.502537] saa7130[0]: i2c eeprom 40: ff 35 00 c0 00 10 03 02 ff 04 ff ff ff ff ff ff [ 10.512026] saa7130[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.521514] saa7130[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.530935] saa7130[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.540418] saa7130[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.549677] saa7130[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.558693] saa7130[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.567617] saa7130[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.567739] saa7130[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.567746] saa7130[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.567753] saa7130[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.567758] saa7130[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.567765] tveeprom 1-0050: Encountered bad packet header [ff]. Corrupt or not a Hauppauge eeprom. [ 10.567767] saa7130[0]: warning: unknown hauppauge model #0 [ 10.567768] saa7130[0]: hauppauge eeprom: model=0 [ 10.712041] Chip ID is not zero. It is not a TEA5767 [ 10.720138] tuner 1-0060: chip found @ 0xc0 (saa7130[0]) [ 10.768020] tda8290: no gate control were provided! [ 10.775900] tuner 1-0060: Tuner has no way to set tv freq [ 10.783718] tuner 1-0060: Tuner has no way to set tv freq [ 10.791567] saa7130[0]: registered device video0 [v4l2] [ 10.799359] saa7130[0]: registered device vbi0 [ 10.807034] saa7130[0]: registered device radio0 [ 12.273033] DVB: registering new adapter (saa7130[0]) [ 12.281372] DVB: registering adapter 1 frontend 0 (NXP TDA10048HN DVB-T)... [ 12.617026] tda10048_firmware_upload: waiting for firmware upload (dvb-fe-tda10048-1.0.fw)... [ 12.617029] saa7134 :05:00.0: firmware: requesting dvb-fe-tda10048-1.0.fw [ 12.694154] EXT3 FS on md21, internal journal [ 12.709531] tda10048_firmware_upload: firmware read 24878 bytes. [ 12.718281] tda10048_firmware_upload: firmware uploading [ 16.820022] tda10048_firmware_upload: firmware uploaded [ 16.944017] dvb_init() allocating 1 frontend [ 17.005238] tuner-simple 3-0061: unable to probe Philips TD1316 Hybrid Tuner, proceeding anyway.<6>tuner-simple 3-0061: creating new instance [ 17.013309] tuner-simple 3-0061: type set to 67 (Philips TD1316 Hybrid Tuner) [ 17.021250] DVB: registering new adapter (saa7134[1]) [ 17.029133] DVB: registering adapter 2 frontend 0 (Zarlink MT352 DVB-T)... [ 17.162115] saa7134 ALSA driver for DMA sound loaded [ 17.170016] saa7130[0]/alsa: Hauppauge WinTV-HVR1110r3 DVB-T/Hybrid doesn't support digital audio [ 17.178093] IRQ 19/saa7134[1]: IRQF_DISABLED is not guaranteed on shared IRQs [ 17.186235] saa7134[1]/alsa: saa7134[1] at 0xfc00 irq 19 registered as card -1 I suspect that the key bit is where it loads the firmware, but is th
RE: Leadtek Winfast DTV-1000S
OK, I've gone the next step and downloaded the hvr1200 firmware for the using this link: steventoth.net/linux/hvr1200 I'm still not getting tuning, it isn't clear whether this is due to the firmware or the other errors in the log. Again, my logs have messages from all three cards, including the 7134-based Avermedia. I'm extracting the messages that look like they relate to the DTV1000S, I'm happy to post either the full log or to unplug the other two cards. If I need to do the latter, that means I need to wait for a time where the box isn't supposed to be recording something - as it is also my production box, and WAF is currently quite high :-) The dmesg logs are: [ 10.232789] saa7130/34: v4l2 driver version 0.2.15 loaded [ 10.241194] saa7134 :05:00.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20 [ 10.249731] saa7130[0]: found at :05:00.0, rev: 1, irq: 20, latency: 32, mmio: 0xfc001000 [ 10.258483] saa7130[0]: subsystem: 107d:6655, board: Hauppauge WinTV-HVR1110r3 DVB-T/Hybrid [card=156,insmod option] [ 10.267477] saa7130[0]: board init: gpio is 122009 [ 10.293131] cx88/0: cx2388x v4l2 driver version 0.0.7 loaded [ 10.302052] IRQ 20/saa7130[0]: IRQF_DISABLED is not guaranteed on shared IRQs [ 10.312626] cx88/2: cx2388x MPEG-TS Driver Manager version 0.0.7 loaded [ 10.353716] cx2388x alsa driver version 0.0.7 loaded [ 10.400854] HDA Intel :00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22 [ 10.410254] HDA Intel :00:1b.0: setting latency timer to 64 [ 10.464031] saa7130[0]: i2c eeprom 00: 7d 10 55 66 54 20 1c 00 43 43 a9 1c 55 d2 b2 92 [ 10.473672] saa7130[0]: i2c eeprom 10: 00 ff 82 0e ff 20 ff ff ff ff ff ff ff ff ff ff [ 10.483379] saa7130[0]: i2c eeprom 20: 01 40 01 01 01 ff 01 03 08 ff 00 8a ff ff ff ff [ 10.492999] saa7130[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.502537] saa7130[0]: i2c eeprom 40: ff 35 00 c0 00 10 03 02 ff 04 ff ff ff ff ff ff [ 10.512026] saa7130[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.521514] saa7130[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.530935] saa7130[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.540418] saa7130[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.549677] saa7130[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.558693] saa7130[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.567617] saa7130[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.567739] saa7130[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.567746] saa7130[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.567753] saa7130[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.567758] saa7130[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.567765] tveeprom 1-0050: Encountered bad packet header [ff]. Corrupt or not a Hauppauge eeprom. [ 10.567767] saa7130[0]: warning: unknown hauppauge model #0 [ 10.567768] saa7130[0]: hauppauge eeprom: model=0 [ 10.712041] Chip ID is not zero. It is not a TEA5767 [ 10.720138] tuner 1-0060: chip found @ 0xc0 (saa7130[0]) [ 10.768020] tda8290: no gate control were provided! [ 10.775900] tuner 1-0060: Tuner has no way to set tv freq [ 10.783718] tuner 1-0060: Tuner has no way to set tv freq [ 10.791567] saa7130[0]: registered device video0 [v4l2] [ 10.799359] saa7130[0]: registered device vbi0 [ 10.807034] saa7130[0]: registered device radio0 [ 12.273033] DVB: registering new adapter (saa7130[0]) [ 12.281372] DVB: registering adapter 1 frontend 0 (NXP TDA10048HN DVB-T)... [ 12.617026] tda10048_firmware_upload: waiting for firmware upload (dvb-fe-tda10048-1.0.fw)... [ 12.617029] saa7134 :05:00.0: firmware: requesting dvb-fe-tda10048-1.0.fw [ 12.694154] EXT3 FS on md21, internal journal [ 12.709531] tda10048_firmware_upload: firmware read 24878 bytes. [ 12.718281] tda10048_firmware_upload: firmware uploading [ 16.820022] tda10048_firmware_upload: firmware uploaded [ 16.944017] dvb_init() allocating 1 frontend [ 17.005238] tuner-simple 3-0061: unable to probe Philips TD1316 Hybrid Tuner, proceeding anyway.<6>tuner-simple 3-0061: creating new instance [ 17.013309] tuner-simple 3-0061: type set to 67 (Philips TD1316 Hybrid Tuner) [ 17.021250] DVB: registering new adapter (saa7134[1]) [ 17.029133] DVB: registering adapter 2 frontend 0 (Zarlink MT352 DVB-T)... http://drivers.softpedia.com/get/TV-Tuner-Co/LEADTEK/Leadtek-WinFast-DTV1000S-XP-Driver-20070907-WHQL.shtml -- 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: Leadtek Winfast DTV-1000S
I've been working through this thread. I am running 2.6.30-rc6. I've checked out the patch from ttp://kernellabs.com/hg/~mk/hvr1110, and installed it. I modified one file - cx88-cards.c, which doesn't seem to work with my DTV2000H, but otherwise just using the code per the patch. I've added "options saa7134 card=156" into a file in /etc/modprobe.d/ So far, so good. I have made more progress than Brad appears to have, it is recognising the card, but appears to not be tuning it. I suspect the problem is the lack of firmware: dvb-fe-tda10048-1.0.fw I have three tuner cards in my machine - a DTV2000H and an Avermedia 777, so my full dmesg log is a bit untidy. This is exacerbated by the fact that the Avermedia also uses the saa7134 chipset. I believe the lines that relate to the DTV1000S, and that are relevant are these: saa7130[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff tveeprom 2-0050: Encountered bad packet header [ff]. Corrupt or not a Hauppauge eeprom. saa7130[0]: warning: unknown hauppauge model #0 saa7130[0]: hauppauge eeprom: model=0 Chip ID is not zero. It is not a TEA5767 tuner 2-0060: chip found @ 0xc0 (saa7130[0] tda8290: no gate control were provided! tuner 2-0060: Tuner has no way to set tv freq tuner 2-0060: Tuner has no way to set tv freq tda10048_firmware_upload: waiting for firmware upload (dvb-fe-tda10048-1.0.fw)... saa7134 :05:00.0: firmware: requesting dvb-fe-tda10048-1.0.fw tda10048_firmware_upload: Upload failed. (file not found?) tuner-simple 3-0061: unable to probe Philips TD1316 Hybrid Tuner, proceeding anyway.<6>tuner-simple 3-0061: creating new instance tuner-simple 3-0061: type set to 67 (Philips TD1316 Hybrid Tuner) I can see the appropriate firmware for the Hauppage, but I'm guessing that I need special firmware for the WinFast implementation. So I think I need to do something to get the right firmware. Is it a reasonable presumption that the firmware is the problem here - or is it actually the earlier messages that are the underlying problem? Or perhaps both? I have /dev/adapter1/ created, but it won't tune. When trying to tune, dmesg is getting errors along the lines of missing firmware, then seg fault. That was leading me to think that firmware is the issue. Is it useful to try the hauppage firmware, or is that unlikely to work? Thanks, Paul -- 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
