but they still seem to be trying to figure it out for you even though you do not share the same sediments for others.

Well, they're not right about the 700 vs. 710. They were both available with Core-mx, the 710 is just a refresh of the 700 (11" vs. 11" anyway), the 700 wasn't long for this world, only was in production about 5 months before the 710 replaced it. Both are available in multiple sizes, both the 11" is core-mx only, both the larger sizes can be had in core-ix. EXTREMELY similar devices, but the 710 has had battery life improved by quite a bit (according to Lenovo).

However, in the grand scheme of things, I'm now running Arch on my 700 (yes, it most definitely is a 700) after putting Fedora on my 14-an013nr since I wanted to see if Arch vs. whatever was any REAL difference with nearly exact same packages installed, surprisingly, it's not. Fedora performs very nearly identically and now even better since I upgraded my ram to 8 GB yesterday (found a 2x4 GB on craigslist for $25, sold the other 4 GB stick to my friend who ALSO has a 14-an013nr), so then put Arch on the Yoga 700 in order to try it for a while on something with a little more OOOMPH than the 14-an013nr (if you're not familiar, really low end AMD APU w/ 32 GB eMMC & 4 GB ram, but a gorgeous 1080P 14" lcd that can be had on Amazon for a mere $200 brand new).

So I wish the void folks well, but I'm not really interested in figuring out what the issue is with void and this hardware anymore. Maybe in a few more versions (when I'm sure this laptop will be gone, as my wife says, I go through laptops like most people do underwear) I'll revisit it.

well I do believe the actual point being is its a kernel thing.. because it is the part of the entire system that is running and establishing coms between the HW and OS with its Software, and seeings how the rest of the software cannot be started until the Kernel has done what it needs to do then it logically shows that it is not Void itself but the kernel having issues with the hardware init process.

Not Void .. just like I am having issues with XFCE4 .. it is not a void problem it is an xfce4 issue that just happens to be running on Void.

Yoga 700 is barely one year old. Playing with newish hardware but avoiding kernel params and module blacklists guarantees crashes once in a while. They come with the territory. Maybe you saw Arch wiki mention kernel crashing with Core-M.

Most OEM sales departments force engineering to ship bugs and make initial customers their beta testers. Pay attention to OEM firmware upgrades when toying with the latest hotness.

The lazy way to hop distros is on older gear, say 3 years. By that time, kernel and drivers are generally ironed out, and the gear is cheaper anyway. Otherwise one really does need to spend time reading bug reports to play with shiny newness.

Void ships the very latest upstream software, including kernels, even faster than Arch. What it doesn't are frequent live boot images. The reason your Arch and Fedora worked is that they had more recent kernels, I expect. Here's the Void workaround. Install to an older PC on a USB boot stick. Upgrade Void on that, adding drivers needed by the target PC (you may need to enable "nonfree" repositories). Shutdown the setup PC, and move the USB boot stick to the target PC. Voila, the latest Void is now under test on the target.

Or, as you say, just wait for the next set of live boot images. Your call.

Good luck....