5 minutes ago, ich777 said:

Sorry overlooked the post from above where you've already wrote that...

As said above this is not a trivial issue, also see here: Click

 

It may be related that the chip that you are using is a Engineering Sample, I've now tried it again on my i5-10600 and it works without a flaw.

 

If you are using Parsec you can always try this: Click

Thank you, this should be the problem of Engineering Sample

One more question, BK650M2-CH shows: On battery in the UPS setting plug-in, is there any way to fix it?

Using the Network UPS Tools (NUT) plug-in also does not work properly NUT Settings issues

18 minutes ago, s1oz said:

Thank you, this should be the problem of Engineering Sample

This is only a guess, maybe it will work with driver from Parsec or better speaking the tutorial that I've linked in the previous post.

 

18 minutes ago, s1oz said:

One more question, BK650M2-CH shows: On battery in the UPS setting plug-in, is there any way to fix it?

I think you should create a post hover here:

 

I’ve confirmed my issue was my dummy plug. I plugged in a monitor and all resolutions work fine

 

what dummy plugs are you guys using?

I use this one. But, admittedly, I have been booting with a monitor plugged in first. Sometimes my system seems to hang on boot/reboot, maybe BIOS. If I boot with a monitor, I can press keys to get past.

 

Once Unraid it booting, I quickly swap off the monitor to the dummy plug *shrug*

5 hours ago, freeridekid said:

what dummy plugs are you guys using?

I'm using this one: https://www.amazon.de/gp/product/B06XT1Z9TF/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1

Im back to being stuck at that resolution again

 

Also, when i boot up my unraid machine, the display cuts out once booted up if i select either normal or gui mode, i wonder if that has anything to do with it

1 hour ago, freeridekid said:

Im back to being stuck at that resolution again

What have you done that it worked before?

 

1 hour ago, freeridekid said:

Also, when i boot up my unraid machine, the display cuts out once booted up if i select either normal or gui mode, i wonder if that has anything to do with it

What do you mean exactly with that?

That is just normal at time when the driver is loaded during boot.

4 minutes ago, ich777 said:

What have you done that it worked before?

 

What do you mean exactly with that?

That is just normal at time when the driver is loaded during boot.

If I hook up my monitor to my server and boot up, I am able to select start with GUI and see all the processes, and then the monitor cuts out

 

I am not sure what I did different. My VM crashed and I had to re install but it won't work this time

35 minutes ago, freeridekid said:

If I hook up my monitor to my server and boot up, I am able to select start with GUI and see all the processes, and then the monitor cuts out

Completely or for only a short time?

 

35 minutes ago, freeridekid said:

My VM crashed and I had to re install

Only because it crashed you had to reinstall Windows?

12 minutes ago, ich777 said:

Completely or for only a short time?

 

Only because it crashed you had to reinstall Windows?

It completely cuts out

 

Yah I don't know what happened but the VM crashed and disappeared completely 

12 minutes ago, freeridekid said:

It completely cuts out

Please share your Diagnostics again.

 

13 minutes ago, freeridekid said:

Yah I don't know what happened but the VM crashed and disappeared completely 

Something seems really wrong on your system if such a thing happens...

16 minutes ago, ich777 said:

Please share your Diagnostics again.

 

Something seems really wrong on your system if such a thing happens...

 

 

Here they are

trialskid-diagnostics-20220224-1111.zip

the resolution scales fine in RDP

Well I figured it out again. 

 

If i go into advanced display settings > Display adapter settings for Display 2 > List All Modes > I can select it and change through there and it works

Is there any way we can continue to use the gui with this?

44 minutes ago, freeridekid said:

Is there any way we can continue to use the gui with this?

What do you mean exactly with GUI the VM?

1 hour ago, ich777 said:

What do you mean exactly with GUI the VM?

No, when i hook a monitor up to my server, it goes black and has no video output once it posts

10 minutes ago, freeridekid said:

No, when i hook a monitor up to my server, it goes black and has no video output once it posts

Should be fixed in 6.10.0

1 hour ago, ich777 said:

Should be fixed in 6.10.0

awesome, thanks

Hey guys,

Not sure why, but I am getting a "GVT-g not supported" error even though I have a newly purchased Intel Core i5-10400 and an ASUS Prime B560-PLUS motherboard. It worked for a short period then stopped. I didn't touch the bios after I initially got it working, so not sure where I went wrong. Any help would be appreciated. Thanks!

 

Edited February 27, 20224 yr by LakersFan
removed diagnostics due to update post below

@ich777，Is there a timeline to support the 11th  intel CPU?

3 hours ago, wangwei4819 said:

@ich777，Is there a timeline to support the 11th  intel CPU?

 

Intel quitted support on > gen 10, so there is nothing @ich777 can do about it.

5 hours ago, LakersFan said:

Hey guys,

Not sure why, but I am getting a "GVT-g not supported" error even though I have a newly purchased Intel Core i5-10400 and an ASUS Prime B560-PLUS motherboard. It worked for a short period then stopped. I didn't touch the bios after I initially got it working, so not sure where I went wrong. Any help would be appreciated. Thanks!

tower-diagnostics-20220226-1555.zip 158.36 kB · 0 downloads

I made sure my primary graphics was set to CPU in the bios. Still no luck. Still shows not supported. Attached is my latest diagnostics.

tower-diagnostics-20220226-2136.zip

46 minutes ago, LakersFan said:

I made sure my primary graphics was set to CPU in the bios. Still no luck. Still shows not supported. Attached is my latest diagnostics.

Please remove "nomodset" from your syslinux.conf since this instructs the Kernel to not load the graphic drivers until X is started.

Why did you use this command?

Thank you! That fixed it.

 

I have zero idea why or how that got changed... I wish I did. But I honestly don't believe I ever touched that file, as I would have had to unhide my flash drive to even access it.