Fedora Rawhide AArch64 image recipes and validation tools for uke / SM7675.
Kernel sources and RPM rules are maintained in the Senemos repository.
Project status · Architecture · Development COPR · Image releases
The Plasma first-run recipe prepares the full original Fedora desktop selection, user-created accounts and the enabled development COPR. Offline checks are separate from first-run GUI and tablet acceptance; the currently published Alpha image is not replaced by this source change.
Matched RAM boots reach the tablet console, the existing 64 GiB Fedora root, software KDE and Wi-Fi SSH. The revised initramfs starts ADSP charger services and exposes battery readings in a fresh RAM boot. Repeated cold boots, normal slot-B startup and automatic charging still need testing. Finger input and ten simultaneous touch contacts also worked in the 14 October tablet test; stylus and touch lifecycle checks remain open. Power and volume buttons and manual backlight control also worked. Backlight adjustment is linear and difficult to use comfortably; a logarithmic curve is planned.
Published Core and KDE prebuild roots have separate host/filesystem checks; those exact root images have not been booted on the tablet. Current device results come from a different development installation. See the hardware table.
Core and early-initramfs payloads reject Python. The Fedora root may retain Python supplied by unmodified original Fedora desktop dependencies, under the 14 October exception. Those files must match separately verified signed RPMs. Project device helpers remain native code or shell. KDE applications are not cloned, forked or rebuilt as Uke variants.
Run image commands from the Uke workspace:
./ukelinux.sh --build core --distro=fedora --test
./ukelinux.sh --build boot-pair --distro=fedora --help
./ukelinux.sh --build boot --distro=fedora --help| Target | Output / purpose |
|---|---|
core |
Console filesystem and separate UEFI/ESP development outputs |
boot-pair |
Root-capable fedora_boot.img and system.img for the stock Android bootloader |
boot |
Older initramfs-only debug image; does not switch to the Linux root |
For a kernel build, use the kernel repository's entry point:
./senemos-uke-kernel/senemos.sh --build 7.2.9 --distro=fedora --testBuild scripts support dry-run, offline and self-test modes. They do not create partitions, flash images or select slots. Other compiler jobs retain priority; source and completed build caches are reused.
The current pair recipe selects exactly one physical ext4 GPT partition named
linux through root=PARTLABEL=linux. A fixed filesystem UUID is not required.
The boot image targets boot_b; no ESP is needed. Runtime device-tree changes
preserve the bootloader's RAM map and reserved regions. Android userdata,
init_boot, vendor_boot and dtbo are not changed by the builder.
Image, initramfs, device tree and modules must come from a matching build.
Installing a kernel RPM through DNF does not update the embedded boot image or
write boot_b. Older package revisions sharing the same kernel release can
replace its modules, so updates need a reviewed boot/module set and rollback.
Before a device trial:
./ukelinux.sh --check-device --pair DELIVERY_DIRECTORYThis read-only check verifies delivery files, root selection, Uke identity,
slot/unlock state and target capacities. --offline checks local files only;
--report NEW_FILE saves a private result. Exit 2 means device prerequisites
are unavailable. Passing the check does not establish a backup or successful boot.
The recipe mounts persist read-only to preserve OEM calibration. Sensor tests
must not turn it into a writable registry. The current debug profile can provide
local and USB shells; they are development features, not secure release defaults.
See the image guide, private boot-pair instructions and boot-B instructions for exact profiles and rollback requirements. The UEFI/ESP32-S3 host route is separate work; it does not inherit stock-bootloader test results.
Dated reports retain their original test scope. The October 9 pair used a UUID contract; later recipes use the partition name. A VM boot or package installation does not establish tablet UFS, screen, USB or sleep behavior.
- Image construction
- Stock-bootloader pair
- Kernel lifecycle
- Host bootstrap
- COPR automation
- Recovery packages
- Private engineering records
Firmware redistribution and licenses are reviewed separately from kernel source packages. Public releases include checksums and installation limits; physical results are reported separately for each tested build and device variant.
New Core and boot-pair roots use noatime and errors=remount-ro on ext4. This matches the boot integration template while preserving the existing filesystem identity, normal ordered journaling, write barriers and commit interval. The first option avoids access-time writes; the second protects an errored root from further writes. Periodic trimming remains separate from continuous mount-time discard. Source checks do not qualify a newly exported image.