From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] 2.6.28-gentoo sources quite sluggish on Dell Inspiron 8100 / 1GHz PIII
Date: Thu, 22 Jan 2009 15:41:08 -0600 [thread overview]
Message-ID: <58965d8a0901221341m3c9e7fabp77766ab3d70140da@mail.gmail.com> (raw)
In-Reply-To: <4978E6BE.9050207@gmail.com>
On Thu, Jan 22, 2009 at 3:35 PM, Dale <rdalek1967@gmail.com> wrote:
> Paul Hartman wrote:
>> On Wed, Jan 21, 2009 at 9:05 PM, Dale <rdalek1967@gmail.com> wrote:
>>
>>> Volker Armin Hemmann wrote:
>>>
>>>> On Donnerstag 22 Januar 2009, Dan Farrell wrote:
>>>>
>>>>
>>>>> Hi all,
>>>>>
>>>>> I recently updated my dell Inspirion 8100's software after I found to
>>>>> my suprise I could no longer play video fast enough to watch. I did a
>>>>> kernel upgrade from 2.6.24 to 2.6.28, with a number of
>>>>> reconfigurations, including moving from madwifi to in-kernel ath5k.
>>>>> Also updated nvidia-drivers to go along with the new system.
>>>>>
>>>>> Now my system is extremely sluggish. It updates the screen very slowly
>>>>> in X and CPU performance is noticably slower without X running too.
>>>>> WiFi speed is dismal.
>>>>>
>>>>> I tried to remove all cruft and extras from the kernel, but I haven't
>>>>> managed to improve matters yet. Since it now takes hours to update the
>>>>> system, I was hoping someone might have and idea as to what the cause
>>>>> of the slowdown might be.
>>>>>
>>>>> Sound Familiar? Any guesses?
>>>>>
>>>>>
>>>> group scheduling? get rid of it.
>>>>
>>>>
>>>>
>>>>
>>>>
>>> I have been using 2.6.23 kernel for a while for the same reason. I'm
>>> going to check my config now.
>>>
>>> Dale
>>>
>>
>> On my laptop it is noticeably sluggish when using SLUB instead of SLAB
>> (despite SLUB being the default, I find it to be worse every time I've
>> tried it so far)
>>
>>
>>
>
>
> Is there a howto for this sort of thing? From what I read here and
> other places, some laptops are really confusing but there are even
> desktops that have issues with some new features. How does one get a
> idea of what they should try? I remember a list ages ago when I first
> installed Gentoo that has a list of CPUs andsome of the options a person
> could put in make.conf. I think we need one of those, maybe on a wiki
> or something, that lists models and what setting really work. I think
> laptops would really benefit from this. I have never had a laptop but
> they seem to be tricky to be nice about it.
I think, other than power-saving stuff, there shouldn't really be any
big difference between desktop and laptop settings...
http://linuxonlaptops.com has lots of info about specific
configurations for various laptops.
prev parent reply other threads:[~2009-01-22 21:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 1:45 [gentoo-user] 2.6.28-gentoo sources quite sluggish on Dell Inspiron 8100 / 1GHz PIII Dan Farrell
2009-01-22 1:47 ` Volker Armin Hemmann
2009-01-22 2:53 ` Dan Farrell
2009-01-22 3:05 ` Dale
2009-01-22 15:18 ` Paul Hartman
2009-01-22 21:35 ` Dale
2009-01-22 21:41 ` Paul Hartman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=58965d8a0901221341m3c9e7fabp77766ab3d70140da@mail.gmail.com \
--to=paul.hartman+gentoo@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox