Hi Brice CONFIG_HIGHMEM64G was indeed enabled and the problem, it is working now!
Thank you very much, if I hadn't asked you, this wouldn't be fixed by now. Although my situation is probably rare, maybe we should add a comment mentioning this in the Changelog or README just in case, for other people who also happen to compile their own kernel with this option. Thanks again Huy Brice Goglin wrote: > > Do you have CONFIG_HIGHMEM64G in your kernel ? If so, GEM cannot work > with this option (before 2.6.31). > > If not, can you try a Debian kernel? Or send your kernel .config and dmesg? > > Thanks > Brice > > -- e10a5ba52ebd2b06b3cb114647d0b2d7149357ece59ebfb787a2a6cb653280ba Key ID = 0xE7C65F23 Key fingerprint = A3C6 F3CB C3F9 005A 95B0 9614 3AC5 A4D3 E7C6 5F23 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
