You are not logged in.
Pages: 1
Hi all,
i have a two ide drives that are usually named hda and hdb and 2 usb external drives named sda and sdb, with ArchLinux those drive are all seen as sda, sdb, sdc, sdd.
The problem is that when i recmpile the kernel thay come back to hda/hdb and i must rename /etc/fstab to make it works; now can anyone tell me why with the default kernel those drives are all mapped to sda/sdb?
I don't know what kernel option is enabled...
Caranthir
Offline
I'm just guessing, but look for IDE SCSI emulation in your self-compiled kernel options... possibly it is the ide-scsi module. Otherwise it may be a udev issue.
Dusty
Offline
Don't know the option name - all I know is that some kernel releases ago IDE drives moved to a new "architecture" called libata, common with SATA. If it's enabled, they're sdX, if they use a legacy option, it's hdX.
Similarly, if you use ide hook in mkinitcpio, IDE drives are seen as hdX, if you use pata, it's sdX.
Last edited by lucke (2007-10-05 12:34:39)
Offline
You can set persisten block device names, then it doesn't matter what you use: http://wiki.archlinux.org/index.php/Per … ice_naming
Daniel
Last edited by ise (2007-10-05 12:39:07)
Offline
You can set persisten block device names, then it doesn't matter what you use: http://wiki.archlinux.org/index.php/Per … ice_naming
Daniel
I'll enable it later, right now i recompiling the kernel, maybe i've found what options i've to enable
see you later and thanks for the quick answers
Offline
Ok, i enabled the experimental support for libata under Device drivers and unchecked ide support, now with the custom kernel i have my ide drives named sda/sdb
I receive e few errors when installing the kernel (btw the PKGBUILD i use is the default one, i took it with abs):
loading package data... done.
checking dependencies... done.
cleaning up... done.
checking for file conflicts... done.
upgrading kernel26ck...
>>>
>>> If you use the LILO bootloader, you should run 'lilo' before rebooting.
>>>
>>> Updating module dependencies. Please wait ...
>>> MKINITCPIO SETUP
ERROR: module 'pata[-_]sis' not found
find: /lib/modules/2.6.22-ck: No such file or directory
>>> ----------------
ERROR: module 'ata[-_]generic' not found
>>> If you use LVM2, Encrypted root or software RAID,
>>> Ensure you enable support in /etc/mkinitcpio.conf .
>>> More information about mkinitcpio setup can be found here:
>>> http://wiki.archlinux.org/index.php/Mkinitcpio
>>> Generating initial ramdisk, using mkinitcpio. Please wait...
==> Building image "default"
==> Running command: /sbin/mkinitcpio -m "ATTENTION:\nIf you get a kernel panic below
and are using an Intel chipset, append 'earlymodules=piix' to the
kernel commandline" -k 2.6.22-ck -c /etc/mkinitcpio.conf -g /boot/kernel26ck.img
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [autodetect]
find: /lib/modules/2.6.22-ck: No such file or directory
find: /lib/modules/2.6.22-ck: No such file or directory
:: Parsing hook [pata]
:: Parsing hook [scsi]
:: Parsing hook [sata]
:: Parsing hook [usbinput]
:: Parsing hook [keymap]
:: Parsing hook [filesystems]
:: Generating image '/boot/kernel26ck.img'...SUCCESS
==> SUCCESS
find: /lib/modules/2.6.22-ck: No such file or directory
==> Building image "fallback"
ERROR: module 'BusLogic' not found
==> Running command: /sbin/mkinitcpio -m "ATTENTION:\nIf you get a kernel panic below
and are using an Intel chipset, append 'earlymodules=piix' to the
kernel commandline" -k 2.6.22-ck -c /etc/mkinitcpio.d/kernel26ck-fallback.conf -g /boot/kernel26ck-fallback.img
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [ide]
:: Parsing hook [scsi]
:: Parsing hook [sata]
:: Parsing hook [usbinput]
:: Parsing hook [raid]
:: Parsing hook [filesystems]
:: Generating image '/boot/kernel26ck-fallback.img'...SUCCESS
==> SUCCESS
done.
the BusLogic module is not compiled at all, i don't know why the script looks for it but i can enable in the next kernel
the modules pata_sis anda ata_generic and compiled statically in the kernel so ofc they aren't present as modules but they're enabled anyway...
don't know about the find errors onestly, ck is the localversion of the kernel but all modules are in /lib/modules/2.6.22
In the /etc/mkinitcpio.conf i've this line:
MODULES="pata_sis ata_generic"
that is probably causing this problem, it looks for these modules but ofc they can't be found
That said the script install the modules in pkg/lib/modules/2.6.22 instead of pkg/lib/modules/2.6.22-ck (as it should?), plus when i install the kernel it creates a initrd image that i don't use, the kernel starts even without it so i can remove it?
Caranthir
Offline
"I know nothing except the fact of my ignorance."
- Socrates
Offline
Pages: 1