imagebuilder
imagebuilder copied to clipboard
hexdump0815
misc: all good - i'm happy :)
this issue is here in case someone wants to leave a comment when everything with an image is working well, so there would be no other reason for opening an issue here :) ... maybe some info about the system/image used would be interesting too
All good, boots just fine from a microSD card. (firmware v 2.10.4). Thanks!
Update: so far the best build of headless Linux image out there. Everything working out-of-the box. Even got this https://github.com/eswincomputing/eswin_6600u running without having to build it myself. Again, many thanks! You made my day easier :-)
Hi @hexdump0815, I initially became aware of your work when I was searching for a way to make music using a raspberry pi zero. I had dabbled a little in pure data and supercollider and build a MeeBlip synthesizer, but I learned about VCV Rack and it didn't run on my netbook. I built VCV Rack using your scripts and I only remember that it took forever to build on the raspberry pi itself. Traded the Raspberry Pi for a Nokia N900 somewhere afterwards and fell in love with SunVox. I tried to install mainline Debian with some success, always returned back to stock to make phone calls. weird flash formats, missing GPU/DRM support and the lack of a stable internet connection were also discouraging. Changed from the N900 to a Sony Xperia, ostensibly to use Sailfish OS. Didn't even install LineageOS after actually using the device.
When I saw the announcement regarding mainline support for powervr I bought a Lenovo Yoga N23 Chromebook (hana). I had tried a few times to boot debian with the chromeos kernel as outlined here for example: https://elinux.org/User:Uli/Acer_Chromebook_R13_GPU_test_system There are other bits of information that helped me familiarize myself with bootable images for chromeos devices, even if they don't look like success stories: https://gitlab.tails.boum.org/tails/blueprints/-/wikis/ARM_platforms/Acer_Chromebook_R_13_CB5-312T/ The A/B kernel partitions and immutable root remind me of Fedora Silverblue, right now, Fedora doesn't really feel at home on MediaTek cbs: https://fedoraproject.org/wiki/Architectures/ARM/Chromebook
Your builds for hana are the most viable option to test the current mainline status before committing to turning off the beep with a suzyqable and installing to EMMC. I've run Renoise and SunVox after setting up JACK2 with you scripts and recorded electronic jam sessions with OBS Studio, Reaper and the Sony mentioned earlier as network camera.
Until we see some mainline work from IMG regarding the GPU and google is still offering updates, I don't mind that external displays are not working yet. I imagine the work to support external displays via USB-C/HDMI depends a lot on the DRM kernel driver, so I bought a Tanix TX6S to learn a little about that.
From your notes I thought my hassel would be to get panfrost working, but it seems I got a different hardware revision as you suggested here: https://github.com/hexdump0815/imagebuilder/issues/130#issuecomment-1472493061 If I had seen that earlier, I might have chosen a model with an H6 processor instead - hate to open a new device to add UART, but after the experience with the chromeos and maemo this is still worth the trouble. I'll also test the MiniArch and MiniMyth builds, to see if a patch arrives there early. For the H616 TV Box, I might want to build a minimal image using your scripts to run a media sever: https://wiki.debian.org/FreedomBox/Hardware/Debian
Once I have checked all troubleshooting resources that are available, I will start leaving some notes and try my luck to make my own builds. I wonder if I could build Ubuntu Focal still, now that UBports finally moved to that Ubuntu version, there might be some interesting things to try. Haven't really seen LoMiri run on 2-in-1 devices yet. Firmware blobs from ChromeOS or Android are meant for 32-bit rootfs in both of my devices and I didn't see anyone in the comments here try what's written on elinux.
At the end, I wanted to share a magazine that has been a source of inspiration for my journey with linux on ARM devices: https://solar.lowtechmagazine.com/2018/09/how-to-build-a-lowtech-website.html
Thanks to your work, I am able to use some low-powered consumer devices as development and education tools. I hope to see support for the MT81xx with a legacy desktop distro such as MX Linux or Ubuntu Mate to be the fruition of work done here. Compared to the first 32-bit armhf chromebooks, the mt8173 can be found in a number of education editions which I expect to be around for at least as long as that darn T430 and last 8 hours a charge with the usage outlined in your daily driver doc.
One day, I needed a budget Chromebook. I found one on sale on a trusted online marketplace in India. Since the price was so good, I forgot to check for Linux support. When I wanted Linux, I only found guides for x86. So, I dived a little bit deeper and found your awesome repo. I tried Cadmium but there was no support for kappa. Your image worked without sound, so I raised an issue. Thanks to your quick response, I was able to know that you got sound working and you were going to release an image with sound support soon. One suggestion though. It would be nice if we had Arch Linux or Fedora support. The only true mainline Linux alternative for kappa is postmarketOS, which has no Bluetooth support. Recently, under load the freezing problem was fixed with the 6.0+ kernels. Now the images could be used better. I am running Debian since Ubuntu feels a little bloated, I am more used to Debian, and there is a graphical glitch with Wayland. Thank you for making a streamlined process to run Linux on ARM Chromebooks.
Thanks, Aneesh (Link to my website)
Seems to be working okay on my hana Lenovo 100e Chromebook 2nd Gen MTK, booting from eMMC. Looking for more information for Linux on my SoC, seems to be uncommon I can get Arch Linux Arm working too, but not as well as your images
Just to say Thank You for this project :-) And all the useful notes. Pleased to report your 230220-03 build booted fine first time from μSD on my gru/kevin Samsung Chromebook Plus.
Despite it being slightly underpowered, I've been running native Linux (SuSE Leap 15.x) on this cute laptop for 5 years now, with help from this Arch Linux build, but have not had any luck booting more recent kernels than 4.4.159. It's great to finally have Mali GPU support.
(I've started playing with Rockchip RK3588 hardware, and looking forward to seeing its much faster performance in a laptop..)
Anyway, please keep up the good work !
Hello Hexdump0815,
Thanks for the great work. I have gotten Arch Linux, Fedora, and OpenSuse on kappa to run by copying the new kernel files for mt81xx from your repo (6.1.11). I also made a good fstab. But, the system boots up in read-only mode and everything fails. I also tried a few non-systemd distros like Artix and Void, but there is still a problem. Any solution to get this working? Would love to have Fedora on this! If this is possible, we could have more distros.
Thanks, Aneesh
@aneeshlingala - i have no idea what might cause the readonly system - it could be that those systems rely on an initrd/initramfs to work properly and by default the kernel packages are not using innitrd/initramfs
I have removed the default kernel packages by chrooting into the system. What do mean by "those systems rely on an initrd/initramfs to work properly?"
On Sat, May 13, 2023 at 6:44 AM hexdump0815 @.***> wrote:
@aneeshlingala https://github.com/aneeshlingala - i have no idea what might cause the readonly system - it could be that those systems rely on an initrd/initramfs to work properly and by default the kernel packages are not using innitrd/initramfs
— Reply to this email directly, view it on GitHub https://github.com/hexdump0815/imagebuilder/issues/141#issuecomment-1546546068, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUYUBPCKSM4GJSHFMWARYG3XF4UWXANCNFSM6AAAAAAWDLBQYA . You are receiving this because you were mentioned.Message ID: @.***>
some things require an initial ram disk (initrd/initramfs) to work like for instance encryption of the rootfs via luks - i have no idea how those other distributions work, but maybe they also require such an initial ram disk for doing some stuff before the rootfs is mounted - i have no real idea, as i do not know those others dists in detail
I have gotten the init scripts from a non-systemd distro and implanted it into the initramfs. Still didn't work.
On Sat, 13 May 2023, 22:43 hexdump0815, @.***> wrote:
some things require an initial ram disk (initrd/initramfs) to work like for instance encryption of the rootfs via luks - i have no idea how those other distributions work, but maybe they also require such an initial ram disk for doing some stuff before the rootfs is mounted - i have no real idea, as i do not know those others dists in detail
— Reply to this email directly, view it on GitHub https://github.com/hexdump0815/imagebuilder/issues/141#issuecomment-1546813459, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUYUBPDPKUDJXX4WLOJ4L43XGBWHPANCNFSM6AAAAAAWDLBQYA . You are receiving this because you were mentioned.Message ID: @.***>
Installed on HP 14G3 TEGRA K1, with u-boot for nyan blaze 2GB ram on a 32GB microSD card. Everything is working OK, sound need a little configuration from alsamixer, enabling DAC for speakers, left and right. Hdmi is working OK too. Much more faster compared with Postmarket OS. Upgraded to Debian12. If you choose keyboard layout for chromebook, from settings, a part of dedicated key's are activated.Thank you for your great work ! The single limitation is due to 32 bit architecture, but that's another discussion!! Thank you again !!
You are a machine. Booted image off of USB and installed to internal with BT/WiFi/Trackpad/etc. working out the gate. Genius fr. (ASUS C201PA)
Hello! Thx you for your job! Device: Acer CB311-11H (kenzo), don't work touchpad. Tested in Deban and Ubuntu. Other things seems work fine (sound, wifi-bt, touchscreen, etc). Trying this image https://github.com/hexdump0815/imagebuilder/releases/tag/230218-01
@slfdstrctn - thanks for the feedback and report - do you see anything touchpad related in dmesg? (mostly its i2c related stuff usually)
@hexdump0815
Here dmesg logs: [ 0.817478] i2c_dev: i2c /dev entries driver [ 0.928814] mediatek-dpi 14015000.dpi: Found bridge node: /soc/i2c@1100f000/it6505dptx@5c [ 15.297135] elants_i2c 0-0010: supply vcc33 not found, using dummy regulator [ 15.301754] elants_i2c 0-0010: supply vccio not found, using dummy regulator [ 15.404140] elan_i2c 2-0015: supply vcc not found, using dummy regulator [ 15.450020] input: Elan Touchscreen as /devices/platform/soc/11007000.i2c/i2c-0/0-0010/input/input7 [ 15.530407] elan_i2c 2-0015: reading cmd (0x0102) fail. [ 15.532912] elan_i2c 2-0015: failed to get FW version: -6 [ 15.568174] i2c_hid_of 2-002c: supply vdd not found, using dummy regulator [ 15.577482] i2c_hid_of 2-002c: supply vddl not found, using dummy regulator
Genius! Thanks for this! - I got it working fine off a usb and was able to use a usb dongle with a network cable - but how do you access the internal ssd drive? At least I think it is - cracked it open and it looks like its on the main board
You are a machine. Booted image off of USB and installed to internal with BT/WiFi/Trackpad/etc. working out the gate. Genius fr. (ASUS C201PA)
How were you able to install to internal drive?
the internal emmc appears just as another /dev/mmcblk device like an sd card ... it is indeed soldered on the mainboard on all arm chromebooks
@slfdstrctn - i have no real idea yet about your touchpad problem - something similar was the case with cozmo as well and with some kernel version it started to work then - maybe trying to build a v6.4 kernel might work better ... i have adjusted my kernel compile info for kukui recently to v6.4 so that it compiles, but i did not yet get to testing if the resulting kernel will work (but i guess it should do) - see: https://github.com/hexdump0815/linux-mainline-mediatek-mt81xx-kernel/blob/master/readme.mt8 ... some generic info about building your own kernel: https://github.com/hexdump0815/imagebuilder/blob/main/doc/building-own-kernels.md
the internal emmc appears just as another /dev/mmcblk device like an sd card ... it is indeed soldered on the mainboard on all arm chromebooks
Thanks for the reply - I don't show any such devices - this is a samsung galaxy book pro wifi
cat /proc/partitions only shows the usb drives ( I have an extra on the dongle)
parted --list also only shows the usb drives as does lsblk -f
Any suggestions?
@bserret - i assume this is an intel chromebook then? in that case it should have either emmc as well (appearing as mmcblk) or an nvme ssd (which should not be soldered on) ... are there any mmc, sd, nvme related messages in dmesg?
@slfdstrctn - i have no real idea yet about your touchpad problem - something similar was the case with cozmo as well and with some kernel version it started to work then - maybe trying to build a v6.4 kernel might work better ... i have adjusted my kernel compile info for kukui recently to v6.4 so that it compiles, but i did not yet get to testing if the resulting kernel will work (but i guess it should do) - see: https://github.com/hexdump0815/linux-mainline-mediatek-mt81xx-kernel/blob/master/readme.mt8 ... some generic info about building your own kernel: https://github.com/hexdump0815/imagebuilder/blob/main/doc/building-own-kernels.md
thx for replay, i'll try.
Got an openSUSE Leap 15.5 aarch64 rootfs to boot and run successfully on my gru/kevin Samsung Chromebook Plus using hexdump0815's /boot and kernel. Did a number of things to make this work:
- re-did mkfs on the root and /boot partitions (needed to re-size them anyway) in the 6.1.11-stb-cbg+ install image
- copied /lib/modules/ and /lib/firmware/ from the 6.1.11-stb-cbg+ root partition to the target rootfs
- copied all the files from the /boot directory on the SuSE rootfs to the /boot partition
- restored all the /boot files from the 6.1.11-stb-cbg+ install image
- adjusted /etc/fstab on the target rootfs accordingly
I saw the read-only FS problem, but only on the ext4 /boot partition (not the btrfs root), which seemed to have some ext4fs features the SuSE rootfs did not like. Not sure if all the above steps were necessary to get things running, but they appear to be sufficient. Looks like the Leap 15.5 Mesa Panfrost Mali GPU userland support plays nice with the 6.1.11-stb-cbg+ kernel (though some geometry weirdness going dual-head display).
This is of course a very hacky way of doing things compared to getting the imagebuilder stuff to run properly in SuSE, but it at least gets me up and running..
My ODROID-X is finally useful again! Successfully installed the 230224-05 image to my 16GB eMMC module and so far everything appears to be functioning. Will be updating my X2 and U3 devices next.
I remember almost two years ago trying to run Linux on my Peach Pit ChromeBook, trying to get GPU acceleration on it. I didn't know very much about Linux and this is where my inspiration started and thus, my Linux journey truly began. From hardly knowing how to setup a Linux environment to build a functioning kernel to now basically being able to build Linux kernels blindfolded. With my newly learned skills do I hope to effectively and positively contribute back to the very project that helped me reach the inspiration to learn more about Linux in-depth (and Linux on ARM). You do fantastic work HexDump, God bless.
The kukui 230218-01 bookworm image is working great on lenovo 10e (kodama sku288); hw probe, running from usb
There's a quirk to enable dev mode on this model: the internal screen is not initially enabled; to work around, hold down vol buttons and power on, letting go of the buttons after 5s, then press both volume buttons once, then press vol up ten (10) times, then power, then wait 5s; the screen will turn on and you will be at the dev mode menu with os verification disabled, and you can proceed with the rest of the instructions as usual booting from internal drive for the dev mode wipe. Subsequent regular boots will show the dev mode menu and turn the screen on automatically.
(This workaround courtesy of reddit; even the hardware maintenance manual for this model's recovery instructions didn't account for it.)
Also maybe I missed this in the docs somewhere but after writing the usb with dd you have to open gparted or similar and have it fix the problem with the gpt being not right for the size of disk that it will complain about, otherwise the resulting usb boot will complain about not being able to find the kernel
Working:
sound, video, touchscreen, usi stylus, usb, bt/wifi, battery, 2x thermal sensors, chromium reports graphics accel and video decode.
Notes:
- Using dropdowns with the touch screen is difficult as click-and-hold selection doesn't work and click-to-open only works a small percent of the time; idk if this is normal for xfce. a connected mouse works fine
- The sound setup is a bit flaky, where sound plays through the speakers when the speakers are not selected in pulseaudio mixer; just switching the output to speakers and back fixes the problem
- Rotating the display in xfce doesn't rotate the touchscreen or stylus input, but you can manually apply a
Coordinate Transformation Matrixto thehid-over-i2c 04F3:2AC1devices usingxinputto get them rotated; I presume this is normal for xfce - Very occasionally the system will randomly freeze, with a black screen locally and no response over the network, and 10 s power button power off required
@rakslice - thanks a lot for the report and the details about getting it working - i marked kodama as tested now too - https://github.com/hexdump0815/imagebuilder/commit/486175f026b64cbdf34de5f7c0bd264071601cc9 ... the images are not ready yet for proper touch operation (they are just prepared for basic operation in case no keyboard is around or detected) and i think xfce is not the best choice for that right now - i guess gnome or kde are most probably better prepared for that and even then some extra work for automatic screen rotation etc. will most probably be required
@RaylynnKnight My ODROID-X is finally useful again! Successfully installed the 230224-05 image to my 16GB eMMC module and so far everything appears to be functioning. Will be updating my X2 and U3 devices next.
Just for the report: my Odroid U3 works flawlessly with the same image, well done hexdump :)
@rakslice You have to update the kernel to fix freezing issue. Hexdump should have a guide on that. This also happened to me, while playing a video, etc, on kappa.