Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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: Gentoo, Slackware, RHEL. Debian/Ubuntu, FreeBSD, Solaris, OSX, MS
Posts: 57
Rep:
Slack 10.2 on Dell Dimention 9150
I can't install 10.2 on a Dim 9150 with sata disk.
Of cause bare.s don't work, sata.s won't detect the disk. The test2.6 image locks on keymap select.
AFAIK, none of those use libata, it's oldfashioned IDE SATA, right?
Anyone solved this install on a Dim 9150?
I also tried:
Vectorlinux (slack based) doesn't detect the cdrom (NEC 3520 ATA) when searching for an install media, though I can exit the setup and manually mount the cdrom and use it. Can't even continus the installer after manually mounting the cdrom.
Slamd64 also has problems, just don't remember which.
I've install Kubuntu on another Dim 9150; only problem was that it couldn't autodetect the Intel Pro/1000.
That was easily solved by adding 'alias eth0 e1000' to modprobe.conf, insmod'ing the e1000.ko module, and manually editing the network setup.
Haven't tried other *nux'es as yet. XP (Dell install) works fine.
So kubuntu basically works. Why not stick with it until you have more linux experience.
SW will require more hands on configuring from you and requires that you know your hardware specs. You may need to compile your own kernel. Check out linux mafia site sata section for details on sata and sata/ide combo hw in linux.
Distribution: Gentoo, Slackware, RHEL. Debian/Ubuntu, FreeBSD, Solaris, OSX, MS
Posts: 57
Original Poster
Rep:
Kernels and HW specs are not the problem. On my own systems, I solve such things, like installing using non-libata, compiling 2.6 and moving from /dev/hdX to libata and /dev/sdX.
This is not my home computer, it's on the job, and I can't spend time solving special install probs. I don't _need_ to use Slack, just wanted to because it's what I'm most used to.
I tried booting the relevant images without ioapic etc.. to see if that would solve the lockup. No go.
I could choose to install on a PATA, compile a 2.6 kernel, mount the SATA disk, and dd it all to that, but it's too much time for a single computer. I'm the sysadm, so I can do what I want on my own system, but as we're not going to use Slack in production, it's not worth using if I can't install in a quick fashion.
Just wanted to see if others had an easy fix for identifying the Intel SATA controller in the Dim 9150.
EDIT:Personally, I prefer 'standard' pc solutions over proprietary stuff. No legacy disk mode in a Dell BIOS, AFAIR. I'll check for 'compatibility mode' tomorrow; don't think it's there.
No errors, just didn't find the SATA disk.
I'll give the test26 image another go; it should detect the disk. Maybe I misspelled noapic, so it still used ioapic, which then caused it to lock up.
It's odd that the sata kernel didn't detect the disk. I have a Dell Optiplex GX280 that it worked fine with. The only problem I had was that I had to disable the local APIC to get the network card recognised (http://www.linuxquestions.org/hcl/sh...t=2021&cat=202).
The BIOS was set to the default SATA mode (compatibility mode off) and the installer picked it up no problems. Did you get an error or did it just not find it?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.