- This topic has 436 replies, 24 voices, and was last updated Mar 21-8:50 pm by Brian Masinick.
-
Posts
-
Brian Masinick
re: Bluetooth on alpha and antix in general.
I would be interested in trying a “new” headset or headphones or if there was one that was regarded as easily detected by “bluetooth manager”, paired well and was inexpensive (<$50).
stevesr0
This article https://www.consumerreports.org/headphones/best-headphones-for-under-50-dollars-a3732650590/ includes both wired and wireless, ear buds and headphones. A few of them border or exceed the $50 price point, but there are 1 or two options in the $30-40 range. The JBL Tune 510BT looks particularly appealing and it is available at several stores or it can be shopped through online retailers too.
https://www.consumerreports.org/products/headphones-29043/stereo-headphone-29903/jbl-tune-510bt-403385/--
Brian MasinickBrian Masinick
I do like the Anker Soundcore series. I have the Soundcore Life Q10; the Q20 is currently on sale at Amazon with free Prime delivery (if you happen to have it).
The newer Q30 is also available in refurbished form at %59.99. The Q10, though I’ve had Linux Bluetooth issues, works fine with Android and Chromebook implementations of Bluetooth and they also have the auxiliary round serial cable, plus USB charging.--
Brian Masinickolsztyn
I would be interested in trying a “new” headset or headphones or if there was one that was regarded as easily detected by “bluetooth manager”, paired well and was inexpensive (<$50).
To add to the choices provided above by Brian, I sometimes look at discount stores, such as Marshalls or TJ Maxx, where I bought my bluetooth headphones – Altec Lansing Evolution 2. I think I paid $29 at that time. I am sure it does not compare in terms of build to the Bose headphones I bought my daughter during her studies at her university (about $300) but Altec Lansing is a good brand of audio devices and sound is excellent. I did not want to spend much money so went for much cheaper one for myself…
It works great with antiX 23 bluetooth. Tested on Grup Yorum music played on Thinkpad T410 internal bluetooth and X61 with a bluetooth adapter…Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parametersstevesr0
(Wrote a reply, then was not logged in?!)
Hi olsztyn and The Mas,
Thanks for info. I will check those out.
Congratulations olsztyn if you got Bluetooth headphones working on antix23 alpha without systemd!
If multiple users can make the same model of headphone work on their different systems, it serves as a “proof of concept” of sorts that the software “works”. (Obviously, it is important that general software works with LOTS of different hardware.)
stevesr0
Perhaps pulseaudio was (reportedly) exhibiting some latency as measured by instruments. How with so many components on the way pipewire is not expected any latency?
I believe that pulseaudio might beon the way out, replaced by pipewire just for sound routing, I do not think sound latency of microsecond makes a big difference to my ear, but I do not like architecture so fragmented into so many component, almost like a showcase of complexity, often seen in Linux world.Well, I take it back after reading a lot about pipewire/pulseaudio/Jack/Alsa architecture. My apologies for the above my uninformed opinion…
It turns out there is a reason for such many various components, to service variety of interfaces and applications. Bluetooth devices are one example. To interface audio traffic between sound device through alsa hand-off to pulseaudio and bluetooth interface to headphones (as one example) has been a challenge to do.
Pipewire seems to have all these components working finally within one architecture and reliably.
Perhaps this is the reason my bluethooth headphones are working great with pipewire and I think I remember having trouble to make them work with pulseaudio on top of alsa…Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersCongratulations olsztyn if you got Bluetooth headphones working on antix23 alpha without systemd!
If multiple users can make the same model of headphone work on their different systems, it serves as a “proof of concept” of sorts that the software “works”. (Obviously, it is important that general software works with LOTS of different hardware.)Well, it looks to me that these bluetooth headphones are not any exception and most other bluetooth models should work just fine in antiX 23 using pipewire infrastructure.
It starts looking to me that many troubles making bluetooth headphones and speakers work reliably in antiX was pulseaudio sitting on top of alsa. Now it appears that pipewire infrastructure has this handshake all resolved.
I would not be surprised if Brian’s bluetooth headphones started working just fine under antiX 23 and pipewire…- This reply was modified 3 months ago by olsztyn.
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersRobin
Many thanks, anticapitalista! Great work!
Finally I’ve managed to free up an USB stick for testing the new upcoming antiX 23. What should I say: It works great, mostly everything out of the box. Here the deatils. As expected in an alpha release some minor things require your attention.
Here my findings:1.) File name in checksum file doesn’t match the ISO filename present on server, so it fails:
$ shasum -c antiX-23-runit_x64-full.iso.sha256 shasum: antiX-23-runit_x64-full.iso: No such file or directory antiX-23-runit_x64-full.iso: FAILED open or read shasum: WARNING: 1 listed file could not be read $ cat antiX-23-runit_x64-full.iso.sha256 946cef599ea3eb9984612bb1bf98d12cccf94109e3001a5394c392f958ea3896 antiX-23-runit_x64-full.isoOK, this shows that the filename in the checksum file doesn’t match. After fixing it, the checksum matches:
$ shasum -c antiX-23-runit_x64-full.iso.sha256 antiX-23-alpha1-runit_x64-full.iso: OKCreating the Live USB on antiX 21/22 works flawlessly then:
=============================================================================== Starte live-usb-maker 2.41.18 =============================================================================== live-usb-maker 2.41.18 Live Mediengerät /dev/sdb gefunden Gerät /dev/sdd (29,5G SMI USB_DISK) wird als Ziel verwendet Datei /media/sda4/Arbeitsordner/Downloads/antiX23/antiX-23-alpha1-runit_x64-full.iso wird als Quelle verwendet Distro: antiX-23-runit_x64-full Grup Yorum 3 February 2023 Grub Konfiguration 2.0 gefunden gesamt benutzt unbelegt Gesamtes Laufwerk 29.5 GiB 29.5 GiB 1 MiB Hauptpartition 29.4 GiB 1.61 GiB 27.8 GiB UEFI Partition 50 MiB 32 MiB 18 MiB Bereit live-usb auf Gerät sdd ... mit Kopiere Datei /media/sda4/Arbeitsordner/Downloads/antiX23/antiX-23-alpha1-runit_x64-full.iso zu erstellen live-usb-maker 2.41.18: partition-clear >> partition-clear live-usb-maker 2.41.18: partition-make >> partition-make gpt Partitionierung wird verwendet live-usb-maker 2.41.18: makefs-bios >> makefs-bios live-usb-maker 2.41.18: makefs-uefi >> makefs-uefi Dateisystem Typ Größe Benutzt Verf. Verw% Eingehängt auf /dev/sdd1 ext4 29G 24K 29G 1% main /dev/sdd2 vfat 49M 512 49M 1% uefi live-usb-maker 2.41.18: copy-uefi >> copy-uefi Kopiere von iso auf Partition uefi Dateien [Ee][Ff][Ii] version Dell uefi memtest Bug beheben live-usb-maker 2.41.18: copy-main >> copy-main Kopiere von iso auf Partition main copy /antiX/vmlinuz copy /antiX/vmlinuz1 copy /antiX/initrd.gz copy remaining files ... live-usb-maker 2.41.18: check-usb-md5 >> check-usb-md5 Überprüfung von md5 für initrd.gz Überprüfung von md5 für linuxfs Überprüfung von md5 für vmlinuz1 Überprüfung von md5 für vmlinuz live-usb-maker 2.41.18: uuids >> uuids Benutze antiX/MX Grub Config 2.0 live-usb-maker 2.41.18: install >> Installieren extlinux version 6.04 Dateisystem Typ Größe Benutzt Verf. Verw% Eingehängt auf /dev/sdd1 ext4 29G 1,6G 28G 6% main /dev/sdd2 vfat 49M 13M 36M 26% uefi >> Abgeschlossen live-usb-maker took 10 minutes and 13 seconds.And booting from the USB antiX comes stright up with the desktop. It’s unbelievable fast, this runit. Never seen such a fast startup!
Here again a tiny glimpse in GUI needs your attention: Even when choosing modern kernel the second antiX boot screen will show
“legacy 4.19 kernel” in its header, while actually the proper modern kernel will come up.I’ll attach dmesg output and live logfiles from /live/boot-dev/Live-usb-storage/root/live-logs just in case you want to have a look into them. There have been some warnings and complaints during startup, but they flashed by that fast I wasn’t able to read them, and in the logfiles nothing of these shows up.
Next step was a complete system update via
apt-get update apt-get upgradesince
apt list --upgradable
showed lots of updated packages. Erverything went smooth.Then I installed the 6.1.10-antix.1-amd64-smp kernel from the repos, remastered and ran the live-kernel-updater.
Also this kernel runs fine here. Don’t see any issues by now. But the installation of the kernel hangs, even when it works properly:$ sudo apt-get install linux-headers-6.1.10-antix.1-amd64-smp linux-image-6.1.10-antix.1-amd64-smp Paketlisten werden gelesen… Fertig Abhängigkeitsbaum wird aufgebaut… Fertig Statusinformationen werden eingelesen… Fertig Die folgenden NEUEN Pakete werden installiert: linux-headers-6.1.10-antix.1-amd64-smp linux-image-6.1.10-antix.1-amd64-smp 0 aktualisiert, 2 neu installiert, 0 zu entfernen und 122 nicht aktualisiert. Es müssen 62,9 MB an Archiven heruntergeladen werden. Nach dieser Operation werden 343 MB Plattenplatz zusätzlich benutzt. Holen:1 http://repo.antixlinux.com/testing testing/main amd64 linux-headers-6.1.10-antix.1-amd64-smp amd64 6.1.10-antix.1-amd64-smp-1 [8.854 kB] Holen:2 http://repo.antixlinux.com/testing testing/main amd64 linux-image-6.1.10-antix.1-amd64-smp amd64 6.1.10-antix.1-amd64-smp-1 [54,0 MB] Es wurden 62,9 MB in 52 s geholt (1.205 kB/s). Vormals nicht ausgewähltes Paket linux-headers-6.1.10-antix.1-amd64-smp wird gewählt. (Lese Datenbank ... 175553 Dateien und Verzeichnisse sind derzeit installiert.) Vorbereitung zum Entpacken von .../linux-headers-6.1.10-antix.1-amd64-smp_6.1.10-antix.1-amd64-smp-1_amd64.deb ... Entpacken von linux-headers-6.1.10-antix.1-amd64-smp (6.1.10-antix.1-amd64-smp-1) ... Vormals nicht ausgewähltes Paket linux-image-6.1.10-antix.1-amd64-smp wird gewählt. Vorbereitung zum Entpacken von .../linux-image-6.1.10-antix.1-amd64-smp_6.1.10-antix.1-amd64-smp-1_amd64.deb ... Entpacken von linux-image-6.1.10-antix.1-amd64-smp (6.1.10-antix.1-amd64-smp-1) ... linux-headers-6.1.10-antix.1-amd64-smp (6.1.10-antix.1-amd64-smp-1) wird eingerichtet ... linux-image-6.1.10-antix.1-amd64-smp (6.1.10-antix.1-amd64-smp-1) wird eingerichtet ... dkms: running auto installation service for kernel 6.1.10-antix.1-amd64-smp:Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1/source/dkms.conf) Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1/source/dkms.conf) Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1/source/dkms.conf) Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1/source/dkms.conf) Deprecated feature: MODULES_CONF (/etc/dkms/framework.conf) Sign command: /lib/modules/6.1.10-antix.1-amd64-smp/build/scripts/sign-file Signing key: /var/lib/dkms/mok.key Public certificate (MOK): /var/lib/dkms/mok.pub Building module: Cleaning build area... make -j4 KERNELRELEASE=6.1.10-antix.1-amd64-smp KVER=6.1.10-antix.1-amd64-smp.... Signing module /var/lib/dkms/broadcom-sta/6.30.223.271/build/wl.ko Cleaning build area... wl.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.1.10-antix.1-amd64-smp/updates/dkms/ depmod... Deprecated feature: MODULES_CONF (/etc/dkms/framework.conf) Sign command: /lib/modules/6.1.10-antix.1-amd64-smp/build/scripts/sign-file Signing key: /var/lib/dkms/mok.key Public certificate (MOK): /var/lib/dkms/mok.pub Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1/source/dkms.conf) Building module: Cleaning build area... 'make' -j4 KVER=6.1.10-antix.1-amd64-smp USER_MODULE_NAME=rtl8821ce CONFIG_RTW_DEBUG=n........(bad exit status: 2) Error! Bad return status for module build on kernel: 6.1.10-antix.1-amd64-smp (x86_64) Consult /var/lib/dkms/rtl8821ce/5.5.2.1/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. failed! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 update-initramfs: Generating /boot/initrd.img-6.1.10-antix.1-amd64-smp W: No zstd in /usr/bin:/sbin:/bin, using gzip cryptsetup: ERROR: Couldn't resolve device overlay cryptsetup: WARNING: Couldn't determine root device WARNING: Unknown X keysym "dead_belowmacron" WARNING: Unknown X keysym "dead_belowmacron" WARNING: Unknown X keysym "dead_belowmacron" WARNING: Unknown X keysym "dead_belowmacron" I: The initramfs will attempt to resume from /dev/sda2 I: (UUID=57ab2d2d-e0e9-49e6-b8d0-d8bea277cf7c) I: Set the RESUME variable to override this. dpkg: Fehler beim Bearbeiten des Paketes linux-image-6.1.10-antix.1-amd64-smp (--configure): »installiertes post-installation-Skript des Paketes linux-image-6.1.10-antix.1-amd64-smp«-Unterprozess gab den Fehlerwert 1 zurück Fehler traten auf beim Bearbeiten von: linux-image-6.1.10-antix.1-amd64-smp E: Sub-process /usr/bin/dpkg returned an error code (1) demo@antix1:~ $ cat /var/lib/dkms/rtl8821ce/5.5.2.1/build/make.log DKMS make.log for rtl8821ce-5.5.2.1 for kernel 6.1.10-antix.1-amd64-smp (x86_64) Fr 10. Feb 15:37:46 CET 2023 make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/6.1.10-antix.1-amd64-smp/build M=/var/lib/dkms/rtl8821ce/5.5.2.1/build modules make[1]: Verzeichnis „/usr/src/linux-headers-6.1.10-antix.1-amd64-smp“ wird betreten CC [M] /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_cmd.o CC [M] /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_security.o CC [M] /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_debug.o CC [M] /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_io.o CC [M] /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_ioctl_query.o CC [M] /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_ioctl_set.o CC [M] /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_ieee80211.o CC [M] /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_mlme.o CC [M] /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_mlme_ext.o CC [M] /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_mi.o CC [M] /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_wlan_util.o /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_mlme.c: In function ‘rtw_drv_scan_by_self’: /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_mlme.c:3161:17: warning: this ‘else’ clause does not guard... [-Wmisleading-indentation] 3161 | else | ^~~~ /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_mlme.c:3164:25: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘else’ 3164 | goto exit; | ^~~~ /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_mlme_ext.c: In function ‘rtw_txpwr_init_regd’: /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_mlme_ext.c:259:20: warning: this statement may fall through [-Wimplicit-fallthrough=] 259 | if (rfctl->regd_name) | ^ /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_mlme_ext.c:261:9: note: here 261 | default: | ^~~~~~~ /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_mlme_ext.c: In function ‘mgt_dispatcher’: /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_mlme_ext.c:1329:38: warning: this statement may fall through [-Wimplicit-fallthrough=] 1329 | ptable->func = &OnAuthClient; | ~~~~~~~~~~~~~^~~~~~~~~~~~~~~ /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_mlme_ext.c:1331:9: note: here 1331 | case WIFI_ASSOCREQ: | ^~~~ CC [M] /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_vht.o CC [M] /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_pwrctrl.o CC [M] /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_rf.o CC [M] /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_chplan.o CC [M] /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_recv.o CC [M] /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_sta_mgt.o /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_rf.c: In function ‘dump_txpwr_lmt’: /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_rf.c:765:9: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 765 | if (IS_HARDWARE_TYPE_JAGUAR_AND_JAGUAR2(adapter)) | ^~ In file included from /var/lib/dkms/rtl8821ce/5.5.2.1/build/include/drv_types.h:60, from /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_rf.c:17: /var/lib/dkms/rtl8821ce/5.5.2.1/build/include/rtw_debug.h:220:9: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 220 | do {\ | ^~ /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_rf.c:767:17: note: in expansion of macro ‘RTW_PRINT_SEL’ 767 | RTW_PRINT_SEL(sel, "txpwr_lmt_5g_20_40_ref:0x%02x\n", rfctl->txpwr_lmt_5g_20_40_ref); | ^~~~~~~~~~~~~ CC [M] /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_ap.o /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_sta_mgt.c: In function ‘rtw_mfree_stainfo’: /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_sta_mgt.c:379:25: warning: the comparison will always evaluate as ‘true’ for the address of ‘lock’ will never be NULL [-Waddress] 379 | if (&psta->lock != NULL) | ^~ In file included from /var/lib/dkms/rtl8821ce/5.5.2.1/build/include/drv_types.h:108, from /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_sta_mgt.c:17: /var/lib/dkms/rtl8821ce/5.5.2.1/build/include/sta_info.h:263:17: note: ‘lock’ declared here 263 | _lock lock; | ^~~~ CC [M] /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/mesh/rtw_mesh.o CC [M] /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/mesh/rtw_mesh_pathtbl.o CC [M] /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/mesh/rtw_mesh_hwmp.o CC [M] /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_xmit.o CC [M] /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_p2p.o CC [M] /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_rson.o /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_ap.c: In function ‘rtw_ap_update_chbw_by_ifbmp’: /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_ap.c:4392:42: warning: the comparison will always evaluate as ‘true’ for the address of ‘padapters’ will never be NULL [-Waddress] 4392 | if (!(ifbmp & BIT(i)) || !dvobj->padapters) | ^ In file included from /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_ap.c:17: /var/lib/dkms/rtl8821ce/5.5.2.1/build/include/drv_types.h:1041:19: note: ‘padapters’ declared here 1041 | _adapter *padapters[CONFIG_IFACE_NUMBER];/*IFACE_ID_MAX*/ | ^~~~~~~~~ /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_ap.c:4412:42: warning: the comparison will always evaluate as ‘true’ for the address of ‘padapters’ will never be NULL [-Waddress] 4412 | if (!(ifbmp & BIT(i)) || !dvobj->padapters) | ^ /var/lib/dkms/rtl8821ce/5.5.2.1/build/include/drv_types.h:1041:19: note: ‘padapters’ declared here 1041 | _adapter *padapters[CONFIG_IFACE_NUMBER];/*IFACE_ID_MAX*/ | ^~~~~~~~~ CC [M] /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_tdls.o CC [M] /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_br_ext.o CC [M] /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_iol.o CC [M] /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_sreset.o /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_br_ext.c:20:18: fatal error: net/ipx.h: Datei oder Verzeichnis nicht gefunden 20 | #include <net/ipx.h> | ^~~~~~~~~~~ compilation terminated. make[2]: *** [scripts/Makefile.build:250: /var/lib/dkms/rtl8821ce/5.5.2.1/build/core/rtw_br_ext.o] Fehler 1 make[2]: *** Es wird auf noch nicht beendete Prozesse gewartet.... make[1]: *** [Makefile:2019: /var/lib/dkms/rtl8821ce/5.5.2.1/build] Fehler 2 make[1]: Verzeichnis „/usr/src/linux-headers-6.1.10-antix.1-amd64-smp“ wird verlassen make: *** [Makefile:2262: modules] Fehler 2Now every time when using apt for installing some additional program or updating the system it complains about the incomplete installed kernel package and tries to complete the installation, failing at the very same point always. No idea how to stop it from constantly retrying.
So far for now, more input to come.
Again, great work anticapitalista! Many thanks for this excelent OS.
Windows is like a submarine. Open a window and serious problems will start.
OK, board software didn’t accept my tar.gz, so here the repackaged to zip archive type.
And I noticed I missed to post the system information output from this device running on antiX 23 with 6.1.10-antiX1 kernel. Here you are:System: Kernel: 6.1.10-antix.1-amd64-smp arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: lang=de_DE quiet splasht disable=lxF desktop=zzz-icewm mount=all Desktop: IceWM v: 3.3.1 dm: slimski v: 1.5.0 Distro: antiX-23-runit_x64-full Grup Yorum 3 February 2023 base: Debian GNU/Linux bookworm/sid Machine: Type: Desktop Mobo: ASUSTeK model: P7P55-M v: Rev X.0x serial: <superuser required> BIOS: American Megatrends v: 0903 date: 07/09/2010 Battery: Device-1: hidpp_battery_0 model: Logitech MX Keys Wireless Keyboard serial: <filter> charge: Normal status: discharging Device-2: hidpp_battery_1 model: Logitech Marathon Mouse/Performance Plus M705 serial: <filter> charge: Normal status: discharging Memory: RAM: total: 7.76 GiB used: 1.89 GiB (24.4%) RAM Report: permissions: Unable to run dmidecode. Root privileges required. PCI Slots: Permissions: Unable to run dmidecode. Root privileges required. CPU: Info: model: Intel Core i3 540 bits: 64 type: MT MCP arch: Westmere gen: core 1 built: 2010-11 process: Intel 32nm family: 6 model-id: 0x25 (37) stepping: 5 microcode: 0x2 Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 4 MiB desc: 1x4 MiB Speed (MHz): avg: 1364 high: 1838 min/max: 1200/3067 scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 1210 2: 1838 3: 1204 4: 1204 bogomips: 24618 Flags: acpi aperfmperf apic arat arch_perfmon bts clflush cmov constant_tsc cpuid cx16 cx8 de ds_cpl dtes64 dtherm dts ept est flexpriority fpu fxsr ht lahf_lm lm mca mce mmx monitor msr mtrr nonstop_tsc nopl nx pae pat pbe pcid pdcm pebs pge pni popcnt pse pse36 pti rdtscp rep_good sep sse sse2 sse4_1 sse4_2 ssse3 syscall tm tm2 tpr_shadow tsc vme vmx vnmi vpid xtopology xtpr Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable Type: meltdown mitigation: PTI Type: mmio_stale_data status: Unknown: No mitigations Type: retbleed status: Not affected Type: spec_store_bypass status: Vulnerable Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: Retpolines, STIBP: disabled, RSB filling, PBRSB-eIBRS: Not affected Type: srbds status: Not affected Type: tsx_async_abort status: Not affected Graphics: Device-1: AMD Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor: ASUSTeK driver: radeon v: kernel alternate: amdgpu arch: TeraScale 2 code: Evergreen process: TSMC 32-40nm built: 2009-15 pcie: gen: 2 speed: 5 GT/s lanes: 16 ports: active: HDMI-A-1 empty: DVI-I-1,VGA-1 bus-ID: 01:00.0 chip-ID: 1002:68f9 class-ID: 0300 Display: server: X.Org v: 1.21.1.7 driver: X: loaded: radeon unloaded: fbdev,modesetting,vesa gpu: radeon display-ID: :0.0 screens: 1 Screen-1: 0 s-res: 2048x1152 s-dpi: 96 s-size: 541x304mm (21.30x11.97") s-diag: 621mm (24.43") Monitor-1: HDMI-A-1 mapped: HDMI-0 model: PMO S321-IQSC serial: <filter> built: 2021 res: 2048x1152 hz: 60 dpi: 74 gamma: 1.2 chroma: red: x: 0.655 y: 0.337 green: x: 0.322 y: 0.612 blue: x: 0.153 y: 0.059 white: x: 0.314 y: 0.329 size: 700x390mm (27.56x15.35") diag: 801mm (31.5") ratio: 16:9 modes: 2048x1152, 1920x1200, 1920x1080, 1920x1080i, 1600x1200, 1680x1050, 1680x945, 1400x1050, 1600x900, 1280x1024, 1440x900, 1280x960, 1366x768, 1360x768, 1280x800, 1152x864, 1280x768, 1280x720, 1024x768, 1024x576, 832x624, 800x600, 720x576, 848x480, 720x480, 640x480, 720x400 OpenGL: renderer: AMD CEDAR (DRM 2.50.0 / 6.1.10-antix.1-amd64-smp LLVM 15.0.6) v: 4.5 Mesa 22.3.3 direct render: Yes Audio: Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: ASUSTeK 5 driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:3b56 class-ID: 0403 Device-2: AMD Cedar HDMI Audio [Radeon HD 5400/6300/7300 Series] vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 1002:aa68 class-ID: 0403 Sound Server-1: ALSA v: k6.1.10-antix.1-amd64-smp running: yes Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK M4A785/P7P55 driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: c800 bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200 IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> IP v4: <filter> scope: global broadcast: <filter> IP v6: <filter> scope: link WAN IP: <filter> Bluetooth: Message: No bluetooth data found. Logical: Message: No logical block device data found. RAID: Message: No RAID data found. Drives: Local Storage: total: 262.38 GiB used: 116.42 GiB (44.4%) SMART Message: Unable to run smartctl. Root privileges required. ID-1: /dev/sda maj-min: 8:0 vendor: Maxtor model: STM3250318AS size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: CC38 scheme: MBR ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: SMI (STMicroelectronics) model: USB DISK size: 29.49 GiB block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 1100 scheme: GPT SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure? Message: No optical or floppy data found. Partition: ID-1: /live/boot-dev raw-size: 29.44 GiB size: 28.91 GiB (98.18%) used: 4 GiB (13.8%) fs: ext4 dev: /dev/sdb1 maj-min: 8:17 label: antiX-Live-usb uuid: 76ca61e0-47f8-4075-8448-e28989c3b64e ID-2: /media/ANTIX-UEFI raw-size: 49 MiB size: 48.2 MiB (98.43%) used: 12.3 MiB (25.4%) fs: vfat dev: /dev/sdb2 maj-min: 8:18 label: ANTIX-UEFI uuid: 2100-8C30 ID-3: /media/homeantiX raw-size: 49.02 GiB size: 47.95 GiB (97.82%) used: 1.38 GiB (2.9%) fs: ext4 dev: /dev/sda3 maj-min: 8:3 label: homeantiX uuid: e1991eba-59bf-4106-8a46-09b3ee0e94af ID-4: /media/rootantiX21 raw-size: 24.43 GiB size: 23.88 GiB (97.74%) used: 6.59 GiB (27.6%) fs: ext4 dev: /dev/sda1 maj-min: 8:1 label: rootantiX21 uuid: 9d2f9bb5-5d2f-4aad-96ed-12c96919bd8d ID-5: /media/sda4 raw-size: 155.27 GiB size: 151.78 GiB (97.75%) used: 104.44 GiB (68.8%) fs: ext4 dev: /dev/sda4 maj-min: 8:4 label: N/A uuid: c48583c1-9e59-4d5b-9114-c6041479f9f7 Swap: Kernel: swappiness: 10 (default 60) cache-pressure: 50 (default 100) ID-1: swap-1 type: partition size: 3.91 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda2 maj-min: 8:2 label: swapantiX uuid: 57ab2d2d-e0e9-49e6-b8d0-d8bea277cf7c Unmounted: Message: No unmounted partitions found. USB: Hub-1: 1-0:1 info: Full speed or root hub ports: 2 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900 Hub-2: 1-1:2 info: Intel Integrated Rate Matching Hub ports: 6 rev: 2.0 speed: 480 Mb/s chip-ID: 8087:0020 class-ID: 0900 Hub-3: 2-0:1 info: Full speed or root hub ports: 2 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900 Hub-4: 2-1:2 info: Intel Integrated Rate Matching Hub ports: 8 rev: 2.0 speed: 480 Mb/s chip-ID: 8087:0020 class-ID: 0900 Device-1: 2-1.7:3 info: Logitech Unifying Receiver type: Keyboard,Mouse,HID driver: logitech-djreceiver,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s power: 98mA chip-ID: 046d:c52b class-ID: 0300 Hub-5: 2-1.8:4 info: Genesys Logic Hub ports: 4 rev: 2.0 speed: 480 Mb/s power: 100mA chip-ID: 05e3:0608 class-ID: 0900 Device-1: 2-1.8.1:5 info: Silicon Motion - Taiwan (formerly Feiya ) USB DISK type: Mass Storage driver: usb-storage interfaces: 1 rev: 2.1 speed: 480 Mb/s power: 500mA chip-ID: 090c:2000 class-ID: 0806 serial: <filter> Sensors: System Temperatures: cpu: 41.5 C mobo: 35.0 C gpu: radeon temp: 52.5 C Fan Speeds (RPM): cpu: 1155 case-1: 1250 Power: 12v: 12.32 5v: N/A 3.3v: 3.42 vbat: N/A Repos: Packages: apt: 1650 lib: 787 Active apt repos in: /etc/apt/sources.list.d/antix.list 1: deb http: //repo.antixlinux.com/testing testing main nonfree nosystemd Active apt repos in: /etc/apt/sources.list.d/bookworm-backports.list 1: deb http: //deb.debian.org/debian bookworm-backports main contrib non-free non-free-firmware Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 1: deb http: //ftp.de.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: //ftp.de.debian.org/debian/ bookworm main contrib non-free non-free-firmware 2: deb http: //security.debian.org/ bookworm-security main contrib non-free non-free-firmware No active apt repos in: /etc/apt/sources.list.d/various.list Processes: CPU top: 5 of 181 1: cpu: 54.5% command: yad pid: 73538 mem: 31.5 MiB (0.3%) 2: cpu: 7.4% command: firefox-esr pid: 44899 mem: 535.1 MiB (6.7%) 3: cpu: 3.1% command: xorg pid: 40068 mem: 113.1 MiB (1.4%) 4: cpu: 2.7% command: firefox-esr pid: 45174 mem: 142.0 MiB (1.7%) 5: cpu: 1.0% command: xorg.0.log started by: leafpad pid: 70712 mem: 28.7 MiB (0.3%) Memory top: 5 of 181 1: mem: 535.1 MiB (6.7%) command: firefox-esr pid: 44899 cpu: 7.4% 2: mem: 174.7 MiB (2.1%) command: firefox-esr pid: 45206 cpu: 0.6% 3: mem: 142.0 MiB (1.7%) command: firefox-esr pid: 45174 cpu: 2.7% 4: mem: 122.5 MiB (1.5%) command: firefox-esr pid: 45123 cpu: 0.1% 5: mem: 117.3 MiB (1.4%) command: firefox-esr pid: 45172 cpu: 0.1% Info: Processes: 181 Uptime: 1h 47m wakeups: 17 Init: runit v: N/A runlevel: 2 tool: service Compilers: gcc: 12.2.0 alt: 12 Client: shell wrapper v: 5.2.15-release inxi: 3.3.19It also runs fine with the 5.10.142 kernel from ISO. Will check the 4.19 kernel from ISO next.
Windows is like a submarine. Open a window and serious problems will start.
Brian Masinick
olsztyn wrote: “I would not be surprised if Brian’s Bluetooth headphones started working just fine under antiX 23 and pipewire…”
I’d be absolutely thrilled if that were the case. Unfortunately, while the Soundcore Life Q10 model does work with all of my systems, including my Linux systems, it only works on Linux with the audio jack, at least on my HP-14. I removed and added packages repeatedly a year or two ago on my Dell Inspiron 5558 and my previous Acer Aspire 5 A515-55 and after a lot of struggle, got it working.
If it does work on antiX 23, great; if not, I’ll just use it with the jack rather than fight with it. Oddly, I don’t have any problem at all getting it to work with Bluetooth on my Android phone, which uses a Linux kernel, and I have no problem getting it to work with my Chromebook either. But this is NOT unique to antiX; that’s why I doubt Version 23 is going to make a miraculous difference. It didn’t work on PCLinuxOS, siduction, Legacy OS, openSUSE or EndeavourOS either.
Correction: I DID get it working on PCLinuxOS, and I had a note in another thread that I was able to get siduction, EndeavourOS, and openSUSE working too. Maybe it’ll be worth a little effort if it can physically work; I just did get it working, so there’s hope!
- This reply was modified 3 months ago by Brian Masinick.
--
Brian MasinickIf it does work on antiX 23, great; if not, I’ll just use it with the jack rather than fight with it. Oddly, I don’t have any problem at all getting it to work with Bluetooth on my Android phone, which uses a Linux kernel, and I have no problem getting it to work with my Chromebook either. But this is NOT unique to antiX; that’s why I doubt Version 23 is going to make a miraculous difference. It didn’t work on PCLinuxOS, siduction, Legacy OS, openSUSE or EndeavourOS either.
It is not antiX 23 alone I meant but antiX 23 plus pipewire sound system, which antiX 23 enables to work smoothly with bluetooth. In the past I had problems with bluetooth support under antiX because it needed pulseaudio sitting on top of alsa. This worked OK with some hardware but usually was troublesome to connect. Now with pipewire infrastructure to which anticapitalista put so much work to make it work with antiX 23, particularly modifying to be libelogind-free, it seems to work really nicely with hardware I had problems before… Pipewire replaces both pulseaudio and jack. It is now one, uniform infrastructure. As someone said: Linux finally has sound. And possibly even better sound support than Windows…
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersDid some more testing last hour.
First impressions form running antiX 23 (64bit-amd): It is really fast and stable, even when still in alpha state. Whao! Congratulations!If somebody needs to install most recent virtualbox 7.06 on this most recent antiX 23: It works out of the box, when using the .deb packages meant for bullseye from virtualbox download site (since there are no packages for bookworm by now):
https://download.virtualbox.org/virtualbox/7.0.6/virtualbox-7.0_7.0.6-155176~Debian~bullseye_amd64.deb
https://download.virtualbox.org/virtualbox/7.0.6/Oracle_VM_VirtualBox_Extension_Pack-7.0.6-155176.vbox-extpack
https://download.virtualbox.org/virtualbox/7.0.6/VBoxGuestAdditions_7.0.6.iso
https://download.virtualbox.org/virtualbox/7.0.6/SHA256SUMS
https://download.virtualbox.org/virtualbox/7.0.6/UserManual.pdfAnd from debian download site you need:
http://ftp.de.debian.org/debian/pool/main/libv/libvpx/libvpx6_1.9.0-1_amd64.deb
(sha256 checksum is c2466114b2eb1a6db926f0f530f335886ad824c6add69d01fb79373c4cdd4c08 )
http://ftp.de.debian.org/debian/pool/main/o/openssl/libssl1.1_1.1.1n-0+deb11u3_amd64.deb
(sha256 checksum is c3480bf90725c993187de02e5144e90ea81226e7e2538ba24687f5a0adc8ca5c )Don’t ever forget checking the checksums after downloading!
Install the two packages from debian first, this is important, otherwise virtualbox installation will fail. They are from bullseye, but will work properly in bookworm still. They are needed until virtualbox will come up with a true bookworm installer package. (Debian only provides old 6.x virtualbox versions even in bookworm)
sudo apt-get update sudo apt-get install ./libvpx6_1.9.0-1_amd64.deb ./libssl1.1_1.1.1n-0+deb11u3_amd64.deb sudo apt-get install ./virtualbox-7.0_7.0.6-155176~Debian~bullseye_amd64.debAfter installation has successfully finished, simply double click in zzzFM on the file Oracle_VM_VirtualBox_Extension_Pack-7.0.6-155176.vbox-extpack which will install the extensions in case you need them.
And then start virtualbox from antiX-Mainmenu→Programs→System
Add your existing virtual machine (if you have already one) which you had running already from within antiX 21/22 or even antiX 19 or 17.
Start the guest machine
Load the Guest addition iso into the virtual CD/DVD drive and let the most recent guest additions install in the guest system, in case you had previously run another version of virtualbox.
In case you need to print via LPT port:
Before starting virtualbox you need to enter some lines into terminal (e.g. roxterm):$ sudo rmmod lpOnly if you didn’t do this before on the very machine (e.g. when you’ve imported it on your former antiX version) you need the following lines to enter in command line (only once, no need to repeat if you did it on this very machine once before):
$ VBoxManage modifyvm "WinXP" --lptmode1 "/dev/parport0" $ VBoxManage modifyvm "WinXP" --lpt1 0x378 7The name “WinXP” must match the name you have assigned to the virtual machine in virtualbox, so replace my example when entering.
This should do the job in most cases. It will connect the LPT1 port of the host system, which is in antiX called /dev/parport0 to the lpt1 port within the guest system, so you can use it for printing.This runs as perfect in antiX 23 as in all the antiX versions before I’ve seen.
Windows is like a submarine. Open a window and serious problems will start.
There is an issue with user management.
If you add a new user in „User management” from antiX control center, section „Maintenance”, this new user can’t login from slimski login screen after you log off current demo user. Also the new user is not accepted by „Login management” from antiX control center section „Session”. It is simply not available for selection.
I’ve checked, the user folder was created properly, and also the system knows about the new user.But when checking the /etc/passwd file, the new user is marked with /usr/sbin/nologin which is probably the reason for this misbehaviour.
Can anybody confirm this is an issue and not my lack of experience merely?
Is it enough to remove the nologin part of the respective user’s line from /etc/passwd file to fix it? The existing user „demo” has /bin/bash instead of /usr/sbin/nologin at the very position in his line.
UPDATE:
——I’ve edited the /etc/passwd file now using the command
sudo vipwfrom
...:/usr/sbin/nologin
to
...:/bin/bashIn control center, section „login management” the new user wasn’t available still.
But after logging off from demo, the new user was now allowed to login from slimski antiX login screen.Only after this new login, the new user was present for selection as default user for automatic login in „login management” from antiX control center also.
So it is proven the routine for creating new user entries needs to get fixed in control center.
- This reply was modified 3 months ago by Robin.
Windows is like a submarine. Open a window and serious problems will start.
fladd
Shouldn’t the font in QT apps match the font in GTK apps by default? It seems the default for QT apps is a monospace font. It can easily be changed in the QT5 settings, but should probably by default be the matching one.
There is an issue with deleting files or folders in zzzFM on antiX 23.
Everything is fine as long the file or folder to delete lives in the same mount point as the current user has his home folder in (not necessarily the own home folder). Then, when using the „Del” key the file or folder is backuped in a subfolder of current users ~/.local/share folder. But as soon as the file lives somewhere else in file system (even on the very same partition, in a different mount point), the „Del” key does simply nothing, so the user starts looking for missing permissions, wrong rw settings of mounts, auto-remounted partitions after i/o-error, and thinks about a bunch of other common errors a file couldn’t get deleted for. It took me more than half an hour to figure this morning that it is a new bug in zzzFM on antiX 23: The default „Del” key works inconsistently now, functioning only for files in specific positions, while silently failing on most other files and folders unexpectedly. Using Shift+Del instead works fine on every file or folder immediately to actually delete instead of trash, but user expects the „Del” key to work consistently in the first place.
This inconsistent behaviour of default „Del” key should get fixed in some way. The key doesn’t work on at least 90% of files present in a default antiX system any longer.
Btw, it is not a good idea to move all files trashed to the recent users home folder, it will cause some heavy incompatibility: On multiuser systems this will easily exceed the current user’s file system quoata (see https://debian-handbook.info/browse/stable/sect.quotas.html ) when trashing large files from outside current users home, causing unexpected and inconsistent results using the „Del” key in antiX 23 zzzFM. Instead the trashed files need to stay in the very region of e.g. the /home mount point or other filesystem areas where they originally had lived to avoid this.
As a quick and dirty hotfix there could be added a dialog like HAL 9000: »I’m sorry Dave, I’m afraid I can’t do that« and »Please use Shift+Del instead to actually delete the file or folder«, which comes up when the „Del” key refuses working.
Windows is like a submarine. Open a window and serious problems will start.
Just found another, way more important bug in the new behaviour of the „Del“ key in antiX 23 zzzFM:
The new „Del” key will silently delete files without sending them to trash unexpectedly, when the file lives in a folder outside the mountpoint in which home folder of current user resides. For triggering this it is enough to follow a symbolic link from within e.g. current home folder in zzzFM to a folder outside this home folder’s mount point, e.g. on a different drive or partition, where some data is stored. Then all files and subfolders within this place will get deleted immediately by pressing „Del” key, without moving them to trash. This behaviour is extremely dangerous, because user doesn’t expect files actually to be deleted when using the new „send to trash” function mapped to the „Del” key. (The linked folder and it’s contents, including subfolders, will get displayed in zzzFM as part of user’s home folder, but not properly treated by the new Trash functionality)
Windows is like a submarine. Open a window and serious problems will start.
- You must be logged in to reply to this topic.
