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'm newbie to linux, i've tried redhat & mandrake but now i'm eager to try slackware. I've successfully install slackware in my compaq evo machine,but everytime i logout to usual user from the root, the screen became blank, and nothing i can do except reboot the machine,please help me...
There's a bug in the new XFree for certain ati graphics cards with these symptoms. There's some rpm patches around for mandrake; don't know if there is anything for slack. You might try the XFree website if this applies to you.
On second thought, this sounds like a framebuffer problem and/or complications with it.
We'll rule that in/out by passing this option at boot:
<label of slack system> vga = normal
Type this at the boot: prompt for lilo, and it'll disable the framebuffer on next load.
Then try to run normally and see whatcha get.
I have a feeling it's trying to use a vidcard specific kernel framebuffer driver, when vesa would be better. A Kernel recompile with specific driver, or normal vesa driver for the framebuffer will solve this, but vga=normal at boot time will help us narrow the problem down and work as a temporary solution (or permanent, if you don't mind having no framebuffer.)
i might be way off here, but at one time i used framebuffer drivers, and it gave me a lot of trouble. on my laptop where framebuffere ran 1024x768 and x the same i had no problem, but on my desktop with framebuffer doing 1024 and desktop doing 1600x1200, everytime i went into x, i could no longer go into the console. its nice to have framebuffer and this nice big console window, but with xterm its kinda not needed. so, do what he said, if it works, then you tell lilo.conf to use vga instead of framebuffer
I've tell lilo to use this option: "linux vga=normal" but the problems still occurred,
every time i logout from x window, the screen become blank and nothing i can do except reset the machine
i've another problem too, can you guys teach me how to connect to a printer which is using jet direct interface?i've tried to install via SWAT but there's no option for jet direct interface,all interfaces are local interface