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.
Distribution: SlackWare 10.1+, FreeBSD 4.4-5.2, Amiga 1.3,2.1,3.1, Windors XP Pro (makes a fair answering machine)
Posts: 287
Rep:
Problems with Slackware 10.0
I am seeing lots of post about many different issues with Slack 10.0.
Having not read any yet as I have no problems with Slack 10 yet I have a question or two..
1) Are these virgin installs or are they upgrades ?
reason: I have done a virgin install of slack 10 for my hubby on his dual, now tri boot 1ghz Dell box.
The install went flawless on a partition under 3gig hd space w/kde. So far there has not been one issue. Alsa configured during the install (new thing, no asking). Xorg launched default then I tweaked it to the box.
Set-up samba for client mode and nfs. So far so good. He is enjoyin' himself...
2) If upgrades, how?
a) swaret?
b) package upgrade?
c) delete re-install?
IMO I would opt for delete re-install for my machines...
Also I would suggest that after you do an upgrade without swaret I would still do a swaret --dep and see if any libs or files need a fix... This may solve some of the issues here by fixin broke depends.
I believe a virgin install would be the best of all....
So now I will start my upgrades and report more later...
No problems upgrading from 9.1 to 10.0 via swaret here... but I exclude my kernel and alsa in swaret... most painless update of a distro ever for me...
(1) Old P120 classic laptop. Smooth install, no problems, works great, and has even sound (didn't with Slack 9.x). Only thing not perfect, but not annoying, at all: Shutdown doesn't switch the machine off. (Screen goes black, harddiscs stop, just the power LED is still on, so I have to push the power button). I use kernel 2.4.26 on this one. Maybe 2.6.7 would shutdown properly, but as everything else works so fine, I tend not to take the risc of touching a running system... ;-)
(2) Modern desktop (Athlon XP, ATI Radeon etc.). Minor sound problems caused by the fact that I have two sound devices in that machine, onboard sound and PCI card. When I do alsaconf for the latter, it works great, as long as I keep it busy. Once sound stops for a while, Slack 10 / ALSA forgets about this card, despite alsactl store. From that moment on the onboard sound is used by ALSA. So I have sound, but not always quite the way I want it... Apart from this minor issue, Slackware 10 gives me no headache, at all, so far. I use Kernel 2.6.7 on this one.
I'm not sure about everybody else; I installed fresh with Slack 10 all except for the fact I kept my /home part as it was. I didn't have any problems except for the fact that when I startx I would get some annoying XKB errors at start up. Those were pretty easy to fix though. Install went perfectly. I have the Windows XP loader booting slack with some dd and boot.ini changes. For the first time I have sound events working in Gnome right out of the box (Which, incidently, made me jump out of my skin when I started X and GnomeICU announced [screamed] USER ONLINE!!! at fullblast out of speakers less than 2 feet from my head).
The only problem I have that remains to be solved (It's minor again) seems to be with the vesa console. Mustn't like my nvidia card cause when I quit X back to console the entire thing is garbled. I just see different coloured dots all over the place. Input works fine though, and changing lilo back to vga=normal fixed it. Just doesn't look as pretty anymore hehe So I need to figure out how to fix that. But Slack itself isn't at fault.
I've never used Swaret or Slapt-get to upgrade, infact, I don't usually upgrade anyway. I've been frightened away from whole system upgrades since Windows. No matter what you did it always seems that a Windows upgrade was never a perfect one. it left old junk all over the place. So I prefer just to format and reinstall, keeping my /home, just to make sure the it's all installed fresh and clean. I suppose you needn't worry about that with Linux, but I still don't trust upgrades, there are too many variables.
(1) Old P120 classic laptop. Smooth install, no problems, works great, and has even sound (didn't with Slack 9.x). Only thing not perfect, but not annoying, at all: Shutdown doesn't switch the machine off. (Screen goes black, harddiscs stop, just the power LED is still on, so I have to push the power button). I use kernel 2.4.26 on this one. Maybe 2.6.7 would shutdown properly, but as everything else works so fine, I tend not to take the risc of touching a running system... ;-)
you have to uncomment the "apm" -line in /etc/rc.d/rc.modules
Itīs somewhere in there. Search it, find it, remove the comment ( # ) infront of the line and your laptop should poweroff by itself everytime you do a shutdown
edit lilo.conf and comment out the line that says vga=7** ? or some number
and replace it with vga=normal, or at boot type: Linux (or what ever you named it) vga=normal
and no more garbage until nvidia release new drivers.
I had no problems, but I always stay sync'd with current, so upgrading from my current installation to 10.0 was just a matter of downloading and upgrading a few packages.
I always update semi-manually. I examine the ChangeLog and then usually use slapt-get to download and upgrade packages.
Tools like slapt-get and swaret are great conveniences for staying -current, but they are not a replacement for reading the ChangeLog.
i cant get sound working. and my mouse isn't working right. i have no scroll. other than those issues i also need to get my second monitor running. i dont want to use twinview because it screws up UT2k4.
for sound, you want to try running alsaconf
It'll usually set you right up.
After that, run alsamixer and adjust master, pcm, igain, and whatever else looks relevant to about 90%. Use "m" to unmute channels that say off.
About your mousewheel -- Do a search
Notice, you shouldn't consider these problems. They're just a couple of configuration issues -- things you haven't had to do in Fedora
For sound, try running 'alsaconf' as root. Also, make sure that your sound channels are unmuted. Run 'alsamixer' and make sure to unmute Master, PCM, and anything else that looks relevant.
As for the scroll wheel, I can't see your xorg.conf (I get a 404 not found error), but just add:
you have to uncomment the "apm" -line in /etc/rc.d/rc.modules
Itīs somewhere in there. Search it, find it, remove the comment ( # ) infront of the line and your laptop should poweroff by itself everytime you do a shutdown
Thanks! That was it! Now Slackware is running just PERFECT on my little old notebook! Not even a single minor problem left --- EVERYTHING works, NOTHING is imperfect or missing!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.