Tux

...making Linux just a little more fun!

Networking Problem on Hardy Heron

Deividson Okopnik [deivid.okop at gmail.com]


Sat, 17 May 2008 11:34:55 -0300

Anyone tried Hardy Heron (Ubuntu) yet?

I just installed Hardy on my new machine, first Linux distro on that machine, and I couldn't get my network to work. I dual-boot (with XP), and, on WinXP, it's working OK. My network is pretty simple - each machine has its own static IP (no DHCP). On Hardy, I configured the IP via the network config (the same IP I use on that machine for Windows XP), but nothing works. I can't ping other machines on the network, other machines can't ping me, and Hardy is not asking for any driver or anything.

Any clue on what could I check to try to solve that problem?


Top    Back


René Pfeiffer [lynx at luchs.at]


Sat, 17 May 2008 16:46:30 +0200

On May 17, 2008 at 1134 -0300, Deividson Okopnik appeared and said:

> Anyone tried Hardy Heron (Ubuntu), yet?

No, not yet.

> I just installed Hardy on my new machine, first Linux distro on that machine,
> and I couldn't get my network to work. I dual-boot (with XP), and, on WinXP, it's
> working OK. My network is pretty simple - each machine has its own static IP
> (no DHCP). [...]
>
> Any clue on what could I check, to try to solve that problem?

No clue yet, but what's your hardware like? Can you send the output of lspci, lsmod, and "ip -a"/ifconfig? It might be a newer network interface card.

Best, René.


Top    Back


Ben Okopnik [ben at linuxgazette.net]


Sat, 17 May 2008 11:54:35 -0400

On Sat, May 17, 2008 at 11:34:55AM -0300, Deividson Okopnik wrote:

>    Anyone tried Hardy Heron (Ubuntu), yet?

Kat has it installed on her laptop, last week; I was so busy that I only got to upgrade to Gutsy.

>    I just installed Hardy on my new machine, first Linux distro on that
>    machine, and I couldn't get my network to work. I dual-boot (with XP), and,
>    on WinXP, it's working OK. My network is pretty simple - each machine has
>    its own static IP (no DHCP). On Hardy, I configured the IP via the network
>    config (the same IP I use on that machine for Windows XP), but nothing
>    works. I can't ping other machines on the network, other machines can't
>    ping me, and Hardy is not asking for any driver or anything.
> 
>    Any clue on what could I check to try to solve that problem?

What does 'ifconfig -a' say? You might have a shiny, brand-new weird interface name for your NIC - or you might not have anything at all, meaning that you don't have the right module loaded to drive the hardware.

Assuming that all of that is good, what does 'route -n' (or 'netstat -r') say? You might not have routing to the other machines set up. Of course, if you're on a private network, that doesn't apply.

One of the reasons that I originally (albeit grumpily) decided to try Ubuntu is that it was a Debian derivative, and I could still use my command line tools. The CLI will always tell you the truth; the pretty graphical stuff obscures too many things.

-- 
* Ben Okopnik * Editor-in-Chief, Linux Gazette * http://LinuxGazette.NET *


Top    Back


Neil Youngman [ny at youngman.org.uk]


Sat, 17 May 2008 18:44:46 +0100

On Saturday 17 May 2008 15:34, Deividson Okopnik wrote:

> Anyone tried Hardy Heron (Ubuntu) yet?

Downloaded, but not installed.

> I just installed Hardy on my new machine, first Linux distro on that
> machine, and I couldn't get my network to work. I dual-boot (with XP), and, on
> WinXP, it's working OK. My network is pretty simple - each machine has its
> own static IP (no DHCP). On Hardy, I configured the IP via the network
> config (the same IP I use on that machine for Windows XP), but nothing
> works. I can't ping other machines on the network, other machines can't ping
> me, and Hardy is not asking for any driver or anything.
>
> Any clue on what could I check to try to solve that problem?

What type is the network card? Does lsmod show anything that looks like it might be the driver for that card? Does dmesg show any errors that might be related to that card, or to networking generally?

Neil


Top    Back


Ben Okopnik [ben at linuxgazette.net]


Sat, 17 May 2008 14:02:13 -0400

On Sat, May 17, 2008 at 06:44:46PM +0100, Neil Youngman wrote:

> On Saturday 17 May 2008 15:34, Deividson Okopnik wrote:
> > Anyone tried Hardy Heron (Ubuntu), yet?
> 
> Downloaded, but not installed.
> 
> > I just installed Hardy on my new machine, first Linux distro on that
> > machine, and I couldn't get my network to work. I dual-boot (with XP), and, on
> > WinXP, it's working OK. My network is pretty simple - each machine has its
> > own static IP (no DHCP). On Hardy, I configured the IP via the network
> > config (the same IP I use on that machine for Windows XP), but nothing
> > works. I can't ping other machines on the network, other machines can't ping
> > me, and Hardy is not asking for any driver or anything.
> >
> > Any clue on what could I check, to try to solve that problem?
> 
> What type is the network card? Does lsmod show anything that looks like it 
> might be the driver for that card? Does dmesg show any errors that might be 
> related to that card, or to networking generally?

Also, what does 'lspci' show? I've come to rely on it quite a lot while troubleshooting my WiFi (which, sadly, stopped working after a recent upgrade, and, despite my best efforts, hasn't yet returned to the land of the living. I'll drag those tribulations in later, maybe.)

Anyway, the path from that end goes something like this:

1) Use 'lspci' to figure out the hardware.
2) Use Google to figure out the chipset, if applicable (a big deal with WiFi).
3) Use Google again to figure out the right module, if it's not obvious.

This is pretty drastic stuff, though. Usually, it doesn't take anything this complex.

-- 
* Ben Okopnik * Editor-in-Chief, Linux Gazette * http://LinuxGazette.NET *


Top    Back


Deividson Okopnik [deivid.okop at gmail.com]


Mon, 19 May 2008 09:33:31 -0300

Sorry for the delay - that's my work machine, so I didn't have access to it during the weekend. Here's what you guys asked:

root@deivid-ubuntu:/home/deivid# ifconfig -a
eth0      Link encap:Ethernet  Endere=E7o de HW 00:1e:8c:d0:91:d7
          inet end.: 192.168.0.98  Bcast:192.168.0.255  Masc:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  M=E9trica:1
          pacotes RX:0 erros:0 descartados:0 excesso:0 quadro:0
          Pacotes TX:0 erros:0 descartados:0 excesso:0 portadora:0
          colis=F5es:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
          Mem=F3ria:dffc0000-e0000000
(plus the loopback)

root@deivid-ubuntu:/home/deivid# route -n
Tabela de Roteamento IP do Kernel
Destino         Roteador        M=E1scaraGen.    Op=E7=F5es M=E9trica Ref  =
 Uso
Iface
192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 eth=
0
169.254.0.0     0.0.0.0         255.255.0.0     U     1000   0        0 eth=
0
0.0.0.0         192.168.0.100   0.0.0.0         UG    100    0        0 eth=
0

dmesg - only weird network-related stuff I found was:

[   29.866928] ADDRCONF(NETDEV_UP): eth0: link is not ready

The cable is on, though. (If I reboot on Windows, it works.)

lspci and lsmod are on the attached file - pretty weird tho, couldn't spot anything wrong.


Top    Back


René Pfeiffer [lynx at luchs.at]


Mon, 19 May 2008 14:46:04 +0200

On May 19, 2008 at 0933 -0300, Deividson Okopnik appeared and said:

> Sorry for the delay - that's my work machine, so I didn't have access to it
> during the weekend.

No problem.

> Heres what you guys asked:
>=20
> root@deivid-ubuntu:/home/deivid# ifconfig -a
> eth0      Link encap:Ethernet  Endere=E7o de HW 00:1e:8c:d0:91:d7
>           inet end.: 192.168.0.98  Bcast:192.168.0.255  Masc:255.255.255.0
>           UP BROADCAST MULTICAST  MTU:1500  M=E9trica:1
>           pacotes RX:0 erros:0 descartados:0 excesso:0 quadro:0
>           Pacotes TX:0 erros:0 descartados:0 excesso:0 portadora:0
>           colis=F5es:0 txqueuelen:1000
>           RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>           Mem=F3ria:dffc0000-e0000000

