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.
As a followup to my earlier post (thanks, trickykid, for the quick answer), I've got a slight problem with screen resolutions while not using X.
When I installed Slackware, it gave me the option of booting at various resolutions.. I chose "1024x768@64k colors". This worked for a while--I could boot up to the boot: prompt, and then it would switch to 1024x768, and all was hunky-dory.
Then I updated the kernel to 2.4.17. The system booted and then, after the boot: prompt, I got a blank screen. After rebooting, I tried loading my kernel image with "vga=normal", and it worked fine.
As far as I can tell, the 2.4.17 kernel is fine, but I can't get the new config to boot in a higher resolution.
Is there another config file, other than lilo.conf, that needs to be edited to make this work? Slackware took care of this for me originally, so I don't really know the extent of the job.
Thanks... but, unfortunately for for me, my Slackware 7.0 install doesn't know what "SVGATextMode" is. I checked the man page for rdev, and it tells me that all it does is change the kernel's instructions as to which video mode to boot into. If I'm not mistaken, this is what changing the option "vga=" in lilo.conf, and then running lilo, would do.
ACtually, reading further down the man page, it tells me that lilo makes using rdev unecessary. If I'm wrong on either one of these counts, please tell me.
Normally, I'd just give this one up and move on to something else (like that Java homework that's due tomorrow afternoon). But I KNOW there's something going on here... There has to be a method of making this work.
It outlines three separate ways to get "a high resolution console".
The method I was searching for, coincidentally, is the 3rd one listed on the linked page... It involved compiling the kernel with a few of the "Console Device" options set in a way that I didn't have them set up. So, I figured, rather than download some new software, I'd just recompile. The job is running right now, and hopefully it'll give me something to work with.
All told, thank you very much for the help. The only thing more frustrating than banging your head against a wall is doing it alone.
I did (finally!) get the fscking linux machine to boot, and then start using a 1024x768@64k resolution. I feel like I've climbed a freaking mountain. I recompiled my 2.4.17 kernel, as indicated in the link above, to include the options for the framebuffer support. My lilo.conf file has a "vga=791" statement, which directs it to use the proper resolution.
I would say, as a word of warning to anyone trying this: MAKE SURE YOU FOLLOW THE EXACT INSTRUCTIONS IN THE HI-RES HOWTO (link above) AS TO WHICH KERNEL OPTIONS YOU WANT INCLUDED. It took me three kernel compilations (well, two if you discount my unrelated stupid mistake) to get it right.
And dammit, if it's not 7:00 am, EST. Goodbye, sleep. Hello, coffee.