X will not start on a Thinkpad 240 using neomagic

Alex Bowden alex.bowden at outlook.com
Thu Jan 25 17:33:17 UTC 2018

Hi Michel,

Thank you very much for the insight on CONFIG_IO_STRICT_DEVMEM. I was able to use SystemTap to find where the error was occurring in the kernel. It turns out the vesafb takes the framebuffer and sets it IO_RESOURCE_BUSY using sysfb. When the framebuffer memory is set as busy and the strict devmem is enabled it will not allow the userspace to mmap this area. I changed my grub config to use GRUB_TERMINAL=console and that fixed the problem!!


More information about the xorg mailing list