You know what? I've secretly given KDE4 a second chance. After playing with it for a few hours, I learned how to make it behave the way I want, and let me be the first to say it: You're right.

There's really not much more to say than Slackware 13.1 is the best release yet.

You guys rock.

Hi guys. Unfortunately I can´t get it running well.

I have used the 11.0 and currently the 12.2 version and all works perfect, extremely perfect. But when I go with "startx" (the installation of the 13.1 looks work fine), the kde begins to load and suddenly all stops and the system crash (the same thing happens with the 13.0 version). I have and old (not so much) pc.

I know this is not the forum for looking help, but, I just want to enjoy like you the 13.1 version.

PD: I´m still learnig english, so any mistake, please let me know it.

My impression of 13.1 is not good.

On my dual scren PC. I have problem with random freeze when xscreensaver runs. The mouse pointer just like vibrating between the two edge of the screen. Tried compiling fluxbox and new xscreensaver without avail.

On my laptop. It breaks the i915 driver. I noticed that it uses KMS now. But still, it doesn't work with that annoying "no kernel modesetting module not found error".

Everything were working great with 13.0. Downgrading~

Hi,

Which kernel are you using on Slackware 13.1?

@onebuck
I tried the huge.smp kernel and kernel that i compiled myself with KMS enabled by default (framebuffer disabled and no vga= argument on lilo.conf). Then i tried downgrading to version 2.9.1 of xf86-video-intel. Works, but X just freeze (no keyboard and mouse respond) after the desktop appear without any (EE) message on Xorg.0.log.

Hi,

I would use the 'generic' kernel for daily use instead of the installer kernel. Try that then custom to suit if necessary.

A bit late, but I finally installed 13.1, seems to work just fine, despite problems reported by others. Good job.

I'll be installing it in the next week or so.

I always wait a while before upgrading. Partly to read about the experiences of the early adopters, but also because I'm usually in the middle of something and upgrading from a perfectly stable, usable Slackware version to the next is usually not a high priority.



Regards,

Well. I usually compile my own kernel.

I finally installed 13.1 yesterday. In fact this is my first encounter with the kde4 series and I have to admit that the system doesn't seem bloated at all – on the contrary... I'm even surprised at the general speed and responsiveness even with the desktop effects enabled.
Everything was working "out of the box", the most pleasant surprise being xorg.conf-less autoconfiguration.
Also, the installation of packages seem to be much faster than 12.* series (or at least 12.1 with Openbox (!), which I was using before).
As always, great job from Pat and the Slackware team. Keep up the excellent work!

I have been a Debian guy for a while, and all I can see is, I didn't know what I was missing. I always thought dependency checking was a must, but I was wrong. In the Debian days, I would use aptitude and install a program, dozens if not hundreds of dependencies would be installed. I thought on a different Linux distro I would have to install hundreds of dependencies for every program. However, I just go to slackbuilds.org and search for a program, at most I have had to install a couple of dependencies. And best of all, most all of the slackbuilds compile the software, what a nice feature.

For the most part I like Slackware 13.1. The main reason for me upgrading were the package updates and additions (eg. Qt 4.6.2, etc.). I'm an xfce user and I like the simplicity of it. However, the one annoyance I keep on getting on regular basis is the KDE Crash Handler keeps on popping up when there is a notification displayed. For example, when I change the volume, it almost always pops up. I tried upgrading to KDE 4.4.5 and that didn't do anything.

The only thing that has dissapointed me in Slackware 13.1 is the lack of functionality on systems with i810 graphics. I realize this is due to upstream changes, but, it really sucks that I can't seem to get it to work right. XOrg in Slack 12.2 is becoming too old for some tasks, and I'm not compiling a new version on a Pentium 3. Maybe the next Slack won't be unlucky.

I have tried both 13.1 Slackware distributions 32/64bit and I have trouble with Ralink rt2500 driver. The driver loads ok, I have a connection, but is very, very SLOW (around 10ko instead of before 1.5Mo)... Same machine was used before with slackware 11 and a generic kernel 2.6.20 with generic drivers from serialmonkey (old STA driver with a config file in /etc for WPA).
Today I have no third party driver to compile in the internal or generic kernel and the kernel driver for RT2500 is not usable: many packet loss, random ping (speed over 1 hop - my wireless route) from 10 ms to 1000ms.
Setting and forcing rate to 54M not helping.
Still trying ...but unhappy, even if I appreciate this distribution very much.

Hi,

Welcome to LQ!

You should create a new thread to hopefully get things going. You will get more exposure plus the continuity of the thread will insure that things don't become convoluted. Be sure to include clear information along with details. Most members will aid you when you help yourself to a solution. Provide us with what you have attempted and then maybe someone will be able to assist.

I suggest 'How to Ask Questions the Smart Way' would be one link you should look at to help us to help you in the future.