linux-kernel - Re: intel kms "Failed to allocate space for kernel memory manager"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 12 Jan 2009 22:32:35 +0100
From:	Olivier Galibert <galibert@...ox.com>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
Cc:	Dave Airlie <airlied@...il.com>, Jan Dittmer <jdi@....org>,
	Diego Calleja <diegocg@...il.com>,
	linux-kernel@...r.kernel.org, eric.anholt@...tel.com,
	airlied@...ux.ie
Subject: Re: intel kms "Failed to allocate space for kernel memory manager"

On Mon, Jan 12, 2009 at 09:53:49AM -0800, Jesse Barnes wrote:
> On the contrary, I think we have way too many options and configuration 
> possibilities.  The more we have, the more likely some combination of them 
> will be broken.

You need to be able to fix wrong data coming from the bios or other roms.


> That said, modes are generally pretty easy to handle, so users can provide 
> them through xrandr and xorg.conf; I don't see that changing.

The intel driver ignores modelines if a bios mode is present, at least
for lvds.  Check i830_lvds_mode_fixup.

  OG.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/