No proposed fix for this yet? I have been running Karmic without any
issues ever since the awesome workaround, but it would indeed be a
formidable experience for someone unfamiliar with this problem to
install a new system and see everything go haywire. If the solution is
not to disable
Ah the sweet taste of victory... I could not resist doing a new install
of karmic again now that some three months have elapsed, and it all went
like a breeze - install took less than five minutes! Reboot - everything
is perfect... update and upgrade, and install the proprietary nvidia
drivers
I am using the 2.6.28 kernel still, since I am on Jaunty, and the ALSA
package does work on my machine - what I had to do was to switch to
alsa-oss for everything to work properly. I am sure you should be able
to get the sound to work in that kernel too, unless the experts hither
can point out
Mighty awesome I'd say - thanks to Alberto Milone and the rest of the
team!
--
nvidia drivers 185.xx compile into kernel 2.6.28 instead of 2.6.31 on update
from jaunty to karmic
https://bugs.launchpad.net/bugs/474917
You received this bug notification because you are a member of Ubuntu-X,
which
Way to go! Well I am glad coming forward with this bug helped identify
all these issues... Every step we take to weed out bugs is a step to
weed out Bug #1; I would have said the Jackalope itself gives Microsoft
serious competition; the Koala takes it further - let us hope the Lynx
seals the deal!
Yippie!
--
nvidia drivers 185.xx compile into kernel 2.6.28 instead of 2.6.31 on update
from jaunty to karmic
https://bugs.launchpad.net/bugs/474917
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-173 in ubuntu.
Apologies for the delayed reply - I have been tied up all day; also for
the multiple issue report (I was not aware of the 180/185 nomenclature
issue). The trouble is that after the powermizer havoc I was unable to
work on my system, and I could not afford that at the time, so I had
reformatted it
After the bug I had reformatted my system with jaunty; people in the
Ubuntu forums with similar issues had reported that the 190.xx drivers
worked for them because it has a separate powermizer setting.
--
Please consider turning powermizer OFF
https://bugs.launchpad.net/bugs/456637
You received
Yup; seems to me to be exactly the case as in bug #438398 :) Indeed I
believe the nvidia build does not fail even when against the older
kernel, but the fact that it would be built against the older kernel
before the new linux-headers thereby requiring the older one to remain
in place is the
Hmmm yes I don't understand why the build failed in the other bug, since
it succeeded in my case too, and for the 2.6.28 kernel. However, if
2.6.31 does become the default kernel when installed, then the infamous
gdm-respawn-flickering-problem should invariably show up; in my case gdm
started fine
I have been plagued by this bug as well and it has interrupted my karmic
koala experience - I otherwise believe the new changes in karmic are
quite impressive!
The permanent solution to this problem that I believe is (rather than a
workaround which though works is still a workaround and hence an
11 matches
Mail list logo
