[arch-general] Compiling my own kernel: IDE, SATA...
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
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
I found this in the Official Arch Linux Install Guide on the wiki: "With the current kernel, an important change has been introduced pertaining to the ATA/IDE subsystem. The new pata (Parallel ATA) drivers replace the legacy IDE subsystem, and one important change is that the naming scheme for IDE disks has changed from the old hda, hdb, etc. to also use device names of the type sda, sdb, etc, just like SCSI and SATA devices do." This might explain your problem? -geir 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.
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
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
On Wed, May 7, 2008 at 1:13 PM, Carotinho <carotinobg@yahoo.it> wrote: the 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
Carotinho wrote:
Hi!
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:)
In most simple words - when you compile your kernel, exclude 'ATA/ATAPI/MFM/RLL support' completely. Make sure 'SCSI device support' is in sane condition, and select whatever you need from 'Serial ATA (prod) and Parallel ATA.....'.
Hi! Il Wednesday 07 May 2008 21:40:29 Michal Soltys ha scritto:
In most simple words - when you compile your kernel, exclude 'ATA/ATAPI/MFM/RLL support' completely.
Make sure 'SCSI device support' is in sane condition, and select whatever you need from 'Serial ATA (prod) and Parallel ATA.....'.
Aaaah ok that did the trick:) Now I understand what's going on!:) Now I've got /dev/sd* for all the devices. But there's an inconsistence between the ordering of the names. With the stock Arch kernel, I have: /dev/sda = primary IDE disk /dev/sdb = secondary IDE disk /dev/sdc = the only SATA disk I have With my kernel, I got: /dev/sda = the SATA disk /dev/sdb = primary IDE disk /dev/sdc = secondary IDE disk I've read, on the Arch wiki, the pages about consistent naming, but as far as I can tell, there's no track of it in my running system. I mean, in /etc/fstab the drives are mounted by device name, not by-label or id or uuid. So I infer there's another reason for this, and maybe it has to do with the stock initramfs loading the modules in a certain order. I'm not using an initramfs and no modules for scsi,sata etc, so, if that's the reason, I deduce I have to live with the different naming. But thit is based on a supposition: is it right?:) Thanks also to Geir and Ryan for pointing me at the right direction:) ciao! Carotinho Chiacchiera con i tuoi amici in tempo reale! http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com
On Mittwoch, 7. Mai 2008 19:13 Carotinho wrote:
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.
At first sorry that i don't answer your question and gives you instead a hint. I use for a very long time labels for my partitions and i can say that this is a very good method to avoid problems in such cases instead there be some others too. Example from my fstab: LABEL=archroot / jfs defaults,relatime 1 1 LABEL=archboot /boot ext2 defaults,relatime 1 2 LABEL=home /home jfs defaults,relatime 0 2 LABEL=arch64boot /mnt/arch64/boot ext2 defaults,noauto,relatime 0 0 LABEL=arch64root /mnt/arch64/root jfs defaults,noauto,relatime 0 0 For ext2 you can give the the label without the need of formating the partiton (-L option in the most cases for mkfs.*) but for the other filesystems i don't know this exactly. Lately some distros start using UUID but i'm personaly not a fan of this because they be "not so much readable". -) See you, Attila
Hi! Il Thursday 08 May 2008 20:46:57 Attila ha scritto:
I use for a very long time labels for my partitions and i can say that this is a very good method to avoid problems in such cases instead there be some others too.
Yes I think I'm going to switch to using labels! It's really clean and nice, indeed!
For ext2 you can give the the label without the need of formating the partiton (-L option in the most cases for mkfs.*) but for the other filesystems i don't know this exactly.
There's something on the wiki about other filesystems, I saw Thanks:) ciao! Carotinho Chiacchiera con i tuoi amici in tempo reale! http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com
On Donnerstag, 8. Mai 2008 21:20 Carotinho wrote:
Yes I think I'm going to switch to using labels! It's really clean and nice, indeed!
Sorry, i forgot in my first posting that this is only the half of the story because you can use labels with grub too. If you will have labels for your partitions than you should look for the names in /dev. $ ls -l /dev/disk/by-label/ insgesamt 0 lrwxrwxrwx 1 root root 11 10. Mai 09:19 DATEN32 -> ../../sda11 lrwxrwxrwx 1 root root 10 10. Mai 09:19 arch64boot -> ../../sda7 lrwxrwxrwx 1 root root 10 10. Mai 09:19 arch64root -> ../../sda8 lrwxrwxrwx 1 root root 10 10. Mai 09:19 archboot -> ../../sda5 lrwxrwxrwx 1 root root 10 10. Mai 09:19 archroot -> ../../sda6 lrwxrwxrwx 1 root root 11 10. Mai 09:19 home -> ../../sda10 lrwxrwxrwx 1 root root 10 10. Mai 09:19 system -> ../../sda1 Than use the editor of your choice and replace the value of "root=". Example from my menu.lst (i cut my options to avoid line breaks): # Arch Linux title Arch Kernel root (hd0,4) kernel /vmlinuz26 root=/dev/disk/by-label/archroot ro initrd /kernel26.img After this it should not matter if the kernel devs decide to use other device names in the future. -) See you, Attila
Hi! Il Saturday 10 May 2008 09:37:43 Attila ha scritto:
After this it should not matter if the kernel devs decide to use other device names in the future. -)
See you, Attila
Ok thanks again:) ciao! Carotinho Chiacchiera con i tuoi amici in tempo reale! http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com
participants (5)
-
Attila
-
Carotinho
-
Geir Arveschoug Erikstad
-
Michal Soltys
-
Ryan Sims