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.
I suspect that you are set to boot up into graphical mode, but somehow it's not working.
If this is the case, you will need to boot up from the cd (dvd ?), mount the drive partition that contains the /etc dir (relative to YOUR hard drive), and then edit the 'inittab' file. You need to set this line below:
Make sure it says '3', not any higher number (like 4 or 5). Save the file and reboot, removing your CD.
With any luck, you should boot to the command-line, at which point you can login and the configure your graphics.
Ooh dear - this sounds nasty. It appears that you had no problems when you setup from the cd/dvd, and the screen must have worked just fine, else you wouldn't have been able to answer all the questions. Now, once installed, the command line never appears upon boot. Can you confirm that the machine is in fact up - ie can you ssh in over the network to the box. Do you have a separate graphics card, or is there only one on-board card ?
Assuming that you did set the machine to DHCP, and it hasn't, then that does indicate that your problems are earlier in the boot process, and likely that the box has in fact crashed. It's fairly unusual that there's no clue on the screen. I'm assuming that you have installed a 32-bit slackware on a 32 bit box and not a 64-bit slackware on a 32-bit box. I'm not sure if the slackware installer would check that, as I've never done that. I say this because the boot process outputs a lot of stuff to the screen while it loads, and you say nothing is there (before the screen goes off) - indicating that the crash might occur even before the kernel loads properly. What about the disk drive - is it a newish one in good condition. Memory might also be a problem - can you do some sort of memory test from a boot cd ?
i think the problem is the video chipset because when i transfer the harddrive to the older system the boot process was successful i can login to to maintenance mode. and the screen was change to higher resolution.. and i also guess that you are right there is a problem in the frame buffer...
Your problem is not the i3, it's the graphics! I have the same problem with my Intel's GMA4500 chip. After loading several modules screen just turns off! If it's middle of the day I can "see" login screen even though the brightness is at 0%. I still didn't find the solution. I've tried this:
It might be a kernel bug, in which case you would need a newer kernel. That might be difficult to come by as you can't boot into the system normally. If it is a laptop, try the Fn keys and set brightness to max.