Hello Everyone. I have an 8th Gen Core i3-8130U and an 8th Gen Core m3-8100Y. According to the chart, for both, I should be using the Iris image for modern Intel CPUs. According to the charts, the division in versions takes place between the 7th and 8th generations. This seems to me an odd place to make the version division because Cofee Lake (8th Gen) was identical to Kaby Lake (7th Gen).
The Iris installer for modern Intel boots fine on the Coffee Lake processors, but after the install (I installed as dualboot to a 32GB partition on a 128GB micro SD card), both laptops hang on the very first text screen that says something like,“Booting Verified Image A”, but when use the image for older Intel CPUs, the installer boots fine on both and, after the install to the same location, fydeOS boots just fine.
Does this mean that, even though the chart says to use the modern Intel image, it’s not even an option and I am stuck using the image for older Intel? Or, is there a way to make the recommended Iris image boot for the 8th Gen CPU laptops?
I ask because, as I understand it, the Iris installer installs a more modern system, which In would prefer.
I think you are right. After writing this I found that the older image wouldn’t boot in dual boot from the sd either. Now I just have it running in vmware. I get the modern iris this way and I get sound which doesn’t work with fyde on these newer chromebooks which, I’ve read the whys and still don’t understand. Fyde is the perfect thing for chromebooks. Fyde must have made some deal with google to not replace chromeos on supported devices and, if that’s the case, they might as well just say it. It would make a hell of a lot more sense than what they wrote in the “Why fyde doesn’t work on chromebooks” section. Why else would they not have a separate download for chromebooks. FydeOS is the perfect match for Chromebooks and way cooler than ChromeOS.
And, on the same token, Google support is crucial, so a deal would make sense.
Not having a download for chromebooks because it would take much less work since the base was made for chromebooks makes much less sense. That’s, in essence, what is stated in the No Support for Chromebooks section.
I don’t think it would be frowned upon if it said, “We made a deal with Google to not replace ChromeOS on supported devices in exchange for Google integration options in FydeOS.” If that’s the case, I think most people would understand.