Comment 7 for bug 150693

I don't understand how this does not meet the criteria. I see this in the criteria:

* Bugs which represent severe regressions from the previous release of Ubuntu

Now, this may not be a "severe regression" for everyone. But for many that own a computer with a SIS5513 IDE controller, going from a Feisty install where everything works, to a Gutsy install, where the system can't even boot because the IDE controller cannot recognize the hard drives -- that's a very severe regression! No solution has been presented that allows me to boot my computer with its SiS 5513 IDE controller without recompiling the kernel to include the necessary IDE module.

So, here's what I know in regard to the requested documentation:

1) Impact of the bug: Computers with SiS 5513 IDE controllers have reported everything from complete inability to boot, to very flaky disk access, even locking up the system. One proposed work-around was to force the ide_generic and ide_disk modules -- a "solution" that prevents the use of DMA in CD- / DVD-ROM drives connected to the computer. Thus, an unacceptable solution. That from my personal experience coupled with reports seen on the web forums.

2) I don't know of the bug being addressed in the "development" branch. But I can look back to former stable branches!!!

From the Feisty stock .config file:
CONFIG_BLK_DEV_SIS5513=m

From the Gutsy stock .config file:
# CONFIG_BLK_DEV_SIS5513 is not set

3) The patch: well, just correct the one line in the .config file in the kernel. That's it. Basically -- the module that the kernel folk have written for the SiS 5513 IDE controller should be allowed to be used by those of us with such a controller. Since this is built as a module, I would expect it to only be used by computers with the appropriate hardware. (Note: I tested with the ubuntu .config file, but with the latest 2.6.22 official Linux kernel -- if any Ubuntu-specific changes have been made to this module, there may be problems I am not aware of)

4) Reproducing the bug. I migrated my computer up from a Feisty install, so this *might* be a problem specific to migration, rather than new installs, but I doubt it. First: get a computer with a SiS 5513 IDE controller, as the error is specific to this hardware. Then try a) a fresh install with Gutsy, and b) a fresh install with Feisty, followed by a migration to Gutsy. I would expect both to cause problems. (I remember trying the new install. My computer crashed during the install, though I don't recall the specifics of where) If you're able to reboot successfully off of such a computer, and hdparm reports that DMA is settable for any CD- / DVD drives on the IDE controller, then something else is the problem. But I think you're going to find issues.

5) Regression potential: If you have a computer with a SiS 5513 IDE controller, migrating to Gutsy can bring your computer to a complete halt. If you can *somehow* tweak your computer to boot, even with this controller, than you'll probably find that the drives are not all working as they optimally should. This should only affect the users of this particular style of IDE controller, but the probalem for computers using this controller is widespread, if not all-encompassing.

According to my personal experience, SiS 5513 drivers were working fine from Hoary through Feisty, but the install of Gutsy has been problematic for this controller. Recompiling the kernel with this one extra module enabled brought my computer back to its pre-Gutsy working state.

I personally would be eager to test any proposed version of the kernel for usability on a computer with a SiS 5513 controller.

David Wynn