Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mesa: switch from i915 to i915g (gallium) #34620

Closed
wants to merge 1 commit into from

Conversation

tsndqst
Copy link
Contributor

@tsndqst tsndqst commented Dec 19, 2021

I made this change to get sway working on my EeePC 1005HA. I set WLR_NO_HARDWARE_CURSORS=1 before starting sway to get the mouse cursor to work. More information here.

Testing the changes

  • I tested the changes in this PR: briefly

Local build testing

  • I built this PR locally for my native architecture, (i686-glibc, native mode with a 32bit masterdir on x86-64)

@notramo
Copy link

notramo commented Dec 19, 2021

It should be different package, because gallium version is more buggy than classic.
Classic is more reliable for Xorg and some less popular Wayland compositors, and gallium is only needed for wlroots which requires features that are missing from classic.

@tsndqst
Copy link
Contributor Author

tsndqst commented Dec 19, 2021

That makes sense. My quick and dirty change for my system won't be enough.

@ericonr
Copy link
Member

ericonr commented Dec 20, 2021

Dang, what a mess :/

https://gitlab.freedesktop.org/mesa/mesa/-/issues/5418 says it will become default at some point, but we are clearly not there yet

I'd consider potentially a build option for the Void package until then, what do you think?

@q66
Copy link
Contributor

q66 commented Dec 20, 2021

my 2c: mesa 22 (coming in February) retires all the classic dri drivers anyway, so there is nothing much to deal with - we could just flip the switch, turn dri drivers off entirely, and be done with it

@ericonr
Copy link
Member

ericonr commented Dec 20, 2021

My hope is that until February the Gallium driver will be (more) fixed, so doing the switch now would hurt a lot of users unnecessarily.

@q66
Copy link
Contributor

q66 commented Dec 20, 2021

any examples of how i915g is buggy in current releases?

(also, there's probably relatively few i915 users left at this point, since it's ancient hardware)

@Anachron
Copy link
Contributor

Maybe we could revisit this? I'm a i915 user and with the recent mesa and linux combination I can't boot into X anymore.

@tsndqst
Copy link
Contributor Author

tsndqst commented Jun 14, 2022

I won't be much help beyond providing another data point. I am able to run X on my EeePC 1005HA with the latest Mesa 22 package.

@Anachron it might help to provide more information about your setup. Kernel version, /var/log/Xorg.0.log messages (especially if there are lines with (EE)) , etc.

Other folks may be able to provide more specific information about troubleshooting Mesa/X issues.

@tsndqst
Copy link
Contributor Author

tsndqst commented Jun 14, 2022

@Anachron are you using any Mesa environment variables to override behavior such as MESA_LOADER_DRIVER_OVERRIDE? https://docs.mesa3d.org/envvars.html#core-mesa-environment-variables

Perhaps the wrong driver is being selected. The i915 driver is gallium-only so there is no i915g driver anymore. i915 IS the gallium driver. In the past there was i915 and i915g.

@Anachron
Copy link
Contributor

Turns out I had kernel boot parameters added before which are not supported with my i915 hardware anymore. Sorry for the noise.

@tsndqst
Copy link
Contributor Author

tsndqst commented Jun 15, 2022

I'm glad you figured it out.

Mesa has been updated to 22 now so I'm going to close this PR.

@tsndqst tsndqst closed this Jun 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants