Blender 2.82a-3.fc32 completely hangs Fedora Gnome Wayland and X11 #76529

New Issue

ArbySmith · 2020-05-08T03:18:09+02:00

ArbySmith commented

2020-05-08 03:18:09 +02:00

System Information
Operating system: Linux-5.6.8-300.fc32.x86_64-x86_64-with-glibc2.29 64 Bits
Graphics card: Mesa Intel(R) HD Graphics 630 (KBL GT2) Intel 4.6 (Core Profile) Mesa 20.0.6

Blender Version
Broken: version: 2.82 (sub 7), branch: unknown, commit date: 1970-01-01 00:00, hash: rBunknown
Worked: (optional)

Short description of error
I have had all Blender versions from 2.80 fail under Fedora 30 31 & 32.
I am using 2.82a now. Blender completely hangs Gnome and requires hard restart.

Exact steps for others to reproduce the error
The only real changes to the preferences is "right click selection"

Lately I have tried adding a few UV spheres intersecting each other.
I add a plane at origin and scale in edit mode at 3x then move it to base of spheres.
I add Subdivision surface at 3 and 3 for both spheres.
Sometimes I get a render in before it crashes.
I then try to rotate the view in the scene.

Sometimes blender crashes very early on, other times within the time
it takes to do the above steps (within seconds other times a few minutes).

Nothing in the journal since the whole system hangs and requires hard reset.

This happens in Cycles and EVEE.
I have only ever had EVEE render in the latest build in Fedora 32 packages.

I have used blender for many years with systems with only 4 GB RAM and
never had a problem.
The RAM is far from fully used in this example.

I don't know if this is a kernel, Fedora, Intel i3-7100/GPU, driver problem
or specific to blender or maybe the hardware.
Asrock Deskmini H110M-STX (not COM model)
i3-7100 3.9 Ghz
4 GB Crucial RAM

I would like some help troubleshooting.
I have search for this specific example but have not found an exact match.
I have only seen bug reports of this with dedicated graphics cards.

Maybe with system-info.txt someone can supply a solution.

(sidenote: Portable 2.79b has also hanged system but far less often and random)

system-info.txt

**System Information** Operating system: Linux-5.6.8-300.fc32.x86_64-x86_64-with-glibc2.29 64 Bits Graphics card: Mesa Intel(R) HD Graphics 630 (KBL GT2) Intel 4.6 (Core Profile) Mesa 20.0.6 **Blender Version** Broken: version: 2.82 (sub 7), branch: unknown, commit date: 1970-01-01 00:00, hash: `rBunknown` Worked: (optional) **Short description of error** I have had all Blender versions from 2.80 fail under Fedora 30 31 & 32. I am using 2.82a now. Blender completely hangs Gnome and requires hard restart. **Exact steps for others to reproduce the error** The only real changes to the preferences is "right click selection" Lately I have tried adding a few UV spheres intersecting each other. I add a plane at origin and scale in edit mode at 3x then move it to base of spheres. I add Subdivision surface at 3 and 3 for both spheres. Sometimes I get a render in before it crashes. I then try to rotate the view in the scene. Sometimes blender crashes very early on, other times within the time it takes to do the above steps (within seconds other times a few minutes). Nothing in the journal since the whole system hangs and requires hard reset. This happens in Cycles and EVEE. I have only ever had EVEE render in the latest build in Fedora 32 packages. I have used blender for many years with systems with only 4 GB RAM and never had a problem. The RAM is far from fully used in this example. I don't know if this is a kernel, Fedora, Intel i3-7100/GPU, driver problem or specific to blender or maybe the hardware. Asrock Deskmini H110M-STX (not COM model) i3-7100 3.9 Ghz 4 GB Crucial RAM I would like some help troubleshooting. I have search for this specific example but have not found an exact match. I have only seen bug reports of this with dedicated graphics cards. Maybe with system-info.txt someone can supply a solution. (sidenote: Portable 2.79b has also hanged system but far less often and random) [system-info.txt](https://archive.blender.org/developer/F8519422/system-info.txt)

ArbySmith commented

2020-05-08 03:18:09 +02:00

Added subscriber: @BlastedPupil

Alaska commented

2020-05-08 09:00:44 +02:00

Added subscriber: @Alaska

Alaska commented

2020-05-08 09:00:44 +02:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Alaska commented

2020-05-08 09:00:44 +02:00

