wrt this comment, what I have noted on 11.4 is the users who have difficulty are:
- users with AMD RadeonHD find their nominal boot fails from a liveCD (I wrote an AR on this). They need to use the bootcode ‘nomodeset’. This work around is documented in the release notes. The bug ‘crept in’ between openSUSE-11.4 RC1 and RC2 and unfortunately it was not fixed in time for GM version. Later it was determined to be a problem in building the liveCD (a couple of rpms or modules not present with initrd (?) run for liveCD creation - I don’t know exact technical details). In one of the follow-on bug reports it was queried if this bug was sufficient to require a new openSUSE-11.4 liveCD and the answer provided by SuSE-GmbH packagers was not. It is handled by release notes. The problem is NOT in the DVD. Its only the liveCD boot that has it, and both ‘nomodeset’ and ‘failsafe’ work.
- various Intel hardware users have a problem with a nominal boot. In almost every case (but not all cases) a fail safe boot , using the FVDEV driver works.
- a small number of nVidia hardware users find they need to use failsafe (forces FBDEV driver) or ‘nomodeset’ boot (forces ‘nv’ driver) to boot the liveCD and DVD. Again, there are typically work arounds for tuning.
- a very small number of HP users have problems that the boot CD won’t even get to gurb.
In most cases there are work arounds, but no automatic boot solutions without massive and complex code insertion that would likely cause other problems in reliability.
The above are only a very small % of the PC users.
And in most cases, the problems are not openSUSE specific but they are Linux wide.
A lot of the current graphics hiccups are a direct result of the Linux community moving from using the classic /etc/X11/xorg.conf config file, to instead using an automatic X configuration from xorg. And also from KMS being enabled to improve the automatic hardware detection. However xorg’s automatic hardware identification, and automatic driver selection, is not perfect.
openSUSE is not the only distribution bit by this. Most other distributions are also bit by such problems. Dependant on the distribution, some hardware will initially work better than others.
Now reference terminology, in the 9.x and earlier days, the name SuSE was used. From 10.x and later, it was decided to make the old SuSE more open source, and remove the proprietary code that was inside. This was significant ! Most users simply did not understand how significant this was. To attempt to illustrate how important and signficant that was, then along with that fundamental change in SuSE, the name of the distribution was changed from SuSE to openSUSE. As to why they used the English word “open” instead of a German name for “open” is not something I know about, but I suspect the view was the English name would be more widely accepted if they did that.
When one says Suse or Suzzy or Suzie it is massively confusing, because there is no idea as to exactly what one is talking about. One could be refering to 9.x and earlier version of SuSE. One could be refering to current versions of SLED (SuSE Linux Enterprise Desktop) or SLES (SuSE Linux Enterprise Server) or one could be simply completely misusing the term to describe openSUSE.
It is simply not clear, and there is no reason for being unclear.
And if one person starts being unclear, it leads others to be unclear, and then we have total confusion. So lets avoid that.
I see no evidence of that. Just the contrary. Perhaps you can show your reference for that? If all your logic is built on statements such as that, then IMHO it does not provide support for the rest of your views. …
Anyway, thankyou for the suggestions, but as I noted, we need contributers with specifics, and not general non-specific suggestions. One needs to note the exact hardware with problems. One needs to differentiate those having problems because of basic fundamental misunderstandings in the users, to those having problems because of problems with the distribution. General statements do not provide that differentiation.
Also, something I should have stated earlier, note that our opensUSE forum is full of volunteers who support openSUSE, but who have no extra influence on the packaging of openSUSE. Those of us on the forum are NOT SuSE-GmbH nor Novell employees. The SuSE-GmbH developers and SuSE-GmbH packagers for openSUSE do NOT visit the forum. They do not. I hope that is clear. They do not. Those developers and packagers exchange their information via mailing lists and via IRC chat channels. There is guidance here as to how one can connect to those communcation media: openSUSE:Communication channels - openSUSE
So IF one wishes to raise such an issue with the developers, then this forum is not the place.