Xen folks may choose a similar solution, but that’s for them to decide. All drives report the same issues logging not included here which is what had me looking at the controller. Comment 55 Joshua Scoggins This seems weird to me. I still have this issue with a Marvell 88SE and kernel v4. I’m an ESXi user who was pointed to this thread from here:
|Date Added:||21 January 2006|
|File Size:||8.52 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
It seems like you have another problem I can’t access the option rom on my controller either: Comment 43 Tom Wijsman Nanoxia Deep Silence I. Also, this card is unsupported on XenServer, so I don’t anticipate ant help from them to this end.
I do however, want to be of help, even though it only consists of testing the solution at hand, but there are some concerns that need to be cebtos. Tried installing Ubuntu IN Windows, installation went fine, restarted and nothing, here’s a pic: You can google it to get more information. What are the symptoms? Comment oh-itsme Comment 98 Elliott Can anybody confirm that the Marvell 88SE91xx marvfll are not compatible with linux?
Everything appears to be working. Comment 47 Tobias N Xen folks may choose a similar solution, but that’s for them to decide.
Originally Posted by parsec. I had contacted Supermicro about this, but support did not really seem to be aware of this issue, and no update for the controller was sent to me. Yes I think the issue would be fixed with the patch and the added PCI ids. While running the installation from the CentOS5.
Find More Posts by ardvark Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. Thanks for a fast reply. Last edited by ardvark71; at Comment 99 Elliott Hi Alex, I am using v3.
This is what I found. In any case, it should probably be handled in a separate bug. Unfortunately, lspci indicates that the Marvell chip is not using 88we9172 functions lspci upload to followso at this point I can’t tell if I’m on the right trail. So I guess the devices that has the error may be using a context entry with present bit 0.
Comment 40 Shawn Thanks Comment 51 Joshua Scoggins Yes, it’s definitely broken, but trivial to fix. Are you sure xentos seeing the same error?
I’m hitting this error on Fedora 3. Comment 9 Daniel Mayer This turned out to be more work than I expected