AMD Threadripper / AMD Epyc/ AMD Ryzen/ AMD Radeon Pro
3 Attachment(s)
How you mean make for new amd64: AMD Threadripper / AMD Epyc/ AMD Ryzen/ AMD Radeon Pro ?
Attachment 34152Attachment 34151 Support links: https://amd.com https://www.amd.com/ru/processors/ry...readripper-pro https://youtu.be/rQj4PJvPFeU https://youtu.be/Imnyhc_V3rA http://www.slackware.com/~msimons/slackware/grfx/ Attachment 34154 Wanted Linux kernel.org 5.8 ... or later ? |
I am among those who hope for a Slackware 15 soon. But I realize that there is a lot that goes into making a stable distribution that is "current" enough for ordinary users and "stable" enough to be a reliable go-to linux. The strategy I am adopting is to stop updating slackware64_current as of now. I have everything I want and it all works. If there is some crisis in Firefox or some other package that requires upgrading I will hopefully find out about it and be able to upgrade only that package. Maybe in six months or so I will want to upgrade everything again, but I am going to try and restrain myself, since I am in no way a beta tester.
I switched to current because I needed new hardware drivers in the new kernels and some newer program versions. I think the single most important hardware need is for the new AMD ryzen processors and graphics. That seems to be pretty well handled now. I also think it should be made clear to users that the mozjs packages need to be handled with removepkg and install-new. That can be a show-stopper since your computer just doesn't work right if you mess that up. |
|
Even Kubuntu devs do not like Akonadi and KDE-Pim
3 Attachment(s)
Just pissing in the wind with this post/request but screw it - when Plasma5 is FINALLY included - can it be without KDE-Pim and Akonadi? After playing with Kubuntu further (fresh install) , I checked and noticed that Akonadi and KDE-Pim were actually not installed by default *shrug*; and the mem usage via htop makes me happy about it too... So I now have another vote for Plasma5 in my book :)
|
Quote:
Just because they aren't installed by default in Ubuntu, that's NOT that they are removed from Ubuntu's repositories... Anyway, I do not this apply even remotely to Slackware, because here we should install everything or we risk to be excommunicated. |
Quote:
|
Quote:
|
Quote:
|
Quote:
The elogind works just fine, because the today software expects a valid login1 API. No roadblocks there. Quote:
Hear my words, we will hang there in the year 2025 and we will talk about the "roadblocks" of adding Plasma6 to Slackware. While Slackware-current will still have KDE4, and there will be still hopes that 15.0 will be released in the near future, to celebrate 10 years of development. |
Quote:
chris |
Quote:
Anyway...Oh well. Let's leave it at that. :rolleyes: |
Quote:
Code:
# slackpkg install-new I guess a third point is in order, READ, ChangeLog.txt before doing an update. This avoids most show stoppers. |
Quote:
solved the problem: Some parts of "nouveau" are missing, so there was no hw-acceleration anymore ... At this occasion I tried the proprietary nvidia-driver (450.66), that worked with X but when going back to runlevel 3 there was no signal for the monitor! Just a "black screen" with no chance to get back a screen! rebooting over ssh and removing that driver "solved" that self-made problem |
|
Quote:
Quote:
Q. Hello roadside assist, my new Slackware model does not go. Can you help? A. Does the engine go? Q. Yes. What do I try next? A. Does the engine rev when you press the accelerator? Q. Yes. What do I try next? A. Is the car in gear? Q. Yes. What do I try next? A. Then it should be going. Have you made any mods? Q. I wanted a low profile look and took the wheels off. Would that make a difference? |
All times are GMT -5. The time now is 11:44 PM. |