I've installed Slack (9.1 maybe?) on a different system before, using the whole 2.2 gig hard drive But now I want to dual boot with 10 on my current system. It starts booting from the cd, and then suddenly stops where it's at in the picture here - http :// img12.exs.cx/my.php?loc=img12&image=untitled449.jpg (obviously remove the spaces. I know this violates the rules. I'm really sorry, I know how annoying noobs are, but for whatever reason the admins decided, there's no attachments, and I didn't feel like retyping that entire screen...if doing what I did is truly a problem, lemme know and I'll take it out...:-/ ). I have a 2.8@3.2, gigabyte ga-8ipe1000L rev 2, 120 gig seagate sata with 2 windows partitions, linux ext 3 and a swap partition, radeon 9800 pro, sony (basically rebadged liteon) cdrw. Not sure if you need any/all of that information, but better safe than sorry. Any of you guys have any suggestions??

I would try another cd as your screen does not show any error so maybe the install hangs on CD because it can not read data...

I just noticed about halfway down it says "OEM120-72AS 120GB 7200RPM, ATA DISK" ... well, that 'ata' disk is really sata ... could that be it? (note: i have two hard drives in at the moment, one ide, one sata)

The kernel on the slack cds doesn't have support for sata. That is your problem. Search around on how to install on an SATA box.

--Shade

i searched a bit and came up with this:
The way I did it:
1. grabbed 2.4.22 and the -ac4 patch from kernel.org

2. extract the kernel into a directory.

3. patch it w/ -ac4. follow the directions in the README.

4. copy the config file from bare.i into my now 2.4.22-ac4 folder as CONFIG. make mrproper. mv CONFIG .config

5. make menuconfig

6. go to scsi support, --> scsi low level devices --> sata (select Y) --> select Y for VIA (in your case).

7. exit save. make dep. make bzImage

8. Now realize I keep a copy of Slackware in my /Pub/slackware directory and the ~/slackware/kernels directory is there.... I copied my resulting bzImage and System.map.gz into the ~/slackware/kernels/bare.i folder. Then I cd'd into the top level of my slackware directory and used 'mkisofs' to create an iso...there is directions in the isolinux directory of slackware, though I did it a little different. Burned it. Now I had a custom slackware cdrom to boot off of and I just used bare.i as the boot: option.

9. After I got it to install, I copied over the network that patched kernel directory, put it into /usr/src/ and ln -s /usr/src/2.4.22-ac4 /usr/src/linux. I then compiled it on the local machine and installed the resulting kernel this time including make modules && make modules_install. Made sure it would boot then ran from there....


I hope that all makes sense and helps. I am sure there is an easier way....heh like a network install???? but I since delivered that machine to its owner (including the custom slackware install disk) and it was the first SATA box I built. Bottom line. It is doable. I tested it for a week before delivery and it was stable for sure.... good luck.

edit: -ac4 is actually the latest Alan Cox patch for 2.4.22, and after further looking I think 2.4.22 already has SATA in it.... but if it doesn't grab the -ac4 patch.




Now...all I have to say is...the hell?! I don't understand any of that. Not. One. Bit. The thing I -did- understand was the thing about the 2.4.22 already having support for SATA...well Slack 10 says they all have 2.4.26 kernels. Ugh, I'm really confused. If I can't get this, I'll just go to RedHat or something, which I really don't want to do. Just so you know, I don't have a floppy drive, which apparently you usually need. Now, if someone wants to take time and catch me via instant messengers (AIM or MSN) or email, let me know...or we could use this thread, but there are plenty of threads wasting away on this topic, NONE of which I understand. *sigh* sorry guys...I just don't get it

The vanilla 2.4.x series does *not* have support for SATA to the best of my knowledge. You're seeing the alan cox (-ac) patch applied, which I think backports 2.6's SATA support to 2.4. Slackware uses stock unfiddled-around-with kernels, without these sorts of patches. Don't get frustrated because it's not working, it *shouldn't* work with your setup.

All you need to do is create a boot disk with a kernel that supports SATA and you should be in business.
I promise you, the information is on this board

--Shade

So I'm downloading bonecrusher's recompiled sata kernel disk 1 ... will this work, without any problems? I don't need a special second cd, do I? Or am I doing completely the wrong thing altogether...

//EDIT: Now, do I need to use LiLo or GRUB, or will the built in bios OS chooser thing (very specific terms, i know ) work just fine? You know, where it lists XP, and whatever else you have installed and gives you 30 seconds to choose?