[linux-dvb] Nova-t remote stopped working (budget_ci rc5_device not set?)

Kevin Page linux-dvb-list at krp.org.uk
Mon Feb 18 02:05:14 CET 2008

On Sat, 2008-01-26 at 18:07 +0000, Darren Salt wrote:
> Odd... the 34-key version should be showing up as 0x1F and the 45-key
> version as 0x1E. (Or at least that's what happens with mine.)

As far as I can tell I haven't gone entirely mad... however it seems I
have schizophrenic remote control.

I was in the middle of using the remote and it stopped working again - I
was pressing buttons at the time.

Given my previous experience, I again checked it's rc5_device value.
This now appears to be 2! Setting rc5_device to 2 in modprobe.conf
restores the remote control to a working state.

This is a little odd, to say the least. I left the remote for a day with
it's batteries remove; I have fully powered down the PC to ensure a
cold-reload of the Nova-T firmware: the change in rc5_device value has
endured both.

I presume it's most likely to be a fault with the remote, rather than a
problem elsewhere?

In hindsight, it seems likely that the remote was previously identified
as (the default) 0x1F before it decided to adopt 0x1A. However, the
information added to the wiki would still seem to be useful, even if
just for others with cranky remotes...



More information about the linux-dvb mailing list