I am quoting Aussie here,

"The P4P800 Deluxe uses the Intel ICH5R chip for SATA, and kernel 2.4.22 supports this chip."

I have known Aussie to tell the truth here in this forum, but I am having issues that say otherwise (at least with Slackware).

lspci shows this after a fresh install, hotplug enabled, kernel 2.4.22 :

00:00.0 Host bridge: Intel Corp.: Unknown device 2570 (rev 02)
00:01.0 PCI bridge: Intel Corp.: Unknown device 2571 (rev 02)
00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB PCI Bridge (rev c2)
00:1f.0 ISA bridge: Intel Corp.: Unknown device 24d0 (rev 02)
00:1f.1 IDE interface: Intel Corp.: Unknown device 24db (rev 02)
00:1f.3 SMBus: Intel Corp.: Unknown device 24d3 (rev 02)
02:04.0 RAID bus controller: Promise Technology, Inc.: Unknown device 3373 (rev 02)
02:05.0 Ethernet controller: Galileo Technology Ltd.: Unknown device 4320 (rev 13)
02:09.0 VGA compatible controller: S3 Inc. ViRGE/DX or /GX (rev 01)
02:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
02:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)

See the "Unknown device" tags above. That is not good. I bought this board for it's kick ass disk controllers and I can't use them like this.

I could not fix this even with a newly compiled 2.6.6 kernel (which should have picked my hardware up).

Here is the part that kills me ,
Both Gentoo and Knoppix are picking up EVERYTHING with just booting from the cd's. In either case, lspci shows that all hardware is properly recognized.
Both of these cd's use kernel 2.4.22, so as Aussie stated, this kernel does support my hardware perfectly. I even went as far as to install Gentoo, and when I was done, lspci turned up perfect results.

What the hell is going on here with my beloved Slackware? I love Slack until the very end, and I DON'T want to use any other distro, but I may have to, and that sucks big time.

Does anyone have a clue as to what is happening here ?

BTW: Yes, I did download new iso's of Slack 9.1. Still no dice.

well, go thru and re-compile the kernel for your exact
Mobo specs........

320mb -
Me -
I tried that. I enabled the proper options for my board and proc.
The kernel booted and operated just fine when I was through. It did not solve my problem though. Keep in mind that this was Slackware w/2.6.6 and still did not solve this.

With Gentoo and Knoppix, they found my hardware even with kernel 2.4.22.

So I am stumped here. It just isn't adding up, and the last thing I want to do is put something other than Slackware on this server.

Just tried kernel 2.6.4 . I went back to this kernel because I saw in some posts that this kernel detects everything properly.

Still didn't work. lspci is turning up 'unknown devices'.

This sucks. I will have to betray my faithful friend Slackware, and use another distro. I know that Gentoo and Knoppix peg everything correctly, and I suspect Mandrake will as well. I can't even think about Redhat.

What would a die hard Slackware guy like myself take a liking to?
What distro will come the closest to Slackware?

I would think that you have to find out what options or patches Gentoo and Knoppix are using that let them pick up your mb, and then incorporate them into your kernel.

Thank you Kovacs. That is actually a great idea.

Here is an update :

I tried Gentoo, Suse 9.0, Vector SOHO4, and of course Slack 9.1.

What I find is similar disk performance between all of them.
I did not properly benchmark the drives, I just used 'hdparm -tT'
to quickly test throughput of the controller and the disk cahe onboard
each drive.

The numbers on each platform were all between 50-56 MB/S.
I have Slack 9.1 back on my machine (where it belongs), and I just
tested and got 674 MB/S for the drive cache, and 54.70 MB/S for
throughput.

What this appears to be is that Slackware 9.1 does understand the disk
controller, and performs just fine, even though the 'lspci' listing
says otherwise.

I also found that none of the distros had the driver for the new Promise
controller, so I was pissin in the wind there.

Being that I'll have to wait for the Promise kernel module in any event,
I have returned to my faithful friend Slackware.

One last note. As in my previous post, it turns out that Slackware is having no problems supporting ICH5. I further tested the drives with "iozone", and my drives are right where they should be.

Unless I see something realy out-of-place, I will put this one to rest.

I'll be glad when the new promise modules are out. Then I can use that too.

I'm almost certain that the identification issue with "lspci" depends on libpci and not the kernel. It's not sufficient to simply upgrade the kernel.