Mailinglist Archive: opensuse (4344 mails)

[Sid Boyce <sboyce@xxxxxxxxxxxxxxxx>]

Donn Washburn wrote:
> Sid Boyce wrote:
>
> > Donn Washburn wrote:
> >
> > > Hey SuSE;
> > >
> > > You need to fix mkinitrd from mismatching kernel modules and the kernel.
> > >
> > > I decide to play with a xen kernel.  I put it in grub and rebooted.
> > > On reboot the xen  kernel complained about not having an initrd 
> > > file.   OK -> mkinitrd.
> > > Done!  That is when the problem showed up.  SuSE9.3 updated found the
> > > vmlinuz kernels just fine but the modules it assigned to a kernel is 
> > > always
> > > the " 2.6.11.4-21.7-default " modules.  Talk about a mismatch.
> >
> >
> >
> > I wonder what commandline options you gave with mkinitrd, the "-k 
> > <kernel>" and the "-i <INITRD_name>. I issue the command from /boot as 
> > a test just now didn't give me the initrd in /boot when run in another 
> > directory nor is it in that directory.
> > Regards
> > Sid.
>
> Just the basic let it find it method.  -> mkinitrd which used to find 
> all kernels and worked on any kernel
> that I compiled using a prefix "vmlinuz" and it did care about the suffix.
>
> Since you are also running 9.3 try it.  Just "mkinitrd" .
> There is a kernel variable in mkinitrd known as $kernel_image (line 106) 
> that seems to cause the mismatch

Screwy, I've never named my kernels e.g 2.6.12-1 renamed 
vmlinuz-2.6.12-1 and did mkinitrd, it completely ignored it, just built 
ones for the SuSE kernels.
For my own kernels, I do my own thing with naming on all distros here, 
SuSE, Mandriva and gentoo, e.g 2.6.13-rc3 and initrd2.6.13-rc3 via this 
script by doing "INITRD 2.6.13-rc3".
barrabas:~ # o /usr/local/mybin/INITRD
cd /boot; mkinitrd -k $1 -i initrd$1 -d /dev/hda1 -s 1024x768

Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot
Retired IBM Mainframes and Sun Servers Tech Support Specialist
Microsoft Windows Free Zone - Linux used for all Computing Tasks