Skip to contentSkip to conversation

Lifeview hybrid saa7134 driver not working anymore

linux-dvb [email protected] 2 participants 4 messages Aug 23, 2009 – Aug 24, 2009 Media (V4L/DVB)

lore
Share & tools
lore
#0 lore raw

Hi, for a couple of days now, my lifeview PCI hybrid card that worked flawlessly for the last 2 years doesn't work. The problem is with the driver from what I understand from the logs.

Today 23/8/2009 I tried the drivers within vanilla kernel 2.6.30.5 (i386 and amd64) and then separately latest mercurial snapshot. I always use latest mercurial snapshot updating every time a new kernel is released. This card works within Windows XP. I also switched the PCI slot but that didn't help.

For the driver, I issued the command:

modprobe saa7134 i2c_debug=1 i2c_scan=1 disable_ir=1

I attached the log because it's kinda big for posting it on the message. For any ideas or suggestions I am here available for testing them. :)

Linux video capture interface: v2.00
saa7130/34: v4l2 driver version 0.2.15 loaded
ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
saa7134 0000:05:06.0: PCI INT A -> Link[APC1] -> GSI 16 (level, low) -> IRQ 16
saa7133[0]: found at 0000:05:06.0, rev: 209, irq: 16, latency: 32, mmio: 0xd0005000
saa7133[0]: subsystem: 5168:3306, board: LifeView FlyDVB-T Hybrid Cardbus/MSI TV @nywhere A/D NB [card=94,autodetected]
saa7133[0]: board init: gpio is 210000
IRQ 16/saa7133[0]: IRQF_DISABLED is not guaranteed on shared IRQs
saa7133[0]: i2c xfer: < a0 00 >
saa7133[0]: i2c xfer: < a1 =68 =51 =06 =33 =54 =20 =1c =00 =43 =43 =a9 =1c =55 =d2 =b2 =92 =00 =00 =62 =08 =ff =20 =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =01 =40 =01 =03 =03 =01 =01 =03 =08 =ff =01 =16 =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =21 =00 =c2 =96 =10 =05 =01 =01 =16 =32 =15 =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff > saa7133[0]: i2c eeprom 00: 68 51 06 33 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
saa7133[0]: i2c eeprom 10: 00 00 62 08 ff 20 ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 20: 01 40 01 03 03 01 01 03 08 ff 01 16 ff ff ff ff
saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 40: ff 21 00 c2 96 10 05 01 01 16 32 15 ff ff ff ff
saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c xfer: < 01 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 03 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 05 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 07 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 09 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 0b ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 0d ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 0f ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 11 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 13 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 15 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 17 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 19 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 1b ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 1d ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 1f ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 21 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 23 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 25 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 27 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 29 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 2b ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 2d ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 2f ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 31 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 33 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 35 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 37 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 39 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 3b ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 3d ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 3f ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 41 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 43 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 45 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 47 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 49 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 4b ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 4d ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 4f ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 51 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 53 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 55 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 57 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 59 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 5b ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 5d ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 5f ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 61 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 63 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 65 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 67 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 69 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 6b ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 6d ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 6f ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 71 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 73 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 75 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 77 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 79 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 7b ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 7d ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 7f ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 81 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 83 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 85 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 87 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 89 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 8b ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 8d ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 8f ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 91 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 93 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 95 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 97 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 99 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 9b ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 9d ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 9f ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < a1 >
saa7133[0]: i2c scan: found device @ 0xa0 [eeprom]
saa7133[0]: i2c xfer: < a3 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < a5 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < a7 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < a9 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < ab ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < ad ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < af ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < b1 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < b3 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < b5 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < b7 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < b9 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < bb ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < bd ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < bf ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < c1 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < c3 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < c5 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < c7 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < c9 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < cb ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < cd ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < cf ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < d1 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < d3 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < d5 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < d7 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < d9 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < db ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < dd ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < df ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < e1 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < e3 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < e5 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < e7 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < e9 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < eb ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < ed ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < ef ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < f1 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < f3 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < f5 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < f7 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < f9 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < fb ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < fd ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < ff ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 10 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 84 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 86 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 94 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 96 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < c0 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < c2 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < c4 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < c6 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < c8 ERROR: NO_DEVICE
saa7133[0]: registered device video0 [v4l2]
saa7133[0]: registered device vbi0
saa7133[0]: registered device radio0
dvb_init() allocating 1 frontend
saa7133[0]: i2c xfer: < 10 ERROR: NO_DEVICE
tda10046: chip is not answering. Giving up.
saa7133[0]/dvb: failed to attach tda10046
saa7133[0]/dvb: frontend initialization failed
saa7134 ALSA driver for DMA sound loaded
IRQ 16/saa7133[0]: IRQF_DISABLED is not guaranteed on shared IRQs
saa7133[0]/alsa: saa7133[0] at 0xd0005000 irq 16 registered as card -1

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#1 lore raw

