search for: powerup

...no calls. It has been working for several months, and just quit yesterday. Thanks! Found a Wildcard TDM: Wildcard TDM400P REV I (4 modules) Freshmaker version: 73 Freshmaker passed register test Module 0: Installed -- AUTO FXS/DPO Module 1: Installed -- AUTO FXS/DPO ProSLIC on module 2 failed to powerup within 510 ms (0 mV only) -- DID YOU REMEMBER TO PLUG IN THE HD POWER CABLE TO THE TDM400P?? Unable to do INITIAL ProSLIC powerup on module 2 ProSLIC on module 2 failed to powerup within 510 ms (0 mV only) -- DID YOU REMEMBER TO PLUG IN THE HD POWER CABLE TO THE TDM400P?? Unable to do INITIAL...

Hi, I have Wildcard TDM400P with 2 FXS y 2 FXO. After all work fine but now do it: ----- load driver: wctdm y zaptel (zaptel-1.2.1) Module 0: Installed -- AUTO FXS/DPO Unable to do INITIAL ProSLIC powerup on module 1 Unable to do INITIAL ProSLIC powerup on module 1 Module 1: FAILED FXS (FCC) Module 2: Installed -- AUTO FXO (FCC mode) Module 3: Installed -- AUTO FXO (FCC mode) Found a Wildcard TDM: Wildcard TDM400P REV E/F (3 modules) Registered tone zone 0 (United States / North America) ----- /et...

Hi I've a Sangoma A200D with 2FXO and 2FXS. When using it with only the FXO module, it's all good. But when I put in the FXS module and connect the power, logs tells me not enough power. > Mar 31 14:11:54 phone kernel: [ 4761.246931] wanpipe1: Module 1: > Failed to powerup within 600 ms (8V : 72V)! > Mar 31 14:11:54 phone kernel: [ 4761.246937] wanpipe1: Module 1: Did > you remember to plug in the power cable? So I disconnect other power devices in the box (Dell Optiplex GX270) such as the Zip drive and CDROMs, but no luck. Then I took an external powe...

Hi all, I have shorewall up and running on my system. (GNU-Linux Mandrake 9) When I tested my firewall at grc.com, Shields-Up informs me that ports 113 and 135 are closed and not ''stealthed'' When reading the faq on the Shorewall site I saw that shorewall rejects rather than denys connection requests on ''TCP ports 113, 135, 137 and 139 as well as UDP ports

Is there any known incompatibility with the latest 32-bit (i386) CentOS 6 and the latest Lenovo x3650 M5 servers? I?ve been running i386 CentOS 6.X on 3 year old x3650 M4 servers without any issues. Our development environment has not been ported to 64-bit (x86_64) yet, so we are stuck using i386 for another few months. When I try to boot from the netinstall ISO image I just get a ?Boot Failed?

...lk for eth0 Zapata Telephony Interface Registered on major 196 No ISA tormenta card found at d0000 Registered Tormenta2 PCI Freshmaker version: 73 Freshmaker passed register test Module 0: Not installed Module 1: Not installed Module 2: Installed -- AUTO FXO (FCC mode) ProSLIC on module 3 failed to powerup within 510 ms (0 mV only) -- DID YOU REMEMBER TO PLUG IN THE HD POWER CABLE TO THE TDM400P?? Unable to do INITIAL ProSLIC powerup on module 3 Unable to do INITIAL ProSLIC powerup on module 3 Module 3: FAILED FXS (FCC) Found a Wildcard TDM: Wildcard TDM400P REV I (1 modules) Registered tone zone...

...)) { + printk(KERN_ERR "Some devices failed to power down\n"); + goto Done; + } + + ACPI_FLUSH_CPU_CACHE(); + + /* Do arch specific saving of state. */ + if (state > ACPI_STATE_S1) { + error = acpi_save_state_mem(); + if (error) + goto Powerup; + } + + switch (state) { + case ACPI_STATE_S3: + do_suspend_lowlevel(); + break; + default: + error = -EINVAL; + goto Powerup; + } + + printk("Back to C!\n"); + if (state > ACPI_STATE_S1) + acpi_restore_st...

...e to install it by clicking on a Legacy checkbox in the BIOS, which brought up a different list of boot devices and I was finally successful in booting from the ISO image. I then had to finagle the BIOS to always boot in legacy mode so that it would recognize the i386 CentOS boot partition on each powerup. Alfred

