Bug#386916: marked as done (linux-image-2.6.17-2-686: can't boot up)
Your message dated Tue, 12 Sep 2006 19:36:12 +0200
with message-id <20060912173611.GH4868@baikonur.stro.at>
and subject line Bug#386916: linux-image-2.6.17-2-686: can't boot up
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
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 Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-686-smp
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages linux-image-2.6.17-2-686 depends on:
ii initramfs-tools [linux-initra 0.77b tools for generating an initramfs
ii module-init-tools 3.2.2-3 tools for managing Linux kernel mo
Versions of packages linux-image-2.6.17-2-686 recommends:
ii libc6-i686 2.3.6.ds1-4 GNU C Library: Shared libraries [i
-- debconf information:
linux-image-2.6.17-2-686/postinst/old-initrd-link-2.6.17-2-686: true
linux-image-2.6.17-2-686/postinst/old-dir-initrd-link-2.6.17-2-686: true
linux-image-2.6.17-2-686/preinst/lilo-initrd-2.6.17-2-686: true
linux-image-2.6.17-2-686/postinst/depmod-error-initrd-2.6.17-2-686: false
linux-image-2.6.17-2-686/postinst/create-kimage-link-2.6.17-2-686: true
linux-image-2.6.17-2-686/preinst/lilo-has-ramdisk:
linux-image-2.6.17-2-686/preinst/already-running-this-2.6.17-2-686:
linux-image-2.6.17-2-686/preinst/bootloader-initrd-2.6.17-2-686: true
linux-image-2.6.17-2-686/preinst/initrd-2.6.17-2-686:
linux-image-2.6.17-2-686/preinst/abort-install-2.6.17-2-686:
linux-image-2.6.17-2-686/preinst/elilo-initrd-2.6.17-2-686: true
shared/kernel-image/really-run-bootloader: true
linux-image-2.6.17-2-686/preinst/failed-to-move-modules-2.6.17-2-686:
linux-image-2.6.17-2-686/postinst/bootloader-test-error-2.6.17-2-686:
linux-image-2.6.17-2-686/prerm/removing-running-kernel-2.6.17-2-686: true
linux-image-2.6.17-2-686/preinst/abort-overwrite-2.6.17-2-686:
linux-image-2.6.17-2-686/postinst/old-system-map-link-2.6.17-2-686: true
linux-image-2.6.17-2-686/preinst/overwriting-modules-2.6.17-2-686: true
linux-image-2.6.17-2-686/postinst/kimage-is-a-directory:
linux-image-2.6.17-2-686/prerm/would-invalidate-boot-loader-2.6.17-2-686: true
linux-image-2.6.17-2-686/postinst/depmod-error-2.6.17-2-686: false
linux-image-2.6.17-2-686/postinst/bootloader-error-2.6.17-2-686:
--- End Message ---
--- Begin Message ---
On Tue, Sep 12, 2006 at 06:06:27PM +0800, LI Daobing wrote:
> 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
ok bad cabling, will ask that queston sooner next time.
thanks for your feedback.
--
maks
--- End Message ---
Reply to: