Bug 117775 - Net adapter error, multiple devices detected during boot
Summary: Net adapter error, multiple devices detected during boot
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-03-08 13:39 UTC by Jørgen Nørgaard
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-03-08 15:17:29 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jørgen Nørgaard 2004-03-08 13:39:29 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6)
Gecko/20040207 Firefox/0.8

Description of problem:
I have been using kernels 2.6.1-1.65 to 2.6.3-1.118 and up2date'd to
2.6.3-2.1.242.

After that there is a failure during boot related to ethx.

There is one nic on the machine, yet it seems like 2.6.3-2.1.242 tries
to initialize two, eth0 and eth1. Network does not work afterwards.

NIC: 3com 3c905c-tx/tx-m

Relevant entries from boot.log:

Mar  8 13:52:45 fedora network: Setting network parameters:  succeeded
Mar  8 13:52:45 fedora network: Bringing up loopback interface:  succeeded
Mar  8 13:52:45 fedora ifup: cannot change name of eth1 to eth0: File
exists
Mar  8 13:52:45 fedora ifup:
Mar  8 13:52:45 fedora ifup: cannot parse MAC `2' at argument 2
Mar  8 13:52:45 fedora ifup:
Mar  8 13:52:45 fedora ifup: interface 'eth0' not found
Mar  8 13:52:45 fedora ifup:
Mar  8 13:52:45 fedora ifup: cannot parse MAC `2' at argument 2
Mar  8 13:52:45 fedora ifup: cannot change name of eth1 to eth0: File
exists
Mar  8 13:52:45 fedora ifup: Device eth0 has different MAC address
than expected, ignoring.
Mar  8 13:52:45 fedora ifup:
Mar  8 13:52:45 fedora network: Bringing up interface eth0:  failed




Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. boot my machine
2.
3.
    

Additional info:

Going back to kernel 2.6.3-1.118 restores network

Comment 1 Arjan van de Ven 2004-03-08 13:41:43 UTC
you need newer modutils...

Comment 2 Jørgen Nørgaard 2004-03-08 15:17:29 UTC
OK, new modutils did it.

Thanks.


Note You need to log in before you can comment on or make changes to this bug.