It works by having the guest run a Mesa3D (Linux Userspace graphics) driver called virgl in the guest, which takes all of the OpenGL/OpenGL ES commands and send them through through Linux VirtIO to the guest, where they are executed by the virglrenderer application as normal OpenGL / OpenGL ES commands.
This let's you run whichever driver you want on the host, even proprietary ones. And it allows you you to do transparent OpenGL <-> OpenGL ES translation.
Honest question: On most OSes, don't regular drawing operations in these programs (Bitblits, font renderings) typically use hardware acceleration through the OS? On crostini, are these things currently done via pure CPU operations, or are they already being mapped to hardware-accelerated API calls, even before the new OpenGL support?
For other operating systems, the words and details change, but the overall idea of "it's complicated and depends on your driver and OS version and which apps are running and phase of the moon" still applies.
God knows if Xwayland will incorporate GLAMOR. Since almost all compositors except for Weston assume the presence of a GPU, you'd think it would, but I have not been delighted with Wayland development thus far...
There are two reasons for that decision:
- I just love having the ability to have a pen to draw when I needed to share the screen to explain something for my friends when we talk about technical crap. ChromeOS supports the pen reasonably well with its ability to run Android apps.
- The Linux emulation layer on ChromeOS is actually very good. I can run app-get, gcc, Sublime text, Konsole and most of the apps I want to run.
I figured it is a good tradeoff between convenience and utility. I still have to do my embedded work on my desktop which has a real distro. I am very glad they are bringing the upcoming usb redirection support, so I can do embedded work on my laptop. With GPU acceleration I can play games too, fantastic!
Hardware-wise, the Chromebook Pixel has been a disaster. Every once in a while, the USB-C port just craps out completely and I had to do the SMC reset procedure for it to work again. The other day, I left the laptop battery run dry and when I plugged in to charge and tried to turn it on, the keyboard would flicker like a discotheque with nothing on the screen for like 20 minutes when it was charging up. The hardware is just inconsistent and feels flaky as heck.
But all in all, I am actually quite happy with my Pixelbook purchase. If the hardware/firmware experience could improve a bit, then it would have been a very, very good purchase despite all the hates from Youtube reviewers.
How do you forgive something like that? The LTE on my Lenovo X1C 6th gen fails randomly (with recent driver updates, it’s just once a week). I’m never buying a Lenovo again, basic functionality like that should just work. Laptops are solved technology. They should not have bugs like this.
Management bugs on the other hand are harder to forgive, like that time Lenovo shipped rootkits, or the many times Apple has simply lied about bad hardware design, or that time Facebook decided not to refund children based on if it was their parents asking...
How about bent iPads, badly soldered nVidia chips, fraying cables etc?
Code mistakes (sometimes) just get fixed instead of shielded with lies to avoid liability for avoidable mistakes.
I use it as my out-on-the-town laptop out of fear of either dropping or losing my late 2013 macbook pro.
Anyway, the dev community around this is pretty decent, and other distros do run with varying degrees of success. If nothing else, its a fun, quick little project to get it up and running.
edit: I should also mention that having a 8-10hr actual-use battery life is a dream come true.
This really is where the gold is. Many people don't prioritize battery life when picking a laptop, which is just hilarious in my mind.
I even gave it a cute cover (that most people think is hideous) using some mactac -- https://i.imgur.com/wO1WW2t.jpg
The returns on investment on the time you spend tickering with your laptop are lower - because you have other uses for your time, and because you have expectations set in the past while ChomeOs keeps improving.
Now if you take a long sabbatical or go back to school, maybe you'll tinker again!
I wouldn't be satisfied unless I compiled an optimized kernel with almost no module left, etc. This takes more time than I can allot
What emulation are you talking about? ChromeOS is based on Gentoo Linux.
Google sent me a free Acer Chromebook 11 N7, with custom firmware I'm able to dual boot ChromeOS & GalliumOS (built on Xubuntu) & use the latter for running some experiments where fan-less X86 arch comes in handy.
Till X86 based SBC become affordable & widely available, the Celeron based Chromebooks seems to be an google alternative.
Linux tooling support is still very important to me. I want to be able to enjoy Konsole and Sublime text.
Windows Subsystem for Linux is getting there, but I don't think it's as advanced as ChromeOS' yet. Besides, I don't like the Metro interface and Windows 10 in general.
Mac means tying to Apple hardware. Apple hardware means crappy keyboard, heavy laptop, and no touch screen.
Or is this about something else?
So I guess now they are getting big boys HW acceleration.
I've never bought any chromebook since.
Was I just unlucky and should I git it an other try?
In short you need a pendrive and another computer with Chrome to to download a recovery image and flash the pendrive. Afterwards use a key combo on Chromebook and it should be fixed.
In my case it helped, but I retained this pendrive with instructions for my wife if it would happen again (and she managed). I had to skip updates for some time.
A lesson for me was to not buy an ARM Chromebook again.
ChromeOS market share is irrelevant outside North America, just check the worldwide market share in your favourite source.
Only Android/Linux has really taken off and even there we still don't know what are Google's plans regarding Fuchsia. It might pretty well be that some future Android version will get a new kernel, announced at Google IO.
It is now quite common to attend Linux conferences just to watch the presenters using macOS with a Linux distribution running either on a local or remote VM.
Assuming WSL keeps improving, it wouldn't surprise me to see similar sessions being done from a W10 laptop.
However since we are talking about graphics acceleration, not that much looking at the Steam community numbers, or the posts from a couple of game studios a couple of weeks back.
Today Linux apps installed on chrome os don't have sound support yet.
I just set it all up, got VS Code and IntelliJ running, and of the two, VS Code looks the best. It's the only app I've seen that integrates the menu bar items into the ChromeOS menu bar, which saves a lot of space and looks way better.
That post also highlights how, because it's not a Wayland native app, VSCode will still look crummy when e.g. you use it on monitors with varying DPI. Real Wayland apps have multiple, per-screen DPI settings:
"Multi DPI intends to allow clients to seamlessly move around on a display with multiple monitors connected, where each monitor may have very different DPIs, thus different scales, without any sudden size changes or glitches, while at the same time allowing clients to switch between different scaling factors."
wstein@penguin:~$ sudo docker run -it centos bash
Unable to find image 'centos:latest' locally
latest: Pulling from library/centos
a02a4930cb5d: Extracting 75.17MB/75.17MB
docker: failed to register layer: ApplyLayer exit status 1
stdout: stderr: operation not permitted.
See 'docker run --help'.
In fact, I added code to Docker almost 4 years ago to ignore ENOTSUP on xattr errors specifically because of filesystem support (AUFS was the issue at the time). So if it was a support issue you wouldn't see it, because the code already handles it. :P
I also tried the first option for native but it froze while the "ChromiumOS" logo was shown.