Yes it is correct that for amd64 SSE is enabled by default in the
compiler. But (if I'm not wrong) the FFTW --enable-sse flag does not
(only) set compiler flags. Instead it activates the specially written
SSE optimized kernels are compiled. Because the --enable-sse flag is not
passed, those
This link used to be correct. But all bugs got deleted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/391628
Title:
Everything gets swapped out after resume from suspend using fglrx drivers
--
Yes has been reported here:
http://ati.cchtml.com/show_bug.cgi?id=1798
But it might help if everyone report it to
http://www.amd.com/us/LinuxCrewSurvey and to the manufacturer of their
notebook (Dell, HP, ..) I have done both a long time ago. So far it
hasn't helped but may be they address this
Is this fixed with 2.6.32-24? It looks like the patch is included.
--
ext4 kernel bug (2.6.32-22) while writing on USB device
https://bugs.launchpad.net/bugs/592589
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
@jon h: Did you only update the kernel or also the Catalyst driver since
7-22? The change-log of 2.6.32-23 doesn't mention anything which should
affect this bug.
--
Resume from sleep fails / extremely slow with fglrx
https://bugs.launchpad.net/bugs/561292
You received this bug notification
I get the same error on x86-64 but I think it is triggered differently
Different is that the last sysfile is:
/sys/devices/system/cpu/cpu0/topology/physical_package_id
Also my case is not IO intensive. I'm just starting IMB with OpenMPI. And it
happens 2/3x I start it. Thus very reproducible.
Public bug reported:
Binary package hint: fftw3
For x86/i386 FFTW is compiled with --enable-sse(2). For amd64/x86-64
this flag is missing. Adding this flag is very important for the
performance.
The part from debian rules where it is set for i386:
+ifeq ($(ARCHITECTURE), i386)
+
For me 8.66 has the same problem.
I'd suggest to leave a comment on the Dell website about this problem. I
did and they contacted me about this. So they seem to care. Hopefully if
enough people write they make AMD fix their ATI driver.
Just go to your product page. E.g.
I believe I have the same problem. And it is also sometimes OK (wireless
works) and sometimes it is not working (disabled enabled in
knetworkmanager). Luckily for me it is usually OK and only seldom not
OK. Thus if it is not OK I just need to reboot and it is usually working
then. Maybe you want
*** This bug is a duplicate of bug 465250 ***
https://bugs.launchpad.net/bugs/465250
** This bug has been marked a duplicate of bug 465250
dell 1557 special key
--
dell 1557
https://bugs.launchpad.net/bugs/465249
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Binary package hint: gromacs-data
The gromacs-data package includes a FF.dat file with the CHARMM FF. The
CHARMM FF parameters are experimentally and got accidentally added to
the gromacs 4.0.5 source tarball. But the FF.dat does not include a
reference to the CHARMM FF and
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/35205807/Dependencies.txt
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/35205808/XsessionErrors.txt
--
Gromacs package includes prelimanary CHARMM FF
https://bugs.launchpad.net/bugs/476056
You
12 matches
Mail list logo
