Hi all, I've got a Hauppauge WinTV pci board that used to be working until kernel 3.1 was used; I tried 3.1.1, too, without luck. 3.0.7 is working, with the same config as the 3.1s regarding the media parts. I'm compiling my customized kernel from vanilla sources and a linux-vserver patch, and I also tested the 3.1.0-1-amd64 from debian stock with very result. On starting up Zapping, I got these messages: 'Unable to open /dev/video0.' 'The device cannot be attached to any controller.' Tvtime simply complained about 'No signal'. I couldn't find further messages or any errors in syslog nor in messages, so I'm feeling there might be a bug somewhere. The same modules are loaded into the kernel with 3.0.7 (working, with the same config as the 3.1s regarding the media parts), 3.1 and also 3.1.1: bttv btcx_risc rc_core tuner tuner_simple tuner_types videobuf_dma_sg videobuf_core tveeprom $lspci -vv … 05:00.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 02) Subsystem: Hauppauge computer works Inc. WinTV Series Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 64 (4000ns min, 10000ns max) Interrupt: pin A routed to IRQ 16 Region 0: Memory at d0001000 (32-bit, prefetchable) [size=4K] Kernel driver in use: bttv 05:00.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 02) Subsystem: Hauppauge computer works Inc. WinTV Series Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 64 (1000ns min, 63750ns max) Interrupt: pin A routed to IRQ 16 Region 0: Memory at d0000000 (32-bit, prefetchable) [size=4K] Kernel driver in use: Bt87x Thanks in advance. Best, Sebastian Steinhuber -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
