Noticed a problem with the nm-applet in the Antergos Openbox version, both in the live minimal and the fully installed environment.
When I click on a WiFi AP, it just tries to connect, and fails, and doesn’t prompt for a WPA password. Trying to edit the entry in Network Connections applet doesn’t help, because the WiFi Security tab isn’t there. Only way I was able to connect was to select “Connect to Hidden WiFi Network” and manually enter SSID and WPA password. After that it connects fine and I can see the entry with WiFi Security tab and password in Network Connections.
I also tried the full Antergos Gnome Live version, and that works properly, every time I tried it. I’ve never noticed any problem with other Linux distros not prompting for Wifi password with this laptop with RAL RT5390 chipset.
Any others noticed this issue?
- Only 2-4 among millions Antergos users have Grub4DOS, Grub Legacy, Syslinux as their bootloader. Does it worth to change smth in existing installer for them? Probably not. If a person is capable to manipulate boot loaders by hand, for him|her it’s enough to know about resize -s trick. Maybe write an article in Antergos Wiki about it.
+1 for that.
Progress marches on… Seems like the end of the 32-bit era is here. With Arch going EOL on i686, and after May 2016 mke2fs defaulting to 64bit, I would expect most all newer Linux distros 2017 and beyond will be doing the 64bit Ext4.
I’m an old dog using old tricks. When my old Core2 era and early Corei7 BIOS systems start to die out, then I’ll be forced to use Grub2 on new UEFI PCs. Until then, at least I’ll know the old trick to still use Grub4DOS/Syslinux with 32bit Ext4!
I like the Antergos Openbox very much, very slick, nice visuals and functional dock. This is a good alternative to ArchBang which I had been using before as a minimal Arch laptop installer.
Everything worked out of the box from the single CD installer image, with a few hiccups during install (self inflicted)
One issue was the very slow login/password dialog box on the lightdm. Each character entered was delayed half a second. I replaced lightdm-webkit2-greeter with the standard lightdm-gtk-greeter and no more slowness.
Glad I could help track it down!
I was just looking at the before/after of the fsarchiver workaround you revealed, reverted back again in VBox, and noticed the tune2fs output showed the 64bit feature difference.
So after some looking around, tried the change and it worked. Then I later found the Syslinux document which confirmed the 64bit feature as the culprit.
And yeah, unfortunately the cnchi required the format before proceeding, that’s how this whole problem was revealed. I normally prepare all the partitions myself before any Linux installer mucks around with my drives.
The resize2fs -s change is pretty quick and painless, couple seconds. I guess I need to update all my rescue disks with latest 1.43 version e2fsprogs. Had Ubuntu 16.04 LTS and various Puppy Linux also installed on the box, and none of them had the updated resize2fs with the 64bit feature.
I guess this is a bug or feature request:
Installing Antergos in a multiboot system and not selecting the bootloader install option, because I am using my own bootloader/partition, resulted in a non-bootable system.
Scenario: MBR system and installing Antergos into single logical partition /dev/sda7.
The installer marked the /dev/sda7 as active/bootable, which is invalid, resulting in the system being unable to boot, until I went in with rescue disk and restored boot flag to the primary partition that had the boot flag prior to install.
Again, I don’t need help with this and have repaired the system, just reporting what I encountered during install.
OK, I figured out what the problem was. Verified Antergos installed and booting fine now with Grub4DOS on real hardware.
The Antergos installer is creating an Ext4 filesystem with the 64bit feature turned on. This makes it incompatible with booting from Grub1/Legacy, Grub4DOS and even Syslinux.
To fix this, you can remove the 64bit feature from Ext4 after the fact, with the new resize2fs “-s” option, e.g.:
resize2fs -s /dev/sda7
Needs to be a newer resize2fs version as many of the ones I had on other distros and rescue disks could not do it, so I used the one from Antergos Live.
Or they could change the installer to do mke2fs -O ^64bit without the (unneeded?) 64bit option.
I didn’t even know about this option, just found out about it after troubleshooting the fix above. I also installed Syslinux on the PBR and can either direct boot from Grub4DOS or chainload into Syslinux to boot the Antergos partition.
Thanks for the reply.
Yep, that’s the issue. Same problem booting with Grub4DOS as it is similar to Grub1/Legacy I guess.
I tried your trick on the VBox install of Antergos, and it worked! Very strange, I wonder what the Antergos GUI install is doing to the Ext4 filesystem to make it incompatible with Grub4DOS/Grub1?
I’ll try on the other machine on a real partition tomorrow. I had already uninstalled Antergos and restored the partition with partclone. And you’re right, only fsarchiver worked for this fix. I tried with partclone first and it did not work.
I don’t ever notice this problem before with the typical Ubuntu, Fedora or other distros. Or, as you detailed in your post, plain vanilla Arch.
I was just looking at Antergos as another way to get Arch installed. I’m so over the lame “Arch way” of plain vanilla. Right now if I install Arch, I use either of the text based installers, with ArchBoot ISO, or ArchBang is even easier and uses similar text installer.
Problem booting new Antergos installation. Getting the following error on the kernel line:
Error 13: Invalid or unsupported executable format
Always have booted various linux distros from a common bootloader on main partition with a Grub4DOS config. On this particular machine, Antergos (installed without bootloader) was taking the place of a running ArchBang install using the same booting method. I also use this method on other machines with plain vanilla Arch with no problems, either direct boot or chainload into syslinux/grub on the PBS.
I also duplicated the problem in a VirtualBox VM. But here I let the Antergos install its own grub to MBR, which did boot properly. But still could not direct boot it from the Grub4DOS partition.
Is there something different about the Antergos kernel/compression or something special about the grub2 version compared to Arch? Will the current installation method produce something not compatible with Grub4DOS booting?