Oh, thanks for the response gapan.
It seems that I am the only Salix user with this problem, but a search reveals that it is a known issue. Unfortunately blacklisting is not an option for me because my hardware actually needs that module.
Code: Select all
193 /home/ladi$ /sbin/lspci | grep SB
00:11.0 SATA controller: ATI Technologies Inc SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode] (rev 40)
00:12.0 USB Controller: ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:12.2 USB Controller: ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:13.0 USB Controller: ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:13.2 USB Controller: ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 42)
00:14.1 IDE interface: ATI Technologies Inc SB7x0/SB8x0/SB9x0 IDE Controller (rev 40)
00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) (rev 40)
00:14.3 ISA bridge: ATI Technologies Inc SB7x0/SB8x0/SB9x0 LPC host controller (rev 40)
00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge (rev 40)
00:14.5 USB Controller: ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB OHCI2 Controller
00:16.0 USB Controller: ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:16.2 USB Controller: ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB EHCI Controller
Apparently it is to do with some offset address being changed, so the newer kernels do not have that problem.
http://comments.gmane.org/gmane.linux.kernel/1341706
I should have mentioned that I tried with ACPI both on and off in the BIOS, but it made no difference whatsoever. The only way I have been able to get it to even boot was to remaster the ISO and change the kernel to 3.6.9. (I use kernel 3.6.9 just fine with Salix64-XFCE-13.37 on the same PC)
Unfortunately, I did not get it quite right, and now I get up to the login screen but my mouse and keyboard wouldn't work because of some udev issues

Anyway, I am still working on that, and I would like to learn to remaster the ISO just for the fun of it. Meanwhile I have had to go back to 13.37, so I have a working system until I can create a working custom ISO.