It would likely help to know what wireless chipset you have. lspci
in a terminal would report that.
It's a long shot, because, if the wireless finally connects, there might not be any messages output, but you might look in /var/log/messages. I would suggest using the less command, as it will allow you to navigate the file.
It might be best to do this right after a restart or the occurrence of the problem, so any new messages would be near the end of the file.
You might look into some of the other log files in /var/log, but messages is the place to start.
I can say that, while running current, I have had the occasional update affect the wireless, so that it does not maintain a connection; that is, the connection would drop within an hour or two. Generally, the next update has fixed that. I put it down to what happens when you run what's basically a testing version and hooked up the cable.
Right now, it's working fine under the current --Current.