Hi,
after a try with Calculate Linux (promising but lacking LUKS install), I decided to give Artix another try.
I took the last iso (feb 2018).
Bravo !
It installed PERFECTLY with LUKS out of the box. Wow, what an improvment !
No trouble to install PAMAC.
Then installing Plasma worked smoothly.
(I just noticed a small quirk, by installing Beyond compare/AUR it had a dependancy on package qt4, and Artix comes with qt5 only, but impossible to find qt4 using search tool in pamac. I finally succeeded installing qt4 package by installing a non-AUR package that depends on it.).
So far this is close to what I need, I may decide to swith to Artix & get rid of systemd soon.
Thanks a lot guys for your hard work.
(obviously, on top of a "thank you", I will donate)
Bravo ;-)
In pamac QT4 is obtained by ticking any of the top 4 QT4 packages i.e. QT4 Linguist, QT4 QdBusViewer, QT4 Designer and QT4 Assistant confusing I know but in pacman "sudo pacman -S qt4" works
do you know or understand why it is not visible ?
Probably you don't have the "extra" repo enabled as they are in that one
I did update (laptop not opened for 4 weeks)
And now : no more network, Network manager refuses to start, even on ethernet.
;-(
Hello, you can find similar threads on the forum:
https://forum.artixlinux.org/index.php/topic,476.0.html (https://forum.artixlinux.org/index.php/topic,476.0.html)
Thanks !
Let's try downgrade
downgrading networkmanager with the version in cache did the trick.
thanks.
Hi guys, I just decided to move from Antergos, because the install on my spare laptop seems stable.
Artix + Plasma, it works!
btw, my Plasma settings copied from Antergos solved some issues (mainly: the annoying message "The screen locker is broken and unlocking is not possible anymore" - unlock-sessions problem)
But it also slowed it down a lot, especially Dolphin.
I'll have to find out someday.
I just made my small donation, very funny greeting message guys !
:D
(https://i.imgur.com/jzTjIO3.png)
https://imgur.com/a/2WobC
One word of caution for pamac. If you're using any DKMS drivers, (virtualbox, nvidia, etc) you'll want to do those updates from pacman &/or yaourt. pamac doesn't seem to re-run dkms when the updates are done so you'll either have to run it after pamac is finished or upon reboot. In the case of Nvidia getting updated, you'll definitely not want to have to deal with that reboot if the driver isn't recompiled before the reboot.
Sure about that? I use no nvidia, it is a waste of time with Linux. But Virtualbox.
I'll double check that.
Thanks
In regards to pamac, from what I was told in another thread discussing Nvidia issues, that was what was expressed. If I do updates with pamac, dkms is not run and on the reboot I have a console login flashing as fast as it can to deal with. If I update with pacman instead I don't have the same issue so I consider it accurate information that was given to me.
In regards to Nvidia, Nvidia performance over Intel is working well for me on one machine as well as ATI vs Intel on another so I guess it's whatever you're doing on your Linux machine dictates if it's worth it or not. I do a lot of graphic intensive operations and the Intel card can't handle it so I guess that's why it works out better for me.
Sure.
Except Intel Iris, which is quite good (used in mac) even on a 4K display. but I am a developer so it is enough/perfect for me. And I use external displays everyday, where nvidia sucks.
btw, it is really simpler doing pacman -Syyuu or -Suy in the command line: you have a good progress report.
So in fact I will never have the problem.
Thanks
Not sure what you mean by it sucking on external monitors either but ok :) To each his own. I'm running Artix on a Dell Precision 7510 with 3 external monitors and the laptop display and get great performance on all 4 screens using Nvidia.
I mean, you may need to reboot to plug them, the nouveau/bumblebee nightmare hardly works out of the box.
it is not plug and play as it should be.
Don't know whats going on with you too, you seem to be taking this to much to heart.
Not at all. Just general conversation about different experiences ;D
Right. I am just happy I can start using Kde Plasma on Artix - it will become a good systemd free Arch.
I was a happy user of Manjaro OpenRC.
and I think Obarun may be taking the wrong path.
Regarding nvidia, I did sold my laptop to get rid of this mess. And found a good laptop with a matte display & intel iris card (& ssd & 16gb ram). It is hard to find a nvidia free laptop nowadays.
@psy0nic - I finally tried to install Virtualbox.
The problem is I am using kernel 4.14.31-1-lts. because LTS is more stable when using Docker.
There exists a package
virtualbox-host-modules-artix 5.2.8-10 that depends on kernel 4.15.
and when I try to rebuild dkms module in /usr/src/vboxhost-5.2.8_OSE I got this :
=== Building 'vboxdrv' module ===
make[1]: Entering directory '/usr/src/vboxhost-5.2.8_OSE/vboxdrv'
make V= CONFIG_MODULE_SIG= -C /lib/modules/4.14.31-1-lts/build SUBDIRS=/usr/src/vboxhost-5.2.8_OSE/vboxdrv SRCROOT=/usr/src/vboxhost-5.2.8_OSE/vboxdrv -j4 modules
make[2]: Entering directory '/usr/lib/modules/4.14.31-1-lts/build'
make[2]: *** No rule to make target 'modules'. Stop.
make[2]: Leaving directory '/usr/lib/modules/4.14.31-1-lts/build'
make[1]: *** [/usr/src/vboxhost-5.2.8_OSE/vboxdrv/Makefile.include.footer:101: vboxdrv] Error 2
make[1]: Leaving directory '/usr/src/vboxhost-5.2.8_OSE/vboxdrv'
make: *** [Makefile:49: all] Error 2
Indeed '/usr/lib/modules/4.14.31-1-lts/build' has no Makefile.
it seems the LTS package does not come with the build env?
@psy0nic what did you mean by "rereuning dkms"?
If DKMS didn't run during your update via whatever you're using to do your updates, you can re-run it manually to have it recompile your DKMS driver packages by running:
sudo dkms autoinstall
You can chose individual drivers if you want but doing autoinstall is what I do because it does all the registered DKMS modules it finds are appropriate to recompile against a new kernel or to update the module because of a driver update.
Thanks.
but I think it will not work because the LTS folder doesn't have the build files:
$ find /usr/lib/modules/4.14.31-1-lts/build
/usr/lib/modules/4.14.31-1-lts/build
/usr/lib/modules/4.14.31-1-lts/build/vmlinux
There should be a makefile etc...
Do you have the kernel headers installed?
$ sudo find / -iname build
/usr/lib/modules/4.15.14-1-ARTIX/build
/usr/lib/modules/4.15.14-1-ARTIX/build/include/config/build
/usr/lib/modules/4.14.32-1-lts/build
/usr/lib/modules/4.14.32-1-lts/build/include/config/build
ls /usr/lib/modules/4.14.32-1-lts/build/
arch crypto include kernel mm samples sound virt
block drivers init lib Module.symvers scripts tools vmlinux
certs fs Kconfig Makefile net security usr
oops !
I thought, but they were not.
(linux-lts-headers 4.14.32-1 to be installed)
Thanks
Virtualbox now works perfectly