Github messages for voidlinux
 help / color / mirror / Atom feed
* [ISSUE] mesa-20.0.3_1 Error starting CAESES
@ 2020-04-02  9:29 sebu06
  2020-04-02  9:54 ` xtraeme
                   ` (5 more replies)
  0 siblings, 6 replies; 7+ messages in thread
From: sebu06 @ 2020-04-02  9:29 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 2263 bytes --]

New issue by sebu06 on void-packages repository

https://github.com/void-linux/void-packages/issues/20565

Description:
### System

* xuname:  
  Void 5.5.13_1 x86_64 GenuineIntel uptodate rrrrmdFFFF
* package:  
  mesa-20.0.3_1

### Expected behavior
Up to Mesa 19.3.4_1 I was able to run CAESES (proprietary CAD system) without any problems. With the current Mesa-libs, CAESES fails to start.

### Actual behavior
The following error message appears:
`libGL error: MESA-LOADER: failed to open iris (search paths /usr/lib/xorg/modules/drivers)
libGL error: failed to load driver: iris
libGL error: MESA-LOADER: failed to open iris (search paths /usr/lib/xorg/modules/drivers)
libGL error: failed to load driver: iris
libGL error: MESA-LOADER: failed to open swrast (search paths /usr/lib/xorg/modules/drivers)
libGL error: failed to load driver: swrast
QGLTempContext: Unable to create GL context.
init glwindow: context not valid!
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
CAESES: xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
`
By looking at the strace info, Mesa 19.3.4_1 loads:
`[pid 28187] openat(AT_FDCWD, "/usr/lib/xorg/modules/drivers/tls/i965_dri.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
[pid 28187] openat(AT_FDCWD, "/usr/lib/xorg/modules/drivers/i965_dri.so", O_RDONLY|O_CLOEXEC) = 19`
whereas Mesa 20.0.3_1 loads:
`[pid 26302] openat(AT_FDCWD, "/usr/lib/xorg/modules/drivers/tls/swrast_dri.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
[pid 26302] openat(AT_FDCWD, "/usr/lib/xorg/modules/drivers/swrast_dri.so", O_RDONLY|O_CLOEXEC) = 19

[pid 26302] openat(AT_FDCWD, "/usr/lib/xorg/modules/drivers/tls/iris_dri.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
[pid 26302] openat(AT_FDCWD, "/usr/lib/xorg/modules/drivers/iris_dri.so", O_RDONLY|O_CLOEXEC) = 20`

If necessary, I can provide full strace output for both mesa versions, but maybe this is enough to point into the right direction. I tried modesetting and xf86-video-intel - no difference.

Thanks for the help, 
Sebastian


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: mesa-20.0.3_1 Error starting CAESES
  2020-04-02  9:29 [ISSUE] mesa-20.0.3_1 Error starting CAESES sebu06
@ 2020-04-02  9:54 ` xtraeme
  2020-04-02 10:02 ` sebu06
                   ` (4 subsequent siblings)
  5 siblings, 0 replies; 7+ messages in thread
From: xtraeme @ 2020-04-02  9:54 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 158 bytes --]

New comment by xtraeme on void-packages repository

https://github.com/void-linux/void-packages/issues/20565#issuecomment-607743300

Comment:
what GPU is it?

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: mesa-20.0.3_1 Error starting CAESES
  2020-04-02  9:29 [ISSUE] mesa-20.0.3_1 Error starting CAESES sebu06
  2020-04-02  9:54 ` xtraeme
@ 2020-04-02 10:02 ` sebu06
  2020-04-02 10:07 ` sebu06
                   ` (3 subsequent siblings)
  5 siblings, 0 replies; 7+ messages in thread
From: sebu06 @ 2020-04-02 10:02 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 337 bytes --]

New comment by sebu06 on void-packages repository

https://github.com/void-linux/void-packages/issues/20565#issuecomment-607747582

Comment:
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 08)
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07)


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: mesa-20.0.3_1 Error starting CAESES
  2020-04-02  9:29 [ISSUE] mesa-20.0.3_1 Error starting CAESES sebu06
  2020-04-02  9:54 ` xtraeme
  2020-04-02 10:02 ` sebu06
@ 2020-04-02 10:07 ` sebu06
  2020-04-02 15:13 ` st3r4g
                   ` (2 subsequent siblings)
  5 siblings, 0 replies; 7+ messages in thread
From: sebu06 @ 2020-04-02 10:07 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 187 bytes --]

New comment by sebu06 on void-packages repository

https://github.com/void-linux/void-packages/issues/20565#issuecomment-607750530

Comment:
btw: glxgears runs fine using the iris driver

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: mesa-20.0.3_1 Error starting CAESES
  2020-04-02  9:29 [ISSUE] mesa-20.0.3_1 Error starting CAESES sebu06
                   ` (2 preceding siblings ...)
  2020-04-02 10:07 ` sebu06
