Mario Limonciello and others. Sorry for the confusion, Im using gutsy still in my desktop computer and ssh to the server where I have Hardy with the mythtv backend and the nova-t-500. I though I had a terminal with a ssh session onto the server but it seems it wasnt, so uname -r gave me the gutsy kernel version of the desktop computer.
The correct kernel version that I am running on the server is: 2.6.24-16-generic (I installed from the alternate cd). I can confirm the nova-t-500 its not working. It gets detected but it randomly fails to lock on channels (actually most of the time).
Mario Limonciello and others. Sorry for the confusion, Im using gutsy still in my desktop computer and ssh to the server where I have Hardy with the mythtv backend and the nova-t-500. I though I had a terminal with a ssh session onto the server but it seems it wasnt, so uname -r gave me the gutsy kernel version of the desktop computer.
The correct kernel version that I am running on the server is: 2.6.24-16-generic (I installed from the alternate cd). I can confirm the nova-t-500 its not working. It gets detected but it randomly fails to lock on channels (actually most of the time).
Dmesg shows a lot of this:
[69124.200154] mt2060 I2C read failed
[69124.208157] mt2060 I2C read failed
[69125.355212] mt2060 I2C write failed (len=2)
[69125.355241] mt2060 I2C write failed (len=6)
[69125.355255] mt2060 I2C read failed
[69125.363523] mt2060 I2C read failed
[69125.371113] mt2060 I2C read failed
Hugo