You're right that it's a realtively minor PITA, however this sort of thing niggles me ;)<br>I'm surprised there's no way to force reload of the firmware at boot time.<br>I note there's a kernel option-<br>
<br>reboot=cold<br><br>But adding this to my kernel line in grub doesn't solve the problem. Maybe the syntax is wrong... it's listed as reboot=[c]old -<br>maybe it's because I have a Phenom II and this option is deprecated...?<br>
<br>Giles<br><div id=":5j"><br><br>From: Thomas Boehm <<a href="mailto:mythtv-users@lists.boehmi.net">mythtv-users@lists.boehmi.net</a>
<div id=":5j">><br>
To: Discussion about MythTV <<a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a>><br>
Subject: Re: [mythtv-users] Hauppage Nova-T-500 losing remote on<br>
reboot<br>
Message-ID: <<a href="mailto:4F7967C9.3070901@bla.boehmi.net">4F7967C9.3070901@bla.boehmi.net</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
</div><br>
Giles wrote:<br>
> The remote always shows up on:<br>
><br>
>>cat proc/bus/input/devices<br>
><br>
> and works fine from a cold boot. If the system is rebooted with:<br>
><br>
>>sudo shutdown -r now<br>
><br>
> the remote does not respond (to irw - I couldn't get the mode2 command<br>
> to work) if the system is rebooted.<br>
> [...]<br>
> Has anyone had similar issues - is there a workaround? - or is this<br>
> kernel related? Should I file a bug report?<br>
<br>
You're lucky that it only effects the remote control. A lot of people<br>
(including me) can't use this card after a reboot at all. Check your<br>
syslog whether the card is found in a "warm" or "cold" state after a<br>
reboot. If it's found in a warm state, the firmware doesn't get loaded<br>
properly. If your card is found in a cold state, then you have a<br>
different problem.<br>
<br>
I don't have a solution other than always shut it down and switch it<br>
back on. That shouldn't be more difficult than rebooting for your GF ;-)<br>
<br>
HTH<br>
Thomas<br>
</div>