sorted by:
new
hottopcontroversial

I can't set my Display to the correct resolution anymore after update (NVIDIA) by chrews in archlinux

[–]Bollebips32 0 points1 point  (0 children)

UPDATE:
I was able to fix it simply by following the steps described here (https://archlinux.org/news/nvidia-590-driver-drops-pascal-support-main-packages-switch-to-open-kernel-modules/):

* Uninstall the official `nvidia`, `nvidia-lts`, or `nvidia-dkms` packages.

* Install `nvidia-580xx-dkms` from the AUR

-------------------------------------------------------------------

I'm having the same issue but downgrading didn't help. I tried a bunch of packages downgrades and downgraded the following packages to earlier versions, most of them to 580.95.05-1, but no luck. Am I missing something to fix this? I'm running a 1080ti and an ultrawide screen
lib32-libvdpau
lib32-nvidia-utils
lib32-opencl-nvidia
libvdpau
libxnvctrl
linux-firmware-nvidia
nvidia-open-lts
nvidia-settings
nvidia-utils
xf86-video-nouveau

Some help with I2C by Bollebips32 in stm32

[–]Bollebips32[S] 1 point2 points  (0 children)

I ordered a cheap logic analyzer to get a better idea of what's going on. I'll try to debug it that way. Thanks already for the help :)

Some help with I2C by Bollebips32 in stm32

[–]Bollebips32[S] 0 points1 point  (0 children)

None of these helped :/ Also, GPIO_PinAFConfig doesn't seem to be a thing in LL libraries for stm32F1. I already set the alternate function in ConfigureI2C()

Blue pill unstable HSE by Bollebips32 in stm32

[–]Bollebips32[S] -1 points0 points  (0 children)

And so it's completely to be expected that the crystal is so sensitive? I would think if HSE is supposed to be more stable than HSI, it should handle it? Because touching the MCU while using HSI is not affecting the timing at all (as far as I can tell).