how to install Linux on "ChomeBook lenovo N23"

[ZeidMahmoud]

I want to install Linux on my Chromebook but I don't know how?
installing linux on noraml lapotps is very easy ,but it's quit different on Chromebooks.
Can anyone help on how to do so?

 

[GatorsFan]

Most Chromebooks built since 2019 have a built-in Linux environment called Linux (Beta) that you can easily switch to and from within the Chrome OS. It runs in Chrome’s Beta channel, versus the Stable channel used for most activities
Here’s how to activate Linux (Beta) on Chromebooks where it’s available
Go to Settings
Find Linux (Beta)
Select “Turn On”
Allow a few minutes for the Linux (Beta) files to download and install.
When complete, you’ll get a Linux (Beta) Terminal window. You can type Linux commands, install tools using a package manager, and more. The latest versions of Linux (Beta) even allow you to install the desktop of your choice

For older Chromebooks

Linux on eMMC Cards UEFI 32 bit

In order for the system to recognized the installed OS, you must ensure the system is using UEFI boot mode as well as enabling Firmware TPM BEFORE installation. Secure boot MUST be off for installation and after installation. Legacy Option ROM should be disabled. Now we just need to modify the USB so that it will boot on a 32-bit UEFI only system. While Windows is running or on another machine, insert the USB and find a directory called /EFI/BOOT. This needs to contain a bootia32.efi file - you can get it from here

GitHub - hirotakaster/baytail-bootia32.efi

Contribute to hirotakaster/baytail-bootia32.efi development by creating an account on GitHub.

github.com

Now you can install 64bit Linux

After install, the system will recognize the OS and boot properly after the TPM check which will only occur at the very first startup and never occur again .

 

[Egzoset]

The mention of « BayTrail » reminds me of the transformer tablet i destroyed earlier this year. As i recall an .ISO needed to contain more than just the ia32 EFI, like Linuxium for an Atom machine, but i ain't been thinking of that for a long while now so please add corrections if necessary!

Here's what i'd expect to be already in there before running Rufus or similar, or better yet, just copy on a USB 'YUMI-exFAT' thumbdrive when properly supported - which is a demanding test:

​

/EFI/BOOT/bootia32.efi​

/EFI/BOOT/grubia32.efi​

​

/BOOT/GRUB/*.cfg​

/BOOT/GRUB/*.pf2​

/BOOT/GRUB/*.img​

/BOOT/GRUB/i386-efi/*.mod​

/BOOT/GRUB/i386-efi/*.lst​

/BOOT/GRUB/theme/*.png​

/BOOT/GRUB/theme/*​

It's possible i also seen some configuration file redirecting to 'grub.cfg' like this:

/EFI/debian/*.cfg​

Another detail i ain't too sure about anymore is when in a LIVE session trying to install, it may help to replace 'i386-pc' with 'i386-efi' using Synaptic before rebooting but that was a messy era which left me somewhat traumatized i guess, so my brain hurts if i attempt to remember... Save your sanity, find a normal replacement machine or you'll be at risk of witnessing the OS performing harakiri at its next auto-update!



In any case better safe than sorry, have an extra EFI System Partition where to install rEFInd as this may save the day.


Addendum

I checked 69 .ISO images and found a couple hybrids with 'i386-pc'/'i386-efi' (for MBR/GPT i think), which are MX-23 and RescueZilla, then possibly Gentoo but i don't recall why i didn't revisit that one. Those with 'i386-efi' only are Mint, Sparky, Debian and Zorin. You may also wish to try Windows Ubuntu, perhaps even Fedora and OpenSUSE although i predict they'll be slow, plus gParted as a tool similarily to RescueZilla. Perhaps a YUMI/Ventoy drive allows more but we can safely bet that's still going to be under the 20 % mark (at least on an Atom anyway; go figure, a ChromeBook might prove even worse), YMMV!


Supplement

I downloaded the November 27th Gentoo release and now i begin to remember: no HardInfo, then finding out i'd have to compile my own on top of other favourite applications! No way and certainly not without moving my Dull NoteBook to the desk where to get plugged to a much larger display screen, in preparation for long hours of frustrating (torture) hours... Even in LIVE mode there was just too little incentive, so i'll keep wondering what edge i missed. The ia32 restriction no longer applies to me anyway.

 

[Brickwizard]

Installing to a chromebook can be challenging, on older machines they were physically locked, [this may have been by use of a toggle switch or more often an earthing screw which has to be removed, also many were very low powered with entry level CPU's so always look for a lightweight Linux for best results

 

[ZeidMahmoud]

Most Chromebooks built since 2019 have a built-in Linux environment called Linux (Beta) that you can easily switch to and from within the Chrome OS. It runs in Chrome’s Beta channel, versus the Stable channel used for most activities
Here’s how to activate Linux (Beta) on Chromebooks where it’s available
Go to Settings
Find Linux (Beta)
Select “Turn On”
Allow a few minutes for the Linux (Beta) files to download and install.
When complete, you’ll get a Linux (Beta) Terminal window. You can type Linux commands, install tools using a package manager, and more. The latest versions of Linux (Beta) even allow you to install the desktop of your choice

For older Chromebooks

Linux on eMMC Cards UEFI 32 bit

In order for the system to recognized the installed OS, you must ensure the system is using UEFI boot mode as well as enabling Firmware TPM BEFORE installation. Secure boot MUST be off for installation and after installation. Legacy Option ROM should be disabled. Now we just need to modify the USB so that it will boot on a 32-bit UEFI only system. While Windows is running or on another machine, insert the USB and find a directory called /EFI/BOOT. This needs to contain a bootia32.efi file - you can get it from here

GitHub - hirotakaster/baytail-bootia32.efi

Contribute to hirotakaster/baytail-bootia32.efi development by creating an account on GitHub.

github.com

Now you can install 64bit Linux

After install, the system will recognize the OS and boot properly after the TPM check which will only occur at the very first startup and never occur again .

thanks a lot