This makes me wonder whether all the problems were due to a faulty cable and worse error correction under Linux So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel not a mainline one via: After the command above, I just need to do dmraid -s and my raid show up. May have to disabling the NCQ. No such file or directory cat: Still broken, same error. Is there a way to tell ahci to recognize Marvell Controller through Grub?

Uploader: Brall
Date Added: 7 February 2018
File Size: 8.18 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 64445
Price: Free* [*Free Regsitration Required]

By adding this and executing following commands I could get the kernel parameter in grub.

The above file locations are wrong! It may eventually be worked around in the kernel, but it’s not an easy fix.

You need to log in to change this bug’s status. Every time the Marvell controller is enabled, there is an endless boot time with above error messages of not recognizing the controller.

So look like the queue depth doesn’t help: This bug affects 1 person. There is a large number of bugs to go through and several of them have gone stale. This bug affects vanilla kernels up to and including 3. No such file or directory. Knowing what distro you selected may offer better guesses. This problem was never truly resolved and the Kernel mailing list didn’t provide any real answers either.


For more on this, please read the official Ubuntu documentation: Windows 7 CrystalDiskMark benchmarks: It happend with Fedora 16, 17 and now, Any ideas, any suggestions? This change was made by a bot. Can I change the location where the initialization script is looking for the vendor, type, etc. Where do I find that script?

Bug # “Marvell 88SE SATA controller problem with Xen ” : Bugs : Linux Mint

Browse Requests Reports Product Dashboard. Open Source Consulting Domain Registration.

After the command above, I just need to do dmraid -s and my raid show up. If you still experience this bug, please feel free to reopen the bug report.

Linux 下安装识别 Marvell 88SE91xx 硬盘

Sign up using Email and Password. Could you please test http: Sign up using Facebook. Following some further comments I reran the test – just in case something funny happens with the controller with dd, I created a fresh GPT table on the drive with a brand new ext4 partition spanning the entire drive and then copied a large linuxx to the drive. No issues booting into LM13 without Xen hypervisor! I have to completely disable the Marvell controller.


It sounds like the preferred solution is 88xe91xx quirk, and some of the infrastructure is in place, but it hasn’t been implemented yet. If this bug is fixed in the mainline kernel, please add the following tags: Post Your Answer Discard By clicking “Post Your Answer”, you acknowledge that you have read our updated terms of serviceprivacy policy and cookie policyand that your continued use of the website is subject to these policies.

Under Linux copies or writes failed – be it to the drive itself or to the NTFS partition from Windows, under Windows the drive benchmarked fine. I also replaced the SATA cable for the card and things seem to work.

The problem seems to be a design issue with the Marvell controller. However, as a maybe: