Comment 5 for bug 150693

I will admit, I haven't confirmed this in *exactly* a Ubuntu way -- but I have confirmed the issue, and the fix is very simple -- at least in my case, it was much easier than the diff shown. The key is right here in the diff:

-# CONFIG_BLK_DEV_SIS5513 is not set
+CONFIG_BLK_DEV_SIS5513=m

Looking back at my own system, triple boot: Windows ME (got tired of paying the tax); Feisty; Gutsy.

From /boot/config-2.6.20-16-generic (feisty)
CONFIG_BLK_DEV_SIS5513=m

From /boot/config-2.6.22-14-generic (gutsy)
# CONFIG_BLK_DEV_SIS5513 is not set

I took the absolute last version of the 2.6.22 kernels from the official linux kernel archives (as opposed to the Ubuntu source). I then took my config-2.6.22-14-generic and allowed for the SIS5513 module to be built. I rebuilt the kernel and headers and installed them. I then rebooted my computer.

With the Ubuntu 2.6.22-14, my computer always hangs very quickly -- the progress bar shows a couple millimeters before the crash. Then it just takes several minutes to finally drop to a command line. With my newly compiled kernel with the SiS 5513 module available, the computer boots all the way to a normal command line (I'd probably have X, but I don't have the restricted drivers yet for the new kernel).

I am convinced that the solution here, and for everyone else dealing with SiS 5513 controllers is that the current compile of the kernel does not make the needed module available to us.