Language Selection

English French German Italian Portuguese Spanish

Some things that bother me on open source/free software

Filed under
OSS

First I have to say i’m happy with openSUSE 11.0 (It’s best openSUSE ever). After that I have say then comes hardware problems on shiny new HP Proliant DL385GS (4 core AMD CPU).

Everything start on sunny day i’m happy installing openSUSE 11.0 from x84_86 DVD. Everything goes fine and smooth. Then I set up LTSP5 and it goes excelent (remember to remove pulseaudio from server to make it work wirth audio). Users starts to use LTSP5 and suddenly everything doesn’t go fine anymore. Machine crashes everytime they start to do something else than just login (open firefox crash, listen music crash or watch youtube guess what crash). Client keeps itself up but server goes down fast. No kernel panic nothing (Nothing on /var/log/message nor in dmesg)!

I called to HP just to hear awful news. openSUSE is not supported. Okay I understand they can’t support every distro on earth but Novell ain’t small player, openSUSE is quit popular. We can use SLES (this is not about money) but it’s too ancient for us. So we choose suffering!

More Here




More in Tux Machines

Android/ChromeOS/Google Leftovers

Games: SC-Controller 0.4.2, Campo Santo, Last Epoch and More

Android Leftovers

Ryzen 7 2700X CPUFreq Scaling Governor Benchmarks On Ubuntu Linux

With this week's Ryzen 5 2600X + Ryzen 7 2700X benchmarks some thought the CPUFreq scaling driver or rather its governors may have been limiting the performance of these Zen+ CPUs, so I ran some additional benchmarks this weekend. Those launch-day Ryzen 5 2600X / Ryzen 7 2700X Ubuntu Linux benchmarks were using the "performance" governor, but some have alleged that the performance governor may now actually hurt AMD systems... Ondemand, of course, is the default CPUFreq governor on Ubuntu and most other Linux distributions. Some also have said the "schedutil" governor that makes use of the kernel's scheduler utilization data may do better on AMD. So I ran some extra benchmarks while changing between CPUFreq's ondemand (default), performance (normally the best for performance, and what was used in our CPU tests), schedutil (the newest option), and powersave (if you really just care about conserving power). Read more