erikr
-
Posts
81 -
Joined
-
Last visited
-
Days Won
4
Community Answers
-
erikr's post in Nvidia problems after upgrade to 1.2 was marked as the answer
A while ago, around the upgrade, I also had to replace the cpu water cooler and moved my graphics card to the other PCI slot. I now took down the computer and moved it back and things are back to normal.
Don't have a clue why this works but hey, it works.
I have a Asus Prime Z370-P motherboard and a fan-less Pallit GTX 1050 Ti graphics card.
Anyhow, case closed :)
-
erikr's post in KDE Pim 17.12 - Failes to add Dav contacts and calendar was marked as the answer
I think this was crap in the settings. Started a new user and managed to add stuff as expected. Case closed for now :)
-
erikr's post in [Canceled] Only 1/4 of installed memory with EFI-boot was marked as the answer
Well, thanks for the help in this thread. I started to test combinations of my 4 memory modules and found out that something is wrong and it is possible that there is a problem with the motherboard. I have moved on to greener pastures and are now installing on my brand new I7-8700K setup instead. It is fabulous.
After I managed to boot on debian-sources I also had to rebuild webkit-gtk that would actually freeze the computer after 20 minutes. That is what I used to test the memory modules.
Eventually I will return to that motherboard and try to find the problem, it is intended to be a server taking backups. If I decide to trust it.
Regards,
Erik
-
erikr's post in Need help finding a Wifi ticket system was marked as the answer
We gave up and went a completely other way - we are going to put a light switch to the access point and only turn it on when it is supposed to be used. Password to be changed when motivated (i.e. not very often). There will be a light in the switch so one can see if access point is on or not from distance.
The access point will be covered by a box with plexiglass front and wooden sides to avoid being messed with.
All involved are very satisfied by a low tech solution and ready for cover design :)
-
erikr's post in Installation of KDE SC4 was marked as the answer
Some progress.
kde-sunset is not included in the layman list. You have to create an own record, which is fairly simple. The guide can be found here: https://wiki.gentoo.org/wiki/Layman#Adding_custom_overlays
Seems like one have to run:
root # layman -L before layman finds it (before layman -a).
The result is: /etc/layman/overlays/kde-sunset.xml
<?xml version='1.0' encoding='UTF-8'?> <repositories encoding="UTF-8" version="1.1"> <repo priority="50" quality="experimental"> <name>kde-sunset</name> <description>KDE 3 and KDE SC 4 Sunset</description> <homepage>https://gitweb.gentoo.org/proj/kde-sunset.git/</homepage> <source type="git">git://anongit.gentoo.org/proj/kde-sunset.git</source> </repo> </repositories> Then run:
root #layman-updater -R root #layman -L root #layman -a kde-sunset Viola, you will have the KDE SC4 meta-packages back again.
I am building right now but no starting problems so far. Follow the funtoo KDE SC 4 guide: http://www.funtoo.org/KDE_SC_4and things seems to work.
There are some minor problems with some old KDE3 ebuilds in this overlay that causes EIX to produce errors. Seems like it ignores some broken/out of date packages and continues with the ones that works. I have a eix db to search at the end.
