[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Grub hangs at stage 1.5 with cd drive in thinkpad



Hi Folks,
	Some time ago I started having problems with my cd drive in my R40 
Thinkpad. Sometimes it would be detected at boot, other times not.
I also started to get hangs at boot time (the thinkpad bios POST screen
and grub loading stage 1.5, hanging for about 30 secs) I thought the drive
was dying so I removed it and the hanging problem disappeared. Anyway,
after a while I found a cheap upgrade and put it in the machine, and
now I am back to having grub hang at stage 1.5. The drive seems to work ok, 
(can even boot from it) but there are a few errors in the logs regarding the
drive. Heres a few.

Jan  4 12:30:43 linux kernel:     ide1: BM-DMA at 0x1868-0x186f, BIOS
settings: hdc:pio, hdd:pio
Jan  4 12:30:43 linux kernel: hdc: probing with STATUS(0x51) instead of
ALTSTATUS(0x7f)
Jan  4 12:30:43 linux kernel: hdc: _NEC DVD+/-RW ND-6500A, ATAPI
CD/DVD-ROM drive
Jan  4 12:30:43 linux kernel: hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW
drive, 2048kB Cache, DMA
Jan  4 13:05:02 linux kernel: hdc: lost interrupt
Jan  4 13:05:02 linux kernel: hdc: status error: status=0x58
{ DriveReady SeekComplete DataRequest }
Jan  4 13:05:02 linux kernel: hdc: drive not ready for command
Jan  4 13:05:07 linux kernel: hdc: status timeout: status=0xd8 { Busy }
Jan  4 13:05:07 linux kernel: hdc: DMA disabled
Jan  4 13:05:07 linux kernel: hdc: drive not ready for command
Jan  4 13:05:08 linux kernel: hdc: ATAPI reset complete
Jan  4 13:05:25 linux kernel: hdc: lost interrupt
Jan  4 13:05:25 linux kernel: hdc: status error: status=0x58
{ DriveReady SeekComplete DataRequest }
Jan  4 13:05:25 linux kernel: hdc: drive not ready for command
Jan  4 13:05:30 linux kernel: hdc: status timeout: status=0xd8 { Busy }
Jan  4 13:05:30 linux kernel: hdc: drive not ready for command
Jan  4 13:05:30 linux kernel: hdc: ATAPI reset complete
Jan  4 13:05:48 linux kernel: hdc: lost interrupt
Jan  4 13:05:48 linux kernel: hdc: status error: status=0x58
{ DriveReady SeekComplete DataRequest }
Jan  4 13:05:48 linux kernel: hdc: drive not ready for command
Jan  4 13:05:53 linux kernel: hdc: status timeout: status=0xd8 { Busy }
Jan  4 13:05:53 linux kernel: hdc: drive not ready for command
Jan  4 13:05:53 linux kernel: hdc: ATAPI reset complete
Jan  4 13:05:53 linux kernel: hdc: tray open
Jan  4 13:05:53 linux kernel: end_request: I/O error, dev hdc, sector 64
Jan  4 13:05:53 linux kernel: isofs_fill_super: bread failed, dev=hdc,
iso_blknum=16, block=16
Jan  4 13:12:52 linux kernel:     ide1: BM-DMA at 0x1868-0x186f, BIOS
settings: hdc:pio, hdd:pio
Jan  4 13:12:52 linux kernel: hdc: probing with STATUS(0x51) instead of
ALTSTATUS(0x7f)
Jan  4 13:12:52 linux kernel: hdc: _NEC DVD+/-RW ND-6500A, ATAPI
CD/DVD-ROM drive
Jan  4 13:12:52 linux kernel: hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW
drive, 2048kB Cache, DMA
Jan  4 13:12:52 linux kernel: hdc: lost interrupt
Jan  4 13:12:52 linux kernel: hdc: status error: status=0x58
{ DriveReady SeekComplete DataRequest }
Jan  4 13:12:52 linux kernel: hdc: drive not ready for command
Jan  4 13:12:52 linux kernel: hdc: status timeout: status=0xd8 { Busy }
Jan  4 13:12:52 linux kernel: hdc: DMA disabled
Jan  4 13:12:52 linux kernel: hdc: drive not ready for command
Jan  4 13:12:52 linux kernel: hdc: ATAPI reset complete
Jan  4 13:49:36 linux kernel: hdc: drive_cmd: status=0x51 { DriveReady
SeekComplete Error }
Jan  4 13:49:36 linux kernel: hdc: drive_cmd: error=0x04
{ AbortedCommand }
Jan  5 06:18:26 linux kernel:     ide1: BM-DMA at 0x1868-0x186f, BIOS
settings: hdc:pio, hdd:pio
Jan  5 06:18:26 linux kernel: hdc: probing with STATUS(0x51) instead of
ALTSTATUS(0x7f)
Jan  5 06:18:26 linux kernel: hdc: _NEC DVD+/-RW ND-6500A, ATAPI
CD/DVD-ROM drive
Jan  5 06:18:26 linux kernel: hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW
drive, 2048kB Cache, DMA 

Upgraded to the latest bios and controller, still no joy.
I imagine this is probably a hardware problem, as it happens before booting the kernel
just hoping to try and debug before thinking about buying a new motherboard for it. 
Any ideas to try and debug this welcome..

Regards



Reply to: