#INSTALL WINDOWS ON ASUS CHROMEBOX INSTALL#
#INSTALL WINDOWS ON ASUS CHROMEBOX DRIVERS#
#INSTALL WINDOWS ON ASUS CHROMEBOX DRIVER#
#INSTALL WINDOWS ON ASUS CHROMEBOX SOFTWARE#
#INSTALL WINDOWS ON ASUS CHROMEBOX PC#

Instead the driver source files are distributed in a package that recompiles the driver against the current kernel when installed or when the kernel is changed. This means the driver contains a binary blob or something which makes it impossible for GPL purists to distribute as a binary package. apt search r8168 turns up a package called r8168-dkms. lspci shows that the Ethernet chip is a Realtek r8168. Most likely the driver is in a package not in the ISO, and this has to be installed separately. What is it about Ubuntu, which GalliumOS is derived from? A search found a complaint by somebody who got various Linux distros running with a working wired interface, with the exception of Ubuntu. ChromeOS had the wired Ethernet running so it's not a matter of no driver available. ifconfig shows no wired interface, only the wireless one. One oddity is that the wired Ethernet doesn't work under GalliumOS.

I get the wired Ethernet working on GalliumOS Ken Yap.

Maybe get a proper power supply if I get sick of seeing the rubber band.

Or else replace the BIOS with a custom one. Apparently this is possible by changing the Boot Options (GBB flags) with MrChromebox's firmware script.

Fix the firmware so that it goes straight to the legacy BIOS on power up.

Plug in a spare external SSD from upgrades on other computers that is in a 2.5 inch disk form factor enclosure for /home.

So at the moment these are things I want to improve:

#INSTALL WINDOWS ON ASUS CHROMEBOX SOFTWARE#

Of course if I start installing software it will be a different story. I was worried it wouldn't fit on the SSD but in the end it used up about half of the slightly less than 16 GB on the SSD. It all worked including the wired Ethernet.

#INSTALL WINDOWS ON ASUS CHROMEBOX INSTALL#

I plugged in a USB stick that had the openSUSE ISO written on it, booted, and it took me through the install process, I accepted most of the defaults, the major change being using ext4 instead of btrfs for the filesystem as the latter is incompatible with boot block in MBR.

#INSTALL WINDOWS ON ASUS CHROMEBOX PC#

Since the hardware is actually quite PC compatible I decided to see if I could install openSUSE Leap 15.1 on it, the same version running on my other machines. GalliumOS works fine, but the desktop is based on Xfce and I prefer a richer desktop environment.

I ditch GalliumOS and pivot to openSUSE Ken Yap.

The other reason not to change to the custom firmware at the moment is that it's a UEFI BIOS which means that the openSUSE will have to be resintalled as UEFI requires a different partition layout. I'll leave it like this and not install the custom firmware for now as that has a minuscule chance of bricking the box.

So now the machine can boot openSUSE unattended. I discovered that when I had an external USB SDD plugged in, it tried to boot that first. This can also be interrupted by typing ESC. I also reinstalled the FW_LEGACY firmware to boot the internal SDD first. It's still possible to type Ctrl-d or Ctrl-l in that 1 second but I don't expect to need it. I opened up the box and followed the instructions in the Kodi wiki for disabling the hardware write protect, which is a screw bridge on the motherboard.Д«y setting a boot option I was able to select 1 second timeout at the Chrome boot script, then going straight to legacy boot without requiring Ctrl-l. Then when I tried to alter the boot flags, it told me write protection was on. This was fairly easy to do, I just added this option to the end of the GRUB options to the kernel next boot. No doubt one layer of kernel protection needs to be bypassed to use this tool. When I ran the script under openSUSE, the script couldn't read the settings and instructed me to add the kernel parameter iomem=relaxed, or to use a live USB distro. To do this I needed to alter the boot options (GBB flags) as explained by MrChromebox. Now that ChromeOS is no longer of interest, we want to boot openSUSE as soon as possible after power on without any keystrokes. Among other things I also had to transfer the udev rules for various USB devices like the Arduino Uno, STlink dongle, and so forth. Installed openSUSE Leap 15.2 on it last night and currently burning in.ДЄ few weeks later: Burn in finished, all stable so I have moved my desktop to this Chromebox. Pretty good outcome for rescued hardware.

With the i7 CPU this is going to be a powerful machine for the small size. I also bought a 2x8GB kit to bring the RAM up to 16GB, the max supported.

That's the largest I could easily get but should be adequate for desktop use as most of my files are on a workhorse machine. This is quite a short card, only 42 mm long as the form factor indicates. To that end I bought a 250 GB SSD in M.2 2242 form factor. So I will move my desktop to this Chromebox.

#INSTALL WINDOWS ON ASUS CHROMEBOX DRIVERS#

Probably some bug in the X drivers for the Intel video hardware. Getting tired of my current Intel NUC suffering graphics glitches and once in a while locking the screen requiring a couple of Ctrl-Alt-Backspaces to kill the X server (and losing my session).

Install Windows On Asus Chromebox