I'm trying to get Slack. I've posted a few times in the "Installing Slacware" section, mainly discovering that the PC I'm using to install Slack has an Intel chip that recent kernels don't support. I've tried Slackware 13.1 and 13.0, and neither is compatible with my box. I've just finished burning 12.2 to disc, and was going to try that too, but eventually I'm going to get far enough back in time that I'm afraid of running into a Delorian with flux capacitors. What concerns me is that the usb wireless reciever I have won't work, and who knows what else.

I'd seen a few posts suggesting that Salinux might be a better way to go, so I tried that too, only to discover that it's the same kernel as either 13 or 13.1, and won't work either. That got me to thinking (no one who knows me reccomends that I do this any more than neccassary, as they've seen what happens when I do..)

I've only been using Linux for a little more than a year. My first time was Puppy Linux, but I was too new to figure out how to tell grub to find vmlinux and all the rest. I could boot with the live cd and use it mto my heart's content, but I wanted something that would load and run like an operating system, and it was a post here on LQ that led me to Vector Linux. Vectior was cool, it was impossible to change anything because it was based on Slacware, but there was very little that NEEDED changing! It did everything, played Youtube, did Java, all kinds of stuff. Even better, it did it on the same PC I'm referring to in the current dealings I'm having with recent kernels. So I thought I'd dust off the live cd and see what happens.

So here I am, typing from that same live cd. X works without a hitch, I'm using wicd to connect, just point and click, it's all good and all done on a PC that defeated not only Slacware but the new Mint/Debian, and probably Arch too, as I had it working on this computer but was never very happy with the way it worked, (the mouse wouldn't work no matter what I did for instance.) Turns out that's a symptom of the new kernel boogie.

So I'm taking this as a sign that maybe I should just go with what works, and accept it that a lot of very dedicated and talented people have done a lot of hard work to make something so simple that even an idiot like me can use it, and that perhaps the best thing to do is go ahead and use it, enjoy the hell out of it and be glad.

I think it's time I put Vector back on this hard drive and leave it there. I wanted to get Slack so I could learn more, but this sounds like the best ticket to Oz.I still expect suff to come up that'll teach me some Linux. But why look a gift horse in the mouse?

What exactly is the problem? Can you tell us what error messages you got when trying to install Slackware? When you initially booted Slackware to try to install it, did you use the main kernel? Did you try with huge-smp, or without smp?

Your post is kinda hard to read as one big paragraph also.

When I started to use Linux I was satisfied with Slackware 8.1. But in time I became more demanding. Now I expect to run even on older hardware - is it justified? It is difficult to say - but iI cannot imagine to go back - nowadays linux conquers Window$ everywhere - except games.

My first go-round was with 13.1, details here:
http://www.linuxquestions.org/questi...nstall-833637/
Problem is that I have an Intel chip, and newere kernels don't work with it.
Also this, when I tried 13.0 and found it not to work as well.
http://www.linuxquestions.org/questi...nstall-834138/

13.1 couldn't get X to work. With 13.0 X worked, but the mouse wasn't recognied after using the sytem for 10-15 minutes.

You could try using an old version of Slackware. Older releases are still maintained.

Of course, wireless networking has improved a lot over the last releases.

Have you tried 13.1 after copying the vesa config?
Maybe you can try that on the 13.0 install too.

I also have an Intel Graphic card - I upgraded X server to the version 1.9 (see 'Call for Xorg testing' post) and now with Xorg 1.9 and the kernel 2.6.35 I have no problems - I don't use KDE Desktop ( but KDE applications - yes - under Xfce). However If you want a system running out of box I advice to install Slackware 12.2 - an exceptionally stable distribution.

As a general advice, I would recommend to stop thinking about hardware support in terms of a distribution and start doing that in terms of a kernel version and included modules. All the time.

So, you should find out

1) Does the latest kernel support the chip? If not, throw the chip into trash. Linux has stopped to support it, period.

2) Is the support included in any Slackware stock kernel? If yes, just use it. If no,

3) Can I compile a kernel while the chip is nonoperational? That is, can I get the command prompt? If yes, compile the necessary support into the kernel. If no,

4) Is there a live CD or a distribution where I can get to the command prompt and compile the kernel still being compatible with slack? That is, are the same major libraries like C runtime not too old there? If yes, use it to compile the kernel. If no,

5) Use another machine to compile the kernel. You may ask somebody else with Linux to do that.

There may be shortcuts and workarounds to the above, but looking for them may result in an endless loop of distro hopping and question asking.

1 members found this post helpful.

Hi,

One thing you seem to keep missing: Slackware is not a hold your hand distribution. Sometimes you may get lucky and things will work out of the box. You've been given several options to get Slackware on the box.

If you want to use 13.1 then some work on your part is necessary. You did try the 'vesa' option as suggested?

I suggest that you look at 'How to Ask Questions the Smart Way' so in the future your queries provide information that will aid us in diagnosis of the problem. So far you have provide simplistic sense with some of the problems without any real definition that will allow us to help you.

No! The kernels you have attempted to use have not been streamlined to the hardware or system. You need to create a custom kernel or roll back to earlier version(s) to get things working.

You have to remember that to have the newest and fastest will not always be able to achieve. Nothing wrong with working with older versions if they meet the hardware or system needs.

Cute! But nothings set in cement saying you won't get that particular device working at that version level. Again, effort on your part if the device is to work for you. No magic wand or bullet to get things working out of the box. Some tweaking or hunting required. You did say that learning Slackware was the intent.

The portion in bold makes no sense in this context.

"Streamlining" a kernel won't add a new kernel module; the generic kernel that comes with Slackware has all the modules compiled and available.

Hi,

Sorry if you didn't get my meaning. The OP has tried several different versions of Slackware & kernels. His hardware was not driven properly.

If you have a better solution then post it. The versions 13.1, 13.0 have been issues for the OP. See OP's other referenced posts/threads.

If the OP does roll back to earlier versions Slackware then some of the new hardware he/she wants to use may require some additional work. So in order to get that you had better be able to compile or provide the necessary drivers. Suppose you have another solution?

Sure, the stable version has the current available drivers (not all, impossible since new hardware produced all the time) but the OP has an issue with the Intel Chipset. Ways around it but not in the sense attempted.
Two kinds of kernels available for Slackware!

BTW, Slackware is not the only distribution with Intel chipset issues.

Again, present your solution!

I agree with the "roll back to earlier version(s) to get things working" portion of the quote, which is why I neither highlighted nor commented upon it. When you tell someone to "streamline" something, it is quite rare to do so by adding things.

Hi,
I believe the use of the term streamline was justified and correct. Semantics?