> > Could you try modifying your ph script so that when it calls 'inputtrap' get
>  
> > rid of that and call
> > 
> > devi-hid kbd
> > sleep 2
> > devi-hid mouse
> > 
> > And let me know if that yields a different result?
> 
> From hard or soft restart I get inconsistent behaviour - sometimes it works, 
> but more often it doesn't. A couple of times even the keyboard was not 
> functional. 
> 
> Could it be that devi-hid has a dependency on something that is not fully 
> available until later in the Photon startup and then once available it 
> survives exit to text mode and back into Photon? 

Hi Richard,

Not really, the input driver (depending on how it was started) needs to see that Photon is running, once it sees that it
 will be able to issue the Photon events, it will complain if it doesn't see that its running.  If it was a case where 
it was depending on something, the last suggestion would have addressed that I would imagine, also the kbd module would 
be failing as well as it uses the same interface that the mouse does to communicate with Photon.  Also you are not even 
getting the reports from the HID server (io-hid) which happens _way_ before the Photon stuff.

You could try changing the ph script so that it doesn't call _any_ input drivers, and then telnet to the system once 
Photon is up you can start the input driver manually and see.

Another thing to try is to telnet in, slay and restart io-hid and then start Photon and see if that makes any difference
.

Best regards,

Erick