Re: 2.6.15 -- unable to open an initial console

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Gaspar Bakos wrote:
Hi,

RE: Patrick's email:

Are you booting with an initrd?
If so there are instructions at http://fedora.redhat.com/docs/udev/

Indeed, I am booting with initrd.
At the last step of the kernel compile:

make O=/myper/usr/src/build-2.6.15.6 modules_install install \
	> ../build-2.6.15.6/make_install.LOG.3 2>&1 &

This "make install" actually invokes
  depmod -ae ...
and also
  [...]/linux-2.6.15.6/arch/x86_64/boot/install.sh

And this install.sh in turn invokes
   /sbin/new-kernel-pkg --mkinitrd --depmod --install $KERNEL_VERSION
which runs
   /sbin/mkinitrd --allow-missing -f /boot/initrd-2.6.15.6.img 2.6.15.6

So here we go, there is mkinitrd. I read the udev instructions, but
still don't get the point. Isn't mkinitrd (-4.2.15-1) supposed to take
care of all the udev business? In other words, which part of the
instructions did you refer to?

Cheers,
Gaspar


By default, the terminal display is not selected for the 2.6 kernel. This feature for the 2.6 kernel bit me in the 2.5 kernel days.

I forgot which option needs to be set to activate kernel messages from the kernel instead of sending them out a serial port. Have you checked that option.

Just an idea, I have not compiled and installed a kernel in a while.

Jim

--
Your computer's union contract is set to expire at midnight.


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux