[SOLVED] System got totally messed up after huge update yesterday
ArchThis Forum is for the discussion of Arch Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
VirtualBox uses a kernel driver/module so when you change kernels you have to update that module by running the setup command it gave you. The path it gave you in the error may not be 100% accurate. In slackware the command would be
kernel modesetting. Intel, radeon, and nouveau have all started moving the modesetting code out of the Xorg driver and into the kernel direct rendering module. The fact that MTK358 now has a high resolution console is pretty indicative that he's using KMS (though, I guess, vesafb or uvesafb is also a possibility, but less likely, IMO).