Announcement

Collapse
No announcement yet.

SOLVED [kubuntu 9.04] cannot connect to wired internet [Realtek 8139too]

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    SOLVED [kubuntu 9.04] cannot connect to wired internet [Realtek 8139too]

    SOLVED NOW, SEE REPLY BELOW!

    Yet another report about a missing network connection in Kubuntu Jaunty (9.04) ...

    User level: Absolute beginner in linux

    Symptoms of the problem:
    no network connection via DSL router (which works fine in windows xp)
    after fresh install of Kubuntu Jaunty (9.04) (iso..i386 32 bit)
    on an old Medion computer: VIA chipset, RealTek ethernet, with ATI AGP card
    (Radeon HD3450, works somehow but not in best resolution 1680x1050)

    Steps to diagnosis / unsuccessful repair undertaken:

    1) Uninstalled Network Manager, modified /etc/network/interfaces -- problem persists
    ( after Detonate's HowTo http://kubuntuforums.net/forums/inde...opic=3100052.0 )

    2) Tried various other tricks in the forums (no improvement):

    -- Adding a router manually with
    Code:
    sudo route add -net 0.0.0.0 192.168.0.1
    failed with [SRIOCAT{don't remember}]: No such device.
    The IP is however the correct one, according to Windows | ipconfig/all

    -- killing the avahi-daemon gave no result

    -- installing wicd failed
    downloaded wicd_1.5.9-2_all.deb manually with the windows system, but got a
    "Dependency is not satisfiable: python-gtk2" (probably since I have no network...)

    3) Looking at the file /var/log/syslog after boot shows that
    --- with or without Network Manager, by the way ---

    a) the kernel reports an ethernet connection (or does it?)
    Code:
    kernel: [...] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
    b) there are repeated attempts by dhclient to get a connection
    Code:
    dhclient: Listening on LPF/eth0/00:16:17:31:79:88
dhclient: Sending on  LPF/eth0/00:16:17:31:79:88
dhclient: Sending on  Socket/fallback
...
dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
    Remark1: the correct subnet mask for my router should be 255.255.255.0,
    but I don't know how to change this behaviour
    Remark2: the eth0/xxx:etc. identifier is the MAC address of my card

    c) the kernel finally replies
    Code:
    kernel: [  30.927404] eth0: no IPv6 routers present
    and then, an ominous passage follows, marked "---[cut here]---"

    Code:
    kernel: [  31.883383] ------------[ cut here ]------------
