quarkscript / linux-armv7-xe303c12-only Goto Github PK

While tray to install minimal installation of xorg-server for openbox i get errors for every lbibgl. While other trays after installing whole gnome, it was working everything, my target is minimal openbox/wayland.
Seems problem with devfreq gpu.

log xorg

How easy to use firewall in this Arch bulid?
New kernel configuration http://www.linuxfromscratch.org/blfs/view/svn/postlfs/iptables.html dosent work for iptables and nftables after compiling and installing "linux pakage".

• nftables FAILURE:
  my systemctl status nftables - https://pastebin.com/raw/QAt7Py1r
  my journalctl -xe - https://pastebin.com/raw/MubQH2iy
• nftables Main Page - https://wiki.nftables.org/wiki-nftables/index.php/Main_Page#Introduction

Can't load .rules even width new kernel, the same output by every usable iptabes command
iptables v1.8.6 (legacy): can't initialize iptables table filter: Table does not exist (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded.
iptables-restore < /etc/iptables/empty.rules
iptables- F - the same output

my lsmod - https://pastebin.com/raw/iGnXLnuS
my ls /bin | grep table - https://pastebin.com/raw/gaPd9vXD

Works thank you for your work and time for the best device ever ... this aß issuse can be deleted

Hello.

I'm still trying to enable KVM on a more recent kernel version,to be precise on the 5.4.244. Quickly this is what I did :

1. I have formatted my sd card following the procedure explained by the v.o.s website. I mean this is what I did :

In the uboot source directory:

$ sudo ./scripts/sdcard.sh /dev/sdX

This will erase all data and create 4 partitions in the medium, along with copying the u-boot binary to the first partition:

a) ChromeOS signed binary (vos chained u-boot)

b) Partition 2 not used

c) EXT2 partition for u-boot files (here I have copied your zImage (converted in uImage and your exynos5250-snow.dtb files). I've got the zip file that you created for me one month ago,here :

https://github.com/quarkscript/linux-armv7-xe303c12-only/files/11615040/5.4.244-kvm.zip

I have decompress it and I've got the zImage file that was stored inside the deb file. Since I want to use u-boot,I have converted zImage into uImage using the following command :

# mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e 0x80008000 -n "Linux kernel" -d zImage uImage

d) EXT4 partition for userspace files. Here I have copied the devuan 4 userland files that I've got here :

https://drive.google.com/u/0/uc?id=1KSgE-3G2GEBzcYhk_JleVYWl6m061GdI&export=download

but I haven't used a btrfs fs,but ext4. And I have extended the space on the partition from 1882M to 200 GB.

2. sudo dd if=nv_uboot-snow.kpart of=/dev/sdX1 (nv_uboot-snow.kpart taken from the vos website)

what happened ? that the chromebook booted and the desktop enviroment also started. Unfortunately mouse and keyboard and trackpad don't work,so I can't check if kvm exists. But I think that there is an high chance that it works. Why keyboard,mouse and trackpad don't work ? maybe that when you have re-compiled your 5.4.244 kernel,you haven't enabled the drivers ? Previously I had configured the SSH server on the Chromebook,but I can't connect to it because it is enabled only when I will able to overcome the login screen. Can you suggest something to try ?

NB : I have enabled the automatic login and I saw :

1. mouse,wi-fi and keypad don't work : I have no connection
2. the screensaver starts after some time,so the OS is not freezed.

How to Add Regular user to (debian ) devuan lxqt ? and change the autologin to it ?

Hello.

I would like to enable KVM on my old but still functional "Samsung Chromebook ARM model XE303C12 SNOW" because later I want to virtualize FreeBSD with qemu and kvm. I've installed the image file "xe303c12_devu_xfce_1882M_btrfs_5.15.79.img.gz" on my cromebook. it works great. Now the challenge is to be able to enable kvm on this kernel. I know that the support for KVM for arm32 has been removed starting from some version of the 5.x branch. And a greater challenge is to be able to make work the patch to put the bootloader in hypervisor mode. So,I would like to know if your image files are enough good to offer what I would like. Is just enough to recompile the kernel that you have used in your "xe303c12_devu_xfce_1882M_btrfs_5.15.79.img.gz" to enable KVM ? I know that a patch to put the bootloader in hyp mode is needed. Did you already patch the bootloader files ? if not,do you know about a tutorial that teaches me how to do that ? I've found this patch that may be appropriated :

https://github.com/sleirsgoevy/exynos-kvm-patch

but I'm not sure if it will work or not. Please shed a light on me. Thanks.

Helllo.

At the end I've been able to boot FreeBSD 13.2 for armv7 as guest OS on my ARM Chromebook using these qemu parameters :

