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.
almost nothing works mount dosn't work after login
modprobe dosn't work
link
startx
X -configure
lilo
kill
killall
none of it
the only things I have found that works is midnight commander top ps
well it's time to reinstall slack 11
and waite 6 months till the bugs get fixed
No problems here at all with mounting; Slack 12 works well for me.
Did you add yourself to plugdev, cdrom, audio, video, and whatever other groups you want?
If almost nothing works, that means nearly everything works Did you verify the md5sum of your iso before burning? Slack 12 works excellently for me and for many others.
I am very willing to bet money that the problems does not lie with Slackware....
I have been using Slackware 12 for a few weeks... and compiz fusion with its kde-window-decorator is very unstable!
I randomly got the error : "The application KWD (kde-window-decorator) crashed and caused the signal 11 (SIGSEGV)".
I didn't resolve the issue yet... I'm still trying to fix it!!!
No other problems found yet.
If almost nothing works, that means nearly everything works Did you verify the md5sum of your iso before burning? Slack 12 works excellently for me and for many others.
I am very willing to bet money that the problems does not lie with Slackware....
I used kb3 with verfi to write the install disks (md5 sums check out )
I even reinstalled still can't get X to configure
still cant get links to work in graphics mode
frame buffer isen't working eather
it still boots only 1/2 the time and chocks on the hard drive all the time
well it's back to slack 11
thanks for the offers to help but salck 11 works on this machine so that's what I'll use
Well, I haven't had much trouble with Slackware 12, the second time I installed it, none except had to add the created users to groups, which is a thing that would have to be done anyway. Slackware 11 was a lot more trickier. Did you ever run those commands (such as mount, modprobe, ...) as root, or did you configure the user permissions correctly? Slackware is not one of those "everything automagically permitted for everyone in the name of easiness" distributions of Linux, you should know that already..
By the way, if you do know Slackware 11 works on your machine [well?], why did you ever switch it? And what's more important, why on earth did you take the time to come here and cry out loud, if you never had any intentions of trying to fix the "problems", or at least listen to the tips and help of others? If your decicion was done from the beginning, it was just childish to come here barking at something, which doesn't help anyone.
i would not say Slackware-12 is garbage, i will say the changes from Slack-11 to Slack-12 were a LOT, right now i am sticking with Slackware-11 and am going to install Slack-12 in an extra disk partition to learn on, mostly the networking packages are my problem, with Slack-11 & older i could get by with just a few famalure packages (just enough to get online) and now i also notice almost every thing is selected by default so when i get a little free time i need to go though the CDRom and write down what is just the bare minimum to get networking going with a eth0 nic card, (no modem, no dsl, no bluetooth & no wireless, i do miss the old days of slackware and i really really will miss the 2.4.xx linux kernels because they were light-weight and simple...
i wish there would be a fork of 11 or a slackwareish distro keep develpment going with a 2.4.xx kernel (2.6.xx is ok, just more than i need)...
Originally Posted by rob.rice almost nothing works mount dosn't work after login
modprobe dosn't work
link
startx
X -configure
lilo
kill
killall
none of it
the only things I have found that works is midnight commander top ps
well it's time to reinstall slack 11
and waite 6 months till the bugs get fixed
Consider your error report and fact that all of it works for everyone else your bugs might never get fixed, if there is any.
Quote:
Originally Posted by XavierP
If almost nothing works, that means nearly everything works Did you verify the md5sum of your iso before burning? Slack 12 works excellently for me and for many others.
I am very willing to bet money that the problems does not lie with Slackware....
Agreed with XavierP, I don't think that this is Slackware problem, but if there is a bug you should really point it with some error messages, otherwise it's just pointless waste of time.
Not here to bash, just sounds like a case of USER to me
Maybe the connection between the keyboard and the chair got unplugged? I'd check that again :P
I do agree with the above posted statements. Very childish to post something knowing full well you don't even care to fix it. everyone here has better things to do than try to help the not willing. I think you are probably just overly frustrated and should repost when you've calmed down and give all the details.
p.s. that first comment was post entirely just for fun and not to bash, i poke fun at my own users at work with this comment sometimes HAPPY FRIDAY!
It is not my main default system yet but I just added slapt-get and suggestions from the Slack 12 HAL thread for the easiest Slackware ever.
I can believe there can be issues but it is not "garbage".
You've got a nice processor:-) I'm running Slack 12 on a Plll 800 with 768 MB of RAM. I only set aside an 800 MB swap file. With the extra RAM my unit never goes into swap.
Ever considered a RAM upgrade?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.