I'd say that depending on the model of the cable modem, you're looking at a speed/duplex mismatch. Cisco gigabit interfaces are funny sometimes in that they won't autonegotiate with a 100mbps link...I've got a number of 7206 routers (FE interfaces) plugged in to a 4500 switch (GigE interfaces) and they will not negotiate duplex at all. If I leave the GigE ports at auto, I get innundated with CDP messages about a duplex mismatch. If I set them to speed 100 duplex full on both sides, they work perfectly.
Your cable modem may only be capable of 100/half or even 10/half. Some older ones are definitely like that.
You can also try to issue no keepalive to the interface facing the cable modem and fake it...that'll force the interface into up/up mode, regardless of physical/line protocol.
Regarding some other comments, Ethernet interfaces do NOT show up/down if no cable is plugged in to them outside of GNS3. On real equipment, they show down/down, regardless of whether it's a switch or a router. Also, the link and line statuses of sh int and sh ip int brief are referencing the same things. In both cases (sh int and sh ip int) they reference physical link and line protocol. Physical link WILL NOT show "up" unless it actually is up on real equipment.
MtnMan: calling people who do this for a living "trolls" because their experience differs with your tinkering in GNS3 does not do much to endear you to the community. When you've got some seasoning under your belt, then you can come back and tell people off...but until then, your posts have spoken for themselves as to your actual level of knowledge. That level is not such that will garner you any respect among the more knowledgable people on this forum. There are plenty of very knowledgable people here and they will help to the best of their time/abilities...but cursing at them and calling them "trolls" isn't the best way to go about getting that aid.