antiX 23 on 32bit single core, impressions and observations

Forum Forums Official Releases antiX-23 “Arditi del Popolo antiX 23 on 32bit single core, impressions and observations

  • This topic has 13 replies, 7 voices, and was last updated Nov 17-11:07 pm by Robin.
Viewing 14 posts - 1 through 14 (of 14 total)
  • Author
    Posts
  • #123629
    Member
    Robin

      Finally I did it. Updating to antiX 23 runit full on my 19 years old 32bit daily driver notebook. When saying updating, I actually mean install from scratch from the ISO. The reason for doing it right now was: The USB stick antiX 22 was runing from in Live mode stopped working, and I found lots of lz4 compression reading errors in dmesg. After reboot the old stick wouldn’t even boot me to the GUI of antiX 22 again. Well, I could have simply created a new antiX 22 USB stick and copy back the linuxfs and initrd files from my backup (I always do a backup, so no big deal when an USB stick actually breaks down) to recover, but why should I, when taking into account I was planning to migrate to antiX 23 next months anyway. So I decided to do the move immediately instead of recovering antiX 22 from the backup first.

      Again, this new antiX 23 version works fast and fluid on this very notebook, just as the versions 17.4.1, 19 and 22 before. (In 21 I’ve had issues with the noveau driver still not working properly, while the same time nvidia had stopped providing their proprietary drivers and refused to hand over their proprietary blob for their older GPUs to xorg the same time, bricking the user’s hardware this way.) The heavily improved free nouveau driver in recent kernels fixed this issue.

      As I always do, I use it “Live”, meanwhile without persistence, which tends to wear out the USB storage devices unnecessarily, moreover USB 2.0 is a bottleneck if you run home and root persistence both. Instead I just replace some folders in the home directory by symbolic links to folders on the internal hard drive immediately after basic install. This goes for e.g. mozilla (firefox), thunderbird, claws mail and it’s separate mail account folders, and playonlinux (used for running some Windows programs in need of different specific wine versions). This procedure provides double advantage: On the one hand this way I can access them even with from duplicate (backup) stick, and on the other hand huge amount of data (like the mail accounts, internet stuff, and multiple wine installations, windows program installations) are stored on the internal hard drive rather than on these pretty unreliable USB sticks.
      Moreover I don’t store any working result from whatever program within the home folder, but also on the internal hdd instead. Thus it is pretty easy to make frequent manual backups only containing the most recent working results, not any OS stuff or configuration data. The latter is saved immediately after initial setup was completed in a personal ISO created from the USB stick (or a duplicate USB stick, if at hand).
      Whatever happens, I’ll be back at work a couple of minutes later, without any significant loss. Even on completely different hardware, if necessary. Try this on any other OS (without moving everything to cloud)

      I created the live USB-stick using the antiX tool from control center on the 64bit desktop PC, setting GPT and the pmbr_boot marker in the extra options. (This depends on whether your BIOS accepts the USB device this way for booting or not, you can use perfectly fine the default MBR setting as well)

      Hint for unexperienced users: Never forget to check the downloaded ISO against it’s checksum file provided by anticapitalista. Will save you potentionally from trouble:

      $ shasum -c antiX-23-runit_386-full.iso.sha256
      OK

      It’s output MUST read “OK”, otherwise the ISO was damaged on transport.

      
      ===============================================================================
      Starte live-usb-maker 2.41.19-2302
      ===============================================================================
      Live Mediengerät /dev/sdc gefunden
      Gerät /dev/sdd (58,6G Generic Flash Disk) wird als Ziel verwendet
      Datei /media/sda4/Arbeitsordner/Downloads/antiX 23/antiX-23-runit_386-full.iso wird als Quelle verwendet
      Distro: antiX-23-runit_386-full Arditi del Popolo 26 August 2023
      Grub Konfiguration 2.0 gefunden
                            gesamt   benutzt  unbelegt
       Gesamtes Laufwerk  58.6 GiB 58.6 GiB     1 MiB
          Hauptpartition  58.5 GiB 1.54 GiB  57.0 GiB
          UEFI Partition    50 MiB   32 MiB    18 MiB
      Bereit live-usb auf Gerät sdd
      ... mit Kopiere Datei /media/sda4/Arbeitsordner/Downloads/antiX 23/antiX-23-runit_386-full.iso zu erstellen
      live-usb-maker 2.41.19-2302: partition-clear >> partition-clear
       > dd status=none if=/dev/zero of=/dev/sdd bs=512 count=34
       > dd status=none if=/dev/zero of=/dev/sdd bs=512 count=34 seek=64
       > dd status=none conv=notrunc if=/dev/zero of=/dev/sdd bs=512 count=34 seek=122879966
       > partprobe /dev/sdd
      live-usb-maker 2.41.19-2302: partition-make >> partition-make
      gpt Partitionierung wird verwendet
       > parted --script --align optimal /dev/sdd unit MiB mklabel gpt
       > dd status=none if=/dev/zero of=/dev/sdd seek=1024 bs=1K count=128
       > parted --script --align optimal /dev/sdd unit MiB mkpart primary 1 59949
       > parted --script --align optimal /dev/sdd unit MiB set 1 legacy_boot on
       > dd status=none if=/dev/zero of=/dev/sdd seek=61387776 bs=1K count=128
       > parted --script --align optimal /dev/sdd unit MiB mkpart primary 59949 59998
       > parted --script --align optimal /dev/sdd unit MiB set 2 esp on
       > parted --script --align optimal /dev/sdd unit MiB disk_set pmbr_boot on
       > partprobe /dev/sdd
       > wait_for_file /dev/sdd1
      live-usb-maker 2.41.19-2302: makefs-bios >> makefs-bios
       > mkfs.ext4 -O ^64bit -m0 -i16384 -J size=32 /dev/sdd1
      mke2fs 1.47.0 (5-Feb-2023)
      64-bit filesystem support is not enabled.  The larger fields afforded by this feature enable full-strength checksumming.  Pass -O 64bit to rectify.
      Creating filesystem with 15346688 4k blocks and 3842048 inodes
      Filesystem UUID: 64df0b8e-5661-4543-8189-415168934444
      Superblock backups stored on blocks: 
      	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
      	4096000, 7962624, 11239424
      Allocating group tables:   0/469       done                            
      Creating journal (8192 blocks): done
      Writing superblocks and filesystem accounting information:        done
       > tune2fs -L antiX-Live-usb /dev/sdd1
      tune2fs 1.47.0 (5-Feb-2023)
       > wait_for_file /dev/sdd2
      live-usb-maker 2.41.19-2302: makefs-uefi >> makefs-uefi
       > mkfs.vfat -F 32 -n ANTIX-UEFI /dev/sdd2
      mkfs.fat 4.2 (2021-01-31)
       > partprobe /dev/sdd
       > wait_for_file /dev/sdd1
       > mkdir -p ./main
       > mount -t ext4 /dev/sdd1 ./main
       > wait_for_file /dev/sdd2
       > mkdir -p ./uefi
       > mount -t vfat /dev/sdd2 ./uefi
      Dateisystem    Typ  Größe Benutzt Verf. Verw% Eingehängt auf
      /dev/sdd1      ext4   58G     24K   58G    1% main
      /dev/sdd2      vfat   49M     512   49M    1% uefi
      live-usb-maker 2.41.19-2302: copy-uefi >> copy-uefi
      Kopiere von iso auf Partition uefi
      Dateien [Ee][Ff][Ii] version
       > cp --no-dereference --preserve=mode,links --recursive ./iso/EFI ./uefi/.
       > cp --no-dereference --preserve=mode,links --recursive ./iso/version ./uefi/.
      Dell uefi memtest Bug beheben
       > cp ./uefi/EFI/BOOT/grubx64.efi ./uefi/EFI/BOOT/fallback.efi
      live-usb-maker 2.41.19-2302: copy-main >> copy-main
       > rm -rf ./main/boot.orig
      Kopiere von iso auf Partition main
      copy /antiX/vmlinuz
       > cpio -pdm --quiet ./main/
       > e4defrag -v ./antiX/vmlinuz
      e4defrag 1.47.0 (5-Feb-2023)
      ext4 defragmentation for ./antiX/vmlinuz
      [1/1][79;0H[K[1/1]./antiX/vmlinuz:	  0%[79;0H[K[1/1]./antiX/vmlinuz:	100%  extents: 2 -> 1	[ OK ]
      copy /antiX/initrd.gz
       > cpio -pdm --quiet ./main/
       > e4defrag -v ./antiX/initrd.gz
      e4defrag 1.47.0 (5-Feb-2023)
      ext4 defragmentation for ./antiX/initrd.gz
      [1/1][79;0H[K[1/1]./antiX/initrd.gz:	  0%[79;0H[K[1/1]./antiX/initrd.gz:	100%  extents: 2 -> 1	[ OK ]
       Success:			[1/1]
      copy remaining files ...
       > cpio -pdm --quiet ./main/
       > write_file ./main/made-by-live-usb-maker   created: Fr 10. Nov 01:44:01 CET 2023
        program: live-usb-maker
        version: 2.41.19-2302 (Sat, 25 Feb 2023 12:45:10 -0500)
       > dd status=none if=/dev/urandom of=./main/antiX/random-seed bs=512 count=1
       > chmod 600 ./main/antiX/random-seed
       > rm -rf ./main/.disk
      live-usb-maker 2.41.19-2302: check-usb-md5 >> check-usb-md5
      Überprüfung von md5 für initrd.gz
       > md5sum -c initrd.gz.md5
      initrd.gz: OK
      Überprüfung von md5 für linuxfs
       > md5sum -c linuxfs.md5
      linuxfs: OK
      Überprüfung von md5 für vmlinuz1
       > md5sum -c vmlinuz1.md5
      md5sum: vmlinuz1.md5: keine korrekt formatierte Prüfsummenzeile gefunden
      Überprüfung von md5 für vmlinuz
       > md5sum -c vmlinuz.md5
      vmlinuz: OK
      live-usb-maker 2.41.19-2302: uuids >> uuids
      Benutze antiX/MX Grub Config 2.0
       > mkdir -p ./uefi/boot/grub
       > cp ./main/boot/grub/config/efi-grub.cfg ./uefi/boot/grub/grub.cfg
       > touch ./main/boot/grub/config/did-efi-grub
       > sed -i /^\s*#/! s/%UUID%/64df0b8e-5661-4543-8189-415168934444/ ./uefi/boot/grub/grub.cfg
       > rm -f ./main/boot/grub/config/*.id
       > touch ./main/boot/grub/config/9ea9bf2948372b03b3380ba221d2e05d.id
       > sed -i /^\s*#/! s|%ID_FILE%|/boot/grub/config/9ea9bf2948372b03b3380ba221d2e05d.id| ./uefi/boot/grub/grub.cfg
      live-usb-maker 2.41.19-2302: install >> Installieren
      extlinux version 6.04
       > dd status=none bs=440 conv=notrunc count=1 if=/usr/lib/syslinux/mbr/gptmbr.bin of=/dev/sdd
       > rm -f ./main/boot/syslinux/chain.c32
       > rm -f ./main/boot/syslinux/gfxboot.c32
       > rm -f ./main/boot/syslinux/ldlinux.c32
       > rm -f ./main/boot/syslinux/libcom32.c32
       > rm -f ./main/boot/syslinux/libmenu.c32
       > rm -f ./main/boot/syslinux/libutil.c32
       > rm -f ./main/boot/syslinux/menu.c32
       > rm -f ./main/boot/syslinux/syslinux.bin
       > rm -f ./main/boot/syslinux/version
       > cp /usr/lib/syslinux/modules/bios/chain.c32 ./main/boot/syslinux/
       > cp /usr/lib/syslinux/modules/bios/gfxboot.c32 ./main/boot/syslinux/
       > cp /usr/lib/syslinux/modules/bios/vesamenu.c32 ./main/boot/syslinux/
       > cp /usr/lib/syslinux/modules/bios/ldlinux.c32 ./main/boot/syslinux/
       > cp /usr/lib/syslinux/modules/bios/libcom32.c32 ./main/boot/syslinux/
       > cp /usr/lib/syslinux/modules/bios/libmenu.c32 ./main/boot/syslinux/
       > cp /usr/lib/syslinux/modules/bios/libutil.c32 ./main/boot/syslinux/
       > cp /usr/lib/syslinux/modules/bios/linux.c32 ./main/boot/syslinux/
       > cp /usr/lib/syslinux/modules/bios/menu.c32 ./main/boot/syslinux/
       > write_file ./main/boot/syslinux/version 6.04
       > extlinux -i ./main/boot/syslinux
      /run/live-usb-maker/main/boot/syslinux is device /dev/sdd1
      Dateisystem    Typ  Größe Benutzt Verf. Verw% Eingehängt auf
      /dev/sdd1      ext4   58G    1,5G   57G    3% main
      /dev/sdd2      vfat   49M     13M   36M   26% uefi
      >> Abgeschlossen
      live-usb-maker took 9 minutes and 28 seconds.

      On first boot, the system chews a bit on switching the graphics modes properly, displaying wired colorful characters all over the screen, and then blacking the screen completely for a couple of seconds, then flickering a bit, before finally coming up with the expected antiX GUI. I’ll come back to this point later. It seems to be kernel related, and it vanished after I replaced the original kernel during setup process. Same goes for the shutdown: With the original kernel from the ISO I get a black screen only during the full shutdown sequence, for about half a minute at least. Unexperienced users might have the impression the system hangs, actually only the screen is turned black while the shutdown process works fine. (Bad luck, if it halts on error in the end, not powering off or reboting, presenting a message asking user to press a key… he wouldn’t even see this.)

      Next step in my default procedure for setting up the antiX Live USB device for my personal use: A full system upgrade.

      
      $ sudo apt-get update
      $ sudo apt-get upgrade

      Then a “Live Remaster” from antiX Control Center, section Live. Type: Personal. Save home: yes.
      Once completed, Reboot.

      In case you have small amount of RAM, like this notebook with 2GB RAM only, you’ll notice the update process wasn’t completed due to lack of free space in RAM possibly (apt had presented an error then) In this case the following commands will fix it once you’ve freed up your RAM by remastering and rebooting.

      
      sudo apt-get update
      sudo apt-get install --fix-broken
      

      possibly you also need

      
      sudo dpkg --configure -a

      Then complete the system upgrade:

      
      sudo apt-get update
      sudo apt-get upgrade

      If nothing was left to update, check whether you need to remaster again already, but if still enough space in RAM left, start installing the recent kernel (otherwise do so after remaster and reboot)

      
      apt-cache search linux-image | grep antix
      apt-cache search linux-headers | grep antix
      sudo apt-get install linux-headers-5.10.197-antix.1-686-smp-pae linux-image-5.10.197-antix.1-686-smp-pae

      Again do a personal Live-remaster, same settings as before. You don’t need to keep all the interim remaster files, it’s ok to let them get deleted (but you can keep them if you feel not completely sure about what you are doing, and in case you have plenty of space, which would allow you to return to any state in the process and start over from this point in case you made an error.)

      Reboot and go to antiX control center again, section “Live”, and start the “Live Kernel Updater”.
      Select the current system, select the freshly installed kernel and let it work. After it has completed, again reboot.

      Now you should be on the new, most recent kernel already.

      Then install all the additional software you need for your work.
      This can be tons of stuff, some douzends of program packages. I’ve created a list file long ago, tailored for my needs, so it’s just copy and paste in chunks to console. Observe the amount of free RAM while installing, and before you run out of space do a personal Live remaster again, then reboot. Proceed this way until your list of programs you need is completed.
      Some programs need still to get set up. If you want your defaults to be present at each startup, and want these defaults to be included in your USB device (without using the persistence options) just configure the programs as you like them best, and let the home folder include in your personal remaster.

      This setup and configuring the programs according to your preferences and needs is probably the most time consuming part of setting up the system. But luckily you have to do this once only. For some programs it is enough to copy and paste the config files from your old home directory (or from a backup of your old system) to the recent home directory. This can save lots of time.

      I have included e.g. samba server for sharing folders between desktop and notebook, and connectshares for accessing them easily. These programs are fine with copying their config files in place and add the user as samba user.

      Since I run more than a single antiX live system in my network usually, I change the hostname of all the Live machines, so they don’t read antix1 altogether:

      edit the file /etc/hosts using e.g leafpad or geany, add the line (root permissions needed)
      127.0.0.1 myfavouritename
      Save the file. Don’t remove the line reading 127.0.0.1 antix1 in the same step.
      edit the file /etc/hostname using e.g. leafpad or geany, again root permissions needed. Replace the line
      antix1
      by the line
      myfavouritename
      Save the file.
      Again open /etc/hosts for editing the same way as in the beginning, now you can safely remove the line
      127.0.0.1 antix1
      and save the file.
      Open a terminal window and enter:

      hostname -F /etc/hostname
      xauth list

      This will present you a line starting with antix1/unix:0 ……
      copy the tail of the line behind unix:0 completely.
      Then type the following line, paste the copied string to the end of the line in the position of the dots:

      
      xauth add "$hostname"/unix:0 ....

      now xauth list should present you two lines, one with the former antix1 hostname, and another with your new hostname. Check that it reads precisely like the original antix1 line, and the new name in it exactly matches what you have set in the /etc/hostname and /etc/hosts files.
      Only then you can safely remove the old xauth token finally:

      
      xauth remove antix1/unix:0

      This procedure will exclude yourself from your system in case you fail (a simple misspelling or case error is enough already!) But you are on a Live system, so no problem: Just start over by rebooting, and repeat the hostname change.

      If you succeeded, all programs should come up again when starting from the antiX application menu. You’ll notice the changed hostname in a new opened terminal window. Now you should be able to ping the antiX system from another one by using it’s hostname, since it’s unique now.

      And then I always set up another user account instead of demo.
      Go to antiX Control Center, section Maintenance. Klick the entry „Manage Users and Groups”.
      Just add a new user on the very first tab.
      Then change the password of the existing demo and root accounts, also on the very first tab.

      Never neglect password security. You should have a strategy to memorate complex passwords comprising numbers, small and big characters, special characters in arbitrary order.
      You can let generate your passwords e.g. by the tool pwgen. (sudo apt-get install pwgen)

      Now, logoff and logon once to the GUI. You can log into your new account instead of demo already.
      Again open antiX control center, this time section “Session”. Klick “Login Management”. Select your new user for automatic login. You may also set the background image for login screen the same one as you’ve set for the desktop. Save and exit.

      After these changes (hostname, user account, login) you’ll have again to use the live remaster to make them permanent. Make sure you have preset everything on your system as you want to have it for your work, before starting the Live remaster a last time. I prefer having the time and date in zzzFM file manager displayed in dd.mm.YYYY instead of YYYY-mm-ss. I set the columns always to details, and activate mostly all columns. zzzFM allows you to set up it’s design very flexible to meet your needs.

      Since I always install my aCSTV, which is able to record tv program to .ts files, I always bind this file extension in zzzFM to MPV, which is able to play these files without any conversion.

      Once you have prepared your Live USB stick this way, you can clone it 1:1 using e.g. dd (but it must not be booted for this) to have a backup stick, or simply use Live USB maker from antiX control center, it has an option to make a clone from the live system you are currently running (then you don’t have to boot into another system first like with the dd method). As well you could create an ISO from it.

      My linuxfs file is about 4,5 GB in the end. But it’s size is only limited by the amount of space you have available on your USB device. If it grews to big over the time (due to security updates) you can remove some outdated kernels you don’t need any longer, along with their respective header packages, and remaster the system again. Then it will shrink remarkably again.

      
      System:
        Kernel: 6.1.0-13-686-pae arch: i686 bits: 32 compiler: gcc v: 12.2.0 parameters: lang=de_DE
          quiet splasht disable=lxF
        Desktop: IceWM v: 3.4.4 dm: slimski v: 1.5.0 Distro: antiX-23-runit_386-full Arditi del Popolo
          26 August 2023 base: Debian GNU/Linux 12 (bookworm)
      Machine:
        Type: Other-vm? System: Notebook product: RIM2000 v: N/A serial: <superuser required>
          Chassis: No Enclosure type: 1 serial: <superuser required>
        Mobo: Notebook model: RIM2000 serial: <superuser required> BIOS: Phoenix v: RIM00F0A
          date: 05/27/2005
      Battery:
        ID-1: BAT0 charge: 60.7 Wh (100.0%) condition: 60.7/65.1 Wh (93.2%) volts: 16.6 min: 14.8
          model: ARIMA LI4403A type: Unknown serial: <filter> status: full
      Memory:
        RAM: total: 1.96 GiB used: 408 MiB (20.3%)
        RAM Report: permissions: Unable to run dmidecode. Root privileges required.
      PCI Slots:
        Permissions: Unable to run dmidecode. Root privileges required.
      CPU:
        Info: model: Intel Pentium M bits: 32 arch: M Dothan built: 2003-05 process: Intel 90nm family: 6
          model-id: 0xD (13) stepping: 8 microcode: 0x20
        Topology: cpus: 1x cores: 1 smt: <unsupported> cache: 2 MiB note: check
        Speed (MHz): 800 min/max: 800/1733 scaling: driver: acpi-cpufreq governor: schedutil core:
          1: 800 bogomips: 3457
        Flags: acpi apic bts clflush cmov cpuid cx8 de dts est fpu fxsr mca mce mmx msr mtrr nx pae
          pbe pge pse pti sep ss sse sse2 tm tm2 tsc vme
        Vulnerabilities:
        Type: gather_data_sampling status: Not affected
        Type: itlb_multihit status: KVM: VMX unsupported
        Type: l1tf mitigation: PTE Inversion
        Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
        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 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: NVIDIA NV43M [GeForce Go 6600] vendor: Rioworks driver: nouveau v: kernel non-free:
          series: 304.xx status: legacy (EOL) last: release: 304.137 kernel: 4.13 xorg: 1.19 arch: Curie
          process: 90-130nm built: 2003-13 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 ports: active: LVDS-1
          empty: TV-1,VGA-1 bus-ID: 01:00.0 chip-ID: 10de:0148 class-ID: 0300
        Display: server: X.Org v: 1.21.1.7 driver: X: loaded: nouveau unloaded: fbdev,modesetting,vesa
          alternate: nv dri: nouveau gpu: nouveau display-ID: :0.0 screens: 1
        Screen-1: 0 s-res: 1440x900 s-dpi: 96 s-size: 380x238mm (14.96x9.37") s-diag: 448mm (17.65")
        Monitor-1: LVDS-1 model: Seiko Epson 0x3847 built: 2003 res: 1440x900 hz: 60 dpi: 100
          gamma: 1.2 chroma: red: x: 0.580 y: 0.341 green: x: 0.310 y: 0.549 blue: x: 0.153 y: 0.153 white:
          x: 0.314 y: 0.329 size: 367x230mm (14.45x9.06") diag: 433mm (17.1") ratio: 16:10
          modes: 1440x900, 1152x864, 1024x768, 800x600, 640x480, 720x400, 640x400, 640x350
        API: OpenGL v: 2.1 Mesa 22.3.6 renderer: NV43 direct-render: Yes
      Audio:
        Device-1: Intel 82801FB/FBM/FR/FW/FRW High Definition Audio vendor: Rioworks
          driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:2668 class-ID: 0403
        Device-2: Philips s SAA7131/SAA7133/SAA7135 Video Broadcast Decoder vendor: Animation
          driver: saa7134 v: 0, 2, 17 bus-ID: 06:03.0 chip-ID: 1131:7133 class-ID: 0480
        Sound API: ALSA v: k6.1.0-13-686-pae running: yes
        Sound Server-1: JACK v: 1.9.21 running: no
        Sound Server-2: PipeWire v: 0.3.65 running: yes
      Network:
        Device-1: Marvell 88E8036 PCI-E Fast Ethernet vendor: Rioworks driver: sky2 v: 1.30 pcie: gen: 1
          speed: 2.5 GT/s lanes: 1 port: 2000 bus-ID: 02:00.0 chip-ID: 11ab:4351 class-ID: 0200
        IF: eth0 state: down mac: <filter>
        Device-2: Intel PRO/Wireless 2200BG [Calexico2] Network driver: ipw2200 v: 1.2.2kmprq
          modules: wl bus-ID: 06:08.0 chip-ID: 8086:4220 class-ID: 0280
        IF: eth1 state: up 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: 151.75 GiB used: 84.08 GiB (55.4%)
        SMART Message: Unable to run smartctl. Root privileges required.
        ID-1: /dev/sda maj-min: 8:0 vendor: Seagate model: ST9100823A size: 93.16 GiB block-size:
          physical: 512 B logical: 512 B speed: <unknown> type: N/A serial: <filter> rev: 3.02 scheme: MBR
        ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: Generic model: Flash Disk size: 58.59 GiB
          block-size: physical: 512 B logical: 512 B type: SSD serial: <filter> rev: 8.01 scheme: GPT
        SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
        Optical-1: /dev/sr0 vendor: PBDS model: DVD+-RW DS-8W1P rev: BD1B
          dev-links: cdrom,cdrw,dvd,dvdrw
        Features: speed: 24 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r state: running
      Partition:
        ID-1: /live/boot-dev raw-size: 58.54 GiB size: 57.54 GiB (98.29%) used: 8.27 GiB (14.4%) fs: ext4
          dev: /dev/sdb1 maj-min: 8:17 label: antiX-Live-usb uuid: 64df0b8e-5661-4543-8189-415168934444
        ID-2: /media/ANTIX-UEFI raw-size: 49 MiB size: 48.2 MiB (98.43%) used: 12.4 MiB (25.6%)
          fs: vfat dev: /dev/sdb2 maj-min: 8:18 label: ANTIX-UEFI uuid: B9E3-2B0E
        ID-3: /media/_daten3 raw-size: 42.48 GiB size: 41.64 GiB (98.03%) used: 37.91 GiB (91.0%)
          fs: ext3 dev: /dev/sda7 maj-min: 8:7 label: /daten3 uuid: c1bc867a-ec28-436d-831b-e47f334471ce
        ID-4: /media/_daten4 raw-size: 3 GiB size: 2.89 GiB (96.20%) used: 2.58 GiB (89.5%) fs: ext3
          dev: /dev/sda8 maj-min: 8:8 label: /daten4 uuid: 556a43c4-118c-4bb5-baa2-7c997faea6da
        ID-5: /media/_home raw-size: 20 GiB size: 19.52 GiB (97.58%) used: 16.92 GiB (86.7%) fs: ext3
          dev: /dev/sda5 maj-min: 8:5 label: /home uuid: 94021be3-c160-4166-a151-92ad72b26f9a
        ID-6: /media/antiX raw-size: 10 GiB size: 9.74 GiB (97.45%) used: 8.16 GiB (83.8%) fs: ext4
          dev: /dev/sda6 maj-min: 8:6 label: antiX uuid: a6852dda-0c34-4c4f-8efc-5d458cbaaeec
        ID-7: /media/antiX-Frugal raw-size: 8 GiB size: 7.79 GiB (97.43%) used: 4.3 GiB (55.2%)
          fs: ext4 dev: /dev/sda1 maj-min: 8:1 label: antiX-Frugal
          uuid: 19eaea0e-493b-4007-8eff-f14aca40363f
        ID-8: /media/sda10 raw-size: 7.51 GiB size: 7.26 GiB (96.61%) used: 5.93 GiB (81.7%) fs: ext4
          dev: /dev/sda10 maj-min: 8:10 label: N/A uuid: 0eb91a9b-ea52-4f5b-9140-5a06f6f73d1d
      Swap:
        Kernel: swappiness: 10 (default 60) cache-pressure: 50 (default 100)
        ID-1: swap-1 type: partition size: 2.16 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda9
          maj-min: 8:9 label: N/A uuid: 2d151628-e6f1-4e23-a8a6-7820d17b8a14
      Unmounted:
        ID-1: /dev/sda2 maj-min: 8:2 size: 1 KiB fs: <superuser required> label: N/A uuid: N/A
      USB:
        Hub-1: 1-0:1 info: Full speed or root hub ports: 6 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002
          class-ID: 0900
        Device-1: 1-3:2 info: Alcor Micro Flash Drive type: Mass Storage driver: usb-storage
          interfaces: 1 rev: 2.1 speed: 480 Mb/s power: 200mA chip-ID: 058f:6387 class-ID: 0806
          serial: <filter>
        Hub-2: 2-0:1 info: Full speed or root hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
          class-ID: 0900
        Hub-3: 3-0:1 info: Full speed or root hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
          class-ID: 0900
        Device-1: 3-2:2 info: Pixart Imaging Mouse type: Mouse,Keyboard
          driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 093a:2533
          class-ID: 0300
        Hub-4: 4-0:1 info: Full speed or root hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
          class-ID: 0900
      Sensors:
        System Temperatures: cpu: 65.2 C mobo: 55.0 C
        Fan Speeds (RPM): N/A
      Repos:
        Packages: pm: dpkg pkgs: 2072 libs: 977 tools: apt,apt-get,aptitude,synaptic
        Active apt repos in: /etc/apt/sources.list.d/antix.list
          1: deb [signed-by=/etc/apt/keyrings/antix-archive-keyring.gpg] http: //ftp.halifax.rwth-aachen.de/mxlinux/packages/antix/bookworm bookworm 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/librewolf.list
        No active apt repos in: /etc/apt/sources.list.d/liquorix.list
      Processes:
        CPU top: 5 of 140
        1: cpu: 31.7% command: yad pid: 6184 mem: 28.6 MiB (1.4%)
        2: cpu: 8.4% command: gtkdialog pid: 6145 mem: 27.1 MiB (1.3%)
        3: cpu: 6.3% command: xorg pid: 4926 mem: 66.2 MiB (3.2%)
        4: cpu: 2.9% command: icewm pid: 5025 mem: 26.5 MiB (1.3%)
        5: cpu: 2.5% command: zzzfm pid: 5037 mem: 34.5 MiB (1.7%)
        Memory top: 5 of 140
        1: mem: 66.2 MiB (3.2%) command: xorg pid: 4926 cpu: 6.3%
        2: mem: 34.5 MiB (1.7%) command: zzzfm pid: 5037 cpu: 2.5%
        3: mem: 28.6 MiB (1.4%) command: yad pid: 6184 cpu: 31.7%
        4: mem: 27.1 MiB (1.3%) command: gtkdialog pid: 6145 cpu: 8.4%
        5: mem: 26.5 MiB (1.3%) command: icewm pid: 5025 cpu: 2.9%
      Info:
        Processes: 140 Uptime: 5m wakeups: 2 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.25

      Some observations:

      1.) Audio.
      Sound is present out of the box. Pipewire starts up properly at first glance. Volume icon is present in command line.

      But: It’s taskbar slider doesn’t change the volume at all. It does simply nothing. Regardles which position it is drawn to, the sound is constant. Also muting/unmuting provided by this icon is without any function.

      Clicking the Mixer from the volume icon brings up the new shiny mixer provided by pipewire. But it comes with a single audio out device available: digital s/pdif. This output is not connected here, since it is the digital optical audio out this notebook has. I have no device I could connect to it, I’d need an amplifier with optical input to make use of it. Unfortunately all the analog output (and also the input jacks) are not acceseable in the new mixer. They are marked as “not available” altogether in the listing from the settings tab.

      The sound “as is” is very very low, you can hardly hear anything, and (by now) no way to adjust it.

      Will have to do some further testing to find out how to fix this issue. Hopefully I don’t need to deactivate pipewire on this device also, like I was forced to do already on the 64bit desktop PC. Will report soon the results from this 32bit notebook concerning this issue. I’ll open a separate thread for this to discuss.

      2.) Black screen during last part of startup and during whole shutdown sequence with default Kernel. This goes for the linux-image-5.10.188-antix.1-486-smp as present in the antiX 23 ISO as well as for the linux-image-5.10.197-antix.1-686-smp-pae kernel installed from the repos. Since there is no 6.1 antiX kernel for 686 available, I installed the most recent debian linux-image-6.1.0-13-686-pae on this notebook which solved the issue. Now instead of weird coloured characters during startup followed by a black screen, the screen is switched now to a higher resolution properly, displaying the end of startup sequence. And also the full shutdown sequence is not black any longer, but also displayed in the very high resolution like the end of the startup already.

      All other parts of the system do work fine, fast and fully functioning, also all the legion of programs installed.
      Really really great work @anticapitalista. Many thanks for that antiX 23! Unbelievable it brings most recent software and kernels not only to the 64bit desktop PC but also even to this old as the rocks 32-bit-single-core notebook and makes it run like a young horse. (Just like all the antiX versions before already did…) Think, it’s 19 years old, mostly 20 (it has got a bios update early in it’s life, so the bios date doesn’t show the original manufacturing date which was in early 2004 or late 2003 actually)

      I’m writing these lines now from the freshly set up antiX 23 full runit 32bit on this device, using firefox. It’s pure pleasure to see it run.

      Many thanks, @anticapitalista and dev team!

      Windows is like a submarine. Open a window and serious problems will start.

      #123634
      Member
      Robin

        Some news concerning the audio issue mentioned above:

        Arbitrarily after logon the volume icon behaves inconsistent. Sometimes on login it is there, but has no influence on the actual volume when moving the slider as described above already. Also the new mixer behaves arbitrarily differently on each login: Sometimes it shows the single digital audio device s/pdif as described above, but sometimes it simply shows a completely blank screen (see screenshot attached) waiting for connection forever.
        And sometimes the volume icon isn’t displayed at all, as reported by some others in the thread about volumeicon solution for antiX 23. So I tried to restart it manually.

        No luck, trying to start volumeicon manually results in error:

        $ volumeicon
        volumeicon: alsa_backend.c:86: asound_get_volume: Zusicherung »m_elem != NULL« nicht erfüllt.
        Abgebrochen

        But pipewire is running actually when looking at htop or system info:

        Audio:
          Device-1: Intel 82801FB/FBM/FR/FW/FRW High Definition Audio vendor: Rioworks
            driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:2668 class-ID: 0403
          Device-2: Philips s SAA7131/SAA7133/SAA7135 Video Broadcast Decoder vendor: Animation
            driver: saa7134 v: 0, 2, 17 bus-ID: 06:03.0 chip-ID: 1131:7133 class-ID: 0480
          Sound API: ALSA v: k5.10.188-antix.1-486-smp running: yes
          Sound Server-1: PipeWire v: 0.3.65 running: yes

        I’m a bit confused now how to handle this properly. These devices should be present in the mixer, they are reported properly by alsa:

        $ aplay -L
        null
            Discard all samples (playback) or generate zero samples (capture)
        bluealsa
            Bluetooth Audio Hub
        pipewire
            PipeWire Sound Server
        default
        plugequal
        preamp
        duplex
        hw:CARD=Intel,DEV=0
            HDA Intel, ALC880 Analog
            Direct hardware device without any conversions
        hw:CARD=Intel,DEV=1
            HDA Intel, ALC880 Digital
            Direct hardware device without any conversions
        plughw:CARD=Intel,DEV=0
            HDA Intel, ALC880 Analog
            Hardware device with all software conversions
        plughw:CARD=Intel,DEV=1
            HDA Intel, ALC880 Digital
            Hardware device with all software conversions
        sysdefault:CARD=Intel
            HDA Intel, ALC880 Analog
            Default Audio Device
        front:CARD=Intel,DEV=0
            HDA Intel, ALC880 Analog
            Front output / input
        surround21:CARD=Intel,DEV=0
            HDA Intel, ALC880 Analog
            2.1 Surround output to Front and Subwoofer speakers
        surround40:CARD=Intel,DEV=0
            HDA Intel, ALC880 Analog
            4.0 Surround output to Front and Rear speakers
        surround41:CARD=Intel,DEV=0
            HDA Intel, ALC880 Analog
            4.1 Surround output to Front, Rear and Subwoofer speakers
        surround50:CARD=Intel,DEV=0
            HDA Intel, ALC880 Analog
            5.0 Surround output to Front, Center and Rear speakers
        surround51:CARD=Intel,DEV=0
            HDA Intel, ALC880 Analog
            5.1 Surround output to Front, Center, Rear and Subwoofer speakers
        surround71:CARD=Intel,DEV=0
            HDA Intel, ALC880 Analog
            7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
        iec958:CARD=Intel,DEV=0
            HDA Intel, ALC880 Digital
            IEC958 (S/PDIF) Digital Audio Output
        dmix:CARD=Intel,DEV=0
            HDA Intel, ALC880 Analog
            Direct sample mixing device
        dmix:CARD=Intel,DEV=1
            HDA Intel, ALC880 Digital
            Direct sample mixing device

        The new pipewire mixer doesn’t seem to see them.

        Tried to deactivate and reactivate it using the menu entry (or from within antiX control center):

        Deactivating pipewire worked immediately. Volume icon in taskbar is removed and reapears after a short time again. Now the slider works as expected, chancing actually the volume. Mixer brings up now old-school alsamixer instead of the new design. It’s sliders do work and take effect on the actual sound.

        Then reactivating pipewire again from antiX control center fails obviously: Volume icon doesn’t come back at all.

        Trying to manualy start pavucontrol fails. Again it waits forever for a connection to the server.

        Checking whether pipewire is running at all: htop now has no process named pipewire. Also $ pidof -q pipewire doesn’t return anything. So I guess it’s actually not running.

        But still pipewire is reported to be running by system info from antiX cc the same time:

         Audio:
           Device-1: Intel 82801FB/FBM/FR/FW/FRW High Definition Audio driver: snd_hda_intel
           Device-2: Philips s SAA7131/SAA7133/SAA7135 Video Broadcast Decoder driver: saa7134
           Sound API: ALSA v: k5.10.188-antix.1-486-smp running: yes
           Sound Server-1: PipeWire v: 0.3.65 running: yes

        Is pipewire running now or not?

        Let’s assume the report from cc is wrong, and htop and pidof are right. So let’s try to start it manually, using the command found in the startup script in .desktop-session.

        $ pipewire-start
        $ [W][08387.815020] mod.rt       | [     module-rt.c:  274 pw_rtkit_check_xdg_portal()] Can't find org.freedesktop.portal.Desktop. Is xdg-desktop-portal running?
        [W][08387.815238] mod.rt       | [     module-rt.c: 1035 pipewire__module_init()] found session bus but no portal
        [W][08387.816845] mod.rt       | [     module-rt.c:  290 translate_error()] RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
        [W][08387.817230] mod.rt       | [     module-rt.c:  655 set_nice()] could not set nice-level to -11: Datei oder Verzeichnis nicht gefunden
        [W][08387.817677] mod.rt       | [     module-rt.c:  290 translate_error()] RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
        [W][08387.839013] mod.rt       | [     module-rt.c:  274 pw_rtkit_check_xdg_portal()] Can't find org.freedesktop.portal.Desktop. Is xdg-desktop-portal running?
        [W][08387.839234] mod.rt       | [     module-rt.c: 1035 pipewire__module_init()] found session bus but no portal
        [W][08387.840724] mod.rt       | [     module-rt.c:  290 translate_error()] RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
        [W][08387.841109] mod.rt       | [     module-rt.c:  655 set_nice()] could not set nice-level to -11: Datei oder Verzeichnis nicht gefunden
        [W][08387.844402] mod.rt       | [     module-rt.c:  290 translate_error()] RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
        M 15:44:14.205883             mod.rt ../src/modules/module-rt.c:274:pw_rtkit_check_xdg_portal: Can't find org.freedesktop.portal.Desktop. Is xdg-desktop-portal running?
        M 15:44:14.206146             mod.rt ../src/modules/module-rt.c:1035:pipewire__module_init: found session bus but no portal
        M 15:44:14.207698             mod.rt ../src/modules/module-rt.c:290:translate_error: RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
        M 15:44:14.208059             mod.rt ../src/modules/module-rt.c:655:set_nice: could not set nice-level to -11: Datei oder Verzeichnis nicht gefunden
        M 15:44:14.208507             mod.rt ../src/modules/module-rt.c:290:translate_error: RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
        [W][08387.853482] mod.rt       | [     module-rt.c:  290 translate_error()] RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
        M 15:44:14.213017             mod.rt ../src/modules/module-rt.c:290:translate_error: RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
        [W][08387.882752] mod.rt       | [     module-rt.c:  290 translate_error()] RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
        M 15:44:14.244045    m-lua-scripting ../modules/module-lua-scripting/api/config.c:80:load_components: Failed to open module /usr/lib/i386-linux-gnu/wireplumber-0.4/libwireplumber-module-logind: /usr/lib/i386-linux-gnu/wireplumber-0.4/libwireplumber-module-logind.so: Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden
        M 15:44:14.284189          wp-device ../lib/wp/device.c:619:wp_spa_device_new_from_spa_factory: SPA handle 'api.libcamera.enum.manager' could not be loaded; is it installed?
        M 15:44:14.284402   script/libcamera libcamera.lua:168:chunk: PipeWire's libcamera SPA missing or broken. libcamera not supported.
        W 15:44:14.328378         spa.bluez5 ../spa/plugins/bluez5/bluez5-dbus.c:4415:get_managed_objects_reply: GetManagedObjects() failed: org.freedesktop.DBus.Error.NameHasNoOwner
        [E][08388.356021] spa.v4l2     | [    v4l2-utils.c:  653 spa_v4l2_enum_format()] '/dev/video0' VIDIOC_ENUM_FRAMESIZES: Unpassender IOCTL (I/O-Control) für das Gerät
        [E][08388.359880] spa.v4l2     | [    v4l2-utils.c:  653 spa_v4l2_enum_format()] '/dev/video0' VIDIOC_ENUM_FRAMESIZES: Unpassender IOCTL (I/O-Control) für das Gerät
        M 15:44:14.733523    wp-pw-obj-mixin ../lib/wp/private/pipewire-object-mixin.c:303:wp_pw_object_mixin_set_param: <WpNode:0x8a0d78> ignoring set_param on already destroyed objects
        M 15:44:14.736522    wp-pw-obj-mixin ../lib/wp/private/pipewire-object-mixin.c:303:wp_pw_object_mixin_set_param: <WpNode:0x8a0ed8> ignoring set_param on already destroyed objects
        M 15:44:14.779639    m-lua-scripting ../modules/module-lua-scripting/api/api.c:376:object_activate_done: <WpSiAudioAdapter:0xac60c0> Object activation aborted: proxy destroyed
        M 15:44:14.779840 script/create-item create-item.lua:80:chunk: <WpSiAudioAdapter:0xac60c0> failed to activate item: Object activation aborted: proxy destroyed

        OK, ok! I see, something has gone really really wrong obviously. But what does all this mean?

        For now I’ll have to deactivate pipewire, hopefully this mess will be fixed in future updates. My personal impression: By now it’s obviously not reliable for everyday usage. Here on 32bit even worse than on the 64bit desktop. Sometime it comes up, sometimes it even works, and sometimes not. Not really something what I’d expect to be used in productive everyday usage. From my personal point of view pipewire needs to ripen a bit still, shouldn’t have been included in antiX before some more testing and fixing the issues was done.

        Windows is like a submarine. Open a window and serious problems will start.

        #123639
        Member
        Robin

          Another issue I on antiX 23 on this 32bit Notebook which was not present on antiX 22 (fix below):

          Playing videos using MPV creates purple screen, ghost artifacts from the video dance on it (see screenshot). This makes all programs relying on MPV, like aCSTV fail as well.

          After some testing and researching I found the recent MPV version itself is the culprit. It defaults now to a new incompatible driver (called „gpu”) which obviously fails, while the manual reads it is supposed to try automatically the next driver from an internal list in this case until it finds a suitable driver. Obviously this automatic driver selection fails for some reason, producing corrupted video output, so calling MPV explicitly with it’s command line option vo=xv fixes the issue and reduces the same time the CPU load when playing the very same (high resolution) video file from 90% to 70%. Will put it in mpv.conf file in my home directory to make this permanent.

          Attachments:

          Windows is like a submarine. Open a window and serious problems will start.

          #123651
          Moderator
          caprea

            Robin, did you update and upgrade your system? Because the problems you describe with pipewire sound like before the fixes of an upgrade come into effect.If pavucontrol is waiting for a connection to the server, pipewire or at least wireplumber is not running.
            pgrep -l wire
            should list pipewire, wireplumber and pipewire-pulse

            #123653
            Member
            Robin

              did you update and upgrade your system?

              For sure I did, Caprea. The system is most recently completely upgraded (and remastered and rebooted after this). Still, some packages (including pipewire) are displayed as set on hold for some reason:

              $sudo apt-get update
              ...
               sudo apt list --upgradable
              Auflistung… Fertig
              antix-installer/bookworm 23.10.17 i386 [aktualisierbar von: 23.08.06]
              cli-installer-antix/bookworm 5.5 all [aktualisierbar von: 5.4]
              gstreamer1.0-pipewire/bookworm 0.3.84-1.0nosystemd1 i386 [aktualisierbar von: 0.3.65-3.0nosystemd1]
              libpipewire-0.3-0/bookworm 0.3.84-1.0nosystemd1 i386 [aktualisierbar von: 0.3.65-3.0nosystemd1]
              libpipewire-0.3-modules/bookworm 0.3.84-1.0nosystemd1 i386 [aktualisierbar von: 0.3.65-3.0nosystemd1]
              libspa-0.2-bluetooth/bookworm 0.3.84-1.0nosystemd1 i386 [aktualisierbar von: 0.3.65-3.0nosystemd1]
              libspa-0.2-modules/bookworm 0.3.84-1.0nosystemd1 i386 [aktualisierbar von: 0.3.65-3.0nosystemd1]
              libwireplumber-0.4-0/bookworm 0.4.15-1.0nosystemd1 i386 [aktualisierbar von: 0.4.13-1.0nosystemd1]
              packageinstaller/bookworm 2023.09.03 i386 [aktualisierbar von: 2023.06.19]
              pipewire-alsa/bookworm 0.3.84-1.0nosystemd1 i386 [aktualisierbar von: 0.3.65-3.0nosystemd1]
              pipewire-bin/bookworm 0.3.84-1.0nosystemd1 i386 [aktualisierbar von: 0.3.65-3.0nosystemd1]
              pipewire-jack/bookworm 0.3.84-1.0nosystemd1 i386 [aktualisierbar von: 0.3.65-3.0nosystemd1]
              pipewire-pulse/bookworm 0.3.84-1.0nosystemd1 i386 [aktualisierbar von: 0.3.65-3.0nosystemd1]
              pipewire/bookworm 0.3.84-1.0nosystemd1 i386 [aktualisierbar von: 0.3.65-3.0nosystemd1]
              wireplumber/bookworm 0.4.15-1.0nosystemd1 i386 [aktualisierbar von: 0.4.13-1.0nosystemd1]
              $ sudo apt-get upgrade
              Paketlisten werden gelesen… Fertig
              Abhängigkeitsbaum wird aufgebaut… Fertig
              Statusinformationen werden eingelesen… Fertig
              Paketaktualisierung (Upgrade) wird berechnet… Fertig
              Die folgenden Pakete sind zurückgehalten worden:
                antix-installer cli-installer-antix gstreamer1.0-pipewire libpipewire-0.3-0 libpipewire-0.3-modules libspa-0.2-bluetooth
                libspa-0.2-modules libwireplumber-0.4-0 packageinstaller pipewire pipewire-alsa pipewire-bin pipewire-jack pipewire-pulse
                wireplumber
              0 aktualisiert, 0 neu installiert, 0 zu entfernen und 15 nicht aktualisiert.

              So all the packages are most recent, except for the ones held back from upgrading in the repo.

              If pavucontrol is waiting for a connection to the server, pipewire is not running.

              Good to know. But if pipewire actually is not running, why the “wrong” mixer is opened from the volume icon on taskbar at all? Shouldn’t in this case come up the fallback alsa mixer rather than trying forever to connect to something nonexistant?

              Because the problems you describe with pipewire sound like before the fixes of an upgrade come into effect.

              In which version these issues have been fixed? Do I possibly run the outdated versions due to the fact that some packages are held back? Could you please check the versions in my listing above and confirm these are the proper ones you know to be functional?

              Windows is like a submarine. Open a window and serious problems will start.

              #123655
              Member
              Robin

                pgrep -l wire
                lists only pipewire, no wireplumber and no pipewire-pulse. (and additionaly some firewire entries which should not count here)

                So wireplumber has not started properly. Possibly this line from the error output from two postings above gives a hint?
                M 15:44:14.244045 m-lua-scripting ../modules/module-lua-scripting/api/config.c:80:load_components: Failed to open module /usr/lib/i386-linux-gnu/wireplumber-0.4/libwireplumber-module-logind: /usr/lib/i386-linux-gnu/wireplumber-0.4/libwireplumber-module-logind.so: Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden

                For me it looks as if some file needed for running wireplumber is missing.

                Windows is like a submarine. Open a window and serious problems will start.

                #123672
                Moderator
                caprea

                  Die folgenden Pakete sind zurückgehalten worden:
                  antix-installer cli-installer-antix gstreamer1.0-pipewire libpipewire-0.3-0 libpipewire-0.3-modules libspa-0.2-bluetooth
                  libspa-0.2-modules libwireplumber-0.4-0 packageinstaller pipewire pipewire-alsa pipewire-bin pipewire-jack pipewire-pulse
                  wireplumber

                  I would guess that’s the culprit

                  if pipewire actually is not running, why the “wrong” mixer is opened from the volume icon

                  This will get fixed in antiX23.1, in time even if you move to pure alsa the pavu-mixer still opens from volumeicon.

                  There have been problems to start pipewire correctly and then timing problems to start volumeicon, you might have missed that.An upgrade is needed to bring in the fixes,which for me until now worked without problems.
                  Why are the packages held back? Is this might due to upgrade instead of dist-upgrade?

                  Btw, your aCSTV is one of the first software I add to a newly installed system.

                  • This reply was modified 7 months, 1 week ago by caprea.
                  #123682
                  Member
                  Robin

                    in time even if you move to pure alsa the pavu-mixer still opens from volumeicon.

                    Not really. If pipewire is deactivated by means of the switch in antiX control center, the volumeicon flickers for a second, and when clicking it then, the alsamixer comes up (as I stated some postings above already), so this switching between the mixers works fine already. Only the fallback, if pipewire is selected but doesn’t run for some reason, fails (obviously it is falsely reported to be running sometimes).

                    Concerning the hold-back packages: I wasn’t aware I should run a dist-upgrade instead of a default upgrade, since I didn’t migrate from antiX 22 to antiX 23, but installed 23 from ISO from scratch. I simply didn’t expect a dist-upgrade was needed, and thought the packages are hold back for a reason, and the most recent ones usable were the ones delivered by default upgrade. But well, since your answer implies I didn’t get the proper version by now and should better run dist-upgrade, I gave it simply a try.

                    Die folgenden NEUEN Pakete werden installiert:
                      efibootmgr efivar grub-efi-amd64-bin libcairo-gobject-perl libcairo-perl libconfig++9v5
                      libextutils-depends-perl libffado2 libglib-object-introspection-perl libglib-perl libgtk3-perl
                      liblua5.4-0
                    Die folgenden Pakete werden aktualisiert (Upgrade):
                      antix-installer cli-installer-antix gstreamer1.0-pipewire libpipewire-0.3-0 libpipewire-0.3-modules
                      libspa-0.2-bluetooth libspa-0.2-modules libwireplumber-0.4-0 packageinstaller pipewire
                      pipewire-alsa pipewire-bin pipewire-jack pipewire-pulse wireplumber
                    15 aktualisiert, 12 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.

                    No packages are listed as upgradable now, actually everything is up to date. And now wireplumber and pipewire-pulse are listed both along with pipewire after remastering and restarting the system once more:

                    $ pgrep -l wire
                    265 firewire
                    266 firewire_ohci
                    6684 pipewire
                    6692 wireplumber
                    6694 pipewire-pulse

                    Still, pipewire doesn’t work as expected on this device. The slider provided by volumeicon has still no effect.

                    Even when Pavucontrol comes up now reliable when clicking the mixer entry from volume icon, it wouldn’t allow to select the proper output devices. Still only s/pdif is available, which is (as said already in one of the postings above) only the digital optical output and input of this notebook; I can’t test this, since I don’t have an amplifier providing this kind of connector. When selecting the configuration tab in pavucontrol all other analog devices are marked as „not available”, even when plain alsa can access them properly after deactivating pipewire.

                    Windows is like a submarine. Open a window and serious problems will start.

                    #123690
                    Member
                    abc-nix

                      Can you install alsa-ucm-conf, remaster and reboot? It may add the necessary alsa config files for your specific audio card. It helped with one of my devices.

                      Also, You could use the Pro Audio profile from the configuration tab. Based on the Pipewire release notes:

                      PipeWire 0.3.22
                      Pro Audio card profile support. You can now select the Pro Audio profile and have raw device access with the maximum number of channels and no mixer controls. This is the usual setup for managing high end Pro Audio cards.

                      I found this little article useful when setting and configuring some things with pipewire, in case you are interested.

                      #123692
                      Member
                      Xunzi_23

                        Robin,Also congratulations on keeping the old laptop running and still as useful as it was designed to be.
                        You highlight the advantages of running live from USB very well and reasons for keeping remastered rather
                        than using the persistence option.

                        With regard to pipewire your experiences echo mine.
                        @abc-nix, You can now select the Pro Audio profile, still only the single channel mixer, in my cases pointing
                        to either HDMI or spdif. Thanks for the linked article, some of my questions are answered there as well as in
                        https://pipewire.pages.freedesktop.org/wireplumber/configuration/alsa.html. All that though is far from the
                        It just works claims propagated by some forum members, akin to saying others are liars and fools although
                        experiencing frustrating problems on multiple devices with same and very different architecture, over 12 years
                        old to 2 years since release.

                        Robin wrote,

                        Still, pipewire doesn’t work as expected on this device. The slider provided by volumeicon has still no effect.

                        Even when Pavucontrol comes up now reliable when clicking the mixer entry from volume icon, it wouldn’t allow to select the proper output devices. Still only s/pdif is available, which is (as said already in one of the postings above) only the digital optical output and input of this notebook; I can’t test this, since I don’t have an amplifier providing this kind of connector. When selecting the configuration tab in pavucontrol all other analog devices are marked as „not available”, even when plain alsa can access them properly after deactivating pipewire.

                        Mirrors my experience of a very recent test after latest version update.

                        #123711
                        Member
                        PPC

                          Strangely enough, I had no problem at all with pipewire running antiX 23 live:
                          – in my netbook (64bits, but most of the time, slower than my 32bits laptop)- it’s so slow that I had to increase the sleep value before starting volumeicon from the startup file, or just launch it manually (I have it installed in the netbook hard drive, no sleep delay is required, sound works great, even on it’s crappy columns)
                          – in my work desktop – it ran great (in live mode, I still have antiX 22 installed)

                          However, antiX 23.1, test version 2, running live on m work desktop- sound fails. It works great if I toggle pipewire off and then right back on.

                          I’m favorable to Pipewire coming pre-installed and even being on by default, but, in fact, that software seems to be very sensitive to small system changes, like I usually say, if I look at it sideways, it stops working… Probably adding the pipewire toggle GUI was my brightest idea ever, related to antiX!

                          EDIT: the reason I have not installed antiX 23 on my 32bits laptop it’s because I’m an early tester, slow adopter- since I use that device a lot, and it has lots of files that I have to backup, I’ll only mess with it if I have to. It stayed with antiX 19.X for a very, very long time…
                          EDIT2 (I have some free minutes, I’m waiting for an upload to finish): even on some 20 years old computer, antiX really is fast enough for daily use. I usually use seamonkey as the main browser (I even used it as e-mail client too once) and OpenOffice 32’s appimage that I uncompressed, as office software (but I always check it with the much slower, on that machine, LibreOffice, before sending any file). I use OpenOffice’s quick starter- and even that very slow machine opens office apps in a couple of seconds (at the expense of a bit of free RAM). Xine Media player lets me view even HD video, on that device…

                          P.

                          • This reply was modified 7 months, 1 week ago by PPC.
                          • This reply was modified 7 months, 1 week ago by PPC.
                          #123828
                          Member
                          blur13

                            Personally, I see absolutely no reason to run pipewire on a 32-bit netbook (or any system for that matter, but thats besides the point). Alsa does the job just fine. Its not like you’re going to stream audio to a bluetooth speaker, or whatever the specific use cases of pipewire are. Just my unsolicited opinion.

                            #123830
                            Forum Admin
                            anticapitalista

                              Personally, I see absolutely no reason to run pipewire on a 32-bit netbook (or any system for that matter, but thats besides the point). Alsa does the job just fine. Its not like you’re going to stream audio to a bluetooth speaker, or whatever the specific use cases of pipewire are. Just my unsolicited opinion.

                              You will be surprised what unrealistic expectations some people have.

                              Philosophers have interpreted the world in many ways; the point is to change it.

                              antiX with runit - leaner and meaner.

                              #123836
                              Member
                              Robin

                                Actually, and I have to repeat myself, I don’t need pipewire at all on this notebook, and I’m perfectly fine with plain alsa, and I don’t expect anything. Having said this, let me append: I’m trying to make it run on this 32 bit hardware to fathom whether it takes unreasonably system load or CPU usage (like pulseaudio does) on this kind of hardware, once it runs at all. If it turns out pipewire consumes all available power for merely managing audio, we have to think about whether it makes sense to have it activated by default on 32 bit versions of antiX: It’s probably not the very best idea to let people run into this kind of issues like the ones I encounter with pipewire, when somebody is starting antiX for a first time. But if it turns out to be true also for 32 bit hardware, what you can read everywhere about it (probably only ever tested on 64 bit), that it doesn’t consume much system load, then it’s actually worth having it activated in the 32 bit antiX versions by default once the issues are sorted out. It’s a simple evaluation between advantage (in terms of easy usage for everybody) and cost (in terms of CPU and system load).

                                Please note: this is not a netbook, but a rich featured and pretty powerful notebook, aged gracefully (maybe more powerful than some way more recent 64 bit devices I’ve seen in the wild). I’ve even run jack successfully on it (still on antiX 22). And yes, it actually has bluetooth on board, but I never have been able to make this work reasonably on Linux (had to start a virtualised Win 2000 Win XP instead in a virtualbox running on antiX in the end). So maybe pipewire can change things now.

                                Will keep you informed about all advance resulting from checking out all your proposals from above. Please give me some time for this, there is lots of “real life work” waiting to be done right now, and it’s waiting for me 🙂

                                Windows is like a submarine. Open a window and serious problems will start.

                              Viewing 14 posts - 1 through 14 (of 14 total)
                              • You must be logged in to reply to this topic.