Hello, I have a Soyo Dragon Plus motherboard with an onboard Promise Fasttrak100 lite controller (20265) and I'm having troubles in making it work with a custom compiled kernel (2.4.20). Let me first describe my devices: hda: LG DVD-ROM hdd: LG CD-RW hde and hdg: 2x Seagate Barracuda 7200-7 40GB I built a RAID0 array with my two drives and was able to install RedHat 8 and boot from it, using Promise's "pseudo"-SCSI driver. Now I'm trying to make a custom build linux (LFS) with kernel 2.4.20 boot from another partition, and selected the following kernel options in ATA section: CONFIG_BLK_DEV_IDE=y CONFIG_BLK_DEV_IDEDISK=y CONFIG_IDEDISK_MULTI_MODE=y CONFIG_BLK_DEV_IDECD=y CONFIG_BLK_DEV_IDEPCI=y CONFIG_IDEPCI_SHARE_IRQ=y CONFIG_BLK_DEV_IDEDMA_PCI=y CONFIG_IDEDMA_PCI_AUTO=y CONFIG_BLK_DEV_IDEDMA=y CONFIG_BLK_DEV_PDC202XX=y CONFIG_PDC202XX_BURST=y CONFIG_PDC202XX_FORCE=y CONFIG_BLK_DEV_VIA82CXXX=y CONFIG_IDEDMA_AUTO=y CONFIG_BLK_DEV_IDE_MODES=y CONFIG_BLK_DEV_ATARAID=y CONFIG_BLK_DEV_ATARAID_PDC=y CONFIG_BLK_DEV_ATARAID_HPT=y When I boot my kernel it stops with a Kernel Panic, "unable to mount root file system". Ok, the problem is that I even get no message from promise softwareraid driver initialization, althougt I get a message from Highpoint driver saying that no array was found. So I think that softwarraid for promise was not activated. Just to mention, prior to my current HDs setup I had one Maxtor 40 GB HD connected to ide0 that was my primary disk. When I booted linux from this disk (same kernel) with my raid array (not bootable then) activated, I got a "Promise Softwareraid driver version 0.03 ... : no array found" message from kernel initialization, but now I don't get even this! I don't have this disk anymore to test it again, but I think that when I removed it and and booted from my raid0 array this problem appeared (before I was trying to understand it didn't find my array). I tested also kernels 2.4.21-rc7 and 2.4.18, but the problem is the same, no promise softwareraid initialization. I also tried many different kernel options, including disabling CONFIG_PDC202XX_FORCE option (as seen in some messages in this forum) and using an append line in Lilo, without luck. Below are some more details of my system: Motherboard: Soyo Dragon Plus! (Via KT266A chipset) Promise fasttrak100 lite controler, BIOS version 1.31 build 30 Hope I've given sufficient information (BTW, how do I write kernel initialization messages to a file when I'm not able to boot? Is it possible?) Any help appreciated, Thanks, Tiago Gehring tiagogehring@xxxxxxxxxxxx __________________________________________________________________ Try AOL and get 1045 hours FREE for 45 days! http://free.aol.com/tryaolfree/index.adp?375380 Get AOL Instant Messenger 5.1 for FREE! Download Now! http://aim.aol.com/aimnew/Aim/register.adp?promo=380455
