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.
Athlon 64 3200
evga 5700 ultra
Hercules fortissimo III
2 Hitachi deskstar 80GB sata hds
lite on dvd burner
That is basically all i think is need out of the hardware
Anyway I'm having a hard time getting any distro to install. I've tried Slack 9.1, Mandrake 9.1, Fedora 64 beta, Mandrake 10.0 beta and in all cases none of them seem to detect the hard drives.
I've tried to install using raid and non-raid configurations and still nothing.
I've looked, mostly the solution seems to be compile your own kernel and insert it into the slack tree and then make a new iso. The problem being is I don't have a linux system running to compile my own kernel so that won't help. I was more looking for suggestions of a distro that would work with out recompiling.
So, basically....I have a old ata non-serial drive that i'm going to throw in the box, hopefully it will allow slack to be installed and then compile a 2.6 kernel, yada yada yada.
I really didn't want to have to go to all that trouble for something that may or maynot work anyway.
I'm still open to other suggestions....if anyone cares to help
Yeah compile own kernel is solution for yer hardware++, but if it is not worked yet, u ll get experience on the kernel compile which u can use to solve many other thing that not yet come over yer mind or they r, but u just seral tast with one smash...
Compile kernel is kinda experience oriented, u ll have go through the config menus several times, based on how ur experience of hardware is .. But it is not c++ coding contest, that is an successive aproximation approArch, don't ask me about it, n don't mix with that topic. It is kinda time n bandwidth wasting for non anaproofed kid ..
N it has nothing to do with kernel compiling. With luck u ll solve it faster with kernel cooking than to wait for slack9.2 or mdk10 .., peace ..
Hi, I don't know if my experience with Suse can help you, but I have just completed my installation and written a small HOTOW to run arround the traps.
almost every recent linux distro worked fine with my nforce2 sata non-raid, but nothing seemed to work with raid. im suprised that mdk 10 didn't, i thought that kernel 2.6 would handle most of that stuff (i haven't tried it with sata raid yet)
i think it might be with the particular sata controller. my nforce2 has a sil3112, im not sure if the nforce3 has it built in, or still uses an extra chip. if it uses an extra chip, search on that specifically
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.