Ok, well, let's break this down a bit:
Failed modules during boot. Or better yet, any errors at boot.
If you have a working system, regardless of the thousands of errors at boot (I get around 5) then it's usually ok to disregard them, at least until you decide it's necessary to remove them (after you get your system up to par with your needs, such as desktop setup, server issues, whatever).
Assuming you don't want to wait, look through /var/log for info on kernel booting (such as /var/log/kernel/current and /var/log/everything/current if you are using metalog) info. This should display the information that's further down the line. The "OK's" or "Failed" probably won't be there, but errors might.
Once you find out what's failing you can either remove that from /etc/modules.conf (which isn't the file to edit btw in Gentoo. It's actually (from the modules.conf file)
/etc/modules.d and read
# the manpage for modules-update.
) until you no longer recieve those errors. As noted in the perenthesis above, you shouldn't be editing/creating a modules.conf file in the first place, this could be a reason for many of your errors.
Networking can sometimes be a real fun thing (yeah right). I'd lean towards your module having issues because of the above mentioned way of editing your modules.conf file. Try unloading the module:
And then reloading it:
And see how that goes.
Something I just noticed is that you use PPP to connect, and I've got no clue how to setup internet using that. However, I have seen quite a few threads on it, and I don't think that'd be distro specific (it might require packages to be emerged though).