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

Bug#426712: marked as done (linux-image-2.6.21-1-686)

Your message dated Wed, 17 Mar 2010 23:14:14 +0100
with message-id <20100317221414.GA3195@galadriel.inutil.org>
and subject line Re: Bug#426712: linux-image-2.6.21-1-686
has caused the Debian Bug report #426712,
regarding linux-image-2.6.21-1-686
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
426712: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=426712
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.21-1-686
Version: 2.6.21-4

System setup: Debian unstable, Reiser FS
Problem: After installing the package with dpkg and having the inird image automatically generated by mkinitrd, rebooting stops with the message: "Waiting for root file system" after loading the kernel. I did not make any changes to the grub configuration or fstab. Booting into the old kernel (2.6.18) works without problems.
Fix: Creating the initrd image with yaird instead of mkinitrd fixed the problem for me.
I hope this message ends up at the right place. Please forward it as you see appropriate. 

Best,

Peter

--- End Message ---
--- Begin Message --- 
On Tue, Jun 12, 2007 at 12:57:47AM +0200, maximilian attems wrote:
> hello,
> 
> On Mon, Jun 11, 2007 at 06:23:07PM -0400, Peter Wood wrote:
> > Hi,
> > 
> > Thanks for your help. I replaced all instances of hdX by sdX in my grub 
> > config and in fstab and that fixed the problem.
> 
> ok cool.
>  
> > I do want to point out that I am running the up-to-date 2.6.21 kernel 
> > contrary to what you were writing in your last e-mail.
> 
> hmm strange
> ah pata_sis defaults to yes so it is currently the only pata
> driver that is build.
> 
> so either we should disable PATA_SIS eplicitly or kick
> CONFIG_BLK_DEV_SIS5513

This bug is quite old and the driver has seen many changes. Closing,
the bug, if this still occurs with current kernels, please reopen.

Cheers,
        Moritz

--- End Message ---
Reply to: