WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Mesa 12.x?  (Read 3388 times)

Offline pq5190362

  • Full Member
  • ***
  • Posts: 205
Mesa 12.x?
« on: July 28, 2016, 10:44:02 AM »
Hi,

any chance you could update the Xorg-7.7-3d.tcz extension in the x86 and x86_64 repos with Mesa 12.x:

http://www.mesa3d.org/

?

Regards

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 9369
Re: Mesa 12.x?
« Reply #1 on: July 28, 2016, 11:55:29 PM »
Hmm - that's not a small task - it might have to wait for tc-8.x...

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 9369
Re: Mesa 12.x?
« Reply #2 on: August 01, 2016, 02:47:37 AM »
Updated in the X86_64 repo - x86 to follow.

Take care to update all X related extensions at the same time

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 9369
Re: Mesa 12.x?
« Reply #3 on: August 02, 2016, 08:15:05 AM »
updated in the x86 repo

Offline Misalf

  • Hero Member
  • *****
  • Posts: 1540
Re: Mesa 12.x?
« Reply #4 on: August 02, 2016, 06:49:59 PM »
Will the  xf86-video*  extensions need a rebuild as well or do I need to reconfigure something?

Before the update, none of the 3D applications I tried ran properly. Graphical artifacts or displaying just black.
Now 3D works but it's extremely slow compared to TC-6.x.

I'm using:
Xorg-7.7-3d.tcz
xf86-video-intel.tcz

TC-7.x x86
Netbook MSI Wind U100

sudo lspci -v -s $(lspci | grep VGA | awk '{print $1}')
Code: [Select]
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] Device 0110
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at dfe80000 (32-bit, non-prefetchable) [size=512K]
I/O ports at d100 [size=8]
Memory at c0000000 (32-bit, prefetchable) [size=256M]
Memory at dff00000 (32-bit, non-prefetchable) [size=256K]
Expansion ROM at <unassigned> [disabled]
Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Kernel driver in use: i915

lspci -n -s $(lspci | grep VGA | awk '{print $1}')
Code: [Select]
00:02.0 0300: 8086:27ae (rev 03)

OLD: glxinfo | grep 'renderer string'
Code: [Select]
OpenGL renderer string: Mesa DRI Intel(R) 945GME x86/MMX/SSE2

NEW: glxinfo | grep 'renderer string'
Code: [Select]
OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.7, 128 bits)

in  /var/log/Xorg.0.log  this is new (checked with meld)
Code: [Select]
(II) AIGLX: enabled GLX_EXT_fbconfig_packed_float

« Last Edit: August 02, 2016, 06:56:23 PM by Misalf »
Download a copy and keep it handy: Core book ;)

Offline Misalf

  • Hero Member
  • *****
  • Posts: 1540
Re: Mesa 12.x?
« Reply #5 on: August 02, 2016, 08:30:38 PM »
Code: [Select]
$ glxgears
libGL error: unable to load driver: i915_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: i915
549 frames in 5.0 seconds = 109.771 FPS
708 frames in 5.0 seconds = 141.489 FPS
712 frames in 5.0 seconds = 142.231 FPS
716 frames in 5.0 seconds = 143.157 FPS
671 frames in 5.0 seconds = 134.106 FPS
...
Download a copy and keep it handy: Core book ;)

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 9369
Re: Mesa 12.x?
« Reply #6 on: August 02, 2016, 10:23:13 PM »
Code: [Select]
OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.7, 128 bits)

This means that software acceleration is being used.

