Fix Gemma 4 quantized per-layer projection loading#935
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
While trying to run unsloth/gemma-4-E2B-it-UD-MLX-4bit, I hit a loading error:
After cross-checking this against the Gemma 4 implementation in Transformers (constructor, projection path), I replaced the custom
ScaledLinearwrapper used forper_layer_model_projectionwith a standard bias-freenn.Linearand moved thehidden_size**-0.5scale into the projection path explicitly.The math stays the same, but the layer now works with MLX's normal quantization and loading flow.
For reference, here's the same fix on mlx-lm: ml-explore/mlx-lm#1112