Re: [opensuse-factory] Status: M3
Quoting Basil Chupin
On 12/04/12 14:04, Larry Finger wrote: I hope that this is not taken as the go-ahead to release MS #3 because it is doing on the 32-bit system the same as the last build I downloaded did: you need to type "nomodeset" on the kernel boot line before the CD will do anything.
No "nomodeset" and all you get is going around and around in an endless loop of the "system" (a name for want of any other better word right now) of not doing anything and the screen coming up with "No signal".
you DID report that in bugzilla right? If not: why did you expect a solution to it? Don't forget to add information about used graphic chips and other chipsets used... I doubt this is a problem everybody sees... Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 12/04/12 17:09, Dominique Leuenberger a.k.a DimStar wrote:
Quoting Basil Chupin
: On 12/04/12 14:04, Larry Finger wrote: I hope that this is not taken as the go-ahead to release MS #3 because it is doing on the 32-bit system the same as the last build I downloaded did: you need to type "nomodeset" on the kernel boot line before the CD will do anything.
No "nomodeset" and all you get is going around and around in an endless loop of the "system" (a name for want of any other better word right now) of not doing anything and the screen coming up with "No signal".
you DID report that in bugzilla right? If not: why did you expect a solution to it? Don't forget to add information about used graphic chips and other chipsets used...
I doubt this is a problem everybody sees...
Dominique
I have mentioned this fact several times in this list (and one other I think) and there was a bit of a discussion about the use of "nomodeset" - which was deemed by the "experts" to be non sequitur. Re "why did you expect a solution to it?". Apart from what I just said, I don't expect a solution for it as I know now how to handle the situation and with comments from such people as yourself the chances of having the problem resolved fade even further into the distance. But I mention it because there will some bunnies out there who will be incited to try out openSUSE 12.2 Milestone #3 and, once again, have no luck in trying out the Live CD (let alone trying to install it). I know that people who actually have some control over what happens with the openSUSE distribution, such as Andreas, are paying attention to what is being said here and they act on what they read - as right now with Andreas stating that he will release MS #3 simply on what Larry posted. And yet I state something 'opposing' this action and you go into 'damage' mode and question if I submitted a bug report. BC -- There comes a time in the affairs of a man when he has to take the bull by the tail and face the situation. W C Fields -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thursday, April 12, 2012 10:04:23 Basil Chupin wrote:
On 12/04/12 17:09, Dominique Leuenberger a.k.a DimStar wrote:
Quoting Basil Chupin
: On 12/04/12 14:04, Larry Finger wrote: I hope that this is not taken as the go-ahead to release MS #3 because it is doing on the 32-bit system the same as the last build I downloaded did: you need to type "nomodeset" on the kernel boot line before the CD will do anything.
No "nomodeset" and all you get is going around and around in an endless loop of the "system" (a name for want of any other better word right now) of not doing anything and the screen coming up with "No signal".
you DID report that in bugzilla right? If not: why did you expect a solution to it? Don't forget to add information about used graphic chips and other chipsets used...
I doubt this is a problem everybody sees...
Dominique
I have mentioned this fact several times in this list (and one other I think) and there was a bit of a discussion about the use of "nomodeset" - which was deemed by the "experts" to be non sequitur.
Re "why did you expect a solution to it?".
Apart from what I just said, I don't expect a solution for it as I know now how to handle the situation and with comments from such people as yourself the chances of having the problem resolved fade even further into the distance.
But I mention it because there will some bunnies out there who will be incited to try out openSUSE 12.2 Milestone #3 and, once again, have no luck in trying out the Live CD (let alone trying to install it).
That's why it needs to be in bugzilla and on the wiki page with the most annoying bugs.
I know that people who actually have some control over what happens with the openSUSE distribution, such as Andreas, are paying attention to what is being said here and they act on what they read - as right now with Andreas stating that he will release MS #3 simply on what Larry posted.
I said: I'll test myself as well and took's Larry's comments as move some stuff forward and plan on releasing it. I would have released M3 anyway today - with or without LiveCDs. It's good that the LiveCDs boot again. The rest we can fix for M4.
And yet I state something 'opposing' this action and you go into 'damage' mode and question if I submitted a bug report.
Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Basil,
Quoting Basil Chupin
On 12/04/12 17:09, Dominique Leuenberger a.k.a DimStar wrote: I have mentioned this fact several times in this list (and one other I think) and there was a bit of a discussion about the use of "nomodeset" - which was deemed by the "experts" to be non sequitur.
Yet, no bugzilla report... and this is doomed to fall of the shelf! Honestly... The bug list is looked at, the mail archive not so much (the topic is known during the course of 'discussion' and then forgotten and overshadowed by another topic). Bugzilla is not meant as a burden... and yes, I know: some bugs lie there forever... this though should not stop you from reporting them (be it only to tell 'people like me' that there is indeed a bug report!)
Re "why did you expect a solution to it?".
Apart from what I just said, I don't expect a solution for it as I know now how to handle the situation and with comments from such people as yourself the chances of having the problem resolved fade even further into the distance.
I feel honored to get your personal attention. As for the solution: see above ^^ A bug report does not per se give a solution, but it ensures that people doing the fixing will not have to crawl through mailing list archives...
But I mention it because there will some bunnies out there who will be incited to try out openSUSE 12.2 Milestone #3 and, once again, have no luck in trying out the Live CD (let alone trying to install it).
That's very thoughtful of yours... thank you for that. Yet, those 'bunnies' would profit even more from a real fix than from a workaround. Did I mention that having the issue registered in Bugzilla would ensure it not falling it off the radar after 2 days of ML-discussion?
I know that people who actually have some control over what happens with the openSUSE distribution, such as Andreas, are paying attention to what is being said here and they act on what they read - as right now with Andreas stating that he will release MS #3 simply on what Larry posted.
I honestly have the feeling to have a good part of control over the distribution myself... and yes, of course, the 'releaser' will take anything into account he hears.. that's the point of the 'job'. By the way: Bugzilla knows the 'blocker' flag... it's meant to raise full awareness for the 'release process' :)
And yet I state something 'opposing' this action and you go into 'damage' mode and question if I submitted a bug report.
Sorry if you took the question about Bugzilla that bad! It was an honest reminder that only there the things do not get lost (or lets say, 'less lost') than on a mailing list... frankly, if you're fixing stuff and can't just do it on the spot: how often do you go back in the Mailing list to find what else was broken? I'd guess the answer is very close to 0. Hence bugzilla...
BC
DL (don't take offense in the excessive amount of mentioning the word 'Bugzilla' in this mail.. it IS intentional, but not meant offensive). -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
Andreas Jaeger
-
Basil Chupin
-
Dominique Leuenberger a.k.a DimStar