hi, My question is may be a bit out of scope but I don't know where to turn, I have a 1760 with a ccme 24 user licences 1 bri card. I want to configure a bri card in a cisco 1760 on port 0/0, the card is new, seen by the router, show isdn status gives layer 1 desactived , layer not activated, what ever I do, no shutdown command / shutdown command, etc , the green OK light never turn on,

Hi, This patch includes port of NUT to LynxOS 4.0. The patch is against yesterday's svn tree. Here is a brief description of changes: drivers/powercom.c: Rename shutdown() to shutdown2(). shutdown() is already defined in LynxOS system header files. Please feel free to rename it more appropriately. (I didn't do it due to lack of imagination :-) ) include/proto.h: Added

...D3hot by pci_set_power_state() and subsequently into D3cold by invoking the nonstandard means. However as a consequence the cached current_state is incorrectly left at D3hot. What we need to do is walk the hierarchy below such a PCI device on powerdown and update the current_state to D3cold. On powerup the PCI device itself and the hierarchy below it is in D0uninitialized, so we need to walk the hierarchy again and wake all devices, causing them to be put into D0active and then letting them autosuspend as they see fit. To this end make pci_wakeup_bus() & pci_bus_set_current_state() public so...

This is all on SuSE enterprise 10 Our server was moved to a new location last night. After powerup there was no sign of networking so our ISP reconfigured the box. Outbound connectivity had previously been through eth1 but is now through eth0 Since restarting Xen I now have no network connectivity through the hosts. I have tried to provide all the relevant details below. If anyone has a moment...

...ED; + } optiquery( "Ct1" ); optiquery( "Cs00000010" ); return STAT_INSTCMD_HANDLED; @@ -202,6 +240,12 @@ /* This actually stays off as long as the batteries hold, * if the line power comes back before the batteries die, * the UPS will never powerup its output stage!!! */ + if ( testvar(OPTI_ZINTO) ) + { + optiquery( "Ct1" ); + optiquery( "Cs0000001" ); + return STAT_INSTCMD_HANDLED; + } optiquery( "Ct0" ); optiquery( "Cs00000010" ); return STAT_INSTCMD_HANDLED; @@ -217,11...

On 20/12/2018 15:33, mark wrote: > lejeczek via CentOS wrote: >> hi guys >> >> I wonder if any Centosian here have done something different than only >> contemplated using Fedora Server, actually worked on it in test/production >> envs. >> >> If here are some folks who have done it I want to ask if you deem it to >> be a viable option to put it on

I posted a thread on this once long ago[1] -- but we''re still fighting with this problem and I wanted to throw it out here again. All of our hardware is from Silicon Mechanics (SuperMicro chassis and motherboards). Up until now, all of the hardware has had a single 24-disk expander / backplane -- but we recently got one of the new SC847-based models with 24 disks up front and 12 in the

Hi, FreeBSD-9 works fine on this Lenovo T400 - except that suspending with no USB devices plugged in result in no ports working after resume. If I have a device plugged in during suspend - on any port - then all the ports work fine after resume. I've attached usbconfig and acpidump output. here's what is logged in the kernel buffer during suspend and resume: Her'es the suspend:

We have a 3TB external USB drive that I am trying to attach to some CentOS5 servers. I have tried an older Dell PE1950 and a newer R310 but neither one seems to be able to read the drive. It works no problem on windows servers/workstations and I was able to format with NTFS. I know there are different methods for formatting large disks but this one doesn't even seem to show up as a /dev/

...s: 1x Windows 95 (Brother Printer) 8x Windows XP <=problematic! 2x Windows Visa 2x Windows 7 1x Samba 3.5.8 (WINS,DNS, supose to be LMB) There is a serious problem with a browselist. Ever single windows XP workstations disapear from browselist after an about 24 - 28 minutes after workstation powerup or smbd restart. After this they are still accesable by hostname, netbiosname, and ip. Other workstations are visible as they should be and don't disapear. First i thought it is an name resolution problem but i run correctly configured dns server. This server answers for both types of querr...

Hi Ingo, This series of patches implements a number of improvements to the softlockup watchdog and its users. They are: 1. Make the watchdog ignore stolen time When running under a hypervisor, the kernel may lose an arbitrary amount of time as "stolen time". This may cause the softlockup watchdog to trigger spruiously. Xen and VMI implement sched_clock() as measuring unstolen time,

Hi Ingo, This series of patches implements a number of improvements to the softlockup watchdog and its users. They are: 1. Make the watchdog ignore stolen time When running under a hypervisor, the kernel may lose an arbitrary amount of time as "stolen time". This may cause the softlockup watchdog to trigger spruiously. Xen and VMI implement sched_clock() as measuring unstolen time,