Slackware -current/15-beta: bootup tip on hardware using Intel 915 based chipsets on kernel 5.10.x, don't use vga= parameter
by ddmayne from LinuxQuestions.org on (#5HE1J)
The title has the punch. I also saw this Arch based advice, which helped me solve the longstanding issue.
I started using Slackware -current sometime in the last year and half because of better support on some of the hardware I use. I was getting a lot of display glitches that were not addressed on the 4.4.x kernel. When I first switched to --current, it was using the 4.19.x kernel series. When -current switched to 5.x.x, I experienced some of the long running display issues that I had seen on Slackware 14.2 once again. So, I stuck with the 4.19.x kernel (self-compiled) for quite a while- up to 4.19.179. Luckily, the display issues were finally addressed in the 5.10.x series at about 5.10.15. I wrote about these issues at reddit.
I also saw the glitch occur again on some hardware in the last month when updating the kernel beyond 5.10.30. Dropping the kernel boot parameter "vga=ask" fixed that issue for me.
As you all probably know slackware 14.2 is aging rapidly with many waiting expectantly for 15. HTH as a general tip, but it might not be all that useful depending on what bootloader is used. Also, the bug resolves itself when switching to runlevel 4, but I use runlevel 3 on a lot of equipment I use regularly.
I started using Slackware -current sometime in the last year and half because of better support on some of the hardware I use. I was getting a lot of display glitches that were not addressed on the 4.4.x kernel. When I first switched to --current, it was using the 4.19.x kernel series. When -current switched to 5.x.x, I experienced some of the long running display issues that I had seen on Slackware 14.2 once again. So, I stuck with the 4.19.x kernel (self-compiled) for quite a while- up to 4.19.179. Luckily, the display issues were finally addressed in the 5.10.x series at about 5.10.15. I wrote about these issues at reddit.
I also saw the glitch occur again on some hardware in the last month when updating the kernel beyond 5.10.30. Dropping the kernel boot parameter "vga=ask" fixed that issue for me.
As you all probably know slackware 14.2 is aging rapidly with many waiting expectantly for 15. HTH as a general tip, but it might not be all that useful depending on what bootloader is used. Also, the bug resolves itself when switching to runlevel 4, but I use runlevel 3 on a lot of equipment I use regularly.