EFICODE=/home/marietto/Dati/Si/AAVMF32_CODE.fd
UEFIVARS=/home/marietto/Dati/Si/AAVMF32_VARS.fd
CD=/home/marietto/Dati/Si/FreeBSD-13.2-RELEASE-arm-armv7-GENERICSD.img
DISK=/home/marietto/Dati/Si/FreeBSD.img

qemu-system-arm \
-enable-kvm -serial stdio \
-m 512 -M virt -cpu cortex-a15 \
-drive if=pflash,format=raw,unit=0,file=$UEFICODE \
-drive if=pflash,format=raw,unit=1,file=$UEFIVARS \
-drive file=$CD,media=disk,format=raw \
-drive file=$DISK,format=raw \
-device i82559er,netdev=net0,mac="52:54:00:12:34:55" \
-netdev tap,ifname=tap0,script=no,id=net0  \
-device virtio-gpu-pci \
-usb -device nec-usb-xhci \
-device usb-kbd -device usb-mouse \
-device vmware-svga,id=video0,vgamem_mb=16

I've recompiled kernel 5.4.244 because I need to create a qemu bridged or tun tapped connection and I realized that in the config file the parameter bridge was disabled (CONFIG_BRIDGE not set) as well as the IP TABLES (CONFIG_NF_TABLES not set). I have also recompiled the kernel modules like follows :

root@devuan:/home/marietto/Dati/No/linux-5.4.244# make modules

no errors

and :

root@devuan:/home/marietto/Dati/No/linux-5.4.244# make modules install


  LD [M]  sound/usb/snd-usbmidi-lib.ko

sh ./arch/arm/boot/install.sh "5.4.244" \

arch/arm/boot/Image System.map "/boot"

run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.4.244 /boot/vmlinuz-5.4.244

run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.4.244 /boot/vmlinuz-5.4.244

update-initramfs: Generating /boot/initrd.img-5.4.244

cryptsetup: ERROR: Couldn't resolve device /dev/root

cryptsetup: WARNING: Couldn't determine root device

run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 5.4.244 /boot/vmlinuz-5.4.244

But mouse,keyboard and trackpad does not work.

Hello my friend.

I'm trying to compile Xen on my ARM Chromebook following this tutorial :

https://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Extensions/Chromebook

I've reached almost on the end of tutorial when I got an error message that I'm not able to fix :

# ls (current directory)

exynos5250-snow.dtb  Gringoli  script  xen.bin  xen-chromebook-image  zImage

nano script :

/dts-v1/;
 / {
   description = "Chrome OS kernel image with one or more FDT blobs";
   #address-cells = <1>;
   images {
     kernel@1 {
       data = /incbin/("xen.bin");
       type = "kernel";
       arch = "arm";
       os = "linux";
       compression = "none";
       load = <0x80200000>;
       entry = <0x80200000>;
     };
     kernel@2 {
       data = /incbin/("zImage");
       type = "kernel_noload";
       arch = "arm";
       os = "linux";
       compression = "none";
       load = <0>;
       entry = <0>;
     };
     fdt@1 {
       description = "exynos5250-snow.dtb";
       data = /incbin/("exynos5250-snow.dtb");
       type = "flat_dt";
       arch = "arm";
       compression = "none";
       hash@1 {
         algo = "sha1";
       };
     };
   };
   configurations {
     default = "conf@1";
     conf@1 {
       kernel = "kernel@1";
       fdt = "fdt@1";
     };
   };
 };


# mkimage -f script xen-chromebook-image

script:6.15-14.8: Warning (unit_address_vs_reg): /images/kernel@1: node has
a unit name, but no reg or ranges property

script:15.15-23.8: Warning (unit_address_vs_reg): /images/kernel@2: node
has a unit name, but no reg or ranges property

script:24.12-33.8: Warning (unit_address_vs_reg): /images/fdt@1: node has a
unit name, but no reg or ranges property

script:30.15-32.10: Warning (unit_address_vs_reg): /images/fdt@1/hash@1:
node has a unit name, but no reg or ranges property

script:37.13-40.8: Warning (unit_address_vs_reg): /configurations/conf@1:
node has a unit name, but no reg or ranges property

Image contains unit addresses @, this will break signing

FIT description: Chrome OS kernel image with one or more FDT blobs
Created:         Sat Oct 28 00:29:40 2023
Image 0 (kernel@1)
 Description:  unavailable
 Created:      Sat Oct 28 00:29:40 2023
 Type:         Kernel Image
 Compression:  uncompressed
 Data Size:    868291 Bytes = 847.94 KiB = 0.83 MiB
 Architecture: ARM
 OS:           Linux
 Load Address: 0x80200000
 Entry Point:  0x80200000
Image 1 (kernel@2)
 Description:  unavailable
 Created:      Sat Oct 28 00:29:40 2023
 Type:         Kernel Image (no loading done)
 Compression:  uncompressed
 Data Size:    2424696 Bytes = 2367.87 KiB = 2.31 MiB
