CentOS - Jan 2015 - Sun Microsystems Quad gigabit ethernet nic compatibility

On Thu, 2015-01-01 at 22:01 -0800, John R Pierce wrote:
> On 1/1/2015 9:41 PM, mechy2k2000 wrote:
> > Hello I am thinking of buying this card to and wanted  to know if this
NIC
> > is supported. The card is a Sun Microsystems PCI-X Quad-Port Gigabit
> > Ethernet Adapter QGEXPCI 501-6738-10. Can't find any info on how
well the
> > card plays with centos and also proxmox ve (if any of you use that
distro )
> 
> I've not tried that card on anything other than Sun UltraSparc running 
> Solaris 9 and 10, but rumor has it Linux has a 'cassini' driver
that
> supports the Sun GigaSwift NIC on those.
> 
> 
> 
> 
> 
I see. My gut is starting to tell me its not worth the time to replace
it, if this Sun NIC doesnt play nice with Linux. I also intend to use
the card with Proxmox VE which is debian based.  

~
Rafeal Stewart

On Fri, Jan 2, 2015 at 1:35 AM, Rafeal Stewart <mechy2k2000 at gmail.com>
wrote:
> On Thu, 2015-01-01 at 22:01 -0800, John R Pierce wrote:
> > On 1/1/2015 9:41 PM, mechy2k2000 wrote:
> > > Hello I am thinking of buying this card to and wanted  to know if
this
> NIC
> > > is supported. The card is a Sun Microsystems PCI-X Quad-Port
Gigabit
> > > Ethernet Adapter QGEXPCI 501-6738-10. Can't find any info on
how well
> the
> > > card plays with centos and also proxmox ve (if any of you use
that
> distro )
> >
> > I've not tried that card on anything other than Sun UltraSparc
running
> > Solaris 9 and 10, but rumor has it Linux has a 'cassini'
driver that
> > supports the Sun GigaSwift NIC on those.
> >
> >
> >
> >
> >
>
> I see. My gut is starting to tell me its not worth the time to replace
> it, if this Sun NIC doesnt play nice with Linux. I also intend to use
> the card with Proxmox VE which is debian based.
>
Why not instead buy an Intel Quad port NIC?
Something you _know_ will be well supported.

While I'm using a dual port PCI-X NIC and not a quad, I'm really happy
with
the compatibility (ethool can blink the LEDs) and have no complaints about
performance.

It is an Intel 82571EB using the e1000e kernel driver.
lspci (for one interface of the dual) output below:


~]# lspci -s 08:00 -vv
08:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet
Controller (rev 06)
Subsystem: Intel Corporation PRO/1000 PT Dual Port Server Adapter
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: 64 bytes
Interrupt: pin A routed to IRQ 31
Region 0: Memory at d5ee0000 (32-bit, non-prefetchable) [size=128K]
Region 1: Memory at d5ec0000 (32-bit, non-prefetchable) [size=128K]
Region 2: I/O ports at dce0 [size=32]
Capabilities: [c8] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: 00000000fee2000c  Data: 41d9
Capabilities: [e0] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal+ Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr+ FatalErr- UnsuppReq+ AuxPwr+ TransPend-
LnkCap: Port #1, Speed 2.5GT/s, Width x4, ASPM L0s L1, Latency L0 <4us, L1
<64us
ClockPM- Surprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x4, TrErr- Train- SlotClk+ DLActive- BWMgmt-
ABWMgmt-
Capabilities: [100 v1] 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: 14, GenCap- CGenEn- ChkCap- ChkEn-
Capabilities: [140 v1] Device Serial Number 00-15-17-ff-ff-3d-58-10
Kernel driver in use: e1000e
Kernel modules: e1000e


-- 
---~~.~~---
Mike
//  SilverTip257  //

