Brief version: How can I debug my Chromebook woes when trying to run kernel-next with the Mali drivers?
I followed this guide: Graphics and Compute Development on Samsung Chromebook It worked, but I'm left with an incredibly unstable system. I'm running a Samsung Chromebook, model number SNOW FREMONT A-E 0878.
A list of stability issues so far:
I'm even sure there's more, but for now that should give a good idea of what's up: ridiculous instability. I might be able to throw the image on a USB drive and use a USB wifi adapter and skate by some of this, but that's really not a sufficient solution. Given that and the incredible unlikeliness that anyone here has already had or is having this issue, I'd really like it if someone could tell me how to debug these issues as I don't have any clue how to approach it. I have a bit of familiarity with the Linux kernel and a ton with C, but not a darn clue how I'd go about debugging Linux running on a Chromebook.
Hope this is related enough to be discussed here - I certainly don't know where else to discuss problems with this guide.
Hmm... I'm certainly intrigued, but will it really solve my problems? I'm having issues with the MMC bus on only 3.8 - 3.4 stock with Chrubuntu works, and I can access the SD card just fine inside Cros, no signs of instability. However, even running off USB stick, excessive use of the SDIO WiFi device will cause my device to crash. (The crash leaves me at a screen with an empty VT, a non-blinking cursor at the top left, and the mouse cursor still on screen. I'm guessing that's just the result of a kernel panic happening.)