View previous topic :: View next topic |
Author |
Message |
gnac Guru
Joined: 30 Jun 2003 Posts: 302 Location: Columbia River Gorge
|
Posted: Wed Feb 25, 2004 3:40 am Post subject: Promise Ultra 100 tx2 not detected |
|
|
First of all sorry, I realize this is the n-millionth post about this subject, however the n-million-minus-1 threads I read did not propose a solution to my problem.
I installed two 80G drives on my Promise Ultra tx2 controller.
I rebuilt the kernel with the promise 202... installed as a module.
I had to add pdc202xx_new to my modules.autoload because hotplug did not do it automatically.
Doing a grep for "ide" on the output of dmesg gives me this segment:
Code: | 76:NFORCE2: IDE controller at PCI slot 00:09.0
80:AMD_IDE: nVidia Corporation nForce2 IDE (rev a2) UDMA100 controller on pci00:09.0 |
which appears to tell me that my motherboard chipset (nforce) has found the promise controller. However grepping for "promise" returns nothing. grepping "md" gives me this relevent output:
Code: | 101:md: raid1 personality registered as nr 3 1368 2363 8000338+
102:md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
103:md: Autodetecting RAID arrays.art8 2364 4853 20000893+
104:md: autorun ...
105:md: ... autorun DONE.t0/lun0/part9 4854 7343 20000893+ |
Problem is, the drives are not listed in /dev/hd* anywhere. I have no idea where else to look. I read a post from another user that switched to Fedora which detected and installed fine. Please tell me I don't have to do this, or worse yet, return to using that vestigial Windows partition I still have laying around. :~)
Please help. _________________ "I thought she'd steal my heart, instead she stole my kidney,
and now its for sale, on the black market in Sydney" - Better Abraham |
|
Back to top |
|
|
Richie n00b
Joined: 03 Sep 2003 Posts: 52 Location: Home
|
Posted: Wed Feb 25, 2004 7:46 pm Post subject: |
|
|
What does this command say? Does it show your promise controller?
Also, promise raid devices appear under /dev/ataraid/discX/partY for newer kernels and /dev/ataraid/dXpY for older ones iirc. |
|
Back to top |
|
|
amne Bodhisattva
Joined: 17 Nov 2002 Posts: 6378 Location: Graz / EU
|
Posted: Wed Feb 25, 2004 8:03 pm Post subject: |
|
|
i guess compiling as module gives you the trouble. i have CONFIG_BLK_DEV_PDC202XX_NEW=y (a.k.a. [*] in make menuconfig) in my .config and it works like a charm. as it works in fedora, there might be a way to solve this with a module as well, but i don't know how. |
|
Back to top |
|
|
gnac Guru
Joined: 30 Jun 2003 Posts: 302 Location: Columbia River Gorge
|
Posted: Wed Feb 25, 2004 9:14 pm Post subject: |
|
|
Richie wrote: | What does this command [iirc] say? Does it show your promise controller? |
It shows it, but doen't know what it is?
Code: | 01:06.0 Unknown mass storage controller: Promise Technology, Inc. 20268 (rev 02) |
Richie wrote: | Also, promise raid devices appear under /dev/ataraid/discX/partY for newer kernels and /dev/ataraid/dXpY for older ones |
First of all, no. there is no /dev/ataraid at all. This raises another point. I'm not planning on using ataraid, but rather software raid. Should I still expect the promise IDE controller to show up under ataraid?
amne wrote: | i guess compiling as module gives you the trouble |
Well, I don't really have a reason for compiling it as a module other than thats how I read to do it in other threads. I might try rebuilding this when I get a chance.
thanks _________________ "I thought she'd steal my heart, instead she stole my kidney,
and now its for sale, on the black market in Sydney" - Better Abraham |
|
Back to top |
|
|
ProtectionFault Apprentice
Joined: 14 Nov 2003 Posts: 170 Location: /dev/zero
|
Posted: Wed Feb 25, 2004 9:45 pm Post subject: |
|
|
I'm using the same controller on my server.
It's not a raid controller, only an IDE controller card...
So there will be no ataraid entry in /dev...
I've never compiled this driver as module.
Try compiling it into your kernel.
Maybe this solves your problem.
Best regards
ProtectionFault _________________ ASUS Z87-PLUS, i7-4770, 2x8GB DDR3-1600, 700W OCZ Power Supply, EVGA GTX760 4GB, 3TB HDD, Gentoo ~amd64 (3.10.10, dm-crypt full disk, awesome) |
|
Back to top |
|
|
gnac Guru
Joined: 30 Jun 2003 Posts: 302 Location: Columbia River Gorge
|
Posted: Wed Feb 25, 2004 10:17 pm Post subject: |
|
|
amne wrote: | i guess compiling as module gives you the trouble |
ProtectionFault wrote: | Try compiling it into your kernel. |
Code: | ls /dev/hd? -l
Feb 25 17:15 /dev/hda -> ide/host0/bus0/target0/lun0/disc
Feb 25 17:15 /dev/hdf -> ide/host2/bus0/target1/lun0/disc
Feb 25 17:15 /dev/hdg -> ide/host2/bus1/target0/lun0/disc |
Awesome, awesome, awesome.
Thank you very much!
Now to get software raid working! _________________ "I thought she'd steal my heart, instead she stole my kidney,
and now its for sale, on the black market in Sydney" - Better Abraham |
|
Back to top |
|
|
stdPikachu Apprentice
Joined: 10 Mar 2004 Posts: 254 Location: UK
|
Posted: Tue May 18, 2004 10:20 am Post subject: |
|
|
Bah, just came across the same problem myself!
Promise TX2 (mine is ATA 133, newer model) and the boot kernel detected it straight out of the box. Support was compiled in as a module (20248xx_new or whatever it's called) in the current gentoo-sources (2.4.25r2), and lo and behold none of the drives on it were detected at boot.
I wish the kernel help had made it more obvious that it needed to be compiled in rather than moduled. I thought since none of the drives on the controller are used for boot drives, they'd just become visible later, but alas no. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|