![](https://seccdn.libravatar.org/avatar/7c8d44c6b8084760ec77c99f075de32d.jpg?s=120&d=mm&r=g)
On Tuesday, February 14, 2017 2:50:17 PM EST Mark Hounschell wrote:
I am running the same GA-990FXA-UD5 with the same CPU but with 16GB of memory. I did a "trial" install of Leap 42.2. I'm still running 13.2 with vanilla kernels. Just to get it installed I had to disable the IOMMU in the bios and set my memory to 4gb. "kernel command line mem=4096M". The reason was that the kernel version in the dist package has an AMD IOMMU bug. I was getting IOMMU page faults all over the place. But if the IOMMU was not enabled and running more than 4GB, the I/O devices have to use Dual Address Cycles (DAC) to access memory above that 4GB. And I have yet to see a MB that supports DAC reliably. So I was having major issues just getting everything installed. But once I got up and running with the latest kernel, I was then able to turn the IOMMU back on and run with the full 16GB of memory. I'm still running 13.2 on it now though.
I am running the Asus counterpart to that Gigabyte board with the FX-6300, the 970/950 chipset, and 8GB of RAM. IOMMU is disabled in the UEFI bios, I have seen no problems with that. But just fwiw, have you checked the disk? I had a lot of weird problems after multiple attempts clean installing 42.2. Finally I installed vanilla and applied each kernel update one at a time, checking journalctl after each reboot. The 4.4.36-8 kernel (but not the previous; strange) threw a disk access error at each boot. The disk had been running 13.2 fine for a long time, and SMART showed the disk as healthy. But a closer look revealed a large number of bad blocks. After installing to a different disk, all the problems are gone. Might be worth a look? --dg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org