antiX-19-b2-full (64 and 32 bit) available

[Anonymous]

Helpful

Up

0

::

There must be something wrong with the driver then.

+1 4 Xecure.

@entropyfoe

Try Kernels 5.3 and newer.

https://betanews.com/2019/07/13/amd-ryzen-3000-linux-problems/
https://hardforum.com/threads/ryzen-issues-with-linux.1966533/
https://community.amd.com/thread/238773

Just as example but, there are tons of other issues with all AMD Ryzen’s, 1 ~ 3k.

Just try binging, googleing … after “amd ryzen linux sound problems”.

[Member entropyfoe]

Helpful

Up

0

::

My Ryzen is first generation, and sound works well under the 4.19 series that MX uses, and I have just installed from tha antiX repos using synaptic.

Does a 5.3 kernel exist in the antiX repos?
I just saw the announcement for a new 5.1.

Asus Prime 370X-Pro
AMD Ryzen 1600X (6 cores @ 3.6 GHz)
16 Gig DDR4 3200 (G Skill)
Nvidia -MSI GeForce GT 710 fanless
Samsung 960 NVMe SSD nvme0n1 P1,P2, and P3=MX-18, P4=antiX-19 beta
2TB WD sda1= data
on-board ethernet &and sound

[Anonymous]

Helpful

Up

0

::

Does a 5.3 kernel exist in the antiX repos?

Definitely not but, probably the ‘doers’ could do it.

Kernel 5.2 brought many improvements for new machines but, was missing AMD part.
Since AMD finally released their Code too, it all flew in to the 5.3.

https://www.heise.de/ct/artikel/Linux-5-2-freigegeben-Aenderungsrekord-und-Geschwindigkeitsverbesserungen-4424484.html?seite=all
https://www.heise.de/ct/artikel/Linux-5-3-bringt-Treiber-fuer-AMDs-neue-Grafikchip-Generation-4470638.html

[Member Xecure]

Helpful

Up

0

::

entropyfoe wrote:

Can you give some more detailed instruction on how to execute the command you showed.

dmesg | grep “audio”

Play again any sound and check the end of dmesg for errors
dmesg | tail

I am doing something wrong. Do I navigate to the var/logs directory and run those commands in the terminal?

Because I get nothing, or the “command not found” error.

Sorry. I should have explained better. Let us understand each thing so you don’t go in blind. We may also learn something about how the computer works. This may even help figure out what needs to be done so this fix works out of the box when the stable release goes out. (The next explanation is flawed, but it will help illustrate what each command does).

The linux kernel “talks” with the hardware, but the hardware has many parts that “talk different languages”. So that the kernel understands each piece of hardware, so that it can “have a conversation”, it needs a “translator”. The drivers are the translators. The drivers are built (or can later be built) as modules “in” the kernel.
The kernel loads these modules “dynamically” as they are needed, but sometimes it loads modules that “complicate” the translation (or simply translate badly). That is why sometimes modules have to be blacklisted so they don’t come out and complicate the translation.

To see all the modules that are loaded by the kernel at any given time, we use “list module” = lsmod. Open any terminal and check it out
lsmod
For your sound device, the driver used is “hda_intel”, so you can check out all modules that share that name and the ones that depend on this hda_intel module
lsmod | grep "hda_intel"

This is my device:

$ inxi -A
Audio:
  Device-1: Intel 7 Series/C216 Family High Definition Audio 
  driver: snd_hda_intel 
  Sound Server: ALSA v: k4.9.182-antix.1-amd64-smp 

And this is what lsmod shows for this module (or “driver”):

$ lsmod | grep "snd_hda_intel"
snd_hda_intel          22909  1
snd_hda_codec          85234  4 snd_hda_intel,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek
snd_hda_core           44417  5 snd_hda_intel,snd_hda_codec,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek
snd_pcm                78120  4 snd_hda_intel,snd_hda_codec,snd_hda_core,snd_hda_codec_hdmi
snd                    58235  10 snd_hda_intel,snd_hwdep,snd_hda_codec,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek,snd_pcm