You mentioned that you got a black screen previously, which would seem to indicate that hardware acceleration doesn't work with either the old or the new version for you?

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 9369
Re: Mesa 12.x?
« Reply #7 on: August 02, 2016, 10:33:25 PM »
Do you get this when the kms driver loads:
Code: [Select]
WARNING: CPU: 1 PID: 3338 at drivers/gpu/drm/i915/intel_display.c:12326 0xffffffffa01a9b49()
pipe state doesn't match!
Modules linked in: drbg ctr ccm iwlmvm mac80211 iwlwifi cfg80211 cpufreq_userspace cpufreq_conservative cpufreq_stats cpufreq_powersave i915 drm_kms_helper i2c_designware_platform i2c_designware_core drm intel_gtt agpgart i2c_algo_bit i2c_i801 squashfs lz4_decompress loop dell_wmi sparse_keymap ppdev parport_pc parport sdhci_acpi 8250_fintek sdhci_pci sdhci video backlight mmc_core e1000e ptp pcspkr pps_core 8250_dw wmi intel_smartconnect dell_rbtn battery intel_rst mei_me mei ac lpc_ich xhci_pci xhci_hcd
CPU: 1 PID: 3338 Comm: Xorg.wrap Tainted: G        W       4.2.9-tinycore64 #1999
Hardware name: Dell Inc. Latitude E7240/05PTPV, BIOS A18 04/28/2016
 0000000000000000 0000000000000009 ffffffff81514b36 ffff88040690b8f8
 ffffffff81069070 ffff88040690b8f0 ffffffffa01a9b49 ffffffffa0207904
 ffff8804071aa000 ffff88040540d000 0000000000000001 ffff88040690b988
Call Trace:
 [<ffffffff81514b36>] ? 0xffffffff81514b36
 [<ffffffff81069070>] ? 0xffffffff81069070
 [<ffffffffa01a9b49>] ? 0xffffffffa01a9b49
 [<ffffffff810690cd>] ? 0xffffffff810690cd
 [<ffffffffa01a9b49>] ? 0xffffffffa01a9b49
 [<ffffffff810107f0>] ? 0xffffffff810107f0
 [<ffffffff810a8916>] ? 0xffffffff810a8916
 [<ffffffff810107f0>] ? 0xffffffff810107f0
 [<ffffffffa01b8b94>] ? 0xffffffffa01b8b94
 [<ffffffff81108513>] ? 0xffffffff81108513
 [<ffffffffa01b99ae>] ? 0xffffffffa01b99ae
 [<ffffffffa01568fa>] ? 0xffffffffa01568fa
 [<ffffffffa01286d7>] ? 0xffffffffa01286d7
 [<ffffffffa0157eb1>] ? 0xffffffffa0157eb1
 [<ffffffffa01595c6>] ? 0xffffffffa01595c6
 [<ffffffffa01c6099>] ? 0xffffffffa01c6099
 [<ffffffffa01e677e>] ? 0xffffffffa01e677e
 [<ffffffffa01e6778>] ? 0xffffffffa01e6778
 [<ffffffffa011ef31>] ? 0xffffffffa011ef31
 [<ffffffffa011f414>] ? 0xffffffffa011f414
 [<ffffffff81112680>] ? 0xffffffff81112680
 [<ffffffff8107c6b2>] ? 0xffffffff8107c6b2
 [<ffffffff8100a4b9>] ? 0xffffffff8100a4b9
 [<ffffffff815198fc>] ? 0xffffffff815198fc
---[ end trace 8de49e2169362044 ]---
[drm:0xffffffffa01a9b28] *ERROR* mismatch in ips_enabled (expected 1, found 0)

..but even with that I get this:
Code: [Select]
$ glxinfo | grep 'renderer string'
OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 9516
Re: Mesa 12.x?
« Reply #8 on: August 03, 2016, 12:17:46 AM »
Try to find the cause for that "driver pointer missing", maybe "strace glxgears" or Xorg.0.log shows something.

edit: Also try LIBGL_DEBUG=verbose glxgears
The only barriers that can stop you are the ones you create yourself.

Offline Misalf

  • Hero Member
  • *****
  • Posts: 1540
Re: Mesa 12.x?
« Reply #9 on: August 03, 2016, 01:58:01 AM »
Quote
You mentioned that you got a black screen previously, which would seem to indicate that hardware acceleration doesn't work with either the old or the new version for you?
Yes. Neither the old nor the new version works.

