Quote:
I have tried changing the Kconfig.debug ad setting STRICT_DEVMEM=y.
|
In fact it should be the other way round. If you set CONFIG_STRICT_DEVMEM = y, you'll definitely not be allowed to access certain parts in the physical address space. As far as I know, CONFIG_STRICT_DEVMEM is enabled by defualt ( that is set to 'y' ) in Ubuntu, so you should in fact set it to 'n' and then try
Quote:
I also looked at some solutions which said that changes need to be made to other (arch/x86/mm/init_32.c, init_64.c, drivers/char/mem.c). But I do not see those files.
|
Very surprising! I've Kernel 2.6.37.1 and mem.c is very much there. Please check your sources again.
Also check for functions like range_is_allowed()(drivers/char/mem.c) and devmem_is_allowed()(arch/x86/mm/init.c) in your source and you can learn why your /dev/mem is being blocked!