Hi scoop,

Am Sonntag, den 23.08.2009, 17:52 +0300 schrieb [email protected]:

Quoted 5 lines

Hi, for a couple of days now, my lifeview PCI hybrid card that worked flawlessly for the last 2 years doesn't work. The problem is with the driver from what I understand from the logs.

Today 23/8/2009 I tried the drivers within vanilla kernel 2.6.30.5 (i386 and amd64) and then separately latest mercurial snapshot. I always use latest mercurial snapshot updating every time a new kernel is released. This card works within Windows XP. I also switched the PCI slot but that didn't help.

Quoted 7 lines

For the driver, I issued the command:

modprobe saa7134 i2c_debug=1 i2c_scan=1 disable_ir=1

I attached the log because it's kinda big for posting it on the message. For any ideas or suggestions I am here available for testing them. :)

the report is at least fine.

An i2c device, working over years on 0x10, vanished mysteriously.

I guess you don't have much better options here than to try, if it comes back with any combination of either most triggering it or not at all ...

Cheers,
Hermann

#2 lore raw

Considering your reply, I started today by changing the card to all PCI slots and powering on and off the machine each time, until when I put the card to the bottom PCI it worked again ! Then I tried all other slots again and it was working this time. That is some weird card behaviour !

Thanks for the tip.

Quoted 18 lines

Hi scoop,

Am Sonntag, den 23.08.2009, 17:52 +0300 schrieb [email protected]:

Quoted 5 lines

Hi, for a couple of days now, my lifeview PCI hybrid card that worked flawlessly for the last 2 years doesn't work. The problem is with the driver from what I understand from the logs.

Today 23/8/2009 I tried the drivers within vanilla kernel 2.6.30.5 (i386 and amd64) and then separately latest mercurial snapshot. I always use latest mercurial snapshot updating every time a new kernel is released. This card works within Windows XP. I also switched the PCI slot but that didn't help.

Quoted 7 lines

For the driver, I issued the command:

modprobe saa7134 i2c_debug=1 i2c_scan=1 disable_ir=1

I attached the log because it's kinda big for posting it on the message. For any ideas or suggestions I am here available for testing them. :)

the report is at least fine.

Quoted 7 lines

An i2c device, working over years on 0x10, vanished mysteriously.

I guess you don't have much better options here than to try, if it comes back with any combination of either most triggering it or not at all ...

Cheers,
Hermann

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#3 lore raw

Am Montag, den 24.08.2009, 08:58 +0300 schrieb [email protected]:

Quoted 1 line

Considering your reply, I started today by changing the card to all PCI slots and powering on and off the machine each time, until when I put the card to the bottom PCI it worked again ! Then I tried all other slots again and it was working this time. That is some weird card behaviour !

It is still a very unpleasant situation for all involved, for you of course in the first place.

But until it should not be a single problem report anymore,for now it is, we have good reasons, to start questioning about the PSU in use and its current shape, the mobo distributing the voltage further, and in the end too, if something like a capacitor on the card itself starts leaking.

After all that, unfortunately, programming still can be a point, of course, but it did not change within that driver since long.

However, others operating on a higher level, can introduce_something/clear/fail_at_all on such too.

If you can't get out of that random, but windows always works, I guess we have a performance problem on your hardware ;)

Cheers,
Hermann

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb