SlackwareThis Forum is for the discussion of Slackware 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.
You have my sympathy. I (unfortunately) have responsibility for a netbook that uses the GMA500. What a bloody fiasco (on Intels behalf IMHO). Alan Cox' recent work with the driver are starting to bear fruit, but it's a crap chip - hopefully yours is better.
Try nomodeset on the kernel line to see if a basic VESA display will get you the messages.
I just looked and the 3.2 config does not have the GMA3600 option at all, but in the config files for the huge kernels in /testing it is enabled by default. So after trying it with the nomodeset option I would recommend to go for the 3.5 kernel instead of 3.2.
Do I understand that right that you can boot from the install-DVD without that problem? If so, chroot into the installed system, then start the compile action, install the new kernel and don't forget to run lilo after you have changed lilo.conf.
Not exactly related but the huge kernel will lock hard on my system with my TV card installed. Has done that for years with all past releases. The only way I can boot into my system with the huge kernel is either remove the card or blacklist the module. I have no problem with a custom built kernel.
I share this because you might be experiencing something similar, although not necessarily a TV card.