From: Mike Edenfield <kutulu@kutulu.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Updates = slow firefox
Date: Wed, 21 Apr 2010 15:57:03 -0400 [thread overview]
Message-ID: <4BCF588F.6090401@kutulu.org> (raw)
In-Reply-To: <q2k49bf44f11004211207u5689453br7f090823dcfcd2e1@mail.gmail.com>
On 4/21/2010 3:07 PM, Grant wrote:
> Could this be the problem?
>
> # grep ^\(EE /var/log/Xorg.0.log
> (EE) Failed to load module "vesa" (module does not exist, 0)
> (EE) Failed to load module "fbdev" (module does not exist, 0)
> (EE) intel(0): [drm] Failed to open DRM device for : No such file or directory
> (EE) intel(0): Failed to become DRM master.
> (EE) intel(0): Failed to initialize kernel memory manager
The first two errors are fine; Xorg defaults to trying vesa and fbdev as
display drivers and you just don't have them.
The last three are your problem. The intel video driver is unable to
properly access the DRM subsystem, which will definitely cause X to slow
to a crawl.
The most likely cause of your errors is that the intel AGP driver (i810
or i915, depending on your hardware) isn't getting loaded. If that's
the case, you should see an error such as:
[drm] failed to load kernel module "i915"
in Xorg.0.log just before the ones from intel. If the modules are being
loaded, you'll likely see some other errors around that same area. The
aren't tagged with (EE), unfortunately; try:
# grep -5 'Failed to open DRM' Xorg.0.log
You can also check your dmesg output to see if the devices are being
initialized properly:
platypus log # dmesg | grep agp
Linux agpgart interface v0.103
agpgart-intel 0000:00:00.0: Intel 965GM Chipset
agpgart-intel 0000:00:00.0: detected 7676K stolen memory
agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xe0000000
platypus log # dmesg | grep drm
[drm] Initialized drm 1.1.0 20060810
[drm] set up 7M of stolen space
[drm] initialized overlay support
fb0: inteldrmfb frame buffer device
[drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
If everything's working, you should have the following devices that the
Xorg driver needs:
platypus log # ls -l /dev/dri
total 0
crw-rw---- 1 root video 226, 0 Apr 20 13:11 card0
crw-rw---- 1 root video 226, 64 Apr 20 13:11 controlD64
next prev parent reply other threads:[~2010-04-21 19:57 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 22:06 [gentoo-user] Updates = slow firefox Grant
2010-04-19 22:12 ` deface
2010-04-19 22:43 ` Grant
2010-04-20 1:24 ` deface
2010-04-20 18:15 ` Bartosz Szatkowski
2010-04-20 18:51 ` Grant
2010-04-20 19:14 ` Bartosz Szatkowski
2010-04-21 11:26 ` Adam
2010-04-21 13:23 ` Mick
2010-04-21 19:07 ` Grant
2010-04-21 19:57 ` Mike Edenfield [this message]
2010-04-21 20:11 ` Grant
2010-04-22 16:47 ` Grant
2010-04-22 20:18 ` Mick
2010-04-23 9:01 ` Bartosz Szatkowski
2010-04-23 16:51 ` Grant
2010-04-23 17:08 ` erdunand
2010-04-23 17:13 ` Paul Hartman
2010-04-23 17:37 ` Grant
2010-04-23 17:46 ` Mike Edenfield
2010-04-23 18:21 ` Grant
2010-04-23 18:38 ` Dale
2010-04-24 7:33 ` Bartosz Szatkowski
2010-04-27 2:10 ` Grant
2010-04-27 17:00 ` Bartosz Szatkowski
2010-04-27 17:37 ` Grant
2010-04-27 21:31 ` Bartosz Szatkowski
2010-04-28 16:57 ` Grant
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=4BCF588F.6090401@kutulu.org \
--to=kutulu@kutulu.org \
--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