|
Bugzilla – Full Text Bug Listing |
| Summary: | Network not configured during automatic configuration | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | Holger Sickenberg <holgi> |
| Component: | Installation | Assignee: | Michal Zugec <mzugec> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Blocker | ||
| Priority: | P5 - None | CC: | coolo, forgotten_Si7ddX0wxG, mvidner |
| Version: | Beta 3plus | Flags: | coolo:
SHIP_STOPPER+
|
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Component Test | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
hwinfo.txt
/y2logs.tgz output.txt logs.tgz |
||
|
Description
Holger Sickenberg
2008-05-28 11:12:27 UTC
Created attachment 218558 [details]
hwinfo.txt
Created attachment 218559 [details]
/y2logs.tgz
this sounds like a duplicate of 395079 - for me network setup worked just fine. Hm, here the problem is that output from yast2-hardware reports link status nil, but directly from hwinfo the status is true. And YaST configures first "connected" device (in case no NM is used) Martin? Can you provide output from : echo '`Read(.probe.netcard)'|/usr/lib/YaST2/bin/y2base stdio scr Created attachment 219089 [details]
output.txt
Created attachment 219181 [details]
logs.tgz
eth1 didn't propagate carrier status because link was down (as a workaround - "ip link set eth1 up") *** Bug 396135 has been marked as a duplicate of this bug. *** Hmm, I just marked #396135 as duplicate, but there the problem is that only eth1 is configured and eth0 is not. Maybe not the same problem? fixed in yast2-network-2.16.47 problem description: - before network configuration proposal there is hardware detection - in hardware detection there should modprobe drivers for all network devices when needed and also set link status to up - here is the problem - for "setting link status" there was hardcoded "eth0" *** Bug 395079 has been marked as a duplicate of this bug. *** |