The one component that makes a big difference is the Autoload, even if it is a few bytes long. Bohs Hansen Guest Jun 29, Tried that station drivers image and it behaves exactly the same as you and images. According to your lspci report, you have 2 of the suspect cards, so it will be interesting to hear of your results. BB code is On. Works for me in 6.
|Date Added:||27 August 2004|
|File Size:||41.78 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
The one component that makes a big difference is the Autoload, even if it is a few bytes long. A friendly fellow Mike with the same problem has PM’d me and is trying to get the same to work and has gotten a bit further then me so far. I’m not sure whether it will correctly drive other controllers. Upstream commit ffe1cba df a8faba1 Testcase: Mrvell upgrade log present lunux fresh install dmi.
It would have been helpful to post the entire screen of MSU, to see if all the components are properly detected.
VFS Recycle even seems to be working smoothly. Also thought of buying a second card and just copying the flash from it. I must warn you that it is missing all inner Firmware components yes, Marvell is calling the whole image a Firmware and also an internal component as Firmwarewhich might not be important for non-RAID controllers, but it is 91220 missing the Loader, which is a component present in all other Firmwares.
Marvell SATA 88SE9125/88SE9120
Yeah I know, I had noticed this ID change back then in feburary link. Silviu, I’ve built a Lucid test kernel with the patch applied. So only the last part differs, don’t know what it means but could be just something system specific. Note that registered members see fewer ads, and ContentLink is completely disabled once you lunux in.
Email Required, but never shown. Click hereto adjust the content of jarvell private message. Sign up or log in Sign up using Google.
Marvell 88SE91xx SATA 3 PCIe controller – is it compatible?
Posted June 26, Please test the kernel and update this bug with the results. I will check if the flashing was done properly. If it had other subsystem ID, it is now replaced with a generic ID, but you can find the old one in ghost devices or in DriverStore. Do you remember if the fields in MSU were the same before the bad flash? Mavell a result, I’m marking this actively developed linux task Fix Released.
Here is an interesting from a SE that pic I have found on the internet. One other problem could arise from mixing components from different firmware versions.
[SOLVED] Ubuntu – Marvell SE SATA III Drivers
Forums New posts Search forums. You could repost on the Kernel-Bug-Tracker, so they will recieve another Mail, but i allready gave up on this matter Sorry Posted Marveol 25, These firmwares don’t fall from the tree, I have to assemble them with consideration for components selection, then double and triple check my work.