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.
I have a dual boot configuration using GRUB on my desktop PC. Dell Optiplex GX60, 2.40 celeron, 512 RAM, . The computer is only about 4 months old, so the hardware is fairly decent.
I installed SuSe 9.1 pro a few months ago, and it has been really running slow sinces the first day. So I decided to start again and re-installed it again, same result.
Grub boot loader
Windows XP Pro on the first partition
The problem is this:
Under any user, after I select to boot to Linux, it will take about 2 minutes to get passed the part where it shows the progress Icons. Then after the desktop background comes up it takes about an additional 3 minutes to populate the desktop with the task bar, icons.
After everything loads, which is a total of about 5 minutes, it seems to be a little slow on starting apps, but seems to move a decent speed once I am in the app. i.e. web browser and so on.
I read some other threads about machines "lagging" or pausing without I/O or 100% CPU. I have the following:
Pentium 4 2.66GHz
40GB HDD with DMA enabled
Ubuntu Linux 6.10 (just installed it again)
Just recently - before the reinstalling my OS - I noticed that selecting to run programs from the menus didn't start the programs until 1-3 minutes later. The CPU utilization was low and idling as if I hadn't selected to have anything run. No disk usage either, as my LED isn't flickering.
For example, opening Firefox:
1) I go to Apps -> Internet -> Firefox
2) Less than 1 sec of disk activity
3) Many minutes of waiting around...
4) The harddrive starts grinding as it normally does when an app is loading to memory.
5) App is working.
When I use these programs, they function as they normally do when open. However even after a cold start of Firefox, or XMMS, or Gaim, or the Gnome-Terminal the delay still persists.
One possibility that comes to mind is the preemption model of the kernel (since I've just been messing around with that today). If it's set to fully preemptible, then it seems to make things start slower while being more responsive once they are running. So the voluntary preemption model is usually a better choice than full.
So if you could grep your kernel config (I'm not sure where it would be in SuSe) for PREEMPT to see if that's the case here?
$ cat /usr/src/linux-headers-2.6.17-10/kernel/Kconfig.preempt
prompt "Preemption Model"
bool "No Forced Preemption (Server)"
This is the traditional Linux preemption model, geared towards
throughput. It will still provide good latencies most of the
time, but there are no guarantees and occasional longer delays
Select this option if you are building a kernel for a server or
scientific/computation system, or if you want to maximize the
raw processing power of the kernel, irrespective of scheduling
bool "Voluntary Kernel Preemption (Desktop)"
This option reduces the latency of the kernel by adding more
"explicit preemption points" to the kernel code. These new
preemption points have been selected to reduce the maximum
latency of rescheduling, providing faster application reactions,
at the cost of slighly lower throughput.
This allows reaction to interactive events by allowing a
low priority process to voluntarily preempt itself even if it
is in kernel mode executing a system call. This allows
applications to run more 'smoothly' even when the system is
Select this if you are building a kernel for a desktop system.
bool "Preemptible Kernel (Low-Latency Desktop)"
This option reduces the latency of the kernel by making
all kernel code (that is not executing in a critical section)
preemptible. This allows reaction to interactive events by
permitting a low priority process to be preempted involuntarily
even if it is in kernel mode executing a system call and would
otherwise not be about to reach a natural preemption point.
This allows applications to run more 'smoothly' even when the
system is under load, at the cost of slighly lower throughput
and a slight runtime overhead to kernel code.
Select this if you are building a kernel for a desktop or
embedded system with latency requirements in the milliseconds
bool "Preempt The Big Kernel Lock"
depends on SMP || PREEMPT
This option reduces the latency of the kernel by making the
big kernel lock preemptible.
Say Y here if you are building a kernel for a desktop system.
Say N if you are unsure.
I don't know if this is the right file or not. If I change this to voluntary preemption, is a recompile of the kernel necessary?
That file just shows what the options are. Maybe there's a copy of the config in /boot? or in /proc? Yes, changing it would require a recompile. But then I can't guarantee if that 's the answer here, 1m10.562s seems like more than just preemption would cause?