[noggin]

The chromeOS backup is what I was referring to. So that answers my question.

What I don't understand is that so much data is recoverable on the usb that it seems the only thing missing is the firmware backup. Would this be on a fat partition or would it be stuck on some ext4 partition or something? I have stuff coming up from years ago because this drive sees so little use, but not a trace of the firmware rom.

I'm pretty sure you would not have been able to use that drive for the firmware backup, the script likely would not handle a flash drive with 12 partitions unless the first was mountable. I guess you could check by manually mounting the first partition ( /dev/sd[x]1/ ).

[quote='Matt Devo' pid='1748837' dateline='1404757469']


[quote='tret' pid='1748767' dateline='1404750697']
Thanks Matt, do you happen to have any information (main thread, bug number, etc.) about the intel driver bug so I can keep track of it and watch for developments?

https://bugs.freedesktop.org/show_bug.cgi?id=78960

the solution right now is to run with hardware acceleration (VAAPI) disabled until the issue is fixed

I may be wrong but the latest fernetmenta XBMC builds (may not be in OpenElec yet) may address this with a workaround : http://forum.xbmc.org/showthread.php?tid...pid1744261

I had some content that always froze prior to this and now plays fine if you disable "Prefer VAAPI rendering" (which retains VAAPI decoding, but uses software de-interlacing AND continues to use the SSE copying for progressive content too) It may not fix everything - but I've not had any hangs with VAAPI acceleration since?

---

Matt Devo - I may well be running two Chromeboxes on the same network, both with new core boot firmware, soon. How do I ensure they have different MAC addresses?