- This topic has 169 replies, 25 voices, and was last updated Sep 17-6:03 am by Anonymous.
-
Posts
-
Xecure
Several times after boot, connman registered failure to automatically connect to my saved wireless network.
Connman takes a bit of time, and the pop-up o connect will always launch even if the wifi configuration is OK. You just have to wait a bit.
postinst script within the package performs the change, silently, immediately (and permanently, unless running live and you throwaway persistence)
sudo apt install usrmerge && sudo apt purge usrmerge
Thanks. That is what I thought. It worked this way.
Does dpkg -S no longer support full paths?
The example I presented lacked context. Immediately after the “no path found” result, I installed usrmerge & retried the identical “dpkg -S /usr/local/bin/antixcc.sh” command and it succeeded.
Thanks. I tested now and it works. I don’t know what happened before for it to fail me. Sorry for the false alarm.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.
Wallon
Additional information,
On the 1st screen of my Live USB key, there is;
UEFI
or
USB Disk
I take the USB Disk optionOn the second screen of my Live USB key, I take the following options;
F2 > French or French (BE), it is the same
Use Legacy or Use Modern, it’s the sameOn the third screen of my Live USB key, I take the following options;
F2 > French(BE)
F3 > Brussels
F4 > noautomount
F6 > space-iceWM
NORMAL BootThe installation is only in UEFI mode. Legacy mode is gone.
Xecure
The installation is only in UEFI mode. Legacy mode is gone.
I didn’t understand, Wallon.
Do you mean that when you boot in UEFI mode the option “Legacy” is not there? The UEFI (grub) menus have the option to select a different kernel in Advanced options, (where you can also select desktop, noautomount, save-grub mode -> to select how you want your selected options to be saved, etc.). NON uefi (isolinux/syslinux) has a different menu system to UEFI mode (grub menus).
Before, in UEFI mode, you could only select option in text menus or directly writing the bootcode inside the “editing” grub mode. Now we can select language/keyboard/timzone in the seconf grub menu option, and also have more advanced menus in the “Advanced Options”, which lets us change kernel, and many other boot parameters.My am not sure if this answers the question.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.Wallon
Dear Xecure,
I found the solution with the new Antix Installer.
So I’m still trying to pretend I don’t know anything about Linux.
I always do a manual installation and choose;
1) my second USB key to do the installation,
2) the SWAP physical partition on the second USB key (sdi1 in my case),
3) the ROOT physical partition on the second USB key (sdi2 in my case).
I checked that the GRUB is always installed on my second USB key and never on the internal SSD in (U)EFI mode.The new Antix Installer selects my internal SSD drive to do a (U)EFI install. (The sda2 in my case).
First solution, in the “Use for” column, you have to put a blank on the internal SSD line and the new Antix Installer will automatically install the Grub on my second USB key (ROOT partition).
Second solution, put manually the mount point with a slash “/” instead of the word “Root”. The Grub will also be installed on the second USB key.
As my MSI motherboard doesn’t allow me to erase mount points on my internal SSD, I don’t like to do a (U)EFI installation. I’ve seen AMD motherboards that have a utility in the “Bios” to very easily erase mount points.
Sincerely,
WallonXecure
Ok. Now I understand what you meant. Sorry for the confusion.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.Xecure
When I installed b1-sysvinit and b1-runit, I did not see an option to preserve the /home directory like I saw in previous install versions?
Now it is present in the advanced installation option, when selecting the home partition, you can choose to “Preserve”, the same as for Swap. See if this image helps:
antiX Live system enthusiast.
General Live Boot Parameters for antiX.
Brian Masinick
@Xecure: RE: The “Preserve” Format option. Is this new for the upcoming release? If not, perhaps I missed it somewhere along the way.
Please let me know if this is documented anywhere other than in this thread and I’d be happy to read up on it since I’ve also missed this feature.
Thanks!
--
Brian Masinickcalciumsodium
When I installed b1-sysvinit and b1-runit, I did not see an option to preserve the /home directory like I saw in previous install versions?
Now it is present in the advanced installation option, when selecting the home partition, you can choose to “Preserve”, the same as for Swap.
Got it. I understand now how it works. Thanks for your help @Xecure.
Brian Masinick
I’ve done some searching; I am guessing that “Preserve” is only mentioned in the “Format -” section on the left side of the Advanced Installation; I’ve been searching the Internet (including our site) for at least 1/2 hour and do not see it documented elsewhere, so I’m presuming that if it is documented, it’s somewhere on that left panel (and it’s lower than what’s shown) – EXCEPT in the post @
https://www.antixforum.com/wp-content/uploads/2021/06/manuel-mount-point.jpgIs it anywhere else? Maybe that’s why I managed to miss it.
--
Brian MasinickXecure
@masinick There is no documented post about this new installer. It was mentioned in the antiX 19.4 release notes:
https://antixlinux.com/antix-19-4-available/
Changes:* more options in the installer
I mentioned it in the video I uploaded (almost 1 month too late. I know, I am very slow making videos).
Excellent video about antiX 19.4 posted by Xecure on YouTube.
https://www.youtube.com/watch?v=Xcd1fkZ16jE
There are 3 minutes and 44 seconds of information.
Hopefully there is more info in the MX forums.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.Brian Masinick
Yeah, “more options” doesn’t really highlight it.
I think that the left panel is the only place that it’s shown and you only see it 1) IF you specify the advanced boot screen AND you scroll down to read the full dialogue in the Format section.
I didn’t do that so until today I didn’t read about any of this.
We certainly have a wealth of options. For as many years and as many times I have installed and used antiX there are still options available that I have never seen or used.
It indicates the richness of our system and it’s actually good that it is not necessary to know or understand everything (unless you have a specific need for a feature). Then it’s sometimes a challenge to find out the less obvious features.
This has been a helpful discussion; I hope that it helps someone else along the way…
- This reply was modified 1 year, 11 months ago by Brian Masinick.
--
Brian Masinick
xinomilo
ok, so i had a serious issue with my main prod laptop with another distro, and thought i’d move permanently/for good to antix. formatted last night with this iso (with uefi/runit/5.10 kernel).
some notes :
– luks partition not mounting problem at boot i had with a1 iso, is fixed in b1! boots normally!
– systemd-timesyncd package shows in “residual configs”, had to :dpkg --purge systemd-timesyncd
– during livecd evaluation, andapt upgrade, i noticed package libpolkit-gobject-elogind-1-0 was marked for autoremoval (probably because it was a version earlier/mirror issue?)… that was fixed in a later upgrade, so just mentioning it.some issues i’ve been seeing :
1) ps:
runsvdir -P /etc/service log: /run: file does not exist runsv lvm2: fatal: unable to start ./run: file does not exist runsv acpi-support: fatal: unable to start ./run: file does not exist runsv rsync: fatal: unable to start ./run: access denied runsv ofono: fatal: unable to start ./run: access denied runsv sudo: fatal: unable to start ./run: file does not exist ./finish: 4: .: cannot open /etc/default/runit: No such file
any idea how to fix it? maybe /etc/sv/$service/run needs to be executable?
2) backlight setting resetting to 100% after boot
3) used the same iso in legacy bios with a decade old laptop and everything was working fine in boot menu for live usb.. with uefi live in this laptop, boot menu didn’t work at most options (some tpm error i didn’t write down 🙁 , something about “TPM unknown error” while trying any options at boot). choosing to boot default entry right after boot was the only thing that worked/booted.
4) after installation, i’ve seen occasional flickering on screen with i915. will see if that continues, cause i’ve just upgraded everything to sid.. (imho, it’s a nice timing to dist-upgrade to sid, things are more stable during release freeze 🙂 )some package suggestions/wishlist :
– replace mlocate with plocate, for bullseye and newer… it is much faster.
– replace keepassx with keepassxc in package suggestions (more up to date i think)
– add signal-desktop option to messaging apps. probably telegram-desktop too, but that’s already in debian repos.
– add ungoogled-chromium in browsers.
– i thought clipit was abandoned(?) and even debian has clipit nowadays as a metapackage to install diodon instead. maybe prefer parcellite as an alternative?Host: LIFEBOOK E746
Kernel: 5.10.27-antix.1-amd64-smp
CPU: Intel i5-6200U (4) @ 2.800GHz
GPU: Intel Skylake GT2 [HD Graphics 520]thanks 🙂
fehlix
3) used the same iso in legacy bios with a decade old laptop and everything was working fine in boot menu for live usb.. with uefi live in this laptop, boot menu didn’t work at most options (some tpm error i didn’t write down, something about “TPM unknown error” while trying any options at boot). choosing to boot default entry right after boot was the only thing that worked/booted.
Probably related to the TPM (Trusted Platform Module) enabled chip within UEFI firmware setting, which might be by default enabled (not only for secure boot). So would you mind to disable GRUB’s tpm module this way:
At GRUB menu press ‘c’ to get a GRUB command line
and remove GRUB’S tpm module with this line and press <ENTER>
rmmod tpm
Press <ESC> to go back to the menu.
Removing tpm by default might be one option to consider.
Thanks- This reply was modified 1 year, 11 months ago by fehlix.
Xecure
some issues i’ve been seeing :
1) ps:
runsvdir -P /etc/service log: /run: file does not exist runsv lvm2: fatal: unable to start ./run: file does not exist runsv acpi-support: fatal: unable to start ./run: file does not exist runsv rsync: fatal: unable to start ./run: access denied runsv ofono: fatal: unable to start ./run: access denied runsv sudo: fatal: unable to start ./run: file does not exist ./finish: 4: .: cannot open /etc/default/runit: No such file
any idea how to fix it? maybe /etc/sv/$service/run needs to be executable?Something similar was reported in alpha 2.
1.1 Remove /etc/service/acpi-support and /etc/service/sudo (they lack a run file)
1.2 For /etc/sv/rsync and /etc/sv/ofono, the run files are not executable, as you have mentioned. Make them executable.
1.3 If you see disk-writes even when the computer should be in idle, install iotop and run
sudo iotop -o
and monitor the services that are writing on disk. This will let you know what services are malfunctioning and constantly reporting errors.2) backlight setting resetting to 100% after boot
Also reported in alpha2. We need to create a backlight service for runit. I will see what I can do and try to send it to anticapitalista if I get it to work.
– add signal-desktop option to messaging apps. probably telegram-desktop too, but that’s already in debian repos.
– add ungoogled-chromium in browsers.If you can create the command instructions, a merge can be requested to packageinstaller-pkglist to be included there, if it is accepted.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.Anonymous
I replied to the points raised by xinomilo.
Is the spamfilter holding my post in purgatory?
- You must be logged in to reply to this topic.