In the title of the post you said you were using Wayland. Blender 2.82 doesn't have a Wayland implementation. This means many of the issues you're experiencing may be because you're running the Xorg version of Blender under Wayland. A Wayland implementation is currently underdevelopment with the first initial patch being added a week ago 66e70fe299 for developers to test.

In the title of the post you said you were using Wayland. Blender 2.82 doesn't have a Wayland implementation. This means many of the issues you're experiencing may be because you're running the Xorg version of Blender under Wayland. A Wayland implementation is currently underdevelopment with the first initial patch being added a week ago 66e70fe299 for developers to test.

Philipp Oeser commented

2020-05-08 11:14:20 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2020-05-08 11:14:20 +02:00

I have no such issues

System Information
Operating system: Linux-5.5.13-200.fc31.x86_64-x86_64-with-fedora-31-Thirty_One 64 Bits
Graphics card: GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.64
version: 2.90 (sub 0), branch: master, commit date: 2020-05-08 03:43, hash: b4d50d3f07

I have no such issues **System Information** Operating system: Linux-5.5.13-200.fc31.x86_64-x86_64-with-fedora-31-Thirty_One 64 Bits Graphics card: GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.64 version: 2.90 (sub 0), branch: master, commit date: 2020-05-08 03:43, hash: `b4d50d3f07`

ArbySmith commented

2020-05-09 14:42:38 +02:00

Thank you for replying.

I should have mentioned that I have tried also in Gnome Xorg and that
I have tried the Fedora and portable versions of each.
I just tried again to confirm that it still happens.

(I have also tried in live version of Debian)

Maybe this has to do with this being a Kaby Lake and mitigations are
affecting something ?

(I have tried with another laptop with an AMD and seems to work fine,
but slow and it gets hot)

Another thought is this is a small desktop machine/CPU but uses
laptop sodimm RAM but I don't think that would matter.

I will review how to compile blender in the meantime, which I haven't
tried before.

Maybe someone can recommend some compiling options for this
specific processor, i3-7100 ?
If more info is needed for these options I will provide what I can.

Thanks again

Thank you for replying. I should have mentioned that I have tried also in Gnome Xorg and that I have tried the Fedora and portable versions of each. I just tried again to confirm that it still happens. (I have also tried in live version of Debian) Maybe this has to do with this being a Kaby Lake and mitigations are affecting something ? (I have tried with another laptop with an AMD and seems to work fine, but slow and it gets hot) Another thought is this is a small desktop machine/CPU but uses laptop sodimm RAM but I don't think that would matter. I will review how to compile blender in the meantime, which I haven't tried before. Maybe someone can recommend some compiling options for this specific processor, i3-7100 ? If more info is needed for these options I will provide what I can. Thanks again

ArbySmith commented

2020-05-20 20:13:02 +02:00

Just to update and let you know I am still trying here.

I have also tried flatpak installs in Wayland and X11 but there is not difference.

Currently trying to build blender from master but I am getting errors.
CMakeLists.txt seems to have to be manually remove each time then complains
that it is not there.

I will keep trying

Just to update and let you know I am still trying here. I have also tried flatpak installs in Wayland and X11 but there is not difference. Currently trying to build blender from master but I am getting errors. CMakeLists.txt seems to have to be manually remove each time then complains that it is not there. I will keep trying

ArbySmith changed title from ~~Blender 2.82a-3.fc32 completely hangs Fedora Gnome Wayland~~ to Blender 2.82a-3.fc32 completely hangs Fedora Gnome Wayland and X11

2020-05-20 20:13:43 +02:00

Alaska commented

2020-05-21 06:13:39 +02:00

Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'

Alaska commented

2020-05-21 06:13:39 +02:00

The thing is that I and @lichtwerk and many other users don't experience this issue. So it's really hard for us to diagnose the problem. You could attach a debugger to Blender and send the results to us. But I don't know how to do that and thus can't run you through the steps of setting it up.

One thing you could potentially try is a clean install of your operating system or of a different distribution of Linux. Sorry I can't be of much help.

The thing is that I and @lichtwerk and many other users don't experience this issue. So it's really hard for us to diagnose the problem. You could attach a debugger to Blender and send the results to us. But I don't know how to do that and thus can't run you through the steps of setting it up. One thing you could potentially try is a clean install of your operating system or of a different distribution of Linux. Sorry I can't be of much help.

ArbySmith commented

2020-05-21 16:55:10 +02:00

