You are not logged in.
If you want to boot wo/ an initrd then, no. If you don't care, it shouldn't matter.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
thanks for the help graysky - I think I found the problem though.
When creating the kernel image I am consistently getting an error pointing to SCSI Disk support:
# mkinitcpio -k 2.6.39.1 -g /boot/kernel26-2.6.39.1.img
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [autodetect]
:: Parsing hook [pata]
:: Parsing hook [scsi]
ERROR: module 'sd_mod' not found
:: Parsing hook [sata]
:: Parsing hook [filesystems]
:: Generating module dependencies
:: Generating image '/boot/kernel26-2.6.39.1.img'...SUCCESS
The odd thing is that when I look at 'menu makeconfig' it's already configured as 'M'.
I'm trying it 'built-in' to the kernel to see how it goes...is this normal?
Offline
Not normal:
[2011-06-11 06:21] Running 'pacman -U /dev/shm/kernel26-ck/kernel26-ck-1:2.6.39.1-2-x86_64.pkg.tar.xz /dev/shm/kernel26-ck/kernel26-ck-headers-1:2.6.39.1-2-x86_64.pkg.tar.xz'
[2011-06-11 06:24] >>> Updating module dependencies. Please wait ...
[2011-06-11 06:24] >>> MKINITCPIO SETUP
[2011-06-11 06:24] >>> ----------------
[2011-06-11 06:24] >>> If you use LVM2, Encrypted root or software RAID,
[2011-06-11 06:24] >>> Ensure you enable support in /etc/mkinitcpio.conf .
[2011-06-11 06:24] >>> More information about mkinitcpio setup can be found here:
[2011-06-11 06:24] >>> http://wiki.archlinux.org/index.php/Mkinitcpio
[2011-06-11 06:24]
[2011-06-11 06:24] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2011-06-11 06:24] ==> Building image "default"
[2011-06-11 06:24] ==> Running command: /sbin/mkinitcpio -k 2.6.39-ck -c /etc/mkinitcpio.conf -g /boot/kernel26-ck.img
[2011-06-11 06:24] :: Begin build
[2011-06-11 06:24] :: Parsing hook [base]
[2011-06-11 06:24] :: Parsing hook [udev]
[2011-06-11 06:24] :: Parsing hook [autodetect]
[2011-06-11 06:24] :: Parsing hook [sata]
[2011-06-11 06:24] :: Parsing hook [filesystems]
[2011-06-11 06:24] :: Generating image '/boot/kernel26-ck.img'...SUCCESS
[2011-06-11 06:24] ==> SUCCESS
[2011-06-11 06:24] ==> Building image "fallback"
[2011-06-11 06:24] ==> Running command: /sbin/mkinitcpio -k 2.6.39-ck -c /etc/mkinitcpio.conf -g /boot/kernel26-ck-fallback.img -S autodetect
[2011-06-11 06:24] :: Begin build
[2011-06-11 06:24] :: Parsing hook [base]
[2011-06-11 06:24] :: Parsing hook [udev]
[2011-06-11 06:24] :: Parsing hook [sata]
[2011-06-11 06:24] :: Parsing hook [filesystems]
[2011-06-11 06:24] :: Generating module dependencies
[2011-06-11 06:24] :: Generating image '/boot/kernel26-ck-fallback.img'...SUCCESS
[2011-06-11 06:24] ==> SUCCESS
[2011-06-11 06:24] Changelog for new kernel release at http://kernelnewbies.org/Linux_2_6_39
[2011-06-11 06:24] upgraded kernel26-ck (1:2.6.39.1-2 -> 1:2.6.39.1-2)
[2011-06-11 06:24] upgraded kernel26-ck-headers (1:2.6.39.1-2 -> 1:2.6.39.1-2)
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
So how do I 'fix' it?
(I'm assuming building it into the kernel is going to stop the problem though).
Offline
Building into the kernel is only useful if you want to avoid using the initrd image completely. If you don't care, you have no reason to build it in. My advise is to start from the ARCH config/config.x86_64 file and carefully edit them if that is your goal. I'm guessing that you disabled some kernel option(s) that you box needs to boot.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Building into the kernel is only useful if you want to avoid using the initrd image completely. If you don't care, you have no reason to build it in. My advise is to start from the ARCH config/config.x86_64 file and carefully edit them if that is your goal. I'm guessing that you disabled some kernel option(s) that you box needs to boot.
I've been using the one from /proc/config.gz - in this last build I didn't remove anything - just 'loaded' it and saved it.
What's the difference between the two and where the heck do I pull the x86_64 from? My useless brain can't seem to find it locally
Offline
Use abs
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Yeah...shoulda thought of that. We'll see if I have time today.
Thanks graysky
Offline