Gregor Maier wrote:
> Hi there,
>
> i tried to use a Promise Ultra100 Tx2 IDE Controller with Kernel 2.4.7 but I
> didn't work. I compiled the kernel myself and added support for the Promise
> Chips (PD...) I also enabled the general IDE settings like UDMA support.
>
> When scanning the pci bus the card is as a part of the bus but the
> IDE-Controller isn't initialized. Since my primary HD is a SCSI Disk the boot /
> init process goes on until the initscript tries to mount my IDE Disk with a
> error message that the device is not there.
>
> Are there any options in the kernel config that are required to make the
> Controller work (others as I mentioned support for Promise Chips is already
> enabled). Or maybe I have to pass some kernel options??
>
> Thanks
>
> Gregor
>
> ----------------------------------
> E-Mail: Gregor Maier <[EMAIL PROTECTED]>
> Date: 24-Jul-2001
> Time: 16:31:29
> ----------------------------------
I reported exactly your problem to this list two weeks with no answer. Here is what
I found to solve the problem. I used the Ultra 100TXE on the cooker kernel
2.4.6-4mdk (which has another unrelated problem which maybe is resolved in the
current version: 2.4.6-5mdk):
your problem has nothing to do with the kernel version! The Promise Ultra 100TXE
IDE-controller card simply defines different logical names for your disk(s)!
Example:
You boot normally from SCSI:
-> /dev/sda
You boot your disk from the first built-in IDE controller as the master device on
this controller:
-> /dev/hda
etc.
...
-> /dev/hdd ( You boot from slave device on the second built-in IDE-Controller)
You boot your disk from first controller on the Promise Ultra 100TX2:
-> /dev/hde (!)
etc.
you boot your disk as the slave device from the second controller on the Promise
100TX2:
-> /dev/hdh (!)
Important: the logical names of your boot device are independant of which
controller(s) are really in use/not in use.
Simply tell lilo.conf the correct logical name of your boot partition! That's all.
Hope it helps.
-Joachim
