On Tue,09.Feb.10, 23:06:08, Stan Hoeppner wrote:
Andrei Popescu put forth on 2/9/2010 3:37 AM:
On Mon,08.Feb.10, 16:33:39, Stan Hoeppner wrote:
So, are you saying it didn't happen? Couldn't have happened? Shouldn't
have
happened? I'm imagining things? Are you kidding?
No,
On Wed, Feb 10, 2010 at 10:46:08AM +0200, Andrei Popescu wrote:
On Tue,09.Feb.10, 23:06:08, Stan Hoeppner wrote:
Andrei Popescu put forth on 2/9/2010 3:37 AM:
On Mon,08.Feb.10, 16:33:39, Stan Hoeppner wrote:
[snip]
I don't know anything about these scripts. When do they run? And are
In 20100210084608.gu14...@think.homelan, Andrei Popescu wrote:
On Tue,09.Feb.10, 23:06:08, Stan Hoeppner wrote:
I don't know anything about these scripts. When do they run?
Udev is a daemon, started fairly early in the boot process. It communicates
with the kernel. It evaluates the rules
On Mon,08.Feb.10, 16:33:39, Stan Hoeppner wrote:
So, are you saying it didn't happen? Couldn't have happened? Shouldn't have
happened? I'm imagining things? Are you kidding?
No, I'm saying that under normal circumstances it should work.
It broke. I fixed it by manually editing the
On Mon,08.Feb.10, 20:07:36, Frank Miles wrote:
I won't belabor this.
Putting in a different NIC fixed things. No fuss, though interesting that it
(presumably udev) wanted to call it eth2. I can live with that.
Of course it did, eth0 and eth1 were already taken ;)
Regards,
Andrei
--
Andrei Popescu put forth on 2/9/2010 3:37 AM:
On Mon,08.Feb.10, 16:33:39, Stan Hoeppner wrote:
So, are you saying it didn't happen? Couldn't have happened? Shouldn't have
happened? I'm imagining things? Are you kidding?
No, I'm saying that under normal circumstances it should work.
Thanks so much to Stan, Tom H, and Cameleon!
It seems that the consensus is that it's a NIC problem. In case
it wasn't previously clear, the RealTek 8169 is part of the Gigabyte
motherboard.
I thought that I'd escaped non-free-firmware hell by getting a MB
with the graphics based on an Intel
Frank Miles put forth on 2/8/2010 10:32 AM:
Thanks so much to Stan, Tom H, and Cameleon!
It seems that the consensus is that it's a NIC problem. In case
it wasn't previously clear, the RealTek 8169 is part of the Gigabyte
motherboard.
I thought that I'd escaped non-free-firmware hell by
On Mon,08.Feb.10, 01:15:43, Stan Hoeppner wrote:
Perhaps the kernel brings eth1 into existence by first establishing it as
eth0, then renaming it to eth1; then bringing the real eth0 into
existence.
The above can happen when you add NICs to the system. I hate UDEV for this,
and
it
Andrei Popescu put forth on 2/8/2010 2:29 PM:
On Mon,08.Feb.10, 01:15:43, Stan Hoeppner wrote:
Perhaps the kernel brings eth1 into existence by first establishing it as
eth0, then renaming it to eth1; then bringing the real eth0 into
existence.
The above can happen when you add NICs to
I won't belabor this.
Putting in a different NIC fixed things. No fuss, though interesting that it
(presumably udev) wanted to call it eth2. I can live with that.
Thanks again, everyone!
-Frank
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of
I am in the final throes of getting a new system running (Debian/squeeze).
For the past 2 weeks it's had just eth0, and the network has worked fine.
Now I want this system to have two network interfaces - the original eth0,
and eth1 to a DSL modem, just like its precessor system.
The strange
On Sun, 07 Feb 2010 07:07:03 -0800, Frank Miles wrote:
(...)
There is one troubling line in the logs from boot:
udev: renamed network interface eth0 to eth1
Doing an ifdown eth1 does not fix the eth0 problem.
Mmm... check your /etc/udev/rules.d/70-persistent-net.rules, there
should be
Thanks, Camaleon (sorry - don't know how to generate the proper characters).
That file includes:
# PCI device 0x10ec:0x8168 (r8169)
SUBSYSTEM==net, ACTION==add, DRIVERS==?*, ATTR{address}==xx:xx:xx:xx:xx:xx, ATTR{dev_id}==0x0,
ATTR{type}==1, KERNEL==eth*, NAME=eth0
# PCI device 0x10b7:0x9050
On Sun, 07 Feb 2010 10:41:46 -0800, Frank Miles wrote:
Thanks, Camaleon (sorry - don't know how to generate the proper
characters).
Still us-ascii? ;-) No problem.
That file includes:
# PCI device 0x10ec:0x8168 (r8169)
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
[snip]
I fail to see what it's doing, but I cannot see any reference to eth1,
it's like only one interace is being recognized :-?
What is the output of dmesg | grep eth?
[6.317161] eth1: RTL8168d/8111d at 0xc9c4e000, xx:xx:xx:xx:xx:xx,
XID 083000c0 IRQ 32
[6.384830] eth1:
That file includes:
# PCI device 0x10ec:0x8168 (r8169)
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
ATTR{address}==xx:xx:xx:xx:xx:xx, ATTR{dev_id}==0x0, ATTR{type}==1,
KERNEL==eth*, NAME=eth0
# PCI device 0x10b7:0x9050 (3c59x)
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
On Sun, 07 Feb 2010 13:36:13 -0800, Frank Miles wrote:
[snip]
I fail to see what it's doing, but I cannot see any reference to eth1,
it's like only one interace is being recognized :-?
What is the output of dmesg | grep eth?
[6.317161] eth1: RTL8168d/8111d at
I made a minor effort earlier to suppress the IPv6 modules, but [a] didn't
succeed
Add
ipv6.disable=1
to the grub kernel/linux line to disable ipv6 (without recompiling the kernel)
but it cannot be the problem.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject
On Sun, 07 Feb 2010 13:36:13 -0800, Frank Miles wrote:
[snip]
I fail to see what it's doing, but I cannot see any reference to eth1,
it's like only one interace is being recognized :-?
What is the output of dmesg | grep eth?
[6.317161] eth1: RTL8168d/8111d at
[ 6.317161] eth1: RTL8168d/8111d at 0xc9c4e000,xx:xx:xx:xx:xx:xx,
XID 083000c0 IRQ 32
[ 6.384830] eth1: unable to apply firmware patch
[ 7.190453] udev: renamed network interface eth1 to eth0
[ 7.229390] udev: renamed network interface eth0_rename to eth1
[ 11.276999]
... ok, started...
[snip]
I fail to see what it's doing, but I cannot see any reference to eth1,
it's like only one interace is being recognized :-?
What is the output of dmesg | grep eth?
[6.317161] eth1: RTL8168d/8111d at 0xc9c4e000,xx:xx:xx:xx:xx:xx, XID 083000c0 IRQ 32
[
Hi Frank, sorry you're going through such pains here. Did the same myself not
long ago.
Frank Miles put forth on 2/7/2010 12:41 PM:
Feb 7 04:51:22 puffin kernel: [6.156559] r8169 Gigabit Ethernet
driver 2.3LK-NAPI loaded
Feb 7 04:51:22 puffin kernel: [6.156573] r8169 :02:00.0:
23 matches
Mail list logo
