Need help getting Intel IGP to work again

Message boards : GPUs : Need help getting Intel IGP to work again
Message board moderation

To post messages, you must log in.

AuthorMessage
ProDigit

Send message
Joined: 8 Nov 19
Posts: 713
United States
Message 107024 - Posted: 9 Feb 2022, 1:34:22 UTC
Last modified: 9 Feb 2022, 1:40:25 UTC

I'm running Lubuntu 18.04.6, updated from 18.04.4.
I had to reinstall the Beignet drivers, because it's an old Celeron, pushing 2x RTX 2000 series GPUs, and used to run the Collatz on the intel IGP just fine..
It was running the 'franco d' whatever' boinc package before, but now running the one provided with the Ubuntu repositories.

After some playing around everything works, except for the Intel IGP.
The log says something like:

....
App version refers to missing GPU type intel_gpu
Application uses missing intel_gpu GPU.
missing coprocessor for task collatz_sieve.....


The manager shows "GPU missing, waiting to run (0.25CPU + intel_gpu GPU)"

lspci shows the intel GPU, and intel_gpu_top works (just shows the gpu is passive/inactive).

what do I do now?
ID: 107024 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 4945
United Kingdom
Message 107025 - Posted: 9 Feb 2022, 8:29:58 UTC - in response to Message 107024.  

Check the first 30-40 lines of the message log from the last time BOINC was restarted, or restart again to get a fresh set.
ID: 107025 · Report as offensive
ProDigit

Send message
Joined: 8 Nov 19
Posts: 713
United States
Message 107027 - Posted: 9 Feb 2022, 14:40:05 UTC - in response to Message 107025.  

