Re: Error message about cdrom tray open during boot
On 09 Jan 2008, Douglas A. Tutty wrote:
> On Wed, Jan 09, 2008 at 09:15:10AM +0000, Anthony Campbell wrote:
> > On 08 Jan 2008, Douglas A. Tutty wrote:
> > > On Tue, Jan 08, 2008 at 09:37:09AM +0000, Anthony Campbell wrote:
> > > > On 07 Jan 2008, Paul Johnson wrote:
> > > > > On Jan 7, 2008 6:57 AM, Anthony Campbell <ac@acampbell.org.uk>
> > > > > wrote:
> > > > >
> > > > > > hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Er ror }
> > > > > > Jan 7 10:32:50 corinthia kernel: hdc: drive_cmd: error=0x04 {
> > > > > > AbortedCommand } Jan 7 10:32:50 corinthia kernel: ide: failed
> > > > > > opcode was: 0xef
> > > > >
> > > > > Is your CDROM drive going bad?
> > > >
> > > > That'w what I'm wondering. But it wtill works OK. And why does the
> > > > message not appear with the other installation of Debian?
> > >
> > > Have you tried reinstalling the kernel?
> > >
> > Linux-image-2.6.18-4-686 is not available now. I tried the currently
> > available kernel (2.6.23) but this gave the same error and also
> > prevented X from working for some reason. I removed acpi-support and the
> > error went away.
>
> 2.6.23 is not in Etch. If you're running lenny or sid with a 2.6.18-4
> then you are seriously out of date. If you're running Etch with
> 2.6.18-4 then your are mildly out of date.
>
> Current kernel on Etch is 2.6.18-5 and there have been several security
> updates to it (without changing the version number). Ideally, you
> should have the linux-image-2.6 meta-package installed which always
> depends on the most recent stable version.
>
> Doug.
>
This is Sid. As I say, I tried the current kernel (2.6.23) there but for
some reason Icewm wouldn't start properly - it hung halfway through the
process. And the error message about /dev/hdc was there as well so it
doesn't seem to be a kernel problem.
Anthony
--
Anthony Campbell - ac@acampbell.org.uk
Microsoft-free zone - Using Linux Gnu-Debian
http://www.acampbell.org.uk (blog, book reviews,
on-line books and sceptical articles)
Reply to: