On 10/25/06, Ken Moffat <[EMAIL PROTECTED]> wrote:
On Wed, Oct 25, 2006 at 09:23:47AM +0000, randhir phagura wrote:
> 3. On the other hand, when no module-loading is commented-out, all the
> modules are shown as loaded without trouble, in the log. But in this case,
> AGP is disabled. Extracts of log below shows the Error:
>
> (EE) SIS(0): [drm] Failed to acquire AGP, AGP disabled <--- <---
> (II) SIS(0): [drm] No valid IRQ number for device 1:0:0 (code -22)
> (II) SIS(0): [dri] Visual configs initialized
That sounds nasty. Did you google for 'Failed to acquire AGP' ?
My first hit just now was for the proprietary ati driver, but it did
point out that this message means you need the agp module for your
motherboard's chipset. In the kernel's .config it comes just before
the DRM (that is, dri!) options, so you might need to set CONFIG_AGP
and either CONFIG_AGP_INTEL or CONFIG_AGP_SYS [ or both of them ].
I suppose that means that without the dri module you are falling
back to pci access, which is not what I would have expected.
It really seems that you're having a problem with Mesa or drm, and sis
isn't exactly common, so that's possible. It looks like there's a new
version of the sis dri driver in Mesa-6.5.1. The entry log for the
main commit is "The SiS and Unichrome drivers assume that the handle
to the AGP map is equivalent to the AGP physical address. Fix this."
So, that could certainly be helpful.
Here's the commit and diff:
http://gitweb.freedesktop.org/?p=users/krh/mesa.git;a=commit;h=eb19a6b764d6145fce9ca1a8961d8c746f615c72
http://gitweb.freedesktop.org/?p=users/krh/mesa.git;a=commitdiff;h=eb19a6b764d6145fce9ca1a8961d8c746f615c72;hp=b64a89520566f1aebdd95ea03e5a8833d0bee5b8
You could try to apply just that patch to Mesa-6.5. Or, you could try
out Mesa-6.5.1. That would probably be fine.
BTW, what kernel version are you using?
--
Dan
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
