# Sculpt 26.04 Release Candidates **URL:** \ **Category:** Genode and Sculpt OS\ **Created:** [April 20, 2026, 6:26am UTC](https://genode.discourse.group/t/sculpt-26-04-release-candidates/308 "2026-04-20T06:26:49Z")\ **Posts on this page:** 20\ **Page:** 2
**Author:** ![nfeske](https://dub1.discourse-cdn.com/flex006/user_avatar/genode.discourse.group/nfeske/32/6_2.png) [@nfeske](https://genode.discourse.group/u/nfeske)\ **Post date:** [April 29, 2026, 8:33am UTC](https://genode.discourse.group/t/sculpt-26-04-release-candidates/308/21 "2026-04-29T08:33:46Z")
> Maybe with the ability to automatically convert to “launcher” format and copy to the clipboard, for easy Launcher creation. This has become much less of a nuisance now that the launchers have been replaced by options. In the new version, one can copy a `child` node as is from the deploy file to an option file. Formatting changes are no longer needed. ---
**Author:** ![jjkarcher](https://avatars.discourse-cdn.com/v4/letter/j/a9adbd/32.png) [@jjkarcher](https://genode.discourse.group/u/jjkarcher)\ **Post date:** [April 29, 2026, 5:26pm UTC](https://genode.discourse.group/t/sculpt-26-04-release-candidates/308/22 "2026-04-29T17:26:11Z")
Sounds great! Can’t wait to read all about it… 🙂 ---
**Author:** ![Nos](https://avatars.discourse-cdn.com/v4/letter/n/eb9ed0/32.png) [@Nos](https://genode.discourse.group/u/Nos)\ **Post date:** [May 3, 2026, 6:25pm UTC](https://genode.discourse.group/t/sculpt-26-04-release-candidates/308/23 "2026-05-03T18:25:17Z")
I like the idea of highlighting the clients of the active/ choosen component in Leitzentrale. By the way are there already plans for updating components? ---
**Author:** ![chelmuth](https://dub1.discourse-cdn.com/flex006/user_avatar/genode.discourse.group/chelmuth/32/1_2.png) [@chelmuth](https://genode.discourse.group/u/chelmuth)\ **Post date:** [May 18, 2026, 2:38pm UTC](https://genode.discourse.group/t/sculpt-26-04-release-candidates/308/24 "2026-05-18T14:38:44Z")
We are about to publish a Sculpt 26.04.1 patch release that addresses some minor issues, e.g., suspend to RAM regressions and improved NVMe compatibility. A release candidate is available from the following URLs or via online update (chelmuth repo). [https://depot.genode.org/chelmuth/image/sculpt-pc-2026-05-18.img.xz](https://depot.genode.org/chelmuth/image/sculpt-pc-2026-05-18.img.xz) [https://depot.genode.org/chelmuth/image/sculpt-pc-2026-05-18.zip](https://depot.genode.org/chelmuth/image/sculpt-pc-2026-05-18.zip) ---
**Author:** ![G0retZ](https://avatars.discourse-cdn.com/v4/letter/g/94ad74/32.png) [@G0retZ](https://genode.discourse.group/u/G0retZ)\ **Post date:** [May 18, 2026, 6:49pm UTC](https://genode.discourse.group/t/sculpt-26-04-release-candidates/308/25 "2026-05-18T18:49:45Z")
> [@chelmuth](#): > > We are about to publish a Sculpt 26.04.1 patch release that addresses some minor issues, e.g., suspend to RAM regressions and improved NVMe compatibility. A release candidate is available from the following URLs or via online update (chelmuth repo). Just gave it a try for the on my machines. The behavior is similar to the 26.04 release (so this is a joint report). Machine1: - Core i3-9100 CPU - 16GB of RAM - Asus Prime H310M-A R2.0 motherboard. - 1 NvME SSD (in PCIe mode via BIOS). - 3 Toshiba N300 SATA HDDs. - Network: Built-in E1000 Ethernet card Machine 2: - Core i7-10700 CPU - 32GB of RAM - Asus Pro H410T/CSM - 1 NvME SSD (Samsung 970) - 1 SATA SSD (CT240BX500SSD1) - Network: M.2 Intel AX210 Wi-Fi/Bluetooth card Machine 1 behavior: - 3 SATA HDDs are visible in the system (this works well) ✅ - The **Hard reboot** works every time without issues ✅ - The **ACPI Hard power down** works every time without issues ✅ - The **ACPI Standby** goes to sleep well ✅ But on resume the mouse clicks are not working. The mouse is moving, but clicks have no effect. ❌ Tried to unplug and plug back the mouse - no luck, the system still doesn’t respond to mouse clicks 😔 - Network is totally fine ✅ Machine 2 behavior: - SATA SDD is visible in the system (this works well) ✅ - The **Hard reboot** works every time without issues ✅ - The **ACPI Hard power down** works every time without issues ✅ - The **ACPI Standby** goes to sleep well ✅ The same mouse on resume is responsive and works well ✅ - Network works well initially ✅ Though when I re-add `wifi` component via the `network` component sometimes it fails to connect or scan, reporting it will sleep forever. ❌ Also on resuming from **ACPI Standby** it ask several times for increasing the memory qouta. Then is not able to connect also. ❌ Tried to restart the `wifi` component and re-add it via the `network` component - no luck 😔 Wi-Fi issue scenario: 1. Start machine (acpi is part of deploy on used disk) 2. Put it in Stanby mode 3. Resume 4. Grant memory for all requests from `wifi` 5. Observe it fails 6. Restart `wifi` and observe it fails 7. Remove and re-add `wifi` using `network` component and observe it fails Wi-Fi issue logs: > **[paste.sh · encrypted pastebin](https://paste.sh/khivQB50#UTjQr8McTg4bNRo96ViswLWX)** > **[PasteFox - Share Code & Text Instantly | Free Pastebin Alternative](https://pastefox.com/4h8gz2)** > > Free, fast, and secure pastebin for sharing code snippets with syntax highlighting for 130+ languages. Password protection, folder, API, expiration, burn after read, and fun reveal effects. ---
**Author:** ![alex-ab](https://dub1.discourse-cdn.com/flex006/user_avatar/genode.discourse.group/alex-ab/32/10_2.png) [@alex-ab](https://genode.discourse.group/u/alex-ab)\ **Post date:** [May 19, 2026, 10:57am UTC](https://genode.discourse.group/t/sculpt-26-04-release-candidates/308/26 "2026-05-19T10:57:37Z")
> [@G0retZ](#): > > Machine 1 behavior: > > - 3 SATA HDDs are visible in the system (this works well) ✅ > - The **Hard reboot** works every time without issues ✅ > - The **ACPI Hard power down** works every time without issues ✅ > - The **ACPI Standby** goes to sleep well ✅ > But on resume the mouse clicks are not working. The mouse is moving, but clicks have no effect. ❌ Tried to unplug and plug back the mouse - no luck, the system still doesn’t respond to mouse clicks 😔 > - Network is totally fine ✅ If you can setup the report\_dump (GenodeLabs index) component, we may get a log after resume for collecting ideas. ---
**Author:** ![G0retZ](https://avatars.discourse-cdn.com/v4/letter/g/94ad74/32.png) [@G0retZ](https://genode.discourse.group/u/G0retZ)\ **Post date:** [May 19, 2026, 11:20am UTC](https://genode.discourse.group/t/sculpt-26-04-release-candidates/308/27 "2026-05-19T11:20:38Z")
> [@alex-ab](#): > > If you can setup the report\_dump (GenodeLabs index) component, we may get a log after resume for collecting ideas. Sure, I can try that today evening 👌 Though I thought I captured all the logs the system provided before and after the suspend… Note a standby time gap between18th an 60th seconds in the logs I provided yesterday? 🤔 ---
**Author:** ![alex-ab](https://dub1.discourse-cdn.com/flex006/user_avatar/genode.discourse.group/alex-ab/32/10_2.png) [@alex-ab](https://genode.discourse.group/u/alex-ab)\ **Post date:** [May 19, 2026, 11:24am UTC](https://genode.discourse.group/t/sculpt-26-04-release-candidates/308/28 "2026-05-19T11:24:08Z")
> [@G0retZ](#): > > Though I thought I captured all the logs the system provided before and after the suspend… > Note a standby time gap between18th an 60th seconds in the logs I provided yesterday? 🤔 The one log are from Machine 2 regarding Wifi, or ? I’m interested in the log of Machine 1, with the non-working mouse click especially. ---
**Author:** ![G0retZ](https://avatars.discourse-cdn.com/v4/letter/g/94ad74/32.png) [@G0retZ](https://genode.discourse.group/u/G0retZ)\ **Post date:** [May 19, 2026, 11:28am UTC](https://genode.discourse.group/t/sculpt-26-04-release-candidates/308/29 "2026-05-19T11:28:57Z")
> [@alex-ab](#): > > The one log are from Machine 2 regarding Wifi, or ? I’m interested in the log of Machine 1, with the non-working mouse click especially. Ah, ok, sorry I misunderstood that. Will try to capture today evening 👌 ---
**Author:** ![G0retZ](https://avatars.discourse-cdn.com/v4/letter/g/94ad74/32.png) [@G0retZ](https://genode.discourse.group/u/G0retZ)\ **Post date:** [May 19, 2026, 7:00pm UTC](https://genode.discourse.group/t/sculpt-26-04-release-candidates/308/30 "2026-05-19T19:00:11Z")
> [@alex-ab](#): > > If you can setup the report\_dump (GenodeLabs index) component, we may get a log after resume for collecting ideas. Ok, I grabbed the logs. 🫴 Here they are (expire in 1 week) ➡ : [Download log.tar.xz | LimeWire](https://limewire.com/d/HAxob#QyQQ144KXW) Hope this helps! ✌ ---
**Author:** ![Nos](https://avatars.discourse-cdn.com/v4/letter/n/eb9ed0/32.png) [@Nos](https://genode.discourse.group/u/Nos)\ **Post date:** [May 19, 2026, 9:12pm UTC](https://genode.discourse.group/t/sculpt-26-04-release-candidates/308/31 "2026-05-19T21:12:22Z")
I tried the 26.04.1 release using my Thinkpad X380 Yoga today evening. - nvme: it is already installed on my built-in nvme storage and boots from it - usb-mouse, touchpad, touchscreen: works well (most of the time) - VMs (Virtualbox): successfully tried with linux (including internet and basic 3d hw-accelleration) - sound: still not working since 26.04 - restart, shutdown: works well - Suspend: - wifi got reconnect after resume - webbrowser playing an internetvideo: continue after resume - the mentioned linux vm: continue after resume too - touchpad: Cursor jumps around near the upper right corner (and restarting the usb-hid did not change this) - usb-mouse, touchscreen: needs short time but than mostly works again Sometimes mouse clicks or even keyboard input was not processed. After clicking around for half a minute it works again sometimes. Sometimes I had to restart my notebook to solve this. ---
**Author:** ![alex-ab](https://dub1.discourse-cdn.com/flex006/user_avatar/genode.discourse.group/alex-ab/32/10_2.png) [@alex-ab](https://genode.discourse.group/u/alex-ab)\ **Post date:** [May 22, 2026, 12:34pm UTC](https://genode.discourse.group/t/sculpt-26-04-release-candidates/308/32 "2026-05-22T12:34:00Z")
> [@G0retZ](#): > > Ok, I grabbed the logs. 🫴 > Here they are (expire in 1 week) ➡ : [Download log.tar.xz | LimeWire](https://limewire.com/d/HAxob#QyQQ144KXW) > Hope this helps! ✌ Thanks, for your effort, unfortunately the logs do not reveal some obvious mouse related issue. Can you still switch via F12 back to the runtime and interact with some window (like system shell) with keyboard and also using the mouse to move the window ? It may behave differently between leitzentrale and runtime … ---
**Author:** ![Nos](https://avatars.discourse-cdn.com/v4/letter/n/eb9ed0/32.png) [@Nos](https://genode.discourse.group/u/Nos)\ **Post date:** [May 22, 2026, 3:23pm UTC](https://genode.discourse.group/t/sculpt-26-04-release-candidates/308/33 "2026-05-22T15:23:17Z")
I forgot to mention that after resuming from suspend even the hdmi-output is continue to work well on my Thinkpad. ---
**Author:** ![chelmuth](https://dub1.discourse-cdn.com/flex006/user_avatar/genode.discourse.group/chelmuth/32/1_2.png) [@chelmuth](https://genode.discourse.group/u/chelmuth)\ **Post date:** [June 4, 2026, 1:43pm UTC](https://genode.discourse.group/t/sculpt-26-04-release-candidates/308/34 "2026-06-04T13:43:44Z")
We are about to publish a Sculpt 26.04.2 patch release that addresses driver restart and wifi issues as well as window manager tweaks. A release candidate is available from the following URLs or via online update (chelmuth repo). [https://depot.genode.org/chelmuth/image/sculpt-pc-2026-06-04.img.xz](https://depot.genode.org/chelmuth/image/sculpt-pc-2026-06-04.img.xz) [https://depot.genode.org/chelmuth/image/sculpt-pc-2026-06-04.zip](https://depot.genode.org/chelmuth/image/sculpt-pc-2026-06-04.zip) ---
**Author:** ![Nos](https://avatars.discourse-cdn.com/v4/letter/n/eb9ed0/32.png) [@Nos](https://genode.discourse.group/u/Nos)\ **Post date:** [June 4, 2026, 5:21pm UTC](https://genode.discourse.group/t/sculpt-26-04-release-candidates/308/35 "2026-06-04T17:21:25Z")
Thanks for the release candidate. I gave it a short test drive on my usual notebooks (Lenovo X380 Yoga, (amd based) Framework 16 and some further notebooks (Lenovo X390 Yoga, Lenovo X1 Yoga (Gen 3)) too. I’m really excited to see how everything keeps working a little bit better. Still, here are a few problems I’ve come across: - general problems I experienced while testing - (amd based) Framework 16: I will give the wifi a separate test drive - Lenovo X390 Yoga: Wifi does not work (it scans without end; I can provide the log if needed); fortunately usb-net works well ---
**Author:** ![chelmuth](https://dub1.discourse-cdn.com/flex006/user_avatar/genode.discourse.group/chelmuth/32/1_2.png) [@chelmuth](https://genode.discourse.group/u/chelmuth)\ **Post date:** [June 5, 2026, 6:18am UTC](https://genode.discourse.group/t/sculpt-26-04-release-candidates/308/36 "2026-06-05T06:18:36Z")
> [@Nos](#): > > - Lenovo X390 Yoga: Wifi does not work (it scans without end; I can provide the log if needed); fortunately usb-net works well According to [Evaluation of hardwaresupport for ThinkPad X380 Yoga](https://genode.discourse.group/t/evaluation-of-hardwaresupport-for-thinkpad-x380-yoga/174) this looks like a regression, right? Did you try mutliple boots? In our tests, Intel 82xx CNVi WiFi was also not 100% reliable (i.e., timing sensitive) with the original 26.04 release too. ---
**Author:** ![Nos](https://avatars.discourse-cdn.com/v4/letter/n/eb9ed0/32.png) [@Nos](https://genode.discourse.group/u/Nos)\ **Post date:** [June 5, 2026, 9:02am UTC](https://genode.discourse.group/t/sculpt-26-04-release-candidates/308/37 "2026-06-05T09:02:48Z")
I tried to use wifi at the X390 Yoga for several times now. After some reboots, restarts of the network and wifi components and using the ramfs instead the usb thumbdrive it works now. Here comes some log snippets. > **Summary with the error mentioned above** > > ```auto > 6.0 [core] [init -> runtime] child "prepare" exited with exit value 0 > 11.3 [acpi_support] e[34mWarning: 00:00.0 emulate read 0x60 -> 0xe0000001e[0m > 11.5 [acpi_support] detected - ec > 11.5 [acpi_support] failed - sleep button registration - error=22 > 11.5 [acpi_support] detected - ac > 11.5 [acpi_support] detected - smart battery: BAT0 > 11.5 [acpi_support] detected - lid > 11.5 [acpi_support] open - lid (0) > 11.6 [model_query] e[34mWarning: ack for unknown File_system handle 905e[0m > 16.2 [runtime_view] e[34mWarning: attempt to handle the same signal context twice (nested)e[0m > 16.6 [usb] usb 3-7: USB disconnect, device number 3 > 16.6 [model_query] e[34mWarning: ack for unknown File_system handle 934e[0m > 16.9 [usb] usb 3-7: new high-speed USB device number 7 using xhci_hcd > 17.1 [model_query] e[34mWarning: ack for unknown File_system handle 963e[0m > 30.1 [wifi] SLUB: HWalign=64, Order=0-1, MinObjects=0, CPUs=1, Nodes=1 > 30.1 [wifi] NR_IRQS: 4352, nr_irqs: 4352, preallocated irqs: 256 > 30.1 [wifi] clocksource: dde_counter: mask: 0xffffffffffffff max_cycles: 0x1d854df40, max_idle_ns: 3526361616960 ns > 30.2 [wifi] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns > 30.2 [wifi] NET: Registered PF_NETLINK/PF_ROUTE protocol family > 30.2 [wifi] clocksource: Switched to clocksource dde_counter > 30.2 [wifi] pci_iomap: request for dev: 00:14.3 bar: 0 > 30.2 [wifi] iwlwifi 00:14.3: pci_enable_msi failed - -38 > 30.2 [wifi] task_work_add: task: 00000000002bc000 work: 00000000412fee20 notify: 0 > 30.2 [wifi] iwlwifi 00:14.3: Detected crf-id 0x2816, cnv-id 0x1000100 wfpm id 0x80000000 > 30.2 [wifi] iwlwifi 00:14.3: PCI dev 9df0/0030, rev=0x312, rfid=0x105110 > 30.2 [wifi] iwlwifi 00:14.3: Detected Intel(R) Wireless-AC 9560 160MHz > 30.2 [wifi] NET: Registered PF_PACKET protocol family > 30.2 [wifi] sched_clock: Marking stable (14615000, 18022000)->(71398000, -38761000) > 30.2 [model_query] e[34mWarning: ack for unknown File_system handle 1079e[0m > 30.2 [wifi] reg: Loading compiled-in X.509 certificates for regulatory database > 30.2 [wifi] e[34mWarning: /dev/rtc not readable, returning 0e[0m > 30.2 [wifi] iwlwifi 00:14.3: WRT: Overriding region id 0 > 30.2 [wifi] iwlwifi 00:14.3: WRT: Overriding region id 1 > 30.2 [wifi] iwlwifi 00:14.3: WRT: Overriding region id 2 > 30.2 [wifi] iwlwifi 00:14.3: WRT: Overriding region id 3 > 30.2 [wifi] iwlwifi 00:14.3: WRT: Overriding region id 4 > 30.2 [wifi] iwlwifi 00:14.3: WRT: Overriding region id 6 > 30.2 [wifi] iwlwifi 00:14.3: WRT: Overriding region id 8 > 30.2 [wifi] iwlwifi 00:14.3: WRT: Overriding region id 9 > 30.2 [wifi] iwlwifi 00:14.3: WRT: Overriding region id 10 > 30.2 [wifi] iwlwifi 00:14.3: WRT: Overriding region id 11 > 30.2 [wifi] iwlwifi 00:14.3: WRT: Overriding region id 15 > 30.2 [wifi] iwlwifi 00:14.3: WRT: Overriding region id 16 > 30.2 [wifi] iwlwifi 00:14.3: WRT: Overriding region id 18 > 30.2 [wifi] iwlwifi 00:14.3: WRT: Overriding region id 19 > 30.2 [wifi] iwlwifi 00:14.3: WRT: Overriding region id 20 > 30.2 [wifi] iwlwifi 00:14.3: WRT: Overriding region id 21 > 30.2 [wifi] iwlwifi 00:14.3: WRT: Overriding region id 28 > 30.2 [wifi] iwlwifi 00:14.3: loaded firmware version 46.6b541b68.0 9000-pu-b0-jf-b0-46.ucode op_mode iwlmvm > 30.2 [wifi] reg: loaded regulatory.db is malformed or signature is missing/invalid > 30.3 [wifi] iwlwifi 00:14.3: base HW address: 50:e0:85:82:2f:f8, OTP minor version: 0x4 > 30.3 [wifi] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs' > 30.4 [wifi] iwlwifi 00:14.3: Hardware error detected. Restarting. > 30.4 [wifi] iwlwifi 00:14.3: DEVICE_ENABLED bit is not set. Aborting dump. > 30.5 [wifi] iwlwifi 00:14.3: WRT: Collecting data: ini trigger 4 fired (delay=0ms). > 30.8 [wifi] iwlwifi 00:14.3: WRT: Failed to dump region: id=19, type=16 > 30.8 [wifi] iwlwifi 00:14.3: Microcode SW error detected. Restarting 0x12000000. > 30.8 [wifi] iwlwifi 00:14.3: Start IWL Error Log Dump: > 30.8 [wifi] iwlwifi 00:14.3: Transport status: 0x0000024B, valid: 6 > 30.8 [wifi] iwlwifi 00:14.3: Loaded firmware version: 46.6b541b68.0 9000-pu-b0-jf-b0-46.ucode > 30.8 [wifi] iwlwifi 00:14.3: 0x0000005D | ADVANCED_SYSASSERT > 30.8 [wifi] iwlwifi 00:14.3: 0x00A0A2F0 | trm_hw_status0 > 30.8 [wifi] iwlwifi 00:14.3: 0x00000000 | trm_hw_status1 > 30.8 [wifi] iwlwifi 00:14.3: 0x00488E8A | branchlink2 > 30.8 [wifi] iwlwifi 00:14.3: 0x00478EDE | interruptlink1 > 30.8 [wifi] iwlwifi 00:14.3: 0x00478EDE | interruptlink2 > 30.8 [wifi] iwlwifi 00:14.3: 0x0001B0B2 | data1 > 30.8 [wifi] iwlwifi 00:14.3: 0x00080000 | data2 > 30.8 [wifi] iwlwifi 00:14.3: 0x40A0044C | data3 > 30.8 [wifi] iwlwifi 00:14.3: 0x003F6921 | beacon time > 30.8 [wifi] iwlwifi 00:14.3: 0x000096DD | tsf low > 30.8 [wifi] iwlwifi 00:14.3: 0x00000000 | tsf hi > 30.8 [wifi] iwlwifi 00:14.3: 0x00000000 | time gp1 > 30.8 [wifi] iwlwifi 00:14.3: 0x000096DE | time gp2 > 30.8 [wifi] iwlwifi 00:14.3: 0x00000001 | uCode revision type > 30.8 [wifi] iwlwifi 00:14.3: 0x0000002E | uCode version major > 30.8 [wifi] iwlwifi 00:14.3: 0x6B541B68 | uCode version minor > 30.8 [wifi] iwlwifi 00:14.3: 0x00000312 | hw version > 30.8 [wifi] iwlwifi 00:14.3: 0x00489002 | board version > 30.8 [wifi] iwlwifi 00:14.3: 0x001C01D2 | hcmd > 30.8 [wifi] iwlwifi 00:14.3: 0x20022000 | isr0 > 30.8 [wifi] iwlwifi 00:14.3: 0x00000000 | isr1 > 30.8 [wifi] iwlwifi 00:14.3: 0x08001802 | isr2 > 30.8 [wifi] iwlwifi 00:14.3: 0x004000C0 | isr3 > 30.8 [wifi] iwlwifi 00:14.3: 0x00000000 | isr4 > 30.8 [wifi] iwlwifi 00:14.3: 0x001C01D2 | last cmd Id > 30.8 [wifi] iwlwifi 00:14.3: 0x0001B0B2 | wait_event > 30.8 [wifi] iwlwifi 00:14.3: 0x00000000 | l2p_control > 30.8 [wifi] iwlwifi 00:14.3: 0x00000020 | l2p_duration > 30.8 [wifi] iwlwifi 00:14.3: 0x00000000 | l2p_mhvalid > 30.8 [wifi] iwlwifi 00:14.3: 0x00000000 | l2p_addr_match > 30.8 [wifi] iwlwifi 00:14.3: 0x0000000D | lmpm_pmg_sel > 30.8 [wifi] iwlwifi 00:14.3: 0x10032208 | timestamp > 30.8 [wifi] iwlwifi 00:14.3: 0x0000183C | flow_handler > 30.8 [wifi] iwlwifi 00:14.3: Start IWL Error Log Dump: > 30.8 [wifi] iwlwifi 00:14.3: Transport status: 0x0000024B, valid: 7 > 30.8 [wifi] iwlwifi 00:14.3: 0x20000070 | NMI_INTERRUPT_LMAC_FATAL > 30.8 [wifi] iwlwifi 00:14.3: 0x00000000 | umac branchlink1 > 30.8 [wifi] iwlwifi 00:14.3: 0xC0088BBE | umac branchlink2 > 30.8 [wifi] iwlwifi 00:14.3: 0xC0084458 | umac interruptlink1 > 30.8 [wifi] iwlwifi 00:14.3: 0xC0084458 | umac interruptlink2 > 30.8 [wifi] iwlwifi 00:14.3: 0x00000800 | umac data1 > 30.8 [wifi] iwlwifi 00:14.3: 0xC0084458 | umac data2 > 30.8 [wifi] iwlwifi 00:14.3: 0xDEADBEEF | umac data3 > 30.8 [wifi] iwlwifi 00:14.3: 0x0000002E | umac major > 30.8 [wifi] iwlwifi 00:14.3: 0x6B541B68 | umac minor > 30.8 [wifi] iwlwifi 00:14.3: 0x000096F4 | frame pointer > 30.8 [wifi] iwlwifi 00:14.3: 0xC088627C | stack pointer > 30.8 [wifi] iwlwifi 00:14.3: 0x001D0F07 | last host cmd > 30.8 [wifi] iwlwifi 00:14.3: 0x00000000 | isr status reg > 30.8 [wifi] iwlwifi 00:14.3: IML/ROM dump: > 30.8 [wifi] iwlwifi 00:14.3: 0x00002319 | IML/ROM error/state > 30.8 [wifi] iwlwifi 00:14.3: 0x00000003 | IML/ROM data1 > 30.8 [wifi] iwlwifi 00:14.3: Fseq Registers: > 30.8 [wifi] iwlwifi 00:14.3: 0x6C182A5B | FSEQ_ERROR_CODE > 30.8 [wifi] iwlwifi 00:14.3: 0x00000000 | FSEQ_TOP_INIT_VERSION > 30.8 [wifi] iwlwifi 00:14.3: 0x033CE22A | FSEQ_CNVIO_INIT_VERSION > 30.8 [wifi] iwlwifi 00:14.3: 0x0000A384 | FSEQ_OTP_VERSION > 30.8 [wifi] iwlwifi 00:14.3: 0x680E531A | FSEQ_TOP_CONTENT_VERSION > 30.8 [wifi] iwlwifi 00:14.3: 0xE6E0C2A3 | FSEQ_ALIVE_TOKEN > 30.8 [wifi] iwlwifi 00:14.3: 0x1967F9F9 | FSEQ_CNVI_ID > 30.8 [wifi] iwlwifi 00:14.3: 0x4842CDE9 | FSEQ_CNVR_ID > 30.8 [wifi] iwlwifi 00:14.3: 0x01000100 | CNVI_AUX_MISC_CHIP > 30.8 [wifi] iwlwifi 00:14.3: 0x01300202 | CNVR_AUX_MISC_CHIP > 30.8 [wifi] iwlwifi 00:14.3: 0x0000485B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM > 30.8 [wifi] iwlwifi 00:14.3: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR > 30.8 [wifi] iwlwifi 00:14.3: 0x4D816CC0 | FSEQ_PREV_CNVIO_INIT_VERSION > 30.8 [wifi] iwlwifi 00:14.3: 0x454B28A7 | FSEQ_WIFI_FSEQ_VERSION > 30.8 [wifi] iwlwifi 00:14.3: 0x29CC5243 | FSEQ_BT_FSEQ_VERSION > 30.8 [wifi] iwlwifi 00:14.3: 0xEA92DF8E | FSEQ_CLASS_TP_VERSION > 30.8 [wifi] iwlwifi 00:14.3: FW error in SYNC CMD DBGC_SUSPEND_RESUME > 30.8 [wifi] backtrace "ep" > 30.8 [wifi] iwlwifi 00:14.3: Device error - SW reset > 30.8 [wifi] ieee80211 phy0: Hardware restart was requested > 30.8 [wifi] iwlwifi 00:14.3: Failed to send MAC_CONTEXT_CMD (action:2): -5 > 30.8 [wifi] iwlwifi 00:14.3: failed to update MAC 50:e0:85:82:2f:f8 > 30.8 [wifi] iwlwifi 00:14.3: Failed to send MAC_CONTEXT_CMD (action:2): -5 > 30.8 [wifi] iwlwifi 00:14.3: failed to update MAC 50:e0:85:82:2f:f8 > 30.8 [wifi] iwlwifi 00:14.3: WRT: Collecting data: ini trigger 4 fired (delay=0ms). > 31.1 [wifi] iwlwifi 00:14.3: WRT: Failed to dump region: id=19, type=16 > 31.1 [wifi] iwlwifi 00:14.3: Failed to synchronize multicast groups update > 31.2 [wifi] iwlwifi 00:14.3: Hardware error detected. Restarting. > 31.2 [wifi] iwlwifi 00:14.3: DEVICE_ENABLED bit is not set. Aborting dump. > 31.3 [wifi] iwlwifi 00:14.3: WRT: Collecting data: ini trigger 4 fired (delay=0ms). > 31.6 [wifi] iwlwifi 00:14.3: WRT: Failed to dump region: id=19, type=16 > 31.6 [wifi] iwlwifi 00:14.3: Microcode SW error detected. Restarting 0x12000000. > 31.6 [wifi] iwlwifi 00:14.3: Start IWL Error Log Dump: > 31.6 [wifi] iwlwifi 00:14.3: Transport status: 0x0000034B, valid: 6 > 31.6 [wifi] iwlwifi 00:14.3: Loaded firmware version: 46.6b541b68.0 9000-pu-b0-jf-b0-46.ucode > 31.6 [wifi] iwlwifi 00:14.3: 0x0000005D | ADVANCED_SYSASSERT > 31.6 [wifi] iwlwifi 00:14.3: 0x00A022F0 | trm_hw_status0 > 31.6 [wifi] iwlwifi 00:14.3: 0x00000000 | trm_hw_status1 > 31.6 [wifi] iwlwifi 00:14.3: 0x00488E8A | branchlink2 > 31.6 [wifi] iwlwifi 00:14.3: 0x00478EDE | interruptlink1 > 31.6 [wifi] iwlwifi 00:14.3: 0x00478EDE | interruptlink2 > 31.6 [wifi] iwlwifi 00:14.3: 0x0001B0B2 | data1 > 31.6 [wifi] iwlwifi 00:14.3: 0x00080000 | data2 > 31.6 [wifi] iwlwifi 00:14.3: 0x40A0044C | data3 > 31.6 [wifi] iwlwifi 00:14.3: 0x003F71CC | beacon time > 31.6 [wifi] iwlwifi 00:14.3: 0x00008E33 | tsf low > 31.6 [wifi] iwlwifi 00:14.3: 0x00000000 | tsf hi > 31.6 [wifi] iwlwifi 00:14.3: 0x00000000 | time gp1 > 31.6 [wifi] iwlwifi 00:14.3: 0x00008E34 | time gp2 > 31.6 [wifi] iwlwifi 00:14.3: 0x00000001 | uCode revision type > 31.6 [wifi] iwlwifi 00:14.3: 0x0000002E | uCode version major > 31.6 [wifi] iwlwifi 00:14.3: 0x6B541B68 | uCode version minor > 31.6 [wifi] iwlwifi 00:14.3: 0x00000312 | hw version > 31.6 [wifi] iwlwifi 00:14.3: 0x00489002 | board version > 31.6 [wifi] iwlwifi 00:14.3: 0x001C01D2 | hcmd > 31.6 [wifi] iwlwifi 00:14.3: 0x00022000 | isr0 > 31.6 [wifi] iwlwifi 00:14.3: 0x00000000 | isr1 > 31.6 [wifi] iwlwifi 00:14.3: 0x08001802 | isr2 > 31.6 [wifi] iwlwifi 00:14.3: 0x004000C0 | isr3 > 31.6 [wifi] iwlwifi 00:14.3: 0x00000000 | isr4 > 31.6 [wifi] iwlwifi 00:14.3: 0x001C01D2 | last cmd Id > 31.6 [wifi] iwlwifi 00:14.3: 0x0001B0B2 | wait_event > 31.6 [wifi] iwlwifi 00:14.3: 0x00000000 | l2p_control > 31.6 [wifi] iwlwifi 00:14.3: 0x00000020 | l2p_duration > 31.6 [wifi] iwlwifi 00:14.3: 0x00000000 | l2p_mhvalid > 31.6 [wifi] iwlwifi 00:14.3: 0x00000000 | l2p_addr_match > 31.6 [wifi] iwlwifi 00:14.3: 0x0000000D | lmpm_pmg_sel > 31.6 [wifi] iwlwifi 00:14.3: 0x10032208 | timestamp > 31.6 [wifi] iwlwifi 00:14.3: 0x0000183C | flow_handler > 31.6 [wifi] iwlwifi 00:14.3: Start IWL Error Log Dump: > 31.6 [wifi] iwlwifi 00:14.3: Transport status: 0x0000034B, valid: 7 > 31.6 [wifi] iwlwifi 00:14.3: 0x20000070 | NMI_INTERRUPT_LMAC_FATAL > 31.6 [wifi] iwlwifi 00:14.3: 0x00000000 | umac branchlink1 > 31.6 [wifi] iwlwifi 00:14.3: 0xC0088BBE | umac branchlink2 > 31.6 [wifi] iwlwifi 00:14.3: 0xC0084458 | umac interruptlink1 > 31.6 [wifi] iwlwifi 00:14.3: 0xC0084458 | umac interruptlink2 > 31.6 [wifi] iwlwifi 00:14.3: 0x00000800 | umac data1 > 31.6 [wifi] iwlwifi 00:14.3: 0xC0084458 | umac data2 > 31.6 [wifi] iwlwifi 00:14.3: 0xDEADBEEF | umac data3 > 31.6 [wifi] iwlwifi 00:14.3: 0x0000002E | umac major > 31.6 [wifi] iwlwifi 00:14.3: 0x6B541B68 | umac minor > 31.6 [wifi] iwlwifi 00:14.3: 0x00008E49 | frame pointer > 31.6 [wifi] iwlwifi 00:14.3: 0xC088627C | stack pointer > 31.6 [wifi] iwlwifi 00:14.3: 0x001D0F07 | last host cmd > 31.6 [wifi] iwlwifi 00:14.3: 0x00000000 | isr status reg > 31.6 [wifi] iwlwifi 00:14.3: IML/ROM dump: > 31.6 [wifi] iwlwifi 00:14.3: 0x00002319 | IML/ROM error/state > 31.6 [wifi] iwlwifi 00:14.3: 0x00000003 | IML/ROM data1 > 31.6 [wifi] iwlwifi 00:14.3: Fseq Registers: > 31.6 [wifi] iwlwifi 00:14.3: 0x6C182A5B | FSEQ_ERROR_CODE > 31.6 [wifi] iwlwifi 00:14.3: 0x00000000 | FSEQ_TOP_INIT_VERSION > 31.6 [wifi] iwlwifi 00:14.3: 0x033CE22A | FSEQ_CNVIO_INIT_VERSION > 31.6 [wifi] iwlwifi 00:14.3: 0x0000A384 | FSEQ_OTP_VERSION > 31.6 [wifi] iwlwifi 00:14.3: 0x680E531A | FSEQ_TOP_CONTENT_VERSION > 31.6 [wifi] iwlwifi 00:14.3: 0xE6E0C2A3 | FSEQ_ALIVE_TOKEN > 31.6 [wifi] iwlwifi 00:14.3: 0x1967F9F9 | FSEQ_CNVI_ID > 31.6 [wifi] iwlwifi 00:14.3: 0x4842CDE9 | FSEQ_CNVR_ID > 31.6 [wifi] iwlwifi 00:14.3: 0x01000100 | CNVI_AUX_MISC_CHIP > 31.6 [wifi] iwlwifi 00:14.3: 0x01300202 | CNVR_AUX_MISC_CHIP > 31.6 [wifi] iwlwifi 00:14.3: 0x0000485B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM > 31.6 [wifi] iwlwifi 00:14.3: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR > 31.6 [wifi] iwlwifi 00:14.3: 0x4D816CC0 | FSEQ_PREV_CNVIO_INIT_VERSION > 31.6 [wifi] iwlwifi 00:14.3: 0x454B28A7 | FSEQ_WIFI_FSEQ_VERSION > 31.6 [wifi] iwlwifi 00:14.3: 0x29CC5243 | FSEQ_BT_FSEQ_VERSION > 31.6 [wifi] iwlwifi 00:14.3: 0xEA92DF8E | FSEQ_CLASS_TP_VERSION > 31.6 [wifi] iwlwifi 00:14.3: FW error in SYNC CMD DBGC_SUSPEND_RESUME > 31.6 [wifi] backtrace "ep" > 31.6 [wifi] iwlwifi 00:14.3: Device error - reprobe! > 31.6 [wifi] iwlwifi 00:14.3: WRT: Collecting data: ini trigger 4 fired (delay=0ms). > 31.8 [wifi] iwlwifi 00:14.3: WRT: Failed to dump region: id=19, type=16 > 31.8 [wifi] iwlwifi 00:14.3: Failed to synchronize multicast groups update > 31.8 [wifi] iwlwifi 00:14.3: Failed to send MAC_CONTEXT_CMD (action:2): -5 > 31.8 [wifi] iwlwifi 00:14.3: failed to update MAC 50:e0:85:82:2f:f8 > 31.8 [wifi] iwlwifi 00:14.3: Failed to synchronize multicast groups update > 31.8 [wifi] iwlwifi 00:14.3: failed to update power mode > 31.8 [wifi] iwlwifi 00:14.3: restart completed > 31.8 [wifi] iwlwifi 00:14.3: Failed to send MAC_CONTEXT_CMD (action:3): -5 > 31.8 [wifi] iwlwifi 00:14.3: Failed to disable queue 1 (ret=-5) > 31.8 [wifi] iwlwifi 00:14.3: Failed to remove station. Id=1 > 31.8 [wifi] iwlwifi 00:14.3: Failed sending remove station > 31.8 [wifi] e[31mError: Function gen_kill_estimator not implemented yet!e[0m > 31.8 [wifi] backtrace "ep" > 31.8 [wifi] Will sleep forever... > 32.1 [usb] usb 3-7: USB disconnect, device number 7 > 32.4 [usb] usb 3-7: new high-speed USB device number 8 using xhci_hcd > 32.6 [model_query] e[34mWarning: ack for unknown File_system handle 1137e[0m > 39.2 [network] [uplink] dynamic IP config: none > 39.2 [network] [uplink] NIC sessions: 0 > 39.2 [network] [default] static IP config: interface 10.0.1.1/24, gateway 0.0.0.0, P2P 0 > 39.2 [network] [default] NIC sessions: 0 > 39.2 [network] [http] static IP config: interface 10.0.80.1/24, gateway 0.0.0.0, P2P 0 > 39.2 [network] [http] NIC sessions: 0 > 39.2 [network] [telnet] static IP config: interface 10.0.23.1/24, gateway 0.0.0.0, P2P 0 > 39.2 [network] [telnet] NIC sessions: 0 > 39.2 [network] [gdb] static IP config: interface 10.0.99.1/24, gateway 0.0.0.0, P2P 0 > 39.2 [network] [gdb] NIC sessions: 0 > 39.2 [network] [vnc] static IP config: interface 10.0.59.1/24, gateway 0.0.0.0, P2P 0 > 39.2 [network] [vnc] NIC sessions: 0 > 47.6 [usb] usb 3-7: USB disconnect, device number 8 > 47.6 [model_query] e[34mWarning: ack for unknown File_system handle 1195e[0m > 47.9 [usb] usb 3-7: new high-speed USB device number 9 using xhci_hcd > 48.0 [model_query] e[34mWarning: ack for unknown File_system handle 1224e[0m > 59.5 [wifi] SLUB: HWalign=64, Order=0-1, MinObjects=0, CPUs=1, Nodes=1 > 59.5 [wifi] NR_IRQS: 4352, nr_irqs: 4352, preallocated irqs: 256 > 59.5 [wifi] clocksource: dde_counter: mask: 0xffffffffffffff max_cycles: 0x1d854df40, max_idle_ns: 3526361616960 ns > 59.6 [wifi] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns > 59.6 [wifi] NET: Registered PF_NETLINK/PF_ROUTE protocol family > 59.6 [wifi] clocksource: Switched to clocksource dde_counter > > ``` > **Summary working** > > ```auto > 4.0 [core] [init -> runtime] child "prepare" exited with exit value 0 > 39.8 [wifi] SLUB: HWalign=64, Order=0-1, MinObjects=0, CPUs=1, Nodes=1 > 39.8 [wifi] NR_IRQS: 4352, nr_irqs: 4352, preallocated irqs: 256 > 39.8 [wifi] clocksource: dde_counter: mask: 0xffffffffffffff max_cycles: 0x1d854df40, max_idle_ns: 3526361616960 ns > 39.9 [wifi] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns > 39.9 [wifi] NET: Registered PF_NETLINK/PF_ROUTE protocol family > 39.9 [wifi] clocksource: Switched to clocksource dde_counter > 39.9 [wifi] pci_iomap: request for dev: 00:14.3 bar: 0 > 39.9 [wifi] iwlwifi 00:14.3: pci_enable_msi failed - -38 > 39.9 [wifi] task_work_add: task: 00000000002bc000 work: 00000000412fee20 notify: 0 > 39.9 [model_query] e[34mWarning: ack for unknown File_system handle 876e[0m > 39.9 [wifi] iwlwifi 00:14.3: Detected crf-id 0x2816, cnv-id 0x1000100 wfpm id 0x80000000 > 39.9 [wifi] iwlwifi 00:14.3: PCI dev 9df0/0030, rev=0x312, rfid=0x105110 > 39.9 [wifi] iwlwifi 00:14.3: Detected Intel(R) Wireless-AC 9560 160MHz > 39.9 [wifi] NET: Registered PF_PACKET protocol family > 39.9 [wifi] sched_clock: Marking stable (19386000, 19900000)->(76970000, -37684000) > 39.9 [wifi] reg: Loading compiled-in X.509 certificates for regulatory database > 39.9 [wifi] e[34mWarning: /dev/rtc not readable, returning 0e[0m > 39.9 [wifi] iwlwifi 00:14.3: WRT: Overriding region id 0 > 39.9 [wifi] iwlwifi 00:14.3: WRT: Overriding region id 1 > 39.9 [wifi] iwlwifi 00:14.3: WRT: Overriding region id 2 > 39.9 [wifi] iwlwifi 00:14.3: WRT: Overriding region id 3 > 39.9 [wifi] iwlwifi 00:14.3: WRT: Overriding region id 4 > 39.9 [wifi] iwlwifi 00:14.3: WRT: Overriding region id 6 > 39.9 [wifi] iwlwifi 00:14.3: WRT: Overriding region id 8 > 39.9 [wifi] iwlwifi 00:14.3: WRT: Overriding region id 9 > 39.9 [wifi] iwlwifi 00:14.3: WRT: Overriding region id 10 > 39.9 [wifi] iwlwifi 00:14.3: WRT: Overriding region id 11 > 39.9 [wifi] iwlwifi 00:14.3: WRT: Overriding region id 15 > 39.9 [wifi] iwlwifi 00:14.3: WRT: Overriding region id 16 > 39.9 [wifi] iwlwifi 00:14.3: WRT: Overriding region id 18 > 39.9 [wifi] iwlwifi 00:14.3: WRT: Overriding region id 19 > 39.9 [wifi] iwlwifi 00:14.3: WRT: Overriding region id 20 > 39.9 [wifi] iwlwifi 00:14.3: WRT: Overriding region id 21 > 39.9 [wifi] iwlwifi 00:14.3: WRT: Overriding region id 28 > 39.9 [wifi] iwlwifi 00:14.3: loaded firmware version 46.6b541b68.0 9000-pu-b0-jf-b0-46.ucode op_mode iwlmvm > 39.9 [wifi] reg: loaded regulatory.db is malformed or signature is missing/invalid > 40.0 [wifi] iwlwifi 00:14.3: base HW address: 50:e0:85:82:2f:f8, OTP minor version: 0x4 > 40.0 [wifi] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs' > 40.3 [wifi] l2_packet_linux: setsockopt(SO_ATTACH_FILTER) failed: No such file or directory > 40.3 [wifi] e[34mWarning: Libc RNG not configurede[0m > 66.2 [leitzentrale -> nitpicker] e[34mWarning: Gui (wm -> runtime_view -> runtime) not enough RAM to preserve buffer content during resizee[0m > > ``` ---
**Author:** ![chelmuth](https://dub1.discourse-cdn.com/flex006/user_avatar/genode.discourse.group/chelmuth/32/1_2.png) [@chelmuth](https://genode.discourse.group/u/chelmuth)\ **Post date:** [June 5, 2026, 9:03am UTC](https://genode.discourse.group/t/sculpt-26-04-release-candidates/308/38 "2026-06-05T09:03:02Z")
Sorry, I have to correct myself. According to @jws your wifi card is not CNVi and should work. ---
**Author:** ![chelmuth](https://dub1.discourse-cdn.com/flex006/user_avatar/genode.discourse.group/chelmuth/32/1_2.png) [@chelmuth](https://genode.discourse.group/u/chelmuth)\ **Post date:** [June 5, 2026, 9:04am UTC](https://genode.discourse.group/t/sculpt-26-04-release-candidates/308/39 "2026-06-05T09:04:36Z")
> [@Nos](#): > > I tried to use wifi at the X390 Yoga for several times now. So you own two Yoga devices X380 and X390? ---
**Author:** ![Nos](https://avatars.discourse-cdn.com/v4/letter/n/eb9ed0/32.png) [@Nos](https://genode.discourse.group/u/Nos)\ **Post date:** [June 5, 2026, 9:13am UTC](https://genode.discourse.group/t/sculpt-26-04-release-candidates/308/40 "2026-06-05T09:13:04Z")
> [@chelmuth](#): > > So you own two Yoga devices X380 and X390? The X390 Yoga should actually be an upgraded X380 Yoga but to my surprise it is the newer X390 Yoga. [Previous page](https://genode.discourse.group/t/sculpt-26-04-release-candidates/308.md?page=1) [Next page](https://genode.discourse.group/t/sculpt-26-04-release-candidates/308.md?page=3)