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

Bug#334123: linux-image-2.6.13-1-k7: 2.6.12 works OK, 2.6.13 doesn't



On Sat, Oct 15, 2005 at 09:08:17PM +0200, Ralf Hildebrandt wrote:
> On Saturday 15 October 2005 20:38, you wrote:
> 
> > > Versions of packages linux-image-2.6.13-1-k7 depends on:
> > > ii  initrd-tools                  0.1.82     tools to create initrd
> > > image for p ii  module-init-tools             3.2-pre9-2 tools for
> > > managing Linux kernel mo
> > >
> > > linux-image-2.6.13-1-k7 recommends no packages.
> >
> > 2.6.13-1 cannot work with initrd-tools, try using initramfs-tools or
> > yaird instead and see if this solves your problem.
> 
> a) Why does it depend on initrd-tools instead of  initramfs-tools then?

Well, it is an experimental package, it was buggy, this is fixed in SVN and
will be solved for the next upload, and we have grander plans for this, which
are currently being implemented.

> b) It does indeed work, except for USB, it boots, it loads modules.
> c) If I tinker with boot options ( "irqpoll noapic lapic"), I even get 
> USB to work
> d) 
> # apt-get install  initramfs-tools
> Reading package lists... Done
> Building dependency tree... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> 
> Since you only requested a single operation it is extremely likely that
> the package is simply not installable and a bug report against
> that package should be filed.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>   initramfs-tools: Depends: busybox-cvs-static (>= 20040623-1) but it is 
> not installable

Oh well, try yaird then, i hesitated in proposing this one, but i guess it is
a good idea, since initramfs-tools is currently broken. You need to set :

ramdisk=/usr/sbin/mkinitrd.yaird

or something such in /etc/kernel-img.conf and rerun dpkg-reconfigure on the
kernel image.

Friendly,

Sven Luther




Reply to: