FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian User

 
 
LinkBack Thread Tools
 
Old 02-09-2008, 08:58 AM
Tero Mäntyvaara
 
Default Gigabyte M61P-S3 and wild MAC address of ethernet interface

Hi,

I have got Debian 4.0r2 and Gigabyte M61P-S3 motherboard and I noticed
it has "dynamic" MAC address :-/


I tried to fix the problem with the help of document
http://www.debian-administration.org/articles/501 but with no success.
The problem is that every time I boot my system Debian finds the new
ethernet interface and so I do not have internet connection.


Has someone else had similar problem and so also sollution?


Tero Mäntyvaara


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 02-10-2008, 02:44 PM
Florian Kulzer
 
Default Gigabyte M61P-S3 and wild MAC address of ethernet interface

On Sat, Feb 09, 2008 at 11:58:38 +0200, Tero Mäntyvaara wrote:
> Hi,
>
> I have got Debian 4.0r2 and Gigabyte M61P-S3 motherboard and I noticed
> it has "dynamic" MAC address :-/
>
> I tried to fix the problem with the help of document
> http://www.debian-administration.org/articles/501 but with no success.
> The problem is that every time I boot my system Debian finds the new
> ethernet interface and so I do not have internet connection.
>
> Has someone else had similar problem and so also sollution?

I am not familiar with this problem, so I cannot promise anything, but I
think it will help if you post some more information about your system.
Let's start with the output of the following commands:

lspci -nn | grep -i net

dmesg | egrep -i 'mac|eth'

/sbin/ifconfig

cat /etc/udev/rules.d/z25_persistent-net.rules

cat /etc/network/interfaces

--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |
 
Old 02-10-2008, 04:27 PM
Tero Mäntyvaara
 
Default Gigabyte M61P-S3 and wild MAC address of ethernet interface

Hi,

Many thanks for your answer! :-) Here is the information you requested:

# lspci -nn | grep -i net
00:07.0 Bridge [0680]: nVidia Corporation MCP61 Ethernet [10de:03ef]
(rev a2)

# dmesg | egrep -i 'mac|eth'
ACPI: PCI Interrupt Link [LMAC] (IRQs 5 7 9 10 *11 14 15)
forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.56.
forcedeth: using HIGHDMA
0000:00:07.0: Invalid Mac address detected: 3f:3d:75:4d:1a:00
Please complain to your hardware vendor. Switching to a random MAC.
eth0: forcedeth.c: subsystem: 01458:e000 bound to 0000:00:07.0
eth1394: eth0: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0)
eth6: no IPv6 routers present

# /sbin/ifconfig
eth6 Link encap:Ethernet HWaddr 00:00:6C:B1:C1:64
inet addr:10.11.12.12 Bcast:10.11.12.255 Mask:255.255.255.0
inet6 addr: fe80::200:6cff:feb1:c164/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5656 errors:0 dropped:0 overruns:0 frame:0
TX packets:3957 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2779018 (2.6 MiB) TX bytes:450604 (440.0 KiB)
Interrupt:201 Base address:0xe000

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:257 errors:0 dropped:0 overruns:0 frame:0
TX packets:257 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:20036 (19.5 KiB) TX bytes:20036 (19.5 KiB)

# cat /etc/udev/rules.d/z25_persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, probably run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single line.
# MAC addresses must be written in lowercase.

# Firewire device 001a4d0000e18fd8 (ohci1394)
SUBSYSTEM=="net", DRIVERS=="?*",
ATTRS{address}=="00:1a:4d:00:00:e1:8f:d8", NAME="eth0"

# PCI device 0x10de:0x03ef (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:44:27:b6",
NAME="eth1"

# PCI device 0x10de:0x03ef (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:af:3b:bd",
NAME="eth2"

# PCI device 0x10de:0x03ef (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:81:6e:05",
NAME="eth3"

# PCI device 0x10de:0x03ef (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:51:2c:f2",
NAME="eth4"

# PCI device 0x10de:0x03ef (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:1e:81:f6",
NAME="eth5"

# PCI device 0x10de:0x03ef (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:b1:c1:64",
NAME="eth6"

# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth1
iface eth1 inet dhcp

Additional information:
The problem is that OS thinks that the MAC address is invalid some how.
I verfied that OS informs at every boot that MAC address is invalid. I
was wondering if this is result of incorrectly programmed Ethernet
physical controller MAC address? My PHY-controller is Realtek RTL8211.


Tero Mäntyvaara

Florian Kulzer wrote:

On Sat, Feb 09, 2008 at 11:58:38 +0200, Tero Mäntyvaara wrote:


Hi,

I have got Debian 4.0r2 and Gigabyte M61P-S3 motherboard and I noticed
it has "dynamic" MAC address :-/


I tried to fix the problem with the help of document
http://www.debian-administration.org/articles/501 but with no success.
The problem is that every time I boot my system Debian finds the new
ethernet interface and so I do not have internet connection.


Has someone else had similar problem and so also sollution?



I am not familiar with this problem, so I cannot promise anything, but I
think it will help if you post some more information about your system.
Let's start with the output of the following commands:

lspci -nn | grep -i net

dmesg | egrep -i 'mac|eth'

/sbin/ifconfig

cat /etc/udev/rules.d/z25_persistent-net.rules

cat /etc/network/interfaces





--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 02-10-2008, 07:24 PM
Florian Kulzer
 
Default Gigabyte M61P-S3 and wild MAC address of ethernet interface

On Sun, Feb 10, 2008 at 19:27:23 +0200, Tero Mäntyvaara wrote:
> Florian Kulzer wrote:
>> On Sat, Feb 09, 2008 at 11:58:38 +0200, Tero Mäntyvaara wrote:
>>> I have got Debian 4.0r2 and Gigabyte M61P-S3 motherboard and I
>>> noticed it has "dynamic" MAC address :-/
>>>
>>> I tried to fix the problem with the help of document
>>> http://www.debian-administration.org/articles/501 but with no
>>> success. The problem is that every time I boot my system Debian
>>> finds the new ethernet interface and so I do not have internet
>>> connection.

[...]

> Many thanks for your answer! :-) Here is the information you requested:
>
> # lspci -nn | grep -i net
> 00:07.0 Bridge [0680]: nVidia Corporation MCP61 Ethernet [10de:03ef] (rev a2)
>
> # dmesg | egrep -i 'mac|eth'
> ACPI: PCI Interrupt Link [LMAC] (IRQs 5 7 9 10 *11 14 15)
> forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.56.
> forcedeth: using HIGHDMA
> 0000:00:07.0: Invalid Mac address detected: 3f:3d:75:4d:1a:00
> Please complain to your hardware vendor. Switching to a random MAC.
> eth0: forcedeth.c: subsystem: 01458:e000 bound to 0000:00:07.0
> eth1394: eth0: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0)
> eth6: no IPv6 routers present
>
> # /sbin/ifconfig
> eth6 Link encap:Ethernet HWaddr 00:00:6C:B1:C1:64
> inet addr:10.11.12.12 Bcast:10.11.12.255 Mask:255.255.255.0

[...]

> # cat /etc/udev/rules.d/z25_persistent-net.rules
> # This file was automatically generated by the /lib/udev/write_net_rules
> # program, probably run by the persistent-net-generator.rules rules file.
> #
> # You can modify it, as long as you keep each rule on a single line.
> # MAC addresses must be written in lowercase.
>
> # Firewire device 001a4d0000e18fd8 (ohci1394)
> SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1a:4d:00:00:e1:8f:d8", NAME="eth0"
>
> # PCI device 0x10de:0x03ef (forcedeth)
> SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:44:27:b6", NAME="eth1"

[ snip: Udev dutifully adds a rule at every reboot because it thinks
that each semi-random 00:00:6c:* MAC address corresponds to a new
device. Right now we are at eth6. ]

