Even running "radeontool --help" gives back the "mmap error" message. Reproducible: Always Steps to Reproduce: 1. radeontool --help Actual Results: mmap error Expected Results: The help about command line arguments. The following patch fixes the problem to me: --- radeontool.c 2004-12-31 00:32:43.476822439 +0100 +++ radeontool.c.orig 2004-12-31 00:31:55.265222292 +0100 @@ -107,8 +107,7 @@ mem_fd, base ); - if( (void*) device_mem == MAP_FAILED ) { - //if ((long)device_mem < 0) { + if ((long)device_mem < 0) { if(debug) fprintf(stderr,"mmap returned %d\n",(int)device_mem); fatal("mmap error \n");
Ooops: I reversed the filenames in the diff command! --- radeontool.c.orig 2004-12-31 00:31:55.265222292 +0100 +++ radeontool.c 2004-12-31 00:32:43.476822439 +0100 @@ -107,7 +107,8 @@ mem_fd, base ); - if ((long)device_mem < 0) { + if( (void*) device_mem == MAP_FAILED ) { + //if ((long)device_mem < 0) { if(debug) fprintf(stderr,"mmap returned %d\n",(int)device_mem); fatal("mmap error \n"); Sorry for the inconvenience!
Please attach the output of 'emerge --info'.
This bug report is awaiting feedback from the reporter.
Created attachment 47946 [details] emerge --info output Sorry for the delay;: I was far from my email. In any case it seems more a thinko in the mmap() return check than an environment issue.
Thank you for reporting back.
Thank you for reporting this. I have fixed this in app-laptop/radeontool-1.5-r1 and submitted the patch upstream.