DanielCoffey
-
Posts
268 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by DanielCoffey
-
-
Hmm... this is really beginning to get frustrating. I am still getting the blank screen even with the new 1080 Ti as the only GPU, with or without the nomodeset / nouveau.modeset=0 or grub_gfxmode=1024x768x16.
I have the card in its own IOMMU group so my next step is to obtain the ROM and give the VM the rom details. Fingers crossed that works otherwise it is off to Ubuntu. Heck, even Windows gets it right!
IOMMU group 0 [8086:591f] 00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05) IOMMU group 1 [8086:1901] 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 05) IOMMU group 2 [8086:1905] 00:01.1 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x8) (rev 05) IOMMU group 3 [8086:5912] 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) IOMMU group 4 [8086:a2af] 00:14.0 USB controller: Intel Corporation 200 Series PCH USB 3.0 xHCI Controller IOMMU group 5 [8086:a282] 00:17.0 SATA controller: Intel Corporation 200 Series PCH SATA controller [AHCI mode] IOMMU group 6 [8086:a2e7] 00:1b.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #17 (rev f0) IOMMU group 7 [8086:a2eb] 00:1b.4 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #21 (rev f0) IOMMU group 8 [8086:a290] 00:1c.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #1 (rev f0) IOMMU group 9 [8086:a294] 00:1c.4 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #5 (rev f0) IOMMU group 10 [8086:a296] 00:1c.6 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #7 (rev f0) IOMMU group 11 [8086:a298] 00:1d.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #9 (rev f0) IOMMU group 12 [8086:a2c5] 00:1f.0 ISA bridge: Intel Corporation 200 Series PCH LPC Controller (Z270) [8086:a2a1] 00:1f.2 Memory controller: Intel Corporation 200 Series PCH PMC [8086:a2a3] 00:1f.4 SMBus: Intel Corporation 200 Series PCH SMBus Controller IOMMU group 13 [8086:15b8] 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V IOMMU group 14 [10de:1b06] 01:00.0 VGA compatible controller: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] (rev a1) [10de:10ef] 01:00.1 Audio device: NVIDIA Corporation GP102 HDMI Audio Controller (rev a1) IOMMU group 15 [1b73:1100] 02:00.0 USB controller: Fresco Logic FL1100 USB 3.0 Host Controller (rev 10) IOMMU group 16 [144d:a804] 04:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961 IOMMU group 17 [1b21:2142] 06:00.0 USB controller: ASMedia Technology Inc. Device 2142 IOMMU group 18 [1b21:2142] 07:00.0 USB controller: ASMedia Technology Inc. Device 2142 -
I had a delay while I tested to find the source of unexplained reboots (power delivery to the motherboard in the end) and then decided to go shopping. I now have a 1050 Ti for low power Linux use and a 1080 Ti for the Win10 gaming. I have not recreated the Linux VM yet as I am still adding components back into the array (new PSU to be fitted tomorrow) so I don't know if it will automatically detect the 10xx GPU.
-
Finally resolved...ish.
@tdallen - you were right about FF being Finished Fine because it was legacy boot mode. If I boot to an UEFI device such as an SSD I get A0. If I boot to the unRAID Legacy USB stick I get FF. Every time.
However... the random reboots and 00/04 flickering were a serious issue that I have managed to (almost) isolate. It was the delivery of power to the motherboard, particularly to the 8-pin CPU power header.
I bought a very cheap refurb Corsair PSU from Scan and attached it and noticed the ROG LEDs on the PCIe slots flickering madly as soon as the PSU was connected but before the board was switched on. Reseating the PSU cables resolved it and regardless of whether I used the old PSU or the refurb new one, the board then booted cleanly every time. I did then manage to reproduce the LED flickering when fiddling with the PSU cables on the old PSU. The 8-pin cable is really touchy. I don't know yet if it is a loose connector in the cable, in the PSU (but it does not seem to be limited to one PCIe 8-pin output (PSU is modular) or if it is the motherboard 8-pin header. When I have a bit more brain in the next day or so I will spend more time examining it.
In preparation for a future upgrade to Xeon and twin-GPU I have ordered a new high capacity PSU which will arrive on Wednesday. I will try the board with all new cables and the new PSU. If the PCIe ROG LEDs flicker then, I have proved it is the motherboard and Scan have confirmed they will accept it back.
No sleep because of the UK gales last night and my brain hurts! I did manage to install a Noctua DH15 cooler though - that thing is huge!
-
If you get one of the LSI 9201 cards they will use SAS to 4xSATA forward breakout cables.
-
PM sent re some spare drives I have.
EDIT : The 9201-8i and -16i cards are already in IT mode but may have old firmware. The current firmware is version P20 I think. My 9201-8i had P11 when I got it.
-
unRAID already is 64-bit and there are people using 64Gb+ according to the poll thread...
-
I have started the RMA process but of course it is a weekend now. I bought the motherboard and CPU in March as a bundle deal from Scan in the UK so it will be interesting to hear which part they want back.
-
OK, I am now a step closer to working out what my hardware issue is.
PSU self-tests green.
PSU cables 20-pin and 8-pin to motherboard
CPU air cooler fitted and fan connected to CPU_FAN
One RAM stick in DIMM_A2 (as advised by manual)
Power/Reset buttons and HDD_LED/PWR_LED to motherboard header
The first time I turned it on, the CPU fan spun normally. I got all the way to the BIOS, reset to defaults and allowed the machine to boot. I got all the way to the unRAID boot choice screen without issue. I selected the normal unRAID boot option and it seemed that the early stages of an unRAID boot were proceeding (about ten seconds) and then something failed with the hardware. The POST LED flickered and alternated between 00 and 04. The CPU fan changed speed and "fluttered" unevenly in speed. I powered off.
Now, despite clearing CMOS and removing the battery the machine fails POST immediately on power on. I get 00 then it alternates rapidly to 04 "PCH initialisation before microcode loading" and back to 00. The CPU fan "flutters" in speed and the motherboard red CPU error LED lights and flickers rapidly.
Normally the CPU error LED would point to the CPU but the 04 PCH points to the motherboard.
What do you think?
-
They are good value yes, but will not fit my usage. I don't think I need that many cores, and at a low clock speed.
-
Right - I checked the pumps and they were fine. Flow was suitable but I cranked them up and blew a load of old bubbles out of the tubes at the same time. No change in POST codes.
I did notice that it sat on A9 while on the unRAID boot choice screen then the instant I selected normal boot it flicked very briefly to F6 then changed to FF and sat there.
I have now drained and stripped the machine to the bare parts and will swap the CPU water block for a generic air cooler tomorrow when it arrives. I have a spare GPU now as well (1050ti) so apart from the PSU (which self-tests OK), there is nothing left that I can replace. I will set my working unRAID USB aside and use the trial USB stick I have just set up.
If I get the FF code with the bare board, CPU, one memory stick and iGPU then I will briefly set up a bootable WIn10 or Linux install on a spare SSD and see if it does it with that. I may have to buy a PSU tester too. After that if I still get the FF then I can talk to Scan in the UK to start any appropriate RMA process.
If I pass the barebones boot, I will add in the second memory and the 1050ti and see how we go.
-
Hmm... I think the pumps were running (dual D5s) but I can make sure flow is good. It is certainly worth checking. I can review the TIM too but it has only been since March when the CPU was fitted. PSU passes its self test when all cables are unplugged.
-
On the consumer boards, FF is usually an error code. A0 is most often the "everything is normal A-Ok" code.
I don't have a bootable disk yet but I will when I have stripped the machine down. The issue has appeared suddenly. Last night I had one unexpected shutdown. I got another this morning then this afternoon it became constant on every boot.
-
As I said, I would normally wait for the W-2145 8C/16T but it simply isn't available and Scan in the UK are under NDA not to disclose a release date but my current unRAID and gaming box is dead (see my "FF POST" thread in the General forum.)
Now I think about it, I suppose a twin Xeon 4C/8T machine would fit my needs too.
-
I think this thread best goes in here. I am needing help diagnosing the cause of a FF Post error on my unRAID machine.
Specs are as follows...unRAID : 6.4.0-rc9f on iGPU
Mobo : ASUS Maximus IX Formula (current BIOS, in warranty)
CPU : Intel i7 7700K (in warranty)
RAM : 2x16Gb Corsair Vengeance DDR4-3000 (in warranty)
GPU : Nvidia 780ti 3Gb (no warranty)
PSU : Corsair AX860i (unknown if in warranty)HDD : 4x WD Red 8Tb (in warranty)
Cache : Samsung 850PRO 512Gb (in warranty)
NVMe : Samsung 960PRO 1Tb (in warranty)
PCIe : Asus Hyper M.2 Mini x4 (in warranty)
PCIe : Inateck USB 3.0 x5e/x2i
Symptom : POST is successful all the way till unRAID presents its boot/boot with GUI, safe boot, safe boot with GUI, memtest screen. I can hold it there and it is all fine.
The INSTANT I select any unRAID boot option (even safe mode) the motherboard immediately flips to FF. There are no warning LEDs on the motherboard anywhere.
unRAID continues to load for about 30 seconds, usually reaching the root login. There is GUI activity over the LAN if watched from the iPad. After about 30s, the PC will simply shut down.
Things I have tried : pull all PCIe cards, all HDD/SSD/NVMe devices - no change. Try RAM one stick at a time - no change. Reset BIOS to defaults - no change.
What I am about to try : remove all water-cooling and re-fit air coolers to CPU and GPU so I can pull the GPU and run it off the iGPU only.
What is it that unRAID does within a second of passing the blue unRAID BOOT screen?
EDIT : I forgot to mention, I tried a different USB stick with trial license and it had no effect.
-
I am totally confused by the current Xeon lineup and would appreciate some advice please.
Which is the recommended Xeon for a single-cpu server board that has 8C/16T or equivalent?
I need DDR4 ECC and must have a single CPU. It can support a full sized board as my current case goes all the way up to SSI-EEB. I would prefer the current generation for power efficiency. Its intended use is unRAID (1C/2T), Plex (1C/2T) and gaming (4C/8T). I would like reasonable clock speeds due to the gaming use. I would like a little headroom for future needs hence mentioning 8C/16T.
I would normally have waited for the Xeon W-2145 but they are not available in retail yet.
Thank you in advance.
-
Yes the GPU is in its own IOMMU. It works with Windows and Ubuntu.
Tomorrow is draining, tearing down and refitting old air coolers so I can separate and test. Ugh!
-
You may be right but I have just had a total computer failure... FF Post error the moment unRAID starts off the onboard graphics... so it means a shopping trip anyway.
I will have to drain and tear down the entire PC since it is all water cooled and with rigid tubing but I may be able to isolate the faulty component. The GPU is well out of warranty and has had a hard life being highly overclocked since day one. The motherboard, CPU and RAM are still in warranty.
I will report back once I make any progress.
-
I have the processor iGPU enabled in the bios. unRAID boots off that and I can see the output fine for the unRAID log from that HDMI connection. The 780ti is in the first PCIe x16 slot and is not assigned to unRAID. I simply make it available to the VM on the template screen along with its sound card.
It all works fine in my Win10 VM (which is stopped at the moment). It is just the Linux Mint VM which is giving the typical Mint/nvidia black screen boot problems that were usually resolved by adding nomodeset parameter to the grub boot screen.
I simply cannot get past the black screen when I give the 780ti to Mint in the Linux template. I can see output from grub - I can edit the grub options... I just can't get the Mint installer to load through the 780ti.
-
I have erased that VM and started again.
1. When I assign the VNC GPU, I can complete the installation properly but of course have no nvidia drivers available for the discrete GPU.
2. If I assign the discrete nvidia GPU and try to create a new VM, I see the bios splash, get the grub menu and can 'e' to add the nomodeset parameter to the options. Regardless of whether I try the main or compatibility boot, if I 'ctrl-x' to proceed with the boot, I just get a solid black screen with no blinking cursor. Pressing ctrl-alt-del will reboot the session and bring me back to the bios then grub screen. Nothing I have tried will allow me to proceed.
Any help please?
EDIT : Adding nvidia.modeset=0 to the options in grub menu passes the solid black screen, shows the small Mint logo with dots for a few seconds then gives the blank screen with blinking cursor. It doesn't get past that though.
-
Could someone point me to a guide to install a Linux Mint VM when you have an nVidia GPU please? I am hitting the "black screen on boot" issue that seems to plague nVidia cards.
If I pass the nVidia GPU to the VM I don't even get the grub menu to add the nomodeset parameter. If I use the VNC GPU then I do get grub and can get into the desktop and install but cannot add the nVidia drivers.
I am stumped.
-
I would appreciate some advice on which specific sound card is recommended for use with unRAID and a gaming VM using headphones.
I have a small under monitor sound bar which works perfectly in the VM and is fine for casual stereo sound when my wife and I are listening to a YouTube video together but the majority of my listening and gaming is done with a pair of Grado SR60 headphones.
The reason I am asking is that first I noticed that my onboard sound would not break out into its own IOMMU group. From a forum search I understand this is an issue on some Skylake and Kabylake boards (ASUS Maximus IX Formula in my case). The warning when starting the VM is clear that it is the group the onboard sound is in.
Next I thought to try my external Roland Quad Capture over USB since it has a headphones monitor socket. I quickly discovered that the audio was faint and very, very distorted. I checked the Roland support site and saw the disclaimer of "This driver cannot be used in a virtual Windows environment, such as Hyper-V or Virtual PC." Damn, there goes that idea.
I am now at the position of needing a PCIe sound card. I do have a spare PCIe 3.0 x1 slot on the motherboard so please could you suggest something. The main brands I have in front of me at Scan in the UK are ASUS and Creative.
=====================================
EDIT : Thread title changed and method for solving detailed below
I have managed to pass through my Roland Quad Capture successfully to the VM and get rid of the poor, choppy sound from it.
Thanks to gridrunner in his YouTube video on how to pass a USB controller to the VM, it works perfectly. In the video he makes a comment about how external sound cards generally prefer to be on a stubbed USB controller that has been passed to the VM rather than just being handed to the VM directly. This was the key to getting the Roland working. Once I stubbed my PCIe USB controller in the syslinux file, rebooted, set the USB mode in the VM to XHCI (3.0) and gave the whole controller to the VM, all issues with the Roland ceased and it behaved as expected.
Thanks, gridrunner - you saved me from buying a sound card!
-
If you have the share as "cache prefer" it will fill the cache first then overflow to the array until Mover can sort it out. If the share is "cache only" it will only use the cache until it is full then stop.
-
Lee - SpaceInvaderOne covers this in his unRAID Introduction to VMs video... I have just started this video myself as I am working through setting up a Win10 VM for the first time.
-
It was really hard to measure the temperature in the X2M case as the card was just above the PSU and facing downwards. I have moved the card over to the main machine now and can get a better look at it through the side panel.
Creating Linux Mint VM with nVidia GPU?
in VM Engine (KVM)
Posted
I have managed to get it to work in SeaBIOS rather than OVMF but need to understand the consequences.
1. Passing the 1080 Ti ROM in the VM definition (as per gridrunner's video) - no change, I get the grub menu then a blank screen
2. Recreate the VM with SeaBIOS. This worked in that the initial boot seemed slower but I got the Mint splash icon instead of the grub menu. I then ended up on a Mint desktop in emulated GPU mode at 640x480. I was able to complete the install, update the nVidia drivers and get a proper resolution.
What are the key differences between SeaBIOS and OVMF? How can I get the grub menu when in SeaBIOS? Can I switch that VM to OVMF now I have managed to create the vdisk?
I did try creating a second OVMF Mint VM and pointing it to the vdisk from the SeaBIOS one but got thrown into a shell rather than Grub.