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.
Hi everyone, i have a Acer Verition at school that im trying to get Slack to work on. The porblem is that once the startup has finished, it waits a min or 2 then automatically reboots. I havnt timed it on how long it takes for the reboot to kick in, but its around 2 mins or so after the login prompt is shown.
I dont have to login for the reboot to happen, it can be just sitting waiting for a command or in X.
I have installed Debian 3.0, Redhat 7.3 and mandrake 9.1 + 9.2 before on the same machine, and i havnt had this problem on any of them.
I checked the ACPI and APM(?) settings in the bios, but there were none to enable/disable, and also checked the motherboard for any signs of jumpers or whatnot.
I also tried to use the acpi=no apm=off noapic parameters for the kernel boot, but i still get the same problem.
I have read that you can compile a kernel on another machine, and copy it over, tho im not a very experienced linux user, i have no idea how to do this.
If anyone has any ideas/suggestions or want me to try something out, ill be glad to help.
p.s: i did a dmesg |more and put it to a txt file, if anyone wants that, let me know
hhhhmmmm it sounds more like a hardware problem despite having had other distros on it before, can you put something else on it for a bit and see what happens? as far as compiling a kernel on another box all you need is configure it just like you would if you were compiling it on the problem computer and put it on a disk or something, nothing special, if you want modules thats harder but just a rescue kernel shouldnt need modules anyways and you can get it working then afterwards