timkenhan

joined 1 year ago
[–] timkenhan@sopuli.xyz 2 points 1 week ago

Did the magic smoke come out?

If so, you can try replacing the chip. Some basic SMD (de)soldering is required.

If not, you can try reseating your clip. Hopefully the chip is still good. It may have more tolerance than specified.

[–] timkenhan@sopuli.xyz 8 points 1 week ago

While many comments here are correct that it would affect less than you'd expect, there are things that may not be covered.

For example:

  • there's no setting for hyperthreading
  • no way to disable SATA drives, in case you'd like to be selective
  • you'll need to reflash the BIOS if you want to change boot order permanently

Also, make sure you have the correct video BIOS.

[–] timkenhan@sopuli.xyz 1 points 1 week ago (1 children)

How would the lack of passive CPU powersaving affect things on your end?

[–] timkenhan@sopuli.xyz 18 points 3 months ago (22 children)

Serious question: you'd use that for your daily driver?

[–] timkenhan@sopuli.xyz 1 points 5 months ago (1 children)

How would Flatpak know which driver to install?

[–] timkenhan@sopuli.xyz 27 points 5 months ago

Still better than no update.

 

Hopefully this is the right place to ask. Lemme know otherwise.

I got a Thinkpad W530 with Quadro K2000M GPU (Kepler). With coreboot, I was able to get around all the headaches related to Optimus only having the discrete GPU enabled.

The GPU itself is well-supported by nouveau driver, missing only a few features on the power management side of things.

Things are good when I run stuff natively. However, I have yet to figure out Flatpak. I know we use org.freedesktop.Platform.GL.* packages that are some kind of Mesa abstraction layer.

Things are much more straightforward with Intel and AMD GPU. It is actually quite easy with the proprietary NVidia driver, but it doesn't exactly come free.

The ultimate question is: Should I install one of those org.freedesktop.Platform.GL.nvidia-<ver> packages with my nouveau? If so, which version?

[–] timkenhan@sopuli.xyz 6 points 7 months ago

Could be things to execute. They may run a shell script (source it if they don't have exec permission), but they won't have all the previleged commands (definitely no dd)

[–] timkenhan@sopuli.xyz 2 points 7 months ago

I currently have a Thinkpad W530 with a Quadro K2000M. Because I have coreboot as its firmware, I am able to run completely on the discrete GPU. So far I've been doing great.

I've looked on the feature matrix of the nouveau support and my GPU (Kepler) happens to have all the features checked-off, with the exception of dynamic power management (mostly WIP).

Right now, I'm running KDE wayland with the nouveau driver with no issue.

On the other hand, I've tried having the hybrid GPU and it sucks.

[–] timkenhan@sopuli.xyz 6 points 7 months ago (5 children)

How the mighty has fallen.

[–] timkenhan@sopuli.xyz 10 points 10 months ago

Don't get me started.

There are good reasons why I have personal "production system" to do my work with.

[–] timkenhan@sopuli.xyz 1 points 10 months ago

Yes, I did set the BIOS GPU config to "discrete only" and now it works.

 

Hi everyone, I've neen having this issue when running KDE wayland with multiple screen on my Thinkpad W530. I'm using the nouveau driver.

The primary monitor is fine, but the secondary one is glitching.

This is tested on Gentoo as well as Debian. I know it's not hardware issue because it runs fine on X11.

Anyone have any idea about this issue?

Edit: I should probably mention that I was using DisplayPort in the photo, but I also tried VGA and it gave the same result.

Edit1: I was able to narrow down the problem somewhat. Switching the BIOS setting to "Discrete only" for the GPU (thanks coreboot!) seems to make the glitching go away! This means the Optimus would be to blame.

view more: next ›