Announcement

Collapse
No announcement yet.

9.04 "Jaunty" eth0 network problems.

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    9.04 "Jaunty" eth0 network problems.

    Hi community.

    I am using laptop HP
    model : m530

    Processor
    Clock Speed: 1.6 GHz
    Manufacturer: Intel
    Multi-Core Technologyual-Core
    Processor Number: T2050
    Type:Core Duo

    Networking
    Compliant Standards: IEEE 802.11a , IEEE 802.11b , IEEE 802.11g
    Data Link Protocol: Ethernet , Fast Ethernet , IEEE 802.11a , IEEE 802.11b , IEEE -802.11g
    Type: Network adapter
    Wireless NIC: Intel PRO/Wireless 3945ABG
    Wireless Protocol: 802.11a/b/g

    So, I have problem with eth0 , on Kubuntu 8.10 KDE 4.1 I don't have any problems with network just plug RJ-45 cable into network card and it's is all finish
    But on Kubuntu 9.04 "Jaunty" network is down , I don't have access on internet pls can you help me to diagnose problem.Here is my network infos:

    Code:
    apoc@Ragnarok:~$ lspci
    00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03)
    00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)
    00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
    00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01)
    00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 01)
    00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 01)
    00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 01)
    00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 01)
    00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e1)
    00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 01)
    00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 01)
    02:06.0 CardBus bridge: ENE Technology Inc CB1410 Cardbus Controller (rev 01)
    02:08.0 Ethernet controller: Intel Corporation 82562ET/EZ/GT/GZ - PRO/100 VE (LOM) Ethernet Controller Mobile (rev 01)
    10:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
    --
    apoc@Ragnarok:~$ ifconfig
    eth0   Link encap:Ethernet HWaddr 00:16:d4:f0:24:a1
         inet addr:192.168.1.65 Bcast:192.168.1.255 Mask:255.255.255.0
         inet6 addr: fe80::216:d4ff:fef0:24a1/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
         RX packets:606 errors:0 dropped:0 overruns:0 frame:0
         TX packets:289 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:50283 (50.2 KB) TX bytes:30203 (30.2 KB)
    
    lo    Link encap:Local Loopback
         inet addr:127.0.0.1 Mask:255.0.0.0
         inet6 addr: ::1/128 Scope:Host
         UP LOOPBACK RUNNING MTU:16436 Metric:1
         RX packets:176 errors:0 dropped:0 overruns:0 frame:0
         TX packets:176 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:12432 (12.4 KB) TX bytes:12432 (12.4 KB)
    --
    apoc@Ragnarok:~$ lshw -c network
    WARNING: you should run this program as super-user.
     *-network DISABLED                
        description: Wireless interface       
        product: PRO/Wireless 3945ABG [Golan] Network Connection
        vendor: Intel Corporation                
        physical id: 0                     
        bus info: pci@0000:10:00.0
        logical name: wmaster0
        version: 02
        serial: 00:1b:77:38:a4:4c
        width: 32 bits
        clock: 33MHz
        capabilities: cap_list logical ethernet physical wireless
        configuration: broadcast=yes driver=iwl3945 latency=0 module=iwl3945 multicast=yes wireless=IEEE 802.11abg
     *-network
        description: Ethernet interface
        product: 82562ET/EZ/GT/GZ - PRO/100 VE (LOM) Ethernet Controller Mobile
        vendor: Intel Corporation
        physical id: 8
        bus info: pci@0000:02:08.0
        logical name: eth0
        version: 01
        serial: 00:16:d4:f0:24:a1
        width: 32 bits
        clock: 33MHz
        capabilities: bus_master cap_list ethernet physical
        configuration: broadcast=yes driver=e100 driverversion=3.5.23-k6-NAPI firmware=N/A ip=192.168.1.65 latency=64 maxlatency=56 mingnt=8 module=e100 multicast=yes
     *-network DISABLED
        description: Ethernet interface
        physical id: 2
        logical name: pan0
        serial: de:89:e0:d2:be:a3
        capabilities: ethernet physical
        configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A multicast=yes
    0
    yes
    0%
    0
    no
    0%
    0

    #2
    Re: 9.04 "Jaunty" eth0 network problems.

    I solve problem.
    Knetowork-manager does not work . for DHCP or Manual configuration .
    So I edit /etc/network/interfaces.

    Code:
    apoc@Ragnarok:~/Desktop$ sudo kate /etc/network/interfaces
    [sudo] password for apoc:
    
    # Reedit interfaces to:
    
    auto lo
    iface lo inet loopback
    address 127.0.0.1
    netmask 255.0.0.0
    
    #configuration for eth0
    
    auto eth0
    iface eth0 inet dhcp
    address 192.168.1.10
    netmask 255.255.255.0
    gateway 192.168.1.254
    # save file then 
    sudo /etc/init.d/networking restart

    Comment


      #3
      Re: 9.04 "Jaunty" eth0 network problems.

      Originally posted by apoc
      I solve problem.
      Knetowork-manager does not work . for DHCP or Manual configuration .
      It works for DHCP, but not for static.

      Instead of setting the net config manually, I recommend using WICD (http://wicd.sourceforge.net/download.php)
      Specs:  Intel Core 2 Quad Q6600 (@3Ghz), G.SKILL 4GB DDR2 1066, ASUS Striker II Formula MB, Asus EN9800GTX+ Dark Knight, ABS Tagan BZ800 PS, Antec 900 Case.

      Comment


        #4
        Re: 9.04 "Jaunty" eth0 network problems.

        I using DHCP not static and it's doesn't work I don't know why.
        I try manual setting ip addresses but doesn't work so I reedit /etc/network/interfaces.
        OK I will try with WICD . Thx

        Comment


          #5
          Re: 9.04 "Jaunty" eth0 network problems.

          Originally posted by apoc
          I using DHCP not static and it's doesn't work I don't know why.
          I try manual setting ip addresses but doesn't work so I reedit /etc/network/interfaces.
          OK I will try with WICD . Thx
          Hmmm... not sure why DHCP's not working. That's what I'm using with for this machine (with KNetworkManager). Maybe I'm not having problems with it because I never attempted to change the settings from my 8.10 install.

          On all my other machines (where I use static addresses), I use WICD. It always "just works", as opposed to KNetworkManager... which still seems to be going through growing pains with each release. I don't think you'll be sorry for giving WICD a try.
          Specs:  Intel Core 2 Quad Q6600 (@3Ghz), G.SKILL 4GB DDR2 1066, ASUS Striker II Formula MB, Asus EN9800GTX+ Dark Knight, ABS Tagan BZ800 PS, Antec 900 Case.

          Comment


            #6
            Re: 9.04 "Jaunty" eth0 network problems.

            Hi guys.

            Since Kubuntu 8.04 I am looking for a solution to the static IP problem on eth0 WITHOUT any manually editing of some config file and WITHOUT deinstalling Knetworkamanger and switching to WICD. I know it works in Ubuntu/Gnome and it works it OpenSuse 11.1(?, I mean the most up-to-date one) with KDE 4.1. I am not a developer guy, just a "normal" user. I understand that there were some things going wrong in the 8.10, release which caused a total functionality loss of the Knetworkmanager and by searching for a solution I ran across a comment/apology from some Kubuntu dev. I totally understand that errors cannot be avoided and really honour all the work and time spent on developing Kubuntu, but that static IP problem (which still remains in my case, using an updated 8.10), is really annoying. In my case, I need static Ips to enter the network of my university. I have at least 3 university friends which are willing to switch to kubuntu (from WinXP) but with this problem remaining in 8.10 and now, against my hope, perhaps even in 9.04 (I know it is still alpha)...I just want to say to the dev's: Please, please solve this problem. If it just were some minor bug in some app... but not being able to connect to the internet is about the worst thing that could happen, because you also loose your only chance to solve the problem yourself!

            So, does anybody know if this problem is on the radar of the Kubuntu dev's and is getting fixed?

            It just would be a real pity if I had to change to some other distri JUST because of that bug because I really like Kubuntu. And now with KDE 4.2 out....Jesus!..please fix that BUG!!

            Comment


              #7
              Re: 9.04 "Jaunty" eth0 network problems.

              I can't look now, as i got my Jaunty Installation at home and i only have Ubuntu here, but if I get you right, you want a static ip configuration to be saved, and you dont want to edit it by hand?

              So I think you got three options:

              1) I think in KNetworkmanager you can specify your own connection. You have the option there to set a static ip.
              2) install Gnome Networkmanager (Fedora does this for their KDE edition I think)
              3) Make a short script

              I'll look up at 1) when I'm at home. Greetings

              Comment


                #8
                Re: 9.04 "Jaunty" Static IP issues

                Yup,

                I think you're right. Even if I make a new connection in the network manager, and store the IP address, its still no go. For those who don't know, here's how you set things up manually (this can be done in a simple shell script, if you wish):

                ifconfig eth0 192.168.1.10 netmask 255.255.255.0
                route add -net 0.0.0.0 192.168.1.1
                echo nameserver 192.168.1.1 > /etc/resolv.conf

                You probably do not need to use the the netmask part of the ifconfig command - although I do where I work, so I've put it in for completeness.

                In the route command, the 192.168.1.1 would be the address of your router.

                The address on the third line could be that of your router, an openDND address or one of your ISP's nameserver. Personally I put two nameservers in resolv.conf, and you could do this by adding a fourth line, like this:

                echo nameserver 192.168.1.2 >> /etc/resolv.conf

                Note the two > signs, which says to append to the file.

                Hopefully this will be helpful to some.

                Best Regards,

                Paul
                ~~~~

                Comment


                  #9
                  Re: 9.04 "Jaunty" Static IP issues

                  Originally posted by rvsjimbo


                  The address on the third line could be that of your router, an openDND address or one of your ISP's nameserver. Personally I put two nameservers in resolv.conf, and you could do this by adding a fourth line, like this:
                  echo nameserver 192.168.1.2 >> /etc/resolv.conf
                  According to man resolv.conf only three nameservers can be listed in resolv.conf.

                  Comment


                    #10
                    Re: 9.04 "Jaunty" eth0 network problems.

                    After all the problems I have had in the past with network manager, I switched to wicd.

                    This little program is not affected by changing kernels or kernel updates.

                    So, I am happy and my etho and ath0 and wlan0 work all the time.

                    Until network manager is finally improved and made foolproof, I will stick with wicd.

                    Comment

                    Working...
                    X