> # PCI device 0x10de:0x03ef (forcedeth)
> SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:b1:c1:64", NAME="eth6"
>
> # cat /etc/network/interfaces
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
>
> # The loopback network interface
> auto lo
> iface lo inet loopback
>
> # The primary network interface
> allow-hotplug eth1
> iface eth1 inet dhcp
>
> Additional information:
> The problem is that OS thinks that the MAC address is invalid some how.
> I verfied that OS informs at every boot that MAC address is invalid. I
> was wondering if this is result of incorrectly programmed Ethernet
> physical controller MAC address? My PHY-controller is Realtek RTL8211.

I would try this: Edit /etc/udev/rules.d/z25_persistent-net.rules so
that it looks like this (not including the "-----" delimiter lines):

------------------------------------------------------------------------
# This file was automatically generated by the /lib/udev/write_net_rules
# program, probably run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single line.
# MAC addresses must be written in lowercase.

# Firewire device 001a4d0000e18fd8 (ohci1394)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1a:4d:00:00:e1:8f:d8", NAME="firewire"

# PCI device 0x10de:0x03ef (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:*", NAME="eth0"
------------------------------------------------------------------------

Watch out if your email client wraps long lines: There should be exactly
two rules (the rest of the lines are comments); each rule starts with
"SUBSYSTEM==...", ends with "NAME=...", and has to be written in one
line.

The idea here is to a) make sure that the firewire device does not
interfere with the assignment of eth* names, and b) use the "*" wildcard
so that udev recognizes all the possible MAC addresses of the MCP61 as
being the same device. (If I understand forcedeth.c correctly, it always
picks a MAC address starting with 00:00:6c; only the last three bytes
are chosen randomly.)

To be on the safe side, I would furthermore use the trick from the
debian-administration article to make sure that this computer always
presents the same MAC address to the rest of the network. Therefore I
would change the stanza for the primary network interface in
/etc/network/interfaces to refer to eth0 and add one line to make one of
the valid 00:00:6c:* MAC addresses stick (leave the loopback device
stanza as it is):

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp
hwaddress ether 00:00:6c:b1:c1:64

Then you can reboot and keep your fingers crossed.

--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |
 
Old 02-10-2008, 09:31 PM
Tero Mäntyvaara
 
Default Gigabyte M61P-S3 and wild MAC address of ethernet interface

Problem solved! :-D

Thank you for your help.

I am still wondering why this kind of problem is possible. Is the
problem the hardware, the driver or the kernel? Or is it just the
"property" that I am not aware of?



Tero Mäntyvaara

Florian Kulzer wrote:

On Sun, Feb 10, 2008 at 19:27:23 +0200, Tero Mäntyvaara wrote:


Florian Kulzer wrote:


On Sat, Feb 09, 2008 at 11:58:38 +0200, Tero Mäntyvaara wrote:

I have got Debian 4.0r2 and Gigabyte M61P-S3 motherboard and I
noticed it has "dynamic" MAC address :-/


I tried to fix the problem with the help of document
http://www.debian-administration.org/articles/501 but with no
success. The problem is that every time I boot my system Debian
finds the new ethernet interface and so I do not have internet
connection.



[...]



Many thanks for your answer! :-) Here is the information you requested:

# lspci -nn | grep -i net
00:07.0 Bridge [0680]: nVidia Corporation MCP61 Ethernet [10de:03ef] (rev a2)

# dmesg | egrep -i 'mac|eth'
ACPI: PCI Interrupt Link [LMAC] (IRQs 5 7 9 10 *11 14 15)
forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.56.
forcedeth: using HIGHDMA
0000:00:07.0: Invalid Mac address detected: 3f:3d:75:4d:1a:00
Please complain to your hardware vendor. Switching to a random MAC.
eth0: forcedeth.c: subsystem: 01458:e000 bound to 0000:00:07.0
eth1394: eth0: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0)
eth6: no IPv6 routers present

