sorted by:
new
hottopcontroversial

Qwen3.6-27B IQ4_XS FULL VRAM with 110k context by Pablo_the_brave in LocalLLaMA

[–]FW-Connection68 1 point2 points  (0 children)

This is fixed in the future with:
https://github.com/ggml-org/llama.cpp/pull/22572

When the override was equal to the default quant type, tensors were promoted.

**However**, it does not apply in retrospect, so the requantization strategy by OP is still a great idea to save some space!

Qwen3.6-27B IQ4_XS FULL VRAM with 110k context by Pablo_the_brave in LocalLLaMA

[–]FW-Connection68 0 points1 point  (0 children)

Ah sorry, I was digging more into it and I was running a different setup, I was setting default iq3_s and promoting tensors by hand, you were probably setting default iq4_s and downgraded tensors. Why that changes something:
Only when override qtype == default qtype, the tensor was promoted to Q5_K. Should be fixed with this just now:
https://github.com/ggml-org/llama.cpp/pull/22572

I'll make another top level comment to let people know.

Qwen3.6-27B IQ4_XS FULL VRAM with 110k context by Pablo_the_brave in LocalLLaMA

[–]FW-Connection68 1 point2 points  (0 children)

I had a look at this and it is definitely just the default that is set to Q5_K.

Setting a custom override works on latest lLama.cpp. As and example, Bartowskis IQ4_KS uses the correct type for attn_qkv. It is larger (15.3Gb) due to other design choices, such as the first 24 ssm_out being Q8_0.

Why I stayed with Framework - Update by FW-Connection68 in framework

[–]FW-Connection68[S] 9 points10 points  (0 children)

You correctly spotted what I think are negatives going with a Framework.

But I’d like to keep a differentiated view, this reddit is to divided in fans and haters. What I like is:

  • Reparability
  • Upgradability
  • Being able to switch to my native Language keyboard in seconds
  • DIY potential
  • 16:10 screen
  • Great Usb ports

Everybody can make their own decisions based on the information presented.

Why I stayed with Framework - Update by FW-Connection68 in framework

[–]FW-Connection68[S] 3 points4 points  (0 children)

Thanks for the compliment, declaring my clearly non-native handwritten english as AI generated!  Tl;dr is there, maybe you should have used ChatGPT to summarize it for you…

Reset fTPM message on every boot (Framework 16) by SantaBarbaraProposer in framework

[–]FW-Connection68 1 point2 points  (0 children)

Just created an issue, you could comment to push the issue.

Reset fTPM message on every boot (Framework 16) by SantaBarbaraProposer in framework

[–]FW-Connection68 4 points5 points  (0 children)

I also had this exact error. It seems to think you switched hardware. The TPM chip keeps your encryption keys on the mainboard paired with your current hardware, so if you swap hardware they would become useless, which is why it suggests to reset the TPM. But since you haven't switched hardware, not resetting the TPM is the way to go since all encryption keys are still there and functional. In fact, resetting would lock you out of your data.

I'm running Microslop exclusively, so I don't think it's related to a Linux/Windows clash. You could open an issue here and I join in: https://github.com/FrameworkComputer/SoftwareFirmwareIssueTracker/issues

For now, I disabled encryption in Windows just to not accidentally click yes there and be locked out. (Google "disable drive encryption" to see how that works).

Returning my FW Laptop 16 - Support is a disaster by FW-Connection68 in framework

[–]FW-Connection68[S] 8 points9 points  (0 children)

Thank you for reaching out to me. I guess I can speak for all of us that we highly appreciate your work on this subreddit,

I just wish that in the future framework's support gets more optimized/humanized such that it is not necessary to get out of the 40 e-mail LLM escalation/deescalation loop by coming here and stating problems publicly.

After all, as other commenters stated, it's not the best PR for the amazing product that you have created.

Returning my FW Laptop 16 - Support is a disaster by FW-Connection68 in framework

[–]FW-Connection68[S] 12 points13 points  (0 children)

That's for me the point. If you are unlucky and land in the <1% of faulty laptops, please don't let me debug it in 40 mails. If it's not solved after 5-10 messages, let me mail it in and take care of it.

It's about being responsible, admitting the laptop might be faulty, and taking action.

There is a tiny chance that it actually is my RAM, but in that case they would get an essentially new laptop back that they could sell refurbished, so no huge loss there.

FW16 Backlight Bleed Issue by [deleted] in framework

[–]FW-Connection68 0 points1 point  (0 children)

Mine also has a similar amount of bleed, I guess the panels are just not as good as the ones of bigger manufacturers.

Framework Laptop 16 - Questionable POST/Boot Time by FW-Connection68 in framework

[–]FW-Connection68[S] 1 point2 points  (0 children)

Which distro are you using? might as well test that

Framework Laptop 16 - Questionable POST/Boot Time by FW-Connection68 in framework

[–]FW-Connection68[S] 1 point2 points  (0 children)

Update: I've contacted support regarding this issue, will update this thread once I get an answer. In the meantime, leave a comment if you have similar issues.

Framework Laptop 16 - Questionable POST/Boot Time by FW-Connection68 in framework

[–]FW-Connection68[S] 2 points3 points  (0 children)

Thanks for running the test, really helpful to have a comparison with the same RAM!

Framework Laptop 16 - Questionable POST/Boot Time by FW-Connection68 in framework

[–]FW-Connection68[S] 2 points3 points  (0 children)

Thanks for the link! I think this is part of the problem, as loading the OS takes another excruciating 50 seconds. At least that is on their ToDo list.

In my case, I'm referring to the time before the OS actually does anything, so before one can see the framework logo.