On Thursday 18 February 2016 15:11:44 J. Roeleveld wrote: > On Thursday, February 18, 2016 12:05:14 PM Peter Humphrey wrote: --->8 > > Now that I think about it, I did update the AMI BIOS several weeks ago. > > It went from 1102 to 2101 - a bit of a step. Maybe that's what's broken > > my system - well, this bit of it, anyway. > > Could very well be the case.
In which case I'm stuck, because the BIOS's ez-flash utility won't let me go backwards in versions. Meanwhile I've flashed the latest one again just to see if it would make any difference (it hasn't), this time remembering to reset to defaults first. There is a BIOS option called "Addon ROM display mode" which seems to ask whether an expansion card's ROM should override the installed default, though it's hard to tell with the "pidgin" English. I'll try flipping that and see what happens. Later: nothing, as far as I can see. > Also, not sure if the following might help: > # zgrep -i iomm /proc/config.gz > CONFIG_GART_IOMMU=y > # CONFIG_CALGARY_IOMMU is not set > CONFIG_IOMMU_HELPER=y > CONFIG_IOMMU_API=y > CONFIG_IOMMU_SUPPORT=y > # Generic IOMMU Pagetable Support > CONFIG_IOMMU_IOVA=y > # CONFIG_AMD_IOMMU is not set > CONFIG_INTEL_IOMMU=y > CONFIG_INTEL_IOMMU_DEFAULT_ON=y > CONFIG_INTEL_IOMMU_FLOPPY_WA=y > # CONFIG_IOMMU_DEBUG is not set > # CONFIG_IOMMU_STRESS is not set Mine's the same. > # zgrep -i dmar /proc/config.gz > CONFIG_DMAR_TABLE=y Ditto. My options now seem to be to replace the motherboard, replace the display card, both of which are now just over six years old - or drop BOINC projects that use VirtualBox. Thanks for the help, Joost. If anyone else has any ideas I'd be grateful to hear them too. -- Rgds Peter
