This bug has not disappeared completely, however the reproducibility
factor has gone down to 10%. My setup is a Dell M1330 GF 9400M GS.
Disabling loose bindings did more or less the same result for me. Now
i'm running with: compiz.real --ignore-desktop-hints --replace --loose-
binding core ccp
I have noticed something interesting..
When a menu is open (Applications,Places or Systems), and Fn+up/Fn+down keys
are pressed, the screen brightness is changed correctly without any
double/quadruple steps, although, now there are only 5 brightness levels,
whereas my LCD screen supports 8
*** This bug is a duplicate of bug 207473 ***
https://bugs.launchpad.net/bugs/207473
** This bug is no longer a duplicate of bug 261721
X never sees brightness key release events
** This bug has been marked a duplicate of bug 207473
Screen brightness double level changes
--
*** This bug is a duplicate of bug 283873 ***
https://bugs.launchpad.net/bugs/283873
This is probably related to https://bugs.launchpad.net/ubuntu/+source
/linux-restricted-modules/+bug/269926
Two were mentioned there, one by Craig: (the link has the 5000 ucode
too)
I downloaded
In software sources enable pre-released unsupported important
recommended updates. Then just upgrade.
--
intrepid update kills wireless 15 oct 08
https://bugs.launchpad.net/bugs/283873
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Running 2.6.27-7-generic kernel on intrepid beta 32-bit, Dell M1330,
Nvidia 8400M 177.80 driver. Same problem. Dell fan control might fix it.
Or it might be that the driver cant get info from bios, therefore puts
it on max, could be one module too much/too little.
--
Latest nvidia driver for
I confirm this on Dell XPS M1330 with nvidia 177.80. Running Intrepid
with latest updates.
--
Screen refresh problems with nvidia on intrepid
https://bugs.launchpad.net/bugs/269904
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Sorry for posting so many times in a row.
But this time I have solved the freezes, in my case at least. What I did
was to create a redistributable bootable backup dvd with remastersys
in case I had to reinstall. Since I gutted the Hardy installation from
trying to fix the bug I used the backup
Hi!
Can you help me testing out this (ugly fix?). Out of pure curiosity I did:
echo 1 /proc/sys/vm/block_dump
but while trying to 'trace' the bug with dmesg (assuming it's I/O related) I
couldn't find anything. WHY? Because my Ubuntu Hardy stopped freezing! My
theory is that this command works
Ignore echo 1 /proc/sys/vm/block_dump, this only delayed the freeze.
Bug remains.
--
Linux kernel 2.6.24-12 lockup
https://bugs.launchpad.net/bugs/204996
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Managed to get some output with block_dump enabled. Very interesting.
Most interesting excerpts here, complete one attached. Note, the mouse
freeze is least relevant here.
[ 9499.124930] psmouse.c: GlidePoint at isa0060/serio1/input0 lost
synchronization, throwing 1 bytes away.
[ 9500.058337]
2.6.24-19-generic
** Attachment added: lspci-vvnn.log
http://launchpadlibrarian.net/15539016/lspci-vvnn.log
--
Linux kernel 2.6.24-12 lockup
https://bugs.launchpad.net/bugs/204996
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Under the assumption that this is related to harddrive (sata) I've tried
changing fstab to not use the realtime function, but with no avail. The
2.6.25-7/8 kernels did not contribute to any improvement either.
However there's a major clue (ugly fix),
echo 1 /proc/sys/vm/block_dump
this triggers
I can confirm that the 2.6.24-16-generic (hardy) Linux kernel running
under Gutsy had no such issues. However, appeared only when I
reinstalled with Hardy. Just like DJ Dallas, I cannot reproduce the bug
at will, nor can I trace it in any way. The only difference is that the
heavy freeze doesn't
14 matches
Mail list logo