On Jan 2, 2015 12:40 PM, "SilverTip257" <silvertip257 at
gmail.com> wrote:
>
> On Fri, Jan 2, 2015 at 1:35 AM, Rafeal Stewart <mechy2k2000 at
gmail.com>
> wrote:
>
> > On Thu, 2015-01-01 at 22:01 -0800, John R Pierce wrote:
> > > On 1/1/2015 9:41 PM, mechy2k2000 wrote:
> > > > Hello I am thinking of buying this card to and wanted  to
know if
this
> > NIC
> > > > is supported. The card is a Sun Microsystems PCI-X Quad-Port
Gigabit
> > > > Ethernet Adapter QGEXPCI 501-6738-10. Can't find any
info on how
well
> > the
> > > > card plays with centos and also proxmox ve (if any of you
use that
> > distro )
> > >
> > > I've not tried that card on anything other than Sun
UltraSparc running
> > > Solaris 9 and 10, but rumor has it Linux has a 'cassini'
driver that
> > > supports the Sun GigaSwift NIC on those.
> > >
> > >
> > >
> > >
> > >
> >
> > I see. My gut is starting to tell me its not worth the time to replace
> > it, if this Sun NIC doesnt play nice with Linux. I also intend to use
> > the card with Proxmox VE which is debian based.
> >
>
> Why not instead buy an Intel Quad port NIC?
> Something you _know_ will be well supported.
>
> While I'm using a dual port PCI-X NIC and not a quad, I'm really
happy
with
> the compatibility (ethool can blink the LEDs) and have no complaints about
> performance.
>
> It is an Intel 82571EB using the e1000e kernel driver.
> lspci (for one interface of the dual) output below:
>
>
> ~]# lspci -s 08:00 -vv
> 08:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet
> Controller (rev 06)
> Subsystem: Intel Corporation PRO/1000 PT Dual Port Server Adapter
> 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: 64 bytes
> Interrupt: pin A routed to IRQ 31
> Region 0: Memory at d5ee0000 (32-bit, non-prefetchable) [size=128K]
> Region 1: Memory at d5ec0000 (32-bit, non-prefetchable) [size=128K]
> Region 2: I/O ports at dce0 [size=32]
> Capabilities: [c8] Power Management version 2
> Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
> Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME-
> Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
> Address: 00000000fee2000c  Data: 41d9
> Capabilities: [e0] Express (v1) Endpoint, MSI 00
> DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <512ns, L1
<64us
> ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset-
> DevCtl: Report errors: Correctable- Non-Fatal- Fatal+ Unsupported-
> RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
> MaxPayload 128 bytes, MaxReadReq 512 bytes
> DevSta: CorrErr- UncorrErr+ FatalErr- UnsuppReq+ AuxPwr+ TransPend-
> LnkCap: Port #1, Speed 2.5GT/s, Width x4, ASPM L0s L1, Latency L0 <4us,
L1
> <64us
> ClockPM- Surprise- LLActRep- BwNot-
> LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
> ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
> LnkSta: Speed 2.5GT/s, Width x4, TrErr- Train- SlotClk+ DLActive- BWMgmt-
> ABWMgmt-
> Capabilities: [100 v1] 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: 14, GenCap- CGenEn- ChkCap- ChkEn-
> Capabilities: [140 v1] Device Serial Number 00-15-17-ff-ff-3d-58-10
> Kernel driver in use: e1000e
> Kernel modules: e1000e
>
>
> --
> ---~~.~~---
> Mike
> //  SilverTip257  //
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> http://lists.centos.org/mailman/listinfo/centos
This is for my personal home "server".  I have dual gigabit intel nic
PCIE
and it is nice knowing that, chances are no matter what distro I use that
the card will work. I see these "Pulled from working system" Sun quad
gigabit NICs  pcix on ebay for like 10 to 20 shipped thought I might ask
around.




On Fri, Jan 2, 2015 at 3:59 PM, Ned Slider <ned at unixmail.co.uk> wrote:
>
>
> On 02/01/15 06:01, John R Pierce wrote:
> > On 1/1/2015 9:41 PM, mechy2k2000 wrote:
> >> Hello I am thinking of buying this card to and wanted  to know if
this
> >> NIC
> >> is supported. The card is a Sun Microsystems PCI-X Quad-Port
Gigabit
> >> Ethernet Adapter QGEXPCI 501-6738-10. Can't find any info on
how well
> the
> >> card plays with centos and also proxmox ve (if any of you use that
> >> distro )
> >
> > I've not tried that card on anything other than Sun UltraSparc
running
> > Solaris 9 and 10, but rumor has it Linux has a 'cassini'
driver that
> > supports the Sun GigaSwift NIC on those.
> >
> >
> >
> >
> >
>
> The cassini.ko driver is present in el5 and el6, but Red Hat dropped
> support from RHEL7. If you want to use it on el7 then elrepo.org has
> packaged the driver for el7, backported from kernel-3.10.63:
>
> kmod-cassini-1.6-1.el7.elrepo.x86_64.rpm
>
> At present it's in the testing repo so do let us know if you try it and
> it works for you.
>
> Regards,
>
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
Thanks