--- In LINUX_Newbies@yahoogroups.com, Scott <scottro@...> wrote:
>
> On Sun, Jan 09, 2011 at 01:52:15AM -0000, kazman1914 wrote:
> > Hi,
> >
> > Thank you for showing such patience to an extreme newbie. You asked:
>
> Some folks here are good at that. :) (That's why it's called
> Linux_Newbies).
>
>
> To summarize
> Time Warner gave you a cable modem (that also works your phone.) You've
> established that the hardware works, as Windows can get an address.
>
> You're not using wireless. (That's what was meant by the question about
> whether a wire was connected. )
>
> > "If there is no wire and you are able to connect to the internet
> > using Windows, please let us know that also. We will work
> > from there."
>
> > "Please tell us exactly which Ubuntu you installed. It is possible
> > to download many different flavors of Ubuntu and some install what
> > is called Network Manager (or equivalent) and some don't."
> >
> > I'll have to get back to you on that. It's the latest non-BETA version, 10.04 I think, but I'll have to check to be sure. Based on my conversation with customer service at TWC, the modem is set to provide the IP address via DHCP.
>
> Question--does Ubuntu definitely see the ethernet card. That is, if you
> open a terminal (In Ubuntu, I think it's under
> Applications=>Accessories) and type
>
> ifconfig eth0
>
> Does it show something?
>
> My guess is always on NetworkManager, which came by its nickname of
> NetworkMangler honestly.
>
> Also, Ubuntu 10.04 has long term support (henceforth known as LTS), but
> it isn't the newest. The newest theoretically stable version is 10.10
> and there's an alpha of the next one coming out.
>
> I'd be really curious to know if other distributions worked.
>
> For the moment, please try the ifconfig eth0 command and see if that
> brings a result. You'll get about 4 or 5 lines of output, assuming it
> sees the card. If you see something like failure fetching device, then
> that would be the problem.
>
> Also, please post the output of
>
> lspci |grep -i ether
>
> (lspci gives information about the hardware--grep gets specific
> information, in this case the ethernet card. Usually, the output will
> be Ethernet with a capital E, but we use the -i to make it case
> insensitive.)
>
>
>
> --
> Scott Robbins
> PGP keyID EB3467D6
> ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 )
> gpg --keyserver pgp.mit.edu --recv-keys EB3467D6
>
> Spike: What, your Mom doesn't know?
> Joyce: Know what?
> Buffy: That I'm, uh...in a band. A rock band...with Spike here.
> Spike: Right. She plays the-the triangle...
> Buffy: Drums.
> Spike: Drums, yeah. She's hell on the old skins, you know.
> Joyce: (to Spike) And what do you do?
> Spike: Well I sing.
>
First thing I'd still do is reboot the modem. Just because it seems to "work" doesn't mean it is actually fully functional. Then for laughs just type pump -i eth0 and cross your fingers it might work.
I like network mangler! That has been my experience with it and this other devilish garbage that seems to get installed by default anymore called avahi-daemon.
While many changes have made Linux supposedly more wireless friendly they definitely make plain old wired connections a byzantine mess!
Some files I have found that affect network behavior include:
/etc/udev/rules.d/70-persistent-net.rules
/etc/network/interfaces
Then there are the traditional files one would expect:
/etc/resolv.conf
/etc/hosts
Helpful commands include:
pump
route -n
less /etc/network/run/ifstate
If you would like to get rid of pesky programs:
# apt-get remove network-manager
# update-rc.d -f avahi-daemon remove
# /etc/init.d/networking restart
No comments:
Post a Comment