2008/5/7 Ryan Sims <rwsims@gmail.com>:

At a guess, it sounds like arch is loading a module that's a specific
driver for your chipset, while your own kernel is using the generic
ata drivers. Take a look at the output of hwd, lspci and such. You
also might get some mileage out of googling your motherboard, or poke
around on the forums (you could also check gentoo's) for your
chipsets. Do an lsmod under an arch kernel to see what modules its
loading, that'll help you configure your kernel.

It would help if you posted more specifics about your rig, and what
options you're selecting in the block devices part of the kernel
config.

On Wed, May 7, 2008 at 1:13 PM, Carotinho <carotinobg@yahoo.it> wrote:
> Hi!
>
> I'm sure this is an already answered question, but the problem is that I don't
> know which could be the question whose answer I'm in need of:)
>
> After this prologue, the problem is:
> The currently running system, with the Arch-supplied 2.6.24 kernel, has the
> disk devices all mapped to a /dev/sd* scheme, even if 3 are IDE and another
> is SATA.
> When I compile myself the kernel, I get the "traditional" /dev/hd* scheme,
> which is in contrast with the content of /etc/fstab.
>
> The main question is: how can I obtain the "right" behaviour from my own
> compiled kernel? Is this due to some misconfiguration of the kernel at
> compile-time, or is it obtained through some other kind of magic?
> The real problem here is that I cannot give a name to this problem, hence
> being unable to search for it!:) I've always used a Slack system with
> traditional disk mapping, it's the first time I come across this problem:)
>
> Thanks in advance!
>
> Carotinho
> Chiacchiera con i tuoi amici in tempo reale!
> http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com
>
>
>

--
Ryan W Sims