You can get rid of these in /var/log/messages: Feb 6 17:33:01 pacific modprobe: modprobe: Can't locate module sound-slot-1 Feb 6 17:33:01 pacific modprobe: modprobe: Can't locate module sound-service-1-0 with this: # No 2nd sound card alias sound-slot-1 off alias sound-service-1-0 off in /etc/modules.confapparently some kde stuff and the flash plug in try for more than one sound card which is what is generating the error messages.
<!-- <!--#printenv--> -->to all of my html pages before including the cgi scripts. Otherwise, the environment variables were defined, but not set to anything. I gave up on trying to find the root cause.
VFS: Cannot open root device "LABEL=/" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)The most common advice given is to change your grub entry to something like root=/dev/hda2.
What most of the other posts on this topic don't include is the preceeding messages:
kernel: checking if image is initramfs...it isn't (no cpio magic); looks like an initrd kernel: Freeing initrd memory: 98k freed kernel: RAMDISK: Compressed image found at block 0 kernel: RAMDISK: incomplete write (-28 != 32768) 4194304
The root of the problem is that the default ramdisk size of 4096 is not big enough for the initrd used on Fedora. I presume the same problem exists on other systems.
Increasing your ramdisk size to 8192K will fix the problem. The config item is CONFIG_BLK_DEV_RAM_SIZE and it can be found under device drivers, then block devices in the configuration menus.
[mjfrazer@arctic linux-2.6.6]$ egrep 'INITRD|RAM_SIZE' .config CONFIG_BLK_DEV_RAM_SIZE=8192 CONFIG_BLK_DEV_INITRD=y [mjfrazer@arctic linux-2.6.6]$
ibook.mjfrazer.orgwhich are the two names configured in my DHCP server. This causes my ssh X forwarding to get messed up. It generates the error
ibook-eth.mjfrazer.org
Warning: No xauth data; using fake authentication data for X11 forwarding.Su'ing to root and running 'hostname ibook.mjfrazer.org' fixes it up. Note that every time you start X11.app, you get new xauth data, so you may need to restart X11 after you fix up the hostname.
bind: Address already in useerror for each LocalForward in my config. When I stopped using the FC distro kernel due to hangs with my Matrox G400 and my Via rhine based ethernet cards, I stopped seeing this error message. I reckon that it was due to the FC distro kernel enabling both IPv4 and IPv6, and the sshd trying to bind to 127.0.0.1 and :::::001 (or whatever the localhost address is in IPv6) at the same time.