Don't Laugh, I have kind of a Frankenstein System here.

Ok, I just purchased a 120 GB HD (39.00 bucks at Best Buy) However it had an Ultra ATA/100 interface. My MoBo didn't support the Ultra ATA but I had an old Ultra ATA/33 Promise card. So I have it all hooked up and XP sees it just fine. I formatted it as NTFS since I was pretty sure Linux would mount an NTFS drive. However, Linux doesn't see the drive.
fdisk -l shows other drive but not 120 GB.

The Hardware info shows that indeed the promise card is recognized but not HD.
Is it that the HD is NTFS? I was almost positive that Linux would be able to mount that.

Suse 10 dual boot 1 hd is Suse the other XP.

any ideas?

The exact description of the IC mounted on the controller.

Thank you for the reply .
Sorry for taking so long.
I'm not sure exactly what numbers you'd like, but I'll srtart with the most obvious.

In yast2 Hardware information
it's identified as a Promise 20246
On the card on the chip which I think is the bios says V1.20

PN 6000560
Assy 9709-00

I'm just somewhat flabbergasted that XP sees it fine but Suse 10 doesn't.
The new HD is where I store and catalog MP3s and that's what I do in Linux.

If you need any more info let me know.
I PROMISE (Get it ha ha ha Ok, maybe not funny) to get back to you quicker.

I'm sure this isn't the answer you're looking for, but linux has limited NTFS support. Basically, you can read NTFS partitions but there's limits on writing to them (something like you can't delete or change the size of any files, or create new ones). fat32 is a better option if you need to write to the drive.

What is your output from dmesg? particularly the part where drives get assigned to device nodes.

Thank you for your reply.
It's just somewhat aggravating that XP sees the HD fine and Linux won't.
I'm just using the HD to store MP3s and my main reason for using Linux is to do all the ripping, encoding, cataloging and playing mp3s so if I can't see my new HD , I'll probably have to scrap linux all together. I really don't want to do this.
I really want to make it work, but here's the dmesg output:

Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
SCSI subsystem initialized
PIIX4: IDE controller at PCI slot 0000:00:04.1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xb800-0xb807, BIOS settings: hdaMA, hdbio
ide1: BM-DMA at 0xb808-0xb80f, BIOS settings: hdcMA, hddMA
Probing IDE interface ide0...
hda: Maxtor 91190D7, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: max request size: 128KiB
hda: 23243472 sectors (11900 MB) w/256KiB Cache, CHS=23059/16/63, UDMA(33)
hda: cache flushes not supported
hda: hda1 hda2 hda3
Probing IDE interface ide1...
hdc: WDC WD136AA, ATA DISK drive
hdd: CREATIVEDVD5240E-1, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hdc: max request size: 128KiB
hdc: 26564832 sectors (13601 MB) w/2048KiB Cache, CHS=26354/16/63, UDMA(33)
hdc: cache flushes not supported
hdc: hdc1
hdd: ATAPI 32X DVD-ROM drive, 512kB Cache, DMA
Uniform CD-ROM driver Revision: 3.20
PCI: Found IRQ 5 for device 0000:00:0a.0
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0
<Adaptec 2940 Ultra SCSI adapter>
aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs

Vendor: MATSHITA Model: CD-ROM CR-508 Rev: XS03
Type: CD-ROM ANSI SCSI revision: 02
target0:0:5: Beginning Domain Validation
target0:0:5: Domain Validation skipping write tests
target0:0:5: FAST-10 SCSI 10.0 MB/s ST (100 ns, offset 15)
target0:0:5: Ending Domain Validation
sr0: scsi-1 drive
Attached scsi CD-ROM sr0 at scsi0, channel 0, id 5, lun 0
Attached scsi generic sg0 at scsi0, channel 0, id 5, lun 0, type 5
Attempting manual resume
swsusp: Suspend partition has wrong signature?
ReiserFS: hda2: found reiserfs format "3.6" with standard journal
ReiserFS: hda2: using ordered data mode
ReiserFS: hda2: journal params: device hda2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: hda2: checking transaction log (hda2)
ReiserFS: hda2: Using r5 hash to sort names
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
Adding 385552k swap on /dev/hda3. Priority:-1 extents:1

and the last 5 lines are this:
end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 0
subfs: unsuccessful attempt to mount media (256)


please let me know if there is anything else you would like to know.
Any suggestions would be helpful.
Thank you

AHA!
I just tried to boot it from a Knoppix 3.3 live cd and it worked fine and even automounted the 120 GB NTFS drive so the problem appears to be with SUSE.
I think I may rephrase the question on the SUSE forum.

Thank you all for your ideas and suggestions.

In a bold and daring move,
I figured out that even though Suse could see the Promise Controller card, it wasn't loading the module/driver thingie.
So in the Yast Control Center I enabled the Module for the Promise card in the Disc Controller settings.
The Angels can now get back to playing harps and singing.