[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#706499: marked as done (Ethernet with Realtek R8169 only working with IPV6)

Your message dated Mon, 06 May 2013 13:50:34 +0100
with message-id <1367844634.4131.62.camel@deadeye.wl.decadent.org.uk>
and subject line Re: Bug#706499: Ethernet with Realtek R8169 only working with IPV6
has caused the Debian Bug report #706499,
regarding Ethernet with Realtek R8169 only working with IPV6
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
706499: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706499
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: firmware-realtek
Version: 0.36+wheezy.1
Severity: normal

Hello,

please refer to this bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611954
and
http://serverfault.com/questions/384165/after-installing-debian-squeeze-ethernet-does-not-come-up

The card only works when you do a manually ifup eth0 with IPV4.
But not every time - sometimes it is simply dead for IPV4.

Here what you see when it comes up:

[   12.096480] uli526x 0000:00:0d.0: eth1: NIC Link is Down
[   12.551617] r8169 0000:02:07.0: eth0: link up
[   12.551821] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   18.235598] Netfilter messages via NETLINK v0.30.
[   22.568023] eth0: no IPv6 routers present
[   24.229825] device eth0 entered promiscuous mode
[  260.098704] device eth0 left promiscuous mode
[ 1222.481295] r8169 0000:02:07.0: eth0: link down
[ 1222.481308] r8169 0000:02:07.0: eth0: link down
[ 1222.481564] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1225.543046] r8169 0000:02:07.0: eth0: link up
[ 1225.543248] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 1235.824012] eth0: no IPv6 routers present

lspci shows:

02:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8169 PCI Gigabit Ethernet Controller (rev 10)
        Subsystem: Realtek Semiconductor Co., Ltd. RTL8169/8110 Family PCI Gigabit Ethernet NIC
        Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 20
        I/O ports at e000 [size=256]
        Memory at fbff9c00 (32-bit, non-prefetchable) [size=256]
        Expansion ROM at fbfc0000 [disabled] [size=128K]
        Capabilities: [dc] Power Management version 2
        Kernel driver in use: r8169

Regards
Karsten


-- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-486
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

firmware-realtek depends on no packages.

firmware-realtek recommends no packages.

Versions of packages firmware-realtek suggests:
ii  initramfs-tools                        0.109.1
ii  linux-image-3.2.0-4-486 [linux-image]  3.2.41-2

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Mon, 2013-05-06 at 09:56 +0200, Karsten Malcher wrote:
[...]
> Afterwards the R8169 card works without problem.

Good.

[...]
> The problem has come like a ghost and gone like a ghost.
> It's hard to say for me but - the bug can be closed.
> This problem is really not reproducible.
> 
> Now i must master my routing problem - maybe the problem will come up
> again ...

I think this was likely some kind of configuration problem all along
(though I don't know what).  If you're not sure whether a problem is a
bug, it would be better to ask first on debian-user@lists.debian.org,
#debian IRC channel or http://ask.debian.net

Ben.

-- 
Ben Hutchings
If God had intended Man to program,
we'd have been born with serial I/O ports.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: