DViCo Dual Fusion Express (cx23885) remote control issue
Hi,
I recently upgraded my Myth box from Ubuntu 8.04 to 9.10 (runs 2.6.31-20-generic). Previously I used the drivers from
http://www.itee.uq.edu.au/~chrisp/Linux-DVB/DVICO/ however the card worked out of the box (once I got the later firmware) and so I presumed they had been merged.
However one thing that wasn't working was the IR receiver so I checked out the latest v4l-dvb code and built it (after disabling the 1394 based ones as they broke the build) and then installed and rebooted and it detected the IR OK, ie
Apr 13 14:40:05 mythtv kernel: [ 7.601716] input: i2c IR (FusionHDTV) as /devices/virtual/input/input6 Apr 13 14:40:05 mythtv kernel: [ 7.632093] ir-kbd-i2c: i2c IR (FusionHDTV) detected at i2c-0/0-006b/ir0 [cx23885[0]]
And it works with lirc etc etc..
However I came to use it this morning and it now doesn't find it even if I load the module from where it was built..
[mythtv 15:13] ~/v4l-dvb >sudo rmmod ir_kbd_i2c
[mythtv 15:13] ~/v4l-dvb >lsmod |grep ir_kbd_i2c
[mythtv 15:13] ~/v4l-dvb >sudo insmod /home/myth/v4l-dvb/v4l/ir-kbd-i2c.ko
I haven't delved much further yet (planning to printf my way through the probe routines) as I am a Linux kernel noob (plenty of FreeBSD experience though!).
If any one has any suggestions or patches I'd be happy to try them out :)
Thanks.
Signature · 6 lines
Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
Quoted 3 lines · Daniel O'Connor
I haven't delved much further yet (planning to printf my way through the probe routines) as I am a Linux kernel noob (plenty of FreeBSD experience though!).
I found that it is intermittent with no pattern I can determine.
When it doesn't work the probe routine is not called, but I am not sure how i2c_register_driver decides to call the probe routine.
Does anyone have an idea what the cause could be? Or at least somewhere to start looking :)
Thanks.
Signature · 6 lines
Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
Quoted 7 lines · Daniel O'Connor
Quoted 3 lines · Daniel O'Connor
I haven't delved much further yet (planning to printf my way through the probe routines) as I am a Linux kernel noob (plenty of FreeBSD experience though!).
I found that it is intermittent with no pattern I can determine.
Quoted 8 lines
When it doesn't work the probe routine is not called, but I am not sure how
i2c_register_driverdecides to call the probe routine.Does anyone have an idea what the cause could be? Or at least somewhere to start looking :)
Thanks.
A patch was posted that was suposed to be merged that fixed the ir problem, at least for me. Though my problem was not intermittent. The patch worked for me. Now if I could just get both tuners to keep working
Quoted 11 lines · Timothy D. Lenz
Quoted 10 lines · Daniel O'Connor
Quoted 3 lines · Daniel O'Connor
I haven't delved much further yet (planning to printf my way through the probe routines) as I am a Linux kernel noob (plenty of FreeBSD experience though!).
I found that it is intermittent with no pattern I can determine.
When it doesn't work the probe routine is not called, but I am not sure how
i2c_register_driverdecides to call the probe routine.
Quoted 7 lines
Quoted 2 lines
Does anyone have an idea what the cause could be? Or at least somewhere to start looking :)
A patch was posted that was suposed to be merged that fixed the ir problem, at least for me. Though my problem was not intermittent. The patch worked for me. Now if I could just get both tuners to keep working
Hmm do you have a subject line or message ID I can search for?
I haven't found any problems with tuners not working although I don't often fire them both up at once.
Signature · 6 lines
Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
Quoted 20 lines · Daniel O'Connor
Quoted 11 lines · Timothy D. Lenz
Quoted 10 lines · Daniel O'Connor
Quoted 3 lines · Daniel O'Connor
I haven't delved much further yet (planning to printf my way through the probe routines) as I am a Linux kernel noob (plenty of FreeBSD experience though!).
I found that it is intermittent with no pattern I can determine.
When it doesn't work the probe routine is not called, but I am not sure how
i2c_register_driverdecides to call the probe routine.Quoted 7 lines
Quoted 2 lines
Does anyone have an idea what the cause could be? Or at least somewhere to start looking :)
A patch was posted that was suposed to be merged that fixed the ir problem, at least for me. Though my problem was not intermittent. The patch worked for me. Now if I could just get both tuners to keep working
Quoted 5 lines
Hmm do you have a subject line or message ID I can search for?
I haven't found any problems with tuners not working although I don't often fire them both up at once.
[PATCH] FusionHDTV: Use quick reads for I2C IR device probing
Quoted 5 lines · Timothy D. Lenz
Quoted 3 lines
I haven't found any problems with tuners not working although I don't often fire them both up at once.
[PATCH] FusionHDTV: Use quick reads for I2C IR device probing
I finally found some time to look at this and found..
https://patchwork.kernel.org/patch/86939/
However I don't see anything in /sys/bus/i2c/devices so I presume it's another issue :(
--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
-- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C