View previous topic :: View next topic |
Author |
Message |
tux61 n00b
Joined: 25 Dec 2003 Posts: 65 Location: Plérin sur Mer, France
|
Posted: Sun Sep 04, 2005 4:13 pm Post subject: forcedeth problem after upgrade to 2.6.13 |
|
|
Hi,
I encountered a strange problem after an emerge gentoo-sources (2.6.13) :
ifconfig : Code: | Invalid Mac address detected: ff:ff:ff:ff:ff:ff | on eth1 !!!
No problem with eth0. I tried the nvnet driver from nvidia but same problem !
Everything works fine with 2.6.12 kernel.
My config. :
K8N Neo2 Platinum, 1 LAN supports 10/100/1000 Fast Ethernet by Marvell 88E1111 (forcedeth driver) + 1 LAN supports 10/100/1000 Fast Ethernet by Realtek 8110S (r8169 driver).
Any idea ? |
|
Back to top |
|
|
get sirius Guru
Joined: 27 Apr 2002 Posts: 316 Location: Madison, WI
|
Posted: Sun Sep 04, 2005 6:39 pm Post subject: |
|
|
Try a BIOS update. I have a Tyan K8WE, and dmesg told me the same thing. A BIOS update fixed it.
Luck! |
|
Back to top |
|
|
tux61 n00b
Joined: 25 Dec 2003 Posts: 65 Location: Plérin sur Mer, France
|
Posted: Sun Sep 04, 2005 7:43 pm Post subject: |
|
|
Good idea but... I have already the last BIOS from MSI (version 1.A, date 2005-8-16) |
|
Back to top |
|
|
truc Advocate
Joined: 25 Jul 2005 Posts: 3199
|
Posted: Sun Sep 04, 2005 10:07 pm Post subject: |
|
|
sorry, this may be useless but your ff:ff:ff*:ff isn't it an IPv6 address?
do you still have IPv4 address, netmask and so on well configured? |
|
Back to top |
|
|
truc Advocate
Joined: 25 Jul 2005 Posts: 3199
|
Posted: Sun Sep 04, 2005 10:09 pm Post subject: |
|
|
edit: oops
Last edited by truc on Mon Sep 05, 2005 8:57 am; edited 1 time in total |
|
Back to top |
|
|
get sirius Guru
Joined: 27 Apr 2002 Posts: 316 Location: Madison, WI
|
Posted: Sun Sep 04, 2005 11:47 pm Post subject: |
|
|
tux61 wrote: | Good idea but... I have already the last BIOS from MSI (version 1.A, date 2005-8-16) |
Then MSI screwed up with their BIOS settings. It happens, e.g. Tyan had to release a beta BIOS for the K8WE just to fix the very same problem in their previous version Dmesg actually shows the results of the kernel's interactions with the BIOS. |
|
Back to top |
|
|
gschneider Tux's lil' helper
Joined: 10 Apr 2002 Posts: 81 Location: Darmstadt, Germany
|
Posted: Fri Sep 09, 2005 1:10 pm Post subject: |
|
|
I'm having exactly the same problem with my shuttle sn25p.
Kernel 2.6.12-* is working fine, kernel 2.6.13-gentoo is showing:
Quote: | Link encap:UNSPEC HWaddr 00-XX-XX-XX-00-00-XX-XX-00-00-00-00-00-00-00-00 |
There are a little too many groups in that address.
haven't tried the nvnet driver yet.
there is no newer bios yet.
[edit]
tried the nvnet, no difference. _________________ /(bb|[^b]{2})/ |
|
Back to top |
|
|
spielc Guru
Joined: 20 Apr 2004 Posts: 452
|
Posted: Sat Sep 10, 2005 8:05 am Post subject: |
|
|
I learned during my time with gentoo that it is not a wise idea to change the kernel as soon as it comes out. When i changed from the 2.6.11.x to a 2.6.12.x kernel i wasn't able to get alsa-1.0.9b working altho it worked like a charm on the old 2.6.11-kernel. Another funny thing i remarked after the kernel upgrade was, that i when i started my wifi-card it wouldn't shut-down or reboot any more it just hang while trying to shutdown kde (btw. this was fixed and works again now...) but still it's strange that it worked with the old kernel without any problem...
So i just stick to the kernel i have installed for a while before i switch to a new kernel...
Maybe a lil off-topic but still it might be helpful... |
|
Back to top |
|
|
tam Guru
Joined: 04 Mar 2003 Posts: 569
|
Posted: Sat Sep 10, 2005 9:08 am Post subject: |
|
|
Works nice with my Gigabyte GA-K8N Ultra-9 (Bios F3) |
|
Back to top |
|
|
arokh n00b
Joined: 12 Feb 2003 Posts: 33
|
Posted: Mon Sep 19, 2005 12:24 pm Post subject: |
|
|
gschneider wrote: | I'm having exactly the same problem with my shuttle sn25p.
Kernel 2.6.12-* is working fine, kernel 2.6.13-gentoo is showing:
|
I have an SN25P, no such problems here. Running 2.6.13-archck5 which is pretty close to vanilla except for the scheduler. |
|
Back to top |
|
|
|