Image 2 (fdt@1)
 Description:  exynos5250-snow.dtb
 Created:      Sat Oct 28 00:29:40 2023
 Type:         Flat Device Tree
 Compression:  uncompressed
 Data Size:    26819 Bytes = 26.19 KiB = 0.03 MiB
 Architecture: ARM
 Hash algo:    sha1
 Hash value:   d1c2a89560f84b6fd1e17d9b8edd45fb9bc5e588
Default Configuration: 'conf@1'
Configuration 0 (conf@1)
 Description:  unavailable
 Kernel:       kernel@1
 FDT:          fdt@1

On ubuntu 23.04 :

# vbutil_kernel --keyblock /usr/share/vboot/devkeys/kernel.keyblock --version 1 --signprivate /usr/share/vboot/devkeys /kernel_data_key.vbprivk --vmlinuz xen-chromebook-image --arch arm --pack signed-xen-chromebook-image

FATAL: do_vbutil_kernel: Missing required config file.

PS : I have tried to remove /incbin/ but it didn't work :

# mkimage -f script xen-chromebook-image

Error: script:7.15-16 syntax error
FATAL ERROR: Unable to parse input tree
mkimage: Can't open xen-chromebook-image.tmp: No such file or directory
Error: Bad parameters for FIT image type
Usage: mkimage [-T type] -l image
         -l ==> list image header information
         -T ==> parse image file as 'type'
         -q ==> quiet
      mkimage [-x] -A arch -O os -T type -C comp -a addr -e ep -n name -d
data_file[:data_file...] image
         -A ==> set architecture to 'arch'
         -O ==> set operating system to 'os'
         -T ==> set image type to 'type'
         -C ==> set compression type 'comp'
         -a ==> set load address to 'addr' (hex)
         -e ==> set entry point to 'ep' (hex)
         -n ==> set image name to 'name'
         -R ==> set second image name to 'name'
         -d ==> use image data from 'datafile'
         -x ==> set XIP (execute in place)
         -s ==> create an image with no data
         -v ==> verbose
      mkimage [-D dtc_options] [-f fit-image.its|-f auto|-F] [-b <dtb> [-b
<dtb>]] [-E] [-B size] [-i <ramdisk.cpio.gz>] fit-image
          <dtb> file is used with -f auto, it may occur multiple times.
         -D => set all options for device tree compiler
         -f => input filename for FIT source
         -i => input filename for ramdisk file
         -E => place data outside of the FIT structure
         -B => align size in hex for FIT structure and header
         -b => append the device tree binary to the FIT
         -t => update the timestamp in the FIT
Signing / verified boot options: [-k keydir] [-K dtb] [ -c <comment>] [-p
addr] [-r] [-N engine]
         -k => set directory containing private keys
         -K => write public keys to this .dtb file
         -g => set key name hint
         -G => use this signing key (in lieu of -k)
         -c => add comment in signature node
         -F => re-sign existing FIT image
         -p => place external data at a static position
         -r => mark keys used as 'required' in dtb
         -N => openssl engine to use for signing
         -o => algorithm to use for signing
      mkimage -V ==> print version information and exit
Use '-T list' to see a list of available image types
Long options are available; read the man page for details

It seems that the validation is enough to bypass the bootloader protection. So,signing the kernel files,I may stop using the virtual open systems patched u-boot and I can use another bootloader , like your.

Hello my friend.

Have you ever seen this error inside the log of your ARM Chromebook model XE303C12 ?

[ 2416.631903] vidioc_try_fmt:379: Unsupported format for destination.
[ 2416.631937] vidioc_try_fmt:379: Unsupported format for destination.
[ 2437.287065] vidioc_g_selection:764: Can not get compose information
[ 2437.294194] vidioc_g_fmt:347: Format could not be read
[ 2437.300364] vidioc_g_selection:764: Can not get compose information
[ 2437.301979] vidioc_g_fmt:347: Format could not be read
[ 2441.711496] vidioc_g_selection:764: Can not get compose information
[ 2441.713115] vidioc_g_fmt:347: Format could not be read
[ 2455.174443] vidioc_g_selection:764: Can not get compose information
[ 2455.175663] vidioc_g_fmt:347: Format could not be read

I'm not sure but they could be correlated with the warnings I get when I try to watch an mp4 file using SMPlayer :

libEGL warning : egl failed to create dri2 screen
libEGL warning : failed to get driver name for fd -1
libEGL warning : MESA-LOADER : failed to retrieve device informations

I'm looking for the technical reason why,when I play an mp4 video with VLC or SMplayer (and for sure other multimedia player),the video proceeds in spurts.

