https://bugzilla.novell.com/show_bug.cgi?id=709886
https://bugzilla.novell.com/show_bug.cgi?id=709886#c15
--- Comment #15 from Michael McWilliam 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.