https://bugzilla.novell.com/show_bug.cgi?id=415034
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=415034#c26
--- Comment #26 from Thomas Renninger 2008-09-02 07:39:10 MDT ---
Some workaround ideas:
1) ifup all the network interfaces by another program ealier on 2nd stage
install/setup boot.
Is not nice, because the yast lan module will still be broken stand
alone
2) Wait the same amount as currently if one or more carrier files show 1
-> link detected. It is then expect that:
a) We have something to use for installation -> not that bad if
another
link is not detected. Also cards of the same type should be ready.
b) If no link is detected at all, at least wait 5 secs (should not be
that often).
3) Re-evaluate carrier link after Yast lan is fully started and adjust
things to the user
-> Probably very hard to implement in Yast?
Best would be 2+3, this would be fully satisfactoring, but 3 may not be
possible as Yast could make assumptions displaying things on the result of the
detection?
I am off from discussion. I do not know enough in this area..., just some
ideas.
But it seems, beside that our auto-installation does not work on several
systems, we hit a sever bug here (especially Karsten's power saving assumptions
make me nervous, that would mean that link detection time could take even
longer in cards upcoming in the future if they take more care about power
consumption?)
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.