[    3.360507] snow-audio sound: Failed parsing codec node
[    3.374522] snow-audio sound: ASoC: failed to instantiate card -517
[    4.328846] snow-audio sound: ASoC: failed to instantiate card -517
[    4.329318] snow-audio sound: ASoC: failed to instantiate card -517
[    4.331707] snow-audio sound: ASoC: failed to instantiate card -517
[    4.982068] snow-audio sound: ASoC: failed to instantiate card -517

Any help would be appreciated

I am incredibly exhausted, I am a beginner but I think I did exceptionally well for a noob, but this is so hard for me right now. Please help me, I'll list all the things that happened here:
a. Used 3 of your test images (1 archlinuxarm, 1 kali and 1 void). The Kali Linux one performed incredibly amazing in comparison with your archlinuxarm and void linux. Somehow, when I use your test image for archlinuxarm, the arrow cursor keeps blinking (which I have not experienced with your build of Kali Linux).
I am unaware at first of what would happen of certain actions; I tried installing chromium (and performed apt update if I remembered correctly). After a reboot, there was only a beep.

Anyway, I did anything that I could do:
Since I don't have a laptop or pc (I only have my chromebook), I have no idea how to flash your image once again. Did a few searches and I stumbled upon chroot. (Important since I can't extract the zst package using chromeos, or maybe I just don't know how)

So using chroot (and bind mount), and mv command, I finally have the extracted img. With little knowledge from my past experience with linux, I used fdisk /dev/sda and deleted all partitions, made a new one, created a gpt partition table, and formatted using mkfs.vfat (or mkfs.ext4)

I flashed it once again, this time, blocked linux kernel from updating (yet somehow, after trying to install chromium, after a reboot, I still got a beep)

So I scoured through the internet and found out about the kernel issue. Using chroot once again, I tried everything that I can possibly think of but still failed. Frustrated, I tried to use archbk (hey, it's an easy easy script that automates everything)
I used dd once again to flash, all is well not until I tried to boot from it, there is a beep once again!!!
Possibly furious, I searched the net for a mirror of old versions of archarm for chromebook (found one in 2020)). I used it, dd-ed to drive, it worked!!
Although, after populating the keyring and performing pacman -Syu, after a reboot it did not work once again LMAO i'm so mad at this point, but anyway I had no choice, need it to work for my studies (Chrome from official chromeos no longer works with googlemeet and other important websites)

After everything, I found out that the reason why it does not boot is because of the kernel being larger than 8m??
So of course, I tried dd-ing the old archarm image to drive, and performed
"pacman -S uboot-tools vboot-utils dtc" in preparation with the solution I found on an archarm thread.
And since I can't access archarm once again, I opted to use chroot only to find out that it returns this error:

sudo mount /dev/sda2 /mnt

mount: /mnt: wrong fs type, bad partition, bad superblock on /dev/sda2, missing codepage or helper program, or other error

Not trying to give up, I flashed the old archarm on another drive and now after trying to chroot, I received this error:

mount: /mnt: unknown filesystem type 'btrfs'

This is truly depressing. I give up, only you can help me.
If you can, please update the kali testimage please, one where I can just install chromium. If not, help me how to deal with this issue. I had several sleepless nights (and bandwidth lost because I used mobile data) just to figure out how to breath new life in my device.
My exams are next week, and the chromebook's my best option for studying.

Hello.

The project that I've been working on since 2 years is to enable KVM (with the support of libvirt and virt-manager) on a recent version of Linux and of its kernel on the old but still nice ARM Chromebook model xe303c12. My goal is to virtualize FreeBSD 13.2 for armV7. I've almost completed the project. At today I'm using Ubuntu 22.04 (but it works also with Devuan 5) ; KVM is enabled ; libvirt 9.7.0 and virt-manager are working great. And I've almost been able to virtualize FreeBSD. Almost because I've found a problem that I need to fix or the whole project will die. Ubuntu recognizes only 1 GB of memory free,but the ARM Chromebook has 2 GB of memory soldered to the mobo. So,1 GB of memory has been lost during the transition from the first project I tried to enable KVM with an old kernel (and ubuntu) version,that you can find here :

http://www.virtualopensystems.com/en/solutions/guides/kvm-on-chromebook/#setting-up-the-boot-medium

and my project,that uses a more recent kernel version (5.4) and ubuntu version (22.04). I think that when I have recompiled the kernel,I've lost some kernel entries that are enabled on the 3.13 kernel used by the developers at the Virtual Open System. Well,I have no idea about which entries my kernel config are missing.

I have checked the available memory for the OS giving the command :

# free -m

If I don't recover 1 GB of memory,I can't virtualize FreeBSD,because only 1 GB is a very small amount of memory to be able to run the host and the guest OS.

So,can you help me to find which kernel entries I should add to have all the 2 GB of memory available ?

Virtual Open System offers it's own kernel config file,that I have saved here :

