search for: reseating

...lasts the entire call. In some cases, the noise doesn't start until a minute or 2 into the call, while others last the entire call. In some of the more serious cases, calls are dropped after the noise has occurred as well. Another symptom has been really bad static on a specific channel. After reseating the card to try to fix both this as well as the problem above, the problem usually goes away, but it seems to come back quicker each time. Also, the channel that the static occurs on changes after each reseating (after some time). Could this just be a bad digium card? Or could it be a bad PCI bus...

Has anyone had any compatibility issues with a TE110P card installed on a Dell Poweredge 1950? I noted the following error on the LCD display of the Dell Poweredge 1950: E1711 PCI PErr Slot 1 E171F PCIE Fatal Error B0 D4 F0. The Dell hardware owners manual states that it means the system BIOS has reported a PCI parity error on a component that resides in PCI configuration space at bus 0,

I've never seen anything like this. We moved it from the data center yesterday, and this morning I plug it in, and it won't power up. I find a manual for it online, and it says that on plugging it in, wait 3 minutes. The power button will flash 4x/sec, then slow down to once a sec, and at that time you can power it up. Well, it never stops flashing at 4x/sec. I've connected a network

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Not new: I can remember seeing DEC engineers cleaning up the contacts on memory boards for a VAX 11/782 with a pencil eraser c.1985. It's still a pretty standard first fix to reseat a card or connector. On 18/01/16 15:47, Matt Garman wrote: > That's strange, I expected the SMART test to show some issues. > Personally, I'm still

...t the writes and scrubs yielded 0 errors. However, now that this disk works as part of a larger old pool (9*5-vdev raidz1 sets), it suffers CKSUM error counts found on every scrub. They tried to reseat the disk in the same position (and will soon try the ex-position of another failed disk), but reseating did not help. For some reason, while early high CKSUM counts led to ZFS degrading the pool, this no longer happens (and my questionable script to clear the errors during scrub is not in use anymore). Numbers of CKSUM errors vary, in no dependable pattern: 1852, 317, 146, 83, 32, 1063, 6, 163, 4...

Hi all, we're trying to install CentOS 5.1 on a Sun Ultra 40. This is an AMD-powered machine and we're using the x86_64 version of CentOS 5.1. The machine is using the NVidia CK804 chipset and has SATA disks. It also has 16GB's of memory which prompted us to upgrade the BIOS on the machine from 1.1 to 1.6 per this (we also have the two quadro cards):

...ecause when we plugged in the cable the light on the card did not light up.?? when we connect the pair server to another separate server it did.? Once the server is back up I will try these things that you suggest, and compare them to the pair server we are trying to connect to.? We are hoping that reseating the card will work.? Probably wishful thinking. Thx.KM From: Gordon Messmer <gordon.messmer at gmail.com> To: CentOS mailing list <centos at centos.org> Sent: Monday, February 13, 2017 12:08 PM Subject: Re: [CentOS] A question on networking (CentOS 6) On 02/13/2017 06:55...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I suspect that the gold layer on edge connectors 30-odd years ago was a lot thicker than on modern cards. We are talking contacts on 0.1" spacing not some modern 1/10 of a knat's whisker. (Off topic) I also remember seeing engineers determine which memory chip was at fault and replacing the chip using a soldering iron. Try that on a DIMM!

...er of times, but never for more than getting info, or setting the server name on a Dell LCD screen. However, I had a server screaming about intruder alert, intruder alert, er, "Chassis intrusion detected", and I thought there might be a way to shut it up (this after pulling the server and reseating the lid). A quick google found, on the first page, an 8 page document by Dell called "Managing Dell PowerEdge Servers Using IPMItool". It's clear, comprehensible, has links to the ipmitool project, and to the IPMI standard, which has documentation on calls and parameters. It also has...

