Yes, it was made clear in the release notes and article that the latest
driver still does not have "2.6.23 kernel support", which is most likely
a euphemism for not handling the SLUB allocator which is default in
2.6.23. However, the bright side according to the article is that next
month's drop i
It may be worth noting that looking to other new or upcoming releases of
other distros is not going to help. Although I initially was frustrated
with Ubuntu (and yes, there are other suggestions for improved
communication of the problem to users), the frustration should be
pointed towards AMD as C
I can confirm as an employee of a company with 1000s of Thinkpad users
who use various distros, but lots of Ubuntu, this is going to really
suck. I just decided to try Gutsy and this is the one thing that is a
real downer to hear that no one really cares if ATI-based notebook users
just can't susp
this is most likely bug 121653.. a problem with fglrx (ATI binary
driver) and the new SLUB allocator. Summary of #121653 (my paraphrase):
ATI needs to fix the fglrx driver since it's closed source, and Ubuntu
kernel devs aren't willing to return to SLAB allocator which doesn't
cause the fglrx driv
if it helps your investigations, 8.4 is the first in the 8.x series that
works reliably for me on suspend/resume and various crashes/hangs I was
getting on any earlier version of fglrx. I have now had a 5 or 6 days
of uptime on 8.4 and multiple suspend/resumes (with no changes to the
acpi default
ATI released Catalyst 8.1 this morning (at least my RSS feed updated this AM
with the news).. big claims in the readme:
- Ubuntu 7.10 shown as supported
- 2.6.23 suspend/resume issues (to ram or disk) fixed
I will be trying it out this morning, but if this is a winner, I hope
that Ubuntu will t
Yes--your patch fixes the issue--I'm back to the functionality I had in
gutsy where NM can manage my wireless network connections
(successfully). I believe I had seen that mentioned elsewhere--that
madwifi isn't supporting wext very well--so your patch makes sense that
it resolves the issue.
--
We probably don't need too much more guessing about whether it's network
manager or wpa_supplicant, etc.. for those who are reporting similarity to the
original reporter the following experience is the common bond:
- *can* connect using Atheros h/w to a protected or unprotected network using
non
It should also be noted that this is a regression from gutsy (at least
on my atheros hardware). In gutsy both NM and wpa_supplicant paths
worked fine for WPA1/2, WEP, open connections to wireless networks.
In Hardy (at least alpha4-6 where I can confirm) *only* wpa_supplicant
(or iwconfig if you
i'm having the same issue after upgrading to 7.04 (i386) yesterday. I
use rhythmbox daily to listen to hours of music, so this is definitely a
huge change with feisty as I can't get through 10 minutes or more of
music. I will try and generate a core file and get a backtrace for the
problem
--
a
Well, that was interesting--I'm not sure if I am having the same issue
as the original submitter, but I can at least give details on what I
found. I believe (and I'm ignoring other crash bugs related to
gstreamer or specific songs/files that crash..) in my case this problem
was exacerbated by a ne
Fixed in glibc.. Fedora/RH bug:
https://bugzilla.redhat.com/show_bug.cgi?id=624852
Only affects --static binaries
** Bug watch added: Red Hat Bugzilla #624852
https://bugzilla.redhat.com/show_bug.cgi?id=624852
--
busybox sed core dump
https://bugs.launchpad.net/bugs/615953
You received this
2010-08-19 Andreas Schwab
* sysdeps/i386/i686/multiarch/strspn.S [!SHARED]: Fix SSE4.2 check.
Index: glibc-2.12-2-gc4ccff1/sysdeps/i386/i686/multiarch/strspn.S
===
--- glibc-2.12-2-gc4ccff1.orig/sysdeps/i386/i686/multiarch/strspn.S
13 matches
Mail list logo
