Re: Kernel 2.6.0-testX show stoppers
And thus we see that Roberto Sanchez said, :
I am having some problems getting 2.6.0-test11 working on my 2 Sid
<snip>
I am also receiving the following errors on boot when my scripts
set up the parameters on my HDD and CD/DVD:
hda: dma_intr: status=0x58 { DriveReady SeekComplete DataRequest }
hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hda: drive not ready for command
hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hda: drive not ready for command
hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hda: DMA disabled
hda: drive not ready for command
hda: set_drive_speed_status: status=0x58 { DriveReady SeekComplete
DataRequest }
<snip>
Hi Roberto,
There is an option called IDEDISK_MULTI_MODE which describes the problem
that you are having (well except that it describes status=0x51; but hey,
it somethings just work). I found it while inspecting the config for the
kernel when I installed it on a test box. Hmm, so far 2.6-test11 is
working good. Well here is the way to get to that option if you do "make
xconfig" (the QT graphical config):
Go in the tree to
Device Drivers
--> ATA/ATAPI/MFM/RLL Support
--> Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support
--> Include IDE/ATA-2 DISK support
--> []'Use multi-mode by default'
And make sure that the option is "y" or is ticked (you need to compile
its parents into the kernel and not as modules to be able to acheive
this. If you don't, then your IDE drive wouldn't work anyway! :) [I
didn't need this option for my drive; but I looked at it anyway. Hey I
guess it saved some of your time.]
And as a word to anyone else having an IDE disk; make *SURE* to compile
the IDE stuff and your filesystem *directly* into the kerenel (e.g. ext3
driver) or it will not boot at all. I had to compile the kernel twice
before I realized this!! :) I wonder why I never had to bother with 2.4.x .
Good luck,
--
Harshwardhan Nagaonkar
Electrical Engineering Sysop
Brigham Young University, UT-84602
Reply to: