public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: deloptes <emanoil.kotsev@deloptes.org>
To: linux-scsi@vger.kernel.org
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: SSD SATA 3.3 and Broadcom / LSI SAS1068E PCI-Express Fusion-MPT SAS
Date: Wed, 16 Aug 2023 01:21:47 +0200	[thread overview]
Message-ID: <ubh1ab$147i$1@ciao.gmane.io> (raw)
In-Reply-To: 20230815231517.GA271814@bhelgaas

Bjorn Helgaas wrote:

> I saw some mention about BIOS knobs that controlled the minimum
> acceptable SATA link speed or something; that's the kind of thing I
> wondered about.
> 

You surely mean the SAS1068E controller. I'll have to look into the
documentation. Thanks for the advice.

>> As mentioned in the other posting I will attach those SSDs directly to
>> the mobo. There are 6 SATA ports there. I think this is the best
>> approach. But you know curiosity is a force you can not resist, so I
>> still want to know why?! :)
> 
> Haha, yeah, I know!  I noticed in your response to Sathya that you're
> running a 4.19.288 kernel, which is really, really old.  If it's
> practical, the first thing I would try is booting a current kernel,
> e.g., v6.4, on the chance that something has been fixed since v4.19.
> I didn't try to compare the mptsas driver to see if it has changed
> since then, so I don't know whether it's likely.

I'll check and try in any case. Thanks for the advice.

I'll report back in Sept.

BR

-- 
FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0


  reply	other threads:[~2023-08-15 23:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ubgv7c$43t$1@ciao.gmane.io>
2023-08-15 23:15 ` SSD SATA 3.3 and Broadcom / LSI SAS1068E PCI-Express Fusion-MPT SAS Bjorn Helgaas
2023-08-15 23:21   ` deloptes [this message]
2023-09-25  1:06   ` deloptes
     [not found] <uba6vj$10n6$1@ciao.gmane.io>
2023-08-14 16:20 ` Bjorn Helgaas
2023-08-14 23:35   ` deloptes
2023-08-15 14:45     ` Sathya Prakash Veerichetty
2023-08-15 17:49     ` Bjorn Helgaas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='ubh1ab$147i$1@ciao.gmane.io' \
    --to=emanoil.kotsev@deloptes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox