[SOLVED] Trouble getting initrd-image to work

Question

Hello everyone
I'm trying to get plymouth to work and for that reason I'm messing with initrd images for the first time in my life.
I had no issues generating the image, but once I rebooted, nothing happened. It looks like lilo fails to load the image since I'm not getting the 'Loading initrd-blahblah.img........' message, although I'm not getting any error messages either. Basically it just loads kernel and boots normally like it's never heard of initrd images.
These are the lines I've changed in/etc/mkinitcpio.conf. Everything else is default.
MODULES="radeon"
HOOKS="base udev plymouth autodetect sata filesystems"
COMPRESSION="lzma"
running mkinitcpio.conf, no errrors there
# mkinitcpio -c /etc/mkinitcpio.conf -g /boot/initrd-$(uname -r).img
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [plymouth]
:: Parsing hook [autodetect]
:: Parsing hook [sata]
:: Parsing hook [filesystems]
:: Generating module dependencies
:: Generating image '/boot/initrd-2.6.35.4-ck1.img'...SUCCESS
/etc/lilo.conf:
lba32
boot=/dev/sdb
compact
prompt
timeout=50
default=2.6.35.4-ck1
read-only
root=/dev/sdb1
image=/boot/kernel-2.6.35.4-ck1
label=plymouth
initrd=/boot/initrd-2.6.35.4-ck1.img
append="quiet splash sata_nv.swncq=1 pci=nomsi snd-hda-intel.model=3stack snd-hda-intel.probe_mask=1 powernow-k8.vcore_list=1125,1125,825"
running lilo shows error message but I've been getting it since I installed arch, and it has been working fine nevertheless.
# lilo
/proc/misc: No entry for device-mapper found
Is device-mapper driver missing from kernel?
Failure to communicate with kernel device-mapper driver.
Added 2.6.35.4-ck1 *
Added plymouth
Added nokms
Added bootchart
Also I think it might be relevant to point out that I'm building my kernels by hand (no PKGBUILDs or anything).
Any ideas will be appreciated 
EDIT: solved. forgot to enable support for initramfs/initrd in kernel
Last edited by pussi (2010-09-17 06:47:47)

Answer 1

In the future you should never post valid IP addresses.
If you use DHCP addressing then the IP addresses are assigned automatically from the DHCP server. Your router contains a DHCP server that is used to provide local IP addresses to devices that share an IP address via NAT. You should not use a manual IP address on such a network unless it happens to be a local IP address. And it you do then the IP address must be in the range of IP addresses served by your router. Different routers serve different address ranges. Yours is serving in the range of 10.0.1.2 to 10.0.1.199. Your router currently assigns your machine the address of 10.0.1.2.
If you configure Network preferences to use DHCP with manual addressing then you can assign your computer the 10.0.1.2 address that is presently assigned by the router. The gateway IP address and network mask will still be assigned automatically by your router.
When you set up port forwarding the IP address to which the ports are forwarded should be the IP address used by your machine - 10.0.1.2 in the above example.
If your modem also has a built-in router then you must disable it. There should only be one active router in your network. It can be either the Airport Extreme or your modem's built-in router but not both. If you use your modem's built-in router then the IP addresses involved will no longer be in the 10.0.1.xxx range.