Can't Login After Directly Instillation

Hi Everyone,
I have just tried to install Modx Revolution onto a brand new SUSE 11 Linux server. The instillation process ran smoothly, but when I try to log into the manager the login doesn't go anywhere. It just clears the login form. If I type an incorrect password or username I get an error. I have tried deleting the session_name, session_cookie_path, and session_cookie_domain out of the system_settings table, and clearing/deleting my cache, but nothing has worked. I have found a few threads of people having the same problem, but I haven't found a consistent answer the the problem...

Has anyone ever experienced this problem? If so, what are some other things I can try?

http://rtfm.modx.com/display/revolution20/Moving+Your+Site+to+a+New+Server

in the middle of this page, there's information about the files that need to be set to your site paths. Check the files, they should have the correct paths. If not, edit them. The login loop you're describing is often caused by incorrect paths in these files.

They should have been set during setup however. Did you install MODX manually or with a script from your server?

Thank you for the response! All my links seem to be linking to the proper places. Towards the end of that link you provided, there is an insert query to update the workspaces table. I updated that so that instead of using the {core_path} it has the full path (example: /srv/www/htdocs/myFoderName/core/). That didn't make a difference...

I installed modx 2.2.2-pl with the setup instillation process. I have actually used this same set of instillation files on another SUSE 11 server as well as a WAMP server and they worked perfectly.

I have noticed that even thought I have told the setup file to get deleted after the instillation it is still there. Is it possible it could be a file permissions problem?

So after messing with this for a few more hours today, I have noticed that you can login just fine with Firefox, but not Chrome or Internet Explorer.... I am extremely confused as to why it works on one browser, but not the others.....

You might try turning off the css and js compression. Sometimes servers and browsers don't get along well with the compression.