Was gnif’s patch committed to the Linux kernel yet ?
Or are the kernel devs still holding this up by individually marking their territory on the patch ?
I have quasi confirmed, but more testing underway.
Vega GPUs still have their own set of bugs but it does appear fixed for bioses packing AGESA 1.1.0.0
Wonder how long it will take ASUS to roll out this BIOS, I’m on v1003 which has AGESA 1.0.0.5 (and the ability to not disable C-States, which gives me firmware bug errors at boot time).
I’ve a TR 1920x and want to try this vfio stuff with looking glass, but I need to get the system to clean boot first
This makes me sad, I too love ASUS, but as mentioned above, BIOS updates are very slow for release. if at all.
I like the ROG Zenith Extreme because it has the 2 by x16, and 2 by x8 lane PCIe slots, which I need (2 by x8 for LSI controllers, and 2 by x16 for GPU’s).
However, I don’t think I’ll be supporting ASUS too soon again because of these BIOS delays. I’ve had my TR and Zenith Extreme since they first came out, switched to linux about 2 months ago and still trying to get some of my errors out of my boot logs.
Yeah the lack of bios updates for the Zenith has been very disappointing. Probably the last time I go ASUS. I would’ve went for the Gigabyte Designare board had that been available at launch, oh well.
The update can’t be that far off since I’m assuming they will have something ready for TR2 launch, hopefully.
My last ASUS board was an AM2 thing… I had an early phenom in it, but when the next generation came out (AM2+) I was unable to use them without manually hacking an updated agesa into the BIOS. Still to date ASUS never released a new bios for the board.
So is this not going to be patched in the Linux kernel anymore ?
I’ve been holding off purchase of parts for my planned Threadripper build because of this bug. For 6 months or so, already.
Apart from the monster delay, meanwhile the DDR4 prices have of course gone up.
I plan on buying the ASRock Fatal1ty X399 Professional Gaming.
On Ubuntu 18.04, did patch kernel 4.15.18 with the tr.patch, compiled and installed. System boots, LookingGlass works great. However, after exiting VM, and trying to init it again, Im getting:
error: Failed to start domain win10
error: internal error: Unknown PCI header type ‘127’
Host: Radeon Pro WX 7100 Graphics
Passthrough: Asus Radeon RX Vega 56 OC 8GB
That means the reset issue is still present. It won’t reinitialize and even if you do, you will get a system lockup because you’re trying to reinitialize something that can’t be reinitialized.
Only solution is to kill power to the entire system (literally kill all power) and start the system from a pure cold boot. I had this problem non stop with the Fresco Logic FL1009 controller with a older firmware that can’t be updated.