Imagine there are Test versions ....

[Akoellh]

Originally Posted by caf4926

Maybe worth a try for your issues?

Nope, as I already reported this issue and why this behavior occurs including a workaround (on x86_64 the default kernel is affected as well).

It is not a classic "bug" but an intended change in kernel configuration, so one has to do some argumentation, why it should be considered a bug (not for the first time, the last issue I reported was reverted a few weeks later), but with this one, obviously my points were not valid enough.

caf4926 wrote:
> Going on my current use of 11.2 RC2
> It's virtually bug free.

it is a wonder that you miss them all, i say because "This [bug] list
is too long for Bugzilla's little mind ... 1563 bugs found" cite:
<https://bugzilla.novell.com/buglist.cgi?query_format=advanced&short_desc_type= allwordssubstr&short_desc=&classification=openSUSE &product=openSUSE+11.2&long_desc_type=substring&lo ng_desc=&bug_file_loc_type=allwordssubstr&bug_file _loc=&status_whiteboard_type=allwordssubstr&status _whiteboard=&keywords_type=anywords&keywords=&bug_ status=NEW&bug_status=ASSIGNED&bug_status=NEEDINFO &bug_status=REOPENED&emailassigned_to1=1&emailtype 1=substring&email1=&emailassigned_to2=1&emailrepor ter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=su bstring&email2=&bugidtype=include&bug_id=&votes=&c hfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=do it&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=>

--
palladium
Have a lot of fun..

[caf4926]

@palladium
You know only too well that everyone's experience will be different. Hence I said 'My current use'.

[Akoellh]

Originally Posted by Akoellh

B) Switch from NetworkManager to IFUP, configure your user to allowing him access via kinternet/cinternet and try to configure any ethernet interface (wired or wireless) via one of those frontends.

=> You can not connect to smpppd not even as root with kinternet/cinternet(/or qinternet), there are no ethernet interfaces visible.

Fixed with latest update of smpppd.

P.S.

Permission problem with sr0 -NEEDS URGENT FIXING - openSUSE Forums

=> http://nctritech.files.wordpress.com...pip_punch1.jpg

[hcvv]

Originally Posted by Akoellh

P.S.

Permission problem with sr0 -NEEDS URGENT FIXING - openSUSE Forums

I saw this post and it is shows your point to advantage.

Swerdna is still talking to him, but I bet he will never learn.

[Akoellh]

Originally Posted by hcvv

I saw this post and it is shows your point to advantage.

Maybe it should be "pinned" as a sticky acting as a role model on "How NOT to do it", at best next to another one as a role model on "How to actually DO it and what can happen then", which brings me back to your strange CPU problem.

Just read the thread developing in kernel bugzilla and you now have a real expert answering you (Thomas Gleixner is one of the subsystem maintainers for the x86 architecture IIRC).

And you just see the difference between a -maybe somehow- experienced user and somebody actually working on this stuff.

We both found this "nolapic" suspicious, the maintainer tells you directly that it is the cause of missing SMP and now we will see, how it can (and I am quite sure it will) be fixed.

[hcvv]

Yes, I also googled a bit about that nolapic. It is definitely blocking SMP. The question being now, why did the install think it nessecary to put it there. And it is nessecary in that I can not boot without it.

And I am now more or less to stay at home because I do not want the guru let waiting for me to long when he asks something

But this is now in the wrong thread. Let us stay on topic.

[ReferenceSeete]

RE: The OP
I largely agree. The Beta/Pre-Release forum is largely not about testing with an eye to improving the distro or upstream projects, rather it often seems to be about finding workarounds to bugs and leaving it there. We can do better.


RE: Propriety drivers & patented codecs
Again, I absolutely agree. If a user cannot find out how to install NVidia drivers manually (and actually do it) then there are probably legitimate questions to be had about whether using a pre-release is appropriate. The posts about how people are somehow "owed" codec package ABC or propriety graphics driver XYZ in order for Factory or a Milestone to be 'usable' miss the point (to be fair the similar posts have shown up in the mailing lists).


RE: Bugzilla
Bugzilla is going to be upgraded this coming Saturday (2009-11-14). One of the improvements is a simplified version of the bug reporting page. You can read a summary of what will happen here:
openSUSE News » Project Bugzilla Update Planned to Version 3.4

The full Bugzill 3.4 release notes are here:
Bugzilla 3.4 Release Notes :: Bugzilla :: bugzilla.org

Despite these changes I do agree with the OP that if users can't be bothered to file a bug report (or even add useful information to existing bug reports) then why are they using a pre-release? More importantly why are such users coming to the forum to start fresh threads? In the case of openSUSE the login for the forum works for Bugzilla so the whole "too many sites, too many passwords" issue is moot here.


RE: Improvements for the future
There are some bright spots here. The first is that people are actually using pre-release versions! The problem is converting those users' forum posts into useful bug reports.

Here's what I propose...I'm on the openSUSE Testing Core Team (TCT), something that was just started in the last few weeks, and I'm really focused on a knock-out run leading up to openSUSE 11.3. What I will do - and ask the rest of the Testing Team to do - is to watch the Pre-Release sub-forum for issues and see if we can reproduce them to either improve bug reports filed or to file fresh bug reports.

Although I feel somewhat conflicted in doing this - I do fear that the TCT might get overwhelmed covering for users who opt for the easy route rather than filing bugs since they know what we're up to - I think it is a practical way to get something positive done. We cannot guarantee that others will file bug reports, even if they come to the forum...but we can leverage what is in the forum for bug squashing purposes.

Naturally everyone (TCT member or not) is welcome to help in the effort to convert complaints into bug-reports!