Bug 8605 - Controller locking up, only reacting to some keystrokes
: Controller locking up, only reacting to some keystrokes
Status: RESOLVED INVALID
Product: SB Controller
Classification: Unclassified
Component: UI
: unspecified
: PC Other
: -- major (vote)
: ---
Assigned To: Unassigned bug - please assign me!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-06-30 04:39 UTC by Michael Herger
Modified: 2008-06-30 10:35 UTC (History)
3 users (show)

See Also:
Category: ---


Attachments
log file from reboot -> lock up -> a few button presses -> failed shutdown (44.51 KB, application/octet-stream)
2008-06-30 04:39 UTC, Michael Herger
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Herger 2008-06-30 04:39:58 UTC
Created attachment 3512 [details]
log file from reboot -> lock up -> a few button presses -> failed shutdown

Some controllers seem to have a problem rebooting under whatever conditions. Mine does boot correctly, but while connected to my SC, updating the NP screen etc, most of the keys and the wheel are dead. Trying to shut it down using the Home key will display the Goodbye message, but never really stop it. 

Home button seems to be working, as is Volume and Rew/Ffd, but not eg. Play or Add, Center button etc.

One common property might be that the three of us (Max, Alan, me) are using pre-production units, which only recently (a week ago or so) were programmed a UUID (Alan & me), or not at all (Max).
Comment 1 Michael Herger 2008-06-30 04:43:07 UTC
One more thing: the MAC address my SBC is reporting is wrong and has been already before setting the UUID. It's no SD MAC.
Comment 2 Alan Young 2008-06-30 05:52:50 UTC
Comments by Richard suggest that this is as a result of no-longer-supported boot firmware.
Comment 3 Chris Owens 2008-06-30 10:11:04 UTC
Richard seems pretty convinced this is due to old old firmware and bootloader.  Please update or replace and re-open if there's still a problem.
Comment 4 Michael Herger 2008-06-30 10:35:14 UTC
bootloader update seems to have fixed this form me indeed. Successfully updated to 2631, rebooted etc.