https://pastebin.ubuntu.com/p/j4B54TChKD/

using their kernel config file I see that I have a total of 2 GB of memory available (I spend 400 mb to load Linux,so only 600 remains ; it's not good. In Fact I get a lot of qemu crashes), but If I use my config file the OS starts with only 1 GB.

Hello.

my ARM Chromebook SNOW model has the mmc slot broken,but I've realized that I can boot Linux using the USB port ! To enable the booting of Linux via USB I have modifed this file :

https://github.com/virtualopensystems/u-boot/blob/eecfeb578e296ef3b739ac918a39b6c177dff58a/include/configs/snow.h#L101

in this way :

/*
 * Copyright (C) 2013 - Virtual Open Systems
 * Author: Nikolay Nikolaev <[email protected]>
 *
 * This program is free software; you can redistribute it and/or modify
 * it under the terms of the GNU General Public License, version 2, as
 * published by the Free Software Foundation.
 *
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 * GNU General Public License for more details.
 *
 * You should have received a copy of the GNU General Public License
 * along with this program; if not, write to the Free Software
 * Foundation, 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA.
 */

#ifndef __configs_snow_h__
#define __configs_snow_h__

#include <configs/smdk5250.h>

#undef CONFIG_DEFAULT_DEVICE_TREE
#define CONFIG_DEFAULT_DEVICE_TREE      exynos5250-snow

/* Generally verified boot needs more heap space */
#undef CONFIG_SYS_MALLOC_LEN
#define CONFIG_SYS_MALLOC_LEN	(32 << 20)

#define CONFIG_INITRD_ADDRESS 0x44000000

#include <configs/chromeos.h>

/* Disable ChromeOS specifics */
#undef CONFIG_CHROMEOS

/* Force reading the environment */
#undef CONFIG_OF_LOAD_ENVIRONMENT

#define CONFIG_CHROMEOS_USB

/* Support vboot flag reading from GPIO hardwrae */
#define CONFIG_CHROMEOS_GPIO_FLAG

/* Support vboot flag reading from EC */
#define CONFIG_CHROMEOS_MKBP_FLAG

/* Use the default arch_phys_memset implementation */
#define CONFIG_PHYSMEM

/* Adjust the display resolution. */
#undef MAIN_VRESOL_VAL
#undef MAIN_HRESOL_VAL
#define MAIN_VRESOL_VAL 0x300
#define MAIN_HRESOL_VAL 0x556
#undef LCD_XRES
#undef LCD_YRES
#define LCD_XRES 1366
#define LCD_YRES 768
#define CONFIG_SYS_WHITE_ON_BLACK

/*
 * Extra bootargs used for direct booting, but not for vboot.
 * - console of the board
 * - debug and earlyprintk: easier to debug; they could be removed later
 */
#define CONFIG_DIRECT_BOOTARGS \
	"console=tty1 debug clk_ignore_unused"

/* Standard input, output and error device of U-Boot console. */
#define CONFIG_STD_DEVICES_SETTINGS 	EXYNOS_DEVICE_SETTINGS

#define CONFIG_CHROMEOS_SD_TO_SPI \
	"sd_to_spi=echo Flashing U-Boot from SD card to SPI flash; " \
	"if mmc dev 1 && " \
	"mmc rescan && " \
	"mmc read 40008000 1 1000 && " \
	"sf probe 1:0 && " \
	"sf update 40008000 0 80000; then " \
	"echo Flash completed; else " \
	"echo Flash failed; " \
	"fi\0"

/* Replace default CONFIG_EXTRA_ENV_SETTINGS */
#ifdef CONFIG_EXTRA_ENV_SETTINGS
#undef CONFIG_EXTRA_ENV_SETTINGS
#endif
#define CONFIG_EXTRA_ENV_SETTINGS \
	EXYNOS_DEVICE_SETTINGS \
	"dtaddr=0x43000000\0"\
	"initrdaddr=0x44000000\0"\
	"boot_noinitrd=usb start ; usb dev 0 ; ext2load usb 0:2 ${loadaddr} uImage ; ext2load usb 0:2 ${dtaddr} exynos5250-snow.dtb ; bootm ${loadaddr} - ${dtaddr}\0"\
	"boot_initrd=usb start ; usb dev 0 ; ext2load usb 0:2 ${loadaddr} uImage ; ext2load usb 0:2 ${initrdaddr} initrd ; ext2load usb 0:2 ${dtaddr} exynos5250-snow.dtb ; bootm ${loadaddr} ${initrdaddr} ${dtaddr}\0"\
	"bootdelay=10\0"

#ifdef CONFIG_BOOTARGS
#undef CONFIG_BOOTARGS
#endif
#define CONFIG_BOOTARGS \
	"console=tty1 root=/dev/da0p4 rw rootwait clk_ignore_unused --no-log"

/* Replace default CONFIG_BOOTCOMMAND */
#ifdef CONFIG_BOOTCOMMAND
#undef CONFIG_BOOTCOMMAND
#endif
#define CONFIG_BOOTCOMMAND \
	"run boot_noinitrd"

/* Enable splash screens */
#define CONFIG_CROS_SPLASH

/* Enable simple framebuffer */
#define CONFIG_SIMPLEFB

/* Enable writing on a FAT formatted filesystem */
#define CONFIG_FAT_WRITE

/* Enable virt mode commands */
#define CONFIG_ARMV7_VIRT

/* Disable d-cache */
#define CONFIG_SYS_DCACHE_OFF

#endif /* __configs_snow_h__ */

I have modified mmc with usb 0 and I've changed the timeout from "bootdelay=3\0" to "bootdelay=10\0" and I ran the script that located here :

https://github.com/virtualopensystems/u-boot/blob/eecfeb578e296ef3b739ac918a39b6c177dff58a/scripts/build.sh

that creates a new : nv_uboot-snow-usb.kpart file,that I install on the sd card where I have installed Linux,using the following commands :

# dd if=/dev/zero of=/dev/sdi1
dd: writing to '/dev/sdi1': No space left on device
32769+0 records in
32768+0 records out
16777216 bytes (17 MB, 16 MiB) copied, 2.07775 s, 8.1 MB/s

# sudo dd if=nv_uboot-snow-usb.kpart of=/dev/sdi1

at this point I attach the usb to sd card converter on the Chromebook and I try to boot Linux,but with my surprise I see that the bootloader is still set to 3 seconds. It means that for some reason,the new nv_uboot-snow-usb.kpart is not detected,because when I have recompiled it,I have chosen 10 seconds of timeout for u-boot. I really don't have idea of the reasons why the new settings aren't applied.

Install sosumi replace common and find the code
https://files.fm/u/82zpbg9yc
https://uptobox.com/f9ugkg0vim8e
common2_7_EB_common_snap_sosumi_digital_god_and_jan_sloot_script_as_dvd_drive.tar.gz

Hi!

I really like the project you have going for the XE303C12 here. I'm excited to see where this project goes and I think it's truly a great project.

I was wondering on how everything was pulled off (including hardware acceleration) the older XE303C12 ChromeBooks under Arch and Void Linux because I'd like to attempt to implement/replicate the same thing for my XE503C12 ChromeBook and hopefully also achieve hardware acceleration with the Mali GPU (its GPU is a Mali T628 MP6).

Currently at the time of writing, hardware acceleration on Peach-Pit is not very heard of at all. I'm not requesting added support for the XE503C12 since your project clearly states that it is for the XE303C12 only, but any information on how to do the same for the XE503C12 would be greatly appreciated.

Thanks and I hope you have a great day! -Nathan

blackarcharm

While tray to install it from repo i can't get it to work its a issuse from distro or from repo ?
Seems like pacman not accept gpg. Uncomment of mirrors not help any advice ?

Hello to everyone.

I've installed ubuntu 14.04 + kernel 3.13 + kvm on my Samsung Chromebook ARM "SNOW" model XE303C12. Almost everything works (but not the mouse usb). My goal is to upgrade ubuntu (kernel and userland and I want keep enabled kvm). So,I've got a new kernel sources from this link :

https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.4.244.tar.xz

I have unpacked it and I've added at the bottom of the .config file these lines :

CONFIG_HAVE_KVM_IRQCHIP=y
CONFIG_KVM_MMIO=y
CONFIG_HAVE_KVM_CPU_RELAX_INTERCEPT=y
CONFIG_VIRTUALIZATION=y
CONFIG_KVM=y
CONFIG_KVM_ARM_HOST=y
CONFIG_KVM_ARM_MAX_VCPUS=2
CONFIG_KVM_ARM_VGIC=y
CONFIG_KVM_ARM_TIMER=y

I tried to add those lines directly on the .config file editing the file with nano because as soon as I have wrote "make menuconfig",I saw that the KVM entries weren't there,as you can see :

https://ibb.co/WcXPTj5

unfortunately those lines don't stick on the kernel config file. When I save it and I reopen it,I see that the kvm lines have been deleted. (I'm trying to compile the 5.4 kernel directly on the chromebook using an SSH connection). As a second attempt I've used the kernel config file offered by virtual open systems on their guide here :

