[Bug 246269] Re: Switched from vesafb to uvesafb, but uvesafb can't work without v86d

[D. Hugh Redelmeier]

denisius.sion in #58 (probably 3 messages up, but I cannot tell until
after I post) seems to have an MTRR problem.

This message means that the kernel is refusing to change the type of an MTRR as the driver is telling it to do:
[ 16.285745] mtrr: type mismatch for fb000000,800000 old: write-back new: write-combining

The problem is likely due to nested MTRRs.  I bet you have 4GiB of RAM
or more on your machine.  Anyway, I think that you can ignore this
problem for now: I expect the only effect to be reduced performance from
uvesafb.

The same problem may or may come up when you run the X device driver.
It may or may not be serious then.  I don't know what nvidia driver you
use nor do I know much about those drivers anyway.

The proprietary ATI X driver that I have refuses to run if it cannot
adjust the MTRRs.

There are several workarounds for this nested MTRR problem (if, indeed,
I have correctly identified the problem).  One place to look is
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-
modules-2.6.24/+bug/224404

If I'm right, the MTRR problem is not really related to this particular
bug report.  Further MTRR discussion should be elsewhere.

-- 
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux-meta in ubuntu.