I just came across this bug in Lucid, trying to compile my own zen
kernel, does anyone know if this is still going on in Maverick?
--
dkms - error when installing custom kernel
https://bugs.launchpad.net/bugs/292606
You received this bug notification because you are a member of Ubuntu
Bugs, which
Sadly, I have to report that this bug still persists in ubuntu Lucid.
--
dkms - error when installing custom kernel
https://bugs.launchpad.net/bugs/292606
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
On a fully-updated Karmic I had the same problem while installing a custom
kernel compiled with make-kpkg.
Installing this package solved the problem:
http://linux.dell.com/dkms/permalink/dkms_2.1.1.2-0ubuntu1_all.deb
Hope this will help those who cannot upgrade to (still unstable) Lucid.
--
d
Maybe this is related:
https://bugs.launchpad.net/ubuntu/+source/nvidia-common/+bug/292606
Can you also have a look at it? Fix should be similar
--
dkms - error when installing custom kernel
https://bugs.launchpad.net/bugs/292606
You received this bug notification because you are a member of Ubu
Maybe this?
http://linux.dell.com/dkms/permalink/dkms_2.1.1.2-0ubuntu1_all.deb
--
dkms - error when installing custom kernel
https://bugs.launchpad.net/bugs/292606
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
Fix released for Lucid... What about Karmic?
Shall I recompile/patch the package?
I see that the version of dkms for Karmik is 2.1.0.1... Will be released a
2.1.1.2 for Karmic too?
--
dkms - error when installing custom kernel
https://bugs.launchpad.net/bugs/292606
You received this bug notifica
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 sourc
I've got a fix committed upstream that will handle this particularly:
http://linux.dell.com/git/?p=dkms.git;a=commit;h=f113f8759d2eb60ad2cde4e009d4f5966c6ad4f1
There are several other related commits near by that include the
conversion to upstart, and causing all logging to go to the syslog.
** C
Hi,
So I can change the status of the package in the file /var/lib/dpkg/status
I changed the status from ``install ok half-configured''
to ``install ok installed''.
That at least prevents aptitude and apt-get from breaking my nvidia
driver.
Karim
--
dkms - error when installing custom kernel
Hi
So I have this problem now. As a result of an upgrade I had serious boot
issues, I almost considered reinstalling an os. Anyways I installed a
custom kernel and the latest Nvidia drivers. Apparently this is bad
form? It's linux is it not so I can use kernel.org kernels can I not?
So I have thi
** Changed in: nvidia-common (Ubuntu)
Status: New => Invalid
--
dkms - error when installing custom kernel
https://bugs.launchpad.net/bugs/292606
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
Also happening for me in Karmic. The fix outlined above:
"Patching /etc/kernel/postinst.d/dkms to redirect stdout DOES FIX the problem.
Adding "1>&2" to the invocation of /etc/init.d/dkms_autoinstaller keeps stdout
clean."
fixes the problem for me.
--
dkms - error when installing custom kernel
Mike Stroyan's analysis is correct. This is not a bug in nvidia-common,
it's a bug in dkms for outputting to stdout.
Standard Ubuntu kernel packages don't load the debconf confmodule, but
custom packages built with make-kpkg do, and this is perfectly
legitimate. Anything called from a maintainer
Mario:
Adding the debconf trigger in every modalias package would imply calling the
trigger every time the modaliases are installed which could be, say, 3 times
(as currently there are 3 different drivers) in row when dist-upgrading to
Karmic. This means that users will see the same message thre
** Changed in: dkms (Ubuntu)
Status: Confirmed => Invalid
** Changed in: nvidia-common (Ubuntu)
Status: Invalid => New
** Changed in: dkms
Status: New => Invalid
--
dkms - error when installing custom kernel
https://bugs.launchpad.net/bugs/292606
You received this bug notif
Alberto:
I don't agree here that running this in the kernel postinst is going to
increase the likelihood of nvidia-common helping transition users. The
order that the nvidia-common postisnt and kernel postinst would trigger
is irrelevant, because the message will be displayed either way, and the
@Mario
the kernel postinst exists because it can happen that the nvidia-common
postinst is triggered before the installation of the new (or updated) modalias
files takes place thus preventing nvidia-common from helping users with the
transition to a new driver.
The kernel postinst gives nvidia-
Why does the nvidia-common kernel postinst even exist? It looks like
it's only purpose is to replicate the functionality that was there from
the nvidia-common postinst. Obsoleted drivers won't be introduced by
new kernel images, but instead by newer modaliases as detected by
nvidia-common.
nvidi
The actual fix to dkms is not adding flushing of stdout.
The fix is redirecting /etc/init.d/dkms_autoinstaller output to stderr so that
it doesn't send confusing output to debconf via stdout.
--
dkms - error when installing custom kernel
https://bugs.launchpad.net/bugs/292606
You received this b
As discussed in this bug report, the problem should be fixed in DKMS (by
flushing stdout after printing).
I have marked the report as invalid for nvidia-common and assigned the
bug to dkms instead.
** Also affects: dkms (Ubuntu)
Importance: Undecided
Status: New
** Changed in: dkms (Ub
I'm a bit confused here. The last patch in comment 29 looks weird and
does not incorporate Alberto's latest proposed change.
Alberto, can you please attach a complete and tested patch, and re-
subscribe the sponsoring team once its ready? Thanks!
--
dkms - error when installing custom kernel
htt
This bug is still present in dkms 2.0.21.1-0ubuntu3.
--
dkms - error when installing custom kernel
https://bugs.launchpad.net/bugs/292606
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubun
This bug is still present in dkms as of 2.0.21.1. It would be nice if it gets
fixed before karmic's release. So I nominated it for karmic.
Attached a debdiff for the maintainers.
** Attachment added: "dkms_2.0.21.1-0ubuntu4.debdiff"
http://launchpadlibrarian.net/30693591/dkms_2.0.21.1-0ubuntu4
@Alberto Milone
I applied you attached patch to:
/var/lib/dpkg/info/nvidia-common.config
in addition to what I had already applied previously to:
/usr/share/pyshared/NvidiaDetector/nvidiadetector.py
/etc/kernel/postinst.d/nvidia-common
Same problem persists...
I guess Mike Stroyan has a point h
** Branch linked: lp:ubuntu/karmic/nvidia-common
--
dkms - error when installing custom kernel
https://bugs.launchpad.net/bugs/292606
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.c
Flushing stdout is not going to help with this problem.
As I said in comment #17, the error is caused by /etc/init.d/dkms_autoinstaller
sending text to debconf via stdout.
Flushing output within /etc/kernel/postinst.d/nvidia-common won't undo that
error.
Debconf has already gotten the bad command
@jasmineaura:
Does it solve the problem if you apply the attached patch to your
/var/lib/dpkg/info/nvidia-common.config ?
Please let me know
** Attachment added: "test1.patch"
http://launchpadlibrarian.net/29714472/test1.patch
--
dkms - error when installing custom kernel
https://bugs.launc
(in addition to what you had already applied from the package in karmic)
--
dkms - error when installing custom kernel
https://bugs.launchpad.net/bugs/292606
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
NOPE, NOT FIXED!
Got the diff from:
http://launchpadlibrarian.net/29611367/nvidia-common_0.2.11_0.2.12.diff.gz
Applied the relevant changes to 0.2.11 in:
/usr/share/pyshared/NvidiaDetector/nvidiadetector.py
/etc/kernel/postinst.d/nvidia-common
BUT still, same problem persists:
Examining /etc/ke
This bug was fixed in the package nvidia-common - 0.2.12
---
nvidia-common (0.2.12) karmic; urgency=low
* debian/control:
- Drop dependency on nvidia-71-modaliases.
* NvidiaDetector/nvidiadetector.py:
- Use a text file in /usr/share/nvidia-common/
instead of hardcodi
The latest commit in my branch should fix this (by flushing stdout
before printing): lp:nvidia-common
--
dkms - error when installing custom kernel
https://bugs.launchpad.net/bugs/292606
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: nvidia-common (Ubuntu)
Importance: Undecided => Medium
** Changed in: nvidia-common (Ubuntu)
Status: New => In Progress
** Changed in: nvidia-common (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
--
dkms - error when installing custom kernel
http
I'm having the same problem on Ubuntu 9.04.
--
dkms - error when installing custom kernel
https://bugs.launchpad.net/bugs/292606
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
ht
I've got the same errors with dkms/nvidia-common when installing my
fresh from the shelf linux kernel image.deb. I also noticed there's no
abi-file in the /boot directory. From what I've figured out, this makes
me either press the -bar at system bootup (after GRUB) or I can
chose to just wait 30 se
"man 7 debconf" states-
* Avoid outputting anything to stdout in your postinst, since that
can confuse debconf, and postinst should not be verbose anyway.
Output to stderr is ok, if you must.
It might be better to redirect stdout to file descriptor 3.
I see
I don't know that I agree that's logically correct. the output from the
init script should be going to to stdout. It is *not* error output from
DKMS's kernel postinstall script, so it shouldn't be on stderr.
If it's not happening while DKMS is running, then before loading debconf
in nvidia-commo
** Package changed: nvidia-common (Ubuntu) => dkms (Ubuntu)
--
dkms - error when installing custom kernel
https://bugs.launchpad.net/bugs/292606
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
This is not actually a defect in nvidia-common. It is a defect in dkms.
The /etc/kernel/postinst.d/dkms script is sending messages to stdout.
That script is run under /usr/share/debconf/frontend, which expects that stdout
will only be used for messages to it.
The actual response to the output doe
Error still present
sudo dpkg -i ../linux-image-2.6.28.9_2.6.28.9-10.00.Custom_i386.deb
[sudo] password for niko:
Выбор ранее не выбранного пакета linux-image-2.6.28.9.
(Чтение базы данных... на данный момент установлено 305345 файлов и каталогов.)
Распаковывается пакет linux-image-2.6.28.9 (из ф
Disregard both of my posts.
My issue was not as it appeared.
Since I had edited my menu.lst by hand in the past (to add Grub
Invaders) the update-grub process was being skipped after the kernel
install. When I ran it by myself it asked if I want to keep my own
menu.lst or take the package-mainta
upon closer inspection, no abi is made for the kernel when "installed"
without nvidia-common (no error, no finish).
the /boot/ directory has abi-2.6.27etc for each kernel image except the
kernel I compiled.
--
dkms - error when installing custom kernel
https://bugs.launchpad.net/bugs/292606
You
In Intrepid amd64 with kernel 2.6.27.18:
If I remove the nvidia-common package, the kernel install "finishes"
without error, but it is not really finishing.
The kernel is never added to /boot/grub/menu.lst and I suspect other
more important steps are being skipped.
I can manually add the kernel
i can confirm the same exact error of those above with 2.6.28. it seems
to happen whathever you use distro supplied nvidia drivers or not (i use
nvidia installer for both kernel module and driver (exactly 180.18) and
i could run xorg as soon as i rebooted after installing the module with
the nvidia
I'm having the same problem after compiling a custom kernel using
kernel-package:
$ sudo make-kpkg --initrd --append-to-version=-nostradamus kernel_image
kernel_headers
$ sudo dpkg -i linux-
image-2.6.27.10-nostradamus_2.6.27.10-nostradamus-10.00.Custom_amd64.deb
Selecting previously deselected
** Changed in: nvidia-common (Ubuntu)
Sourcepackagename: None => nvidia-common
--
dkms - error when installing custom kernel
https://bugs.launchpad.net/bugs/292606
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
Hello
I had the same Problem. I solved it like this:
Boot system in FileSave Mode
Go to root Console
do apt-get purge nvidia-common
install your Kernel. dpkk -i "KERNEL.deb"
when done reinstall the nvidia-common Package apt-get install nvidia-common
It worked for me. Everything fine. Nvidia Driv
Wouldn't removing nvidia-common not let you install the drivers?
--
dkms - error when installing custom kernel
https://bugs.launchpad.net/bugs/292606
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
Same problem here.
>Failed to process /etc/kernel/postinst.d at
>/var/lib/dpkg/info/linux-image-2.6.27.2.postinst line 1181.
The fix of removing nvidia-common worked for me.
Geoff
--
dkms - error when installing custom kernel
https://bugs.launchpad.net/bugs/292606
You received this bug notific
I have the exact same issue when installing the debs of my custom kernel
--
dkms - error when installing custom kernel
https://bugs.launchpad.net/bugs/292606
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
I had to do the following:
sudo chmod -x /etc/kernel/postinst.d/nvidia-common
sudo apt-get remove nvidia-common
This completes the installation of the custom kernel. However, the
/etc/kernel/postinst.d/nvidia-common is still there. So, I, reinstalled it
and then purged:
sudo apt-get install nvi
I have the same problem and I came to same conclusion that it was
nvidia-common ... upon trying to figure out what package it came from...
it comes from "nvidia-common" (quite simple).
The weird thing is I didn't have that package installed.. so I installed
it (and it also flagged other modaliases
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms
run-parts: executing /etc/kernel/postinst.d/nvidia-common
+ . /usr/share/debconf/confmodule
++ set -x
++ '[' '!' 1 ']'
++ '[' -z '' ']'
++ exec
++ '[' '' ']'
++ exec
++ DEBCONF_REDIR=1
++ export DEBCONF_REDIR
+ db_se
Same problem here.
cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.10
DISTRIB_CODENAME=intrepid
DISTRIB_DESCRIPTION="Ubuntu 8.10"
uname -a
Linux jambo 2.6.27-7-generic #1 SMP Tue Nov 4 19:33:20 UTC 2008 i686 GNU/Linux
ii linux-firmware1.2
I have exactly the same error here. I tried to build my own kernel. All
is ok, but when I try to install the *.deb, I get the error during the
package configuration.
There is my configuration :
- Ubuntu 8.10. Installed from scratch, no upgrades from a previous version.
- Nvidia Driver version : 1
I am having the exact same issues, though I am not using envy for my
nvidia drivers and my kernel and patches are straight from kernel.org.
---
Failed to process /etc/kernel/postinst.d at
/var/lib/dpkg/info/linux-image-2.6.27.4.tyro2.postinst line 1181.
dpkg: error processing linux-image-2.6.27.4
55 matches
Mail list logo
