mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christopher Lentocha <christopherericlentocha@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH 1/1] Fix 2 Acer FA100 NVMe SSDs from interfering in one PC
Date: Thu, 29 Jun 2023 21:29:59 -0400	[thread overview]
Message-ID: <35a40ad9-19f9-f072-acd4-dd5e51ec062f@gmail.com> (raw)


In order for 2 Acer FA100s to work in one PC (in the case of myself, a
Lenovo Legion T5 28IMB05), and not show one drive and not the other, and
sometimes mix up what drive shows up, these two lines of code need to be
added, and then both of the SSDs will show up and not conflict when
booting off of one of them, since if you boot off of one of the SSDs
without this patch, you may randomly get into a kernel panic or
initramfs if set up, else if you do merge this patch, there should
never be problems with booting or really anything at all.

Signed-off-by: Christopher Lentocha <christopherericlentocha@gmail.com>
---
 drivers/nvme/host/pci.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
index 48c60f7fda0b..4bb521a6b68f 100644
--- a/drivers/nvme/host/pci.c
+++ b/drivers/nvme/host/pci.c
@@ -3427,6 +3427,8 @@ static const struct pci_device_id nvme_id_table[] = {
 		.driver_data = NVME_QUIRK_BOGUS_NID, },
 	{ PCI_DEVICE(0x1cc1, 0x5350),   /* ADATA XPG GAMMIX S50 */
 		.driver_data = NVME_QUIRK_BOGUS_NID, },
+	{ PCI_DEVICE(0x1dbe, 0x5216),   /* Acer/INNOGRIT FA100/5216 NVMe SSD */
+		.driver_data = NVME_QUIRK_BOGUS_NID, },
 	{ PCI_DEVICE(0x1dbe, 0x5236),   /* ADATA XPG GAMMIX S70 */
 		.driver_data = NVME_QUIRK_BOGUS_NID, },
 	{ PCI_DEVICE(0x1e49, 0x0021),   /* ZHITAI TiPro5000 NVMe SSD */
-- 
2.38.1


                 reply	other threads:[~2023-06-30  1:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=35a40ad9-19f9-f072-acd4-dd5e51ec062f@gmail.com \
    --to=christopherericlentocha@gmail.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®