This is for Chromebooks with the Intel X86 processor.
Puppy will not work on ARM based Chromebooks.
This will hopefully turn into a one stop place to get information on how to boot, run, use, and install Puppy on a Chromebook.
The questions people may want to solve:
How to setup the Chromebook to boot Puppy?
How to boot from a USB drive or SDHC card?
How to keep Chrome OS and dual boot with Puppy?
How to dump Chrome OS and only use Puppy?
How to boot only to the Puppy boot loader?
How to install Puppy to the internal SSD drive?
How to properly reformat the internal SSD drive?
How to get the touch pad working?
How to get all the keyboard keys working properly?
How to get the sound working?
CTRL-L stooped working. What do you do?
Answers are in the next few posts.
I need your help!!
If you have confirmed results to using Puppy on a Chromebook
and can give good details on how to do any of this.
Please help to provide this information for others to use.
I will try to update this info as you post your help.
Chromebook (How to use and put Puppy on a Chromebook)
Chromebook (How to use and put Puppy on a Chromebook)
Last edited by bigpup on Mon 22 Oct 2018, 07:09, edited 14 times in total.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
How to setup the Chromebook to boot Puppy?
Usually you want to first boot Puppy installed on a USB device. USB flash drive.
First make a backup of Chrome OS in case you want to restore:
Boot up your Chromebook and login
Plug in a spare ~2GB+ USB flash drive
Open the Chrome browser
Go to chrome://imageburner
This should give you a backup of the Chrome OS.
Next you will need to make the Chromebook able to boot from a USB device.
This gets a little complicated due to the different Chromebooks and when they were made.
Basically you need to setup the computers bios to offer the option to boot from USB.
What is needed:
"legacy boot" mode needs setup and selected in the computers bios.
How to get "legacy boot" setup depends on the Chromebook.
Basic steps:
Enable developer mode.
(This sets up the computer to always boot in developer mode, so you can select devices to boot from).
To enable developer mode:
Press and hold the Esc + F3 (Refresh) keys, then press the Power button. This enters Recovery Mode.
Some Chromeboxes have a dedicated Recovery button, which should be pressed/held while powering on
Press Ctrl + D (no prompt). It will ask you to confirm, then the system will revert its state and enable Developer Mode.
If done correctly, you get the developer mode screen that gives warning "OS verification is off"
Depending on the bios in the computer.
1. Chrome OS device with SeaBIOS:
Enable legacy boot / SeaBIOS.
Set SeaBIOS as default ( not needed, requires disabling the write protection).
OR:
2.Chrome OS device without SeaBIOS:
Flash a custom firmware.
This will install Seabios to give you legacy boot option.
Arch/Linux has a good help page on how to setup "legacy boot".
https://wiki.archlinux.org/index.php/Chrome_OS_devices
MrChromebox.tech is a very good place to get needed firmware(bios).
Several versions of firmware to choose from.
https://mrchromebox.tech/
Example:
Getting "legacy boot" to work on my HP Chromebook 14.
It did not have the Seabios already installed. I had to Flash a custom firmware.
1. I enabled developer mode.
2. Used this for the custom firmware.
https://mrchromebox.tech/#fwscript
I just selected to do the Install/Update the RW_LEGACY Firmware. (Did not need to do firmware write-protect disable).
Now when the Chromebook boots I get the developer mode screen that gives warning "OS verification is off"
(Gives 30 seconds to give command or boots into Chrome OS).
Press keys ctrl-L
Press ESC (escape key) for boot menu.
Changes to the selection screen to choose which device to boot from.
USB is selected to boot Puppy on a USB flash drive.
Now booted to a running Puppy.
Usually you want to first boot Puppy installed on a USB device. USB flash drive.
First make a backup of Chrome OS in case you want to restore:
Boot up your Chromebook and login
Plug in a spare ~2GB+ USB flash drive
Open the Chrome browser
Go to chrome://imageburner
This should give you a backup of the Chrome OS.
Next you will need to make the Chromebook able to boot from a USB device.
This gets a little complicated due to the different Chromebooks and when they were made.
Basically you need to setup the computers bios to offer the option to boot from USB.
What is needed:
"legacy boot" mode needs setup and selected in the computers bios.
How to get "legacy boot" setup depends on the Chromebook.
Basic steps:
Enable developer mode.
(This sets up the computer to always boot in developer mode, so you can select devices to boot from).
To enable developer mode:
Press and hold the Esc + F3 (Refresh) keys, then press the Power button. This enters Recovery Mode.
Some Chromeboxes have a dedicated Recovery button, which should be pressed/held while powering on
Press Ctrl + D (no prompt). It will ask you to confirm, then the system will revert its state and enable Developer Mode.
If done correctly, you get the developer mode screen that gives warning "OS verification is off"
Depending on the bios in the computer.
1. Chrome OS device with SeaBIOS:
Enable legacy boot / SeaBIOS.
Set SeaBIOS as default ( not needed, requires disabling the write protection).
OR:
2.Chrome OS device without SeaBIOS:
Flash a custom firmware.
This will install Seabios to give you legacy boot option.
Arch/Linux has a good help page on how to setup "legacy boot".
https://wiki.archlinux.org/index.php/Chrome_OS_devices
MrChromebox.tech is a very good place to get needed firmware(bios).
Several versions of firmware to choose from.
https://mrchromebox.tech/
Example:
Getting "legacy boot" to work on my HP Chromebook 14.
It did not have the Seabios already installed. I had to Flash a custom firmware.
1. I enabled developer mode.
2. Used this for the custom firmware.
https://mrchromebox.tech/#fwscript
I just selected to do the Install/Update the RW_LEGACY Firmware. (Did not need to do firmware write-protect disable).
Now when the Chromebook boots I get the developer mode screen that gives warning "OS verification is off"
(Gives 30 seconds to give command or boots into Chrome OS).
Press keys ctrl-L
Press ESC (escape key) for boot menu.
Changes to the selection screen to choose which device to boot from.
USB is selected to boot Puppy on a USB flash drive.
Now booted to a running Puppy.
Last edited by bigpup on Thu 19 Mar 2020, 05:23, edited 21 times in total.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
How to boot from a USB drive or SDHC card?
Get the Chromebook setup to use "legacy boot" as shown above.
Now when the Chromebook boots:
You get the "developer mode" screen that gives warning "OS verification is off"
Press keys ctrl-L
Press ESC (escape key) for boot menu.
Changes to the selection screen to choose which device to boot from.
Select the USB drive or SDHC card device that has Puppy on it.
Now should boot to a running Puppy.
Note:
ctrl-U is also a bios boot option, but it is for booting a Chrome OS that is on a USB device.
Do not try to use this to boot Puppy.
Get the Chromebook setup to use "legacy boot" as shown above.
Now when the Chromebook boots:
You get the "developer mode" screen that gives warning "OS verification is off"
Press keys ctrl-L
Press ESC (escape key) for boot menu.
Changes to the selection screen to choose which device to boot from.
Select the USB drive or SDHC card device that has Puppy on it.
Now should boot to a running Puppy.
Note:
ctrl-U is also a bios boot option, but it is for booting a Chrome OS that is on a USB device.
Do not try to use this to boot Puppy.
Last edited by bigpup on Fri 12 Apr 2019, 13:06, edited 7 times in total.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
How to keep Chrome OS and dual boot with Puppy?
Easy answer:
Only boot Puppy from a USB device or from a SDHC card.
Chrome OS stays the way it is on the internal SSD drive.
You will have option to boot the one you want to.
Get the Chromebook setup to use "legacy boot" as shown in previous posts.
At first boot you will see the warning screen "OS verification is off".
You have two options:
1, Press keys ctrl-L.
This will give you option to boot from the Puppy USB or SDHC card.
Or
2. Press keys ctrl-D
This will boot into Chrome OS.
You can also do nothing at the "OS verification is off" screen and Chrome OS will boot after 30 sec.
Note:
If you keep Chrome OS do not change the partitioning on the internal SSD drive. It is setup for Chrome OS.
There should be one partition that is large and formatted ext 4. Puppy can use it for storage, but keep in mind that Chrome OS also uses it for storage.
Easy answer:
Only boot Puppy from a USB device or from a SDHC card.
Chrome OS stays the way it is on the internal SSD drive.
You will have option to boot the one you want to.
Get the Chromebook setup to use "legacy boot" as shown in previous posts.
At first boot you will see the warning screen "OS verification is off".
You have two options:
1, Press keys ctrl-L.
This will give you option to boot from the Puppy USB or SDHC card.
Or
2. Press keys ctrl-D
This will boot into Chrome OS.
You can also do nothing at the "OS verification is off" screen and Chrome OS will boot after 30 sec.
Note:
If you keep Chrome OS do not change the partitioning on the internal SSD drive. It is setup for Chrome OS.
There should be one partition that is large and formatted ext 4. Puppy can use it for storage, but keep in mind that Chrome OS also uses it for storage.
Last edited by bigpup on Thu 16 Apr 2020, 02:08, edited 7 times in total.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
How to remove Chrome OS and only use Puppy
Delete ChromeOS from internal drive and replace with a Puppy version.
There are so many different Chromebooks, that one method is probably not 100% works on all.
However, this general procedure will usually work.
http://www.murga-linux.com/puppy/viewto ... 91#1055391
WARNING:
This requires replacing the Chromebooks firmware(bios) with a full replacement firmware.
The one offered by mrchromebox.tech
Carefully follow all steps and procedures.
Note:
You will need to use a UEFI boot loader to boot any Puppy version.
Mrchromebox firmware only works with UEFI boot loaders.
Frugalpup Installer
http://www.murga-linux.com/puppy/viewtopic.php?t=114340
This is the best Puppy installer to use.
It will install a UEFI boot loader.
Delete ChromeOS from internal drive and replace with a Puppy version.
There are so many different Chromebooks, that one method is probably not 100% works on all.
However, this general procedure will usually work.
http://www.murga-linux.com/puppy/viewto ... 91#1055391
WARNING:
This requires replacing the Chromebooks firmware(bios) with a full replacement firmware.
The one offered by mrchromebox.tech
Carefully follow all steps and procedures.
Note:
You will need to use a UEFI boot loader to boot any Puppy version.
Mrchromebox firmware only works with UEFI boot loaders.
Frugalpup Installer
http://www.murga-linux.com/puppy/viewtopic.php?t=114340
This is the best Puppy installer to use.
It will install a UEFI boot loader.
Last edited by bigpup on Thu 16 Apr 2020, 10:17, edited 5 times in total.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
How to install Puppy to the internal SSD drive?
See above post.
See above post.
Last edited by bigpup on Thu 16 Apr 2020, 00:56, edited 1 time in total.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
This is only if you are going to completely remove Chrome OS from the internal SSD drive.
How to properly reformat the internal SSD drive?
THANKS to rcrsn51 for this information!
Here is my understanding of the "SSD Partition Alignment" issue. This may be over-simplified - please feel free to comment.
Conventional hard drives read/write data in blocks of 512 bytes (1/2 K). But SSD's work in larger 4K blocks. When your computer wants to read/write a chunk of data to the SSD, it's best if the chunk fits entirely inside one of these 4K blocks. If it straddles the boundary of two blocks, the SSD has to read/write both of them. That's bad.
So when you format an SDD, you want each partition to start on a 4K boundary. That way, each data block from your computer is guaranteed to fit inside a 4K block on the SSD.
But in conventional partitioning schemes, partitions can start almost anywhere. If they start on old-style cylinder boundaries, they probably won't match up with the 4K blocks.
Here is how Gparted now works with an SSD. It collects the 4K blocks into groups of 256 (4K x 256 = 1 MB). So it sees the SSD as a string of 1MB blocks.
It reserves the first 1MB block for the MBR/partition table, even though a standard DOS MBR only needs a bit of that space. It then starts each partition on a 1 MB boundary. That ensures that each 1MB block of the partition matches up exactly with a whole number of 4K blocks on the SSD. Your SSD is optimized.
If you are using a recent version of Gparted, just select the default "Align to MB" and you are good to go.
This might be a significant issue for Puppy users who have installed SSD's but have formatted them with old versions of Gparted that have "aligned to cylinders".
Here is a test. Run "fdisk -l" and check the Start value for each partition. If it's an odd number like 63, that's bad. The partition is NOT aligned. If it's a power of two, like 2048, that's good.
Here is why 63 is bad. A 4K block on the SSD is equivalent to 8 basic 512 byte sectors. In fdisk, sectors are numbered starting at 0. If your first partition starts at sector 63, there are 63 unassigned sectors before it. But that's one less than a multiple of 4K. So the start of your partition is not aligned with the start of a 4K block.
Note:
You may have to do this with Gparted to get it correct.
Start up Gparted and find your SSD in the upper-right dropdown menu. Select it, and click on your first partition in the menu. Hit the Resize/Move button in the toolbar. Change the "Free Space Preceding" box to 2MB, uncheck "Round to Cylinders", and hit "Resize/Move". (If you're using a newer live CD, check the "MiB" box). Hit Apply once and let it do its thing.
Now hit Resize/Move again, and change the "Free Space Preceding" box to 1MB. Uncheck "Round to Cylinders" again, hit Resize/Move, then click Apply. Now your drive will be aligned to exactly 2048 blocks after the beginning of the disk, which allows for optimal SSD performance. Note that if you have multiple partitions on your SSD, you'll need to repeat this process for each partition, not just the first one on the disk.
How to properly reformat the internal SSD drive?
THANKS to rcrsn51 for this information!
Here is my understanding of the "SSD Partition Alignment" issue. This may be over-simplified - please feel free to comment.
Conventional hard drives read/write data in blocks of 512 bytes (1/2 K). But SSD's work in larger 4K blocks. When your computer wants to read/write a chunk of data to the SSD, it's best if the chunk fits entirely inside one of these 4K blocks. If it straddles the boundary of two blocks, the SSD has to read/write both of them. That's bad.
So when you format an SDD, you want each partition to start on a 4K boundary. That way, each data block from your computer is guaranteed to fit inside a 4K block on the SSD.
But in conventional partitioning schemes, partitions can start almost anywhere. If they start on old-style cylinder boundaries, they probably won't match up with the 4K blocks.
Here is how Gparted now works with an SSD. It collects the 4K blocks into groups of 256 (4K x 256 = 1 MB). So it sees the SSD as a string of 1MB blocks.
It reserves the first 1MB block for the MBR/partition table, even though a standard DOS MBR only needs a bit of that space. It then starts each partition on a 1 MB boundary. That ensures that each 1MB block of the partition matches up exactly with a whole number of 4K blocks on the SSD. Your SSD is optimized.
If you are using a recent version of Gparted, just select the default "Align to MB" and you are good to go.
This might be a significant issue for Puppy users who have installed SSD's but have formatted them with old versions of Gparted that have "aligned to cylinders".
Here is a test. Run "fdisk -l" and check the Start value for each partition. If it's an odd number like 63, that's bad. The partition is NOT aligned. If it's a power of two, like 2048, that's good.
Here is why 63 is bad. A 4K block on the SSD is equivalent to 8 basic 512 byte sectors. In fdisk, sectors are numbered starting at 0. If your first partition starts at sector 63, there are 63 unassigned sectors before it. But that's one less than a multiple of 4K. So the start of your partition is not aligned with the start of a 4K block.
Note:
You may have to do this with Gparted to get it correct.
Start up Gparted and find your SSD in the upper-right dropdown menu. Select it, and click on your first partition in the menu. Hit the Resize/Move button in the toolbar. Change the "Free Space Preceding" box to 2MB, uncheck "Round to Cylinders", and hit "Resize/Move". (If you're using a newer live CD, check the "MiB" box). Hit Apply once and let it do its thing.
Now hit Resize/Move again, and change the "Free Space Preceding" box to 1MB. Uncheck "Round to Cylinders" again, hit Resize/Move, then click Apply. Now your drive will be aligned to exactly 2048 blocks after the beginning of the disk, which allows for optimal SSD performance. Note that if you have multiple partitions on your SSD, you'll need to repeat this process for each partition, not just the first one on the disk.
Last edited by bigpup on Fri 12 Apr 2019, 13:05, edited 4 times in total.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
How to get the touch pad working?
This is determined by the touch pad hardware.
The best help is to be using a Puppy version, using Linux kernel 4 series. The newer the kernel the better.
A good search on the internet for the specific chromebook (make and model) and using touch pad in Linux, is going to help.
Example:
I have a HP Chromebook 14
Bionicpup64 7.9.5, using Linux kernel 4.14.71
Most functions of the touch pad work, but I have no adjustment options.
This helps to get mouse/keyboard wizard>Touchpad working.
Using Puppy Linux Bionicpup64 8.0
Touchpad works.
All support is already setup.
This is determined by the touch pad hardware.
The best help is to be using a Puppy version, using Linux kernel 4 series. The newer the kernel the better.
A good search on the internet for the specific chromebook (make and model) and using touch pad in Linux, is going to help.
Example:
I have a HP Chromebook 14
Bionicpup64 7.9.5, using Linux kernel 4.14.71
Most functions of the touch pad work, but I have no adjustment options.
This helps to get mouse/keyboard wizard>Touchpad working.
Update:corvus wrote:Edit the file /etc/X11/xorg.conf removing the # symbol from the beginning of the following lines:andSection "Module"
# Load "synaptics" #loadsynapticsadd the following section:Section "ServerLayout"
# InputDevice "Synaptics Mouse" "AlwaysCore" #serverlayoutsynapticsRestart.Section "InputDevice"
Identifier "Synaptics Mouse"
Driver "synaptics"
Option "SHMConfig" "on"
EndSection
Using Puppy Linux Bionicpup64 8.0
Touchpad works.
All support is already setup.
Last edited by bigpup on Wed 22 May 2019, 12:32, edited 5 times in total.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
How to boot only to the Puppy boot loader?
This will depend on what firmware(bios) you are using.
If using Legacy Boot option in Seabios or by flashing the bios with mrchromebox RW_LEGACY Firmware.
You will have to navigate, to the Puppy USB drive, and finally, get to the Puppy boot loader.
If using the mrchromebox, (UEFI) Full ROM, replacement firmware.
Configure it's default, boot device, to be the drive Puppy is installed on.
When it boots.
It is auto timed (5 seconds) to first give the (UEFI) Full ROM boot screen.
Than the Puppy boot menu.
This will depend on what firmware(bios) you are using.
If using Legacy Boot option in Seabios or by flashing the bios with mrchromebox RW_LEGACY Firmware.
You will have to navigate, to the Puppy USB drive, and finally, get to the Puppy boot loader.
If using the mrchromebox, (UEFI) Full ROM, replacement firmware.
Configure it's default, boot device, to be the drive Puppy is installed on.
When it boots.
It is auto timed (5 seconds) to first give the (UEFI) Full ROM boot screen.
Than the Puppy boot menu.
Last edited by bigpup on Tue 28 Apr 2020, 16:05, edited 1 time in total.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
How to get sound working?
Here is a warning about sound.
http://www.murga-linux.com/puppy/viewto ... 54#1025054
There is much more specific information available now, which specifically relates to the Realtek ALC5650 audio chip on some Braswell type Chromebooks, with a list of the affected models.
https://wiki.galliumos.org/Support/Braswell
https://github.com/GalliumOS/galliumos- ... issues/270
IMPORTANT NOTE REGARDING AUDIO
Braswell Chromebooks come with one of two audio chips: Maxim 98090 or Realtek ALC5650/5654. There are several reports of hardware speaker failures (overheating) on models with the Realtek chip.
Models with Maxim 98090
Acer Chromebook R11 CYAN
Models with Realtek ALC5650/5654
Acer Chromebook 14 EDGAR
Lenovo N22/N42 Chromebook REKS
HP Chromebook 11 G5 SETZER
Samsung Chromebook 3 (XE500C13) CELES
Acer Chromebook 15 (CB3-532) BANON
ASUS Chromebook C202SA TERRA
ASUS Chromebook C300SA TERRA
CTL NL61 Chromebook RELM
Lenovo ThinkPad 11e Chromebook G3 ULTIMA
Lenovo ThinkPad Yoga G3 ULTIMA
How to get sound working:
There are so many different Chromebooks, that one method will not work, for all.
Some Chromebooks, sound will just work.
Others will need some added drivers, firmware, different Linux kernel, support files, and settings.
Note about Linux kernel:
The kernel has to be configured for activating the sound device in the Chromebook.
This is a kernel compiled, that hopefully does this, for your sound device.
Linux kernel 5.4.27 (64bit)
http://www.murga-linux.com/puppy/viewto ... 53#1055653
change_kernels (entered in a terminal) will run a program made for changing the kernel.
Doing a good search of the internet, for your specific Chromebook and sound, will probably give you information, on what you need.
The sound hardware is the important thing to look for.
Example:
This is a general idea of what you may need to do.
This seems to work to get sound, if your Chromebook has the chtmax98090 sound hardware.
http://www.murga-linux.com/puppy/viewto ... 41#1056141
Here is a warning about sound.
http://www.murga-linux.com/puppy/viewto ... 54#1025054
There is much more specific information available now, which specifically relates to the Realtek ALC5650 audio chip on some Braswell type Chromebooks, with a list of the affected models.
https://wiki.galliumos.org/Support/Braswell
https://github.com/GalliumOS/galliumos- ... issues/270
IMPORTANT NOTE REGARDING AUDIO
Braswell Chromebooks come with one of two audio chips: Maxim 98090 or Realtek ALC5650/5654. There are several reports of hardware speaker failures (overheating) on models with the Realtek chip.
Models with Maxim 98090
Acer Chromebook R11 CYAN
Models with Realtek ALC5650/5654
Acer Chromebook 14 EDGAR
Lenovo N22/N42 Chromebook REKS
HP Chromebook 11 G5 SETZER
Samsung Chromebook 3 (XE500C13) CELES
Acer Chromebook 15 (CB3-532) BANON
ASUS Chromebook C202SA TERRA
ASUS Chromebook C300SA TERRA
CTL NL61 Chromebook RELM
Lenovo ThinkPad 11e Chromebook G3 ULTIMA
Lenovo ThinkPad Yoga G3 ULTIMA
How to get sound working:
There are so many different Chromebooks, that one method will not work, for all.
Some Chromebooks, sound will just work.
Others will need some added drivers, firmware, different Linux kernel, support files, and settings.
Note about Linux kernel:
The kernel has to be configured for activating the sound device in the Chromebook.
This is a kernel compiled, that hopefully does this, for your sound device.
Linux kernel 5.4.27 (64bit)
http://www.murga-linux.com/puppy/viewto ... 53#1055653
change_kernels (entered in a terminal) will run a program made for changing the kernel.
Doing a good search of the internet, for your specific Chromebook and sound, will probably give you information, on what you need.
The sound hardware is the important thing to look for.
Example:
This is a general idea of what you may need to do.
This seems to work to get sound, if your Chromebook has the chtmax98090 sound hardware.
http://www.murga-linux.com/puppy/viewto ... 41#1056141
Last edited by bigpup on Sat 02 May 2020, 20:06, edited 5 times in total.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
CTRL-L stopped working
CTRL-L stopped working.
All I get is beeping when I press CTRL-L.
If you let the computers battery go dead.
The CTRL-L key combination could be lost and has to be reset.
Do this:
At the developer mode screen that gives warning "OS verification is off"
1. Press Ctrl-D to boot into ChromeOS, but DON’T LOG IN.
2. Press CTRL-ALT-(the forward arrow key on top row of keys. 2nd one over from Escape key) image attached
will bring you to tty2, which presents you with a standard Linux login prompt.
3. Log in as chronos (no password, unless you’d previously set one).
4. Enter:
That’s it. You’re now ready to reboot and SUCCESSFULLY Ctrl-L .
All I get is beeping when I press CTRL-L.
If you let the computers battery go dead.
The CTRL-L key combination could be lost and has to be reset.
Do this:
At the developer mode screen that gives warning "OS verification is off"
1. Press Ctrl-D to boot into ChromeOS, but DON’T LOG IN.
2. Press CTRL-ALT-(the forward arrow key on top row of keys. 2nd one over from Escape key) image attached
will bring you to tty2, which presents you with a standard Linux login prompt.
3. Log in as chronos (no password, unless you’d previously set one).
4. Enter:
Code: Select all
sudo crossystem dev_boot_usb=1 dev_boot_legacy=1- Attachments
-
- chromebookkeyboard-300x225.jpg
- (23.01 KiB) Downloaded 1937 times
Last edited by bigpup on Tue 28 Apr 2020, 15:28, edited 10 times in total.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
-
gcmartin
This might be helpful and this too
Lots of useful information on the 2nd link.
Be aware. ChromeOS on a touch device is about to get VERY useful. ... very!
Lots of useful information on the 2nd link.
Be aware. ChromeOS on a touch device is about to get VERY useful. ... very!
gcmartin,
Thanks for the links.
That information is good if your Chromebook has the options.
Some do, some do not.
My second post "How to setup the Chromebook to boot Puppy" is basically trying to explain how this information applies to booting Puppy.
Thanks for the links.
That information is good if your Chromebook has the options.
Some do, some do not.
My second post "How to setup the Chromebook to boot Puppy" is basically trying to explain how this information applies to booting Puppy.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
toucpad with puppy
Hi
I have been using Puppy on an Acer C720 Chromebook for about 2 years now. I find that Puppy works very well on it apart from the touchpad and closing the lid. Fatdog has the touchpad working but it is not as good as when the Chromebook is using the ChromeOS system. My wife uses an HP14 Chromebook which is very good apart from some niggles but it does set a standard since it uses the same processors, etc.
I should also say that I have tried different distros on it and Ubuntu and Mint work well including the touchpad and lid closure. However, the touchpad is still not as good as with the ChromeOS. I have tried other distros as well including PCLinuxOS which has the touchpad working although it is not as good as the Ubuntu type Distros.
I have had the touchpad working in Puppy but to do that I had to to use the Woof-ce process and recompile the kernel to include the drivers for the touchpad, etc. It was still not as smooth as the ChromeOS but it was usable. My OS was at an alpha/beta stage and I did not pursue it further although I keep thinking I should. If any anyones wants it I am sure that I could find my dotconfigs that I used to compile the kernel.
peterw
I have been using Puppy on an Acer C720 Chromebook for about 2 years now. I find that Puppy works very well on it apart from the touchpad and closing the lid. Fatdog has the touchpad working but it is not as good as when the Chromebook is using the ChromeOS system. My wife uses an HP14 Chromebook which is very good apart from some niggles but it does set a standard since it uses the same processors, etc.
I should also say that I have tried different distros on it and Ubuntu and Mint work well including the touchpad and lid closure. However, the touchpad is still not as good as with the ChromeOS. I have tried other distros as well including PCLinuxOS which has the touchpad working although it is not as good as the Ubuntu type Distros.
I have had the touchpad working in Puppy but to do that I had to to use the Woof-ce process and recompile the kernel to include the drivers for the touchpad, etc. It was still not as smooth as the ChromeOS but it was usable. My OS was at an alpha/beta stage and I did not pursue it further although I keep thinking I should. If any anyones wants it I am sure that I could find my dotconfigs that I used to compile the kernel.
peterw
peterw,
Any tips on how you did it and are using Puppy?
HP Chromebook 14 is what I have.
Touch pad and sound is my only problems, using the latest versions of Puppy.
Any tips on correcting these issues?
Please give some details on how Puppy is installed.I have been using Puppy on an Acer C720 Chromebook for about 2 years now.
Any tips on how you did it and are using Puppy?
HP Chromebook 14 is what I have.
Touch pad and sound is my only problems, using the latest versions of Puppy.
Any tips on correcting these issues?
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
Installing Puppy
Hi
Originally I kept the 16GB ssd but managed to set up partitions for Puppy and Hugegreenbugs Ubuntu and Bodhi for the C720. They worked well but with Puppies I had to use an external mouse. Fatdog developed a Puppy that enabled the use of the touchpad. Both Hugegreenbugs Ubuntu and Bodhi worked really well althogh the sensitivity and features of the touch pad were not as good as the original ChromebookOS. I also have a HP14 Chromebook that my wife uses and it uses the same processor and touchpad as the C720 and so it sets a standard.
After the warranty run out and ssd prices dropped enough, I bought a 128GB 42mm ssd for C720 and that is what I run now. At the moment the partitions are: I have 2GB for SWAP, although I don't think I need it, 12 GB for frugally installed Puppies and these do change' and the two equalish partitions for Mint with xfce, 32 bit and PCLinux with the addition of Mythtv which with the use of a usb TV stick works well on the occasions I need it.
Unfortunately, to get the touchpad in Puppy working in the Chromebook you need to go through the Woof-ce process and recompile the kernel and enable the trackpad in the dotconfig file. I have done this and intend to have another go and I got the trackpad working but lost proper icons, etc. I was at a alpha / beta stage and did not have the skill to sort it out. I have the intention to try again but need to find the time.
OK. When I started on this I used the procedure outlined by John Lewis? You need to enable developer mode and modify the boot code. The nearest I can find to it at the moment is the Arch web site instructions.
https://wiki.archlinux.org/index.php/Chrome_OS_devices
When changing the ssd I disconnected the battery and this meant that I had to reinstall the ChromeOS again to go into developer mode to alter the boot code. This time I took out the screw so that I could make changes to the boot permanent. This has the benefit that I Don't have to do a Cntrl + L every time I boot and if I let the batteries run down, it does not matter. I don't have to reinstall ChromeOS to go into developer mode, etc.
I need to mention that many distros boot OK on the Chromebook although some need mem=1950m added because of a feature of the coreboot/seabios.
Rereading your request. I need to mention sound. The Chromebook has both HDMI sound and its internal one. With Puppy it boots up with the HDMI sound and you need to use the sound setup to switch them.
I hope this is of some use.
Originally I kept the 16GB ssd but managed to set up partitions for Puppy and Hugegreenbugs Ubuntu and Bodhi for the C720. They worked well but with Puppies I had to use an external mouse. Fatdog developed a Puppy that enabled the use of the touchpad. Both Hugegreenbugs Ubuntu and Bodhi worked really well althogh the sensitivity and features of the touch pad were not as good as the original ChromebookOS. I also have a HP14 Chromebook that my wife uses and it uses the same processor and touchpad as the C720 and so it sets a standard.
After the warranty run out and ssd prices dropped enough, I bought a 128GB 42mm ssd for C720 and that is what I run now. At the moment the partitions are: I have 2GB for SWAP, although I don't think I need it, 12 GB for frugally installed Puppies and these do change' and the two equalish partitions for Mint with xfce, 32 bit and PCLinux with the addition of Mythtv which with the use of a usb TV stick works well on the occasions I need it.
Unfortunately, to get the touchpad in Puppy working in the Chromebook you need to go through the Woof-ce process and recompile the kernel and enable the trackpad in the dotconfig file. I have done this and intend to have another go and I got the trackpad working but lost proper icons, etc. I was at a alpha / beta stage and did not have the skill to sort it out. I have the intention to try again but need to find the time.
OK. When I started on this I used the procedure outlined by John Lewis? You need to enable developer mode and modify the boot code. The nearest I can find to it at the moment is the Arch web site instructions.
https://wiki.archlinux.org/index.php/Chrome_OS_devices
When changing the ssd I disconnected the battery and this meant that I had to reinstall the ChromeOS again to go into developer mode to alter the boot code. This time I took out the screw so that I could make changes to the boot permanent. This has the benefit that I Don't have to do a Cntrl + L every time I boot and if I let the batteries run down, it does not matter. I don't have to reinstall ChromeOS to go into developer mode, etc.
I need to mention that many distros boot OK on the Chromebook although some need mem=1950m added because of a feature of the coreboot/seabios.
Rereading your request. I need to mention sound. The Chromebook has both HDMI sound and its internal one. With Puppy it boots up with the HDMI sound and you need to use the sound setup to switch them.
I hope this is of some use.
Location of screw for bios
Hi
If you are using a HP 14 Chromebook the screw is given by:
http://s290.photobucket.com/user/bond30 ... 3.jpg.html
Also, as an aside, my HP14 was very fan noisy at times and it was annoying. After reading many complaints about swapping fans as a solution and seeing that this was not the cause, I noted that there was a printed ribbon connector going across the top of the fan with a little circuitry the other side. The penny dropped. I unscrewed the little circuitry and added a bit of grease to better the thermal contact and then tightening up the screw so that it pressed against against the metal of the hinge which is the heat sink the HP 14 went quiet. Success. That circuitry monitors the temperature at the far end of the fan and to do this well it needs to be attached to its heat sink - the hinge.
If you are using a HP 14 Chromebook the screw is given by:
http://s290.photobucket.com/user/bond30 ... 3.jpg.html
Also, as an aside, my HP14 was very fan noisy at times and it was annoying. After reading many complaints about swapping fans as a solution and seeing that this was not the cause, I noted that there was a printed ribbon connector going across the top of the fan with a little circuitry the other side. The penny dropped. I unscrewed the little circuitry and added a bit of grease to better the thermal contact and then tightening up the screw so that it pressed against against the metal of the hinge which is the heat sink the HP 14 went quiet. Success. That circuitry monitors the temperature at the far end of the fan and to do this well it needs to be attached to its heat sink - the hinge.