https://bugzilla.novell.com/show_bug.cgi?id=709886 https://bugzilla.novell.com/show_bug.cgi?id=709886#c Michael McWilliam <pilot.mm@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High Version|Factory |Final -- 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=709886 https://bugzilla.novell.com/show_bug.cgi?id=709886#c2 Erik Sorenson <sorenson2743@amtelecom.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 - High |P1 - Urgent CC| |sorenson2743@amtelecom.net Component|Kernel |Kernel Version|Final |Milestone 5 Product|openSUSE 11.4 |openSUSE 12.1 Target Milestone|--- |Milestone 5 Severity|Major |Critical --- Comment #2 from Erik Sorenson <sorenson2743@amtelecom.net> 2011-09-29 14:06:03 UTC --- I did a test install two nights ago of KDE from 12.1m5-64bit DVD, and problem still exists. The issue is well written up here in this bug report and at: http://forums.opensuse.org/english/get-technical-help-here/hardware/461975-d... I have a Z68 board with the Realtk rtl8111e network chip with a wired connection. The downloaded driver from Realtek, to fix the problem (severe, hung system while updating, sufring, etc) crapped out with a fatal running autorun.sh ... something about wrong kernel driver r8169 rather than r8168. Needless to say, Win 7's 8111e driver works fine. So I have been forced to abandon 12.1 (any status) until fixed. A scan of newish series 6 boards (as well as AMD 8 and 9 series boards) offered for sale on NewEgg reveals that the overwhelming majority are deploying this 8111e chip and that, if the problem is not fixed, 12.1 RTM will be unusable and increasingly so. Thus I recommend that this bug be escalated to "Critical -- Showstopper". -- 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=709886 https://bugzilla.novell.com/show_bug.cgi?id=709886#c4 --- Comment #4 from Michael McWilliam <pilot.mm@gmail.com> 2011-10-21 15:39:54 UTC --- Why are we quibbling about the severity of this bug when the fix is so simple? It is merely a matter of changing over the driver. Lets just fix it. Honestly if I knew there was some directory on some repository and I knew what line into what config file I would just do it myself. The people that are trying to push up the severity just want to see it get fixed. A bug that makes the computer crash yet it is easy to fix should be a no-brainer. Why are people sitting on their hands arguing about some silly drop box in a bug tracker? Fix-it, fix-it, fix-it!!! -- 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=709886 https://bugzilla.novell.com/show_bug.cgi?id=709886#c6 Greg Kroah-Hartman <gregkh@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P1 - Urgent |P4 - Low CC| |gregkh@suse.com Severity|Critical |Enhancement --- Comment #6 from Greg Kroah-Hartman <gregkh@suse.com> 2011-10-21 15:57:27 UTC --- we will not just "replace the existing in-kernel driver" with a random tarball from the internet, sorry. Please work with the upstream kernel developers to get your hardware working. The fact that your hardware works with the external driver is a great start, perhaps it's just a few line change for the in-kernel driver to solve the issue. Please email the linux-wireless@vger.kernel.org mailing list with the information here and they will be glad to help you out. -- 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=709886 https://bugzilla.novell.com/show_bug.cgi?id=709886#c8 --- Comment #8 from Michael McWilliam <pilot.mm@gmail.com> 2011-10-22 05:15:43 UTC --- Greg My apologies if my comment seems forceful. It was a little frustrating reading Stephan's post. It seemed a little bit inane not to fix a problem affecting a 12.1 release because it was originally posted as a 11.4 bug. I can understand your concern about a "random tarball" however it is from Realtek Semiconductor Co. Thus in my opinion it is trustworthy. I can also understand your concern about this being a responsibility for the Kernel folks. However I post bug reports hoping to improve the experiences of other Suse users not technically skilled enough to solve these type of problems themselves. I do not see why this simple fix could not be included in a release while the kernel people sort out there driver problems. Sven does give some interesting information. I wonder will openSuse eventually migrate to kernel 3.0? An aside for me is the backwards compatibility... but that is a totally separate issue... Well that being said Greg I am just trying to help improve openSuse I will leave it up to you whether you want to act on my findings or not. Take Care Mike -- 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=709886 https://bugzilla.novell.com/show_bug.cgi?id=709886#c10 christos gitsis <cgitsis@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cgitsis@gmail.com --- Comment #10 from christos gitsis <cgitsis@gmail.com> 2011-10-29 04:01:54 UTC --- (In reply to comment #9)