It would be great if you could do this command in MX linux and antiX 19b, so that we could compare. Maybe a wrong module is being loaded and “complicating the translation”.

To manually load modules (or unload) them, the command “modprobe” is used. We may have to unload some modules or even reload them if we want to find the problem. Hopefully, which modules to unload or reload could be decided by an expert (not me, but I will help as much as I can).

When something goes on with the drivers (good or bad), the kernel informs us through messages. This messages can be seen with the command “dmesg”. Wikipedia explains it best:

dmesg (display message or driver message) is a command on most Unix-like operating systems that prints the message buffer of the kernel. The output of this command typically contains the messages produced by the device drivers.

That is why I was asking you for what “errors” does the kernel find with the audio drivers. This works best the first time one executes the system. On a live environment, I get this when asking dmesg about any message containing the word “audio”:

$ dmesg | grep "audio"
[    9.086341] snd_hda_codec_realtek hdaudioC0D0: ALC269VB: SKU not ready 0x598301f0
[    9.086918] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC269VB: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[    9.086921] snd_hda_codec_realtek hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[    9.086923] snd_hda_codec_realtek hdaudioC0D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[    9.086925] snd_hda_codec_realtek hdaudioC0D0:    mono: mono_out=0x0
[    9.086926] snd_hda_codec_realtek hdaudioC0D0:    inputs:
[    9.086928] snd_hda_codec_realtek hdaudioC0D0:      Internal Mic=0x1b
[    9.086930] snd_hda_codec_realtek hdaudioC0D0:      Mic=0x18
[    9.155598] snd_hda_intel 0000:00:1b.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])

This shows some info, but I cannot see any errors.
I guess that the antiX19b2 cannot “see” any errors for you either, as each time you run the “dmesg” command asking for the driver, no message (no errors) pop up.

Our only clue now is to figure out how differently are the drivers behaving between MX and antiX, so to find what module/driver is “misbehaving” and to blacklist it or find out if it needs a different module to correctly “translate” between the system and the audio chip.

If someone with experience can come in, we could do this in less time and find the problem sooner, so nobody wastes too much time.

Thanks for reading.

• This reply was modified 3 years, 9 months ago by Xecure. Reason: Corrections

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member entropyfoe]

Helpful

Up

0

::

Xecure,

Again, I am thankful for your knowledge and willingness to help on this. I think it is important that I get this figured out, as this is a common Asus board and common audio chip, so others may face this same issue. Including me, when MX 19 arrives !

Your instructions are clear, and I will execute them tonight.
I can do the modprobe and dmesg on both the beta2 installation and my MX-18 with working sound.

This is one reason I like the partition set-up I have for dual booting, I can experiment, and always compare to a known working system on the exact same hardware.

I don’t think a different kernel is the answer, something in Buster(?). It is these drivers and modules that I must compare to the MX-18, there will be the difference, and hopefully a solution. Or I am missing something really obvious and stupid.

This forum is what makes antiX and MX so great, helpful knowledgeable people.

Asus Prime 370X-Pro
AMD Ryzen 1600X (6 cores @ 3.6 GHz)
16 Gig DDR4 3200 (G Skill)
Nvidia -MSI GeForce GT 710 fanless
Samsung 960 NVMe SSD nvme0n1 P1,P2, and P3=MX-18, P4=antiX-19 beta
2TB WD sda1= data
on-board ethernet &and sound

[Anonymous]

Helpful

Up

0

::

this is a common Asus board and common audio chip, so others may face this same issue

If it’s common hardware, a websearch should be enlightening.

Is pulseaudio installed (to check: apt policy pulseaudio)

