Bug#386916: linux-image-2.6.17-2-686: can't boot up

2006-09-12 Thread maximilian attems
On Tue, 12 Sep 2006, LI Daobing wrote: On 9/12/06, maximilian attems [EMAIL PROTECTED] wrote: ok so it's loaded, did you have udev troubles and downgraded? I don't know what's the meaning of udev troubles yes it's name nc, sorry. really need the dmesg to see anything why your devices

Bug#386916: linux-image-2.6.17-2-686: can't boot up

2006-09-12 Thread LI Daobing
On 9/12/06, maximilian attems [EMAIL PROTECTED] wrote: On Tue, 12 Sep 2006, LI Daobing wrote: On 9/12/06, maximilian attems [EMAIL PROTECTED] wrote: ok so it's loaded, did you have udev troubles and downgraded? I don't know what's the meaning of udev troubles yes it's name nc, sorry.

Bug#386916: linux-image-2.6.17-2-686: can't boot up

2006-09-12 Thread LI Daobing
On 9/12/06, LI Daobing [EMAIL PROTECTED] wrote: On 9/12/06, maximilian attems [EMAIL PROTECTED] wrote: On Tue, 12 Sep 2006, LI Daobing wrote: On 9/12/06, maximilian attems [EMAIL PROTECTED] wrote: ok so it's loaded, did you have udev troubles and downgraded? I don't know what's the

Bug#386916: linux-image-2.6.17-2-686: can't boot up

2006-09-11 Thread maximilian attems
On Mon, Sep 11, 2006 at 12:08:57PM +0800, LI Daobing wrote: On 9/11/06, Steve Langasek [EMAIL PROTECTED] wrote: Yes, we definitely will need more info, since this kernel is of course working for many other users. For starters, we probably want the driver your disk normally uses, and the exact

Bug#386916: linux-image-2.6.17-2-686: can't boot up

2006-09-11 Thread LI Daobing
On 9/11/06, maximilian attems [EMAIL PROTECTED] wrote: lsmod output, dmesg output for starting points. in attachment(these log generated from 2.6.16 system) what is the last message you are seeing. Begin: waiting for root filesystem... ... -- LI Daobing Module Size Used

Bug#386916: linux-image-2.6.17-2-686: can't boot up

2006-09-11 Thread LI Daobing
On 9/11/06, maximilian attems [EMAIL PROTECTED] wrote: On Mon, Sep 11, 2006 at 08:20:13PM +0800, LI Daobing wrote: On 9/11/06, maximilian attems [EMAIL PROTECTED] wrote: lsmod output, dmesg output for starting points. in attachment(these log generated from 2.6.16 system) what is the

Bug#386916: linux-image-2.6.17-2-686: can't boot up

2006-09-11 Thread maximilian attems
On Mon, Sep 11, 2006 at 08:20:13PM +0800, LI Daobing wrote: On 9/11/06, maximilian attems [EMAIL PROTECTED] wrote: lsmod output, dmesg output for starting points. in attachment(these log generated from 2.6.16 system) what is the last message you are seeing. Begin: waiting for root

Bug#386916: linux-image-2.6.17-2-686: can't boot up

2006-09-11 Thread maximilian attems
On Mon, Sep 11, 2006 at 09:13:07PM +0800, LI Daobing wrote: On 9/11/06, maximilian attems [EMAIL PROTECTED] wrote: On Mon, Sep 11, 2006 at 08:20:13PM +0800, LI Daobing wrote: On 9/11/06, maximilian attems [EMAIL PROTECTED] wrote: lsmod output, dmesg output for starting points. in

Bug#386916: linux-image-2.6.17-2-686: can't boot up

2006-09-11 Thread maximilian attems
On Mon, Sep 11, 2006 at 09:51:06PM +0800, LI Daobing wrote: 0.78 is latest initramfs-tools in testing, update your box. you dont give a lot explanations on your trouble try to run and then reboot: update-initramfs -u done no change? I got a initramfs shell and I don't know how to deal

Bug#386916: linux-image-2.6.17-2-686: can't boot up

2006-09-11 Thread LI Daobing
On 9/11/06, maximilian attems [EMAIL PROTECTED] wrote: On Mon, Sep 11, 2006 at 09:13:07PM +0800, LI Daobing wrote: On 9/11/06, maximilian attems [EMAIL PROTECTED] wrote: On Mon, Sep 11, 2006 at 08:20:13PM +0800, LI Daobing wrote: On 9/11/06, maximilian attems [EMAIL PROTECTED] wrote:

Bug#386916: linux-image-2.6.17-2-686: can't boot up

2006-09-11 Thread LI Daobing
On 9/11/06, maximilian attems [EMAIL PROTECTED] wrote: On Mon, Sep 11, 2006 at 09:51:06PM +0800, LI Daobing wrote: 0.78 is latest initramfs-tools in testing, update your box. you dont give a lot explanations on your trouble try to run and then reboot: update-initramfs -u done no change?

Bug#386916: linux-image-2.6.17-2-686: can't boot up

2006-09-11 Thread maximilian attems
On Mon, Sep 11, 2006 at 10:22:59PM +0800, LI Daobing wrote: On 9/11/06, maximilian attems [EMAIL PROTECTED] wrote: please post it from there. it is important to know if that module got loaded. It is. I copy it from initramfs shell with my pen. ata_piix 11556 0 - Live 0xf089 piix 9476 0

Bug#386916: linux-image-2.6.17-2-686: can't boot up

2006-09-11 Thread LI Daobing
On 9/12/06, maximilian attems [EMAIL PROTECTED] wrote: ok so it's loaded, did you have udev troubles and downgraded? I don't know what's the meaning of udev troubles yes it's name nc, sorry. really need the dmesg to see anything why your devices are not there. it works. new log in

Bug#386916: linux-image-2.6.17-2-686: can't boot up

2006-09-10 Thread LI Daobing
Package: linux-image-2.6.17-2-686 Version: 2.6.17-8 Severity: grave Justification: renders package unusable can't boot up. I stop at find root device, I think the kernel does not detect my disk. It works fine under 2.6.16. If you need more information, please mail me. Thanks -- System

Bug#386916: linux-image-2.6.17-2-686: can't boot up

2006-09-10 Thread Steve Langasek
tags 386916 moreinfo severity 386916 important thanks On Mon, Sep 11, 2006 at 09:46:07AM +0800, LI Daobing wrote: Package: linux-image-2.6.17-2-686 Version: 2.6.17-8 Severity: grave Justification: renders package unusable can't boot up. I stop at find root device, I think the kernel does

Bug#386916: linux-image-2.6.17-2-686: can't boot up

2006-09-10 Thread LI Daobing
On 9/11/06, Steve Langasek [EMAIL PROTECTED] wrote: Yes, we definitely will need more info, since this kernel is of course working for many other users. For starters, we probably want the driver your disk normally uses, and the exact error messages printed out at boot time. driver maybe is:

Bug#386916: linux-image-2.6.17-2-686: can't boot up

2006-09-10 Thread LI Daobing
On 9/11/06, LI Daobing [EMAIL PROTECTED] wrote: On 9/11/06, Steve Langasek [EMAIL PROTECTED] wrote: Yes, we definitely will need more info, since this kernel is of course working for many other users. For starters, we probably want the driver your disk normally uses, and the exact error