similar to: watchdog for centos 4.1 and D865 intel motherboard

All, I have an GigaByte motherboard GA-M61P-S3 and I was wondering if any kernel watchdog processes will work with that? Jerry ----------------------------- /lib/modules/2.6.18-53.1.4.el5/kernel/drivers/char/watchdog /lib/modules/2.6.18-53.1.4.el5/kernel/drivers/char/watchdog/softdog.ko /lib/modules/2.6.18-53.1.4.el5/kernel/drivers/char/watchdog/ibmasr.ko

Seems like overnight every motherboard that worked with linux has DROPPED off the face of the earth. Every motherboard I looked at is using the realtek 8111 chipset and a northbridge that is not supported. Example: GIGABYTE GA-970A-DS3, does not work with linux I tried disabling the onboard NIC and using a PCI-E intel card I always use and that would not work either. The north or south bridge

Hello All I made the mistake of assuming all Intel motherboards would be Linux compatible out of the box and bought one without checking support information. And now on initial install the Network is not working....the Network port is not detected at all. I have bought an Intel board DG41RQI (http://www.intel.com/support/motherboards/desktop/DG41RQ/index.htm) which does not support Linux Out of

I have a system that is RAID -1 configured as /dev/md0 is /dev/hda1 /dev/hdb1 /dev/md1 is /dev/hdb3 /dev/hdb3 it seems as though /dev/hda has failed.... I have another disk (identical model) that I can replace hda with. I know about the commands fdisk to repartion and raidhotadd /dev/md0 /dev/hda1 and raidhotadd /dev/md1 /dev/hda3 (to be ran after the system boots). BUT... how do I now get

Alle, We have recently had one of our office servers go south. The hardware was an Intel SDS2 motherboard (EATX), Dual Intel PIII 1.4GHz FC-PGA2-L2 512KB, 3GB (6x512MB) 168 pin DIMM, SDRAM 133MHz/PC-133-ECC with 1x3Ware 7006-2 and 2x3Ware 7506-4LP RAID controllers. The OS was RHEL3. Apparently, according to the beep codes, there has been an FRB failure. I've migrated most of the

Hey there, What recommendations does anybody have as to motherboards known to work well with the Digium TE110P T1 interface cards and the TDM400P analog POTS interface cards? We currently make use of the TE110P for our T1 (esf w/ b8zs - not a PRI) and have experienced many issues caused by our PBX's motherboard. Additionally, we built a server to become our new PBX, but that machine runs

I know most of the motherboards based off of the Intel Q35 northbridge usually have VT-d options for it to be enabled or disabled in the BIOS.  I''ve heard the same for Intel 5400''s and Intel 3200/3210''s but been looking through manuals for various server boards and don''t see VT-d options in the BIOS. However, I was wondering if anyone had success stories or

Hi there, has anyone run into any Desktop/Workstation Intel brand motherboards that work with CentOS 5.1 (4.6/3.9 out of box compatibility is a very large plus) and work with the 1333MHZ cpus such as the 8400/9450 and accept 8GB of RAM? The closest we've found so far is the DG31PR which is alright but it has the limitation of 4GB of RAM and an unsupported Realtek NIC. The DQ35JO is also ok,

Hi! I''m trying to run w83627hf_wdt.ko watchdog driver in domain 0 (xenlinux 2.6.10-xen0), but the driver doesn''t seem to work (the machine reboots all the time after the watchdog-timeout set in BIOS). Is there something that could prevent the driver from accessing the watchdog-hardware (io-ports/registers) ? The watchdog-driver is very simple, and you can find it in

Hello, I'm looking at building a couple new PRI Gateway boxes using TE405P cards, and was wondering if anyone has had any experiences (good or bad) with the Intel SE7210TP1_E motherboards from Intel. General Technics builds some really nice (and cost effective) 1U servers based on the board: Server: http://www.gtweb.net/gt637.html Specs:

Hello, I have a server pfsense in bridge mode to function as transparent FW, the problem is that once I connect the pfsense between my router core and my core switch catalyst a few seconds begin to appear several messages like these: em2: watchdog timeout - resetting em2: watchdog timeout - resetting em2: watchdog timeout - resetting em2: watchdog timeout - resetting And the connection falls

Does anyone have information on support for Intel D965-based motherboards for CentOS 4 (i386)? I've got a DG965RYCK that fails a CentOS 4.4 install early on (problems scanning the PCI bus). Fedora Core 6 installs just fine. If anyone has any information, or magic boot parameters to try, please let me know. ("Works for me" is OK too). Thanks much. Dave Thompson UW-Madison

All, I am installing a BOXD915GAVL system and centos 4. The CPU is a 2.8 GIG celeron D with 1GIG memory and 120GIG Seagate drive. Is is VERY slow. What gives? Any other experience with something like this? It is installing but even after install when booting it is taking VERY long time to even get to the Checking new hardware screen. Thanks, Jerry -------------- next part -------------- An

I need to replace my Abit BE7 board (cannot run the newer Linux) and keep my near new IDE HD's (250 GB). A D865GLC is new available that uses the Intel 865G chip set, but I have no experience in matching Mobo's with Linux. Todd -- Ariste Software 2200 D Street Ext Petaluma, CA 94952 (707) 773-4523

Good morning! On a CentOS 6.4 / 64 bit server I have installed the watchdog 5.5 package. The rpm -qi watchdog states: The watchdog program can be used as a powerful software watchdog daemon or may be alternately used with a hardware watchdog device such as the IPMI hardware watchdog driver interface to a resident Baseboard Management Controller (BMC). ... This configuration file is also used to

Hi all, I've got a Portwell NANO-6060 board I am testing out for potential use in a project of ours. One of the nice features of this board, beyond nice NICs, is that it has a hardware watchdog timer. The problem is that I don't get a /dev/watchdog device file. I know the hardware works, because when I enable it in BIOS, the box will reboot after the timer expires. However,

Apologies if this is posted on the wrong list, but when I try to get pci passthrough to work on a Wheezy Xen box I get NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out and then not much else works at all. The same hardware works just fine with Xen and Squeeze. It seemed to me that the problem I am seeing is very similar to

Hello Nut Devs, I'm working with usbhid-ups and a Tripplite OMNI1000LCD. I used a USB packet sniffer to discover something cool about the watchdog feature in this unit. (not sure if the other OMNI-X-LCD models work the same or not.) Basically there's a single HID variable at Report ID 0x52 (UPS.OutletSystem.Outlet.ffff0092) that's one byte (0-255 int) and it contains the Watchdog

https://bugs.freedesktop.org/show_bug.cgi?id=95330 Bug ID: 95330 Summary: [NV84] Hangs with gr: DATA_ERROR [INVALID_BITFIELD], TRAP_PROP [RT_FAULT], fb: trapped write [PGRAPH] [PROP] [RT0] [PAGE_NOT_PRESENT], bsp: Watchdog interrupt, engine hung Product: xorg Version: unspecified

# HG changeset patch # User Olaf Hering <olaf@aepfle.de> # Date 1336153082 -7200 # Node ID 9a430b7e2df2893f7f4f75d10e66d52bdffa7efa # Parent 113fd57259b91af06a5352404dd94b484a98d2bc tools/hotplug: remove 4 from default runlevel in xen-watchdog, xend and xendomains Similar to what changeset 24847:0900b1c905f1 does in xencommons, remove runlevel 4 from the other runlevel scripts. LSB defines