I will research on running a Blender debugger and continue trying to compile
Blender.

The OS is new install of Fedora 32 but I am considering trying another distro.
It may be due to some Intel Gen7 cpu mitigations that have yet to be updated.
I hear that kernel 5.7 will include some updates and am hoping it resolves this.
(Otherwise I may have to adamantly recommend against Asrock products)

I have seen these same problems in previous releases in forums, etc. but it
seems they have resolved for others but for some reason not here.

I am also thinking that Blender may try to allocate memory that may conflict
with the current OS, being that I am running with only 4GB and integrated
graphics. I'm not saying it's a Blender problem but some incompatibility and
the mitigations mentioned above.

I will keep updating any progress here in case it helps someones else and/or
blender in general.

I will research on running a Blender debugger and continue trying to compile Blender. The OS is new install of Fedora 32 but I am considering trying another distro. It may be due to some Intel Gen7 cpu mitigations that have yet to be updated. I hear that kernel 5.7 will include some updates and am hoping it resolves this. (Otherwise I may have to adamantly recommend against Asrock products) I have seen these same problems in previous releases in forums, etc. but it seems they have resolved for others but for some reason not here. I am also thinking that Blender may try to allocate memory that may conflict with the current OS, being that I am running with only 4GB and integrated graphics. I'm not saying it's a Blender problem but some incompatibility and the mitigations mentioned above. I will keep updating any progress here in case it helps someones else and/or blender in general.

Alaska commented

2020-05-22 06:01:42 +02:00

The RAM thing could defiantly be a issue. If Intel GPUs operate like some of the older stuff I've seen with computers, in theory you will have 2GB of "VRAM" for your GPU and 2GB of RAM for your CPU. This isn't that much to run Blender.

However, I may be wrong on this assumption.

The RAM thing could defiantly be a issue. If Intel GPUs operate like some of the older stuff I've seen with computers, in theory you will have 2GB of "VRAM" for your GPU and 2GB of RAM for your CPU. This isn't that much to run Blender. However, I may be wrong on this assumption.

Gary Parris commented

2020-06-13 07:06:04 +02:00

Added subscriber: @GAPsWorld

Gary Parris commented

2020-06-13 07:06:04 +02:00

I have also been having issues with 2.83 & 2.90 of the system hanging, i get mouse abality and can manage to shutdown safely through memorised key presses or using a kill command set up ready for this, but with varying success. a reboot is the only thing possible once blender hang. workbench also freezes!

I have used Xorg with Gnome and Cinnamon (my default), with Mesa drivers, i've even used the AMD GPU console to see what Blender is doing with GPU, it only works in CPU and doesn't even show my AMD or Intel HD 620, also very unstable in Workbench, EEVEE and cycles, it shows a mouse cursor as corrupted lines. workbench also freezes! i have also tried Fedora from FC 30/31/32. i have the latest Mesa driver for amdgpu and am using a HP laptop with a passthrough GPU Intel HD 620/AMD Radeon R7 M440.

i can use 2.82 without crashing but still my GPU doesnt show as available or render in GPU cycles or eevee.

i have just tried 2.90 on my other main system using a Nvidia GTX 1060 and it works flawlessly no freeze no errors, GPU and CPU. If AMD are working with blender and Linux why are their Drivers not upto date or working with linux, its ridiculus that AMD cannot support Linux properly and with blender to get these issues sorted.

I have also been having issues with 2.83 & 2.90 of the system hanging, i get mouse abality and can manage to shutdown safely through memorised key presses or using a kill command set up ready for this, but with varying success. a reboot is the only thing possible once blender hang. workbench also freezes! I have used Xorg with Gnome and Cinnamon (my default), with Mesa drivers, i've even used the AMD GPU console to see what Blender is doing with GPU, it only works in CPU and doesn't even show my AMD or Intel HD 620, also very unstable in Workbench, EEVEE and cycles, it shows a mouse cursor as corrupted lines. workbench also freezes! i have also tried Fedora from FC 30/31/32. i have the latest Mesa driver for amdgpu and am using a HP laptop with a passthrough GPU Intel HD 620/AMD Radeon R7 M440. i can use 2.82 without crashing but still my GPU doesnt show as available or render in GPU cycles or eevee. i have just tried 2.90 on my other main system using a Nvidia GTX 1060 and it works flawlessly no freeze no errors, GPU and CPU. If AMD are working with blender and Linux why are their Drivers not upto date or working with linux, its ridiculus that AMD cannot support Linux properly and with blender to get these issues sorted.

