No you can’t. The reason for the limitation is that static methods can also be called from non-static contexts without needing to prepend the class name (so MyStaticMethod() instead of MyClass.MyStaticMethod()). The compiler can’t tell which you’re looking for if you have both.
You can have static and non-static methods with the same name, but different parameters following the same rules as method overloading, they just can’t have exactly the same signature.