already did.
It's definitely a software issue.
Not sure if boot order in bios is going to make any difference, as lspci recognizes the GPU, and intel_gpu_tools is installed and recognizes the GPU (which means OpenCL works via the beignet drivers.
ID: 107027 · Report as offensive
Ian&Steve C.

Send message
Joined: 24 Dec 19
Posts: 227
United States
Message 107028 - Posted: 9 Feb 2022, 14:48:52 UTC - in response to Message 107027.  
Last modified: 9 Feb 2022, 14:49:55 UTC

If BOINC doesn’t detect it, then the OpenCL drivers likely aren’t installed properly. lspci detects the hardware is there, not if drivers are installed.

Is it detected by clinfo?
ID: 107028 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 4945
United Kingdom
Message 107029 - Posted: 9 Feb 2022, 15:36:41 UTC - in response to Message 107027.  

already did.
But you didn't show us the startup messages.

I agree with Ian - it's likely to be a driver issue.

Intel produces separate (distinct) drivers for their CPUs and the GPU component in the CPU package. BOINC would list them separately. If you picked the CPU driver only, that wouldn't make the GPU available.
ID: 107029 · Report as offensive
ProDigit

Send message
Joined: 8 Nov 19
Posts: 713
United States
Message 107056 - Posted: 11 Feb 2022, 19:13:16 UTC - in response to Message 107028.  

If BOINC doesn’t detect it, then the OpenCL drivers likely aren’t installed properly. lspci detects the hardware is there, not if drivers are installed.

Is it detected by clinfo?


$ clinfo
Number of platforms                               3
  Platform Name                                   Intel Gen OCL Driver
  Platform Vendor                                 Intel
  Platform Version                                OpenCL 2.0 beignet 1.3
  Platform Profile                                FULL_PROFILE


Yes, recognized.
And like I mentioned, intel_gpu_top also shows something, which means OpenCL is installed (though from the Beignet drivers, which shouldn't really matter, as it's an older CPU).
Still, it shows, which means OpenCL is installed successfully.
If it wasn't installed, it would show an error.

                   render busy:   0%:                                        render space: 0/16384

                          task  percent busy
                                                              vert fetch: 0 (0/sec)
                                                              prim fetch: 0 (0/sec)
                                                           VS invocations: 0 (0/sec)
                                                           GS invocations: 0 (0/sec)
                                                                GS prims: 0 (0/sec)
                                                           CL invocations: 0 (0/sec)
                                                                CL prims: 0 (0/sec)
                                                           PS invocations: 0 (0/sec)
                                                           PS depth pass: 0 (0/sec)
ID: 107056 · Report as offensive
Les Bayliss
Help desk expert

Send message
Joined: 25 Nov 05
Posts: 1654
Australia
Message 107057 - Posted: 11 Feb 2022, 19:41:24 UTC - in response to Message 107056.  

You still haven't shown us the startup messages from the Event Log!
ID: 107057 · Report as offensive
ProDigit

Send message
Joined: 8 Nov 19
Posts: 713
United States
Message 107058 - Posted: 11 Feb 2022, 19:42:16 UTC - in response to Message 107029.  
Last modified: 11 Feb 2022, 19:44:57 UTC

already did.
But you didn't show us the startup messages.

I agree with Ian - it's likely to be a driver issue.

Intel produces separate (distinct) drivers for their CPUs and the GPU component in the CPU package. BOINC would list them separately. If you picked the CPU driver only, that wouldn't make the GPU available.

I largely showed the messages, generated by the collatz in the log.
I removed the app_config.xml from the collatz, and reset it to not use CPU.
Now there's no more reference in the log to the Intel GPU at all.
All there is, is references to my Nvidia GPUs that are installed.

Fri 11 Feb 2022 11:24:18 AM EST |  | Starting BOINC client version 7.9.3 for x86_64-pc-linux-gnu
Fri 11 Feb 2022 11:24:18 AM EST |  | log flags: file_xfer, sched_ops, task
Fri 11 Feb 2022 11:24:18 AM EST |  | Libraries: libcurl/7.58.0 OpenSSL/1.1.1 zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3
Fri 11 Feb 2022 11:24:18 AM EST |  | Data directory: /var/lib/boinc-client
Fri 11 Feb 2022 11:24:19 AM EST |  | CUDA: NVIDIA GPU 0: NVIDIA GeForce RTX 2070 (driver version 510.47, CUDA version 11.6, compute capability 7.5, 4096MB, 3968MB available, 14930 GFLOPS peak)
Fri 11 Feb 2022 11:24:19 AM EST |  | CUDA: NVIDIA GPU 1: NVIDIA GeForce RTX 2060 (driver version 510.47, CUDA version 11.6, compute capability 7.5, 4096MB, 3970MB available, 12902 GFLOPS peak)
Fri 11 Feb 2022 11:24:19 AM EST |  | OpenCL: NVIDIA GPU 0: NVIDIA GeForce RTX 2070 (driver version 510.47.03, device version OpenCL 3.0 CUDA, 7982MB, 3968MB available, 14930 GFLOPS peak)
Fri 11 Feb 2022 11:24:19 AM EST |  | OpenCL: NVIDIA GPU 1: NVIDIA GeForce RTX 2060 (driver version 510.47.03, device version OpenCL 3.0 CUDA, 5935MB, 3970MB available, 12902 GFLOPS peak)
Fri 11 Feb 2022 11:24:19 AM EST |  | [libc detection] gathered: 2.27, Ubuntu GLIBC 2.27-3ubuntu1.4
Fri 11 Feb 2022 11:24:19 AM EST |  | Host name: ****
Fri 11 Feb 2022 11:24:19 AM EST |  | Processor: 4 GenuineIntel Intel(R) Pentium(R) Gold G5600 CPU @ 3.90GHz [Family 6 Model 158 Stepping 11]
Fri 11 Feb 2022 11:24:19 AM EST |  | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon $Fri 11 Feb 2022 11:24:19 AM EST |  | OS: Linux Ubuntu: Ubuntu 18.04.6 LTS [4.15.0-168-generic|libc 2.27 (Ubuntu GLIBC 2.27-3ubuntu1.4)]
Fri 11 Feb 2022 11:24:19 AM EST |  | Memory: 7.68 GB physical, 2.00 GB virtual
Fri 11 Feb 2022 11:24:19 AM EST |  | Disk: 54.28 GB total, 31.36 GB free
Fri 11 Feb 2022 11:24:19 AM EST |  | Local time is UTC -5 hours
Fri 11 Feb 2022 11:24:19 AM EST |  | VirtualBox version: 5.2.42_Ubuntur137960


The Intel IGP is working though, when I do CTRL+ALT+F3 for instance, I get a terminal on the IGP output.
And, beignet says the drivers are installed. And so is Intel-OpenCL drivers.
Maybe there's a conflict between the intel OpenCL and the beignet drivers.
ID: 107058 · Report as offensive
Ian&Steve C.

Send message
Joined: 24 Dec 19
Posts: 227
United States
Message 107065 - Posted: 12 Feb 2022, 18:06:52 UTC - in response to Message 107058.  

The fact that you installed two different Intel drivers simultaneously probably would have been helpful information to post initially. And that’s an obvious thing to try. You never want two drivers for the same device.

Remove both drivers. Re-install only the Intel OpenCL icd package.
ID: 107065 · Report as offensive
ProDigit

Send message
Joined: 8 Nov 19
Posts: 713
United States
Message 107090 - Posted: 15 Feb 2022, 23:51:42 UTC - in response to Message 107065.  

The fact that you installed two different Intel drivers simultaneously probably would have been helpful information to post initially. And that’s an obvious thing to try. You never want two drivers for the same device.

Remove both drivers. Re-install only the Intel OpenCL icd package.

OpenCL package is probably the one not working. Will look at it later.
Beignet is the proper opencl package for my IGP.
ID: 107090 · Report as offensive

Message boards : GPUs : Need help getting Intel IGP to work again

Copyright © 2023 University of California. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.