To add to #14 comment, a file in /var/lib/initramfs-tools also gets
generated if the host kernel differs from the chroot environments
kernel.
In my case I'm running a Debian system with the 4.9.0-6-amd64 kernel and
a Ubuntu (Xenial) chroot environment with the 4.4.0-127-generic kernel.
When
It is still not possible to install nvidia-current in a chrooted
environment if the kernel name of the running kernel (e.g.
2.6.38-10-server) is different to the kernel name of the chroot (e.g.
2.6.38-10-generic).
(The system tries to locate modules.dep in
/lib/modules/2.6.38-10-server/ in the
A working workaround (tested) would be to check for the kernel
existence, something like:
if [ -n $NEWEST_KERNEL ] [ ${CURRENT_KERNEL} !=
${NEWEST_KERNEL} ]; then
# This can fail when dealing with a chroot see LP: #556653
if [ -e
can you attach the image build log, please?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/556653
Title:
build fails in chrooted system
Attaching the transcript of the debug session.
Upon entering the chroot env, after receiving the error once, I cleaned the
remnant initrd file.
The I modified the postinst script inserting a set -x, set GL to be provided by
MESA and reconfigured the package. No errors.
Then I configured nvidia
I'm testing the natty package in the same chrooted environment, and although
the implemented fix allows the configuration to be successful, a bogus file
/boot/initrd.img-2.6.xx-yy-generic (ie initrd.img-2.6.35-28-generic if running
on a maverick host) is generated.
That file is an incomplete
** Tags added: lucid
--
build fails in chrooted system
https://bugs.launchpad.net/bugs/556653
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in ubuntu.
___
Mailing list:
This bug was fixed in the package nvidia-graphics-drivers-96 -
96.43.14-0ubuntu12
---
nvidia-graphics-drivers-96 (96.43.14-0ubuntu12) lucid; urgency=low
* debian/nvidia-$flavour.{dirs|postinst}.in, rules:
- Install the blacklist file in /lib/nvidia-$flavour instead
of
This bug was fixed in the package nvidia-graphics-drivers-173 -
173.14.22-0ubuntu11
---
nvidia-graphics-drivers-173 (173.14.22-0ubuntu11) lucid; urgency=low
* debian/nvidia-$flavour.{dirs|postinst}.in, rules:
- Install the blacklist file in /lib/nvidia-$flavour instead
of
This bug was fixed in the package nvidia-graphics-drivers -
195.36.15-0ubuntu2
---
nvidia-graphics-drivers (195.36.15-0ubuntu2) lucid; urgency=low
* debian/nvidia-$flavour.{dirs|postinst}.in, rules:
- Install the blacklist file in /lib/nvidia-$flavour instead
of
I'm ok with that workaround. Tks for the quick patch proposal.
--
build fails in chrooted system
https://bugs.launchpad.net/bugs/556653
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-173 in ubuntu.
Ok, thanks for your feedback
** Also affects: fglrx-installer (Ubuntu)
Importance: Undecided
Status: New
** Changed in: fglrx-installer (Ubuntu)
Importance: Undecided = High
** Changed in: fglrx-installer (Ubuntu)
Status: New = In Progress
** Changed in: fglrx-installer
Note: the problem also affects the fglrx driver
--
build fails in chrooted system
https://bugs.launchpad.net/bugs/556653
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in ubuntu.
___
This bug was fixed in the package fglrx-installer - 2:8.721-0ubuntu8
---
fglrx-installer (2:8.721-0ubuntu8) lucid; urgency=low
* debian/rules, fglrx.dirs, fglrx.postinst:
- Install the blacklist file in /lib/fglrx instead of
/usr/lib/fglrx so that the file is available
** Branch linked: lp:ubuntu/fglrx-installer
--
build fails in chrooted system
https://bugs.launchpad.net/bugs/556653
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in ubuntu.
___
Mailing
I know that I asked you to report this problem but now that I recall the
use case for the code I don't think it's a bug.
If you don't pass the -k parameter to update-initramfs, it uses the
latest kernel by default.
In the following code, the initramfs is always called for the latest
kernel,
I understand that in a chroot this can be a problem. Would it be ok if I
simply did update-initramfs -u -k $CURRENT_KERNEL || true so that the
installation doesn't fail in chroots?
--
build fails in chrooted system
https://bugs.launchpad.net/bugs/556653
You received this bug notification because
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: New = Triaged
** Changed in: nvidia-graphics-drivers (Ubuntu)
Importance: Undecided = High
** Changed in: nvidia-graphics-drivers (Ubuntu)
Assignee: (unassigned) = Alberto Milone (albertomilone)
--
build fails in chrooted
** Also affects: nvidia-graphics-drivers-173 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-96 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-96 (Ubuntu)
Status: New = Triaged
** Changed in:
19 matches
Mail list logo