https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1781294
I have found the culprit. Sound card was intercepted by another process (timidity), so Pulseaudio was unable to use it.
I have discovered the offending process via the sudo fuser /dev/snd/* command.
Uninstalling timidity has solved the issue.

.

https://askubuntu.com/questions/1042318/no-sound-in-ubuntu-18-04-hp-notebook
{paraphrased}
Install music packages of rhythmbox with: sudo apt install rhythmbox
or if it’s already installed then: sudo apt install –reinstall rhythmbox
This package contains some additional drivers.
Then reboot.

.

for me, the simple fix was

sudo alsa force-reload

.

https://askubuntu.com/questions/1059619/sound-card-shown-as-dummy-output-in-ubuntu-18-04

$ sudo lshw -c sound
*-multimedia UNCLAIMED
description: Audio device
product: 200 Series PCH HD Audio
vendor: Intel Corporation

[Anonymous]

Helpful

Up

0

::

Seriously ?!?

This instance of finding my collaboration // contribution attempts spurned isn’t ego shattering, but it does serve as a reminder of how much wasted effort I’ve cumulatively expended in crafting items intended to enhance antiX, or (SLiM, fluxbox, rox-filer, etc) tailored to suit the “rube goldberg” -ish antiX desktop-session

The way it is now, you got things networked together with the (xxxxxx.antix)dependencies, you can’t get rid of something without the .antix dependencies, it’s endemic, reminds me of systemd in a way.

— macondo
https://www.antixforum.com/forums/topic/launching-ratpoison/#post-23641

.
Sigh. Talkin to the wall. Y’all gonna do what you’re gonna do.

Anonymous wrote:

prox, I agree that additional info on the download page would be helpful.
[..]
a presentation like this (with horizontal dividers) would provide a clear delineation

_______________________________________________________________________________

The following completely systemd-free flavours for both 32 and 64 bit architecture are offered:

antiX-full (c1GB) – 4 windows managers – IceWM (default), fluxbox, jwm and herbstluftwm, plus full libreoffice suite
antiX-base (c680MB so fits on a cd) – 4 windows managers – IceWM (default), fluxbox, jwm and herbstluftwm
_______________________________________________________________________________

Also, for expert users (who are comfortable with building up a customized debian-based linux system):

antiX-core (c330MB) systemd-free – no X, but should support most wireless
antiX-net (c170MB) systemd-free – no X. Just enough to get you connected (wired) and ready to build.

_______________________________________________________________________________

https://www.antixforum.com/forums/topic/boot-process-does-not-result-in-starting-x-a-window-manager/

[Member entropyfoe]

Helpful

Up

0

::

Xecure,

OK, I have booted both partitions and executed the commands. As I see the result is the same.
In both cases, a fresh boot, open and play a wave file. (In MX-18, It plays, I hear it with clementine) In the beta2, I fresh boot, open a wave file im xmms, the equalizer is moving up and down, time is advancing, no sound.

From MC-18.3, sound works.
music@Ryzen:~
$ lsmod | grep "hda_intel"
snd_hda_intel          32768  5
snd_hda_codec         118784  4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek
snd_hda_core           65536  5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek
snd_pcm                98304  4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core
snd                    81920  18 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm
music@Ryzen:~

root@Ryzen:/home/music# dmesg | grep "audio"
[    4.960275] snd_hda_intel 0000:0a:00.1: Handle vga_switcheroo audio client
[    4.972159] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC1220: line_outs=3 (0x14/0x15/0x16/0x0/0x0) type:line
[    4.972161] snd_hda_codec_realtek hdaudioC1D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[    4.972162] snd_hda_codec_realtek hdaudioC1D0:    hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
[    4.972163] snd_hda_codec_realtek hdaudioC1D0:    mono: mono_out=0x0
[    4.972164] snd_hda_codec_realtek hdaudioC1D0:    dig-out=0x1e/0x0
[    4.972165] snd_hda_codec_realtek hdaudioC1D0:    inputs:
[    4.972166] snd_hda_codec_realtek hdaudioC1D0:      Front Mic=0x19
[    4.972167] snd_hda_codec_realtek hdaudioC1D0:      Rear Mic=0x18
[    4.972168] snd_hda_codec_realtek hdaudioC1D0:      Line=0x1a

And in the beta2 I have these modules (darn… I should have checked the snd modules in MX 18)
r`oot@Ryzen:/home/music# lsmod | grep “snd”
snd_hda_codec_hdmi 57344 1
snd_hda_codec_realtek 122880 1
snd_hda_codec_generic 86016 1 snd_hda_codec_realtek
snd_hda_intel 45056 1
snd_hda_codec 151552 4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek
snd_hda_core 94208 5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek
snd_hwdep 16384 1 snd_hda_codec
snd_pcm 114688 4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core
snd_timer 36864 1 snd_pcm
snd 94208 10 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm
soundcore 16384 1 snd

And the output of the commands, looks the same as the beta, so the snd_intel stuff is all OK, maybe one of the other ones is incorrect?
The Realtek detection is there, and looks correct.  Here is the beta2 command output.

root@Ryzen:/home/music# dmesg | grep “audio”g
[ 5.327751] snd_hda_intel 0000:0a:00.1: Handle vga_switcheroo audio client
[ 5.349848] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC1220: line_outs=3 (0x14/0x15/0x16/0x0/0x0) type:line
[ 5.349849] snd_hda_codec_realtek hdaudioC1D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 5.349850] snd_hda_codec_realtek hdaudioC1D0: hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
[ 5.349851] snd_hda_codec_realtek hdaudioC1D0: mono: mono_out=0x0
[ 5.349851] snd_hda_codec_realtek hdaudioC1D0: dig-out=0x1e/0x0
[ 5.349852] snd_hda_codec_realtek hdaudioC1D0: inputs:
[ 5.349853] snd_hda_codec_realtek hdaudioC1D0: Front Mic=0x19
[ 5.349854] snd_hda_codec_realtek hdaudioC1D0: Rear Mic=0x18
[ 5.349854] snd_hda_codec_realtek hdaudioC1D0: Line=0x1a`

skidoo, I will start checking the google, maybe somebody with this board is also trying a buster install. But in the past, I have seen that answers here at the forums are more reliable.

The main difference is still only what inxi shows – that AMD Family 17h

 From the beta1 and 2
Audio:
Device-1: NVIDIA GK208 HDMI/DP Audio driver: snd_hda_intel
Device-2: AMD Family 17h HD Audio driver: snd_hda_intel Same on the beta2
Sound Server: ALSA v: k4.9.176-antix.1-amd64-smp

From the working mx-18
Audio: Device-1: NVIDIA GK208 HDMI/DP Audio driver: snd_hda_intel
Device-2: AMD driver: snd_hda_intel
Sound Server: ALSA v: k4.19.18-antix.1-amd64-smp

• This reply was modified 3 years, 9 months ago by entropyfoe. Reason: Forgot to add one code section from the beta2
• This reply was modified 3 years, 9 months ago by entropyfoe.

Asus Prime 370X-Pro
AMD Ryzen 1600X (6 cores @ 3.6 GHz)
16 Gig DDR4 3200 (G Skill)
Nvidia -MSI GeForce GT 710 fanless
Samsung 960 NVMe SSD nvme0n1 P1,P2, and P3=MX-18, P4=antiX-19 beta
2TB WD sda1= data
on-board ethernet &and sound

[Anonymous]

Helpful

Up

0

::

Hi entropyfoe,

Is XMMS setup in antix-19 for the right soundcard?

in XMMS goto options-preferences then see if the output plugin is set to the right
sound card under configure.

[Member entropyfoe]

Helpful

Up

0

::

linuxdaddy,

Wow, that was easy !

I opened xmms, opened the little square in the upper left, selected options -> preferences. It has the first tab, Audio I/O plugins.
The output plugin was ALSA 1.2.11 output plugin [libALSA.so]. I clicked the configure button, selected the audio device , it was set to default with Realtek options analog and digital below. I selected the analog. Then the Audio device shows as hw:1,0. I clicked OK, then apply on the preferences window. Click OK, and now ……

Voila, sound emerges from the speakers !

Thanks to everyone that helped me troubleshoot this.
I never knew that the preferences existed !

Then I checked youtube, still no sound. So maybe it too needs a configuration in the browser?

• This reply was modified 3 years, 9 months ago by entropyfoe.
• This reply was modified 3 years, 9 months ago by entropyfoe. Reason: Mistakenly wrote Nvidia audio instead of the Realtek, fixed mis-typings

Asus Prime 370X-Pro
AMD Ryzen 1600X (6 cores @ 3.6 GHz)
16 Gig DDR4 3200 (G Skill)
Nvidia -MSI GeForce GT 710 fanless
Samsung 960 NVMe SSD nvme0n1 P1,P2, and P3=MX-18, P4=antiX-19 beta
2TB WD sda1= data
on-board ethernet &and sound

[Member Xecure]

Helpful

Up

0

::

entropyfoe wrote:

I opened xmmx, opened the little square in the upper left, selected options ->preferences. It has the first tab, Audio I/O plugins.
The optput plugin was ALSA 1.2.11 outputp lugin [libALSA.so]. I clicked the configure button, selected the audio device , it was set to default with Nvidia options analog and digital. I selected the analog. Then the Audio device shows as hw:1,0. I clicked OK, then apply on the preferences window. Click OK, and now ……

Voila, sound emerges from the speakers !

Good news! It is not driver related! Now to figure out the firefox issue.

Today I was lucky and I had access to a friends computer with a Ryzen 5 2400G. He doesn’t use a dedicated graphic card but the integrated ATI one in the AMD chip.
I loaded antiX 19b2 from USB and had no sound at the begining. I suspected that it must be related to the monitor being conected to HDMI. He has speakers conected to a jack port (to the motherboard). Out of the box, everything worked (including wifi) except for sound, but I didn’t have much time to test.

$ inxi -F
System:
  Host: antix1 Kernel: 4.9.182-antix.1-amd64-smp x86_64 bits: 64 
  Desktop: IceWM 1.5.5+git20190610 
  Distro: antiX-19.b2_x64-full Marielle Franco 13 July 2019 
Machine:
  Type: Desktop Mobo: Micro-Star model: B450I GAMING PLUS AC (MS-7A40) 
  v: 2.0 serial: <root required> UEFI [Legacy]: American Megatrends v: A.20 
  date: 11/06/2018 
CPU:
  Topology: Quad Core model: AMD Ryzen 5 2400G with Radeon Vega Graphics 
  bits: 64 type: MT MCP L2 cache: 2048 KiB 
  Speed: 1600 MHz min/max: 1600/3600 MHz Core speeds (MHz): 1: 1600 2: 1600 
  3: 1600 4: 1600 5: 1600 6: 1600 7: 1600 8: 1600 
Graphics:
  Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] 
  driver: N/A 
  Display: x11 server: X.Org 1.20.4 driver: vesa resolution: 1920x1080~N/A 
  OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6 
Audio:
  Device-1: AMD driver: snd_hda_intel 
  Device-2: AMD driver: snd_hda_intel 
  Sound Server: ALSA v: k4.9.182-antix.1-amd64-smp 

I checked the audio devices:

$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: Generic [HD-Audio Generic], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: Generic_1 [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

So the only one I was interested in was card 1

I tested out things before trying to change the card:
played mp3: no sound
played video on youtobe: no sound

I went to Control Center > Hardware > Sound Card Chooser
(you can also access this using alsa-set-default-card in terminal)
First device didn’t work. Choosing it, it then asked for testing, I said “yes”, but the sound test just skiped.

Second device, I chose to test it, and I had sound. Everything was very easy and worked.
The video in Firefox still had no sound (because I didn’t close it before changing cards).
i closed Firefox, opened again, and now it used the default card and sound played out of the speakers.

As linuxdaddy sugested to change the card in XMMS, that means that the “set Default Sound Card” isn’t working properly. You had to manually change the card in the XMMS media player, so it didn’t use the “Default Sound Card”. try choosing the sound card again with
alsa-set-default-card
Execute it in terminal.
Test ALL devices and perform the sound test for each. If none works, you will have to set the correct device using the terminal.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Moderator BobC]

Helpful

Up

0

::

anti, Is there any help you need with diagnosis or testing on the problem with not being able to connect via wifi while booted from the flashdrive? That problem was with the Dell D620 running the BRCM 4311 wifi. Nothing shows up in Connman after I enable wireless. I don’t need a fix for me, as installing solved it for me, but I’m concerned if others try the distro and can’t connect…

[Member orcrist]

Helpful

Up

0

::

When trying to connect a printer (Control Center–> Hardware–> Print Settings), I get the message “Printing service unavailable. Start the service on this computer or connect to another server”.
I had to run the command “sudo service cups restart” on the terminal in order to continue with the printer connection.

[Forum Admin anticapitalista]

Helpful

Up

0

::

orcrist wrote:

When trying to connect a printer (Control Center–> Hardware–> Print Settings), I get the message “Printing service unavailable. Start the service on this computer or connect to another server”.
I had to run the command “sudo service cups restart” on the terminal in order to continue with the printer connection.

If running live, then you need to do either what you did or remove the disable=lx cheat at the boot menu (it turns off cups)

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

antiX with runit - leaner and meaner.

[Forum Admin Dave]

Helpful

Up

0

::

Anonymous wrote:

Seriously ?!?

This instance of finding my collaboration // contribution attempts spurned isn’t ego shattering, but it does serve as a reminder of how much wasted effort I’ve cumulatively expended in crafting items intended to enhance antiX, or (SLiM, fluxbox, rox-filer, etc) tailored to suit the “rube goldberg” -ish antiX desktop-session

The way it is now, you got things networked together with the (xxxxxx.antix)dependencies, you can’t get rid of something without the .antix dependencies, it’s endemic, reminds me of systemd in a way.

— macondo
https://www.antixforum.com/forums/topic/launching-ratpoison/#post-23641

.
Sigh. Talkin to the wall. Y’all gonna do what you’re gonna do.

skidoo wrote:

prox, I agree that additional info on the download page would be helpful.
[..]
a presentation like this (with horizontal dividers) would provide a clear delineation

_______________________________________________________________________________

The following completely systemd-free flavours for both 32 and 64 bit architecture are offered:

antiX-full (c1GB) – 4 windows managers – IceWM (default), fluxbox, jwm and herbstluftwm, plus full libreoffice suite
antiX-base (c680MB so fits on a cd) – 4 windows managers – IceWM (default), fluxbox, jwm and herbstluftwm
_______________________________________________________________________________

Also, for expert users (who are comfortable with building up a customized debian-based linux system):

antiX-core (c330MB) systemd-free – no X, but should support most wireless
antiX-net (c170MB) systemd-free – no X. Just enough to get you connected (wired) and ready to build.

_______________________________________________________________________________

https://www.antixforum.com/forums/topic/boot-process-does-not-result-in-starting-x-a-window-manager/

I always seem to read a different 1000 words than what was intended by the picture.
I am dense… what are the images referring to / pointing out ?

Is it related to how things are packaged?
That the repo package is now a few versions back from the github?
That the text does not fit in the window?
Some apps are named with the same intended function or that some apps need to be conditionally purged from the list?

Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown

[Author]

Posts