Description of problem:
Boot on CD1 and wait until it is finished scanning for installation
(my root & boot FSs are on an ide disk, but the rest is on SCSI). Got
to console and do "fdisk -l" no SCSI disks appear.
Version-Release number of selected component (if applicable):
Fedora Core 3
Steps to Reproduce:
No eata module loaded. No SCSI disks present.
eata module loaded and SCSI disks present.
I tried "modprobe eata", but it appears that this module is not
This is an irritating bug since it "forced me" to perform a fresh installtion
(well, it was due, I have been upgrading since RH4.2). However, every update
kernel since has also lacked this driver which again "forces me" to recompile
the .src distribution.
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem. Please update to this new kernel, and
report whether or not it fixes your problem.
If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.
This is still the case:
[root@leia linux]# cat configs/kernel-2.6.12-i686.config | grep EATA
# CONFIG_SCSI_EATA is not set
this code is unmaintained upstream, and from a quick eyeball, looks very dated.
(It even implements its own queueing algorithm instead of using the block layer).
I'm surprised to hear that it even builds.
Given this is the only request we've had to enable this driver, I'm not overly
enthusiastic about enabling it.
I have been in contact with the maintainer of the driver, Dario Ballabio, and he
says he still maintains it if need be (even though, somebody has recently
reformated the code without his knowledge). He also claims that it does not have
its own queueing mechanism, and I quote "It is a standard compliant low level
driver, with the additional optional feature of sorting requests not yet sent to
I ask for a reconsideration. :)
The potential for problems is far greater than the benefits.
As mentioned above, yours is the only request we've ever had for this.
Now, if only I'm using the module, what potential problems could that be? ;-)
Seriously, I'm curious about the nature of these potential problems since the
author/maintainer of the driver does not seem to share your concerns.