similar to: watchdog on gigabyte motherboard

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

Hi folks, after all this struggle with Gigabyte''s Tech-Support and self-modified bioses it seems Gigabyte reconsidered making Virtualization-Support available for the masses. The F6-bios for the GA-M61P-S3 rev 1.0 Motherboard is hopefully the beginning (not a mistake) and others will follow. Thanks to all the people writing to the Gigabyte-Tech-Support making this reconsideration

As a follow up to this post http://lists.xensource.com/archives/html/xen-users/2007-07/msg00476.html I have ZenEnterprise 4.0.1 and Virtual Iron 3.7.2 running Windows guests on my GA M61P S3. To enable the AMD-V hardware virtualization capabilities on my Gigabyte motherboard: * install the Gigabyte bios version F2 dated Dec 2006 (download from Gigabyte support site) and expand out

I downloaded the src rpm for CentOS 5 and tried to recompile it. It failed with the following message: + sh ./scripts/modsign/modsign.sh /var/tmp/kernel-2.6.18-8.el5-root /lib/modules/2.6.18-8.el5PAE/kernel/drivers/char/watchdog/pcwd_pci.ko CentOS gpg: WARNING: unsafe permissions on homedir `..' + mv -f

Below is a kernel dump that I just got. This is a fresh new install of centos 5.1 on NVIDIA gigabyte MB-GA-M61P-S3. nothing extra has been added. I have not tried the irqpoll but I am surprised to get this. Also the machine keeps running just hod this show on the console... Any ideas??? Jerry Jan 8 05:20:00 localhost kernel: irq 169: nobody cared (try booting with the "irqpoll"

Hi Recently I upgraded my kernel to 2.6.11 (debian) and applied some patches from pom-ng (netfilter) and the iproute2-ss050330 package I have been experiencing a lot of crashes in the kernel (snip below) ================================== Apr 5 20:00:21 sydlxfw01 kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000221 Apr 5 20:00:21 sydlxfw01 kernel: printing eip:

There is a new fallthrough pseudo-keyword macro that can be used to replace the various /* fallthrough */ style comments that are used to indicate a case label code block is intended to fallthrough to the next case label block. See commit 294f69e662d1 ("compiler_attributes.h: Add 'fallthrough' pseudo keyword for switch/case use") These patches are intended to allow clang to

There is a new fallthrough pseudo-keyword macro that can be used to replace the various /* fallthrough */ style comments that are used to indicate a case label code block is intended to fallthrough to the next case label block. See commit 294f69e662d1 ("compiler_attributes.h: Add 'fallthrough' pseudo keyword for switch/case use") These patches are intended to allow clang to

There is a new fallthrough pseudo-keyword macro that can be used to replace the various /* fallthrough */ style comments that are used to indicate a case label code block is intended to fallthrough to the next case label block. See commit 294f69e662d1 ("compiler_attributes.h: Add 'fallthrough' pseudo keyword for switch/case use") These patches are intended to allow clang to

There is a new fallthrough pseudo-keyword macro that can be used to replace the various /* fallthrough */ style comments that are used to indicate a case label code block is intended to fallthrough to the next case label block. See commit 294f69e662d1 ("compiler_attributes.h: Add 'fallthrough' pseudo keyword for switch/case use") These patches are intended to allow clang to

There is a new fallthrough pseudo-keyword macro that can be used to replace the various /* fallthrough */ style comments that are used to indicate a case label code block is intended to fallthrough to the next case label block. See commit 294f69e662d1 ("compiler_attributes.h: Add 'fallthrough' pseudo keyword for switch/case use") These patches are intended to allow clang to

I've been doing this on CentOS 4 and CentOS 5 but after installing 2.6.18-53.1.4el kernel, I'm having a bit of a struggle... # make -C /lib/modules/2.6.18-53.1.4.el5/build \ SUBDIRS=/usr/src/appletalk modules make: Entering directory `/usr/src/kernels/2.6.18-53.1.4.el5-i686' CC [M] /usr/src/appletalk/aarp.o CC [M] /usr/src/appletalk/ddp.o CC [M] /usr/src/appletalk/dev.o

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> </head> <body bgcolor="#ffffff" text="#000000"> <font size="-2">Hi All ,<br> Any one using Cisco VPN Client [</font><font size="-2">vpnclient-linux-4.6.00.0045-k9.tar.gz] </font><font size="-2">on

Hi all, I am trying to load kernel module ipmi_si, while failed with error "No such device", truth is I can find file in ../kernel/drivers/char/ipmi/ipmi_si.ko. So why I can't load it? Steps: # ls -l /lib/modules/2.6.32-573.el6.x86_64/kernel/drivers/char/ipmi/ipmi_si.ko -rwxr--r--. 1 root root 93080 Jul 23 2015

Hello, I have a big problem: Dom0 is centos5.1, domU are centos5.1. My setup is really simple, the only thing is that I give 3 nics to the domU so I use a modified network script (which has worked since january... since fedora 6): " #!/bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 "$dir/network-bridge" "$@" vifnum=1

Hi all, I'm having issue with my Centos 5.1 /Xen installation. I'm having 2 dom0 running 2.6.18-53.1.4.el5xen (x86_64). These two dom0 are connected to a SAN. These two dom0 hosts multiple domU like Centos 4.5 (2.6.9-55.0.9.ELxenU) and Centos 5.1 (2.6.18-53.1.4.el5xen). These two dom0 run ntpd to synchronize dom0 time. When i start a virtual machine on the first dom0 all seems good, the

https://bugs.freedesktop.org/show_bug.cgi?id=54830 Bug #: 54830 Summary: Display is shifted to right (ASUS VS197) Classification: Unclassified Product: xorg Version: 7.7 (2011) Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: minor Priority: medium Component:

Hello All, Consider a CentOS-5.1 Xen server (2.6.18-53.1.4.el5xen) hosting two domains running CentOS-5.1 (2.6.18-53.1.4.el5). One domain has a fairly accurate clock, the other domain has a clock that gains ungodly amounts of time, roughly one minute every two or three minutes. For a fix, one suggestion is to run this command in DomU: echo 1 > /proc/sys/xen/independent_wallclock This

I've asked this on the Xen users list, but had no response so far: I'm running CentOS 5.1 with all current updates: xen-libs-3.0.3-41.el5 xen-3.0.3-41.el5 kernel-xen-devel-2.6.18-53.1.4.el5 kernel-xen-2.6.18-53.1.4.el5 and have a domU config file from another (5.0) server which works. The difference is that on the new machine I want to use routed rather than bridged networking. In

Hija! I get this error while doing the cleanup, hints? Cheers, JJ ----------------------------------------------------------- [root at neonbox ~]# package-cleanup --oldkernels --count 2 Setting up yum Loading "priorities" plugin Loading "kernel-module" plugin Loading "protectbase" plugin Loading "kmdl" plugin Loading "skip-broken" plugin