# Attempting to build with ubuntu 24.04

**URL:** <https://community.solid-run.com/t/attempting-to-build-with-ubuntu-24-04/966>\
**Category:** OCTEON CN9130\
**Created:** [January 14, 2025, 1:51pm UTC](https://community.solid-run.com/t/attempting-to-build-with-ubuntu-24-04/966 "2025-01-14T13:51:19Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![RoutingLoop](https://avatars.discourse-cdn.com/v4/letter/r/ac8455/32.png) [@RoutingLoop](https://community.solid-run.com/u/RoutingLoop)\
**Post date:** [January 14, 2025, 1:51pm UTC](https://community.solid-run.com/t/attempting-to-build-with-ubuntu-24-04/966/1 "2025-01-14T13:51:19Z")

</div>

Hello, it’s been a while since posting, (2022 by the looks of it), my clear-fog base has been running along nicely since my 2022 build. but I’d like to upgrade it to upgrade to noble 24.04 - i know it’s not supported yet by solidrun. I’ll happily contribute back when i’ve built.

I’ve trying to build against develop-SDK12 and develop-SDK12-mainline trees.

My current attempt, fails after writing the ubuntu filesystem. (that seems to complete).

```auto
Creating journal (8192 blocks): done
Copying files into the device: done
Writing superblocks and filesystem accounting information: done
**
ERROR:../../target/arm/internals.h:738:regime_is_user: code should not be reached
Bail out! ERROR:../../target/arm/internals.h:738:regime_is_user: code should not be reached
./runme.sh: line 314: 19045 Aborted (core dumped) qemu-system-aarch64 -m 1G -M virt -cpu max -smp 4 -netdev user,id=eth0 -device virtio-net-device,netdev=eth0 -drive file=rootfs.ext4,if=none,format=raw,cache=unsafe,id=hd0,discard=unmap -device virtio-blk-device,drive=hd0 -device virtio-rng-device -nographic -no-reboot -kernel "${ROOTDIR}/images/tmp/boot/Image" -append "console=ttyAMA0 root=/dev/vda rootfstype=ext4 ip=dhcp rw init=/stage2.sh"

```

There is discussion of a very similar looking issue caused by a bug but i think it might going down a rabbit hole after reading into to it.

[https://lore.kernel.org/all/CAFEAcA8uJL1t2MDjaJL7u5oW4ns23\_E+sk7987x4gAcs3dSZOw@mail.gmail.com/](https://lore.kernel.org/all/CAFEAcA8uJL1t2MDjaJL7u5oW4ns23_E+sk7987x4gAcs3dSZOw@mail.gmail.com/)  
I’m using docker build env.

Any pointers to look into would be greatly appreciated.  
[edit] As i’m reading it may be related to the bug in qemu-system-aarch64  
Kind regards  
Adrian

---

<div class="post-metadata">

**Author:** ![RoutingLoop](https://avatars.discourse-cdn.com/v4/letter/r/ac8455/32.png) [@RoutingLoop](https://community.solid-run.com/u/RoutingLoop)\
**Post date:** [January 14, 2025, 11:00pm UTC](https://community.solid-run.com/t/attempting-to-build-with-ubuntu-24-04/966/2 "2025-01-14T23:00:30Z")

</div>

[UPDATE]

Seems like it was related to the, or a related, bug in qemu-system-aarch64. I’ve compiled the most recent version from [https://gitlab.com/qemu-project/qemu](https://gitlab.com/qemu-project/qemu) master.

QEMU emulator version 9.2.50 (v9.2.0-945-ge8aa7fdcdd).

previous version was what ever was used in docker. it also occured on qemu-8.2.2 from noble apt respository.

I’m continuing with the build at least.

---

<div class="post-metadata">

**Author:** ![RoutingLoop](https://avatars.discourse-cdn.com/v4/letter/r/ac8455/32.png) [@RoutingLoop](https://community.solid-run.com/u/RoutingLoop)\
**Post date:** [January 21, 2025, 2:12pm UTC](https://community.solid-run.com/t/attempting-to-build-with-ubuntu-24-04/966/4 "2025-01-21T14:12:31Z")

</div>

as a bit of an update to this. I managed to successfully build ub24.04 with kernel6.13-rc7. I had to hack the musdk/modules/cma and pp2 code to get it to compile.

however, eth1 link will not come up, it’s succesfully loaded in PHY/SGMII link mode. i’m not sure if it’s related to my above hack to get it to compile. But i wanted to try a pre-built image to compare.