ArbySmith commented

2020-06-13 22:51:57 +02:00

I have now tried 2.83 portable version using Wayland and Xorg.
The problem continues but seems to take longer before it hangs the system.

Trying to find a reproducible event but I have yet to find one.
It seems that it may be related to change back to solid view after LookDev or Render view.
Another possibility is toggling back and forth from the ortho/perspective (using 5 on numpad)

I still have had no luck compiling but this might be Fedora specific problem.
I have installed missing libs that compiler could not find but it still fails to find them.

Sorry if the following is a bit of subject but since user is also experiencing a similar hang...

In #76529#953107, @GAPsWorld wrote:

...it only works in CPU and doesn't even show my AMD...

i can use 2.82 without crashing but still my GPU doesnt show as available or render in GPU cycles or eevee.

I have also been trying to use on a machine with Intel i5 M 450 and AMD RV710/M92 and although it has
been working it does not show as GPU available in Blender even though inxi shows "direct render: Yes"

Have you had any success compiling in Fedora ?

I have now tried 2.83 portable version using Wayland and Xorg. The problem continues but seems to take longer before it hangs the system. Trying to find a reproducible event but I have yet to find one. It seems that it may be related to change back to solid view after LookDev or Render view. Another possibility is toggling back and forth from the ortho/perspective (using 5 on numpad) I still have had no luck compiling but this might be Fedora specific problem. I have installed missing libs that compiler could not find but it still fails to find them. Sorry if the following is a bit of subject but since user is also experiencing a similar hang... > In #76529#953107, @GAPsWorld wrote: > >...it only works in CPU and doesn't even show my AMD... > > i can use 2.82 without crashing but still my GPU doesnt show as available or render in GPU cycles or eevee. > I have also been trying to use on a machine with Intel i5 M 450 and AMD RV710/M92 and although it has been working it does not show as GPU available in Blender even though inxi shows "direct render: Yes" Have you had any success compiling in Fedora ?

Gary Parris commented

2020-06-14 11:14:08 +02:00

In #76529#953360, @BlastedPupil wrote:
I have now tried 2.83 portable version using Wayland and Xorg.
The problem continues but seems to take longer before it hangs the system.

Trying to find a reproducible event but I have yet to find one.
It seems that it may be related to change back to solid view after LookDev or Render view.
Another possibility is toggling back and forth from the ortho/perspective (using 5 on numpad)

I still have had no luck compiling but this might be Fedora specific problem.
I have installed missing libs that compiler could not find but it still fails to find them.

Sorry if the following is a bit of subject but since user is also experiencing a similar hang...

In #76529#953107, @GAPsWorld wrote:

...it only works in CPU and doesn't even show my AMD...

i can use 2.82 without crashing but still my GPU doesnt show as available or render in GPU cycles or eevee.

I have also been trying to use on a machine with Intel i5 M 450 and AMD RV710/M92 and although it has
been working it does not show as GPU available in Blender even though inxi shows "direct render: Yes"

Have you had any success compiling in Fedora ?

In #76529#953360, @BlastedPupil wrote:
I have now tried 2.83 portable version using Wayland and Xorg.
The problem continues but seems to take longer before it hangs the system.

Trying to find a reproducible event but I have yet to find one.
It seems that it may be related to change back to solid view after LookDev or Render view.
Another possibility is toggling back and forth from the ortho/perspective (using 5 on numpad)

I still have had no luck compiling but this might be Fedora specific problem.
I have installed missing libs that compiler could not find but it still fails to find them.

Sorry if the following is a bit of subject but since user is also experiencing a similar hang...

In #76529#953107, @GAPsWorld wrote:

...it only works in CPU and doesn't even show my AMD...

i can use 2.82 without crashing but still my GPU doesnt show as available or render in GPU cycles or eevee.

I have also been trying to use on a machine with Intel i5 M 450 and AMD RV710/M92 and although it has
been working it does not show as GPU available in Blender even though inxi shows "direct render: Yes"

Have you had any success compiling in Fedora ?

I've no luck at all with Passthrough nor with compiling its fails to build and halts on some repository that doesnt seem to respond, not sure if it it is linked to the current buildbot problems or not but tried to follow blenders instruction page to build but it doesnt seem to fork with fedora 30/31/32 currently

