SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It should be smooth, you shouldn't encounter problems, it's pretty stable - as stable as some other distros' actual "stable". However, unless you are prepared to encounter the occasional problem and fix it yourself and pass the fixes upstream, I wouldn't recommend it. IOW, if you want to contribute to Slack by testing and improving -current, go for it. If you just want to have the latest packages and will be surprised and just complain if anything breaks, then you should stick to 13.1.
(Note, I'm not making any assumption that you match either description - just talking about principles. )
The most common "problem" I experience is when I need a new piece of software and the Slackbuild fails. This is usually easy enough to fix with a version bump and a small edit to foo.slackbuild. Sometimes that isn't the case. I'm not saying it happens everytime, but it isn't uncommon and at this particular stage in -current it's probably a little more likely due to recent updates. In general I consider it smooth and consider it my insignificant opportunity to contribute to the future of Slackware, mostly I do it just for fun.
My home server doesn't follow current and my laptop which I need to just work doesn't either, but my main workstation/desktop does.
Upgrading now. Keeping my fingers crossed; I'm about halfway through and I just noticed that Jack isn't working. Hope that goes away once the process is complete...
Okay... I'm not one of the lucky ones, I guess. I finished the upgrade, rebooted, and it gets right up to the part where it's supposed to launch the KDE login screen, some messages fly past faster than I can follow, and it stops on a black screen with a flashing cursor at the top. Won't accept any kind of input, although along with the flashing cursor there's also a white rectangular cursor-type object that moves around with the mouse. Help! Is there any way I can get into a console and maybe figure out what's wrong?
I'm considering upgrading my 13.1 box to current. Is the upgrade usually smooth, or can I expect problems? Also, how stable is current?
Failed here to get usable X with "VGA compatible controller: nVidia Corporation NV44 [GeForce 6200 TurboCache(TM)] (rev a1)" which is a 256 MB PC-Express card (got X with a frozen mouse)
Strange is that xorgsetup failed (scrolled away).
Tried than the followings:
1.) without an xorg.conf
2.) with xorg.conf (edited by hand):
2/a.) "nv" driver
2/b.)"vesa" driver
Suspected that "nouveau" is causing the problems, blacklisted and tried 1., 2/a, 2/b with the same result.
(What I did not try was installing the proprietary driver.)
At last I downgraded do Slackware 12.2 where ewerything works for me, I am fine now (13.0 and 13.1 worked, but missed KDE-3.5 sooo much . Will wait with upgrading the system until the next hardware upgrade.
Okay... I'm not one of the lucky ones, I guess. I finished the upgrade, rebooted, and it gets right up to the part where it's supposed to launch the KDE login screen, some messages fly past faster than I can follow, and it stops on a black screen with a flashing cursor at the top. Won't accept any kind of input, although along with the flashing cursor there's also a white rectangular cursor-type object that moves around with the mouse. Help! Is there any way I can get into a console and maybe figure out what's wrong?
Have you tried ctrl-alt-f1? You can also append boot parameters to lilo I believe to boot into runlevel 3 rather than 4.
This is why I don't generally boot into runlevel4.
Do you have nvidia's driver installed? If so, you will have to boot to init 3 and uninstall it, then install it again. I've certainly done that before. Kernel upgraded, then forget about the nvidia driver.
press ESC, and then select your Linux entry and add 3 after the prompt (dont forget the space)
So, if your label is Linux, it will be like Linux 3 and then press ENTER
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.