@ 2020-04-02 15:13 ` st3r4g
  2020-04-02 16:13 ` sebu06
  2020-04-02 16:13 ` [ISSUE] [CLOSED] " sebu06
  5 siblings, 0 replies; 7+ messages in thread
From: st3r4g @ 2020-04-02 15:13 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 512 bytes --]

New comment by st3r4g on void-packages repository

https://github.com/void-linux/void-packages/issues/20565#issuecomment-607907284

Comment:
`MESA_LOADER_DRIVER_OVERRIDE=i965 ./CAESES` should tell the loader to load the old driver.
If this has no effect, another way is to create the following configuration file in `~/.drirc` (per user) or `/etc/drirc` (system-wide):
```
<driconf>
  <device driver="loader" kernel_driver="i915">
    <option name="dri_driver" value="i965" />
  </device>
</driconf>
```

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: mesa-20.0.3_1 Error starting CAESES
  2020-04-02  9:29 [ISSUE] mesa-20.0.3_1 Error starting CAESES sebu06
                   ` (3 preceding siblings ...)
  2020-04-02 15:13 ` st3r4g
@ 2020-04-02 16:13 ` sebu06
  2020-04-02 16:13 ` [ISSUE] [CLOSED] " sebu06
  5 siblings, 0 replies; 7+ messages in thread
From: sebu06 @ 2020-04-02 16:13 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 163 bytes --]

New comment by sebu06 on void-packages repository

https://github.com/void-linux/void-packages/issues/20565#issuecomment-607943402

Comment:
Thanks - that helped.

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [ISSUE] [CLOSED] mesa-20.0.3_1 Error starting CAESES
  2020-04-02  9:29 [ISSUE] mesa-20.0.3_1 Error starting CAESES sebu06
                   ` (4 preceding siblings ...)
  2020-04-02 16:13 ` sebu06
@ 2020-04-02 16:13 ` sebu06
  5 siblings, 0 replies; 7+ messages in thread
From: sebu06 @ 2020-04-02 16:13 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 2303 bytes --]

Closed issue by sebu06 on void-packages repository

https://github.com/void-linux/void-packages/issues/20565

Description:
### System

* xuname:  
  Void 5.5.13_1 x86_64 GenuineIntel uptodate rrrrmdFFFF
* package:  
  mesa-20.0.3_1

### Expected behavior
Up to Mesa 19.3.4_1 I was able to run CAESES (proprietary CAD system) without any problems. With the current Mesa-libs, CAESES fails to start.

### Actual behavior
The following error message appears:
`libGL error: MESA-LOADER: failed to open iris (search paths /usr/lib/xorg/modules/drivers)`
`libGL error: failed to load driver: iris`
`libGL error: MESA-LOADER: failed to open iris (search paths /usr/lib/xorg/modules/drivers)`
`libGL error: failed to load driver: iris`
`libGL error: MESA-LOADER: failed to open swrast (search paths /usr/lib/xorg/modules/drivers)`
`libGL error: failed to load driver: swrast`
`QGLTempContext: Unable to create GL context.`
`init glwindow: context not valid!`
`[xcb] Unknown sequence number while processing queue`
`[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called`
`[xcb] Aborting, sorry about that.`
`CAESES: xcb_io.c:260: poll_for_event: Assertion !xcb_xlib_threads_sequence_lost' failed.`

By looking at the strace info, Mesa 19.3.4_1 loads:

`[pid 28187] openat(AT_FDCWD, "/usr/lib/xorg/modules/drivers/tls/i965_dri.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)`
`[pid 28187] openat(AT_FDCWD, "/usr/lib/xorg/modules/drivers/i965_dri.so", O_RDONLY|O_CLOEXEC) = 19`

whereas Mesa 20.0.3_1 loads:

`[pid 26302] openat(AT_FDCWD, "/usr/lib/xorg/modules/drivers/tls/swrast_dri.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)`
`[pid 26302] openat(AT_FDCWD, "/usr/lib/xorg/modules/drivers/swrast_dri.so", O_RDONLY|O_CLOEXEC) = 19`

`[pid 26302] openat(AT_FDCWD, "/usr/lib/xorg/modules/drivers/tls/iris_dri.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)`
`[pid 26302] openat(AT_FDCWD, "/usr/lib/xorg/modules/drivers/iris_dri.so", O_RDONLY|O_CLOEXEC) = 20`


If necessary, I can provide full strace output for both mesa versions, but maybe this is enough to point into the right direction. I tried modesetting and xf86-video-intel - no difference.

Thanks for the help, 
Sebastian


^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2020-04-02 16:13 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-04-02  9:29 [ISSUE] mesa-20.0.3_1 Error starting CAESES sebu06
2020-04-02  9:54 ` xtraeme
2020-04-02 10:02 ` sebu06
2020-04-02 10:07 ` sebu06
2020-04-02 15:13 ` st3r4g
2020-04-02 16:13 ` sebu06
2020-04-02 16:13 ` [ISSUE] [CLOSED] " sebu06

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).