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

["LI Daobing" <lidaobing@gmail.com>]

On 9/12/06, LI Daobing <lidaobing@gmail.com> wrote:
> On 9/12/06, maximilian attems <maks@sternwelten.at> wrote:
> > On Tue, 12 Sep 2006, LI Daobing wrote:
> >
> > > On 9/12/06, maximilian attems <maks@sternwelten.at> 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 attachment
> >
> > confirms that 2.6.17 is not finding your disk
> > could you please try out 2.6.18-rc5 from trunk:
> > you find instructions:
> > http://wiki.debian.org/DebianKernel
>
> 2.6.18-rc5 and rc6 both failed, dmesg in attachment. I use following deb files:
>
> $ ls -l *.deb
> -rw-r--r-- 1 lidb lidb 16568456 2006-09-04 12:07
> linux-image-2.6.18-rc5-686_2.6.17+2.6.18-rc5-0experimental.1snapshot.7293_i386.deb
> -rw-r--r-- 1 lidb lidb 16701800 2006-09-09 20:07
> linux-image-2.6.18-rc6-686_2.6.17+2.6.18-rc6-0experimental.1snapshot.7377_i386.deb

Hello,

I find a workaround/solution to this bug.

everything become good after I switch the SATA cable for one socket(?)
on motherboard to another socket. But after switch back to the origin
one, I can reproduce this bug.

I am sorry that wasting so many time of yours. I didn't think this bug
maybe cause by hardware.

you can close this bug now.

--
LI Daobing