Page 1 of 1
MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Wed Mar 26, 2025 6:13 pm
by AVLinux
Hi,
*RC2 has been uploaded please carry on in the RC2 thread. viewtopic.php?t=84298
After many months of testing and consultation with developers ylee and the_waiter from Bodhi Linux I'm very happy to present the first RC1 Testing ISO for the Moksha Desktop Environment on MX Linux; MX Moksha "Out of Bodhi" RC1. As always credit, thanks and great appreciation to the MX Linux developers for the 'build-iso-mx' build system.
For those who are not aware Bodhi Linux is a unique, light and fast Linux Distribution that has carved out a popular niche with it's attractive 'Moksha' Desktop Environment which was forked from Enlightenment E17. For those acquainted with Enlightenment Moksha is quite familiar and has added it's own features, fixes and improvements to the original E17 base. E17 was Iconic for it's uniquely skeumorphic and textural appearance and Bodhi carries on in this vein as an attractive alternative to the current ubiquitous Flat theming trends. It seemed to me Bodhi's uniqueness and the robust stability and toolset of MX would make an excellent hybrid and I was very pleasantly surprised to receive not only a warm welcome from the Bodhi developers but also a helpful and collaborative spirit which had not really been my experience with Enlightenment. Bodhi had already made inroads to moving from a Ubuntu base to also supporting Debian with their recent 'deBodhi 7' release and with some help from ylee I was able to incorporate deBodhi with MX and produce a working build-iso template which has gotten things this far. Essentially this ISO is a Base release with the bare elements of Bodhi Linux 7 and it's Moksha Desktop Environment + MX Linux Tools, AHS Repo and Build system + AV Linux Tweaks, Utilities and File Actions. Other key differences are PipeWire by default and the solid Liquorix 6.6.12 Kernel.
An obvious question is probably how this relates to AV Linux and the answer is not yet known, there are Pros and Cons and as much as I love the 'pure' Enlightenment Desktop Environment there is no real interest from the Enlightenment developer in facilitating deployment of Enlightenment on an ISO or seemingly in furthering it's usage popularity in general. He is a brilliant developer and has invested many years of ingenious work into Enlightenment with a relatively small number of major collaborators and his project is his prerogative and I have come to accept that for what it is. It is promising to me that Moksha is quite similar to Enlightenment and even more resource efficient and that it's developers are open to collaboration and keen to help with potential obstacles to deploying it so I am hopeful that this may be a good match but at the end of the day AV Linux needs to be a reliable workstation platform and until I have a few releases and lots of testing feedback under my belt it's too soon to commit to a future change.
MX Moksha custom theme to complement Bodhi's signature 'Moksha Green' look with a custom Skewaita GTK theme.
MX Moksha with AVL's PipeWire, Yabridge/Wine-Staging setup by default.
AVL's handy and File Manager agnostic Custom Actions are also included with Thunar as the default File Manager.
KNOWN ISSUES:
- As with Enlightenment currently the keyboard settings are not carried through from the Live session to the Install.
- Non-English Users will need to manually set their Moksha keyboard setting from the keyboard applet on the Panel (shelf) once logged in to a fresh install.
*Keyboard setting will be worked on before a final release.
- Live boot has a several second delay from GRUB to the Moksha Desktop loading, this is expected and performance is normal once Desktop loads.
- Currently UI scaling to values higher than the default 1.2 X in Moksha doesn't adjust GTK and Qt apps, this is being worked on, you may find 'DPI' scaling to work better in the meantime on HiDPI didplays
DOWNLOAD IS HERE:
https://downloads.bandshed.net/MX-MOKSHA/
Please post questions, issues and observations in this thread.
This is a preliminary RC Release to find bugs and incompatibility issues, I don't suggest this as a production system yet!
You can optionally add and test AV Linux DAW's, NLE's and Plugins from here:
https://bandshed.net/packages/AVL_MXe-23.X/
*DO NOT install packages from the 'SYSTEM_DEV' folder!
*ADDED NOTES
Some things that have been mentioned in feedback can be controlled in Moksha with it's Environment Variables dialog,
- GTK font scaling can be controlled with a GDK_DPI_SCALE variable, as an example if Moksha is set at 1.5 X scaling a GDK_DPI_SCALE value of 1.2 is an approximate match.
* GTK scaling is being worked on, this is a temp workaround
- The systray width in Moksha can be controlled with a MOKSHA_SYSTRAY_SPACING variable
When entering a variable enter the variable name in the left text box and the value in the right text box the '=' will be automatically formatted.
Screenshot showing Environment Variables dialog with the latest 'Zenithal' rounded Moksha theme which has not been released yet..
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Wed Mar 26, 2025 6:24 pm
by hugok
Nice @AVLinux I'll try it out when I get a chance! Great work :^)
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Wed Mar 26, 2025 7:02 pm
by AVLinux
hugok wrote: Wed Mar 26, 2025 6:24 pm
Nice @AVLinux I'll try it out when I get a chance! Great work :^)
Thanks very much!
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Thu Mar 27, 2025 5:48 pm
by Germ
Looks good! Very well done. I like Moksha but never cared for Bodhi.
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Thu Mar 27, 2025 6:27 pm
by AVLinux
Thanks, the Moksha themes and modules are all available to be installed, the utility stuff MX Tools, MXPI and apt-notifier are all present from MX so visually it's like Bodhi but under the hood it's MX.
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Thu Mar 27, 2025 7:05 pm
by Nokkaelaein
I'm not at all familiar with Moksha, and this does look really good, congrats. It's much more up my alley than the current Enlightenment vibe.
(And all in all, I'm quite a die hard Fluxbox user and customizer :P and prefer sleek, minimal environments. But I do also like building the Fluxbox experience so that I can, for example, use actual graphical alt-tabbing, minimize/iconify windows to the system tray on the fly to declutter the taskbar, have tasteful unobtrusive animations for some window actions with picom, and so on and so forth.)
How's the resource usage with Moksha compared to something like Fluxbox or the current AV Linux Enlightenment configuration? [Edit: coming from the realtime audio angle, I'm especially interested in CPU spikes and such, and the suitability of it all for low latency audio... instead of RAM figures and so on :) - well you know exactly what I mean, Im sure. ] What compositor does this use by default?
Seems very promising, good luck with the project, and thanks for experimenting with stuff like this and showcasing the findings!
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Thu Mar 27, 2025 7:24 pm
by AVLinux
Nokkaelaein wrote: Thu Mar 27, 2025 7:05 pm
I'm not at all familiar with Moksha, and this does look really good, congrats. It's much more up my alley than the current Enlightenment vibe.
(And all in all, I'm quite a die hard Fluxbox user and customizer :P and prefer sleek, minimal environments. But I do also like building the Fluxbox experience so that I can, for example, use actual graphical alt-tabbing, minimize/iconify windows to the system tray on the fly to declutter the taskbar, have tasteful unobtrusive animations for some window actions with picom, and so on and so forth.)
How's the resource usage with Moksha compared to something like Fluxbox or the current AV Linux Enlightenment configuration? [Edit: coming from the realtime audio angle, I'm especially interested in CPU spikes and such, and the suitability of it all for low latency audio... instead of RAM figures and so on :) - well you know exactly what I mean, Im sure. ] What compositor does this use by default?
Seems very promising, good luck with the project, and thanks for experimenting with stuff like this and showcasing the findings!
Moksha is quite efficient even more so than Enlightenment however my development box has a lot of RAM (96Gb) and with any and all DE's I don't seem to get the record breaking numbers because it seems if RAM is plentiful more gets used and I find VM's can be a bit variable in reporting actual RAM usage accurately. That said there are plenty of folks out there reporting 250-300Mb of RAM usage with 64bit Moksha and significantly less with 32bit. So you could probably safely say about 100Mb higher than Fluxbox on the average. There are numerous YT Videos of people installing Bodhi Linux on pretty ancient netbooks and having them perform very well.
Unlike Enlightenment which IMHO has excellent compositing Moksha comes without compositing by default but they have a picom module that can be installed optionally which gives the expected results with picom. I haven't tested it extensively because at this point I have no bare metal MX Moksha installs to really put everything through it's paces so I also have not pressure tested Moksha for Audio production but I'm hoping to get some feedback from this RC release and I will probably replace Enlightenment on my laptop with Moksha once a final release is close at hand.
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Thu Mar 27, 2025 7:32 pm
by Nokkaelaein
Yep, thinking along the same lines, about RAM being plentiful and all that: when wanting to run an audio system, the RAM differences of small(ish) environments like this are pretty much of no consequence if the computer is up to scratch with running the actual audio software anyway - but if the environment itself occasionally does something that hogs the CPU even for a blink of an eye, and does that by design, it's a no go (imo, for that kind of use case).
Ah okay, it's tested with picom by default... Thanks. Yeah, I'm definitely keeping this on my radar, it's an interesting one for designing a desktop experience for a daily driver, if it's readily available for MX like this.
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Thu Mar 27, 2025 7:47 pm
by AVLinux
Nokkaelaein wrote: Thu Mar 27, 2025 7:32 pm
Yep, thinking along the same lines, about RAM being plentiful and all that: when wanting to run an audio system, the RAM differences of small(ish) environments like this are pretty much of no consequence if the computer is up to scratch with running the actual audio software anyway - but if the environment itself occasionally does something that hogs the CPU even for a blink of an eye, and does that by design, it's a no go (imo, for that kind of use case).
Ah okay, it's tested with picom by default... Thanks. Yeah, I'm definitely keeping this on my radar, it's an interesting one for designing a desktop experience for a daily driver, if it's readily available for MX like this.
Looking forward they already have Bodhi/Moksha tested and running on a Debian Trixie base so that variable is figured out, there is no Wayland support (nor will there be in Fluxbox I suppose) and no real Roadmap for Wayland in Moksha (yet). Enlightenment does have Wayland support (I have not tested it myself). In the production sphere the whole thing annoys me to death especially when every major DAW is currently built with intended X11 use except Studio One and their kludgy Plugin Xwayland wrapper.. Like PipeWire another major premature distraction whipping up M.U.D. (Manic Upgrade Disorder) and misinformation making Linux look like a sketchy and confusing production platform yet again..
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Thu Mar 27, 2025 11:20 pm
by sunrat
Booted it live in virt-manager. Seems to work nicely in a quick perusal. Posting now from Firefox in it. RAM use about 350MB after boot, very good. Graphics are a bit blurry in VM.
I have Bodhi installed to metal but never boot it because ubuntu. May try putting this over it instead which should provide better graphics.
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Fri Mar 28, 2025 1:11 am
by AVLinux
sunrat wrote: Thu Mar 27, 2025 11:20 pm
Booted it live in virt-manager. Seems to work nicely in a quick perusal. Posting now from Firefox in it. RAM use about 350MB after boot, very good. Graphics are a bit blurry in VM.
I have Bodhi installed to metal but never boot it because ubuntu. May try putting this over it instead which should provide better graphics.
Hi sunrat!
Thanks a lot for checking it out, I appreciate it!
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Fri Mar 28, 2025 1:33 am
by FullScale4Me
I just gave it a quick try in Virtual Box:
Nice grub menu theming - Is there any way to change Debian to MX Moksha?
Neofetch is present but the newer fastfetch is not. Neofetch gives a logo I don't recognize (I'm not a distro hopper). fastfetch gives a lot more (useful) info IMHO.
smbclient, useful for samba troubleshooting is not present.
Taskbar stuff overlaps the system updater icon when the systray is opened. Can a spacer be added? The icon says wireframe in preferences but visually isn't the MX one. Is it supposed to look like a black checkmark on a white circle?
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Fri Mar 28, 2025 7:32 am
by Senpai
AVLinux wrote: Wed Mar 26, 2025 6:13 pm
Hi,
After many months of testing and consultation with developers ylee and the_waiter from Bodhi Linux I'm very happy to present the first RC1 Testing ISO for the Moksha Desktop Environment on MX Linux; MX Moksha "Out of Bodhi" RC1. As always credit, thanks and great appreciation to the MX Linux developers for the 'build-iso-mx' build system.
You can optionally add and test AV Linux DAW's, NLE's and Plugins from here:
https://bandshed.net/packages/AVL_MXe-23.X/
*DO NOT install packages from the 'SYSTEM_DEV' folder!
Hi AVLinux:
Just 15 days ago I'm playing with a respin of MX-Moksha
I hadn't seen anything on the forum... I don't follow your respin very much because I differentiate music from noise and little else... hahahaha
I liked it Moksha, it's nothing like what you are doing, compiling the ISO from the template, not even close, hahaha,
I just tried adding the Bodhi repository, as in my Cinnamon and ParrotOS respin, I installed Moksha, I also tried the Debian script that the Bodhi developers provide at
https://github.com/BodhiDev/Distros/blo ... install.sh, I like how it looks, a pity that Moksha doesn't work with the MX system-shim either, but it works fine with systemd.
I have installed your beta, and it looks great, I haven't tested it in depth yet, but I love how it looks and the plugins you have created for Thunar, congratulations
, is there any chance you can create some respin for normal MX-Moksha use, without so many audio/video specific programs and plugins....
Best regards
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Fri Mar 28, 2025 8:56 am
by AVLinux
FullScale4Me wrote: Fri Mar 28, 2025 1:33 am
I just gave it a quick try in Virtual Box:
Nice grub menu theming - Is there any way to change Debian to MX Moksha?
Neofetch is present but the newer fastfetch is not. Neofetch gives a logo I don't recognize (I'm not a distro hopper). fastfetch gives a lot more (useful) info IMHO.
smbclient, useful for samba troubleshooting is not present.
Taskbar stuff overlaps the system updater icon when the systray is opened. Can a spacer be added? The icon says wireframe in preferences but visually isn't the MX one. Is it supposed to look like a black checkmark on a white circle?
Hi, thanks for taking a look!
Yep, the GRUB name is a finishing detail I've missed, will fix for future releases.
I think they are working in an updated fastfetch logo, the leaf of the bodhi tree is the Bodhi Linux logo TBH I don't delve into the 'fetches' a lot, if fastfetch is in MX main I will swap them out
mx-updater; Enlightenment had a weird quirk with some colored Icons in the systray so I made my own and prefer them so I put them in the Moksha spin, Moksha has a different systray than Enlightenment and it seems to only expand so big, will ask them about that.
If you want the OG mx-updater Icons just uninstall my 'apt-notifier-custom-icons' package and you will get the OG Icons back
Any suggestions for networking stuff are welcome, I suck at networking so I'll add smbclient to the installed packages.
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Fri Mar 28, 2025 9:05 am
by AVLinux
@Senpai
Great to hear you were also working on Moksha, you do excellent work with all of your Respins! I had ylee make a few changes to that script you linked because there were a few minor places that Bodhi and MX packages could interfere, I think it is pretty good now so yes it it is easy to get vanilla Moksha on an MX system with the script for sure.
The File Actions are designed to work with any File Manager so they are different than actual Thunar-specific Custom Actions but if you want to go to a default MX setup you can simply uninstall my 'mx-moksha-file-actions' package and then install 'thunar-custom-actions-mx' and my actions will be removed and it will be like default MX
I usually try as much as possible to make my customizations as external Debs so they can be added and removed.
Please don't be discouraged if you want to finish your own Moksha Respin and put it here, I'm not competing with anyone and my Spins are never 'pure' they have my dirty fingerprints all over the place.. as an example @user-green also puts up Enlightenment spins here and I think that is great, the more choice the better!
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Fri Mar 28, 2025 11:36 am
by Gabriel_M
Perhaps because I started out with Linux with Slackware, I opted for XFCE with a graphical environment many years ago.
As a serial tester, I've installed countless distributions with different graphical environments through Virtualbox, but none (except Void Linux) or any graphical environment has caught my attention.
I must congratulate you on your brilliant development; this MX Linux respin is very nice and looks great.
Just two questions: How do I change the screen size (in Virtualbox, the screen size is awkward, and the horizontal bar may be vertical, just like MX Linux XFCE).
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Fri Mar 28, 2025 11:50 am
by AVLinux
Gabriel_M wrote: Fri Mar 28, 2025 11:36 am
Perhaps because I started out with Linux with Slackware, I opted for XFCE with a graphical environment many years ago.
As a serial tester, I've installed countless distributions with different graphical environments through Virtualbox, but none (except Void Linux) or any graphical environment has caught my attention.
I must congratulate you on your brilliant development; this MX Linux respin is very nice and looks great.
Just two questions: How do I change the screen size (in Virtualbox, the screen size is awkward, and the horizontal bar may be vertical, just like MX Linux XFCE).
Hi, thanks!
Screen settings are handled by arandr with a patched feature to save it's config in Moksha's startup so;
Menu-->Applications-->Preferences-->Monitor settings.
Right-click on the UI to and select Resolution to change the screen size, leftmost button to apply and rightmost button to save to Moksha startup
To change the Panel position or "shelf' right-click on the panel and a 'shelf' menu item should pop up and take you to a list including 'orientation' where you can change the position.
*Note you will likely want to also go into the shelf Settings menu and in the Size tab uncheck "Shrink to content width" as well
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Fri Mar 28, 2025 2:42 pm
by Senpai
AVLinux wrote: Wed Mar 26, 2025 6:13 pm
Hi,
Hi AVLinux:
Just 15 days ago I'm playing with a respin of MX-Moksha
I hadn't seen anything on the forum... I don't follow your respin very much because I differentiate music from noise and little else... hahahaha
I liked it Moksha, it's nothing like what you are doing, compiling the ISO from the template, not even close, hahaha,
I just tried adding the Bodhi repository, as in my Cinnamon and ParrotOS respin, I installed Moksha, I also tried the Debian script that the Bodhi developers provide at
https://github.com/BodhiDev/Distros/blo ... install.sh, I like how it looks, a pity that Moksha doesn't work with the MX system-shim either, but it works fine with systemd.
I have installed your beta, and it looks great, I haven't tested it in depth yet, but I love how it looks and the plugins you have created for Thunar, congratulations
, is there any chance you can create some respin for normal MX-Moksha use, without so many audio/video specific programs and plugins....
Best regards
Hi:
In the Debian script, I found some typos in lines 64, 98, 105 and 108, just some incorrect spaces, I corrected them and the script worked without problems.
I tried to pass the problem on Github, but I'm a mess and I do not know if I did well the error notice, but well, I have also passed it on the Bodhi forum to see if they can fix it.
Edited:
Just to be clear, the Debian script, works perfectly by cloning the repository.... My mistake .
Best regards
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Fri Mar 28, 2025 4:45 pm
by Stevo
Yes, fastfetch 2.33.0 is in MX 23 main, 2.35.0 in test.
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Fri Mar 28, 2025 7:44 pm
by AVLinux
Stevo wrote: Fri Mar 28, 2025 4:45 pm
Yes, fastfetch 2.33.0 is in MX 23 main, 2.35.0 in test.
Good to know thanks, will switch..
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Fri Mar 28, 2025 11:54 pm
by Stevo
It certainly can display quite a bit!
Code: Select all
$ fastfetch -c all.jsonc
steve@dellmx23
--------------
MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMNMMMMMMMMM OS: MX 23.3 Libretto x86_64
MMMMMMMMMMNs..yMMMMMMMMMMMMMm: +NMMMMMMM Host: Dell G15 5515 (1.4.0)
MMMMMMMMMN+ :mMMMMMMMMMNo` -dMMMMMMMM Bios (UEFI): 1.4.0 (5.3)
MMMMMMMMMMMs. `oNMMMMMMh- `sNMMMMMMMMM Board: 00VT1V (A04)
MMMMMMMMMMMMN/ -hMMMN+ :dMMMMMMMMMMM Chassis: Notebook (1.4.0)
MMMMMMMMMMMMMMh- +ms. .sMMMMMMMMMMMMM Kernel: Linux 6.1.0-32-amd64
MMMMMMMMMMMMMMMN+` ` +NMMMMMMMMMMMMMM Init System: systemd 1:252.6-1mx23+1
MMMMMMMMMMMMMMNMMd: .dMMMMMMMMMMMMMMM Uptime: 1 day, 12 hours
MMMMMMMMMMMMm/-hMd- `sNMMMMMMMMMMMMM Loadavg: 1.92, 1.86, 1.46
MMMMMMMMMMNo` -` :h/ -dMMMMMMMMMMMM Processes: 431
MMMMMMMMMd: /NMMh- `+NMMMMMMMMMM Packages: 4910 (dpkg), 11 (flatpak)
MMMMMMMNo` :mMMN+` `-hMMMMMMMM Shell: bash 5.2.15
MMMMMMh. `oNMMd: `/mMMMMMM Display (CS27QH): 2560x1440 @ 144 Hz in 27" [External]
MMMMm/ -hMd- `sNMMMM Brightness (ddcci7): 50%
MMNs` - :dMMM Brightness (amdgpu_bl0): 50%
Mm: `oMM Monitor (CS27QH): 2560x1440 px @ 143.999 Hz - 600x330 mm (26.96 inches, 108.95 ppi) [HDR Compatible]
MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM LM: sddm 0.19.0 (Wayland)
DE: KDE Plasma 5.27.5
WM: KWin (Wayland)
WM Theme: phuturista-gamer-blue-animated
Theme: KvDarkRed (KvArcDark) [Qt], MX3 [GTK2/3/4]
Icons: Gradient-Dark-Icons [Qt], Gradient-Dark-Icons [GTK2/3/4]
Font: Droid Sans Fallback (12pt) [Qt], Droid Sans Fallback (12pt) [GTK2/3/4]
Cursor: Sweet (36px)
Wallpaper: variety-copied-wallpaper-1dae9bd4643593d50fe5e0c57c25eb19.jpg
Terminal: konsole 22.12.3
Terminal Font: Hack (13pt)
Terminal Size: 146 columns x 25 rows (1466px x 526px)
Terminal Theme: #FCFCFC (FG) - #16162E (BG) [Dark]
CPU: AMD Ryzen 7 5800H (16) @ 3.20 GHz - 59.8°C
CPU Cache (L1): 8x32.00 KiB (D), 8x32.00 KiB (I)
CPU Cache (L2): 8x512.00 KiB (U)
CPU Cache (L3): 16.00 MiB (U)
CPU Usage: 2%
GPU 1: NVIDIA GeForce RTX 3050 Ti Laptop GPU (2560) @ 2.10 GHz - 54.0°C (7.25 MiB / 3.81 GiB, 0%) [Discrete]
GPU 2: AMD Radeon Graphics (8) @ 2.00 GHz - 53.0°C [Integrated]
Memory: 11.06 GiB / 30.70 GiB (36%)
Swap: 20.00 MiB / 13.65 GiB (0%)
Disk (/): 82.44 GiB / 190.60 GiB (43%) - ext4
Disk (/home): 502.60 GiB / 693.30 GiB (72%) - ext4
Battery (0x4D,0x31,0x43,0x50,0x69,0x03,0): 100% [AC Connected]
Media Player: SMPlayer
Media: The Scathing Atheist - 630: Mercola Tapes Edition (Stopped)
Public IP: 37.19.221.235 (Houston, US)
Local IP (wlan0): 192.168.0.195/24 2607:fb91:1b0e:1231:8ebb:6df2:b1d8:bd71/64,fe80::fcf:a623:2626:79e1/64 (cc:15:31:78:32:f5) [MTU 1500] <UP,BROADCAST,RUNNING,MULTICAST,LOWER_UP>
DNS: 10.2.0.1 2a07:b944::2:1
Wifi: Franklin T10 2425 5G - 802.11ac (Wi-Fi 5) - 5 GHz - WPA2 (84%)
Date & Time: 2025-03-28 20:49:58
Locale: en_US.UTF-8
Vulkan: 1.3.289 - radv [Mesa 24.2.8-1mx23ahs]
OpenGL: 4.6.0 NVIDIA 535.216.03
OpenCL: 1.1 Mesa 24.2.8-1mx23ahs
Users: steve - login time 2025-03-27 08:49:28
Bluetooth 1: T17 (100%)
Bluetooth 2: BT5.0 Mouse (94%)
Bluetooth Radio (dellmx23): Unknown
Sound: T17 (66%)
Camera: Integrated_Webcam_HD: Integrate - sRGB (1280x720 px)
Weather: +11°C - Partly cloudy (not found)
Network IO (wlan0): 2.40 KiB/s (IN) - 2.66 KiB/s (OUT)
Disk IO (ADATA LEGEND 700): 46.43 MiB/s (R) - 128.00 KiB/s (W)
Physical Disk (ADATA LEGEND 700): 953.87 GiB [SSD, Fixed] - 43.9°C
TPM: TPM 2.0 Device
Version: fastfetch 2.35.0-debug (x86_64)
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Sat Mar 29, 2025 3:10 am
by sunrat
Stevo wrote: Fri Mar 28, 2025 11:54 pm
It certainly can display quite a bit!
inxi is still much better, particularly for posting to forums in support questions. ASCII logo is just eye candy and pointless for that scenario.
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Sat Mar 29, 2025 7:33 am
by ylee2130
Senpai wrote: Fri Mar 28, 2025 2:42 pm
...
Hi:
In the Debian script, I found some typos in lines 64, 98, 105 and 108, just some incorrect spaces, I corrected them and the script worked without problems.
I tried to pass the problem on Github, but I'm a mess and I do not know if I did well the error notice, but well, I have also passed it on the Bodhi forum to see if they can fix it.
Best regards
Thanks for the interest in my script but those spaces are not errors, Whitespace matters in shell scripts.
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Sat Mar 29, 2025 7:51 am
by Senpai
ylee2130 wrote: Sat Mar 29, 2025 7:33 am
Senpai wrote: Fri Mar 28, 2025 2:42 pm
...
Hi:
In the Debian script, I found some typos in lines 64, 98, 105 and 108, just some incorrect spaces, I corrected them and the script worked without problems.
I tried to pass the problem on Github, but I'm a mess and I do not know if I did well the error notice, but well, I have also passed it on the Bodhi forum to see if they can fix it.
Best regards
Thanks for the interest in my script but those spaces are not errors, Whitespace matters in shell scripts.
Hi:
Thank you for this work.
As I say I have no idea of programming, nor of scritp
I only know, that the downloaded scritp gave me errors in those lines when executing it, and when I corrected it as I showed, it executed without problems in my respin, I have no idea why it gives me errors, nor why running those spaces worked...
but it worked...
Edited:
Just to be clear, the Debian script, works perfectly by cloning the repository.... My mistake .
Best regards
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Sat Mar 29, 2025 9:45 am
by ylee2130
Senpai wrote: Sat Mar 29, 2025 7:51 am
...
Hi:
Thank you for this work.
As I say I have no idea of programming, nor of scritp
I only know, that the downloaded scritp gave me errors in those lines when executing it, and when I corrected it as I showed, it executed without problems in my respin, I have no idea why it gives me errors, nor why running those spaces worked...
but it worked...
Best regards
This is slightly off-topic, but I would have to look at your "respin" to see why. Perhaps it actually failed to make the temp dir. To avoid spamming this thread with off-topic stuff send me an email if possible, It would nice to make sure the script works in this kind of usage.
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Sat Mar 29, 2025 10:01 am
by AVLinux
@ylee2130
Great to see you here! (ylee is Bodhi lead dev)
I can retest the script in a VM today if that will help clarify. I did use it in the past successfully but not the latest update. At this point I have a build template from scratch and I used the script for package names and repo URL etc. Will test and post back later today..
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Sat Mar 29, 2025 10:02 am
by Stevo
sunrat wrote: Sat Mar 29, 2025 3:10 am
Stevo wrote: Fri Mar 28, 2025 11:54 pm
It certainly can display quite a bit!
inxi is still much better, particularly for posting to forums in support questions. ASCII logo is just eye candy and pointless for that scenario.
2.39.1 lists 474 logos built in, but AVLinux is not included. Good reason to leave it off! (There are three MX logos)
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Sat Mar 29, 2025 10:09 am
by AVLinux
Stevo wrote: Sat Mar 29, 2025 10:02 am
sunrat wrote: Sat Mar 29, 2025 3:10 am
Stevo wrote: Fri Mar 28, 2025 11:54 pm
It certainly can display quite a bit!
inxi is still much better, particularly for posting to forums in support questions. ASCII logo is just eye candy and pointless for that scenario.
2.39.1 lists 474 logos built in, but AVLinux is not included. Good reason to leave it off! (There are three MX logos)
I've never submitted one or even looked into it, to Debian I'm likely a b*st*rd stepchild. The Audio geeks and DW know I'm alive but I rarely see AVL mentioned or the logo in any of the usual cool kid listings...lol.
Any budding ascii artists out there want to take a shot? I can provide full size png or svgs.
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Sat Mar 29, 2025 10:51 am
by AVLinux
@Senpai @ylee2130
Further to the script discussion,
I just installed MX-23 (the systemd Respin by
@dolphin_oracle since I know Bodhi is geared to systemd ) I grabbed the Bodhi bookworm script and it ran fine for me except for an error that I missed previously which has probably been there since the beginning since both MX and Bodhi both use Thunar.
There is a conflict with Thunar's accels file but it doesn't prevent the script from finishing.
Code: Select all
dpkg: error processing archive /var/cache/apt/archives/bodhi-skel_1.5-8_all.deb (--unpack):
trying to overwrite '/etc/skel/.config/Thunar/accels.scm', which is also in package desktop-default
s-mx-xfce-desktop 23.12.06mx23
Errors were encountered while processing:
/var/cache/apt/archives/bodhi-skel_1.5-8_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
This is a side issue from the original problem, for me the script itself ran and completed.
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Sat Mar 29, 2025 12:11 pm
by Senpai
ylee2130 wrote: Sat Mar 29, 2025 9:45 am
Senpai wrote: Sat Mar 29, 2025 7:51 am
...
Hi:
Thank you for this work.
As I say I have no idea of programming, nor of scritp
I only know, that the downloaded scritp gave me errors in those lines when executing it, and when I corrected it as I showed, it executed without problems in my respin, I have no idea why it gives me errors, nor why running those spaces worked...
but it worked...
Best regards
This is slightly off-topic, but I would have to look at your "respin" to see why. Perhaps it actually failed to make the temp dir. To avoid spamming this thread with off-topic stuff send me an email if possible, It would nice to make sure the script works in this kind of usage.
I sent it to you by private message. I forgot to say that since Moksha does not work with MX systemd-shim, I remove it and just leave Systemd....
Best regards
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Sat Mar 29, 2025 2:38 pm
by trawglodyte
I love Moksha and MX-Linux, thanks to @AVLinux @Senpai @ylee2130 and everyone involved in doing this! Although I've gotten accustomed to XFCE, I look forward to switching over to Moksha.
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Sat Mar 29, 2025 2:57 pm
by AVLinux
trawglodyte wrote: Sat Mar 29, 2025 2:38 pm
I love Moksha and MX-Linux, thanks to @AVLinux @Senpai @ylee2130 and everyone involved in doing this! Although I've gotten accustomed to XFCE, I look forward to switching over to Moksha.
That's great to hear, from the moment I tried Moksha over a year ago I thought it would be a perfect fit with MX too. Some bugs to work out and features to improve but the Bodhi devs are onboard and the proof of concept ISO is working so just Devil-in-the-details from here on.. Hoping to complete an RC2 next week..
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Sat Mar 29, 2025 5:15 pm
by kmathern
I'm unable to connect via wifi with the 6.6.12-1-liquorix-amd64 kernel.
Here's a QSI
Code: Select all
System:
Kernel: 6.6.12-1-liquorix-amd64 [6.6-16~mx23ahs] arch: x86_64 bits: 64 compiler: gcc
v: 12.2.0 parameters: audit=0 intel_pstate=disable rcupdate.rcu_expedited=1
BOOT_IMAGE=(loop)/antiX/vmlinuz
buuid=72c84fb0-f541-4393-93b5-2db0d93d2c7c
fromiso=/MX_MOKSHA-23-RC1_x64.iso quiet splasht nosplash kbd=us
lang=en_US tz=America/New_York splasht= live_swap=off
Desktop: Moksha v: 0.4.1.18373 vt: 7 dm: LightDM v: 1.32.0
Distro: MX_MOKSHA-23-RC1_x64 Out of Bodhi TBD base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Desktop System: AZW product: EQ v: N/A serial: <superuser required>
Mobo: AZW model: EQ serial: <superuser required> UEFI: American
Megatrends LLC. v: N95V106 date: 12/15/2023
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard serial: <filter>
charge: 55% (should be ignored) rechargeable: yes status: discharging
CPU:
Info: model: Intel N100 bits: 64 type: MCP arch: Alder Lake level: v3
note: check built: 2021+ process: Intel 7 (10nm ESF) family: 6
model-id: 0xBE (190) stepping: 0 microcode: 0xE
Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 384 KiB
desc: d-4x32 KiB; i-4x64 KiB L2: 2 MiB desc: 1x2 MiB L3: 6 MiB desc: 1x6 MiB
Speed (MHz): avg: 1365 high: 3058 min/max: 700/801 boost: enabled scaling:
driver: acpi-cpufreq governor: performance cores: 1: 801 2: 801 3: 3058
4: 801 bogomips: 6451
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Alder Lake-N [UHD Graphics] driver: i915 v: kernel
arch: Gen-12.2 process: Intel 10nm built: 2021-22+ ports: active: HDMI-A-1
empty: DP-1,HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:46d1 class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 compositor: enlightenment driver:
X: loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915
display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1600x900 s-dpi: 96 s-size: 423x238mm (16.65x9.37")
s-diag: 485mm (19.11")
Monitor-1: HDMI-A-1 mapped: HDMI-1 model: Acer HX1953L serial: <filter>
built: 2013 res: 1600x900 hz: 60 dpi: 94 gamma: 1.2
size: 432x239mm (17.01x9.41") diag: 494mm (19.4") ratio: 16:9 modes:
max: 1600x900 min: 720x400
API: OpenGL v: 4.6 Mesa 24.2.8-1mx23ahs renderer: Mesa Intel Graphics
(ADL-N) direct-render: Yes
Audio:
Device-1: Intel driver: snd_hda_intel v: kernel
alternate: snd_sof_pci_intel_tgl bus-ID: 00:1f.3 chip-ID: 8086:54c8
class-ID: 0403
API: ALSA v: k6.6.12-1-liquorix-amd64 status: kernel-api
tools: alsamixer,amixer
Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel driver: iwlwifi v: kernel modules: wl port: N/A
bus-ID: 00:14.3 chip-ID: 8086:54f0 class-ID: 0280
IF: wlan0 state: down mac: <filter>
Device-2: Intel Ethernet I225-V driver: igc v: kernel pcie: gen: 2
speed: 5 GT/s lanes: 1 port: N/A bus-ID: 01:00.0 chip-ID: 8086:15f3
class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-3: Intel Ethernet I225-V driver: igc v: kernel pcie: gen: 2
speed: 5 GT/s lanes: 1 port: N/A bus-ID: 02:00.0 chip-ID: 8086:15f3
class-ID: 0200
IF: eth1 state: down mac: <filter>
Bluetooth:
Device-1: Intel AX201 Bluetooth type: USB driver: btusb v: 0.8
bus-ID: 1-10:3 chip-ID: 8087:0026 class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 3.0
lmp-v: 5.2 sub-v: 362e hci-v: 5.2 rev: 362e
Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff
link-mode: peripheral accept service-classes: rendering, capturing, audio,
telephony
Drives:
Local Storage: total: 476.94 GiB used: 20.88 GiB (4.4%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 model: 512GB SSD size: 476.94 GiB
block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4
type: SSD serial: <filter> rev: SN09843 temp: 34.9 C scheme: GPT
Partition:
Message: No partition data found.
Swap:
Kernel: swappiness: 10 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 256 MiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 43.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos:
Packages: pm: dpkg pkgs: 2204 libs: 1249 tools: apt,apt-get,aptitude pm: rpm
pkgs: 0 pm: flatpak pkgs: 0
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/bodhi-repo.list
1: deb http://packages.bodhilinux.com/bodhi bookworm b7debbie
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mirror.math.princeton.edu/pub/mxlinux/mx/repo/ bookworm main non-free
2: deb http://mirror.math.princeton.edu/pub/mxlinux/mx/repo/ bookworm ahs
Info:
Processes: 278 Uptime: 14m wakeups: 2 Memory: 15.4 GiB
used: 2.13 GiB (13.8%) Init: systemd v: 252 target: graphical (5)
default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
Shell: quick-system-in default: Bash v: 5.2.15 running-in: quick-system-in
inxi: 3.3.26
Boot Mode: UEFI
Wifi partly works, my network/router is shown as being available (as well as several others), but it never succeeds in making a connection.
Fwiw I see the same problem with wifi, with the 6.6.12-1-liquorix-amd64 kernel, on my MX23.5-ahs install, on this same N100 based mini-pc.
On the MX23.5-ahs install wifi does work correctly with the linux-image-6.7.12-1-liquorix-amd64 kernel, and newer liquorix kernel versions up to and including 6.13.* .
Here's a dump of some of what I see in dmesg
Code: Select all
demo@mx-moksha-live:~
$ sudo dmesg | grep wlan0 -A9999
[ 310.308052] wlan0: authenticate with 3c:33:32:c1:2c:79
[ 310.313749] wlan0: send auth to 3c:33:32:c1:2c:79 (try 1/3)
[ 310.399815] wlan0: authenticate with 3c:33:32:c1:2c:79
[ 310.400166] wlan0: send auth to 3c:33:32:c1:2c:79 (try 1/3)
[ 310.442419] wlan0: authenticated
[ 310.442834] wlan0: associate with 3c:33:32:c1:2c:79 (try 1/3)
[ 310.495691] wlan0: RX AssocResp from 3c:33:32:c1:2c:79 (capab=0x1131 status=0 aid=10)
[ 310.497073] iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0.
[ 310.497174] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
[ 310.497175] iwlwifi 0000:00:14.3: Transport status: 0x0000004B, valid: 6
[ 310.497176] iwlwifi 0000:00:14.3: Loaded firmware version: 72.daa05125.0 so-a0-hr-b0-72.ucode
[ 310.497177] iwlwifi 0000:00:14.3: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL
[ 310.497178] iwlwifi 0000:00:14.3: 0x00A08200 | trm_hw_status0
[ 310.497179] iwlwifi 0000:00:14.3: 0x00000000 | trm_hw_status1
[ 310.497180] iwlwifi 0000:00:14.3: 0x004D8C8A | branchlink2
[ 310.497181] iwlwifi 0000:00:14.3: 0x004CF116 | interruptlink1
[ 310.497181] iwlwifi 0000:00:14.3: 0x004CF116 | interruptlink2
[ 310.497182] iwlwifi 0000:00:14.3: 0x000151CA | data1
[ 310.497182] iwlwifi 0000:00:14.3: 0x00000010 | data2
[ 310.497183] iwlwifi 0000:00:14.3: 0x00000000 | data3
[ 310.497184] iwlwifi 0000:00:14.3: 0x00000000 | beacon time
[ 310.497184] iwlwifi 0000:00:14.3: 0x110477A5 | tsf low
[ 310.497185] iwlwifi 0000:00:14.3: 0x00000000 | tsf hi
[ 310.497186] iwlwifi 0000:00:14.3: 0x00000000 | time gp1
[ 310.497186] iwlwifi 0000:00:14.3: 0x11052D47 | time gp2
[ 310.497187] iwlwifi 0000:00:14.3: 0x00000001 | uCode revision type
[ 310.497188] iwlwifi 0000:00:14.3: 0x00000048 | uCode version major
[ 310.497188] iwlwifi 0000:00:14.3: 0xDAA05125 | uCode version minor
[ 310.497189] iwlwifi 0000:00:14.3: 0x00000370 | hw version
[ 310.497190] iwlwifi 0000:00:14.3: 0x58C80002 | board version
[ 310.497190] iwlwifi 0000:00:14.3: 0x80CCFF00 | hcmd
[ 310.497191] iwlwifi 0000:00:14.3: 0x24020000 | isr0
[ 310.497191] iwlwifi 0000:00:14.3: 0x61000000 | isr1
[ 310.497192] iwlwifi 0000:00:14.3: 0x48F00002 | isr2
[ 310.497192] iwlwifi 0000:00:14.3: 0x00C3000C | isr3
[ 310.497193] iwlwifi 0000:00:14.3: 0x00000000 | isr4
[ 310.497194] iwlwifi 0000:00:14.3: 0x0102001C | last cmd Id
[ 310.497194] iwlwifi 0000:00:14.3: 0x000151CA | wait_event
[ 310.497195] iwlwifi 0000:00:14.3: 0x00000010 | l2p_control
[ 310.497196] iwlwifi 0000:00:14.3: 0x00018034 | l2p_duration
[ 310.497196] iwlwifi 0000:00:14.3: 0x0000003F | l2p_mhvalid
[ 310.497197] iwlwifi 0000:00:14.3: 0x00CF00F8 | l2p_addr_match
[ 310.497198] iwlwifi 0000:00:14.3: 0x00000009 | lmpm_pmg_sel
[ 310.497198] iwlwifi 0000:00:14.3: 0x00000000 | timestamp
[ 310.497199] iwlwifi 0000:00:14.3: 0x00001030 | flow_handler
[ 310.497249] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
[ 310.497249] iwlwifi 0000:00:14.3: Transport status: 0x0000004B, valid: 7
[ 310.497250] iwlwifi 0000:00:14.3: 0x20101A0D | ADVANCED_SYSASSERT
[ 310.497251] iwlwifi 0000:00:14.3: 0x00000000 | umac branchlink1
[ 310.497251] iwlwifi 0000:00:14.3: 0x8045E934 | umac branchlink2
[ 310.497252] iwlwifi 0000:00:14.3: 0x0106B050 | umac interruptlink1
[ 310.497253] iwlwifi 0000:00:14.3: 0x00000000 | umac interruptlink2
[ 310.497253] iwlwifi 0000:00:14.3: 0x00000006 | umac data1
[ 310.497254] iwlwifi 0000:00:14.3: 0x00000001 | umac data2
[ 310.497255] iwlwifi 0000:00:14.3: 0x00FF0FFF | umac data3
[ 310.497255] iwlwifi 0000:00:14.3: 0x00000048 | umac major
[ 310.497256] iwlwifi 0000:00:14.3: 0xDAA05125 | umac minor
[ 310.497256] iwlwifi 0000:00:14.3: 0x11052D40 | frame pointer
[ 310.497257] iwlwifi 0000:00:14.3: 0xC0886BBC | stack pointer
[ 310.497258] iwlwifi 0000:00:14.3: 0x005E050F | last host cmd
[ 310.497258] iwlwifi 0000:00:14.3: 0x00000000 | isr status reg
[ 310.497299] iwlwifi 0000:00:14.3: IML/ROM dump:
[ 310.497299] iwlwifi 0000:00:14.3: 0x00000B03 | IML/ROM error/state
[ 310.497307] iwlwifi 0000:00:14.3: 0x00004FB0 | IML/ROM data1
[ 310.497315] iwlwifi 0000:00:14.3: 0x00000090 | IML/ROM WFPM_AUTH_KEY_0
[ 310.497320] iwlwifi 0000:00:14.3: Fseq Registers:
[ 310.497323] iwlwifi 0000:00:14.3: 0x60000000 | FSEQ_ERROR_CODE
[ 310.497325] iwlwifi 0000:00:14.3: 0x80350002 | FSEQ_TOP_INIT_VERSION
[ 310.497328] iwlwifi 0000:00:14.3: 0x00150000 | FSEQ_CNVIO_INIT_VERSION
[ 310.497330] iwlwifi 0000:00:14.3: 0x0000A482 | FSEQ_OTP_VERSION
[ 310.497333] iwlwifi 0000:00:14.3: 0x00000003 | FSEQ_TOP_CONTENT_VERSION
[ 310.497335] iwlwifi 0000:00:14.3: 0x4552414E | FSEQ_ALIVE_TOKEN
[ 310.497338] iwlwifi 0000:00:14.3: 0x00080400 | FSEQ_CNVI_ID
[ 310.497340] iwlwifi 0000:00:14.3: 0x00000501 | FSEQ_CNVR_ID
[ 310.497343] iwlwifi 0000:00:14.3: 0x00080400 | CNVI_AUX_MISC_CHIP
[ 310.497348] iwlwifi 0000:00:14.3: 0x00000501 | CNVR_AUX_MISC_CHIP
[ 310.497352] iwlwifi 0000:00:14.3: 0x05B0905B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[ 310.497357] iwlwifi 0000:00:14.3: 0x0000025B | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[ 310.497360] iwlwifi 0000:00:14.3: 0x00150000 | FSEQ_PREV_CNVIO_INIT_VERSION
[ 310.497362] iwlwifi 0000:00:14.3: 0x00350002 | FSEQ_WIFI_FSEQ_VERSION
[ 310.497365] iwlwifi 0000:00:14.3: 0x00350002 | FSEQ_BT_FSEQ_VERSION
[ 310.497367] iwlwifi 0000:00:14.3: 0x000000C8 | FSEQ_CLASS_TP_VERSION
[ 310.497467] iwlwifi 0000:00:14.3: WRT: Collecting data: ini trigger 4 fired (delay=0ms).
[ 310.497469] ieee80211 phy0: Hardware restart was requested
[ 310.497506] iwlwifi 0000:00:14.3: FW error in SYNC CMD ADD_STA
[ 310.497509] CPU: 0 PID: 42 Comm: kworker/u8:1 Tainted: P O 6.6.12-1-liquorix-amd64 #1 liquorix 6.6-16~mx23ahs
[ 310.497511] Hardware name: AZW EQ/EQ, BIOS N95V106 12/15/2023
[ 310.497512] Workqueue: events_unbound cfg80211_wiphy_work [cfg80211]
[ 310.497555] Call Trace:
[ 310.497557] <TASK>
[ 310.497559] dump_stack_lvl+0x43/0x60
[ 310.497563] iwl_trans_txq_send_hcmd+0x2ae/0x360 [iwlwifi]
[ 310.497582] ? __pfx_autoremove_wake_function+0x10/0x10
[ 310.497585] iwl_trans_send_cmd+0x94/0xf0 [iwlwifi]
[ 310.497601] iwl_mvm_send_cmd_pdu_status+0x5d/0xc0 [iwlmvm]
[ 310.497621] iwl_mvm_sta_send_to_fw+0x334/0x400 [iwlmvm]
[ 310.497639] iwl_mvm_mac_sta_state_common+0x171/0xef0 [iwlmvm]
[ 310.497655] drv_sta_state+0xe3/0x5c0 [mac80211]
[ 310.497694] sta_info_move_state+0x23b/0x2a0 [mac80211]
[ 310.497729] ieee80211_sta_rx_queued_mgmt+0x1666/0x3220 [mac80211]
[ 310.497779] ? intel_fbc_activate+0x54/0x130 [i915]
[ 310.497910] ieee80211_iface_work+0x322/0x450 [mac80211]
[ 310.497960] ? frontbuffer_retire+0x40/0x170 [i915]
[ 310.498095] cfg80211_wiphy_work+0x94/0xc0 [cfg80211]
[ 310.498141] process_one_work+0x136/0x2f0
[ 310.498143] worker_thread+0x359/0x4d0
[ 310.498145] ? __pfx_worker_thread+0x10/0x10
[ 310.498146] kthread+0xe1/0x110
[ 310.498149] ? __pfx_kthread+0x10/0x10
[ 310.498151] ret_from_fork+0x2d/0x50
[ 310.498154] ? __pfx_kthread+0x10/0x10
[ 310.498156] ret_from_fork_asm+0x1b/0x30
[ 310.498159] </TASK>
[ 310.498167] wlan0: failed to move station 3c:33:32:c1:2c:79 to desired state
[ 310.920347] iwlwifi 0000:00:14.3: Failed to trigger RX queues sync (-5)
[ 310.920396] iwlwifi 0000:00:14.3: Failed to send flush command (-5)
[ 310.920397] iwlwifi 0000:00:14.3: flush request fail
[ 310.920400] iwlwifi 0000:00:14.3: Couldn't send the SESSION_PROTECTION_CMD: -5
[ 310.920434] iwlwifi 0000:00:14.3: Failed to send MAC_CONTEXT_CMD (action:2): -5
[ 310.920435] iwlwifi 0000:00:14.3: failed to update MAC f0:d4:15:b7:4b:11
[ 310.920441] iwlwifi 0000:00:14.3: Failed to send binding (action:3): -5
[ 310.920443] iwlwifi 0000:00:14.3: Failed to send MAC_CONTEXT_CMD (action:2): -5
[ 310.920444] iwlwifi 0000:00:14.3: failed to update MAC f0:d4:15:b7:4b:11
[ 310.920451] iwlwifi 0000:00:14.3: PHY ctxt cmd error. ret=-5
[ 311.044378] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x3f
[ 311.044390] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[ 311.044398] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
[ 311.044407] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10
[ 311.170637] wlan0: authenticate with 3c:33:32:c1:2c:76
[ 311.170651] wlan0: 80 MHz not supported, disabling VHT
[ 311.176170] wlan0: send auth to 3c:33:32:c1:2c:76 (try 1/3)
[ 311.293450] wlan0: authenticate with 3c:33:32:c1:2c:76
[ 311.293758] wlan0: send auth to 3c:33:32:c1:2c:76 (try 1/3)
[ 311.336964] wlan0: authenticated
[ 311.337825] wlan0: associate with 3c:33:32:c1:2c:76 (try 1/3)
[ 311.391570] wlan0: RX AssocResp from 3c:33:32:c1:2c:76 (capab=0x1431 status=0 aid=10)
[ 311.393107] iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0.
[ 311.393209] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
[ 311.393210] iwlwifi 0000:00:14.3: Transport status: 0x0000004B, valid: 6
[ 311.393211] iwlwifi 0000:00:14.3: Loaded firmware version: 72.daa05125.0 so-a0-hr-b0-72.ucode
[ 311.393212] iwlwifi 0000:00:14.3: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL
[ 311.393214] iwlwifi 0000:00:14.3: 0x000002F0 | trm_hw_status0
[ 311.393215] iwlwifi 0000:00:14.3: 0x00000000 | trm_hw_status1
[ 311.393215] iwlwifi 0000:00:14.3: 0x004D8C8A | branchlink2
[ 311.393216] iwlwifi 0000:00:14.3: 0x000150D4 | interruptlink1
[ 311.393217] iwlwifi 0000:00:14.3: 0x000150D4 | interruptlink2
[ 311.393217] iwlwifi 0000:00:14.3: 0x0000F03A | data1
[ 311.393218] iwlwifi 0000:00:14.3: 0x00000010 | data2
[ 311.393219] iwlwifi 0000:00:14.3: 0x00000000 | data3
[ 311.393219] iwlwifi 0000:00:14.3: 0x0039E918 | beacon time
[ 311.393220] iwlwifi 0000:00:14.3: 0x8F58D0F2 | tsf low
[ 311.393221] iwlwifi 0000:00:14.3: 0x000003FA | tsf hi
[ 311.393221] iwlwifi 0000:00:14.3: 0x00000000 | time gp1
[ 311.393222] iwlwifi 0000:00:14.3: 0x0006E49F | time gp2
[ 311.393222] iwlwifi 0000:00:14.3: 0x00000001 | uCode revision type
[ 311.393223] iwlwifi 0000:00:14.3: 0x00000048 | uCode version major
[ 311.393224] iwlwifi 0000:00:14.3: 0xDAA05125 | uCode version minor
[ 311.393224] iwlwifi 0000:00:14.3: 0x00000370 | hw version
[ 311.393225] iwlwifi 0000:00:14.3: 0x58C80002 | board version
[ 311.393226] iwlwifi 0000:00:14.3: 0x80E8FD00 | hcmd
[ 311.393226] iwlwifi 0000:00:14.3: 0x00020000 | isr0
[ 311.393227] iwlwifi 0000:00:14.3: 0x68000000 | isr1
[ 311.393227] iwlwifi 0000:00:14.3: 0x58F80002 | isr2
[ 311.393228] iwlwifi 0000:00:14.3: 0x04C00018 | isr3
[ 311.393229] iwlwifi 0000:00:14.3: 0x00000000 | isr4
[ 311.393229] iwlwifi 0000:00:14.3: 0x0102001C | last cmd Id
[ 311.393230] iwlwifi 0000:00:14.3: 0x0000F03A | wait_event
[ 311.393231] iwlwifi 0000:00:14.3: 0x00000010 | l2p_control
[ 311.393231] iwlwifi 0000:00:14.3: 0x00000020 | l2p_duration
[ 311.393232] iwlwifi 0000:00:14.3: 0x0000003F | l2p_mhvalid
[ 311.393232] iwlwifi 0000:00:14.3: 0x00CF00F8 | l2p_addr_match
[ 311.393233] iwlwifi 0000:00:14.3: 0x00000009 | lmpm_pmg_sel
[ 311.393234] iwlwifi 0000:00:14.3: 0x00000000 | timestamp
[ 311.393234] iwlwifi 0000:00:14.3: 0x00004868 | flow_handler
[ 311.393282] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
[ 311.393283] iwlwifi 0000:00:14.3: Transport status: 0x0000004B, valid: 7
[ 311.393284] iwlwifi 0000:00:14.3: 0x20101A0D | ADVANCED_SYSASSERT
[ 311.393285] iwlwifi 0000:00:14.3: 0x00000000 | umac branchlink1
[ 311.393285] iwlwifi 0000:00:14.3: 0x8045E934 | umac branchlink2
[ 311.393286] iwlwifi 0000:00:14.3: 0x0106B050 | umac interruptlink1
[ 311.393287] iwlwifi 0000:00:14.3: 0x00000000 | umac interruptlink2
[ 311.393287] iwlwifi 0000:00:14.3: 0x00000006 | umac data1
[ 311.393288] iwlwifi 0000:00:14.3: 0x00000001 | umac data2
[ 311.393288] iwlwifi 0000:00:14.3: 0x00FF0FFF | umac data3
[ 311.393289] iwlwifi 0000:00:14.3: 0x00000048 | umac major
[ 311.393290] iwlwifi 0000:00:14.3: 0xDAA05125 | umac minor
[ 311.393290] iwlwifi 0000:00:14.3: 0x0006E498 | frame pointer
[ 311.393291] iwlwifi 0000:00:14.3: 0xC0886BBC | stack pointer
[ 311.393291] iwlwifi 0000:00:14.3: 0x0037050F | last host cmd
[ 311.393292] iwlwifi 0000:00:14.3: 0x00000000 | isr status reg
[ 311.393332] iwlwifi 0000:00:14.3: IML/ROM dump:
[ 311.393332] iwlwifi 0000:00:14.3: 0x00000B03 | IML/ROM error/state
[ 311.393340] iwlwifi 0000:00:14.3: 0x000053CA | IML/ROM data1
[ 311.393348] iwlwifi 0000:00:14.3: 0x00000090 | IML/ROM WFPM_AUTH_KEY_0
[ 311.393354] iwlwifi 0000:00:14.3: Fseq Registers:
[ 311.393356] iwlwifi 0000:00:14.3: 0x60000000 | FSEQ_ERROR_CODE
[ 311.393358] iwlwifi 0000:00:14.3: 0x80350002 | FSEQ_TOP_INIT_VERSION
[ 311.393361] iwlwifi 0000:00:14.3: 0x00150000 | FSEQ_CNVIO_INIT_VERSION
[ 311.393363] iwlwifi 0000:00:14.3: 0x0000A482 | FSEQ_OTP_VERSION
[ 311.393366] iwlwifi 0000:00:14.3: 0x00000003 | FSEQ_TOP_CONTENT_VERSION
[ 311.393368] iwlwifi 0000:00:14.3: 0x4552414E | FSEQ_ALIVE_TOKEN
[ 311.393371] iwlwifi 0000:00:14.3: 0x00080400 | FSEQ_CNVI_ID
[ 311.393373] iwlwifi 0000:00:14.3: 0x00000501 | FSEQ_CNVR_ID
[ 311.393376] iwlwifi 0000:00:14.3: 0x00080400 | CNVI_AUX_MISC_CHIP
[ 311.393380] iwlwifi 0000:00:14.3: 0x00000501 | CNVR_AUX_MISC_CHIP
[ 311.393385] iwlwifi 0000:00:14.3: 0x05B0905B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[ 311.393390] iwlwifi 0000:00:14.3: 0x0000025B | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[ 311.393392] iwlwifi 0000:00:14.3: 0x00150000 | FSEQ_PREV_CNVIO_INIT_VERSION
[ 311.393395] iwlwifi 0000:00:14.3: 0x00350002 | FSEQ_WIFI_FSEQ_VERSION
[ 311.393397] iwlwifi 0000:00:14.3: 0x00350002 | FSEQ_BT_FSEQ_VERSION
[ 311.393400] iwlwifi 0000:00:14.3: 0x000000C8 | FSEQ_CLASS_TP_VERSION
[ 311.393500] iwlwifi 0000:00:14.3: WRT: Collecting data: ini trigger 4 fired (delay=0ms).
[ 311.393503] ieee80211 phy0: Hardware restart was requested
[ 311.393536] iwlwifi 0000:00:14.3: FW error in SYNC CMD ADD_STA
[ 311.393539] CPU: 3 PID: 10 Comm: kworker/u8:0 Tainted: P O 6.6.12-1-liquorix-amd64 #1 liquorix 6.6-16~mx23ahs
[ 311.393541] Hardware name: AZW EQ/EQ, BIOS N95V106 12/15/2023
[ 311.393542] Workqueue: events_unbound cfg80211_wiphy_work [cfg80211]
[ 311.393586] Call Trace:
[ 311.393588] <TASK>
[ 311.393589] dump_stack_lvl+0x43/0x60
[ 311.393593] iwl_trans_txq_send_hcmd+0x2ae/0x360 [iwlwifi]
[ 311.393613] ? __pfx_autoremove_wake_function+0x10/0x10
[ 311.393616] iwl_trans_send_cmd+0x94/0xf0 [iwlwifi]
[ 311.393631] iwl_mvm_send_cmd_pdu_status+0x5d/0xc0 [iwlmvm]
[ 311.393651] iwl_mvm_sta_send_to_fw+0x334/0x400 [iwlmvm]
[ 311.393670] iwl_mvm_mac_sta_state_common+0x171/0xef0 [iwlmvm]
[ 311.393686] drv_sta_state+0xe3/0x5c0 [mac80211]
[ 311.393725] sta_info_move_state+0x23b/0x2a0 [mac80211]
[ 311.393760] ieee80211_sta_rx_queued_mgmt+0x1666/0x3220 [mac80211]
[ 311.393809] ieee80211_iface_work+0x322/0x450 [mac80211]
[ 311.393857] ? intel_check_cpu_fifo_underruns+0x270/0x270 [i915]
[ 311.394001] cfg80211_wiphy_work+0x94/0xc0 [cfg80211]
[ 311.394047] process_one_work+0x136/0x2f0
[ 311.394050] worker_thread+0x359/0x4d0
[ 311.394052] ? __pfx_worker_thread+0x10/0x10
[ 311.394053] kthread+0xe1/0x110
[ 311.394056] ? __pfx_kthread+0x10/0x10
[ 311.394057] ret_from_fork+0x2d/0x50
[ 311.394060] ? __pfx_kthread+0x10/0x10
[ 311.394061] ret_from_fork_asm+0x1b/0x30
[ 311.394065] </TASK>
[ 311.394078] wlan0: failed to move station 3c:33:32:c1:2c:76 to desired state
[ 311.394082] iwlwifi 0000:00:14.3: Failed to trigger RX queues sync (-5)
[ 311.394114] iwlwifi 0000:00:14.3: Failed to send flush command (-5)
[ 311.394115] iwlwifi 0000:00:14.3: flush request fail
[ 311.818979] iwlwifi 0000:00:14.3: Couldn't send the SESSION_PROTECTION_CMD: -5
[ 311.819011] iwlwifi 0000:00:14.3: Failed to send MAC_CONTEXT_CMD (action:2): -5
[ 311.819012] iwlwifi 0000:00:14.3: failed to update MAC f0:d4:15:b7:4b:11
[ 311.819018] iwlwifi 0000:00:14.3: Failed to send binding (action:3): -5
[ 311.819021] iwlwifi 0000:00:14.3: Failed to send MAC_CONTEXT_CMD (action:2): -5
[ 311.819022] iwlwifi 0000:00:14.3: failed to update MAC f0:d4:15:b7:4b:11
[ 311.819024] iwlwifi 0000:00:14.3: PHY ctxt cmd error. ret=-5
[ 311.943882] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x3f
[ 311.943893] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[ 311.943902] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
[ 311.943910] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10
[ 315.200437] wlan0: authenticate with 3c:33:32:c1:2c:79
[ 315.204458] wlan0: send auth to 3c:33:32:c1:2c:79 (try 1/3)
[ 315.289793] wlan0: authenticated
[ 315.290897] wlan0: associate with 3c:33:32:c1:2c:79 (try 1/3)
[ 315.320344] wlan0: RX AssocResp from 3c:33:32:c1:2c:79 (capab=0x1131 status=0 aid=10)
[ 315.321892] iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0.
[ 315.321994] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
[ 315.321995] iwlwifi 0000:00:14.3: Transport status: 0x0000004B, valid: 6
[ 315.321997] iwlwifi 0000:00:14.3: Loaded firmware version: 72.daa05125.0 so-a0-hr-b0-72.ucode
[ 315.321998] iwlwifi 0000:00:14.3: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL
[ 315.321999] iwlwifi 0000:00:14.3: 0x00808210 | trm_hw_status0
[ 315.322000] iwlwifi 0000:00:14.3: 0x00000000 | trm_hw_status1
[ 315.322001] iwlwifi 0000:00:14.3: 0x004D8C8A | branchlink2
[ 315.322001] iwlwifi 0000:00:14.3: 0x004CF116 | interruptlink1
[ 315.322002] iwlwifi 0000:00:14.3: 0x004CF116 | interruptlink2
[ 315.322003] iwlwifi 0000:00:14.3: 0x0000B658 | data1
[ 315.322003] iwlwifi 0000:00:14.3: 0x00000010 | data2
[ 315.322004] iwlwifi 0000:00:14.3: 0x00000000 | data3
[ 315.322005] iwlwifi 0000:00:14.3: 0x001094DC | beacon time
[ 315.322005] iwlwifi 0000:00:14.3: 0x8F94C3AC | tsf low
[ 315.322006] iwlwifi 0000:00:14.3: 0x000003FA | tsf hi
[ 315.322007] iwlwifi 0000:00:14.3: 0x00000000 | time gp1
[ 315.322007] iwlwifi 0000:00:14.3: 0x00351DDE | time gp2
[ 315.322008] iwlwifi 0000:00:14.3: 0x00000001 | uCode revision type
[ 315.322008] iwlwifi 0000:00:14.3: 0x00000048 | uCode version major
[ 315.322009] iwlwifi 0000:00:14.3: 0xDAA05125 | uCode version minor
[ 315.322010] iwlwifi 0000:00:14.3: 0x00000370 | hw version
[ 315.322010] iwlwifi 0000:00:14.3: 0x58C80002 | board version
[ 315.322011] iwlwifi 0000:00:14.3: 0x8099FF00 | hcmd
[ 315.322012] iwlwifi 0000:00:14.3: 0x24020000 | isr0
[ 315.322012] iwlwifi 0000:00:14.3: 0x61000000 | isr1
[ 315.322013] iwlwifi 0000:00:14.3: 0x48F00002 | isr2
[ 315.322013] iwlwifi 0000:00:14.3: 0x00C3400C | isr3
[ 315.322014] iwlwifi 0000:00:14.3: 0x00000000 | isr4
[ 315.322015] iwlwifi 0000:00:14.3: 0x0101001C | last cmd Id
[ 315.322015] iwlwifi 0000:00:14.3: 0x0000B658 | wait_event
[ 315.322016] iwlwifi 0000:00:14.3: 0x00000080 | l2p_control
[ 315.322017] iwlwifi 0000:00:14.3: 0x00010034 | l2p_duration
[ 315.322017] iwlwifi 0000:00:14.3: 0x0000003F | l2p_mhvalid
[ 315.322018] iwlwifi 0000:00:14.3: 0x00001800 | l2p_addr_match
[ 315.322018] iwlwifi 0000:00:14.3: 0x00000009 | lmpm_pmg_sel
[ 315.322019] iwlwifi 0000:00:14.3: 0x00000000 | timestamp
[ 315.322020] iwlwifi 0000:00:14.3: 0x00006080 | flow_handler
[ 315.322068] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
[ 315.322068] iwlwifi 0000:00:14.3: Transport status: 0x0000004B, valid: 7
[ 315.322069] iwlwifi 0000:00:14.3: 0x20101A0D | ADVANCED_SYSASSERT
[ 315.322070] iwlwifi 0000:00:14.3: 0x00000000 | umac branchlink1
[ 315.322071] iwlwifi 0000:00:14.3: 0x8045E934 | umac branchlink2
[ 315.322071] iwlwifi 0000:00:14.3: 0x0106B050 | umac interruptlink1
[ 315.322072] iwlwifi 0000:00:14.3: 0x00000000 | umac interruptlink2
[ 315.322073] iwlwifi 0000:00:14.3: 0x00000006 | umac data1
[ 315.322073] iwlwifi 0000:00:14.3: 0x00000001 | umac data2
[ 315.322074] iwlwifi 0000:00:14.3: 0x00FF0FFF | umac data3
[ 315.322074] iwlwifi 0000:00:14.3: 0x00000048 | umac major
[ 315.322075] iwlwifi 0000:00:14.3: 0xDAA05125 | umac minor
[ 315.322076] iwlwifi 0000:00:14.3: 0x00351DD7 | frame pointer
[ 315.322076] iwlwifi 0000:00:14.3: 0xC0886BBC | stack pointer
[ 315.322077] iwlwifi 0000:00:14.3: 0x0038050F | last host cmd
[ 315.322077] iwlwifi 0000:00:14.3: 0x00000000 | isr status reg
[ 315.322117] iwlwifi 0000:00:14.3: IML/ROM dump:
[ 315.322118] iwlwifi 0000:00:14.3: 0x00000B03 | IML/ROM error/state
[ 315.322125] iwlwifi 0000:00:14.3: 0x0000558C | IML/ROM data1
[ 315.322133] iwlwifi 0000:00:14.3: 0x00000090 | IML/ROM WFPM_AUTH_KEY_0
[ 315.322139] iwlwifi 0000:00:14.3: Fseq Registers:
[ 315.322141] iwlwifi 0000:00:14.3: 0x60000000 | FSEQ_ERROR_CODE
[ 315.322144] iwlwifi 0000:00:14.3: 0x80350002 | FSEQ_TOP_INIT_VERSION
[ 315.322146] iwlwifi 0000:00:14.3: 0x00150000 | FSEQ_CNVIO_INIT_VERSION
[ 315.322149] iwlwifi 0000:00:14.3: 0x0000A482 | FSEQ_OTP_VERSION
[ 315.322151] iwlwifi 0000:00:14.3: 0x00000003 | FSEQ_TOP_CONTENT_VERSION
[ 315.322154] iwlwifi 0000:00:14.3: 0x4552414E | FSEQ_ALIVE_TOKEN
[ 315.322156] iwlwifi 0000:00:14.3: 0x00080400 | FSEQ_CNVI_ID
[ 315.322159] iwlwifi 0000:00:14.3: 0x00000501 | FSEQ_CNVR_ID
[ 315.322161] iwlwifi 0000:00:14.3: 0x00080400 | CNVI_AUX_MISC_CHIP
[ 315.322166] iwlwifi 0000:00:14.3: 0x00000501 | CNVR_AUX_MISC_CHIP
[ 315.322170] iwlwifi 0000:00:14.3: 0x05B0905B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[ 315.322175] iwlwifi 0000:00:14.3: 0x0000025B | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[ 315.322178] iwlwifi 0000:00:14.3: 0x00150000 | FSEQ_PREV_CNVIO_INIT_VERSION
[ 315.322180] iwlwifi 0000:00:14.3: 0x00350002 | FSEQ_WIFI_FSEQ_VERSION
[ 315.322182] iwlwifi 0000:00:14.3: 0x00350002 | FSEQ_BT_FSEQ_VERSION
[ 315.322185] iwlwifi 0000:00:14.3: 0x000000C8 | FSEQ_CLASS_TP_VERSION
[ 315.322285] iwlwifi 0000:00:14.3: WRT: Collecting data: ini trigger 4 fired (delay=0ms).
[ 315.322287] ieee80211 phy0: Hardware restart was requested
[ 315.322318] iwlwifi 0000:00:14.3: FW error in SYNC CMD ADD_STA
[ 315.322321] CPU: 2 PID: 10 Comm: kworker/u8:0 Tainted: P O 6.6.12-1-liquorix-amd64 #1 liquorix 6.6-16~mx23ahs
[ 315.322323] Hardware name: AZW EQ/EQ, BIOS N95V106 12/15/2023
[ 315.322324] Workqueue: events_unbound cfg80211_wiphy_work [cfg80211]
[ 315.322368] Call Trace:
[ 315.322370] <TASK>
[ 315.322372] dump_stack_lvl+0x43/0x60
[ 315.322376] iwl_trans_txq_send_hcmd+0x2ae/0x360 [iwlwifi]
[ 315.322396] ? __pfx_autoremove_wake_function+0x10/0x10
[ 315.322399] iwl_trans_send_cmd+0x94/0xf0 [iwlwifi]
[ 315.322414] iwl_mvm_send_cmd_pdu_status+0x5d/0xc0 [iwlmvm]
[ 315.322434] iwl_mvm_sta_send_to_fw+0x334/0x400 [iwlmvm]
[ 315.322453] iwl_mvm_mac_sta_state_common+0x171/0xef0 [iwlmvm]
[ 315.322469] drv_sta_state+0xe3/0x5c0 [mac80211]
[ 315.322508] sta_info_move_state+0x23b/0x2a0 [mac80211]
[ 315.322543] ieee80211_sta_rx_queued_mgmt+0x1666/0x3220 [mac80211]
[ 315.322592] ieee80211_iface_work+0x322/0x450 [mac80211]
[ 315.322632] cfg80211_wiphy_work+0x94/0xc0 [cfg80211]
[ 315.322668] process_one_work+0x136/0x2f0
[ 315.322670] worker_thread+0x359/0x4d0
[ 315.322671] ? __pfx_worker_thread+0x10/0x10
[ 315.322672] kthread+0xe1/0x110
[ 315.322674] ? __pfx_kthread+0x10/0x10
[ 315.322676] ret_from_fork+0x2d/0x50
[ 315.322679] ? __pfx_kthread+0x10/0x10
[ 315.322680] ret_from_fork_asm+0x1b/0x30
[ 315.322683] </TASK>
[ 315.322685] wlan0: failed to move station 3c:33:32:c1:2c:79 to desired state
[ 315.750090] iwlwifi 0000:00:14.3: Failed to trigger RX queues sync (-5)
[ 315.750110] iwlwifi 0000:00:14.3: Failed to send flush command (-5)
[ 315.750112] iwlwifi 0000:00:14.3: flush request fail
[ 315.750114] iwlwifi 0000:00:14.3: Couldn't send the SESSION_PROTECTION_CMD: -5
[ 315.750141] iwlwifi 0000:00:14.3: Failed to send MAC_CONTEXT_CMD (action:2): -5
[ 315.750142] iwlwifi 0000:00:14.3: failed to update MAC f0:d4:15:b7:4b:11
[ 315.750152] iwlwifi 0000:00:14.3: Failed to send binding (action:3): -5
[ 315.750155] iwlwifi 0000:00:14.3: Failed to send MAC_CONTEXT_CMD (action:2): -5
[ 315.750156] iwlwifi 0000:00:14.3: failed to update MAC f0:d4:15:b7:4b:11
[ 315.750158] iwlwifi 0000:00:14.3: PHY ctxt cmd error. ret=-5
[ 315.874946] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x3f
[ 315.874957] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[ 315.874966] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
[ 315.874974] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10
[ 316.817682] wlan0: authenticate with 3c:33:32:c1:2c:76
[ 316.817703] wlan0: 80 MHz not supported, disabling VHT
[ 316.821835] wlan0: send auth to 3c:33:32:c1:2c:76 (try 1/3)
[ 316.912660] wlan0: authenticated
[ 316.913909] wlan0: associate with 3c:33:32:c1:2c:76 (try 1/3)
[ 316.946907] wlan0: RX AssocResp from 3c:33:32:c1:2c:76 (capab=0x1431 status=0 aid=10)
[ 316.948443] iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0.
[ 316.948587] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
[ 316.948588] iwlwifi 0000:00:14.3: Transport status: 0x0000004B, valid: 6
[ 316.948589] iwlwifi 0000:00:14.3: Loaded firmware version: 72.daa05125.0 so-a0-hr-b0-72.ucode
[ 316.948590] iwlwifi 0000:00:14.3: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL
[ 316.948591] iwlwifi 0000:00:14.3: 0x000002F0 | trm_hw_status0
[ 316.948592] iwlwifi 0000:00:14.3: 0x00000000 | trm_hw_status1
[ 316.948593] iwlwifi 0000:00:14.3: 0x004D8C8A | branchlink2
[ 316.948593] iwlwifi 0000:00:14.3: 0x004CF116 | interruptlink1
[ 316.948594] iwlwifi 0000:00:14.3: 0x004CF116 | interruptlink2
[ 316.948595] iwlwifi 0000:00:14.3: 0x00005DCA | data1
[ 316.948595] iwlwifi 0000:00:14.3: 0x00000010 | data2
[ 316.948596] iwlwifi 0000:00:14.3: 0x00000000 | data3
[ 316.948597] iwlwifi 0000:00:14.3: 0x003B5B9A | beacon time
[ 316.948597] iwlwifi 0000:00:14.3: 0x8FAD955E | tsf low
[ 316.948598] iwlwifi 0000:00:14.3: 0x000003FA | tsf hi
[ 316.948599] iwlwifi 0000:00:14.3: 0x00000000 | time gp1
[ 316.948599] iwlwifi 0000:00:14.3: 0x0011F69C | time gp2
[ 316.948600] iwlwifi 0000:00:14.3: 0x00000001 | uCode revision type
[ 316.948600] iwlwifi 0000:00:14.3: 0x00000048 | uCode version major
[ 316.948601] iwlwifi 0000:00:14.3: 0xDAA05125 | uCode version minor
[ 316.948602] iwlwifi 0000:00:14.3: 0x00000370 | hw version
[ 316.948602] iwlwifi 0000:00:14.3: 0x58C80002 | board version
[ 316.948603] iwlwifi 0000:00:14.3: 0x80CDFF00 | hcmd
[ 316.948604] iwlwifi 0000:00:14.3: 0x00020000 | isr0
[ 316.948604] iwlwifi 0000:00:14.3: 0x20000000 | isr1
[ 316.948605] iwlwifi 0000:00:14.3: 0x48F00002 | isr2
[ 316.948605] iwlwifi 0000:00:14.3: 0x00C3000C | isr3
[ 316.948606] iwlwifi 0000:00:14.3: 0x00000000 | isr4
[ 316.948607] iwlwifi 0000:00:14.3: 0x0101001C | last cmd Id
[ 316.948607] iwlwifi 0000:00:14.3: 0x00005DCA | wait_event
[ 316.948608] iwlwifi 0000:00:14.3: 0x00000010 | l2p_control
[ 316.948609] iwlwifi 0000:00:14.3: 0x00000020 | l2p_duration
[ 316.948609] iwlwifi 0000:00:14.3: 0x0000003F | l2p_mhvalid
[ 316.948610] iwlwifi 0000:00:14.3: 0x00CF00F8 | l2p_addr_match
[ 316.948611] iwlwifi 0000:00:14.3: 0x00000009 | lmpm_pmg_sel
[ 316.948611] iwlwifi 0000:00:14.3: 0x00000000 | timestamp
[ 316.948612] iwlwifi 0000:00:14.3: 0x00004064 | flow_handler
[ 316.948659] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
[ 316.948660] iwlwifi 0000:00:14.3: Transport status: 0x0000004B, valid: 7
[ 316.948661] iwlwifi 0000:00:14.3: 0x20101A0D | ADVANCED_SYSASSERT
[ 316.948662] iwlwifi 0000:00:14.3: 0x00000000 | umac branchlink1
[ 316.948662] iwlwifi 0000:00:14.3: 0x8045E934 | umac branchlink2
[ 316.948663] iwlwifi 0000:00:14.3: 0x0106B050 | umac interruptlink1
[ 316.948664] iwlwifi 0000:00:14.3: 0x00000000 | umac interruptlink2
[ 316.948664] iwlwifi 0000:00:14.3: 0x00000006 | umac data1
[ 316.948665] iwlwifi 0000:00:14.3: 0x00000001 | umac data2
[ 316.948665] iwlwifi 0000:00:14.3: 0x00FF0FFF | umac data3
[ 316.948666] iwlwifi 0000:00:14.3: 0x00000048 | umac major
[ 316.948667] iwlwifi 0000:00:14.3: 0xDAA05125 | umac minor
[ 316.948667] iwlwifi 0000:00:14.3: 0x0011F695 | frame pointer
[ 316.948668] iwlwifi 0000:00:14.3: 0xC0886BBC | stack pointer
[ 316.948668] iwlwifi 0000:00:14.3: 0x0035050F | last host cmd
[ 316.948669] iwlwifi 0000:00:14.3: 0x00000000 | isr status reg
[ 316.948709] iwlwifi 0000:00:14.3: IML/ROM dump:
[ 316.948709] iwlwifi 0000:00:14.3: 0x00000B03 | IML/ROM error/state
[ 316.948717] iwlwifi 0000:00:14.3: 0x000055C0 | IML/ROM data1
[ 316.948725] iwlwifi 0000:00:14.3: 0x00000090 | IML/ROM WFPM_AUTH_KEY_0
[ 316.948730] iwlwifi 0000:00:14.3: Fseq Registers:
[ 316.948733] iwlwifi 0000:00:14.3: 0x60000000 | FSEQ_ERROR_CODE
[ 316.948735] iwlwifi 0000:00:14.3: 0x80350002 | FSEQ_TOP_INIT_VERSION
[ 316.948738] iwlwifi 0000:00:14.3: 0x00150000 | FSEQ_CNVIO_INIT_VERSION
[ 316.948740] iwlwifi 0000:00:14.3: 0x0000A482 | FSEQ_OTP_VERSION
[ 316.948743] iwlwifi 0000:00:14.3: 0x00000003 | FSEQ_TOP_CONTENT_VERSION
[ 316.948745] iwlwifi 0000:00:14.3: 0x4552414E | FSEQ_ALIVE_TOKEN
[ 316.948748] iwlwifi 0000:00:14.3: 0x00080400 | FSEQ_CNVI_ID
[ 316.948750] iwlwifi 0000:00:14.3: 0x00000501 | FSEQ_CNVR_ID
[ 316.948753] iwlwifi 0000:00:14.3: 0x00080400 | CNVI_AUX_MISC_CHIP
[ 316.948757] iwlwifi 0000:00:14.3: 0x00000501 | CNVR_AUX_MISC_CHIP
[ 316.948762] iwlwifi 0000:00:14.3: 0x05B0905B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[ 316.948767] iwlwifi 0000:00:14.3: 0x0000025B | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[ 316.948769] iwlwifi 0000:00:14.3: 0x00150000 | FSEQ_PREV_CNVIO_INIT_VERSION
[ 316.948772] iwlwifi 0000:00:14.3: 0x00350002 | FSEQ_WIFI_FSEQ_VERSION
[ 316.948816] iwlwifi 0000:00:14.3: 0x00350002 | FSEQ_BT_FSEQ_VERSION
[ 316.948819] iwlwifi 0000:00:14.3: 0x000000C8 | FSEQ_CLASS_TP_VERSION
[ 316.948965] iwlwifi 0000:00:14.3: WRT: Collecting data: ini trigger 4 fired (delay=0ms).
[ 316.948968] ieee80211 phy0: Hardware restart was requested
[ 316.949030] iwlwifi 0000:00:14.3: FW error in SYNC CMD ADD_STA
[ 316.949033] CPU: 2 PID: 42 Comm: kworker/u8:1 Tainted: P O 6.6.12-1-liquorix-amd64 #1 liquorix 6.6-16~mx23ahs
[ 316.949035] Hardware name: AZW EQ/EQ, BIOS N95V106 12/15/2023
[ 316.949036] Workqueue: events_unbound cfg80211_wiphy_work [cfg80211]
[ 316.949087] Call Trace:
[ 316.949089] <TASK>
[ 316.949091] dump_stack_lvl+0x43/0x60
[ 316.949095] iwl_trans_txq_send_hcmd+0x2ae/0x360 [iwlwifi]
[ 316.949123] ? __pfx_autoremove_wake_function+0x10/0x10
[ 316.949126] iwl_trans_send_cmd+0x94/0xf0 [iwlwifi]
[ 316.949146] iwl_mvm_send_cmd_pdu_status+0x5d/0xc0 [iwlmvm]
[ 316.949169] iwl_mvm_sta_send_to_fw+0x334/0x400 [iwlmvm]
[ 316.949192] iwl_mvm_mac_sta_state_common+0x171/0xef0 [iwlmvm]
[ 316.949211] drv_sta_state+0xe3/0x5c0 [mac80211]
[ 316.949259] sta_info_move_state+0x23b/0x2a0 [mac80211]
[ 316.949304] ieee80211_sta_rx_queued_mgmt+0x1666/0x3220 [mac80211]
[ 316.949364] ieee80211_iface_work+0x322/0x450 [mac80211]
[ 316.949412] cfg80211_wiphy_work+0x94/0xc0 [cfg80211]
[ 316.949456] process_one_work+0x136/0x2f0
[ 316.949459] worker_thread+0x359/0x4d0
[ 316.949461] ? __pfx_worker_thread+0x10/0x10
[ 316.949462] kthread+0xe1/0x110
[ 316.949465] ? __pfx_kthread+0x10/0x10
[ 316.949467] ret_from_fork+0x2d/0x50
[ 316.949470] ? __pfx_kthread+0x10/0x10
[ 316.949472] ret_from_fork_asm+0x1b/0x30
[ 316.949475] </TASK>
[ 316.949478] wlan0: failed to move station 3c:33:32:c1:2c:76 to desired state
[ 316.989773] workqueue: iwl_fw_error_dump_wk [iwlwifi] hogged CPU for >40000us 4 times, consider switching to WQ_UNBOUND
[ 317.379852] iwlwifi 0000:00:14.3: Failed to trigger RX queues sync (-5)
[ 317.379919] iwlwifi 0000:00:14.3: Failed to send flush command (-5)
[ 317.379921] iwlwifi 0000:00:14.3: flush request fail
[ 317.379924] iwlwifi 0000:00:14.3: Couldn't send the SESSION_PROTECTION_CMD: -5
[ 317.379951] iwlwifi 0000:00:14.3: Failed to send MAC_CONTEXT_CMD (action:2): -5
[ 317.379952] iwlwifi 0000:00:14.3: failed to update MAC f0:d4:15:b7:4b:11
[ 317.379957] iwlwifi 0000:00:14.3: Failed to send binding (action:3): -5
[ 317.379960] iwlwifi 0000:00:14.3: Failed to send MAC_CONTEXT_CMD (action:2): -5
[ 317.379961] iwlwifi 0000:00:14.3: failed to update MAC f0:d4:15:b7:4b:11
[ 317.379963] iwlwifi 0000:00:14.3: PHY ctxt cmd error. ret=-5
[ 317.503210] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x3f
[ 317.503221] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[ 317.503272] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
[ 317.503279] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10
[ 327.267907] wlan0: authenticate with 3c:33:32:c1:2c:79
[ 327.275054] wlan0: send auth to 3c:33:32:c1:2c:79 (try 1/3)
[ 327.328872] wlan0: authenticated
[ 327.329698] wlan0: associate with 3c:33:32:c1:2c:79 (try 1/3)
[ 327.355882] wlan0: RX AssocResp from 3c:33:32:c1:2c:79 (capab=0x1131 status=0 aid=10)
[ 327.357353] iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0.
[ 327.357497] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
[ 327.357498] iwlwifi 0000:00:14.3: Transport status: 0x0000004B, valid: 6
[ 327.357499] iwlwifi 0000:00:14.3: Loaded firmware version: 72.daa05125.0 so-a0-hr-b0-72.ucode
[ 327.357500] iwlwifi 0000:00:14.3: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL
[ 327.357502] iwlwifi 0000:00:14.3: 0x00A08200 | trm_hw_status0
[ 327.357502] iwlwifi 0000:00:14.3: 0x00000000 | trm_hw_status1
[ 327.357503] iwlwifi 0000:00:14.3: 0x004D8C8A | branchlink2
[ 327.357504] iwlwifi 0000:00:14.3: 0x004CF116 | interruptlink1
[ 327.357504] iwlwifi 0000:00:14.3: 0x004CF116 | interruptlink2
[ 327.357505] iwlwifi 0000:00:14.3: 0x000151CA | data1
[ 327.357506] iwlwifi 0000:00:14.3: 0x00000010 | data2
[ 327.357506] iwlwifi 0000:00:14.3: 0x00000000 | data3
[ 327.357507] iwlwifi 0000:00:14.3: 0x001113FA | beacon time
[ 327.357508] iwlwifi 0000:00:14.3: 0x904C6937 | tsf low
[ 327.357508] iwlwifi 0000:00:14.3: 0x000003FA | tsf hi
[ 327.357509] iwlwifi 0000:00:14.3: 0x00000000 | time gp1
[ 327.357510] iwlwifi 0000:00:14.3: 0x0097EBF4 | time gp2
[ 327.357510] iwlwifi 0000:00:14.3: 0x00000001 | uCode revision type
[ 327.357511] iwlwifi 0000:00:14.3: 0x00000048 | uCode version major
[ 327.357512] iwlwifi 0000:00:14.3: 0xDAA05125 | uCode version minor
[ 327.357512] iwlwifi 0000:00:14.3: 0x00000370 | hw version
[ 327.357513] iwlwifi 0000:00:14.3: 0x58C80002 | board version
[ 327.357514] iwlwifi 0000:00:14.3: 0x8097FF00 | hcmd
[ 327.357514] iwlwifi 0000:00:14.3: 0x24020000 | isr0
[ 327.357515] iwlwifi 0000:00:14.3: 0x61000000 | isr1
[ 327.357515] iwlwifi 0000:00:14.3: 0x48F00002 | isr2
[ 327.357516] iwlwifi 0000:00:14.3: 0x00C3000C | isr3
[ 327.357517] iwlwifi 0000:00:14.3: 0x00000000 | isr4
[ 327.357517] iwlwifi 0000:00:14.3: 0x0101001C | last cmd Id
[ 327.357518] iwlwifi 0000:00:14.3: 0x000151CA | wait_event
[ 327.357519] iwlwifi 0000:00:14.3: 0x00000010 | l2p_control
[ 327.357519] iwlwifi 0000:00:14.3: 0x00018034 | l2p_duration
[ 327.357520] iwlwifi 0000:00:14.3: 0x0000003F | l2p_mhvalid
[ 327.357520] iwlwifi 0000:00:14.3: 0x00CF00F8 | l2p_addr_match
[ 327.357521] iwlwifi 0000:00:14.3: 0x00000009 | lmpm_pmg_sel
[ 327.357522] iwlwifi 0000:00:14.3: 0x00000000 | timestamp
[ 327.357522] iwlwifi 0000:00:14.3: 0x00005074 | flow_handler
[ 327.357570] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
[ 327.357570] iwlwifi 0000:00:14.3: Transport status: 0x0000004B, valid: 7
[ 327.357571] iwlwifi 0000:00:14.3: 0x20101A0D | ADVANCED_SYSASSERT
[ 327.357572] iwlwifi 0000:00:14.3: 0x00000000 | umac branchlink1
[ 327.357573] iwlwifi 0000:00:14.3: 0x8045E934 | umac branchlink2
[ 327.357573] iwlwifi 0000:00:14.3: 0x0106B050 | umac interruptlink1
[ 327.357574] iwlwifi 0000:00:14.3: 0x00000000 | umac interruptlink2
[ 327.357575] iwlwifi 0000:00:14.3: 0x00000006 | umac data1
[ 327.357575] iwlwifi 0000:00:14.3: 0x00000001 | umac data2
[ 327.357576] iwlwifi 0000:00:14.3: 0x00FF0FFF | umac data3
[ 327.357576] iwlwifi 0000:00:14.3: 0x00000048 | umac major
[ 327.357577] iwlwifi 0000:00:14.3: 0xDAA05125 | umac minor
[ 327.357578] iwlwifi 0000:00:14.3: 0x0097EBEE | frame pointer
[ 327.357578] iwlwifi 0000:00:14.3: 0xC0886BBC | stack pointer
[ 327.357579] iwlwifi 0000:00:14.3: 0x0036050F | last host cmd
[ 327.357579] iwlwifi 0000:00:14.3: 0x00000000 | isr status reg
[ 327.357619] iwlwifi 0000:00:14.3: IML/ROM dump:
[ 327.357619] iwlwifi 0000:00:14.3: 0x00000B03 | IML/ROM error/state
[ 327.357627] iwlwifi 0000:00:14.3: 0x0000529E | IML/ROM data1
[ 327.357636] iwlwifi 0000:00:14.3: 0x00000090 | IML/ROM WFPM_AUTH_KEY_0
[ 327.357641] iwlwifi 0000:00:14.3: Fseq Registers:
[ 327.357643] iwlwifi 0000:00:14.3: 0x60000000 | FSEQ_ERROR_CODE
[ 327.357646] iwlwifi 0000:00:14.3: 0x80350002 | FSEQ_TOP_INIT_VERSION
[ 327.357648] iwlwifi 0000:00:14.3: 0x00150000 | FSEQ_CNVIO_INIT_VERSION
[ 327.357651] iwlwifi 0000:00:14.3: 0x0000A482 | FSEQ_OTP_VERSION
[ 327.357653] iwlwifi 0000:00:14.3: 0x00000003 | FSEQ_TOP_CONTENT_VERSION
[ 327.357656] iwlwifi 0000:00:14.3: 0x4552414E | FSEQ_ALIVE_TOKEN
[ 327.357658] iwlwifi 0000:00:14.3: 0x00080400 | FSEQ_CNVI_ID
[ 327.357661] iwlwifi 0000:00:14.3: 0x00000501 | FSEQ_CNVR_ID
[ 327.357663] iwlwifi 0000:00:14.3: 0x00080400 | CNVI_AUX_MISC_CHIP
[ 327.357668] iwlwifi 0000:00:14.3: 0x00000501 | CNVR_AUX_MISC_CHIP
[ 327.357672] iwlwifi 0000:00:14.3: 0x05B0905B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[ 327.357677] iwlwifi 0000:00:14.3: 0x0000025B | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[ 327.357680] iwlwifi 0000:00:14.3: 0x00150000 | FSEQ_PREV_CNVIO_INIT_VERSION
[ 327.357683] iwlwifi 0000:00:14.3: 0x00350002 | FSEQ_WIFI_FSEQ_VERSION
[ 327.357729] iwlwifi 0000:00:14.3: 0x00350002 | FSEQ_BT_FSEQ_VERSION
[ 327.357731] iwlwifi 0000:00:14.3: 0x000000C8 | FSEQ_CLASS_TP_VERSION
[ 327.357918] iwlwifi 0000:00:14.3: WRT: Collecting data: ini trigger 4 fired (delay=0ms).
[ 327.357926] ieee80211 phy0: Hardware restart was requested
[ 327.357964] iwlwifi 0000:00:14.3: FW error in SYNC CMD ADD_STA
[ 327.357967] CPU: 3 PID: 10 Comm: kworker/u8:0 Tainted: P O 6.6.12-1-liquorix-amd64 #1 liquorix 6.6-16~mx23ahs
[ 327.357969] Hardware name: AZW EQ/EQ, BIOS N95V106 12/15/2023
[ 327.357970] Workqueue: events_unbound cfg80211_wiphy_work [cfg80211]
[ 327.358019] Call Trace:
[ 327.358021] <TASK>
[ 327.358023] dump_stack_lvl+0x43/0x60
[ 327.358027] iwl_trans_txq_send_hcmd+0x2ae/0x360 [iwlwifi]
[ 327.358049] ? __pfx_autoremove_wake_function+0x10/0x10
[ 327.358052] iwl_trans_send_cmd+0x94/0xf0 [iwlwifi]
[ 327.358069] iwl_mvm_send_cmd_pdu_status+0x5d/0xc0 [iwlmvm]
[ 327.358091] iwl_mvm_sta_send_to_fw+0x334/0x400 [iwlmvm]
[ 327.358112] iwl_mvm_mac_sta_state_common+0x171/0xef0 [iwlmvm]
[ 327.358130] drv_sta_state+0xe3/0x5c0 [mac80211]
[ 327.358172] sta_info_move_state+0x23b/0x2a0 [mac80211]
[ 327.358211] ieee80211_sta_rx_queued_mgmt+0x1666/0x3220 [mac80211]
[ 327.358266] ieee80211_iface_work+0x322/0x450 [mac80211]
[ 327.358310] ? intel_check_cpu_fifo_underruns+0x270/0x270 [i915]
[ 327.358440] cfg80211_wiphy_work+0x94/0xc0 [cfg80211]
[ 327.358484] process_one_work+0x136/0x2f0
[ 327.358487] worker_thread+0x359/0x4d0
[ 327.358489] ? __pfx_worker_thread+0x10/0x10
[ 327.358490] kthread+0xe1/0x110
[ 327.358493] ? __pfx_kthread+0x10/0x10
[ 327.358494] ret_from_fork+0x2d/0x50
[ 327.358497] ? __pfx_kthread+0x10/0x10
[ 327.358499] ret_from_fork_asm+0x1b/0x30
[ 327.358502] </TASK>
[ 327.358505] wlan0: failed to move station 3c:33:32:c1:2c:79 to desired state
[ 327.358509] iwlwifi 0000:00:14.3: Failed to trigger RX queues sync (-5)
[ 327.358548] iwlwifi 0000:00:14.3: Failed to send flush command (-5)
[ 327.358549] iwlwifi 0000:00:14.3: flush request fail
[ 327.358552] iwlwifi 0000:00:14.3: Couldn't send the SESSION_PROTECTION_CMD: -5
[ 327.358583] iwlwifi 0000:00:14.3: Failed to send MAC_CONTEXT_CMD (action:2): -5
[ 327.358584] iwlwifi 0000:00:14.3: failed to update MAC f0:d4:15:b7:4b:11
[ 327.358590] iwlwifi 0000:00:14.3: Failed to send binding (action:3): -5
[ 327.358593] iwlwifi 0000:00:14.3: Failed to send MAC_CONTEXT_CMD (action:2): -5
[ 327.358594] iwlwifi 0000:00:14.3: failed to update MAC f0:d4:15:b7:4b:11
[ 327.358596] iwlwifi 0000:00:14.3: PHY ctxt cmd error. ret=-5
[ 327.928068] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x3f
[ 327.928079] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[ 327.928087] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
[ 327.928096] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10
demo@mx-moksha-live:~
$
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Sat Mar 29, 2025 5:27 pm
by AVLinux
@kmathern
Thanks for this report! I've been using this kernel for quite some time in AVL builds as well so this very good to know, I'm sure other silent sufferers have seen this too. Thanks for cross-referencing it in MX-23 as well, pretty much confirms it's the kernel itself... bummer!
6.12 and up were kind of rough sailing so I had been holding back but I need the IRQ threading support from Liquorix... I'll update the kernel in RC2
PS,
Thanks for your legendary XFCE4 removing one-liner, I've used that baby on numerous occasions!
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Sat Mar 29, 2025 5:41 pm
by kmathern
I'm running RC1 'fromiso'. Do you happen to know if our live-kernel-updater tool also works when running fromiso? (I haven't really used it that much)
If it does I might try installing the 6.7.12-1-liquorix kernel to RC1 with live-kernel-updater.
edit: nevermind, it appears live-kernel-updater doesn't like fromiso
Code: Select all
$ sudo live-kernel-updater
===============================================================================
Starting live-kernel-updater
===============================================================================
Error: The system is not a live-usb and no usb drives were detected
demo@mx-moksha-live:~
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Sun Mar 30, 2025 11:13 pm
by AVLinux
@kmathern
To be honest I have never made much use of the live remastering stuff so I'm not very knowledgeable about it..
I'm testing and working on an RC2 ISO and I'm a bit concerned because I built with the Liquorix 6.13 kernel and I'm experiencing lots of freezes in the live session in a VM (I use Gnome Boxes) I'll have to try a few bare metal boots, quite often VM stuff can kick up a fuss over kernels that are too new for the virtualization, I had so much trouble in this regard with Virtualbox I quit using it. If you happen to get around to putting an newer Kernel in the RC1 you're testing I'd be interested in hearing if it works for you without freezing issues.
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Mon Mar 31, 2025 8:59 am
by Senpai
AVLinux wrote: Sun Mar 30, 2025 11:13 pm
@kmathern
To be honest I have never made much use of the live remastering stuff so I'm not very knowledgeable about it..
I'm testing and working on an RC2 ISO and I'm a bit concerned because I built with the Liquorix 6.13 kernel and I'm experiencing lots of freezes in the live session in a VM (I use Gnome Boxes) I'll have to try a few bare metal boots, quite often VM stuff can kick up a fuss over kernels that are too new for the virtualization, I had so much trouble in this regard with Virtualbox I quit using it. If you happen to get around to putting an newer Kernel in the RC1 you're testing I'd be interested in hearing if it works for you without freezing issues.
I am testing your RC1 beta with the latest kernel liquorix 6.13.8-2, it installed fine, and with several programs open it doesn't seem to have problems, Is there any test I can do to try to reproduce those crashes, I am using QEMU with the MX “Popular Applications” Virt-Manager.
Best regards
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Mon Mar 31, 2025 9:37 am
by Freja
Hello, I felt body sick recentry, my replys be late.
about MX moksha default wallpaper, focus on Logo, "Pyramids and the Celestial-Sphere", oh perfect reconize,
Overall nice asian taste I like much. asian taste distribution is rare. This OS is "want to try without thinking!"
"Bodhi" is buddist's important concept well known, Distribution should have own phylosophy ideally, is great!
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Mon Mar 31, 2025 10:22 am
by kmathern
AVLinux wrote: Sun Mar 30, 2025 11:13 pm
@kmathern
To be honest I have never made much use of the live remastering stuff so I'm not very knowledgeable about it..
I'm testing and working on an RC2 ISO and I'm a bit concerned because I built with the Liquorix 6.13 kernel and I'm experiencing lots of freezes in the live session in a VM (I use Gnome Boxes) I'll have to try a few bare metal boots, quite often VM stuff can kick up a fuss over kernels that are too new for the virtualization, I had so much trouble in this regard with Virtualbox I quit using it. If you happen to get around to putting an newer Kernel in the RC1 you're testing I'd be interested in hearing if it works for you without freezing issues.
I did a remaster of RC1 with the Liquorix 6.7 kernel and it fixed the problem with wifi I was seeing.
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Mon Mar 31, 2025 6:34 pm
by AVLinux
Senpai wrote: Mon Mar 31, 2025 8:59 am
AVLinux wrote: Sun Mar 30, 2025 11:13 pm
@kmathern
To be honest I have never made much use of the live remastering stuff so I'm not very knowledgeable about it..
I'm testing and working on an RC2 ISO and I'm a bit concerned because I built with the Liquorix 6.13 kernel and I'm experiencing lots of freezes in the live session in a VM (I use Gnome Boxes) I'll have to try a few bare metal boots, quite often VM stuff can kick up a fuss over kernels that are too new for the virtualization, I had so much trouble in this regard with Virtualbox I quit using it. If you happen to get around to putting an newer Kernel in the RC1 you're testing I'd be interested in hearing if it works for you without freezing issues.
I am testing your RC1 beta with the latest kernel liquorix 6.13.8-2, it installed fine, and with several programs open it doesn't seem to have problems, Is there any test I can do to try to reproduce those crashes, I am using QEMU with the MX “Popular Applications” Virt-Manager.
Best regards
Thanks for letting me know, I am not seeing any freezing issues when I boot RC2 on bare metal so from what you are seeing and my testing on PC instead of in VM it seems fine with Kernel 6.13. I appreciate the info!
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Mon Mar 31, 2025 6:39 pm
by AVLinux
Freja wrote: Mon Mar 31, 2025 9:37 am
Hello, I felt body sick recentry, my replys be late.
about MX moksha default wallpaper, focus on Logo, "Pyramids and the Celestial-Sphere", oh perfect reconize,
Overall nice asian taste I like much. asian taste distribution is rare. This OS is "want to try without thinking!"
"Bodhi" is buddist's important concept well known, Distribution should have own phylosophy ideally, is great!
Hi
@Freja hope you are feeling better!
I can't really take any credit for the Buddhist influence (although I very much admire that worldview) Bodhi Linux and Moksha have been influenced by Buddhist ideas and artwork since they started several years ago. I'm just trying to preserve it's established green look and mold the MX artwork to match it's established look. I hope you don't mind I took some artistic liberties with the MX Logo.
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Mon Mar 31, 2025 6:41 pm
by AVLinux
kmathern wrote: Mon Mar 31, 2025 10:22 am
AVLinux wrote: Sun Mar 30, 2025 11:13 pm
@kmathern
To be honest I have never made much use of the live remastering stuff so I'm not very knowledgeable about it..
I'm testing and working on an RC2 ISO and I'm a bit concerned because I built with the Liquorix 6.13 kernel and I'm experiencing lots of freezes in the live session in a VM (I use Gnome Boxes) I'll have to try a few bare metal boots, quite often VM stuff can kick up a fuss over kernels that are too new for the virtualization, I had so much trouble in this regard with Virtualbox I quit using it. If you happen to get around to putting an newer Kernel in the RC1 you're testing I'd be interested in hearing if it works for you without freezing issues.
I did a remaster of RC1 with the Liquorix 6.7 kernel and it fixed the problem with wifi I was seeing.
Thanks very much for taking the time to do that and letting me know, the generosity of the MX devs is always noticed and appreciated!
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Wed Apr 02, 2025 4:50 am
by loik
Hello, forum.
I followed the link to MX-23.5-Bodhi yesterday.
I am very happy that this respin has been created.
I had 2020/2021 Bodhi 5.0.0 with kernel 4.9.0-6-686 i686.
I liked to use it, but then neglected it at some point for disk space reasons.
I had concentrated on MX.
So I'm all the more pleased that Bodhi is now also available in an MX version, with all MX tools ( MX snapshot yay ).
Thank you very much.
But when I called up the old 32bit Bodhi ( Ubuntu ), I had to realize that it only needs about 400 MB RAM, in contrast to the current 64bit Debian MX variant, which needs at least 1GB RAM. ( but both used in the VM as live iso )
Will there also be a 32bit MX-Bodhi ?
Suggestion for improvement for the next respin:
Pre-install the MX conkys.
Also the xfce4-appfinder and place it in the taskbar.
( please not rofi :)
I was fine with my personal setup.
Bodhi-Mosha is really chic.
But when I was almost done and wanted to take a MX-snapshot, the system froze for a moment due to swap space problems.
This was followed by something like a “Moksha restart”.
After that, many icons were missing.
The gaps you can see on the attached screenshots are actually filled with icons.
Icons are also missing in the menus.
The programs can still be started, both in the menus and in the task bar.
Only the icons are missing.
I like the replacement icon theme automatically selected by the system when the system hangs.
Do any of you recognize its name?
In the settings -> Appearance -> Application theme ( GTK & Icons ), the tab is empty.
But the Gtk applications are still there.
There was another place where you could also choose the icon theme.
But I can't find that again today.
(It takes some getting used to with Bodhi, remembering where to make which settings).
However, the icon theme is still installed and available in /usr/share/icons.
Uninstalling and reinstalling did not change anything.
Installing another icon theme “Numix” has not improved anything either.
The icon settings module remains empty.
How can I fix this?
Translated with DeepL.com (free version)
Code: Select all
/etc/lsb-release: Zeile 2: Moksha: Kommando nicht gefunden.
Snapshot created on: 20250401_2101
System:
Kernel: 6.6.12-1-liquorix-amd64 [6.6-16~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
intel_pstate=disable rcupdate.rcu_expedited=1 quiet threadirqs splash lang=de_DE kbd=de,us
tz=Europe/Berlin
Desktop: Moksha v: 0.4.1.18373 vt: 7 dm: LightDM v: 1.32.0 Distro: MX_MOKSHA-23-RC1_x64 Out of
Bodhi TBD base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Kvm System: QEMU product: Standard PC (Q35 + ICH9, 2009) v: pc-q35-7.2
serial: <superuser required> Chassis: type: 1 v: pc-q35-7.2 serial: <superuser required>
Mobo: N/A model: N/A serial: N/A BIOS: SeaBIOS v: 1.16.3-debian-1.16.3-2~bpo12+1
date: 04/01/2014
CPU:
Info: model: Intel Core i5-3470S bits: 64 type: SMP arch: Ivy Bridge gen: core 3 level: v2
built: 2012-15 process: Intel 22nm family: 6 model-id: 0x3A (58) stepping: 9 microcode: 0x21
Topology: cpus: 4x cores: 1 smt: <unsupported> cache: L1: 4x 64 KiB (256 KiB)
desc: d-1x32 KiB; i-1x32 KiB L2: 4x 4 MiB (16 MiB) desc: 1x4 MiB L3: 4x 16 MiB (64 MiB)
desc: 1x16 MiB
Speed (MHz): avg: 2893 min/max: N/A cores: 1: 2893 2: 2893 3: 2893 4: 2893 bogomips: 23147
Flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: itlb_multihit status: Not affected
Type: l1tf mitigation: PTE Inversion; VMX: flush not necessary, SMT disabled
Type: mds mitigation: Clear CPU buffers; SMT Host state unknown
Type: meltdown mitigation: PTI
Type: mmio_stale_data status: Unknown: No mitigations
Type: retbleed status: Not affected
Type: spec_rstack_overflow status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW, STIBP: disabled, RSB
filling, PBRSB-eIBRS: Not affected
Type: srbds status: Unknown: Dependent on hypervisor status
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Red Hat QXL paravirtual graphic card driver: qxl v: kernel ports: active: Virtual-1
empty: Virtual-2,Virtual-3,Virtual-4 bus-ID: 00:01.0 chip-ID: 1b36:0100 class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 compositors: 1: enlightenment 2: Picom v: 10 driver: X:
loaded: N/A unloaded: fbdev,modesetting,vesa dri: swrast gpu: qxl note: X driver n/a
display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1600x900 s-dpi: 96 s-size: 422x237mm (16.61x9.33") s-diag: 484mm (19.05")
Monitor-1: Virtual-1 res: 1600x900 hz: 60 size: N/A modes: max: 1024x768 min: 640x480
API: OpenGL v: 4.5 Mesa 24.2.8-1mx23ahs renderer: llvmpipe (LLVM 15.0.6 256 bits)
direct-render: Yes
Audio:
Device-1: Intel 82801I HD Audio vendor: Red Hat QEMU Virtual Machine driver: snd_hda_intel
v: kernel bus-ID: 00:1b.0 chip-ID: 8086:293e class-ID: 0403
API: ALSA v: k6.6.12-1-liquorix-amd64 status: kernel-api tools: alsamixer,amixer
Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Red Hat Virtio 1.0 network driver: virtio-pci v: 1 modules: virtio_pci pcie: gen: 1
speed: 2.5 GT/s lanes: 1 port: N/A bus-ID: 01:00.0 chip-ID: 1af4:1041 class-ID: 0200
IF-ID-1: eth0 state: up speed: -1 duplex: unknown mac: <filter>
Drives:
Local Storage: total: 0 KiB used: 0 KiB
Partition:
Message: No partition data found.
Swap:
Kernel: swappiness: 10 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 256 MiB used: 512 KiB (0.2%) priority: 100 dev: /dev/zram0
Sensors:
Src: lm-sensors+/sys Message: No sensor data found using /sys/class/hwmon or lm-sensors.
Repos:
Packages: pm: dpkg pkgs: 2354 libs: 1332 tools: apt,apt-get,aptitude,synaptic pm: rpm pkgs: 0
pm: flatpak pkgs: 0
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/bodhi-repo.list
1: deb http://packages.bodhilinux.com/bodhi bookworm b7debbie
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bookworm main non-free
2: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bookworm ahs
Info:
Processes: 359 Uptime: 2h 20m wakeups: 13 Memory: 3.83 GiB used: 1.87 GiB (48.8%) Init: systemd
v: 252 target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: BIOS (legacy, CSM, MBR)
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Wed Apr 02, 2025 7:40 am
by AVLinux
Hi, thanks for taking a look
There is a tool for this in the 'Accessories' menu called 'MX Moksha Action - Rebuild Efreet Icon Cache' run that tool and it should fix your issue, it appears your Icon cache has been lost or corrupted. I will not be maintaining a 32bit version, in fact it appears upcoming Debian Trixie is dropping 32bit from the Debian Installer options, 32bit libs and apps will still be in Debian itself but not part of the installer options so Distros will completely have do 32bit builds and installs with their own resources. I'm still Debating a Conky, Bodhi Linux already has dozens of really cool Desktop modules and to me MX Conky packaging is too much potentially unused stuff. For a searchable appfinder hit the 'Windows' key and one will appear!
Bodhi Linux itself still has 32bit in Bodhi 7, unknown if they will continue with 32bit in BL8 yet.
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Wed Apr 02, 2025 8:22 am
by Eadwine Rose
@AVLinux Want me to close this topic, since RC2 is out?
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Wed Apr 02, 2025 8:31 am
by AVLinux
Eadwine Rose wrote: Wed Apr 02, 2025 8:22 am
@AVLinux Want me to close this topic, since RC2 is out?
Prolly a good idea, thanks for your tireless Admin work!
Re: MX Moksha "Out of Bodhi" Testing Release RC1
Posted: Wed Apr 02, 2025 8:31 am
by Eadwine Rose
You're welcome, and thanks