http://www.virtualopensystems.com/en/solutions/guides/kvm-on-chromebook/

I've added the kvm entries (this time they stuck) and then I tried to recompile it with the command :

ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- make uImage dtbs -j2

and also :

make uImage dtbs -j2

but this is what happened :

root@marietto-Z87-HD3:/home/ziomario/Desktop/linux-5.4.244# ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- make uImage dtbs -j4

scripts/kconfig/conf  --syncconfig Kconfig
  CC      scripts/mod/empty.o
  CC      scripts/mod/devicetable-offsets.s
  MKELF   scripts/mod/elfconfig.h
  HOSTCC  scripts/mod/modpost.o
  HOSTCC  scripts/mod/sumversion.o
  HOSTCC  scripts/mod/file2alias.o
  HOSTLD  scripts/mod/modpost
  CC      kernel/bounds.s
  CALL    scripts/atomic/check-atomics.sh
  CC      arch/arm/kernel/asm-offsets.s
arch/arm/kernel/asm-offsets.c:45:2: error: #error Your compiler is too buggy; it is known to miscompile kernels
 #error Your compiler is too buggy; it is known to miscompile kernels
  ^
arch/arm/kernel/asm-offsets.c:46:2: error: #error and result in filesystem corruption and oopses.
 #error and result in filesystem corruption and oopses.
  ^