Ok my ignorance... kernel 3.0 is really just another minor release. If Sven is correct it seems like the kernel people have fixed this.... If true then maybe all this bug stuff is resolved... once again sorry about the forcefulness.

Take Care Mike

I would like to say that the issue is not resolved in the 12.1 version I downloaded yesterday. I have solved the problem in other distributions as described earlier, by compiling realtek's driver against my kernel headers. But the problem is bigger in openSUSE liveCDs. Because 'make' and 'gcc' are missing. And how is one supposed to install them, if one's network connection doesn't work? So if you have the CD version of openSUSE installed, you either have to install (again) the DVD version, or somehow download the required development packages, copy them to your machine, and then compile the r8168 module. This is a time consuming procedure, and I imagine many people would quit the effort. -- 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=709886 https://bugzilla.novell.com/show_bug.cgi?id=709886#c12 --- Comment #12 from Sven Hartrumpf <hartrumpf@gmx.net> 2011-11-01 08:42:28 UTC --- (In reply to comment #3)

if the same problem was in 11.4, it's by definition no 12.1 ship stopper

Yes. But then this bug should be assigned to "Product openSUSE 11.4" as it was before. Because otherwise this bug will never be fixed in openSUSE 11.4. If I am right, can somebody please change the "Product" attribute of this bug? Thanks a million. -- 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=709886 https://bugzilla.novell.com/show_bug.cgi?id=709886#c13 Gerard Mulvey <gpmulvey@iol.ie> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P4 - Low |P1 - Urgent CC| |gpmulvey@iol.ie Target Milestone|Milestone 5 |--- Severity|Enhancement |Major --- Comment #13 from Gerard Mulvey <gpmulvey@iol.ie> 2011-11-13 11:29:12 UTC --- This issue affects me in opensuse 11.4 64, 12.1 RC2 64 I have the same issue in both, This is an issue in other distros across linux and is indeed a showstopper. Any one new to linux who hits this issue will be thinking it doesn't work and imeadietely move on. This has to work out of the box for everyone regardless of distro or version. -- 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=709886 https://bugzilla.novell.com/show_bug.cgi?id=709886#c15 --- Comment #15 from Michael McWilliam <pilot.mm@gmail.com> 2011-11-13 23:25:59 UTC --- Hi Greg I urge you to read all the instructions I have posted in this bug report. That fix that I posted IS the driver from the manufacturer. I am getting very confused about this bug. Or at least the communication surrounding it. Your original post about a "random tarball" not being acceptable seems to contradict a recent post of yours: "there's not much we can do here, it is up to the manufacturer to fix their driver issues here" Considering that it is the manufacturers driver that fixes this problem, could you please explain to me and others about this contradiction. When is a manufacturers driver ok and not ok? Furthermore I would like to add that the latest kernel update restored the original problem. This time I couldn't even get intermittent internet. So I would say that the severity is getting worse. At least the intermittent Internet was tolerable enough to download the fix. Finally I would like to add that I posted this bug report (along with a fix) for the benefit of the larger Suse community. Many users have been arguing about the severity of this bug here on this thread. Yet the official communications are brushing us off and working hard at avoiding this problem. It only took a mere three hours for you to over-ride a users opinion on the severity of this bug... If there is some legitimate reason why the fix I proposed cannot be included in the Suse release then please explain that to us users. Honestly it seems that we are all being brushed off. Much of the communication around this bug is simply confusing... Take Care Mike McW -- 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=709886 https://bugzilla.novell.com/show_bug.cgi?id=709886#c17 --- Comment #17 from Michael McWilliam <pilot.mm@gmail.com> 2011-12-20 09:47:08 UTC --- I am afraid that I have been rude on this thread and have probably offended some people. What can I say? I was caught in the middle of a frustrating moment. Accordingly I think this bug will be receiving less attention. Lars and other users I appreciate your comments. I think this bug needs attention, I think the fix is simple. The more people that post here will help the Suse people see past my offensive posts and fix this for the betterment of polite users. -- 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=709886 https://bugzilla.novell.com/show_bug.cgi?id=709886#c Jeff Mahoney <jeffm@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |Kernel Version|Milestone 5 |Final Product|openSUSE 12.1 |openSUSE 11.4 -- 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.