not so impressed
 

I've tried to install Slack before, but I finally succeeded in installing 10.2. The problem is, it freezes. A lot. And its really, really slow. And the version of firefox is like...1.0.6 or something (which crashes a lot). I downloaded the newest firefox, unpacked the tar, cd'd to the directory, tried a ./configure, and I got an error message, stating it couldn't.

I don't know if my best bet is to try install 11 or what. When I tried to install 12 before, 1 kernel kept my mouse from working, and the other one I tried kept the keyboard from working. (so, is there possibly a way to install all the kernels and see which one works?)

If you describe your hardware and give some info on the error messages you're getting when trying to install stuff, it might be easier to figure out what the best course of action is...
Slackware is my primary system, so far it worked great. :)

Hi,

As U_T stated, we need a little more information. Error messages, hardware information and what kernel you were attempting to use.

Where did you get the Slackware install?

If you downloaded the cd/dvd iso then be sure to check the md5sum for the original iso. From the cli;

If the iso md5 is ok then you should try 'CdromMd5sumsAfterBurning''.

This way you will know if the burn was OK!

This will check the download iso with the known md5sum that you also get with the iso.

You could do a ftp install using the 'lmo-install-0.2.iso', it took about 2 hours for me on DSL for Slackware 12.

These links and others can be found at 'Slackware-Links' .

I mostly agree with the above, but have to mention that in the past I did have trouble with Slackware that never cleared before I just switched to another distribution, or rather, put Slackware on another computer instead and used another distribution on that "troublesome" computer. The problem was a usb-connected wireless unit to which both wireless keyboard and mouse were (wirelessly) connected to; keyboard worked well, and mouse otherwise except that scroll wheel didn't. I don't remember which protocol setting I used (maybe IMPS/2?) that worked, but all others made the mouse stop moving, or in good cases only move up/down, or with any button pressed, to right with tics. Not sure what it was, but after a long trying period I gave up, installed Debian-based distribution and the wheel worked out of the box - with the very same settings that Slackware refused to wheel-scroll with :)

Mentioned that just to say that not everything is clear. I asked about the problem in a lot of places, and though I got good ideas and advices, none of them worked - wireless mouse and Slackware just weren't the best friends.

But if you do have a regular cable-connected mouse (and maybe even if you didn't), it's probably just a configuration setting or something as easy as that, so post errors if you can, to help solving it.

The kernel is simply the default 2.4 kernel that the live install cd for slack 10.2 uses.

I have a Celeron D 3.33GHz processor, 80gig hard drive, and 1 Gb of RAM. Neither my mouse or keyboard are USB. The install CDs are fine. Md5sums check out.

Hi,
You did check the new cd with the original iso md5?

Don't rely on your md5 checking with the burn application.

I've got a M$ wireless on several Slackware machines. No setup problems at all. For the mouse configuration use the 'IMPS2' for the 'Wireless Notebook optical mouse 3000'. That's the cheapest M$ wireless mouse in my area.

When you downloaded firefox did you actually download the source? The tar file you get from mozilla is just a binary so ./configure isn't available or necessary. If you install 10.2 then a lot of your packages will be way out of date. You can find the newest 10.2 firefox package (firefox 2.0.0.11) at ftp://ftp.slackware.com/pub/slackwar....11-i686-1.tgz. Updated packages are also available for other Slackware versions on that site as well.

On 10.2, please check your logs (under /var/log/: messages, syslog, Xorg.*.log) and let us know what errors you get. You don't need to post the entire logs. Also, can you describe your environment a little more. What Window Manager/DE are you using? Did you set up X properly after you installed slackware? You need to either run xorgconfig or manually modify your xorg.conf file.


That is really strange that the Slackware 12 huge kernel didn't pick up a PS/2 mouse and keyboard. Did you enter any boot parameters during that install attempt? You said you tried more than one kernel. Which ones did you try?

It could very well be that you will have to create a custom kernel for your setup. If that is the case I would start from the kernel that your keyboard works on as you don't really need a mouse to do system admin.

If you haven't already done so, I encourage you to read the Slackbook. Not only is it a great manual on Slackware, but you might also learn a new thing or two about Linux as well.

Ok, 1st of all, try ALL kernel available for slackware 12 one after another and find which on is more or less funtional. Slackware assumes
quite intence reading around. Go into your CD with slackware and read
docs. Slackbook as well is a good start point. Don't mess with older
Slackware distributions. Figure out what are interfaces you have in your machine (ATA/SATA/SCSI etc.); videocard (ATI/NVIDIA). Make your mouse
and keyboard workable at 1st.

Hi,

Good advise for the kernel selection if you want to waste some time. For Slackware 12 you should attempt to use the generic-smp kernel for use. For install select the huge-smp.s even if you don't have smp.

Did you read the Slackware 12.0 CHANGES_AND_HINTS.TXT, UPGRADE.TXT and RELEASE_NOTES?

Reading the docs is a far reach for a newbie. Heck, it's hard to get them to read online reference.

Why the 'Don't mess with older Slackware distributions.' statement? There are times on legacy hardware you cannot always use the newest and greatest GNU/Linux distribution on older hardware. Rolling back to earlier versions can be the only way to get support for some hardware.

Yes, everyone should attempt or know what hardware they are installing too. Get your system documentation, equipment specification docs and all other relative information. Lot of times the newbie doesn't know hardware specifics and doesn't know how to get them. For a GNU/Linux a simple 'lspci -vv' will provide your with device information. You can use just about any LiveCD or the install cd of a distribution to find this out.

Too many people run into problems not knowing where they are going or where they've been for a install. They must learn to document their work to provide some way of trailing what is done.

You last statement gets me! :) Thou mouse and keyboard must work! :scratch: Really? :rolleyes:

Most people run into these problems using a usb configuration for the I/O. Depending on hardware this can be worked around. Sometimes the configuration is the mouse plugged into the keyboard hub instead of the system hub. Other can be just the mouse device detection. The combinations are numerous. Yes, get the keyboard and mouse working by knowing what you have. And what to do to solve the problem(s)

These type of problems have been addressed so many times on LQ that a search will get you out of trouble. Be it for Slackware or other distributions. A search on LQ will get you loads of information if you know what and how to key for your search.