On Wed, Apr 02, 2008 at 05:36:04PM +0900, Atsuhito Kohda wrote: > On Wed, 2 Apr 2008 09:59:58 +0200, maximilian attems wrote: > > > On Wed, Apr 02, 2008 at 02:26:00PM +0900, Atsuhito Kohda wrote: > > > I encountered a problem recently on my alpha machine > > > running Debian testing. > > > > > > linux-image-2.6.22-3-alpha-generic was failed to boot > > > if I used initramfs-tools to generate initrd.img but > > > it booted successfully with initrd.img generated by yaird. > > > > please report the boot failure against initramfs-tools. > > I'd need to know more like the error message you saw > > and the content of the working initramfs versus non working. > > Okay, but the alpha is so critical for me, i.e. it works > as mail server and web server so it is rather difficult to debug. > When I reboot it, I'll test an initrd.img by initramfs-tools > and write down the error messages as far as I can.
add an rootdelay=9 (maybe a bit higher for alpha) bootparam, makes the wait for the rescue console where you can see which devices are up better to bear. > > > > it seems to make people to lazy to report. > > 2.6.22 is 1/2 a year ago. > > I remembered 2.6.24 came down into testing only about > a week ago. I don't think I'm lazy here. sure but i was reffering to the initramfs-tools failure, who is the default tool and known to generaly work on alpha. thanks for quick reaction -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]