Bug 150248 - Installation fails to set up network module for load during normal bootup (ISA)
Summary: Installation fails to set up network module for load during normal bootup (ISA)
Status: RESOLVED DUPLICATE of bug 208854
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Installation (show other bugs)
Version: Final
Hardware: x86 SuSE Linux 10.0
: P5 - None : Normal
Target Milestone: ---
Assignee: Michal Zugec
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-12 18:01 UTC by Olof Englund
Modified: 2007-06-08 10:30 UTC (History)
1 user (show)

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

Attachments
YaST logs (465.04 KB, application/x-bzip)
2006-02-14 15:25 UTC, Olof Englund 		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 Olof Englund 2006-02-12 18:01:50 UTC 
The 3COM Etherlink III ISA card is detected during CD-install (if I remember correctly, running the Network-install the 3c509 module must be loaded manually!) but when starting the system after install the 3c509 module DOES NOT LOAD!

This was confirmed on two different systems with Suse 10.0 and all the latest updates.

Fix: Manually add 3c509 to appropriate line in /etc/sysconfig/kernel
Comment 1 Christian Boltz 2006-02-13 20:27:34 UTC 
Please attach the y2logs (/var/log/YaST2/*)
Comment 2 Olof Englund 2006-02-14 15:25:12 UTC 
Created attachment 68390 [details]
YaST logs

I had other problems with Suse on the other machines and had to install Mandriva to get in up and running. I can only post theese logs, hope they are enough.
Comment 3 Olaf Kirch 2006-02-16 11:09:34 UTC 
Why is this assigned to me? This seems to be a problem with yast and/or
the init scripts.
Comment 4 Martin Vidner 2006-08-28 11:52:35 UTC 
Reassigning to the new maintainer of yast2-network.
Comment 5 Michal Zugec 2007-06-08 10:30:25 UTC 
fixed in another report

*** This bug has been marked as a duplicate of bug 208854 ***