On Thu, 2008-02-28 at 19:11 +0000, Philip Pemberton wrote:
> [EMAIL PROTECTED]:~$ uptime
> 19:06:28 up 23:42, 3 users, load average: 1.19, 1.22, 1.18
>
> And the log is full of this crap:
> Feb 28 06:29:13 dragon syslogd 1.5.0#1ubuntu1: restart.
> Feb 28 06:29:13 dragon kernel: [39865.332785] cx24123_readreg:
> reg=0x14
> (error=-121)
> Feb 28 06:29:13 dragon kernel: [39865.333946] cx24123_readreg:
> reg=0x20
> (error=-121)
> Feb 28 06:29:13 dragon kernel: [39865.432586] cx24123_readreg:
> reg=0x14
> (error=-121)
> Feb 28 06:29:13 dragon kernel: [39865.433733] cx24123_readreg:
> reg=0x20
> (error=-121)
> Feb 28 06:29:13 dragon kernel: [39865.532380] cx24123_readreg:
> reg=0x14
> (error=-121)
> Feb 28 06:29:13 dragon kernel: [39865.533473] cx24123_readreg:
> reg=0x20
> (error=-121)
> Feb 28 06:29:13 dragon kernel: [39865.632210] cx24123_readreg:
> reg=0x14
> (error=-121)
> Feb 28 06:29:13 dragon kernel: [39865.633301] cx24123_readreg:
> reg=0x20
> (error=-121)
> Feb 28 06:29:13 dragon kernel: [39865.731998] cx24123_readreg:
> reg=0x14
> (error=-121)
> Feb 28 06:29:13 dragon kernel: [39865.733092] cx24123_readreg:
> reg=0x20
> (error=-121)
> Feb 28 06:29:14 dragon kernel: [39865.831820] cx24123_readreg:
> reg=0x14
> (error=-121)
> Feb 28 06:29:14 dragon kernel: [39866.374256] mt2060 I2C write failed
> (len=2)
> Feb 28 06:29:14 dragon kernel: [39866.374262] mt2060 I2C write failed
> (len=6)
> Feb 28 06:29:14 dragon kernel: [39866.374264] mt2060 I2C read failed
> Feb 28 06:29:14 dragon kernel: [39866.382298] mt2060 I2C read failed
> Feb 28 06:29:14 dragon kernel: [39866.390210] mt2060 I2C read failed
> Feb 28 06:29:14 dragon kernel: [39866.398195] mt2060 I2C read failed
> Feb 28 06:29:14 dragon kernel: [39866.406181] mt2060 I2C read failed
> Feb 28 06:29:14 dragon kernel: [39866.414175] mt2060 I2C read failed
> Feb 28 06:29:14 dragon kernel: [39866.422213] mt2060 I2C read failed
> Feb 28 06:29:14 dragon kernel: [39866.430162] mt2060 I2C read failed
>
> And the tuner is utterly shot. It worked for most of one recording,
> then
> promptly died.
>
> *sigh*
>
> Patrik, just out of curiosity, what kernel are you running?
> I'm running 2.6.24-8-generic on Mythbuntu 8.04 alpha 2 and thinking
> about
> downgrading to an earlier kernel.
You do know that the cx24123 module has nothing to do with the
Nova-t-500, don't you?
Would you have a DVB-S card in the system as well?
I do, and I have this module loaded too, zero error message involving
it, and I'm not really losing any tuner in normal use.
I have
* 1 Hauppauge Nova-t-500
* 1 KWorld DVB-S 100
* Gutsy 64-bit system
* Ubuntu 2.6.22 kernel
* Ubuntu updates+backports
* Medibuntu
* Mythbuntu's 0.20.2-fixes updates
* a recent v4l-dvb tree compiles against the Ubuntu headers.
The only other USB device I am using is an RF transmitter for my
keyboard.
All (and I like documenting) details there:
http://www.youplala.net/linux/home-theater-pc
Other than this issue, how's the stability of 0.21 in Hardy?
I'm itching... After al,l I ran Gutsy since alpha 2, for hardware
support reasons, but I have no real motivation apart from "I want to try
the latest and greatest" today.
nico
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
