FYI -- I also had no problems in Feisty, but have been having *serious* issues in Gutsy with booting. I update /etc/intiramfs-tools/modules to include ide-generic, but that means -- no DMA. I also have a SIS5513 IDE controller. I was thinking of recompiling my own kernel, when I found this:
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
Why was this module turned off for Gutsy? Please allow this as a module again. As a module, it can do no harm to folks with other IDE drivers, but I'm guessing it could sure relieve some grief for those of us with this particular driver!
FYI -- I also had no problems in Feisty, but have been having *serious* issues in Gutsy with booting. I update /etc/intiramfs- tools/modules to include ide-generic, but that means -- no DMA. I also have a SIS5513 IDE controller. I was thinking of recompiling my own kernel, when I found this:
From /boot/config- 2.6.20- 16-generic (feisty) BLK_DEV_ SIS5513= m
CONFIG_
From /boot/config- 2.6.22- 14-generic (gutsy) BLK_DEV_ SIS5513 is not set
# CONFIG_
Why was this module turned off for Gutsy? Please allow this as a module again. As a module, it can do no harm to folks with other IDE drivers, but I'm guessing it could sure relieve some grief for those of us with this particular driver!