Hi Gerd,
On Tuesday 10 May 2005 15:19, Gerd Knorr wrote:
> Robbie Dinn <robbie@xxxxxxxxxxxx> writes:
> > Any one else got any ideas?
>
> Had a look today, figured mkinitrd has a bug which causes it using the
> default kernel modules, not the xen kernel ones in case you have both
> -default and -xen installed (which most likely is the case).
>
> Try the patch below, rerun mkinitrd, reboot and see whenever it works
> better then.
>
> HTH,
>
> Gerd
>
> --- /sbin/mkinitrd.o 2005-05-10 14:52:30.201725832 +0200
> +++ /sbin/mkinitrd 2005-05-10 15:11:45.752785097 +0200
> @@ -1671,6 +1671,8 @@
> fi
>
> # Filter modules into fs and non-fs (driver) modules
> + fs_modules=""
> + drv_modules=""
> for module in $resolved_modules; do
> case $module in
> */kernel/fs/*)
both variables are local to mkinitrd_kernel(), so they don't need to be
initialized separately. The bug must be somewhere else, sorry.
Could you please run mkinitrd via bash so that we see the trace,
bash -x /sbin/mkinitrd?
Thanks,
--
Andreas Gruenbacher <agruen@xxxxxxx>
SUSE Labs, SUSE LINUX PRODUCTS GMBH
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home