Quote
Do you get this when the kms driver loads:
Haven't seen that so far. Where would it be displayed? While booting using  loglevel=  bootcode?

LIBGL_DEBUG=verbose glxgears
Code: [Select]
libGL: OpenDriver: trying /usr/local/lib/dri/tls/i915_dri.so
libGL: OpenDriver: trying /usr/local/lib/dri/i915_dri.so
libGL: dlopen /usr/local/lib/dri/i915_dri.so failed (/usr/local/lib/dri/i915_dri.so: undefined symbol: __sync_val_compare_and_swap_8)
libGL error: unable to load driver: i915_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: i915
libGL: OpenDriver: trying /usr/local/lib/dri/tls/swrast_dri.so
libGL: OpenDriver: trying /usr/local/lib/dri/swrast_dri.so
libGL: Can't open configuration file /home/tc/.drirc: No such file or directory.
libGL: Can't open configuration file /home/tc/.drirc: No such file or directory.
574 frames in 5.0 seconds = 114.632 FPS

strace glxgears >/tmp/strace-glxgears 2>&1  output attached.

Xorg.0.log contains no (EE)'s, not even (WW)'s except for missing font directories.
Download a copy and keep it handy: Core book ;)

Offline Misalf

  • Hero Member
  • *****
  • Posts: 1540
Re: Mesa 12.x?
« Reply #10 on: August 03, 2016, 02:15:56 AM »
Attached  /var/log/messages .
Download a copy and keep it handy: Core book ;)

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 9516
Re: Mesa 12.x?
« Reply #11 on: August 03, 2016, 09:56:08 AM »
libGL: dlopen /usr/local/lib/dri/i915_dri.so failed (/usr/local/lib/dri/i915_dri.so: undefined symbol: __sync_val_compare_and_swap_8)

This line is the culprit. The i915 driver requires -march=i586 minimum.
The only barriers that can stop you are the ones you create yourself.

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 9369
Re: Mesa 12.x?
« Reply #12 on: August 03, 2016, 10:03:45 AM »
OK - I'll look tomorrow - do we want to use i686 for this as a minimum?

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 9516
Re: Mesa 12.x?
« Reply #13 on: August 03, 2016, 10:07:57 AM »
I'm not sure if there's 3d users on old cpus really, and the performance improves a lot with newer targets. Something like -march=pentium-m just for mesa might be ok. Maybe ask here if there's users on older ones and wait a week?
The only barriers that can stop you are the ones you create yourself.

Offline pq5190362

  • Full Member
  • ***
  • Posts: 205
Re: Mesa 12.x?
« Reply #14 on: August 03, 2016, 12:53:18 PM »
Will the  xf86-video*  extensions need a rebuild as well or do I need to reconfigure something?

Really couldn't hurt to update the DDX drivers.

Especially xf86-video-intel. xf86-video-intel is in constant development, but the Tiny Core Linux repos only have an old snapshot from 2015.

So, it couldn't hurt to update the Tiny Core Linux repos with a fresh snapshot of xf86-video-intel, directly from git.

By the way:

In recent events, Debian and Ubuntu more or less have deprecated xf86-video-intel in favour of xf86-video-modesetting, for more details see:

https://tjaalton.wordpress.com/2016/07/23/intel-graphics-gen4-and-newer-now-defaults-to-modesetting-driver-on-x/

https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/intel-linux/886898-ubuntu-debian-abandon-intel-x-org-driver-for-most-hardware-moves-to-modesetting-ddx

https://www.reddit.com/r/archlinux/comments/4cojj9/it_is_probably_time_to_ditch_xf86videointel/

xf86-video-modesetting no longer is a separate package. xf86-video-modesetting is built into xorg-server since xorg-server 1.17.0.

To get the latest version of xf86-video-modesetting, it would be necessary to update xorg-server to the latest version, which is 1.18.4 at the time of writing this:

https://cgit.freedesktop.org/xorg/xserver/

 ;)