kernel: [  31.883389] WARNING: at /build/buildd/linux-2.6.28/net/sched/sch_generic.c:226 dev_watchdog+0x219/0x230()
kernel: [  31.883392] NETDEV WATCHDOG: eth0 (8139too): transmit timed out
kernel: [  31.883395] Modules linked in: ppdev bridge stp bnep lp parport snd_via82xx gameport snd_ac97_codec ac97_bus 
[Cont'd] snd_pcm_oss snd_mixer_oss snd_pcm snd_page_alloc snd_mpu401_uart snd_seq_dummy snd_seq_oss snd_seq_midi 
[Cont'd] snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd pcspkr soundcore via_agp i2c_viapro shpchp 
[Cont'd] agpgart usbhid ohci1394 ieee1394 8139too 8139cp mii fbcon tileblit font bitblit softcursor
kernel: [  31.883439] Pid: 0, comm: swapper Not tainted 2.6.28-11-generic #42-Ubuntu
kernel: [  31.883442] Call Trace:
kernel: [  31.883450] [<c0139ab0>] warn_slowpath+0x60/0x80
kernel: [  31.883458] [<c02c44f0>] ? cfq_completed_request+0x160/0x220
kernel: [  31.883464] [<c0502c0e>] ? _spin_lock_irqsave+0x2e/0x40
kernel: [  31.883470] [<c0190f2e>] ? mempool_free_slab+0xe/0x10
kernel: [  31.883475] [<c02b7bef>] ? __freed_request+0xaf/0x120
kernel: [  31.883479] [<c02b8320>] ? blk_run_queue+0x30/0x40
kernel: [  31.883484] [<c02c7290>] ? kobject_put+0x20/0x50
kernel: [  31.883490] [<c034bf8f>] ? put_device+0xf/0x20
kernel: [  31.883496] [<c036a89a>] ? scsi_next_command+0x3a/0x50
kernel: [  31.883500] [<c02cb03d>] ? strlcpy+0x1d/0x60
kernel: [  31.883505] [<c04312f2>] ? netdev_drivername+0x32/0x40
kernel: [  31.883510] [<c0445e49>] dev_watchdog+0x219/0x230
kernel: [  31.883514] [<c043b72b>] ? neigh_table_init_no_netlink+0x14b/0x1d0
kernel: [  31.883518] [<c043af00>] ? neigh_periodic_timer+0x0/0x190
kernel: [  31.883524] [<c0144537>] ? mod_timer+0x37/0x80
kernel: [  31.883527] [<c043b026>] ? neigh_periodic_timer+0x126/0x190
kernel: [  31.883531] [<c0143b00>] run_timer_softirq+0x130/0x200
kernel: [  31.883535] [<c0445c30>] ? dev_watchdog+0x0/0x230
kernel: [  31.883539] [<c0445c30>] ? dev_watchdog+0x0/0x230
kernel: [  31.883544] [<c013f197>] __do_softirq+0x97/0x170
kernel: [  31.883549] [<c01554ef>] ? profile_tick+0x4f/0x90
kernel: [  31.883553] [<c013f2cd>] do_softirq+0x5d/0x60
kernel: [  31.883557] [<c013f445>] irq_exit+0x55/0x90
kernel: [  31.883562] [<c011a07b>] smp_apic_timer_interrupt+0x5b/0x90
kernel: [  31.883566] [<c050104a>] ? schedule+0x41a/0x710
kernel: [  31.883571] [<c0105318>] apic_timer_interrupt+0x28/0x30
kernel: [  31.883575] [<c010b012>] ? mwait_idle+0x42/0x50
kernel: [  31.883579] [<c010285d>] cpu_idle+0x6d/0xd0
kernel: [  31.883584] [<c04f110e>] rest_init+0x4e/0x60
kernel: [  31.883587] ---[ end trace db56c922f63a056d ]---

    So, finally, I'm out of ideas what to try next and would welcome any input from the experts in this forum.

    Thanks for your input,
    Ixhausen

    Attachments:
    - syslog traces on startup, with and without Network Manager,
    - copy of /etc/network/interfaces
    - syslog traces on shutdown (shutdown from KDE does not work, system seems to hang...
    tried Ctrl+Alt+F3 to get a console, "sudo shutdown now", got into recovery mode, chose "resume boot",
    then shutdown again from KDE, finally usual dialog "quit tty3?" OK - system halted)
    Attached Files
    Tags: None
    • Top
    • Bottom
    #2
    SOLVED [kubuntu 9.04] cannot connect to wired internet [Realtek 8139too]

    Aaaah! I heff ze internet now!

    The (trivial!) solution to this "bug" was actually offered in

    http://ubuntuforums.org/showthread.php?t=538448

    Briefly, my RealTek adapter was just put to sleep by Windows on shutdown, and kubuntu could not re-awaken it (even in kernel 2.6.31-999). Did I mention that I have a dual-boot system? Strange things can happen in this case, apparently.

    I simply followed the advice given at the link above and told WinXP to leave the RealTek on (by starting the device manager, locating the RealTek adapter there, dbl-clicking it, and applying the following setting in the advanced tab: Wake-On-Lan After Shutdown = Enabled).

    This behavior may be more general than I thought before. Lots of new *ubuntu users complain about very bad network support, which is of course a show-stopper for the transitionally-minded.

    Maybe the Wake-On-Lan feature is now ubiquitous in the ethernet adapter world?

    I guess that many newbies actually start off with a dual-boot installation, or just try the liveCD RIGHT AFTER WINDOWS SHUTDOWN (i.e. possibly with disabled network devices). The work-around is REALLY easy. But as an ubuntu/kernel/network bug, almost impossible to trace.

    Maybe this hint (make sure you enable Wake-On-Lan in Windows if you experience network problems in *ubuntu and if you're a double-booter, or if you try the liveCD from a windows system), could be included in the "known issues" section of the distro
    Whom do I tell?

    All is well and kubuntu 9.04 just upgraded from absolutely-useless to great-system in my eyes!


    P.S. BTW, the "kubuntu does not shutdown" problem seems to have vanished as well
    • Top
    • Bottom

    Comment

      #3
      Re: SOLVED [kubuntu 9.04] cannot connect to wired internet [Realtek 8139too]

      I wonder if it would also work if you just enable wake-on-lan in the BIOS before booting into Linux.
      • Top
      • Bottom

      Comment

        #4
        Re: SOLVED [kubuntu 9.04] cannot connect to wired internet [Realtek 8139too]

        Actually, no.

        I tried anyway, just to make sure, and it was --- goodbye, network. The old workaround I described above still works, luckily.

        I like this fiddling in winXP better than trying to operate my rather obscure Phoenix BIOS. Since every mainboard manufacturer actually has to adapt the off-the-shelf BIOS to each board, there is a plethora of different BIOSes around. Describing how things work in winXP seems more straightforward.

        In hindsight, it is no wonder that turning on Wake-On-Lan in the BIOS is not the right action: the feature is never really used in the process. --- It is my winXP that decides to switch off the ethernet adapter on shutdown, so that Wake-On-Lan is effectively made impossible. WinXP is also smart enough to turn the device back on at startup, but the present realtek8319too driver in ubuntu is not, apparently. So, at the moment, one has to tell winXP NOT to switch off the ethernet adapter on shutdown by "enabling" Wake-On-Lan-After-Shutdown. Confusing, but correct.
        • Top
        • Bottom

        Comment

          #5
          Re: SOLVED [kubuntu 9.04] cannot connect to wired internet [Realtek 8139too]

          Thanks for trying that for me. I have very little experience with the MS-Windows world.

          I use Wake-On-Lan on a headless server. To make that work I run "ethtool -s eth1 wol g" from a script in /etc/init.d/. The "wol" command supports two parameters:
          p Wake on phy activity
          g Wake on MagicPacket
          Perhaps the p could be useful for other situations like yours. Just a thought.
          • Top
          • Bottom

          Comment

          Previous template Next
          Working...
          X