# /sbin/ifconfig
eth6 Link encap:Ethernet HWaddr 00:00:6C:B1:C1:64
inet addr:10.11.12.12 Bcast:10.11.12.255 Mask:255.255.255.0



[...]



# cat /etc/udev/rules.d/z25_persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, probably run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single line.
# MAC addresses must be written in lowercase.

# Firewire device 001a4d0000e18fd8 (ohci1394)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1a:4d:00:00:e1:8f:d8", NAME="eth0"

# PCI device 0x10de:0x03ef (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:44:27:b6", NAME="eth1"



[ snip: Udev dutifully adds a rule at every reboot because it thinks
that each semi-random 00:00:6c:* MAC address corresponds to a new
device. Right now we are at eth6. ]



# PCI device 0x10de:0x03ef (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:b1:c1:64", NAME="eth6"

# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth1
iface eth1 inet dhcp

Additional information:
The problem is that OS thinks that the MAC address is invalid some how.
I verfied that OS informs at every boot that MAC address is invalid. I
was wondering if this is result of incorrectly programmed Ethernet
physical controller MAC address? My PHY-controller is Realtek RTL8211.



I would try this: Edit /etc/udev/rules.d/z25_persistent-net.rules so
that it looks like this (not including the "-----" delimiter lines):

------------------------------------------------------------------------
# This file was automatically generated by the /lib/udev/write_net_rules
# program, probably run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single line.
# MAC addresses must be written in lowercase.

# Firewire device 001a4d0000e18fd8 (ohci1394)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1a:4d:00:00:e1:8f:d8", NAME="firewire"

# PCI device 0x10de:0x03ef (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:*", NAME="eth0"
------------------------------------------------------------------------

Watch out if your email client wraps long lines: There should be exactly
two rules (the rest of the lines are comments); each rule starts with
"SUBSYSTEM==...", ends with "NAME=...", and has to be written in one
line.

The idea here is to a) make sure that the firewire device does not
interfere with the assignment of eth* names, and b) use the "*" wildcard
so that udev recognizes all the possible MAC addresses of the MCP61 as
being the same device. (If I understand forcedeth.c correctly, it always
picks a MAC address starting with 00:00:6c; only the last three bytes
are chosen randomly.)

To be on the safe side, I would furthermore use the trick from the
debian-administration article to make sure that this computer always
presents the same MAC address to the rest of the network. Therefore I
would change the stanza for the primary network interface in
/etc/network/interfaces to refer to eth0 and add one line to make one of
the valid 00:00:6c:* MAC addresses stick (leave the loopback device
stanza as it is):

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp
hwaddress ether 00:00:6c:b1:c1:64

Then you can reboot and keep your fingers crossed.





--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 02-11-2008, 12:55 AM
David Parker
 
Default Gigabyte M61P-S3 and wild MAC address of ethernet interface

> Problem solved! :-D
>
> Thank you for your help.
>
> I am still wondering why this kind of problem is possible. Is
> the
> problem the hardware, the driver or the kernel? Or is it just
> the
> "property" that I am not aware of?
>
>
> Tero Mäntyvaara
>

Hello,

I have this exact same motherboard, and I experienced this same problem. As I understand it (through several Google searches), the main cause of the problem is that the onboard Nvidia NIC is not supported correctly by the forcedeth driver in Etch. Basically, the driver isn't able to correctly query the NIC for the MAC address. Because it's not able to get a real MAC address from NIC, it assigns a random one instead, which causes some bizarre behavior. The specific problem that I was having was that the device number of the NIC would change each time I rebooted (since the MAC address was different), so it was eth0, then eth1, then eth2, etc.

Another person also had problems with this NIC and the forcedeth driver. That post is here:

http://lists.debian.org/debian-user/2007/10/msg02402.html

Hope this helps.

- Dave
 

Thread Tools




All times are GMT. The time now is 03:18 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org