[SOLVED] i965 error on HD4000 Ivy Bridge Slackware-15.0
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
bash-5.1$ ./Slic3r-1.3.0-x86_64.AppImage
libGL error: MESA-LOADER: failed to open i965: /usr/lib64/dri/i965_dri.so: undefined symbol: _ZNKSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE4findEcm, version GLIBCXX_3.4.21 (search paths /usr/lib64/dri, suffix _dri)
libGL error: failed to load driver: i965
libGL error: MESA-LOADER: failed to open i965: /usr/lib64/dri/i965_dri.so: undefined symbol: _ZNKSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE4findEcm, version GLIBCXX_3.4.21 (search paths /usr/lib64/dri, suffix _dri)
libGL error: failed to load driver: i965
libGL error: MESA-LOADER: failed to open swrast: /tmp/.mount_Slic3rgswkB1/usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /usr/lib64/dri/swrast_dri.so) (search paths /usr/lib64/dri, suffix _dri)
libGL error: failed to load driver: swrast
The program 'slic3r.pl' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
(Details: serial 977 error_code 2 request_code 151 minor_code 24)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
I'm on glibc-2.33 if that matters.
Now IIRC, this sucky HD4000 will work with i915 in 2D, and does a feeble 3D with i965.
Am I correct in suspecting that some conflict is afoot between appimage and system?
If AppImage did not work, did you try to build from source? Did you try to run AppImage on current. you could use AlienBob live usb to test? Can you use an older version AppImage compiled against 2.33 glibc?
It would appear they are all the same file - nouveau, radeon, & intel
Pesonally, my first reaction was to file a bug. But they are graphics libs presumably manipulating Mesa, so even the terminology might be the same. I'm particularly surprised at the i830 being the same as the newer ones. The i830 & r200 are really just glorified D/A converters, not graphics cards. The i915 isn't much better. The later ones can surely do a lot of stuff the earlier ones could not.
Of course making them separate files means they could be patched separately, I suppose.
If AppImage did not work, did you try to build from source? Did you try to run AppImage on current. you could use AlienBob live usb to test? Can you use an older version AppImage compiled against 2.33 glibc?
Build (Cura) from source I'm doing in stints. No, I haven't tried current or live usb because the issue is with the (Cura) AppImage, not my system. I did try the earlier version I had (4.8.0) which had the same issue. It's like they catered for networked printers, not sdcard.
I have got Prusa Slicer with a printer from the same stable configured, so I'll have a go at bending that config to suit my Printer. That seems easier than playing 'whack-a-mole' with Cura's dependencies. It's currently puking for lack of Python3-3.10, while I have 3.9.10. But of course, I'll get python 3.10.0, not 3.10 exactly, which seems to be what it wants.
Yeah, that got Slic3r up and running. Unfortunately, it just seems a poor piece of software, like a dancer with two left feet. Prusa Slicer is writing gcode for me.
I've a way around the video issue, so I'm going to call this solved. The HD4000 is, and always will be a piece of <expletive>, but it's good enough to work with Prusa Slicer.
Oh,BTW, I was right and wrong about Python I'm trtying to build Cura in passing at this stage, but it was looking for Python-3.10 whereas Python comes as 3.x.x
Weii, I installed 3.10.4. But that made a 3.10/ directory for itself.
Look nearly 100% of the posts have been OT, but this was an interesting thread and I learned stuff.
I'm sticking with the hypothesis of dri libs talking to Mesa, so they get away with the same libs until someone informs me better. If they do it might still be OT, but we'll all learn more.
As for post #1: I have worked around the issue, guys have sorted me with a slicer that works, (I think). By the time I discover otherwise, I'll hopefully retiring this old box anyhow.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
