Mandrake Install Problem

[Egress]

While trying to install mandrake 7.1 to my computer it asks me if i have any scsi devices, i reply no, and it continues to ask and i never get any further. could it be my because i have my hard drive on my ata100 channel (asus a7v mobo)? and no, i don't want to put it on my regular IDE ports. how do i get by this, i'm just getting into the whole linux thing.

[phazeman]

Is there any way you download and try to install the Mandrake 8.0 ? It much more nice
and have a lot of updates ...
I don't have the exactly answr for you, just trying to help...

[Egress]

that is a definate possiblity, i'll try it. personally i think its my promise driver thats actually causing the problem, but i don't know how to get by that.
-e

[grendel_khan]

8.0 is the way to go for you. I had the same problem with my Highpoint controller under 7.1, but all was fixed by 7.2.

[bdg1983]

You can use Mandrake 7.1 with the ata100 controller, but you need to do the following from the Ultra66 NHF. There are actually plenty of these all over the web and probably documentation at Mandrake's site on installing with a ata100.

You don't need to patch your hardware (third party controller from promise technologies), if you are running kernel 2.2.x. For 2.0.x I have no idea. I run 30 such boxes in our office, all of them identical, and using this Promise Technologies controller. All I had to do was give extra command line arguments to the kernel at boot time. To figure out the command line arguments, but with a linux boot/rescue floppy. When you reach the command prompt, do a
cat /proc/pci

You should see something like this in the output produced by this command, in addition to other junk. Unknown mass storage controller: Promise Technology Unknown device (rev 1). Vendor id=105a. Device id=4d38.
Medium devsel. IRQ 5. Master Capable. Latency=64.
I/O at 0x1400 [0x1401].
I/O at 0x10f4 [0x10f5].
I/O at 0x10f8 [0x10f9].
I/O at 0x10f0 [0x10f1].
I/O at 0x1080 [0x1081].


Now Note down the values on those lines beginning with I/O, call them a, b, c, d (which in my case are 0x1400, 0x10f4, 0x10f8, 0x10f0). Ignore "e" (0x1080).

Then give the following command line argument to your kernel on the "lilo" prompt.

lilo: linux ide2=a,b+2 ide3=c,d+2

Which in my case is:
lilo: linux ide2=0x1400,0x10f6 ide3=0x10f8,0x10f2

You should see the drive through linux after that. To avoid having to type that command line arguments to kernel everytime, you can configure lilo to automatically do this for you. Just consult lilo doc about "append" option.