Jump to content
nico1995doom

Marvell 88SE9230 not working

12 posts in this topic Last Reply

Recommended Posts

But why would anyone want to disable virtualization for the drives? This means they will not work in a VM, right?

Share this post


Link to post
1 hour ago, fluisterben said:

But why would anyone want to disable virtualization for the drives? This means they will not work in a VM, right?

It's not just the drives, it disables passthrough for the whole machine. The reason they would want to do that is that they are not depending on hardware passthrough and they don't want to spend the money to replace the controller.

 

Not everyone has an unlimited tech budget, we make do with what we can.

Share this post


Link to post
Posted (edited)
50 minutes ago, jonathanm said:

It's not just the drives, it disables passthrough for the whole machine. The reason they would want to do that is that they are not depending on hardware passthrough and they don't want to spend the money to replace the controller.

 

Not everyone has an unlimited tech budget, we make do with what we can.

I asked because I have one of those controllers, a Delock Hybrid 4 x intern SATA 6 Gb/s card with the Chipset Marvell 88SE9230, not because I want to replace it with an even more expensive one. I thought this one was expensive enough.

I need the virtualization in unraid, and I'm just very surprised people settle for switching it off for this bug. It shows all drives in BIOS, in other OSs, yet I don't see it with the slackware of unraid. I tried patching the firmware, to no avail, I tried patching syslinux.cfg, to no avail. I've searched for days all over the internet, it's not solved by anything I found thus far.

This is really seriously bad, if I may say so.

The reason I say this is because when it works OK elsewhere, we're not inclined to expect it will simply fail in unraid, and thus we've not returned the card(s) in time for a refund. This beckons a hardware compatibility fail list that should be in unraid's wiki.

Edited by fluisterben

Share this post


Link to post
14 minutes ago, fluisterben said:

The reason I say this is because when it works OK elsewhere, we're not inclined to expect it will simply fail in unraid

This isn't an Unraid problem, it's a Linux problem with theses controllers and some kernels, this workaround usually works though.

Share this post


Link to post

It's up to the hardware manufacturer to provide drivers that work in Linux. They seem to have fallen behind on some kernels.

Share this post


Link to post
4 minutes ago, johnnie.black said:

This isn't an Unraid problem, it's a Linux problem with theses controllers and some kernels, this workaround usually works though.

That's not true, it's probably based somewhere in slackware, because I had it working just fine in debian 9.

And that workaround I already mentioned, it didn't make it work, unfortunately.

Share this post


Link to post

Different kernel, which goes back to manufacturer responsibility to provide working drivers.

Share this post


Link to post
11 minutes ago, fluisterben said:

it's probably based somewhere in slackware

No, depends on the kernel.

Share this post


Link to post
On 7/5/2019 at 8:40 PM, johnnie.black said:

No, depends on the kernel.

I've just checked, because I already decided to move the card out of the unraid server, and indeed, it does work for that debian, but only since it has all virtualization disabled. Wasn't even aware of that (it needs to be switched on!).

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.