Bug 121853 - Networkcard works only some seconds
Summary: Networkcard works only some seconds
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Final
Hardware: i686 All
: P5 - None : Major
Target Milestone: ---
Assignee: Karsten Keil
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-08 18:09 UTC by Forgotten User xOiK_JGQNy
Modified: 2007-02-16 14:12 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Yast logs (70.44 KB, application/x-gunzip)
2005-12-22 12:40 UTC, Daniel Bauer 		Details
Hardware info from Yast (241.99 KB, text/plain)
2005-12-22 12:41 UTC, Daniel Bauer 		Details
boot.msg (7.32 KB, application/x-gunzip)
2005-12-22 12:42 UTC, Daniel Bauer 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Forgotten User xOiK_JGQNy 2005-10-08 18:09:03 UTC 
I have a 

Davicom 21x4x DEC-Tulip compatible 10/100 Ethernet

nic. In Suse 9.3 it works fine without problems. In Suse 10.0 it works only
during  bootup  (I can ping the machine from another host). But at least when
KDE is up the card is gone.

One difference I can spot is that in 9.3 the dmfe driver is used and in 10.0 the
tulip one.  How can I change the driver for 10.0
Comment 1 Hubert Mantel 2005-10-10 15:39:17 UTC 
Steffen, what is the reason another driver is chosen now?
Comment 2 Steffen Winterfeldt 2005-10-11 08:31:31 UTC 
It's a side effect of bug 105730. tulip and dmfe share pci ids in their 
modinfo data. So it stays random which one is picked until this is resolved 
in the drivers. 
 
You can always change the module manually in /etc/sysconfig/hardware/.
Comment 3 Hubert Mantel 2005-10-19 15:14:25 UTC 
Yes, please use the dmfe driver and things should work.

*** This bug has been marked as a duplicate of 128941 ***
Comment 4 Karsten Keil 2005-11-15 21:54:08 UTC 
to verify IDs.
Comment 5 Karsten Keil 2005-11-15 21:58:16 UTC 
I will try to get the affected IDs removed from tulip drivers, so
please post the PCI IDs of this card here (or verify that it is the same as in bug #128941).
Comment 6 Daniel Bauer 2005-12-22 12:40:49 UTC 
Created attachment 61699 [details]
Yast logs
Comment 7 Daniel Bauer 2005-12-22 12:41:56 UTC 
Created attachment 61700 [details]
Hardware info from Yast
Comment 8 Daniel Bauer 2005-12-22 12:42:36 UTC 
Created attachment 61701 [details]
boot.msg
Comment 9 Daniel Bauer 2005-12-22 12:50:31 UTC 
Hope my attachements helps any further. Had the same problem. Yast install detected the Davicom card as Tulip, therefore there was no network connection (no ping possible). Installed opensuse 10.0 stable via ftp, then a new install from CD 1 (text mode only) and finally again install from CD 1 with option "kde" (standard system, no software collection changes). 
Simply changing the driver from tulip to dmfe in Yast/network cards/hardwaredetails didn't solve the problem. Had to delete the detected card, exit Yast, enter Yast again, add the card again, change "tulip" to "dmfe" in "hardware details", then reboot. 
Now it works, but boot.msg shows that system is waiting for the card, allthough it's defined with fixed ip (no DHCP), and eth0 shows up several times...
Comment 10 Matej Horvath 2007-02-16 14:12:33 UTC 
No reaction on this bug for a long time. Closing as CANTFIX.