- This topic has 709 replies, 38 voices, and was last updated Jan 30-4:02 pm by Brian Masinick.
-
Posts
-
olsztyn
Ok – it does seem like a kerne issue.
What version is the liquorix kernel 6.6.?
I’ll try compiling the kernel to the latest in kernel.orgFor testing I was using Liquorix kernel 6.6.13-1-liquorix-amd64, seems the only one left in 6.6 version, before they moved on to higher versions.
But this issue does not happen with Liquorix 6.16 or 6.18 either. So perhaps this is an opportunity to move antiX to one of these?
Liqorix 6.16 gained lots of positive testing in MX 25 ahs, recently MX moved to Liquorix 6.17…
These Liqorix 6.16 reportedly resolve sound issues existing in debian versions 6.6 or 6.12 with pipewire. This was reported in MX forum recently.- This reply was modified 9 months ago by olsztyn.
Live antiX Boot Options (Previously posted by Xecure):
http://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters
anticapitalista
antiX-25 will ship with 6.6 (and 5.10). 6.16 is EOL and 6.18 has not been tested at all on antiX.
What upstream (kernel.org) version is the liquorix version 6.6.13-1 built from
Ours is 6.6.101
Latest upstream is 6.6.119.
Let’s hope upstream fixed the issue somewhere between 6.6.101 and 6.6.119Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
antiX-25 will ship with 6.6 (and 5.10)
What upstream (kernel.org) version is the liquorix version 6.6.13-1 built fromI am not sure how to determine this. This liquorix kernel shows latest version 6.6-17.1 trixie but not sure this is the piece of info you are looking for.
It would be great if 6.6 could be fixed, so looking forward to it…- This reply was modified 9 months ago by olsztyn.
- This reply was modified 9 months ago by olsztyn.
Live antiX Boot Options (Previously posted by Xecure):
http://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters
Brian Masinick
I also have very good results with Liquorix kernels. Even newer kernels work across a surprisingly large range of systems – I’ve been able to use them on both new and old systems. My Dell Inspiron 5558 is one of the best examples. The technology there is old enough that a V4.4 kernel used to work fine, but so does a new kernel. I’ve not been using this hardware much over the past few months, but it actually works well with V4, V5 and V6 kernels. My old Lenovo Thinkpad X201 is another example of a system that works with V4, V5 and V6 kernels.
My newest systems (HP-14 and Thinkpad T14 Gen 3) don’t recognize WiFi with V5 kernels, but both work fine with the V6 kernel. I like the idea of making a newer vintage Liquorix kernel available and I can attest to their quality and performance, though I’m not certain if we’d want to replace the 6.6.101 kernel with a newer Liquorix kernel or just make their repo or a newer kernel in our repo.
Depending on how much longer we test with Beta or Release Candidates, we could try a Liquorix kernel from a more recent LTS kernel and add it to our choices. If it proves usable to our V6 user community it could replace our 6.6 kernel, then we’d only have to maintain the V5 kernel; if V6 users have trouble, then we can remain with our current kernel choices. I’ve been testing, between antiX 23.2 and 25 Alpha and Beta tests both our V6 kernels and the Liquorix kernels; both work seamlessly for me.
--
Brian Masinick
Alternate "Search B":
This search pageBassman
@olsztyn
Same issue here. Networkmanager is installed including all dependencies.Running beta2 fluxbox dinit. Using Dinit-service-manager
(via controlcentre) I found the service “NetworkManager”, which did not work. I checked “Add” and found the service “networkmanager”,(no uppercase letters)
which I activated and immediately had internet-connection.
Then selected the service “connmand”, removed it and networkmanager was still running, providng a stable network-connection.
I’m very happy, cause connman is absolutely unreliable on my machine.
Best regards
BassmanDepending on how much longer we test with Beta or Release Candidates, we could try a Liquorix kernel from a more recent LTS kernel and add it to our choices. If it proves usable to our V6 user community it could replace our 6.6 kernel, then we’d only have to maintain the V5 kernel
I am posting now using Liquorix 6.18 kernel and it seems to work great on laptops i have tested so far.
On the other hand I will also be happy with kernel 6.6 antiX version if and when it is fixed. Here, many thanks to @anticapitalista for trying to do it.
I have not tested Liquorix kernel 6.18 on my oldest laptops (from 2007) but Liquorix kernel 6.16 proved to be running well on those.Update:
Liquorix kernel 6.18 proves to work fine on my Thinkpad X61 (Core2Duo) from about 2007 after all…
The initial memory footprint is about 230Mb in my setting, so really nice. And hopefully fixes some sound problems with pipewire some reported in MX forum.
But this would mean for me two separate antiX images to run, which could be avoided when the fixed antiX kernel 6.6 is available, then one antiX image would be across all my laptops.- This reply was modified 9 months ago by olsztyn.
Live antiX Boot Options (Previously posted by Xecure):
http://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters@Bassman:
This is a valuable test experience ending in success. I will soon get back to testing Dinit on my laptops, hopefully also with such success.
Thanks and regards…Live antiX Boot Options (Previously posted by Xecure):
http://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersBrian Masinick
Depending on how much longer we test with Beta or Release Candidates, we could try a Liquorix kernel from a more recent LTS kernel and add it to our choices. If it proves usable to our V6 user community it could replace our 6.6 kernel, then we’d only have to maintain the V5 kernel
I am posting now using Liquorix 6.18 kernel and it seems to work great on laptops i have tested so far.
On the other hand I will also be happy with kernel 6.6 antiX version if and when it is fixed. Here, many thanks to @anticapitalista for trying to do it.
I have not tested Liquorix kernel 6.18 on my oldest laptops (from 2007) but Liquorix kernel 6.16 proved to be running well on those.Update:
Liquorix kernel 6.18 proves to work fine on my Thinkpad X61 (Core2Duo) from about 2007 after all…
The initial memory footprint is about 230Mb in my setting, so really nice. And hopefully fixes some sound problems with pipewire some reported in MX forum.
But this would mean for me two separate antiX images to run, which could be avoided when the fixed antiX kernel 6.6 is available, then one antiX image would be across all my laptops.Your experience with the Liquorix kernel 6.18 mirrors my findings over the past several years with Liquorix kernels.
Incidentally, in the entire history of Liquorix kernels I’ve had only two of them misbehave or not work; the problems were fixed within 24 hours, and the two instances were years apart. That’s better than some stock kernels.For me, the 5.10 Linux kernel was a problem. Though it’s been fixed now and it works on my older systems, it wasn’t until pretty late 5.10 updates that it finally worked consistently on my Dell Inspiron 5558; I distinctly recall 5.10 – I think .42 or similar inconsistently recognized and populated /dev. Needless to say, on days that it wasn’t recognizing /dev it was a huge problem, so I went almost exclusively to Liquorix during that time; eventually it got fixed and I checked it again, but often I’d just run a 4.19 kernel or get a fresh Liquorix kernel.
Anyway, regardless of what we do, when we release I’ll probably keep our V6 kernel on my Thinkpad T14, add a Liquorix kernel as an option and ditch the V5 kernel. I’ll do the same on my HP-14. If I install on my Dell, I’ll keep our V5 and V6 kernels.
--
Brian Masinick
Alternate "Search B":
This search pageBrian Masinick
This is a valuable test experience ending in success. I will soon get back to testing Dinit on my laptops, hopefully also with such success.
Thanks and regards.runit, dinit, and sysVinit have been rock solid on Beta 2; s6-rc has been pretty good too. For reasons I don’t completely understand, when LIVE s6-66 runs okay but I’ve had to tinker with it both live and installed; it worked much better on an earlier @ProwlerGr int-diversity respin. s6-66 services work, but they currently have to be invoked on the command line. Once that’s fixed, I’m sure that s6-66 will be really good. At the moment I like the dinit setup better; that may change once all of the services are working 100%.
--
Brian Masinick
Alternate "Search B":
This search pageBrian Masinick
mw # antiX Beta 2 dinit 01:49:07 PM, 12/28/25 PID TTY STAT TIME COMMAND 1 ? S 0:00 /lib/dinit/dinit Private + Shared = RAM used Program 152.0 KiB + 47.5 KiB = 199.5 KiB seatd 324.0 KiB + 133.5 KiB = 457.5 KiB dbus-launch 304.0 KiB + 160.5 KiB = 464.5 KiB startup 344.0 KiB + 232.5 KiB = 576.5 KiB udevil 356.0 KiB + 357.5 KiB = 713.5 KiB icewm-session 668.0 KiB + 330.5 KiB = 998.5 KiB devmon 716.0 KiB + 322.5 KiB = 1.0 MiB dinit 840.0 KiB + 344.5 KiB = 1.2 MiB desktop-session 908.0 KiB + 555.0 KiB = 1.4 MiB agetty (6) 928.0 KiB + 693.5 KiB = 1.6 MiB at-spi-bus-launcher 1.1 MiB + 639.5 KiB = 1.7 MiB dbus-daemon (3) 1.5 MiB + 719.5 KiB = 2.2 MiB pipewire-pulse 1.8 MiB + 847.5 KiB = 2.6 MiB gvfsd 2.2 MiB + 881.5 KiB = 3.1 MiB conky 936.0 KiB + 2.3 MiB = 3.3 MiB sudo (2) 3.5 MiB + 29.5 KiB = 3.6 MiB udevd 3.1 MiB + 612.5 KiB = 3.7 MiB connmand 1.2 MiB + 3.0 MiB = 4.1 MiB dhcpcd (5) 3.2 MiB + 1.4 MiB = 4.6 MiB bash (2) 3.6 MiB + 1.2 MiB = 4.8 MiB pipewire 5.2 MiB + 1.3 MiB = 6.5 MiB slimski 5.2 MiB + 1.6 MiB = 6.8 MiB wpa_supplicant 5.7 MiB + 2.7 MiB = 8.3 MiB icewm 6.9 MiB + 1.7 MiB = 8.6 MiB wireplumber 4.6 MiB + 5.2 MiB = 9.8 MiB volumeicon 13.7 MiB + 6.4 MiB = 20.1 MiB roxterm 115.9 MiB + 1.9 MiB = 117.8 MiB Xorg --------------------------------- 220.1 MiB ================================= System: Kernel: 6.18.2-1-liquorix-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 clocksource: tsc Desktop: IceWM v: 3.9.0 dm: slimski v: 1.5.0 Distro: antiX-25-b2_x64-full Stephen Kapos 17 December 2025 base: Debian GNU/Linux 13 (trixie) Machine: Type: Laptop System: LENOVO product: 21CF003TUS v: ThinkPad T14 Gen 3 serial: <superuser required> Chassis: type: 10 serial: <superuser required> Mobo: LENOVO model: 21CF003TUS v: SDK0T76530 WIN serial: <superuser required> part-nu: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3 uuid: <superuser required> Firmware: UEFI vendor: LENOVO v: R23ET82W (1.58 ) date: 03/04/2025 Battery: ID-1: BAT0 charge: 53.8 Wh (98.6%) condition: 54.6/52.5 Wh (104%) volts: 16.8 min: 15.44 model: Celxpert LNV-5B10W51866� type: Li-poly serial: <filter> charging: status: full control: start: 0% end: 100% cycles: 34 CPU: Info: 8-core model: AMD Ryzen 7 PRO 6850U with Radeon Graphics bits: 64 type: MT MCP smt: enabled arch: Zen 3+ rev: 1 cache: L1: 512 KiB L2: 4 MiB L3: 16 MiB Speed (MHz): avg: 1397 min/max: 1600/4769 boost: enabled cores: 1: 1397 2: 1397 3: 1397 4: 1397 5: 1397 6: 1397 7: 1397 8: 1397 9: 1397 10: 1397 11: 1397 12: 1397 13: 1397 14: 1397 15: 1397 16: 1397 bogomips: 86239 Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Rembrandt [Radeon 680M] vendor: Lenovo driver: amdgpu v: kernel arch: RDNA-2 pcie: speed: 16 GT/s lanes: 16 ports: active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4, DP-5, DP-6, HDMI-A-1, Writeback-1 bus-ID: 04:00.0 chip-ID: 1002:1681 class-ID: 0300 temp: 44.0 C Device-2: Chicony Integrated Camera driver: uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 5-1:2 chip-ID: 04f2:b74f class-ID: fe01 serial: <filter> Display: server: X.Org v: 21.1.16 driver: X: loaded: amdgpu unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu resolution: 1920x1200~60Hz API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.0.7-2 glx-v: 1.4 direct-render: yes renderer: AMD Radeon Graphics (radeonsi rembrandt LLVM 19.1.7 DRM 3.64 6.18.2-1-liquorix-amd64) device-ID: 1002:1681 Info: Tools: api: eglinfo,glxinfo x11: xdriinfo, xdpyinfo, xprop, xrandr Network: Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet vendor: Lenovo driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: 2000 bus-ID: 01:00.0 chip-ID: 10ec:8168 class-ID: 0200 IF: eth0 state: down mac: <filter> Device-2: Qualcomm QCNFA765 Wireless Network Adapter vendor: Lenovo driver: ath11k_pci v: kernel pcie: speed: 5 GT/s lanes: 1 bus-ID: 02:00.0 chip-ID: 17cb:1103 class-ID: 0280 IF: wlan0 state: up mac: <filter> Drives: Local Storage: total: 476.94 GiB used: 25.89 GiB (5.4%) ID-1: /dev/nvme0n1 vendor: Micron model: MTFDKBA512TFK size: 476.94 GiB speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter> fw-rev: 7003V5LN temp: 29.9 C scheme: GPT Partition: ID-1: / size: 93.31 GiB used: 25.89 GiB (27.7%) fs: ext4 dev: /dev/nvme0n1p5 ID-2: /boot/efi size: 96 MiB used: 276 KiB (0.3%) fs: vfat dev: /dev/nvme0n1p1 Unmounted: ID-1: /dev/nvme0n1p2 size: 95.37 GiB fs: ext4 ID-2: /dev/nvme0n1p3 size: 95.37 GiB fs: ext4 ID-3: /dev/nvme0n1p4 size: 95.37 GiB fs: ext4 ID-4: /dev/nvme0n1p6 size: 95.37 GiB fs: ext4 Info: Memory: total: N/A available: 14.4 GiB used: 1.61 GiB (11.2%) Processes: 336 Power: uptime: 4m states: freeze,mem,disk suspend: s2idle wakeups: 0 hibernate: platform Init: Dinit v: 0.20.0 default: 2 Packages: pm: dpkg pkgs: 2130 Compilers: gcc: 14.2.0 Shell: Bash v: 5.2.37 running-in: roxterm pinxi: 3.3.40-1--
Brian Masinick
Alternate "Search B":
This search pageSystem:
Kernel: 6.18.2-1-liquorix-amd64 arch: x86_64 bits: 64
compiler: gcc v: 12.2.0Nice… You are running Liquorix kernel 6.18 and all that in a very low memory footprint on Dinit!
When I get back to testing under Dinit (very shortly) I will try such thing…In the interim, I am trying to re-think my kernel strategy across the board, but in any case looks like I will keep the antiX kernel 5.10 for my dedicated ‘special purpose’ boxes, such as my wife’s music/TV, playing round the clock in the kitchen and in the summer house in Europe when we go there for the summer time. This is though if no sound quality issue with pipewire is detectable. Otherwise it may look like kernel 6.6, when fixed or Liquorix 6.18 across except two laptops with Broadcom WiFi chips, where antiX 6.6 kernel works fine.
This would be mostly because I am still failing to properly compile kernel 6.18 with broadcom-sta-dkms modules so those two laptops see WiFi…- This reply was modified 9 months ago by olsztyn.
Live antiX Boot Options (Previously posted by Xecure):
http://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersBrian Masinick
ou are running Liquorix kernel 6.18 and all that in a very low memory footprint on Dinit!
Yeah, I was a bit surprised by that myself!
--
Brian Masinick
Alternate "Search B":
This search page
Wallon
Bonjour,
If you choose a new Liquorix kernel, it would be good if it were fully compatible with the proprietary Nvidia 550 driver included in Debian 13 Trixie.
Best,
WallonWallon
Bonjour,
I installed antix 25 Full 64-bit beta 2 sysvinit in [fr] with a Belgian keyboard.
Test:
Create a new user who uses English (US).Process:
I create the user “english” with their password. Everything works!
I log into the “english” user session, but everything is in French.
I go to the “User Language” application. I choose English (US). It works!
I ask to localize the programs by clicking on the first icon at the bottom of the window. It works!
I ask to translate the menu by clicking on the second icon at the bottom of the window. antix is completely broken for the “english” user!
I had to press the button on my computer to exit antiX. The keyboard was no longer responding at all!Best,
Wallonstevesr0
Hi anticapitalista,
re the error messages about service files for nonrunning inits when an upgrade is performed,
Any updates will be for all inits, not just the one booted into. So for example, you will get runit-service updates even when not-installed.Presumably, because only one upgrade path for antiX systems can be maintained and with a multiinit version, it will have to cover all inits?
What if, in a system installed to a hard drive, the user/”owner” deletes the unwanted init packages?
- You must be logged in to reply to this topic.