Am 02.05.2013 12:20, schrieb Ben Hutchings:
If you want us, as maintainers, to investigate a bug, you must let us decide what information we need. Please provide
the whole boot log.
On one side you want to have only bug reports with a solution and on the other side you want to be the only one who
decides what information will be given in the bug report without any help from me.
Sorry - that don't fit together.
First i could work with eth0 and installed debian without problems.
After a reboot the problems come up.
Now i use eth1, because eth0 comes not up reliable.
I'm still unclear on what you mean by this. Please provide the output
of 'ip addr' in the case where you consider that eth0 has not come up.
Ben.
O.K. The problem is that this is my server running without keyboard and screen
standing in the basement.
That's the reason why eth must come up reliable to have access.
So it is running with the onboard 100 MB now and the 1000 MB R8169 is not
connected.
For test purposes i can connect an additional network cable to the R8169 and
make the tests you need.
But it seems to be senseless for a closed bug. ;-)
At this time:
# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 00:e0:52:c8:d4:38 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP
qlen 1000
link/ether 00:13:d4:d2:84:32 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.3/24 brd 192.168.1.255 scope global eth1
inet6 fe80::213:d4ff:fed2:8432/64 scope link
valid_lft forever preferred_lft forever
Best regards
Karsten
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51836d7d.8030...@dct.mine.nu
