Jump to content
RESET Forums (homeservershow.com)
Sign in to follow this  
PeterC2609

E3-1265L / PCI-e?

Recommended Posts

GotNoTime

No, nothing gets recognised.

If other cards also don't get recognised then your CPU sounds faulty. The PCIe lanes for that slot are actually directly connected to the CPU. It doesn't go through the motherboard chipset.

 

As einsteinagogo mentions above, the E3-1265L isn't a widely available part and the CPUs that are available are pulled from old servers. Whoever made the servers contracted Intel to make these special CPUs. There is a very remote possibility that there were other changes as well that involved the PCIe bus but it seems unlikely to me and that most likely explanation is that the CPU has a fault. Are the pads on the bottom of the CPU all clean and undamaged?

Share this post


Link to post
Share on other sites
Shonk

try cleaning the underside of the cpu with iso-propanol and a cotton bud maybe one of the contacts has a film over it

Edited by Shonk

Share this post


Link to post
Share on other sites
PeterC2609

Sorry, I read the first question as wrong.

 

I thought it was asking if my satellite card showed up as something different in device manager?

 

I havent got another pcie card to try.

 

I'm going to buy a cheap pcei nic today and test that.

 

Thanks

Share this post


Link to post
Share on other sites
PeterC2609

UPDATE

 

I bought a cheap PCIe NIC.

 

Works perfectly.

 

So it must have something to do with the Satellite Card and the CPU?!

Share this post


Link to post
Share on other sites
gordan

It is most likely a duff CPU, specifically, some of the PCIe lanes are broken or disconnected, most likely the first PCIe lane going to the slot.

Some cards can handle such a broken situation and use a different (or a subset of) channels, others just outright don't show up when a lane is out of action.

I would hazard a guess that if you look at the number of lanes connected (e.g. lspci on Linux will show you) on the card that works, it will probably be fewer than you expect from the card's specification.

Share this post


Link to post
Share on other sites
PeterC2609

Hmm, whats the command/tool for windows??

Share this post


Link to post
Share on other sites
m48t04
Posted (edited)

Hi,

 

I know this is an old topic, but I have come across the same issue of non recognition of the TBS-6982 S2 satellite card with a Xeon E3-1260L processor in the Microserver Gen8.

 

Tried to contact Peter if he came across a resolution on the faulty CPU scenario etc, but perhaps he left the forum.

 

However, I had a newer TBS-6281 T2 terrestrial card that worked in the same slot, so I contacted TBS direct to ask them about this issue and the possibility the newer TBS-6902 S2 card may work based on the terrestrial card result and PCI bridge updates. I got this response:

 

Quote

 

For 6982 is using NXP 7160 PCI-E bridge , some new motherboard have not added PCI-E 1.0a support , so please have a try update the BIOS  to latest version, and set the PCI-E link speed to Gen1.

 

For 6902 it is using new PCI-E bridge which have not this issue you can use it.

 

 

This chipset does appear problematic: https://www.linuxtv.org/wiki/index.php/NXP_SAA716x 

 

I couldn't find any direct references in reference to the special order E3-126XL CPU's, but it does all kinda fall into place beyond a coincidence....

 

I have ordered a TBS-6902 based on this response.... and will update in due course.

 

Hope this helps anyone who finds this thread as the only result in Google regarding this issue between E2-1260L and TBS-6982 cards :)

 

Edited by m48t04

Share this post


Link to post
Share on other sites
m48t04

Hi,

 

Quote

So I have ordered a 6902 based on this response....

 

So the TBS6902 arrived and installed in the Gen8 Microserver with Xeon E3-1260L, seen immediately in BIOS, and works with TBS open source drivers:

 

[    4.510705] TBSECP3 driver 0000:07:00.0: MAC address 00:22:ab:f1:29:de
[    4.510773] i2c i2c-1: Added multiplexed i2c bus 5
[    4.510804] i2c i2c-1: Added multiplexed i2c bus 6
[    4.618794] i2c i2c-6: av201x: Airoha Technology AV201x successfully attached
[    4.618799] TBSECP3 driver 0000:07:00.0: DVB: registering adapter 0 frontend 0 (TurboSight TBS 6902 DVB-S/S2 )...
[    4.618862] dvbdev: DVB: registering new adapter (TBSECP3 DVB Adapter)
[    4.659789] [drm] Initialized mgag200 1.0.0 20110418 for 0000:01:00.1 on minor 0
[    4.738315] TBSECP3 driver 0000:07:00.0: MAC address 00:22:ab:f1:29:df
[    4.738384] i2c i2c-0: Added multiplexed i2c bus 7
[    4.738415] i2c i2c-0: Added multiplexed i2c bus 8
[    4.844817] i2c i2c-8: av201x: Airoha Technology AV201x successfully attached
[    4.844821] TBSECP3 driver 0000:07:00.0: DVB: registering adapter 1 frontend 0 (TurboSight TBS 6902 DVB-S/S2 )...
[    4.844910] TBSECP3 driver 0000:07:00.0: TurboSight TBS 6902 DVB-S/S2 : PCI 0000:07:00.0, IRQ 36, MMIO 0xfbfc0000
 

Seems it's also a Xeon issue with pci 1.0a seen on the Dell T20:

https://www.tbsdtv.com/forum/viewtopic.php?f=176&t=10001

 

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  



×
×
  • Create New...