search for: h77m

Displaying 4 results from an estimated 4 matches for "h77m".

Did you mean: 577m
2013 Jul 01
2
Kernel crash when using usbhid-ups driver.
.../nut-upsuser I found this thread on a google search and just wanted to add that I seem to have encountered a very similar problem: general protection faults once every 1-3 days after installing nut for my CyberPower 1000PFCLCD. Using Ubuntu 12.04 LTS 64-bit, stock kernel 3.5.0-34-generic. ASRock H77M motherboard, Core i3-3225 CPU. A syslog dump is below in case it may be useful. This one's a bit special in that there seems to be 3 successive GPFs. I don't follow this list so please contact me separately if I can be helpful. Jun 30 10:29:24 ns1 kernel: [90099.127943] general protecti...
2012 Nov 29
4
Intel HD4000 IGD pass through appears to work, but monitor complains about 'no signal'
I''ve seen a recent report claiming that it works: http://linux-bsd-sharing.blogspot.pt/2012/10/howto-xen-413-windows-8-hvm-domu-with.html However, in my case, with a slightly different HW configuration the story is totally different. :-( My config: HW: I7-3770 + AsRock H77M-ITX board Dom0: Debian Wheezy stock xen (v4.1.3) + Debian stock kernel (3.2.x / 3.6.x) 64 bit version. Note that both of us have only one gpu in the system. They difference is that the lucky guy has an DQ77MK while mine is an AsRock. Another different is that he picks win 8 as domU, while my targe...
2012 Dec 20
25
[PATCH] hvmloader / qemu-xen: Getting rid of resource conflict for OpRegion.
This is hvmloader part of the change that gets rid of the resource conflict warning in the guest kernel. The OpRegion may not always be page aligned. As a result one extra page is required to fully accommodate the OpRegion in that case. Just reserve one more page here. Signed-off-by: Timothy Guo <firemeteor@users.sourceforge.net> diff -r 11b4bc743b1f tools/firmware/hvmloader/e820.c ---
2012 Dec 03
21
Issue about domU missing interrupt
Hi developers, I met some domU issues and the log suggests missing interrupt. Details from here: http://www.gossamer-threads.com/lists/xen/users/263938#263938 In summary, this is the suspicious log: (XEN) vmsi.c:122:d32767 Unsupported delivery mode 3 I''ve checked the code in question and found that mode 3 is an ''reserved_1'' mode. I want to trace down the source of this