With sys-apps/pciutils-3.1.0-r1 installed pommed refuses to start with following errors: E: mmap failed: Invalid argument E: Could not map GMA950/GMA965 memory E: LCD backlight probe failed, check debug output After digging in the code of pommed I noticed random values of dev->base_addr[0] (dev being the intel graphic chipset) at each run. I downgraded to sys-apps/pciutils-3.0.2, and pommed now starts again. Note that I tried with app-laptop/pommed-1.25 and app-laptop/pommed-9999 before downgrading, both of them displayed the exact same error messages. Obviously this version of pciutils is buggy and might cause other applications that rely on it to crash. Reproducible: Always Steps to Reproduce: 1. merge app-laptop/pommed 2. merge sys-apps/pciutils-3.1.0-r1 3. try to start pommed with "pommed -d" Actual Results: pommed doesn't start Expected Results: pommed should start
This bug is mentioned here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=518750 The fix appears to be included in pommed 1.26, see bug #263729
Must be fixed with version 1.26
pommed 1.26 indeed works with newer versions of pciutils (tested with =sys-apps/pciutils3.1.2)