Is your framebuffer device showing in /dev? It should be called
/dev/fb0,1,2. If yes could you post the output of
$ dmesg | grep fb0
On Sun, Apr 23, 2023, 22:31 wrote:
> No, I did not change anything, during kernel upgrade only run: make
> oldconfig
>
> but nvidia-drivers-525.105.17
No, I did not change anything, during kernel upgrade only run: make oldconfig
but nvidia-drivers-525.105.17 compiled with a note:
WARN: setup
Detected potential configuration issues with used kernel:
CONFIG_FB_SIMPLE: is set, recommended to disable and switch to FB_EFI or
FB_VESA as it
A new build of chromium came down today, no change in behavior. (High
frequency error 11's with blank config, can't even display about:blank )
It must be some kind of dependency conflict but I don't seem to have any
way to diagnose it deeper.
I will be writing these posts daily until the
Did you change something in your kernel config? I had the same problem
once, because I forgot to enable these kernel options:
(From the AMD64 Handbook)
Device Drivers
Firmware Drivers --->
EFI (Extensible Firmware Interface) Support --->
<*> EFI Variable Support via sysfs
4 matches
Mail list logo