make[2]: *** [arch/arm/kernel/asm-offsets.s] Error 1
make[1]: *** [prepare0] Error 2
make: *** [sub-make] Error 2

what you suggest me to do ? thanks.

This is the compiler that I'm using :

gcc --version
gcc (Ubuntu/Linaro 4.8.2-19ubuntu1) 4.8.2 

What is the default password from the test images?

For root and tester username?

Hello.

I'm trying to boot FreeBSD for arm32 bit as DomU on my ARM Chromebook SNOW with xen. Basically there are two ways to accomplish this task :

1. write a patch that allows the FreeBSD kernel to boot as a zImage file. This could be accomplished applying this patch to a specific file that's on the source code of FreeBSD :

https://xenbits.xen.org/gitweb/?p=p...8;hb=0782e25d98cc1391472717035f986c979edef0c9

This patch was written by Julien Grall a lot of time ago and now it does not work anymore. This is the reason explain by the xen developers :

It appears FreeBSD-CURRENT removed the last step converting the kernel file to kernel.bin.
The patch can be readily rebased, but without kernel.bin that doesn't do too much.
So,without a rebase of that patch the first option is not applicable. And I'm not able to fix it.

2. booting FreeBSD using U-Boot,as explained to me by a xen developer :

I was trying to explain why and how Julien's patch works so that you could be the one to re-do
something similar or fix the patch on the FreeBSD kernel that you are working with.
I am happy to help review and write patches but I don't work with the FreeBSD kernel so I wouldn't
be able to help you quickly. However, I might have a suggestion. Do you know if FreeBSD can be booted by U-Boot ? Because U-Boot definitely boots as Xen on ARM guest firmware/bootloader.
You should be able to build U-Boot and use the U-Boot binary as Xen guest kernel,
then U-Boot could load FreeBSD from disk or network and start it. For instance as domU config file:

kernel="/home/petalinux/u-boot.bin"
disk = [ '/home/petalinux/test.img,raw,xvda' ]

Actually I'm working on the idea n. 2. Basically I need to find the proper u-boot file that's able to boot the image of FreeBSD that I have installed (13.2 for arm32 bit). Maybe I found it here :

http://commondatastorage.googleapis.com/chromeos-localmirror/distfiles/nv_uboot-snow-simplefb.kpart.bz2

I found that link inside this tutorial :

https://wiki.freebsd.org/arm/Chromebook

the version of u-boot that has been embedded in that file is the following one :

# strings nv_uboot-snow-simplefb.kpart | grep U-Boot 
U-Boot 2011.12-gc1f6280 (May 27 2013 - 15:06:59) for SMDK5250

So the question is easy : I need to find the source code of that old version of u-boot,because once compiled,it will give to me the proper u-boot.bin kernel / bootloader file that maybe will be able to boot FreeBSD.

Width the new kernel 5.10.3-3
After full migration of system to usb (3.0) but plugged in (2.0) external usb stick can't boot agin. So far I remember width some older kernels it was able to migrate everywhere where you wonted and it was working. This kernel width virtio drivers plase upload it I can't extract it width last kernel, if you have it already.

This usb 3.0 for boot still impossible?
Thanks for possibility to install linux on this device, so farr i wonder how stable it is bulided from you.

Arch console -works
Void X -works
Arch test disk 3 "X" -works

Arch and Kali versions "X" are unbootable from usb
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

qemu script error on (Mac)
qemu-system-arm: could not load kernel 'zImage'

Why we don't go to arm 64 for long term ?

https://www.raspberrypi.com/news/raspberry-pi-os-64-bit/

Hi, I am testing the arch Linux xfce image and my touchpad does not work at all.

Any help would be nice.

