All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 198975] Highpoint 840A RocketRAID Controller and drives are NOT detected by SCSI_HPTIOP kernel module
Date: Sat, 19 Nov 2022 17:40:04 +0000	[thread overview]
Message-ID: <bug-198975-11613-TEaMdP0XtN@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-198975-11613@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=198975

Carol Jams (adnanshaoun582@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |adnanshaoun582@gmail.com

--- Comment #8 from Carol Jams (adnanshaoun582@gmail.com) ---
(In reply to Jaym12 from comment #7)
> I fixed this error(In reply to Matthias Lippert from comment #0)
> > Hello,
> > 
> > This is my first kernel bugzilla report, so please have mercy ;-)
> > 
> > My freshly bought Highpoint 840A RocketRAID Controller and its 8 connected
> > "Samsung 860 EVO" ssd harddrives are NOT detected by the "SCSI_HPTIOP"
> > kernel low-level scsi driver module, but it seems to be the smaller brother
> > of the already from kernel supported 3740A RocketRAID controller by
> > Highpoint.
> > The only differnence seems to be that the 840A supports only 6Gb/s per
> > channel.
> > Thats is also confirmed by the top down view onto the expansion card.
> > In the upper right corner you can see the described dual product markings
> > "RocketRAID 3740A/840A", so the layout and most likely also the raid
> > processor of the controller has been used at least twice by Highpoint.
> > My controllers firmware is the recent 1.0.0 version.
> > I couldnt find any other driver module that is matching my controller more
> > closely.
> > The current published linux drivers by highpoint are useless under (Gentoo)
> > Linux.
> > The controller and its connected drives are working flawlessy under Windows
> > 10, so its not damaged. I am using a "Gigabyte X99-SLI" motherboard with
> > recent F24a bios version.
> > I am also willingly able to provide regular dump logs to kernel developers
> > for driver debugging.
> > 
> > I would be VERY thankful for including support into the next kernel for
> this
> > cool piece of hardware!
> > 
> > 
> > Top-down view onto the expansion card:
> > 
> > https://www.bhphotovideo.com/images/images1000x1000/
> > highpoint_rocketraid_3740a_12gb_s_pcie_1269779.jpg
> > 
> > 
> > dmesg outputs only this, then nothing else related to my controller:
> > 
> > RocketRAID 3xxx/4xxx Controller driver v1.10.0
> > 
> > 
> > lspci -kvv outputs this:
> > 
> > 02:00.0 RAID bus controller: HighPoint Technologies, Inc. Device 0840 (rev
> > a1)
> >         Subsystem: HighPoint Technologies, Inc. Device 0000
> >         Physical Slot: 6
> >         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> > Stepping- SERR+ FastB2B- DisINTx-
> >         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> > <TAbort- <MAbort- >SERR- <PERR- INTx-
> >         Latency: 0, Cache Line Size: 32 bytes
> >         Interrupt: pin A routed to IRQ 11
> >         NUMA node: 0
> >         Region 0: Memory at d0900000 (64-bit, prefetchable) [size=1M]
> >         Region 4: Memory at d0a00000 (64-bit, prefetchable) [size=256K]
> >         Expansion ROM at dfe00000 [disabled] [size=128K]
> >         Capabilities: [80] Power Management version 3
> >                 Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA
> > PME(D0+,D1+,D2-,D3hot+,D3cold-)
> >                 Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
> >         Capabilities: [90] MSI: Enable- Count=1/32 Maskable+ 64bit+
> >                 Address: 0000000000000000  Data: 0000
> >                 Masking: 00000000  Pending: 00000000
> >         Capabilities: [b0] MSI-X: Enable- Count=18 Masked-
> >                 Vector table: BAR=0 offset=00038000
> >                 PBA: BAR=0 offset=00039000
> >         Capabilities: [c0] Express (v2) Endpoint, MSI 00
> >                 DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s
> > <128ns, L1 <2us
> >                         ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
> > SlotPowerLimit 0.000W
> >                 DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
> > Unsupported-
> >                         RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
> >                         MaxPayload 256 bytes, MaxReadReq 512 bytes
> >                 DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr-
> > TransPend-
> >                 LnkCap: Port #0, Speed 8GT/s, Width x8, ASPM L0s L1, Exit
> > Latency L0s <128ns, L1 <2us
> >                         ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+
> >                 LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk-
> >                         ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
> >                 LnkSta: Speed 8GT/s, Width x8, TrErr- Train- SlotClk-
> > DLActive- BWMgmt- ABWMgmt-
> >                 DevCap2: Completion Timeout: Range B, TimeoutDis+, LTR-,
> > OBFF Not Supported
> >                 DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-,
> > LTR-, OBFF Disabled
> >                 LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance-
> SpeedDis-
> >                          Transmit Margin: Normal Operating Range,
> > EnterModifiedCompliance- ComplianceSOS-
> >                          Compliance De-emphasis: -6dB
> >                 LnkSta2: Current De-emphasis Level: -6dB,
> > EqualizationComplete+, EqualizationPhase1+
> >                          EqualizationPhase2+, EqualizationPhase3+,
> > LinkEqualizationRequest-
> >         Capabilities: [100 v2] Advanced Error Reporting
> >                 UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt-
> > RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
> >                 UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt-
> > RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
> >                 UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt-
> > RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
> >                 CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout-
> > NonFatalErr-
> >                 CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout-
> > NonFatalErr+
> >                 AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+
> > ChkEn-
> >         Capabilities: [300 v1] #19
> > 
> > 
> > Highpoints 800er series RocketRAID website:
> > 
> > http://www.highpoint-tech.com/USA_new/series-rr800-overview.htm
> > 
> > 
> > Highpoints 3700er series RocketRAID website:
> > 
> http://www.highpoint-tech.com/USA_new/series-rr3700-overview.htm
> 
> > I have been facing the same issue.
> > https://www.allhdd.com/seagate-st3000lm024-sata-6gbps-hdd/

You can use https://www.allhdd.com/samsung-mz-77q4t0-sata-ssd/ drive it is
working fine for me.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2022-11-19 17:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-198975-11613@https.bugzilla.kernel.org/>
2022-08-06 13:50 ` [Bug 198975] Highpoint 840A RocketRAID Controller and drives are NOT detected by SCSI_HPTIOP kernel module bugzilla-daemon
2022-11-19 17:40 ` bugzilla-daemon [this message]
2024-09-05 22:02 ` bugzilla-daemon

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=bug-198975-11613-TEaMdP0XtN@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.