https://bugzilla.novell.com/show_bug.cgi?id=779400 https://bugzilla.novell.com/show_bug.cgi?id=779400#c kk zhang <kkzhang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kkzhang@suse.com AssignedTo|bnc-team-screening@forge.pr |hmacht@suse.com |ovo.novell.com | -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=779400 https://bugzilla.novell.com/show_bug.cgi?id=779400#c2 Maciej Pilichowski <bluedzins@wp.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|bluedzins@wp.pl | --- Comment #2 from Maciej Pilichowski <bluedzins@wp.pl> 2012-09-10 12:50:33 UTC --- I couldn't wait, so I solved this by myself -- I added nvidia repo and installed appropriate driver for my nvidia card (i.e. the one built-in MBP). If the log of fixed manually system is any worth to you, please let me know, and I will attach it. This bug is the result of the avalanche of installer flaws -- in the end user has to fix them manually. Some things could be done though -- for example: adding nvidia repo (url) for computers with nvidia card, disabling suspend initially, triggering install on first successful network connection + enabling back suspend. With or without drivers, the state of the system should be functional. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=779400 https://bugzilla.novell.com/show_bug.cgi?id=779400#c4 --- Comment #4 from Maciej Pilichowski <bluedzins@wp.pl> 2012-09-10 17:14:04 UTC ---

Which driver did you have installed with 12.1?

The one that works, and you know about it. Nvidia one (from Nvidia repo).

I mean, is this a regression or not?

In terms of upgrade -- I don't know, this was the first update for me (on MBP). ------------------------------------------------------------------------------ Bottom line is this -- I had working system, upgrade turned it into NON-working system. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=779400 https://bugzilla.novell.com/show_bug.cgi?id=779400#c6 Gabriele Mohr <gs@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |gs@suse.com InfoProvider| |bluedzins@wp.pl --- Comment #6 from Gabriele Mohr <gs@suse.com> 2012-09-27 07:31:26 UTC --- Do you use YaST or 'zypper' for upgrade? Please attach the YaST and zypper log files, see http://en.opensuse.org/openSUSE:Report_a_YaST_bug. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=779400 https://bugzilla.novell.com/show_bug.cgi?id=779400#c Gabriele Mohr <gs@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |jsuchome@suse.com -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=779400 https://bugzilla.novell.com/show_bug.cgi?id=779400#c9 Maciej Pilichowski <bluedzins@wp.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|bluedzins@wp.pl | --- Comment #9 from Maciej Pilichowski <bluedzins@wp.pl> 2012-09-27 13:53:11 UTC ---

YaST does not automatically upgrade proprietary repos with newer versions.

I understand that.

But I assume you had an option to edit it manualy during the upgrade, right?

Sure. It works in the infinite loop currently. Repos are deleted, because I have no network. I have no network, because I don't have drivers. And I have no drivers because none are used, and the repos are deleted.

So does it help when you install latest drivers from updated NVidia repo?

Of course. But this is not a solution. ============================================================================ Now I am writing this more a suggestion, let's states the fact. It is technically possible to upgrade the system so the transition would be from working to working system. It can be done in various ways, becase one can think more automated or more user-based way. Let's consider this: a) support for http://someplace.com/$VERSION repo URL encoding -- reported, no progress at all towards this solution b) installation media for version X based on version X-1, however recognized as X c) caching packaged for post-install installation Now the upgrade will be always connected thanks to (b), it could fetch propriety drivers (c) from valid repos (a), after install it would install them (c) and user will be happy. Another path is possible -- boot from DVD and then just switch the already system to upgrade mode, then restart and boot the installed system and upgrade from it -- it will cover the issue with no network. Yet another path is possible -- gathering all problems and then notifying user at the end, that X and Y driver was removed, and she/he should install them again. However please note the numbers and just the line of 11.x and 12.x series -- 11.0, 11.1, 11.2, 11.3, 11.4, 12.0, 12.1, 12.2. 8 upgrades only for 2 series, and EIGHT times user would have to install and install again those drivers, despite the fact he/she already added valid repos and had valid drivers. So it would seem OS is against user will. I opt for fully automatic solving this issue, especially considering the fact (a) for example is not very demanding. To sum this up -- this bug I described here is the result of ignoring small flaws which at the end resulted in broken upgrade. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=779400 https://bugzilla.novell.com/show_bug.cgi?id=779400#c11 --- Comment #11 from Maciej Pilichowski <bluedzins@wp.pl> 2012-09-27 14:32:32 UTC ---

We could not know the naming of proprietary repository URLs, so we cannot offer any automatism here.

But users do know the naming pattern. And you refuse the users would take advantage of it. The problem lies Yast do not provide enough support for fully working upgrade.

When you need to use them, you should care youreself that they are available after upgrade.

I did it even during upgrade, but they were deleted (by Yast).

Once you have network access, you enable them and install what you need to.

And how I should access network when the net driver is deleted as well? Currently you either have to have two computers, or know in advance what installer will do, just in order to fix one computer. This is pretty steep requirement. I am just stating here the facts. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=779400 https://bugzilla.novell.com/show_bug.cgi?id=779400#c13 --- Comment #13 from Maciej Pilichowski <bluedzins@wp.pl> 2012-09-27 16:01:07 UTC ---

So you edited the URL during upgrade, but the repo still got deleted?

Yep. This is another bug (reported) -- if user keep any repo active, and there is not network connection the repo will be deleted. In order to keep repo, you have to disable it, otherwise it won't survive upgrade. (On my second upgrade, I exactly did it -- they survived).

I can see that this bug report is about suspend/resume

Yes, indeed. But I think if you want to focus solely on this report and only this you are limited only to notifying user that the working driver is deleted, and she/he should install the deleted driver again to gain full capabilities. I think it is a minimum, some progress at least. Because this problem is dependent on the other problems with upgrade -- I cannot tell how far you are willing to go with it. More far -- more other reports are involved. Of course as user I would be very happy to see nice automatic fully operational upgrade, considering the fact I am suse user for a long time (since 7.0).

Where did you write you have problems with network drivers?

Also reported: https://bugzilla.novell.com/show_bug.cgi?id=779398 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=779400 https://bugzilla.novell.com/show_bug.cgi?id=779400#c15 Maciej Pilichowski <bluedzins@wp.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|bluedzins@wp.pl | --- Comment #15 from Maciej Pilichowski <bluedzins@wp.pl> 2012-10-02 18:03:30 UTC ---

During upgrade, YaST

I completely disagree with you -- however this is not the report to discuss this issue. =========================================================================

I do not see a way how to inform user that some "working" drivers have been deleted and "not working" are being installed.

Because it was reported and it is reported that the drivers on the DVD do not work. Period. If you start pretending they are OK, and should work, in such case lets change this report into non-working drivers delivered on DVD. It is fine with me. I don't how how you would like to tackle this problem, but the bottom line is there is a problem -- upgrade turns fully working computer into non-working one. For user part, I can attach whatever you want to computer, it won't change situation a bit.

The installer could not know which drivers (or kernel itself) fits your hardware best.

Installer is not a living being, it is designed and created by developers. Whatever knowledge you put there, it will know. Like for example address of Nvidia repo, like for example the fact drivers on DVD are broken, and so on. The more knowledge you put into installer, the better. So the question is -- do you know DVD contains broken driver? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=779400 https://bugzilla.novell.com/show_bug.cgi?id=779400#c Jeff Mahoney <jeffm@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel-maintainers@forge.pr |eich@suse.com |ovo.novell.com | -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=779400 https://bugzilla.novell.com/show_bug.cgi?id=779400#c Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |ASSIGNED -- 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.