Initrd would have been created by install-kernel, which failed for you if
I remember right. This particular kernel has usb-ohci and the
keyboard/mouse built-in, so unless you have "/" on a scsi drive, you can
probably get away without it. You can make your own initrd with the
command:
/sbin/mkinitrd --ifneeded /boot/initrd-2.4.4-6.1mdk 2.4.4-6.1mdk
You'll also need to update /etc/yaboot.conf to use it, and run ybin. But
like I said, unless you are having a problem at boot, you likely don't
need it.
The problem you are having leaving X, sounds similar to one reported by
one of the employees with a TiBook. Apparently Benh does something a
little different with the aty driver that alleviates this problem, as the
same employee reported he did not see the problem with Ben's kernel. I am
downloading that source now to see if I can see what the difference is,
and try patching appropriately. I will need a volunteer to test, as I
don't have the problem here. Unfortunately, it's difficult to make a
kernel that performs well on all the various classes of machines.
Stew Benedict
--
MandrakeSoft OH/TN, USA http://perso.mandrakesoft.com/~sbenedict/
On Tue, 26 Jun 2001, Dippy Black wrote:
> I wonder if my shutdown and reboot problem may be related to the other
> problems being discussed. I tried force installing the package discussed but
> still having problems. Would there be some other config that needs doing
> after the installation.
>
> Another question i have arises from what is in /boot, keeping in mind I have
> symlinked back to the 2.2 kernel:
>
> lrwxrwxrwx 1 root root 23 Jun 26 13:06 System.map ->
> System.map-2.2.19-14mdk
>
> -rw-r--r-- 1 root root 246824 May 22 16:32
> System.map-2.2.19-14mdk
>
> -rw-r--r-- 1 root root 461010 Jun 20 14:10
> System.map-2.4.4-6.1mdk
>
> lrwxrwxrwx 1 root root 19 Jun 26 13:03 config ->
> config-2.4.4-6.1mdk
>
> -rw-r--r-- 1 root root 28822 Jun 20 14:10 config-2.4.4-6.1mdk
>
> -rw-r--r-- 1 root root 509957 Jun 20 09:30initrd-2.2.19-14mdk.img
>
> lrwxrwxrwx 1 root root 23 Jun 20 09:30 initrd-2.2.img ->
> initrd-2.2.19-14mdk.img
>
> lrwxrwxrwx 1 root root 23 Jun 25 17:04 initrd.img ->
> initrd-2.2.19-14mdk.img
>
> lrwxrwxrwx 1 root root 14 Jun 25 16:49 kernel.h ->
> kernel.h-2.4.4
>
> -rw-r--r-- 1 root root 441 Jun 25 16:53 kernel.h-2.4.4
>
> -rw-r--r-- 1 root root 0 Jun 20 09:31 mac-us-ext.klt
>
> -rw-r--r-- 1 root root 130 Jun 20 09:31 message
>
> lrwxrwxrwx 1 root root 20 Jun 26 13:04 vmlinuz ->
> vmlinuz-2.2.19-14mdk*
>
> lrwxrwxrwx 1 root root 20 Jun 20 09:30 vmlinuz-2.2 ->
> vmlinuz-2.2.19-14mdk*
>
> -rwxr-xr-x 1 root root 2343956 May 22 16:39 vmlinuz-2.2.19-14mdk*
>
> -rwxr-xr-x 1 root root 2774136 Jun 20 14:28 vmlinuz-2.4.4-6.1mdk*
>
>
> As you can see the only initrd.img is 2.2 no 2.4. Should a 2.4 version have
> been installed?
>
