similar to: Survey says post your 3.3 volt Mother boards used in PRODUCTION withTE410

Hi list, I need a new mobo for my workstation. I'm planning to buy Asus Z97K or Asus Z97 Pro and install Centos 7. Anyone has experiences with these mobos? I need to know if Z97 chipset and NIC Realtek 8111GR are supported by C7. Another question about Intel I218V NIC installed on Asus Z97 Pro. Is it supported? I've ridden from google that Z97 chipset seems be supported by Linux but

Hi, Can anyone suggest a good motherboard for the T/E410P cards ? Coz it doesn't get inserted in the the regular P4 motherboards due to PCI slot (32 bit) .... Any suggestions. Regards Azher --------------------------------- Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software -------------- next part -------------- An HTML attachment was scrubbed... URL:

This afternoon I finally figured out more with regarding to a strange clock-slip problem we have on our asterisk box. We have two TE410s, in E1 mode: TE410P version c01a009b They have their own interrupts: 66: 781648298 783747388 IO-APIC-level t4xxp 233: 253890977 1311504670 IO-APIC-level t4xxp They have their full 31 channels: span=3,0,0,ccs,hdb3,crc4 bchan=63-77,79-93 dchan=78

Hi all, I'm going to configure a middle asterisk installation. I'll use a TE210P to connect a T1 channel bank and a PRI E1 line. I'm thinking on using a SuperMicro P8SCT Mother Board that has a 1x 64-bit 133MHz PCI-X 3.3V. In TE210P documentation I've read: The TE210P is a 32-bit 33MHz card keyed for 3.3 volt operation. Can SuperMicro slot (that is a 133Mhz slot) be used

  Hi, List ,I am searching any package on R which can do wavelet filtering for mother wavelet morlet ,is anybody having any script for the same ? I am new to the RwAVELET ANALSSIS.. THANKS IN ADVANCE ANIL KUMAR ANIL KUMAR( METEOROLOGIST) LRF SECTION  NATIONAL CLIMATE CENTER ADGM(RESEARCH) INDIA METEOROLOGICAL DEPARTMENT

Hello, I want to build a lightweight server and install centos. Does anyone have a recommendation for a suitable motherboard? Thank you, Joe

Response in-line: Op 22-04-17 om 13:22 schreef Karol Herbst: > info.min and info.max doesn't always represent the actual voltage range we > can use. Do the same as with the entry based volting. > > Fixes "ERROR: Can't get value of subfeature in0_min: Can't read" errors > in sensors. > > Signed-off-by: Karol Herbst <karolherbst at gmail.com> >

On Mon, Dec 1, 2014 at 3:38 PM, Terje Bergström <tbergstrom at nvidia.com> wrote: > On 29.11.2014 10:44, Alexandre Courbot wrote: >> On Fri, Nov 28, 2014 at 9:09 PM, Roy Spliet <seven at nimrod-online.com> wrote: >>> I'm not sure if I completely understand your reply, so forgive me if I am >>> stating some obvious things: >>> The reason why I

On Fri, Nov 28, 2014 at 8:12 PM, Vince Hsu <vinceh at nvidia.com> wrote: > Signed-off-by: Vince Hsu <vinceh at nvidia.com> Make sure you always write a short summary for your patches, even if the title sounds sufficient. At the very least this patch makes the code easier to read, so: Acked-by: Alexandre Courbot <acourbot at nvidia.com>

On 28/11/2014 12:13, Vince Hsu wrote: > The voltage value are calculated by the hardware characterized > result. > > Signed-off-by: Vince Hsu <vinceh at nvidia.com> > --- > > Resend this patch with the fuse change and proper patch prefix > per Thierry's request. Since the voltage table really is per-chipset, it would be insane to add that to the DT. If it was not

Some Kepler cards have no usefull header in the voltage table, which means nouveau has to read the voltages out of the entries directly. This patch fixes volting issues on those cards enabling them to switch cstates --- drm/nouveau/nvkm/subdev/bios/volt.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drm/nouveau/nvkm/subdev/bios/volt.c b/drm/nouveau/nvkm/subdev/bios/volt.c index

Some Kepler cards have no usefull header in the voltage table, which means nouveau has to read the voltages out of the entries directly. This patch fixes volting issues on those cards enabling them to switch cstates --- drm/nouveau/nvkm/subdev/bios/volt.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drm/nouveau/nvkm/subdev/bios/volt.c b/drm/nouveau/nvkm/subdev/bios/volt.c index

Some Fermi+ gpus have no usefull header in the voltage table, which means nouveau has to read the voltages out of the entries directly. The mask may be bigger than 0x1fffff, but this value is already >2V, so it will be fine for now. This patch fixes volting issues on those cards enabling them to switch cstates Signed-off-by: Karol Herbst <nouveau at karolherbst.de> Reviewed-by: Martin

On 21/03/16 18:16, Karol Herbst wrote: > min_id indicates a volt map entry which acts as a floor value, this will be > used to set the lower voltage limit through pstates > > Signed-off-by: Karol Herbst <nouveau at karolherbst.de> Do we really want to push reclocking logic to the volt subsystem? To me, volt should just allow you to read back and set a voltage. All the rest of

I am sure that those are a bit different on other GPUs, but while testing the error range compared to nvidia was around 100%+-3%. Without this change we are most of the time around 10% below nvidias voltage, so this change causes no harm and improves the situation a lot already. The remaining task for this is to figure out which of these constants are chip specific and from where to get the chip

if we calculate the voltage in the table right, we get all kinds of values, which never fit the hardware steps, so we use the closest higher value the hardware can do Signed-off-by: Karol Herbst <nouveau at karolherbst.de> --- drm/nouveau/nvkm/subdev/volt/base.c | 25 ++++++++++++++++++++++--- 1 file changed, 22 insertions(+), 3 deletions(-) diff --git

Some Fermi+ gpus have no usefull header in the voltage table, which means nouveau has to read the voltages out of the entries directly. The mask may be bigger than 0x1fffff, but this value is already >2V, so it will be fine for now. This patch fixes volting issues on those cards enabling them to switch cstates. Signed-off-by: Karol Herbst <nouveau at karolherbst.de> Reviewed-by: Martin

We always want a equal or higher voltage than the requested ones, otherwise nouveau undervolts. Signed-off-by: Karol Herbst <nouveau at karolherbst.de> --- drm/nouveau/nvkm/subdev/volt/gk104.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drm/nouveau/nvkm/subdev/volt/gk104.c b/drm/nouveau/nvkm/subdev/volt/gk104.c index 81788c2..9043dc8 100644 ---

Some Fermi+ gpus have no usefull header in the voltage table, which means nouveau has to read the voltages out of the entries directly. The mask may be bigger than 0x1fffff, but this value is already >2V, so it will be fine for now. This patch fixes volting issues on those cards enabling them to switch cstates. Signed-off-by: Karol Herbst <nouveau at karolherbst.de> Reviewed-by: Martin

if we calculate the voltage in the table right, we get all kinds of values, which never fit the hardware steps, so we use the closest higher value the hardware can do. v3: simplify the implementation Signed-off-by: Karol Herbst <nouveau at karolherbst.de> --- drm/nouveau/nvkm/subdev/volt/base.c | 22 +++++++++++++++++----- 1 file changed, 17 insertions(+), 5 deletions(-) diff --git