So, you have an interface. That's good.

> [...]
> dmesg - only weird network-related stuff I found was:
> [   29.866928] ADDRCONF(NETDEV_UP): eth0: link is not ready

This is the symptom of your problem.

> [...]
> lspci and lsmod are on the attached file - pretty weird tho, couldn't spot
> anything wrong.

But I can. :)

> root@deivid-ubuntu:/home/deivid# lspci [...] 02:00.0 Ethernet
> controller: Attansic Technology Corp. L2 100 Mbit Ethernet Adapter
> (rev a0)

You are the proud owner of a very recent Ethernet chipset whose driver/functionality isn't supported by the Linux kernel (yet). This problem is known and was already discussed on TAG, AFAIR. I only found the discussion in the Ubuntu forum.

http://ubuntuforums.org/showthread.php?t=3D429845

The driver code is here http://atl2.sourceforge.net/, and you have to patch your kernel or find a testing kernel package that already has it.

> root@deivid-ubuntu:/home/deivid# lsmod
> [...]
> atl2                   33176  0=20
> [...]

Although your kernel has the module, I'd check for newer versions. I experienced similar problems with Realtek and Marvell chipsets, that were detected by the kernel, but the module was a little bit too old.

Best, René.


Top    Back


Ben Okopnik [ben at linuxgazette.net]


Mon, 19 May 2008 09:07:22 -0400

On Mon, May 19, 2008 at 02:46:04PM +0200, René Pfeiffer wrote:

> On May 19, 2008 at 0933 -0300, Deividson Okopnik appeared and said:
> > 
> > dmesg - only weird network-related stuff I found was:
> > [   29.866928] ADDRCONF(NETDEV_UP): eth0: link is not ready
> 
> This is the symptom of your problem.

[...]

> > root@deivid-ubuntu:/home/deivid# lspci
> > [...]
> > 02:00.0 Ethernet controller: Attansic Technology Corp. L2 100 Mbit Ethernet Adapter (rev a0)
> 
> You are the proud owner of a very recent Ethernet chipset whose
> driver/functionality isn't supported by the Linux kernel (yet). This
> problem is known and was already discussed on TAG, AFAIR. I only found
> the discussion in the Ubuntu forum.
> 
> http://ubuntuforums.org/showthread.php?t=429845
> 
> The driver code is here http://atl2.sourceforge.net/, and you have to
> patch your kernel or find a testing kernel package that already has it.
> 
> > root@deivid-ubuntu:/home/deivid# lsmod
> > [...]
> > atl2                   33176  0 
> > [...]
> 
> Although your kernel has the module, I'd check for newer versions. I
> experienced similar problems with Realtek and Marvell chipsets, that
> were detected by the kernel, but the module was a little bit too old.

René has covered it in great detail; I just wanted to add that a number of people have had good luck compiling the module from the source code made available by Atheros. (This is based on the reports I've found via Google.) It's possible that the latest, hot-off-the-compiler kernel may have a better version, but, with very recent hardware, the best way is usually to go right to the source - which is available here:

ftp://ftp.hogchain.net/pub/linux/attansic/

-- 
* Ben Okopnik * Editor-in-Chief, Linux Gazette * http://LinuxGazette.NET *


Top    Back


Deividson Okopnik [deivid.okop at gmail.com]


Mon, 19 May 2008 10:19:22 -0300

Thanks a ton :)

Just trying to get to compile stuff without Internet, now. :P Missing packages and deps bad.


Top    Back


Deividson Okopnik [deivid.okop at gmail.com]


Mon, 19 May 2008 11:07:47 -0300

Worked 100% - thanks guys :)

Oh, and on a side-note about - Hardy Heron's Portugues translation is so much worse than Gutsy's :'(


Top    Back