antiX-19 released

[Member olsztyn]

Helpful

Up

0

::

Great. Thanks much for this info…
Thank you development team for this great release. Getting close to a perfect Linux…

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Member olsztyn]

Helpful

Up

0

::

BitJam wrote:

I also gave a quick fix over in the MX forums. To fix an encrypted live-usb that does not boot, (assuming it is at /dev/sdd) run this command:
sudo parted /dev/sdd set 2 boot off set 1 boot on print
It should show the “boot” flag on the first (ex4) partition.

Thanks BitJam for this tip. So it is the boot flag that was set to second partition…
Running this to set boot flag to the first partition worked fine and antiX starts to boot however it stops with a fatal error complaining that encrypted partition is not a LUKS device, giving just two opportunities:
P – Power off
r – reboot.
Am I still missing something? Normally, antiX 17 was asking to set encryption password at this point…
Just to add, I saw this reported on MX forum as you mentioned but I have not seen a resolution…
Considering Live-USB-Maker is already 0.4.0, in case there is no fix I am OK with suggestion from anti to use antiX 17 for Live USB making. This way requires an extra step of creating an ISO from a fully configured antiX 19, as option ‘Create from run system’ cannot be used due to the run system being antiX 17, so just a tool to burn the actual fully configured antiX 19 system.
Thanks again and Regards…

• This reply was modified 3 years, 6 months ago by olsztyn.

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Member ex_Koo]

Helpful

Up

0

::

@rokytnji

Just run this command should be enough if you only have onboard sound sudo antiX-cli-cc then > alsa-set-default-card or you can run it from antiX Control Centre it all sudo anyway.

pulse audio has never been installed by default on any version of antiX i have used. Thankfully

———————————————–
But for my usb sound dac I do this too. Running antiX 19 base & Stevo’s version of waterfox 56.2.14 x64 all sound is working just fine web & music and to tell you the truth I don’t even need apulse to get sound to work a browser. And apulse is install by default on antiX and I don’t know why.

All i do to setup my default sound card is run = cat /proc/asound/cards as below you can see my usb tascam US 2×2 is (3)

10 files = 312K ~ >$cat /proc/asound/cards
 
0 [PCH            ]: HDA-Intel - HDA Intel PCH
                      HDA Intel PCH at 0xf7130000 irq 29
 1 [NVidia         ]: HDA-Intel - HDA NVidia
                      HDA NVidia at 0xf7080000 irq 17
 2 [Device         ]: USB-Audio - USB PnP Audio Device
                      C-Media Electronics Inc. USB PnP Audio Device at usb-0000:00:14.0-4, full speed
 3 [US2x2          ]: USB-Audio - US-2x2
                      TEAC Corporation US-2x2 at usb-0000:00:14.0-10, high speed

Then just edit the etc/asound.conf file and edit these two lines =
defaults.pcm.card 3
defaults.ctl.card 3

asound.conf

# v4.0
# Requires alsa-utils libasound2-plugin-equal

# ***** Defaults *******************************************************

# Audio card/chip and device to use and control
# In most cases these settings should remain commented (#)
# When commented, card and device 0 are usually automatically selected
# When uncommented, the item corresponding to the number is selected
defaults.pcm.card 3
defaults.ctl.card 3
#defaults.pcm.device 0

# ***** Reset **********************************************************

# override the existing definition of the default device 
pcm.!default 
{
   type plug
  
   # point output to the equalizer device
   slave.pcm plugequal
}

# ***** Equalizer ******************************************************

# set up the control interface of the equalizer device
ctl.equalizer
{
   type equal
}

# set up the equalizer device
pcm.plugequal
{
   type equal
  
   # point output to device named preamp
   slave.pcm  "plug:preamp"
}

# ***** Pre-Amp ********************************************************

# set up the preamp device
pcm.preamp 
{
   type softvol

   # name of slider control to display in alsamixer interface
   control.name Pre-Amp
   
   # minimum dB when slider is at 0%
   min_dB -5.0
   
   # maximum dB when slider is at 100%
   max_dB 40.0
   
   # point output to device named duplex
   slave.pcm "duplex"
}

# ***** Playback and Capture *******************************************

# set up the playback/capture device
pcm.duplex 
{
   type asym

   # point playback output to use dmix
   playback.pcm "dmix"

   # point capture input record to use dsnoop
   capture.pcm "dsnoop"
}

[Forum Admin rokytnji]

Helpful

Up

0

::

No worries here Koo. It is nice you posted a alternate way . Friendly suggestion below.

In the how to section would be a treat, with a bonus of being easier to find.

I figure. Give it few days or weeks. Some human being will step up and post a remastered 32bit base iso with firefox removed. Cuz choice is always good in my opinion.
Things just tend to work out well sometimes if one is patient.

• This reply was modified 3 years, 6 months ago by rokytnji.

Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.

Linux Registered User # 475019
How to Search for AntiX solutions to your problems

[Member rayburn]

