Install issues in CentOS7

I am installing Omeka-2.3 under CentOS7 and hitting a few install issues. Mainly, I believe, with the .htaccess/mod_rewrite. I did set "RewriteBase /omeka/" since this us under http://<server>/omeka not in the DocumentRoot of the server itself.

http://<server>/omkea gives the error "mod_rewrite is not enabled. Apache's mod_rewrite extension must be enabled for Omeka to work properly. Please enable mod_rewrite and try again."

mod_rewrite is enabled as I have another URL being rewritten that is working. Also I threw a phpinfo.php file ("<?php phpinfo() ?>") under the main directory and that gets rewritten to install and then gives the error.

SteEnv is on, and log.errors=true but I see nothing in any code pages, or the application/logs/error.log. That file is empty.

Nothing useful under /var/log/http/error_log

I did find reference on the form of going to http://<server>/install/checkModRewrite.html and that gives me the line "Invalid controller specified (checkModRewrite.html)"

Any idea what that means or what might be wrong? The lack of errors has me a little stumped.

Can't tell you how pleased I am to find someone w/ such a problem in common. I am also installing (or trying to) Omeka-2.3 on CentOS7.
After restarting the installation from scratch a few times and trying every possible combination of httpd.conf and .htaccess edits I've come to the conclusion that some other folks in this forum did that the rewrite test was flawed somehow and that I should bypass it by simply going directly to install/install.php - many report they can continue w/ a normal install from that point. Instead, I'm now hitting another problem which is "omeka File storage not set up properly" telling me to make sure /files exists and the server can access it. The directory is there and even w/ the mode set to apache:apache and the all files/folder set to 777 I still get the error. Any suggestions from omeka-land would be very appreciated.

Just in case you are still having issues - this thread on resolving SELinux security context on CentOS may be useful.