yes but I wasn't originally, i installed Ubuntu to make sure some form of Linux would work with it. It looks like a Kernel bug from a discussion i had with c0nv1ct earlier on IRC. i'm gonna try downloading 3.4e and see if it works with that unless i get a better option in the mean time.

When dual booting with boot loaders from other version of Linux, I sometimes run into a problem where SabayonLinux wants to look at everything as sda#, sdb#, etc..., but my other boot loader wants to refer to everything as hda#, hdb#, etc...

Then I usually get some sort of message indicating a valid boot device was not found, and it asks to enter a valid boot device.

Let me know if this sounds like your problem, and I can tell you some of my work-arounds.

no the problem is a compatability issue between the kernel revision for 3.4f and my motherboard's SATA controller by the looks of it. When Sabayon boots (with or without Ubuntu on the HDD) i can read the dmesg and see it loading the sata controller and picking up the hard disks existence but then just not doing anything with it. i'm hoping that 3.4e won't have this issue with being on a different kernel revision.

probably its a kernel issue and a patch is needed. to let our devs patch it, u should open a bug report on our bugzilla giving them all infos possible. they'll try to fix for next sabayon release.meantime u should try some boot cheat codes u find here: http://wiki.sabayonlinux.org/index.php? ... c_Hardware

i suggest trying noapic and/or acpi=off and/or all-generic-ide .. u can also try them combined writing them together separated by a space.make some try, maybe u are lucky.

The motherboard BIOS contains 3 options for the SATA Controller mode. RAID, SATA and AHCI. I had it set to SATA and it wouldn't work, changing it to AHCI fixes the problem.

Please note though, if your dual booting with Windows, make sure you have the chipset drivers installed in Windows before changing this setting as Windows cannot operate AHCI mode controllers without the drivers.