search for: i7s

Yes: Previous complete boot through shutdown Oct 26 21:02:54 i7 upsdrvctl[1955]: Using subdriver: MGE HID 1.32 Oct 26 21:02:55 i7 upsdrvctl[1955]: Network UPS Tools - Generic HID driver 0.38 (2.7.1) Oct 26 21:02:55 i7 upsdrvctl[1955]: USB communication driver 0.32 Oct 26 21:02:56 i7 upsdrvctl[1955]: Network UPS Tools - UPS driver controller 2.7.1 Oct 26 21:02:56 i7 upsd[2226]: fopen

Hello, I have been following the details in this article to configure my UPS: http://rogerprice.org/NUT.html However the system won't shutdown although file permissions look ok: ls -alF /usr/sbin/ups* -rwxr--r-- 1 upsd daemon 64984 Oct 15 2014 /usr/sbin/upsd* -rwxr--r-- 1 upsd daemon 48584 Oct 15 2014 /usr/sbin/upsmon* -rwxr--r-- 1 upsd daemon 31536 Oct 15 2014 /usr/sbin/upssched*

P.S.2 Today I experienced something weird. As I was working, the system started a shutdown and did shut down, then the UPS got powered off and then back on - an expected behavior for a power fail situation. However there was no power failure! I ran nut-journal to check what happened: Previous complete boot through shutdown Oct 29 10:09:33 i7 upsdrvctl[1966]: Using subdriver: MGE HID

Yes, that was the power off test. However the upssched-cmd script gave absolutely no signs of activity. Even it's logger lines don't show up in journalctl. No any permission error messages - nothing. Only the 2 messages from upsmon - on battery and then on line power. Here is the nut-report: http://www.filehosting.org/file/details/518300/NUT.report --- George Anchev On Tue, Oct 27,

> > Did you see a line in the journal similar to this ? > Oct 06 22:49:54 pinta nut-delayed-ups-shutdown[1854]: > nut-delayed-ups-shudown.service calling > upsdrvctl to shut down UPS unit Never after I disabled the service. I pasted the whole journal section of the successful shutdown from last email. However I have been thinking about this line

Beautiful! The shutdown succeeded. Thank you very much. However there was no any notification on desktop at all. Only in journalctl. Here it is: Oct 27 23:38:11 i7 upsmon[2224]: UPS myups at localhost on battery Oct 27 23:38:11 i7 upssched[2244]: Timer daemon started Oct 27 23:38:11 i7 upssched[2244]: New timer: two-minute-warning-timer (5 seconds) Oct 27 23:38:11 i7 upssched[2244]: New timer:

Hi all, I'm just curios and would like some input from the community on this one. We're busy budgeting for a couple of new servers and I thought it would be good to try out the Core i7 CPU's, but see the majority of them don't offer VT-d, but just VT-x. Looking at the LGA1366 range, only the "Intel lga1366 i7 980XE" (from the list of what our suppliers stock) have VT-d,

What is the status of i7 architecture support for CentOS-5? Do the latest updates support it? -- This e-mail may contain technical information which is controlled by the United States Government, Department of State, International Traffic & Arms Regulations (ITAR) (22 CFR 120-130) which requires an export license prior to sharing with foreign persons. Lacking such license, ITAR technical

Hello, BSOD 0x00000101 CLOCK_WATCHDOG_TIMEOUT randomly appears on all HVM Windows 2008R2 (with signed GPLPV drivers) with vcpu''s>=2 after upgrading CPU to hexacore i7-3930K. xen and qemu-dm logs have no suspicious entries after bsod. Before upgrade CPU was i7-2600 and all HVM''s works fine. Such problem persist on all motherboards with i7-3930K,and disappear after moving Dom0

...hey're present, or are > we supposed to find out some other way? > > These three options wouldn't seem to come close to specifying all the > various core i7 CPUs there are and optimizing for all the features of > each. Getting *some* of the additional instructions offered by i7s > would certainly help performance over what the standard distro offers, > but probably still not enough to warrant the extra expense of the > higher-end CPUs. > > http://gcc.gnu.org/onlinedocs/gcc-4.6.4/gcc/i386-and-x86_002d64-Options.html#i386-and-x86_002d64-Options > also offer...

On Thu, 29 Oct 2015, George Anchev wrote: > Today I experienced something weird. As I was working, the system > started a shutdown and did shut down, then the UPS got powered off and > then back on - an expected behavior for a power fail situation. However > there was no power failure! ... > Oct 29 10:46:46 i7 upsmon[2239]: UPS myups at localhost battery is low > Oct 29

Hello, Is there a way to force through R the amount of the cpu's cores (or the cpu's utilization level) used under Windows 7 or Linux? Thanks, Costas

On 6/12/2015 7:09 PM, jd1008 wrote: >> > I want to thank you for posting your installation experience with > Centos 7. > My laptop is Latitude E6500 and I am quite certain it will experience > the same issue > because it is almost the same as your laptop. Difference might be in > cpu speed > and in RAM. My cpu is 2.81GHz dual core, and RAM is 8GB. the E6x00, E6x10,

This computer is my main desktop machine --- an Intel i7-940 CPU and DX58S0 motherboard with a Radeon X1950 Pro video card. It's currently running Fedora 11 and working just fine. However, I have been slowly moving all of my "computer stuff" off of Fedora and onto Centos, and this (and my Acer Aspire One laptop) are the only Fedora installations that I now have left. Does anyone

Hello, I am looking into building a workstation using Xen to host several operating systems. Looking at the pci passthrough requirements of Xen4.1 on the VTdHowTo<http://wiki.xensource.com/xenwiki/VTdHowTo>page, I am a little puzzled with the fact that only Intel Core2Duo (with VT-x), Core2Quad, i7 and Core i5 (vPro Brand) CPU''s are supported while motherboards with the i55x0

https://bugs.freedesktop.org/show_bug.cgi?id=93932 Bug ID: 93932 Summary: Xorg/Nouveau crashes with Segmentation fault when setting i7-Skylake iGPU as primary grapics device in BIOS Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW

These show up under Windows XP as if they are SCSI adapters (they're not, obviously.) Has there been any view towards supporting these on FreeBSD? They're on all the recent Intel motherboards for the last year and a half or so. Also, is there any particular benefit (or penalty) to running the amd64 build on Quad-Core or i7-series processors? I have an app that might benefit from

Here is my post issued again from the beginning in some sort of logical order I hope, with additional information as suggested by George Dunlap. I am having trouble getting PCI Passthrough to work from Dom0 to DomU I am using Xen 4.6 with CentOS kernel 3.18.34-20.el7.x86_64 on a Dell Poweredge T430. When I plug in a device to the USB port, nothing happens. I am Watching /var/log/messages in

uname -a SunOS i7 5.11 snv_114 i86pc i386 i86xpv The box is a core i7 with 6GB of RAM. The command virt-install --name 10u7 --ram 1024 --hvm --file /guests/10u7 --os-type=solaris os-variant=solaris10 --location /export/iso/sol-10-u7-ga-x86-dvd.iso get as far as opening the VNC client, when I select Solaris from grub, the OS starts to boot then panics, closing the session. So I

Trying to set up PCI pass through with xen 3.2.1 on Debian Lenny, with xen Kernel 2.6.26... having no luck. I have the following configured... i) Virtualization and vt-d are both enabled in the bios, I have power cycled after making these changes. ii) I have these option in grub menu; iommu=1 pciback.permissive pciback.hide=(07:01.0)(01:00.0) vtd=1 iii) I have this in my cfg file