Update for 2018

The only thing missing right now is a i386 Tumbleweed JeOS image. With that we should be good. Any help on that is highly appreciated.

Update for 2017

The source code for crouton needs to be fixed up and pushed again to see if it gets accpeted upstream. We should be near (TM).


old description

[edit] After some discussions it seems more reasonable to get crouton to be able to build a openSUSE chroot, so I will look into this. If that's to easy/hard/boring I will fallback to some lowlevel kernel/uboot hacking :) [/edit]

With the chromebook R13 [1] the first arm64 based laptop style HW is available. The idea is to enable openSUSE on it. Lot's of things have to be done here:

  • find out how the image has to look like and build an image
  • forward port the patches needed to get graphics et al working
  • enable the mt8173 SoC in u-boot

[1] https://www.amazon.de/Acer-Chromebook-CB5-312T-K0YK-Convertible-Notebook-Multi-Touch/dp/B01N6JR7UE/ref=sr11?ie=UTF8&qid=1484905877&sr=8-1&keywords=chromebook+r13

Looking for hackers with the skills:

arm64 chromeos bash chromebook

This project is part of:

Hack Week 15 Hack Week 16 Hack Week 17

Activity

  • over 3 years ago: mbrugger left this project.
  • over 4 years ago: cdywan liked this project.
  • over 6 years ago: tdz liked this project.
  • over 6 years ago: rtorrero liked this project.
  • about 7 years ago: michals liked this project.
  • about 7 years ago: a_faerber liked this project.
  • about 7 years ago: mbrugger added keyword "chromebook" to this project.
  • about 7 years ago: TBro liked this project.
  • about 7 years ago: mkubecek liked this project.
  • about 7 years ago: ldevulder liked this project.
  • almost 8 years ago: randybb liked this project.
  • almost 8 years ago: mbrugger added keyword "chromeos" to this project.
  • almost 8 years ago: mbrugger added keyword "bash" to this project.
  • almost 8 years ago: mbrugger started this project.
  • almost 8 years ago: vliaskovitis liked this project.
  • almost 8 years ago: pluskalm liked this project.
  • almost 8 years ago: mbrugger added keyword "arm64" to this project.
  • almost 8 years ago: mbrugger originated this project.

  • Comments

    • mbrugger
      over 7 years ago by mbrugger | Reply

      I'm able to get a basic xfce desktop up and running, code can be found at: https://github.com/mbgg/crouton/tree/opensuse-v2

      Try: sudo sh crouton -r tumbleweed -t xiwi,xfce,cli-extra sudo startxfce4 -X xiwi-tab

      Needs to get merged to the official project though

    Similar Projects

    Create openSUSE images for Arm/RISC-V boards by avicenzi

    Project Description

    Create openSUSE images (or test generic EFI images) for Arm and/or RISC-V boards that are not yet supported.

    Goal for this Hackweek

    Create bootable images of Tumbleweed for SBCs that currently have no images available or are untested.

    Consider generic EFI images where possible, as some boards can hold a bootloader.

    Document in the openSUSE Wiki how to flash and use the image for a given board.

    Boards that I have around and there are no images:

    • Rock 3B
    • Nano PC T3 Plus
    • Lichee RV D1
    • StartFive VisionFive (has some image needs testing)

    Hack Week 22

    Hack Week 21

    Resources


    Investigate non-booting Forlinx OKMX8MX-C board (aarch64) by a_faerber

    Description

    In the context of a SUSE customer inquiry last year, a Forlinx OKMX8MX-C arm64 board had been relayed to me from China that a customer was not successful booting SUSE Linux Micro on. Typically this happens when the vendor's bootloader (e.g., U-Boot) is not configured properly (e.g., U-Boot's distro boot) to be compliant with Arm SystemReady Devicetree (formerly IR) band. Unfortunately I could not immediately get it to emit any output, to even diagnose why it wasn't working. There was no public documentation on the vendor's website to even confirm I was checking the right UARTs.

    Earlier this year (2024) I happened to meet the ODM/OEM, Forlinx, at Embedded World 2024 in Nuremberg and again the Monday before Hackweek 24 at Electronica 2024 in Munich. The big puzzle was that the PCB print "OKMX8MX-C" does not match any current Forlinx product, there being OKMX8MM-C and OKMX8MP-C products with the Mini and Plus variants of NXP i.MX 8M family instead. One suggestion from Forlinx staff was to double-check the DIP switches on the board for boot mode selection.

    Goals

    Double-check the board name and investigate further what may be wrong with this board.

    Resources

    none

    Progress

    • The board name is indeed as spelled above, not matching any product on forlinx.net.
    • The DIP switches were set to boot from microSD.
    • Changing the DIP switches to eMMC boot did result in UART1 RS-232 output! (although at times garbled with the cable supplied and USB adapter used)
    • As feared, it did not automatically load our GRUB from USB.
    • Booting our GRUB manually from USB (via eMMC U-Boot commands fatload+bootefi) was unsuccessful, with partially Chinese error messages.
    • This confirmed the initial suspicion, already shared with Forlinx at Embedded World 2024, that the Forlinx System-on-Module's boot firmware was not Arm SystemReady Devicetree compliant and that a firmware update would be necessary to remedy that.
    • The microSD card turned out not to contain a bootable image but to only include Chinese-language board documentation (dated 20220507) and BSP files. They used a diverging name of OKMX8MQ-C.


    Testing and adding GNU/Linux distributions on Uyuni by juliogonzalezgil

    Join the Gitter channel! https://gitter.im/uyuni-project/hackweek

    Uyuni is a configuration and infrastructure management tool that saves you time and headaches when you have to manage and update tens, hundreds or even thousands of machines. It also manages configuration, can run audits, build image containers, monitor and much more!

    Currently there are a few distributions that are completely untested on Uyuni or SUSE Manager (AFAIK) or just not tested since a long time, and could be interesting knowing how hard would be working with them and, if possible, fix whatever is broken.

    For newcomers, the easiest distributions are those based on DEB or RPM packages. Distributions with other package formats are doable, but will require adapting the Python and Java code to be able to sync and analyze such packages (and if salt does not support those packages, it will need changes as well). So if you want a distribution with other packages, make sure you are comfortable handling such changes.

    No developer experience? No worries! We had non-developers contributors in the past, and we are ready to help as long as you are willing to learn. If you don't want to code at all, you can also help us preparing the documentation after someone else has the initial code ready, or you could also help with testing :-)

    The idea is testing Salt and Salt-ssh clients, but NOT traditional clients, which are deprecated.

    To consider that a distribution has basic support, we should cover at least (points 3-6 are to be tested for both salt minions and salt ssh minions):

    1. Reposync (this will require using spacewalk-common-channels and adding channels to the .ini file)
    2. Onboarding (salt minion from UI, salt minion from bootstrap scritp, and salt-ssh minion) (this will probably require adding OS to the bootstrap repository creator)
    3. Package management (install, remove, update...)
    4. Patching
    5. Applying any basic salt state (including a formula)
    6. Salt remote commands
    7. Bonus point: Java part for product identification, and monitoring enablement
    8. Bonus point: sumaform enablement (https://github.com/uyuni-project/sumaform)
    9. Bonus point: Documentation (https://github.com/uyuni-project/uyuni-docs)
    10. Bonus point: testsuite enablement (https://github.com/uyuni-project/uyuni/tree/master/testsuite)

    If something is breaking: we can try to fix it, but the main idea is research how supported it is right now. Beyond that it's up to each project member how much to hack :-)

    • If you don't have knowledge about some of the steps: ask the team
    • If you still don't know what to do: switch to another distribution and keep testing.

    This card is for EVERYONE, not just developers. Seriously! We had people from other teams helping that were not developers, and added support for Debian and new SUSE Linux Enterprise and openSUSE Leap versions :-)

    Pending

    FUSS

    FUSS is a complete GNU/Linux solution (server, client and desktop/standalone) based on Debian for managing an educational network.

    https://fuss.bz.it/

    Seems to be a Debian 12 derivative, so adding it could be quite easy.

    • [x] Reposync (this will require using spacewalk-common-channels and adding channels to the .ini file)
    • [P] Onboarding (salt minion from UI, salt minion from bootstrap scritp, and salt-ssh minion) (this will probably require adding OS to the bootstrap repository creator) --> Works from UI, need to test the rest.
    • [P] Package management (install, remove, update...) --> Installing a new package works, needs to test the rest.
    • [ ] Patching (if patch information is available, could require writing some code to parse it, but IIRC we have support for Ubuntu already)
    • [ ] Applying any basic salt state (including a formula)
    • [ ] Salt remote commands
    • [ ] Bonus point: Java part for product identification, and monitoring enablement