i also tried 2.79b and it doesnt recognise the AMDGPU either, nor does Luxcore it seems except at least luxcore shows some GPU usage when it passes the final image to the screen. Am tearing my hair out trying to deal with something that should ne a simple click install.

> In #76529#953360, @BlastedPupil wrote: > I have now tried 2.83 portable version using Wayland and Xorg. > The problem continues but seems to take longer before it hangs the system. > > Trying to find a reproducible event but I have yet to find one. > It seems that it may be related to change back to solid view after LookDev or Render view. > Another possibility is toggling back and forth from the ortho/perspective (using 5 on numpad) > > I still have had no luck compiling but this might be Fedora specific problem. > I have installed missing libs that compiler could not find but it still fails to find them. > > Sorry if the following is a bit of subject but since user is also experiencing a similar hang... > >> In #76529#953107, @GAPsWorld wrote: >> >>...it only works in CPU and doesn't even show my AMD... >> >> i can use 2.82 without crashing but still my GPU doesnt show as available or render in GPU cycles or eevee. >> > > I have also been trying to use on a machine with Intel i5 M 450 and AMD RV710/M92 and although it has > been working it does not show as GPU available in Blender even though inxi shows "direct render: Yes" > > Have you had any success compiling in Fedora ? > In #76529#953360, @BlastedPupil wrote: > I have now tried 2.83 portable version using Wayland and Xorg. > The problem continues but seems to take longer before it hangs the system. > > Trying to find a reproducible event but I have yet to find one. > It seems that it may be related to change back to solid view after LookDev or Render view. > Another possibility is toggling back and forth from the ortho/perspective (using 5 on numpad) > > I still have had no luck compiling but this might be Fedora specific problem. > I have installed missing libs that compiler could not find but it still fails to find them. > > Sorry if the following is a bit of subject but since user is also experiencing a similar hang... > >> In #76529#953107, @GAPsWorld wrote: >> >>...it only works in CPU and doesn't even show my AMD... >> >> i can use 2.82 without crashing but still my GPU doesnt show as available or render in GPU cycles or eevee. >> > > I have also been trying to use on a machine with Intel i5 M 450 and AMD RV710/M92 and although it has > been working it does not show as GPU available in Blender even though inxi shows "direct render: Yes" > > Have you had any success compiling in Fedora ? I've no luck at all with Passthrough nor with compiling its fails to build and halts on some repository that doesnt seem to respond, not sure if it it is linked to the current buildbot problems or not but tried to follow blenders instruction page to build but it doesnt seem to fork with fedora 30/31/32 currently i also tried 2.79b and it doesnt recognise the AMDGPU either, nor does Luxcore it seems except at least luxcore shows some GPU usage when it passes the final image to the screen. Am tearing my hair out trying to deal with something that should ne a simple click install.

Gary Parris commented

2020-06-18 05:28:59 +02:00

Here are screen grabs from Ubunto which i tried to use 2.90 Alpha on and in different modes maybe it will help, this is using the version downloaded from 16 June 2020

