search

hexdump0815 / imagebuilder

velvet os - simple script framework to build ubuntu 22.04 lts jammy (in older versions also 20.04 lts focal) and debian 12 bookworm (in older versions also 11 bullseye) bootable usb / sd card images for some arm and intel devices - lots of prebuilt images as well
GNU General Public License v3.0
300 stars 44 forks source link

systems/chromebook_kukui #36

Closed BenjaminWegener closed 2 years ago

BenjaminWegener commented 2 years ago

Wanted to give some feedback... After allowing dev_boot_usb, dev_boot_altfw and usb controller, the july kukui jmage boots on my FENNEL14

Have to try out what works and what not, giving reply soon

BenjaminWegener commented 2 years ago

Burnt with balena etcher on some stick fiy

BenjaminWegener commented 2 years ago

so far some things i discovered:

after first reboot xfce gets tearing, cant see anything but pixelcrap --> now only one thing helps: installing lxde an booting into it. tested gnome too, cant open firefox for example

BenjaminWegener commented 2 years ago

now i updated ubuntu to 22.04 via update-manager cant install firefox(uses snapd, error with squashfs, likely due to missing loopback support in kernel) have no sound, havent dived into alsa ucm using falkon as browser, giving me 30 fps on webgl aquarium, nearly the half of the 60 on cromeos

hexdump0815 commented 2 years ago

lets keep this issue open to give others a chance to find it too

first, thanks a lot for the feedback ... the 30fps for the aquarium sound reasonable, as mainline uses the open source panfrost gpu driver and chromeos the legacy mali driver and panfrost is not yet on par performace wise (and still has a few more bugs maybe as well)

the problems after first reboot sound strange to me - at least as long as nothing has been done inbetween (update etc.) ... if things were updated inbetween it might be that the env vars pointing to the nwwr self compiled mesa do not work anymore on newer ubuntu versions just like they do no longer work on debian bullseye - in this case the debian approach might be required (apt-mark hold for mesa and the xserver and directly linking the mesa dri dirs - i did not yet find a better way than this)

ucm files might require some adjustements per machine and the kernel config options for snap support are already on my todo list - i did not yet look at ubuntu 22.04 at all - i plan to include it into the imagebuilder framework once it is fully out

best wishes - hexdump

BenjaminWegener commented 2 years ago

Aight, sounds reasonable. I updated to your 5.15. kernel,got only black screen,so reverted back to 5.13.

BenjaminWegener commented 2 years ago

had some time, so was digging into the new kernel, 5.15. which is giving me black screen. i pressed power after 1 mnute an it went to shutdown, so i thought it would be possible that it boots normal. so here is the dmesg with black screen: dmesg.txt

the two lines [ 0.000000] kernel: Kernel command line: cros_secure console=tty1 root=PARTUUID=9c3ea286-c06d-7943-8f99-26cb5bb57712/PARTNROFF=3 rootwait ro fsck.fix=yes fsck.repair=yes net.ifnames=0 ipv6.disable=1 fw_devlink=off noresume [ 0.000000] kernel: Unknown kernel command line parameters "cros_secure", will be passed to user space. are suspicious, on the 5.13 there the second line doesn't exist