Since upgraded to hrev50258 x86_gcc2 (from a previous nightly from March 30), my video card is identified as "VESA" instead of "Intel Extreme Graphic" in the monitor settings.
I attach my syslog.
I'm currently blocked and a lot of other people seem to be as well have used other means of communication as well to show this is happening.
Someone at some point mentioned a method of fixing this but I never got it to work (something with validating your email with the spam filter service)?
Configured IMAP then a while later when i presume it's checking for mail it crashes. I've tried this with two different IMAP accounts with different servers. I'm running hrev50258.
My machine is an ASUS eee pc 1015px with an Intel Atom N570 and GMA3150 graphics. Builds prior to and including hrev50194 are working fine with no issues but builds after this fail to boot, halting at the rocket icon on the splash screen. Changing to fail safe graphics and safe mode don't appear to have any effect.
Builds hrev50256 and hrev50252 both however garble the splash screen after all the boot icons are highlighted, and even though the screen is unresponsive and glitched, it seems as though the system has loaded since pressing the power button appears to initiate the shutdown sequence.
Added necessary supporting hooks and write-core CLI command in hrev50258. This completes the items mentioned in this ticket. There are still a few other core-related UI quirks remaining though, that should probably be addressed in their own ticket. Most notably, when debugging a core, the thread state is currently marked as 'Debugged', and consequently the UI thinks one can happily run/step such threads. I'd suggest adding a new thread state such as, say, THREAD_STATE_AUTOPSY to mark such threads so the UI has a way to discriminate that thread control is entirely unavailable, and disable the buttons accordingly.