Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Yeah, also, how does your boot sequence go? Because on my laptop my CD then the FD and finally the HD is booted, and so checking the devices first makes the screen go blank a couple of seconds. How long is the blanking process?
Do you send some extra parameters to the kernel when loading linux?
One that might be important here is vga=xxx. It might be so that you have a kernel that doesn't have framebuffer support for consoles and when you tell the kernel to run in say vga=791 then the screen goes blank.
I think it would be good to post your /boot/grub/menu.lst here.
Ok.. .let me try 0x314. I switched it to splash=0 and all was fine. It booted up fine without the stupid splash screen. But if it wasn't then sometimes when linux was choosen to be booted the screen would just blank out...
Ok i tried it with 0x314 which was 800x600 the problem is still there. Also, I found out that splash=0 actually doesn't get rid of the problem. Even with 0x314 and splash=0 the problem is still there.
I think it might be the linux kernel? I installed redhat9 and there were no problems - could it be that the different distros don't both support my graphics card? (Radeon 9600) I remember on redhat the driver was VESA generic where as the suse one recognised it as RV350 or something on those lines.
I will probably compile a new kernel this weekend and see how this goes, anyone else with ideas?
Yeah... and i will probably compile lotsa other stuff into kernel...
I am actually running legacy ata suport but my harddrive is SATA, so maybe compiling the kernel with sata support might be a good idea.
If/when you do recompile your kernel, make sure you are including support for RAM disks and initrd images, as well as including frame buffer support. Those are all needed to get a bootsplash working correctly I believe