My xe303c12 can boot any of your images. I noticed that the partitions both are chrome partitions. I have also tried multiple other builds from other projects. I can't boot any of them. Are there different XE303C12's? SNOW CLEAR A-I 3922 is the model. Other images (that don't work) have a chrome partition then ext4. The ones that don't boot just beep when I press CTRL-U.

Hello.

How to increase the space on the sd card formatted with btrfs.

What a tarball is used on xe303c12 of void linux from arm section ?
In xbps pakage in aur are missing metadata and can't be installed. Meanwhile i test kali.

vmlinux.kpart from last compiled kernel linux_xe303c12-5.10.13_1.armv7l.xbps on /dev/mmcblk1p1 with dd
void-armv7l-ROOTFS-20191109.tar.xz extracted with tar -xvf on mounted (ext4) /dev/mmcblk1p2
and i can't boot, get black screen (no beep signal)

This is not exactly an issue but can you please document or teach me how to use this? I have the same device but I can't get other os to boot.

I tried lots of stuff already like aok from https://github.com/cubetronic/aok/releases/tag/v0.7.1-beta which gives some error about not having enough space even though I do have space. I also tried archbk from https://github.com/altreact/archbk, i installed archarm on my thumb drive but it just beeps when I press ctrl u and does nothing. Ctrl D returns me to chromeos

And then I stumbled here, finding the same exact device (i even watched a clip from yt showing archarm running on my device with a comment by quarkscript (possibly you))

Please help me, i am a complete beginner, I tried linux distros before like manjaro, ubuntu, fedora but not on arm, i have no idea what to do

Hello.

on my last experiment I've switched from Devuan 4 to Debian bookworm (I've got the image file here : https://github.com/hexdump0815/imagebuilder/releases/download/230220-01/chromebook_snow-armv7l-bookworm.img.gz) . I'm using it right now,but I see some huge errors that are destroying my system files reboot after reboot,because they are produced at a regular intervals :

[   10.480204] mwifiex_sdio mmc2:0001:1: info: FW download over, size 533976 bytes
[   10.719132] mwifiex_sdio mmc2:0001:1: WLAN FW is active
[   10.719369] Bluetooth: vendor=0x2df, device=0x912a, class=255, fn=2
[   11.089624] btmrvl_sdio mmc2:0001:2: sdio device tree data not available
[   11.091551] mwifiex_sdio mmc2:0001:1: CMD_RESP: cmd 0x242 error, result=0x2
[   11.091563] mwifiex_sdio mmc2:0001:1: mwifiex_process_cmdresp: cmd 0x242 failed during initialization
[   11.133736] mwifiex_sdio mmc2:0001:1: info: MWIFIEX VERSION: mwifiex 1.0 (14.68.29.p59) 
[   11.135281] mwifiex_sdio mmc2:0001:1: driver_version = mwifiex 1.0 (14.68.29.p59) 
[   12.914015] NET: Registered protocol family 38
[   19.058217] mwifiex_sdio mmc2:0001:1: info: trying to associate to 'ziomario' bssid 
[   19.093260] mwifiex_sdio mmc2:0001:1: info: associated to bssid  successfully
[   19.116924] mwifiex_sdio mmc2:0001:1: CMD_RESP: cmd 0x23f error, result=0x2
[   19.129679] IPv6: ADDRCONF(NETDEV_CHANGE): mlan0: link becomes ready
[   19.134791] mwifiex_sdio mmc2:0001:1: CMD_RESP: cmd 0x23f error, result=0x2
[   31.849443] TPS65090_RAILSDCDC1: disabling
[   31.858024] TPS65090_RAILSDCDC2: disabling
[   31.868245] TPS65090_RAILSDCDC3: disabling
[   31.878250] TPS65090_RAILSLDO1: disabling
[   31.887352] TPS65090_RAILSLDO2: disabling
[  115.862293] mwifiex_sdio mmc2:0001:1: CMD_RESP: cmd 0x23f error, result=0x2

how can I fix it ? If I don't get wrong,it is the wireless driver that has been added to the system that's causing the problem,right ? or maybe it is incompatible with the Debian 12 ? let me know please. I don't want to return to Devuan because libvirt is easier to configure on Debian. But take in consideration that those errors don't happen on Devuan.

Hello my friend.

I've almost completed my project : to virtualize FreeBSD on top of Linux with qemu-kvm on the ARM Chromebook. Everything works great. Even the network on the vm. One last task needs to be accomplished. To be able to use the panfrost graphic driver on the linux distro that I have chosen and where I have configured everything : Devuan 5. I would like to understand what's the fulll procedure to enable the MALI driver and to make it work. What I did right now is to enable the MALI driver inside the kernel that I'm using (vers. 5.4.257).

The only parameter that I've found on the kernel config file related to MALI is the following :

CONFIG_DRM_MALI_DISPLAY=y

and I set it to y. Until here it was easy. What I don't understand is after enabling that parameter,it will work automatically or if I should make an additional configuration and which kind of configuration it needs. Thanks.