[SOLVED] Distribution Upgrade: Frame Buffer Glitch
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Some time ago when issues relating to using the framebuffer with KMS modules/drivers first began to occur, I did make some changes to liloconfig. It defaults to vga=normal, says that is "the safe choice", and warns that some drivers are not compatible with a framebuffer.
Pat,
I obviously missed seeing that vga=normal was the default. Framebuffers worked before this on this laptop so there was no need for me to disable them. Since there's no benefit to using them other than seeing the number of cores in the CPU (which I know without having to count penguins) there's no need to make further changes.
Again, thanks very much for pointing me to the solution,
I had the same error as you today, rshepard. After recompiling and installing a wifidriver (don't ask) on kernel 3.8.4 my pc went full retard.
I fixed it with a chroot into my installation, which is a pain in the ass with a lot of subvolumes on an encrypted btrfs system, and installed the 3.8.5 kernel.
The new kernel wasn't the fix, it was my i915 kernel module that was blown away by a wifidriver (yeah, I know... never just press enter on nightly builds).
I wansnt able to find the module anywhere, and before my experiment with the driver everything worked perfect.
After I got that module going again my problems were gone. Now everything is back to normal and I think its time for a rescue kernel with its own modules and initrd.gz.
I hope that helps and you get your fb console back.
I had the same error as you today, rshepard. After recompiling and installing a wifidriver (don't ask) on kernel 3.8.4 my pc went full retard.
I wasn't able to find the module anywhere, and before my experiment with the driver everything worked perfect.
After I got that module going again my problems were gone. Now everything is back to normal and I think its time for a rescue kernel with its own modules and initrd.gz.
Actually, not at all the same problem. On my laptop the Intel i915 module is present and loads just fine. It was a frame buffer issue and fixed by turning off frame buffers in /etc/lilo.conf.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.