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

[dolphin_oracle]

dumb question: Have you made sure the volumes are turned up in alsamixer?

[entropyfoe]

Yes, I went into the alsamixer, and turned all the sliders up. I think I arrowed over to get them all including, master, center, LFE, etc.
I will double check tonight.

The sound is not quiet, there is no sound.

[anticapitalista]

Make sure they are not muted (M)

[entropyfoe]

Anti,

Where would I see this "M"?

I did not see any M, but I wasn't looking for it.
Would arrowing up the sliders reverse any mute? :lipsrsealed:

[dolphin_oracle]

Anti,

Where would I see this "M"?

I did not see any M, but I wasn't looking for it.
Would arrowing up the sliders reverse any mute? :lipsrsealed:

actually it doesn't, not in alsamixer. the mute would be at the bottom of the sliders. if you have numbers, then they aren't muted.

[antiX-Dave]

You may have the correct card set, but will need to find which channel is to be set. It may not be channel one. Perhaps channel 2 or 0 or what have you. You should be able to use aplay to play an audio file and specify the card , channel, and volume from terminal. Once you find the magic pair you can set that in the asoundrc file.

Maybe this helps
https://wiki.archlinux.org/index.php/Ad ... chitecture

[entropyfoe]

Thanks antiX-Dave and d_o

I will check those things tonight. The arch documentation (as usual) looks very thorough, much to read.

I was not familiar with the "channels".
I guess for the beta, the question is why would a wrong channel be selected, when in MX 18 and antiX 18, it worked out of the box correctly?

[entropyfoe]

Nothing is muted, al sliders have numbers under them.

So, next to check the channels.

I messed around with that asound command using that Arch link for almost an hour last night. I clearly was too tired, or my brain is getting soft, but I was never able to get any sound out, trying many channels, though I saw errors indicating my syntax for the command may be wrong. The Arch examples don't quite match up, so I am at a loss.

As a last ditch I reinstalled the beta, same result, no sound. My only comment on the installer is that it offers up the grup options during the progress bar, making a user think that the default (to mbr) is selected, even if that is not the eventual choice. How is the user to know, that despite the grub choices being shown, that the option to change them will come later . So, in my first install, I aborted, made my grub selection, and restarted the install. So I thought it may have caused a problem. Hence my try at a reinstall.

[entropyfoe]

The beta1 is fast running from USB and installing.

In the installer, I think the grub options, at least on my machine/USB, come up too soon, while it is installing, causing the user (me) to think it was going to install to mbr.
This would be over my day-to -ay MX 18.3 install. So I aborted and restarted. It should show after the install progress bar stops moving, at least that's how I remember it. The grub is after the installation, right?

As noted above, in the live toram did not work

The nvidia installer in the control panel did not work because ddm-mx was not installed. (This may have been fixed as synaptic installed it upon my reinstall)

My biggest problem is no sound. I tried many things, got advice from the oracle, anti, antix-Dave.
I read a detailed Arch manual page, I could not make it work. I tried a reinstalling. My only clue comes from an inxi-F from the beta and the working mx-18.

Code: Select all

From the beta1
Audio:
  Device-1: NVIDIA GK208 HDMI/DP Audio driver: snd_hda_intel 
  Device-2: AMD Family 17h HD Audio driver: snd_hda_intel 
  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

Interestingly, the system profiler in mx 18 says only

Multimedia
Audio Adapter HDA-Intel - HDA NVidia
Audio Adapter HDA-Intel - HD-Audio Generic

It is almost like the beta1 in the hardware detection is over detecting or incorrectly detecting the audio hardware on this on board (Asus motherboard) audio chip.
When the Ryzen came out 2 years ago, I think the audio driver was still marginal under linux, and it was antiX 17 I think, where I first tried it , and it just worked ! The reason linux support took so long, is that it was a new audio chip, the The Realtek S1220A. Yet all the above, including on the working mx18, the Realtek is not mentioned, it is called generic or amd, and all use the snd_hda_intel driver.

[dolphin_oracle]

these days the new installer asks you config questions, including grub, while the file copy is going on. if you don't enter info right away, it will wait for you though.