Alright, as there's been no responses, I'm going to go ahead and assume
the remaining bug tasks should be closed out. If there actually is work
still needed to be done, either reopen the appropriate task or (even
better) open a new, cleaner bug report against the current development
version,
@Alberto, is there anything more that can be reasonably done with this
bug report? If not, perhaps the remaining bug tasks should be closed
out?
--
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
** Tags added: jaunty2karmic
--
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
** Tags added: patch-accepted-upstream
--
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
** Changed in: ubuntu-release-notes
Status: New = Invalid
--
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
** Tags added: karmic
** Tags added: jaunty
--
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
At this point it's quite clear that we won't get the fix for DKMS in
Karmic, therefore I declined the task for Karmic. This is fixed in Lucid
though.
** Also affects: dkms (Ubuntu Lucid)
Importance: Critical
Assignee: Alberto Milone (albertomilone)
Status: Fix Released
** Also
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
@ochatard:
The fix was released in only Ubuntu Lucid, therefore the bug is still not fixed
in Karmic.
--
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
My graphic card requires the nvidia-96 driver and seems to the same trouble,
even after upgrade to the latest 2.6.31-17 kernel.
The only workaround I found to be able to run in high resolution is to run the
old 2.6.28 kernel, but then, ALSA sound package is no longer working, so the
issue to
This bug was fixed in the package nvidia-graphics-drivers-173 -
173.14.22-0ubuntu1
---
nvidia-graphics-drivers-173 (173.14.22-0ubuntu1) lucid; urgency=low
* Rework packaging taking Mandriva's as a model:
- Use alternatives instead of diversions.
- Reduce the number of
** Branch linked: lp:ubuntu/nvidia-graphics-drivers-173
** Branch linked: lp:ubuntu/nvidia-graphics-drivers-96
--
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
** Branch linked: lp:ubuntu/nvidia-graphics-drivers
--
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
This bug was fixed in the package dkms - 2.1.1.0-0ubuntu1
---
dkms (2.1.1.0-0ubuntu1) lucid; urgency=low
[ Mario Limonciello ]
* New upstream version
* dkms_autoinstall: Minor logic cleanups from submitted patches.
* dkms_autoinstall: Run under dash since dkms.conf isn't
** Branch linked: lp:ubuntu/dkms
--
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
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
Alberto's fix has been committed upstream and will be uploaded to lucid
in the next DKMS upload.
** Changed in: dkms (Ubuntu)
Status: In Progress = Fix Committed
--
nvidia drivers 185.xx compile into kernel 2.6.28 instead of 2.6.31 on update
from jaunty to karmic
http://linux.dell.com/git/?p=dkms.git;a=commit;h=5867cc58c8b1435c4a1dd7f063556f09e5372f0b
--
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
** Changed in: nvidia-graphics-drivers-173 (Ubuntu)
Assignee: piero (petercrue) = Alberto Milone (albertomilone)
--
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
** Changed in: nvidia-graphics-drivers-173 (Ubuntu)
Status: In Progress = Confirmed
** Changed in: nvidia-graphics-drivers-173 (Ubuntu)
Status: Confirmed = Fix Committed
** Changed in: nvidia-graphics-drivers-173 (Ubuntu)
Status: Fix Committed = In Progress
** Changed in:
@piero
Why did you change the status of this bug? I'll upload my fix as soon as my
patch is reviewed by upstream.
--
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
@Alberto Milone: well you can't do that because it is not a genuine
ubuntu package, so I am not sure how to proceed with it. I am not
familiar to the Ubuntu defect process and trying to raise something
directly on the website doesn't work.
Anyhow, the issue I posted appears to be the cause of the
@TaxAlien
I have provided upstream (i.e. DKMS developers) with a patch that I wrote. They
will have to review it and then we should introduce the change in Ubuntu and
fix the drivers.
--
nvidia drivers 185.xx compile into kernel 2.6.28 instead of 2.6.31 on update
from jaunty to karmic
@TaxAlien
Your problem is a different bug. Please file a new bug report against
libxine1-bin by typing the following command from the command line:
ubuntu-bug libxine1-bin
--
nvidia drivers 185.xx compile into kernel 2.6.28 instead of 2.6.31 on update
from jaunty to karmic
** Attachment added: Debdiff for nvidia -96
http://launchpadlibrarian.net/35744695/nvidia-graphics-drivers-96_96.43.13-0ubuntu7.debdiff
--
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
Here's a better version of the patch which makes sure that the fix works
on Rhel based systems too.
** Attachment added: dpkg_rpm.patch
http://launchpadlibrarian.net/35744679/dpkg_rpm.patch
--
nvidia drivers 185.xx compile into kernel 2.6.28 instead of 2.6.31 on update
from jaunty to karmic
** Attachment added: Debdiff for nvidia -173
http://launchpadlibrarian.net/35744697/nvidia-graphics-drivers-173_173.14.20-0ubuntu6.debdiff
** Changed in: dkms (Ubuntu)
Status: New = In Progress
** Changed in: dkms (Ubuntu)
Importance: Undecided = Critical
** Changed in: dkms
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!
I think this is the problem with Nvidia during an upgrade to 9.10 from a
previous version:
libxine1-bin:
Depends: nvidia-185-libvdpau but it is not going to be installed
This is preventing an upgrade or reinstall of Nvidia properly, because
nvidia-185-libvdpau won't be removed with all the
The attached log shows how the patch works.
** Attachment added: mylog.log
http://launchpadlibrarian.net/35478827/mylog.log
** Also affects: nvidia-graphics-drivers-173 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-96 (Ubuntu)
Importance:
I have provided upstream with a patch for DKMS so that we can build the
kernel module for both the kernel in use and for the most recent kernel
in the system.
This solves the problem here.
** Changed in: nvidia-graphics-drivers-180 (Ubuntu)
Assignee: (unassigned) = Alberto Milone
While DKMS is definitely not the cause of the problem here, driver -180
relies on a template which dkms provides in
/usr/lib/dkms/common.postinst.
Driver -173 and -96 should do the same (i.e. source it from the
postinst) so as to minimise efforts here by avoiding code duplication.
--
nvidia
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
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
On Thu, Nov 5, 2009 at 6:10 PM, Bryce Harrington
br...@bryceharrington.org wrote:
manjul, ok thanks for getting back to us. We can focus this bug report
on Daniel's version of the issue.
Daniel, looking at your make.log it seems to be working successfully and
it mentions it's building
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
** Package changed: ubuntu = nvidia-graphics-drivers-180 (Ubuntu)
--
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
Okay, you've mentioned a few different problems, it is generally best to
focus just one issue per bug report. The powermizer bug obviously
already has a bug report. The 180/185 confusion is just that - we left
the package in launchpad named 180 even though the driver itself is 185
(we didn't
39 matches
Mail list logo