Here are screen grabs from Ubunto which i tried to use 2.90 Alpha on and in different modes maybe it will help, this is using the version downloaded from 16 June 2020 ![Screenshot from 2020-06-18 11-05-22.jpg](https://archive.blender.org/developer/F8629555/Screenshot_from_2020-06-18_11-05-22.jpg) ![Screenshot from 2020-06-18 11-04-57.jpg](https://archive.blender.org/developer/F8629557/Screenshot_from_2020-06-18_11-04-57.jpg) ![Screenshot from 2020-06-18 11-05-11.jpg](https://archive.blender.org/developer/F8629558/Screenshot_from_2020-06-18_11-05-11.jpg) ![Screenshot from 2020-06-18 11-03-17.jpg](https://archive.blender.org/developer/F8629561/Screenshot_from_2020-06-18_11-03-17.jpg) ![Screenshot from 2020-06-18 11-03-55.jpg](https://archive.blender.org/developer/F8629562/Screenshot_from_2020-06-18_11-03-55.jpg) ![Screenshot from 2020-06-18 11-04-32.jpg](https://archive.blender.org/developer/F8629563/Screenshot_from_2020-06-18_11-04-32.jpg) ![Screenshot from 2020-06-18 11-04-40.jpg](https://archive.blender.org/developer/F8629564/Screenshot_from_2020-06-18_11-04-40.jpg)

Euan de Kock commented

2020-07-14 13:38:13 +02:00

Added subscriber: @Euan

Euan de Kock commented

2020-07-14 13:38:13 +02:00

I've just recently started experiencing something similar. I run Fedora 32 on a Huawei matebook x, it's been very stable for about a year, running Fedora 31 and 32, but recently blender had become unusable. After a minute or so of working in blender the screen glitches. I'm left with an unresponsive desktop that seems to be stick between two screen updates, and jumps between them. I can get to a console with ctrl-alt-f3, but I cannot see any errors, and I can progressively kill tasks until I eventually force a logout. This only occurs when running blender, and it appears to do it with several versions, 2.8.1 to current at least. I suspect something has been upgraded in gnome or the kernel. I am not using any gpu resources, just the gen 8 i7 CPU. I have tried under Wayland and xorg.

Euan de Kock commented

2020-07-14 15:10:13 +02:00

This looks like an Intel graphics driver issue. It's been reported by a few people over here:

https://gitlab.freedesktop.org/drm/intel/-/issues/2176

This looks like an Intel graphics driver issue. It's been reported by a few people over here: https://gitlab.freedesktop.org/drm/intel/-/issues/2176

Alex Johnson commented

2020-08-31 21:50:29 +02:00

Added subscriber: @MasterF1

Alex Johnson commented

2020-08-31 21:50:29 +02:00

In #76529#978781, @Euan wrote:
I've just recently started experiencing something similar. I run Fedora 32 on a Huawei matebook x, it's been very stable for about a year, running Fedora 31 and 32, but recently blender had become unusable. After a minute or so of working in blender the screen glitches. I'm left with an unresponsive desktop that seems to be stick between two screen updates, and jumps between them. I can get to a console with ctrl-alt-f3, but I cannot see any errors, and I can progressively kill tasks until I eventually force a logout. This only occurs when running blender, and it appears to do it with several versions, 2.8.1 to current at least. I suspect something has been upgraded in gnome or the kernel. I am not using any gpu resources, just the gen 8 i7 CPU. I have tried under Wayland and xorg.

I am having the exact same issue! and I have no idea how to fix it, but do you think blender 2.9 would work?

> In #76529#978781, @Euan wrote: > I've just recently started experiencing something similar. I run Fedora 32 on a Huawei matebook x, it's been very stable for about a year, running Fedora 31 and 32, but recently blender had become unusable. After a minute or so of working in blender the screen glitches. I'm left with an unresponsive desktop that seems to be stick between two screen updates, and jumps between them. I can get to a console with ctrl-alt-f3, but I cannot see any errors, and I can progressively kill tasks until I eventually force a logout. This only occurs when running blender, and it appears to do it with several versions, 2.8.1 to current at least. I suspect something has been upgraded in gnome or the kernel. I am not using any gpu resources, just the gen 8 i7 CPU. I have tried under Wayland and xorg. I am having the exact same issue! and I have no idea how to fix it, but do you think blender 2.9 would work?

Gary Parris commented

2020-09-01 10:46:51 +02:00

i'm only able to use B282a at this stage everything newer is having problems with stability, it will freeze even with the factory defaults loaded, i have tried multiple versions and cant replicate exactly when it will freeze, it can be as simple as changing a value regardless of the mode, or render engine used, it seems to be a vram thing with either AMD GPU or INTEL passthrough to AMD GPU hybrids at this stage.

Richard Antalik commented

2020-11-26 20:45:28 +01:00

Closed as duplicate of #80458

Richard Antalik closed this issue

2020-11-26 20:45:28 +01:00

ArbySmith commented

2020-12-09 20:11:24 +01:00

It turns out it was that the motherboard wasn't compatible (Asrock Deskmini h110m-stx)
I have tried 2.79, 2.80, 2.81, 2.90, 2.91 and alll are working now.

The motherboard is made for Skylake but supposed to be upgradeable to Kaby Lake.
Apparently that is not true and they stopped shipping BIOS updates.

It turns out it was that the motherboard wasn't compatible (Asrock Deskmini h110m-stx) I have tried 2.79, 2.80, 2.81, 2.90, 2.91 and alll are working now. The motherboard is made for Skylake but supposed to be upgradeable to Kaby Lake. Apparently that is not true and they stopped shipping BIOS updates.

ArbySmith commented

2020-12-09 20:11:45 +01:00

Changed status from 'Duplicate' to: 'Resolved'

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Blender 2.82a-3.fc32 completely hangs Fedora Gnome Wayland and X11 #76529