Helpful

Up

0

::

I would like to add my gratitude to all the team who make such a fantastic distro! Long time user here, and it has been near faultless over many years, thanks Anti and all who are involved in the development.

Long may it continue.

[Member greyowl]

Helpful

Up

0

::

I really appreciate all the effort of the developers in making this valuable distribution for all of us to enjoy.

Dell Latitude D620 laptop with antiX 22 (64 bit)

[Member afab4]

Helpful

Up

0

::

I never saw the need for sudo to be offered and selective in the Control Centre. When I want to process something that requires superuser
access, logging in root via “su” has always been and will continue to be my choice.
I understand others feel differently and that is OK. There is a choice.
Unfortunately, after selecting “su” in the Control Centre, I lose the ability to open those apps that require superuser access by using my root password.
If I go back into the Control Centre and re-select sudo then I am able to open those apps using my login password.
Am I doing something wrong? Is there another setting I am missing?
Thanks

It appears some apps work with su and some don’t. Gparted and Synaptic do not.

• This reply was modified 3 years, 6 months ago by afab4.

I support the candidate that will steal the least from me.

[Forum Admin BitJam]

Helpful

Up

0

::

olsztyn wrote:

antiX starts to boot however it stops with a fatal error complaining that encrypted partition is not a LUKS device, giving just two opportunities:
P – Power off
r – reboot.
Am I still missing something

This is another bug. It was fixed yesterday and the fixed version of LUM should be in the repos now. The problem is that on Debian, cryptsetup uses the new luks2 format by default while our live initrd specifies “–type luks” which is interpreted to mean luks1. All very crazy IMO. We removed the “–type luks” in the live initrd and we now have LUM default to luks1. You can get luks2 with –force=luks2 in LUM but it still doesn’t work with our live initrd. The last problem I got was a missing glibc_xxxx library. So for now, only luks1 works in our live initrd and the most recent LUM uses luks1 as the default.

I’m very sorry for all of the trouble and confusion. It is clear now that we need to implement much stricter test procedures before a release. For LUM and the live initrd, I’d like to make a checklist, sort of like the checklist used by pilots before they take off. I’d also like to post the checklist(s) on a forum so volunteers can check things off. We have so many different options available now, it would help if we had a group effort to check them all.

Again, I’m sorry for all the problems.

Context is worth 80 IQ points -- Alan Kay

[Anonymous]

Helpful

Up

0

::

Unfortunately, after selecting “su” …

.

Debian 10 aka Buster ReleaseNotes (PDF)

Semantics for using environment variables for su changed

su has changed semantics in buster and no longer preserves the user environment variables DISPLAY
and XAUTHORITY. If you need to run graphical applications with su, you will have to explicitly set
them to allow access to your display. See bug #905409 (https://bugs.debian.org/905409) for
an extensive discussion.

[Anonymous]

Helpful

Up

0

::

In the desktop menu: Applications } Graphics } Gcolor2
However, the gcolor2 package is not pre-installed.

yad --color
provides a GUI offering functionality identical to gcolor2, FWIW

[Member olsztyn]

Helpful

Up

0

::

BitJam wrote:

This is another bug. It was fixed yesterday and the fixed version of LUM should be in the repos now. The problem is that on Debian, cryptsetup uses the new luks2 format by default while our live initrd specifies “–type luks” which is interpreted to mean luks1.

Thank you BitJam and development team for such expeditious update!
My quick testing confirms the current fix (luks 1) works. As a matter of fact I am typing this from encrypted antiX…
Great you are planning a checklist for the future. Please count me in as one of volunteers to test antiX Live aspects…
Thanks and Regards…

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Member Will B]

Helpful

Up

0

::

anticapitalista and the team, congratulations! Thank you for your hard work! 🙂

Blessed and forgiven in the Pacific Northwest of the US! 😀

[Moderator BobC]

Helpful

Up

0

::

Lookin good, anticapitalista and the Devs!

Because I am on 386 base, I don’t have Synaptic by default. I got it installed manually, but I think it would be a good idea to add it to both the cli Manage Packages as a top GUI package. Skidoo suggested, just offer to install it if you click manage packages, which would be even better.

Thanks again, its running well here…

• This reply was modified 3 years, 6 months ago by BobC. Reason: removed viewer stuff, oh well

[Member fungalnet]

Helpful

Up

0

::

ooohhh ooohhh…. there is a problem, it seems there are people (apparently from Brasil, and I dare call them people) who dislike the choice of the name for the edition 🙂

https://www.reddit.com/r/antiXLinux/comments/dl602q/who_was_marielle_franco_for_whom_antix19_is/

If I was “anticapitalista” I would stay away from cop stations in Rio 🙂

Hey, this sounds better than I thought 🙂

anti-X - Adélie - obarun - systemd Free Space

[Member oops]

Helpful

Up

0

::

Right … A neutral name for the new versions would be much more judicious. Like MX, Ubuntu, etc

[Author]

Posts