Linux - KernelThis forum is for all discussion relating to the Linux kernel.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I just built 4.19 this morning. Now my non-X display doesn't update properly. Artifacts from previous screens are left behind. It may only happen in apps that use ncurses.
I just built 4.19 this morning. Now my non-X display doesn't update properly. Artifacts from previous screens are left behind. It may only happen in apps that use ncurses.
Does anyone else see this?
I upgraded my slackware64-current partitions on both my big boxes last night, and on the vanilla partitions I have set up for clean builds, I get nearly complete lockups in X. As long as I stayed in the console (no X), I was fine. Had to revert back to 4.14.78 on those partitions to fix it. I think something got broken in nouveau between X and the kernel. With the proprietary Nvidia driver I have no such problems. Both my boxes are AMD FX 8-core with 32G RAM and Geforce GTX-1050ti cards.
Distribution: Artix, Slackware, Devuan etc. No systemd!
Posts: 368
Rep:
I can now run a graphical desktop with kernel 4.19.x, although I do have to reduce the screen resolution.
The laptop's native screen resolution is 1920x1080 (16:9). I'm using the nearest 16:9 resolution which is 1600x1024 on my machine.
It's usable for now, but I had to set up auto logins with each distro installed. This is due to a virtually unusable screen at 1920x1080.
Distribution: Artix, Slackware, Devuan etc. No systemd!
Posts: 368
Rep:
I've just added kernel 4.19.1 and Cinnamon to a clean install of Devuan Ascii.
This involved making direct copies of everything relevant from my Mint 19 installation (kernel, firmware, headers & modules).
Yes, O.K. This method is not exactly the recommended one, but I just wanted to do a quick test.
The default screen resolution of 1920x1080 works perfectly fine... So it looks like my particular problem might be down to other things beyond the kernel.
The problem stopped with kernel 4.19.2. The only difference in the .config was the disappearance of CONFIG_CRYPTO_SPECK=m , which should be irrelevant, and appeared in 4.17.1 anyway.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.