[SOLVED] Trying to install Slackware64 on IDE disk
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.
When I boot with the Slackware64 DVD and run either fdisk or cfdisk to partition the hard drive, it only sees the SATA drive, not the IDE drive.
I have a Gigabyte MB #GA-880GM-D2H that has four SATA ports and an IDE port. I have two hard drives, the first one is a 200GB IDE (ST3200822A) and the second one is a 1TB SATA (ST31000524AS).
The DVD-RW drive and the 200 GB IDE drive are plugged into the IDE controller on the motherboard and the 1 TB SATA drive is plugged into SATA 1.
In the BIOS I have it configured as:
IDE Channel 0 Master: ST3200822A (200 GB IDE)
IDE Channel 0 Slave : TSSTCorp CDDVDW (DVD-RW IDE)
IDE Channel 2 Master: None
IDE Channel 2 Slave : None
IDE Channel 3 Master: ST31000524AS (1 TB SATA)
IDE Channel 3 Slave : None
(I have also tried it with the 1 TB SATA on Channel 2 Master).
When I boot Slackware64 and fdisk/cfdisk will see:
First Boot Device: CDROM
Second Boot Device: Hard Disk
Third Boot Device: Floppy
And:
OnChip SATA Controller: Enabled
OnChip SATA Type: Native IDE
(There are two other choices: RAID and AHCI - don't know if that would make a difference or not)
I'd like to use the 200 GB IDE drive as the system drive and the 1 TB SATA as /home.
I hate to say it, but with Windows 7, it sees both drives without any issue and asks which drive to install on.
libATA Developer's Guide + https://ata.wiki.kernel.org/index.ph...error_messages Libata error messages] libata_switchover <- 'This is written to provide one of several ways to retain a working system after upgrading from Slackware 13.0's kernel to the newer kernel in -current (which removes support for the "old" ide subsytem, thereby causing all /dev/hd* devices to have /dev/sd* names.' + 'Must Read to prevent the Gotcha Clown from popping up'
The latter of these links is for Slackware references in general and very useful to garnish helpful information.
One after thought to try: Change the Master & slave positions. Make your ROM media the master with the Hard drive as slave. Remember the master is at the end of the cable.
Do you have a BIOS setting for 'native IDE' or some just say 'IDE mode'?
Quick & dirty would be to just disconnect the SATA drives to do the install then modify the mount point for '/home' after the install. Slackware install will find & assign drive as a 'sd' device via libATA.
To be sure the problem is not on the hardware side, you could try if the installer sees the IDE drive when the SATA drive is unplugged. I don't mean installing, but just running the installer. Anf maybe vice versa. I recall having similar problems with my quite similar setup, but IIRC it was rather a hardware problem, like incorrectly set jumpers or something.
and you want to set it to RAID, or AHCI, or just play around with them to see the results. I am not really knowledgeable about RAID or RAID controllers or anything like that, but you should read the wiki on Advanced Host Controller Interface http://en.wikipedia.org/wiki/Advance...ller_Interface it kind of sheds some light on the subject.
You need to have the IDE-HDD (if this is the case for your system) set as one of the primary boot devices (usually the second device to the selected optical drive). This device should be configured in the jumpers to Master.
cfdisk and fdisk should auto-detect the /dev/sda and/or /dev/hda and show the appropriate device, but if not try the following:
Quote:
fdisk /dev/hda
cfdisk /dev/hda
Just a word of precaution, if you use a single port IDE setup, try to limit usage of the IDE port solely to being used with Hard drives or optical drives, but not both. You should use the SATA ports if you have them for all devices like hard drives and optical drives with the primary hard drive set to port0 and the optical device set to the next port in the series depending on how many hard drives you support.
What do you see in 'dmesg' for the IDE ST3200822A (200 GB IDE) & TSSTCorp CDDVDW (DVD-RW IDE) drives?
I owe you a beverage of your choice. ;-)
I unplugged the sata drive and sure enough the IDE came up in cfdisk just fine. I then plugged in the sata drive again and booted the slackware dvd. Once I got to the root prompt I checked out dmesg and sure enough, the IDE hard drive is registering after the sata drive (e.g. /dev/sdb) so I have the sata drive on /dev/sda and the IDE on /dev/sdb.
I'm currently installing Slackware64 on my new machine while I type this on my old one. ;-)
Well, I thought this was solved....
I tried installed to /dev/sdb configured lilo as such and now I get the following error and then the system hangs when booting:
LILO - Keytable read/checksum error
I even installed to /dev/sda and I still get the error.
I'm stumped now....
Update:
Booted Linux Mint 11 Debian Edition and it found the drives as:
/dev/sda --- 200 GB
/dev/sdb --- 1 TB
Just what I wanted. Although the install is cheesy where you can only specify a / and a /home partition and that's it. I just want to use slackware :-*(
Last edited by bassplayer69; 09-30-2011 at 08:50 PM.
A rather simple solution to that would be to compare the lilo.conf Mint creates with the one Slackware does. My guess is this has either to do with the BIOS boot order or the "compact" flag in lilo.conf.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.