Dne 17.9.2019 v 15:25 Mauricio Tavares napsal(a): > On Tue, Sep 17, 2019 at 9:11 AM Miroslav Geisselreiter <mg at intar.cz> wrote: >> Dne 17.9.2019 v 14:02 Mauricio Tavares napsal(a): >>> On Tue, Sep 17, 2019 at 7:06 AM Miroslav Geisselreiter <mg at intar.cz> wrote: >>>> I have brand new PC with this components: >>>> CPU Intel? Pentium G5400,

I keep getting a red alarm when trying to setup asterisk to use my TE420B EC. I only have a blank context setup in my extensions.conf as I haven't started to config that until I can clear this red alarm. I don't have physical access to the server, so I can't go reseat the modules/card/ethernet cable, though I have hands on location that have done this a couple times

Hi folks, I inherited a very old computer (I guess about 8 years old) which I'd like to use for some training on CentOS. I downloaded images for CentOS 6.4 i386 (DVD 1 and 2) and burned them onto discs. After inserting DVD 1 into drive and booting, on the "Welcome to CentOS 6.4!" screen I select "Install or upgrade an existing system". I then skip the media test and

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 19/01/16 12:34, J Martin Rushton wrote: > Not new: I can remember seeing DEC engineers cleaning up the > contacts on memory boards for a VAX 11/782 with a pencil eraser > c.1985. It's still a pretty standard first fix to reseat a card or > connector. I used to do that as well. The contacts would come out nice and shiny when you

http://www.ebay.com/bhp/ibm-x3650 ;) Jason On 02/22/2017 04:08 PM, m.roth at 5-cent.us wrote: > I've never seen anything like this. We moved it from the data center > yesterday, and this morning I plug it in, and it won't power up. I find a > manual for it online, and it says that on plugging it in, wait 3 minutes. > The power button will flash 4x/sec, then slow down to

Hi Everyone, I found these in my log files. I am running the latest version of gs, as distributed by CentOS Oct 11 18:03:27 charlie kernel: gs[9960]: segfault at 0000000000000000 rip 0000003f0cd2063e rsp 0000007fbfffe090 error 6 Oct 12 14:40:58 charlie sshd(pam_unix)[12919]: session opened for user root by root(uid=0) Oct 13 15:16:11 charlie kernel: gs[16302]: segfault at 0000000000000000 rip

I have two X100P cards that were working just fine for months. When I run modprobe wcfxo today I got the following error: ZT_CHANCONFIG failed on channel 2: No such device or address (6) /lib/modules/2.4.19/misc/wcfxo.o: post-install wcfxo failed /lib/modules/2.4.19/misc/wcfxo.o: insmod wcfxo failed The output of dmesg said that wcfxo:Out of space to write register 06 with e0. What?s

I moved my TDM400B cards (first two cards are 40's, third is a 31, last is an 04) from one computer to another, copied all the config files, and now the LED on the line 11 - third line of the third card doesn't go on (it used to on the previous computer). I can get by telling * not to use this line for now but does anyone have any suggestions for getting it to work? Unseat and

thanks! www.cacti.net - Open source application for handling SNMP manageable devices. There is already a FatPipe host/device template and graph template that someone has built! I haven't loaded it as yet-- note his comments about his RRA being included in his templates. http://forums.cacti.net/about10840.html&highlight=fatpipe Your Asterisk people should consider the mailing list:

Greetings list, Wondering if some kind soul can help me with an issue with chan_sip segfaulting as soon as it loads... Basically, if sip.conf contains any peers with "host=dynamic" in them, asterisk won't start. Doing -vvvdddc yields the following: [chan_sip.so] => (Session Initiation Protocol (SIP)) == Parsing '/etc/asterisk/sip.conf': Found Segmentation fault As

I have a problem with a Sangoma card. It worked until yesterday. Now I keep getting this error: Jul 29 17:45:17 pbxacura kernel: wanpipe1: Enable E1 CAS signalling mode! Jul 29 17:45:17 pbxacura kernel: wanpipe1:w1g1: Rx Error: No 'DeviceSelect' from target: pci fatal error! (0x000FA000) Jul 29 17:45:48 pbxacura last message repeated 30946 times It is using Wanpipe 3.5.6 and Zaptel