I was attempting to compile my own kernel as a debian package, following
these directions:
https://www.debian.org/releases/jessie/i386/ch08s06.html.en
When I got to the point where it has you run make-kpkg itself, where it
suggests the following command:
# fakeroot make-kpkg --initrd
On Tue, 10 Dec 2013 22:36:02 -0500 (EST), Michael Gulick wrote:
>
> I think my only option if I want automatic upgrades is to keep the
> abiname constant. I'm assuming (and I'm not sure whether this
> assumption is correct) that all the third party modules (primarily
> nvidia drivers and vmwar
On Mon, 09 Dec 2013 23:13:32 -0500 (EST), Stephen Powell wrote:
If you want to do this, you won't be able to use make-kpkg. You will
need to do something like make a modified version of the Debian source
package, linux, and build it with dpkg-buildpackage. But you want to
use upstream so
On Mon, 09 Dec 2013 15:39:29 -0500 (EST), Michael Gulick wrote:
>
> Hi,
>
> I'm looking for a way to override the default kernel package versions
> generated by make-kpkg. With 3.0+ kernels, the kernel sublevel (as in
> VERSION.PATCHLEVEL.SUBLEVEL), which is incremente
On Mon, Dec 9, 2013 at 8:39 PM, Michael Gulick wrote:
>
> I'm looking for a way to override the default kernel package versions
> generated by make-kpkg. With 3.0+ kernels, the kernel sublevel (as in
> VERSION.PATCHLEVEL.SUBLEVEL), which is incremented when there are stable
>
Hi,
I'm looking for a way to override the default kernel package versions
generated by make-kpkg. With 3.0+ kernels, the kernel sublevel (as in
VERSION.PATCHLEVEL.SUBLEVEL), which is incremented when there are stable
updates for a kernel release, is used to generate the package name.
ksyms are build as amd64 format.
>I notice that Linux Makefile mentions an environment variable named HOSTCC.
>I tried to set the variable, but it still failed because of linker issue.
>
>Can make-kpkg do this job correctly? What extra parameter I should add?
Yes, you can do this.
1. a
. It can build
> the kernel itself correctly, but the problem is script tools such as
> genksyms are build as amd64 format.
> I notice that Linux Makefile mentions an environment variable named HOSTCC.
> I tried to set the variable, but it still failed because of linker issue.
>
>
Makefile mentions an environment variable named HOSTCC.
I tried to set the variable, but it still failed because of linker issue.
Can make-kpkg do this job correctly? What extra parameter I should add?
On 3/28/12, Stephen Powell wrote:
> (I.e. is this a bug or a feature?)
Haha, indeed! It seems M$ is haunting us, haha...
Regards,
Panayiotis
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
the internal kernel version, and the
package version always did too. There were different suffices, but the
basic version (x.y.z, for example, 2.6.32), was always consistent. This
is no longer the case. As further clarification, make-kpkg uses
the internal version in it's package name, and th
), the version in the
name of the package and the debian package version are often different!
Regards,
Panayiotis
On 03/27/2012 02:05 PM, Stephen Powell wrote:
> On Tue, 27 Mar 2012 06:49:58 -0400 (EDT), Panayiotis Karabassis wrote:
>> I am trying to understand how make-kpkg chooses the
On Tue, 27 Mar 2012 06:49:58 -0400 (EDT), Panayiotis Karabassis wrote:
>
> I am trying to understand how make-kpkg chooses the versions for the
> packages it creates. Each package has a name(a), which contains a
> version part(a1), as well as a version(b), which is further split i
Hi,
I am trying to understand how make-kpkg chooses the versions for the
packages it creates. Each package has a name(a), which contains a
version part(a1), as well as a version(b), which is further split in
upstream version(b1) and Debian revision(b2), right? Assuming this, I'll
ask my que
Hello,
I try to compile a custom kernel in my home-directory with make-kpkg to
create a .deb-package.
Unfortunately, when installing this debian-package, apt-get complains
about a wrong symlink:
Hmm. There is a symbolic link /lib/modules/3.0.9.mptcp+/build
However, I can not read it: No such
Going to try a make-file patch when I get some time.
The patch was offered from a user on the Xen-user mailing list.
[1] http://lists.xensource.com/archives/html/xen-users/2010-09/msg00396.html
-M
> Subject: make-kpkg (from kernel-package) does not bu
Hello list,
I cannot get make-kpkg to build a Xenlinux type kernel into a Debian kernel
binary on my Debian Squeeze x86_64 system.
I am using GNU/Linux kernel sources tree (2.6.34.4) with Xen patches for this
custom kernel. I am trying to use the make-kpkg command to build a working
linux
Hi Here it fails again. this is version 12.033 instead of 12.032
I downloaded kernel--package-12.033.tar.gz
invoke like this
CONCURRENCY_LEVEL=3 make-kpkg --initrd --append-to-version dickhead1.0
kernel_image kernel_headers
All done in /usr/src/linux-source-2.6.32. I am running kernel
Hi I have using make-kpkg successfully on my amd64 dual core system
until about a month ago.
I did the following:
installed debian testing amd64
apt-get install kernel-package make g++ gcc build-essentail
libncurses5-dev linux-source-2.6.32
and any other files I needed to build a kernel
I
Hi Rob,
>
WARNING: Couldn't open directory
/usr/src/linux-source-2.6.26/debian/linux-image-/lib/modules/2.6.32-live1.0:
No such file or directory
FATAL: Could not open
/usr/src/linux-source-2.6.26/debian/linux-image-/lib/modules/2.6.32-live1.0/modules.dep.temp
for writing: No such file or directo
Mart Frauenlob writes:
>You want to see the output of the build, but the clean process is too
>much? The build output will be multiple times greater anyways. This is
>not a problem over the slow link?
Ok. It looks like you haven't run the latest make-kpkg.
I just did a rebuild
Manoj Srivastava writes:
>On Wed, Apr 07 2010, Cameron Hutchison wrote:
>> Is there any way to make make-kpkg (kernel-package 12.033) quieter? When
>> I run a "make-kpkg clean" it spits out lots of lines about unlinking
>> files in debian/...
>Please f
On Thu, Apr 08 2010, Mart Frauenlob wrote:
> Does v.12.033 always run a 'clean' first?
Yes.
> Mine with lenny v.11.015 does not.
That is one major version ago. Things changed a lot witht he new
major version.
manoj
--
mophobia, n.: Fear of being verbally abused by a
On 08.04.2010 12:12, Cameron Hutchison wrote:
> Mart Frauenlob writes:
>
>> On 08.04.2010 01:59, Cameron Hutchison wrote:
>>> Is there any way to make make-kpkg (kernel-package 12.033) quieter? When
>>> I run a "make-kpkg clean" it spits out lots of l
Mart Frauenlob writes:
>On 08.04.2010 01:59, Cameron Hutchison wrote:
>> Is there any way to make make-kpkg (kernel-package 12.033) quieter? When
>> I run a "make-kpkg clean" it spits out lots of lines about unlinking
>> files in debian/... On a slow link, thi
On 08.04.2010 01:59, Cameron Hutchison wrote:
> Is there any way to make make-kpkg (kernel-package 12.033) quieter? When
> I run a "make-kpkg clean" it spits out lots of lines about unlinking
> files in debian/... On a slow link, this is very annoying (if I forget
> to run sc
On Wed, Apr 07 2010, Cameron Hutchison wrote:
> Is there any way to make make-kpkg (kernel-package 12.033) quieter? When
> I run a "make-kpkg clean" it spits out lots of lines about unlinking
> files in debian/... On a slow link, this is very annoying (if I forget
> to run s
Is there any way to make make-kpkg (kernel-package 12.033) quieter? When
I run a "make-kpkg clean" it spits out lots of lines about unlinking
files in debian/... On a slow link, this is very annoying (if I forget
to run screen)
I have RTFM but I cannot see anything about making make
debian/contol and debian/Control
>
> Both of these files are rewritten when I do a `fakeroot debian/rules
> binary` to build the kernel.
,[ Manual page make-kpkg(1) line 145 ]
| --overlay-dir /path/to/directory
|The specified directory should contain files that will be placed
|
On Tue, Feb 16, 2010 at 03:17:20PM -0500, Cliff Flood wrote:
> On Mon, Feb 15, 2010 at 2:11 AM, Tzafrir Cohen wrote:
> > On Fri, Feb 12, 2010 at 02:36:37PM -0500, Cliff Flood wrote:
> >> Hi,
> >>
> >> I'm having some problems with building ker
On Mon, Feb 15, 2010 at 2:11 AM, Tzafrir Cohen wrote:
> On Fri, Feb 12, 2010 at 02:36:37PM -0500, Cliff Flood wrote:
>> Hi,
>>
>> I'm having some problems with building kernel image packages using
>> `make-kpkg`
>>
>> I'm trying to build
On Fri, Feb 12, 2010 at 02:36:37PM -0500, Cliff Flood wrote:
> Hi,
>
> I'm having some problems with building kernel image packages using `make-kpkg`
>
> I'm trying to build a package with a custom dependency and have tried
> editing the control files generated by m
Hi,
I'm having some problems with building kernel image packages using `make-kpkg`
I'm trying to build a package with a custom dependency and have tried
editing the control files generated by make-kpkg but find that these
changes don't make it into the produced package.
So let
The command is make-kpkg buildpackage. So far, it has never
worked under etch. The build starts out but fails after about a
minute:
CHK include/linux/compile.h
/home/martin/linux-2.6.29/scripts/gen_initramfs_list.sh: Cannot open 'y'
make[3]: *** [usr/initramfs_data.cpio.gz] Erro
Manoj Srivastava wrote:
> On Tue, Dec 09 2008, Stefan Goebel wrote:
>
>> Manoj, should I file a bug report for this or is there something else I
>> can try first?
>
> Thankd for the bug-report and patch; it is always appropriate to
> file a bug on kernel-package when you are experiencing
On Tue, Dec 09 2008, Stefan Goebel wrote:
> Manoj, should I file a bug report for this or is there something else I
> can try first?
Thankd for the bug-report and patch; it is always appropriate to
file a bug on kernel-package when you are experiencing difficulties. At
worst, you'll be
On Tue, Dec 09, 2008 at 01:53:58PM +0100, Stefan Goebel wrote:
> Hi,
>
> I'm trying to build a custom Xen (DomU for now) kernel using the Debian
> sources (i.e. linux-source-2.6.26 (2.6.26-11) with Debian's Xen patches
> from linux-patch-debian-2.6.26 (2.6.26-11)) and kernel-package (11.015),
> on
-debian-2.6.26 (2.6.26-11)) and kernel-package (11.015),
>> on an i386 system running Lenny.
>>
>> Applying the Xen patches with "../kernel-patches/all/2.6.26/apply/debian
>> -a i386 -f xen" works, running "make-kpkg --revision='1.0'
>> --append-
015),
> on an i386 system running Lenny.
>
> Applying the Xen patches with "../kernel-patches/all/2.6.26/apply/debian
> -a i386 -f xen" works, running "make-kpkg --revision='1.0'
> --append-to-version='-foo' kernel_image" does not work, appar
François Cerbelle wrote:
> Le Mar 9 décembre 2008 13:53, Stefan Goebel a écrit :
>> Applying the Xen patches with "../kernel-patches/all/2.6.26/apply/debian
>> -a i386 -f xen" works, running "make-kpkg --revision='1.0'
>> --append-to-version='-foo
Le Mar 9 décembre 2008 13:53, Stefan Goebel a écrit :
> Applying the Xen patches with "../kernel-patches/all/2.6.26/apply/debian
> -a i386 -f xen" works, running "make-kpkg --revision='1.0'
> --append-to-version='-foo' kernel_image" does not work,
"../kernel-patches/all/2.6.26/apply/debian
-a i386 -f xen" works, running "make-kpkg --revision='1.0'
--append-to-version='-foo' kernel_image" does not work, apparently
make-kpkg tries to run "make bzImage" on the kernel sources and there is
"N
etc. saved as .config)
> kernel source# fakeroot make-kpkg --revision=custom.1.0 kernel_image
> kernel source# dpkg -i /home/user/src/linux-image-2.6.27_custom.1.0_amd64.deb
> kernel source# mkinitramfs -o /boot/initrd.img-2.6.27 2.6.27
That last should not be required if you h
t;> The kernel compiles correctly using the usual toolchain provided with
>> the sources but fails on the packaging part using make-kpkg.
>>
>> The compile process gets all the way to the end and fails with
>> debian/stamp/Install: Is a directory
>> The exact comma
On Sun, Oct 12 2008, Adrian Levi wrote:
> I have since tried compiling the kernel in a clean lenny debootstrap
> chroot sucessfully.
> Strangely is was called,
> linux-xenu-2.6.27_2.6.27-10.00.Custom_amd64.deb
>
> But it boots and works, must be a version incompatibility somewhere, I
> still have
the sources but fails on the packaging part using make-kpkg.
>
> The compile process gets all the way to the end and fails with
> debian/stamp/Install: Is a directory
> The exact command line I'm using at the top level linux-2.6.27 direcory is:
> fakeroot make-kpkg --initrd -
2008/10/12 thveillon.debian <[EMAIL PROTECTED]>:
> Adrian Levi a écrit :
>
>> I have since tried compiling the kernel in a clean lenny debootstrap
>> chroot sucessfully.
>> Strangely is was called,
>> linux-xenu-2.6.27_2.6.27-10.00.Custom_amd64.deb
>>
> Maybe you enabled xen support in the config :
Adrian Levi a écrit :
I have since tried compiling the kernel in a clean lenny debootstrap
chroot sucessfully.
Strangely is was called,
linux-xenu-2.6.27_2.6.27-10.00.Custom_amd64.deb
Maybe you enabled xen support in the config : CONFIG_XEN
But it boots and works, must be a version incompati
2008/10/12 thveillon.debian <[EMAIL PROTECTED]>:
> I've used Lenny default for the kernel I'm currently running
> (11.001-something I think), and then tried 11.007 from Sid with good
> results.
> The .config is from my previously home-rolled 2.6.26-6, gcc is Lenny 4.3.2,
> config is nothing fancy,
Adrian Levi a écrit :
But you ended up with a .deb package at the end, Mine is failing
before creating the package.
My installed kernel-package version is 11.007 what was yours?
What did you use for a .config file? Mine is from linux-image-2.6.26
in lenny, answered the few new questions and wen
with Sid newly revised kernel-package for testing (aka
> "fun" !) purpose, the compilation went smoothly, including creation of
> kernel-headers, but I didn't actually try the resulting kernel yet.
>
> I'm on Lenny amd64.
>
> Basically command is :
>
> ma
using make-kpkg.
The compile process gets all the way to the end and fails with
debian/stamp/Install: Is a directory
The exact command line I'm using at the top level linux-2.6.27 direcory is:
fakeroot make-kpkg --initrd --arch amd64 kernel_image
have tried to compile this in etch and lenny wi
gt; the sources but fails on the packaging part using make-kpkg.
Have you tried kernel-package 11.007 from sid?
> The compile process gets all the way to the end and fails with
> debian/stamp/Install: Is a directory
> The exact command line I'm using at the top level linux-2.6.27
on the packaging part using make-kpkg.
>
> The compile process gets all the way to the end and fails with
> debian/stamp/Install: Is a directory
> The exact command line I'm using at the top level linux-2.6.27 direcory is:
> fakeroot make-kpkg --initrd --arch amd64 kernel_image
&
I'm having troubles compiling a vanilla 2.6.27 kernel using
kernel-package. Looks like there is a new iwl4965 driver and I'd like
to try it out.
The kernel compiles correctly using the usual toolchain provided with
the sources but fails on the packaging part using make-kpkg.
The compi
>> setarch i386 make-kpkg --initrd --arch=i386 --revision $revision
>> binary
> Thanks for that info, Steve. However I still cannot get it to work.
Try this:
DEB_HOST_ARCH=i386 make-kpkg --arch i386 --cross_compile - \
--rootcmd fakeroot --initrd --append-to-version mytest ker
gt; package, so I cannot install it on an i386 arch.
> I use this:
> setarch i386 make-kpkg --initrd --arch=i386 --revision $revision binary
Thanks for that info, Steve. However I still cannot get it to work.
When I run make-kpkg with the --arch parameter, it seems to always try
to use
is:
setarch i386 make-kpkg --initrd --arch=i386 --revision $revision binary
That correctly builds an i386 package even on my AMD64 machines.
(Note setarch doesn't seem to be available in the util-linux package
for Etch, so you need to backport it.)
I hope that helps.
Steve
--
Cameron Hutchison <[EMAIL PROTECTED]> writes:
>Cameron Hutchison <[EMAIL PROTECTED]> writes:
>>I am trying to build a kernel for my i386 box on my amd64 host. I want
>>to do this because the amd64 box build at least 10 times faster than the
>>target box.
>>I
Cameron Hutchison <[EMAIL PROTECTED]> writes:
>I am trying to build a kernel for my i386 box on my amd64 host. I want
>to do this because the amd64 box build at least 10 times faster than the
>target box.
>I am using make-kpkg to build the kernel package. I am having the
I am trying to build a kernel for my i386 box on my amd64 host. I want
to do this because the amd64 box build at least 10 times faster than the
target box.
I am using make-kpkg to build the kernel package. I am having the
following problem:
$ make-kpkg --rootcmd fakeroot --arch i386 kernel_image
On Thu, May 08, 2008 at 03:55:22AM -0700, Bill wrote:
> Should there be a include/linux/version.h file in the
> 2.6.25 directory?
if you follow the documentation of kernel-package then make-kpkg will
create it.
If no commands were executed in the 2.6.25 directory tree after creating
On Thu, 2008-08-05 at 06:44 +0200, NN_il_Confusionario wrote:
>
> On Wed, May 07, 2008 at 03:05:37PM -0700, Bill wrote:
> > The UTS Release version in include/linux/version.h
> > ""
> > does not match current version:
> > "2.6.25"
> > Please correct this.
>
> > Any pointers here would
On Wed, May 07, 2008 at 03:05:37PM -0700, Bill wrote:
> The UTS Release version in include/linux/version.h
> ""
> does not match current version:
> "2.6.25"
> Please correct this.
> Any pointers here would be helpful.
It might be a faq about kernel-package, and its documentation in
/u
Hi folks,
I'm trying to compile 2.6.25 using
fakeroot make-kpkg clean
fakeroot make-kpkg modules-clean
The second command terminates with an error as follows:
echo "The UTS Release version in include/linux/version.h"; echo "
\"\" "; echo "does not matc
I made a custom kernel:
make kpkg --revision=.custom.10 --append-to-version=.cybo.1 --initrd
kernel_image
this issued in: linux-image-2.6.25.cybo.1_custom.1.0_amd64.deb
I installed this and wanted to make nvidia modules for it:
make-kpkg modules_image
This issued an error: (para phrased
I have recently switched to debian, and I am trying to learn to compile kernels
the debian way. I need a patch and an external module, so I am trying the
following script:
M="make-kpkg \
--us --uc --initrd \
--append-to-version q4 \
--stem linux \
--added-modules ma
Am 2007-03-17 20:11:57, schrieb dranger003:
>
> Indeed it was the debug causing the issue. After disabling all DEBUG lines
> in the .config the kernel is now of the correct size.
:-)
Thanks, Greetings and nice Day
Michelle Konzack
Systemadministrator
Tamay Dogan Network
Debian G
Indeed it was the debug causing the issue. After disabling all DEBUG lines in
the .config the kernel is now of the correct size.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I have exactly the same problem. Also running Feisty.
I used the following to compile the kernel:
sudo make-kpkg --initrd --append-to-version=-1-Custom kernel_image
kernel_headers
My /lib/modules/$(uname -r) folder is huge as well. All the modules have bigger
than normal sizes - every
Am 2007-03-06 22:04:59, schrieb Matt Price:
> this? the vmlinuz produced by the package is of normal size, but the
> initrd is huge -- 43 megs! -- and /lib/modules/kernel-version-number/ is
> on the order of 530 megs!!!
Sorry, but with the infos you have provided I can not help you.
Please, c
hi
obviously a half-gig-sized kernel package is not optimal, i'd very much
like to figure out what's going on here... also i should say that the
after the build process, the source directory becomes enormous -- 2.7
gigs with ubuntu's 2.6.20 as opposed to a more restrained 700megs back
in the ol
i,
i'm having a problem using make-kpkg to build kernel packages on my
laptop, which runs ubuntu feisty and currently has make-kpkg version
10.065ubuntu4. this happens with upstream, debian, and ubuntu sources,
as far as I can tell, but most of my experimentation has been with
ubuntu&#x
On Thu, Jan 11, 2007 at 10:51:13AM -0700, jdaues wrote:
> Just curious:
> >
> >If you're using a stock debian kernel, why not use the pre-packaged
> >nvidia drivers?
> >
> >Get X working with the nv driver and save that xorg.conf as
> >xorg.conf.nv.
> >
> >Then install the nvidia drivers and run
I'm now sure I know enough to answer your question.
I'm *NOT* sure I know enough
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I'm now sure I know enough to answer your question. I first attempted to
use NVIDIA-Linux-x86-1.0-9746-pkg1.run from here:
http://www.nvidia.com/object/linux_display_ia32_1.0-9746.html
but my graphics card is too old.
Anyways, it is now working at 1024x768. I thinks its capable of more,
though.
e point of this command:
> make-kpkg modules_image
Just curious:
If you're using a stock debian kernel, why not use the pre-packaged
nvidia drivers?
Get X working with the nv driver and save that xorg.conf as
xorg.conf.nv.
Then install the nvidia drivers and run the nvidia-xconfig script t
/Debian_NVIDIA_proprietary_display_driver_installation_through_APT
I get to the point of this command:
make-kpkg modules_image
and i get this message:
The modules_* targets should be called from a fully configured source
tree, and one where at least the make-kpkg debian has been run.
What do I do?
Use
jdaues wrote:
I am following instructions for Debian NVIDIA proprietary display driver
installation through APT here:
http://wiki.serios.net/wiki/Debian_NVIDIA_proprietary_display_driver_installation_through_APT
I get to the point of this command:
make-kpkg modules_image
and i get this
I am following instructions for Debian NVIDIA proprietary display driver
installation through APT here:
http://wiki.serios.net/wiki/Debian_NVIDIA_proprietary_display_driver_installation_through_APT
I get to the point of this command:
make-kpkg modules_image
and i get this message:
The modules_
> > If I exclude [loadable module support] then mkinitramfs-kpkg fails,
> > and if I include it then mkinitramfs-kpkg succeeds.
>
> If you don't need loadable modules, then ... you don't need an init*
> because all the stuff you need is already in the kernel.
On Thu, Jan 04, 2007 at 10:33:20PM +0100, Matt Miller wrote:
> > Using mkinitramfs-kpkg to build the ramdisk.
> > mkinitramfs-kpkg failed to create initrd image.
> > ...
> > I'm guessing that I'm missing something else in
> > menuconfig.
>
>
> Using mkinitramfs-kpkg to build the ramdisk.
> mkinitramfs-kpkg failed to create initrd image.
> ...
> I'm guessing that I'm missing something else in
> menuconfig.
Loadable module support. If I exclude it then
mkinitramfs-kpkg fails, and if I include it then
mkinitr
> > Using mkinitramfs-kpkg to build the ramdisk.
> > mkinitramfs-kpkg failed to create initrd image.
>
> there is an initrd support option in menuconfig
I think I selected the necessary options:
[EMAIL PROTECTED]:/usr/src/linux-source-2.6.18$ grep -i ram .config
CONFI
On Thu, Jan 04, 2007 at 07:35:02PM +0100, Matt Miller wrote:
> Under etch I'm trying to use "dpkg -i" to install a .deb I built using
> make-kpkg. I'm passing "--initrd" to make-kpkg, since I'm booting
> off a software RAID device. I've done thi
Under etch I'm trying to use "dpkg -i" to install a .deb I built using
make-kpkg. I'm passing "--initrd" to make-kpkg, since I'm booting
off a software RAID device. I've done this before on this same
machine without a problem, but this one is giving me:
On 11/27/06, Joey Hess <[EMAIL PROTECTED]> wrote:
Matt Price wrote:
> On a mixed sid/ubuntu-edgy system
!!!
> /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 655.
> dh_gencontrol: Compatibility levels before 4 are deprecated.
> Use of uninitialized value in string eq at
> /usr/share/perl5/Debi
Matt Price wrote:
> On a mixed sid/ubuntu-edgy system
!!!
> /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 655.
> dh_gencontrol: Compatibility levels before 4 are deprecated.
> Use of uninitialized value in string eq at
> /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 655.
> dpkg-gencontrol:
Hi,
On a mixed sid/ubuntu-edgy system I am having errors building the
ubuntu kernels from source. The kernel compile seems to go fine but
there are issues with make-kpkg and dh_* along these lines:
$ sudo make-kpkg --append-to-version=-suspend2 --initrd kernel-image
---[snip
Tommie Van Mechgelen wrote:
Dear,
When I use make-kpkg when loadable module support is disabled, make-kpkg is
generating errors. However compiling it with make works fine.
Here is the error I am getting... Enabling loadable module support makes the
error go away...
I am using kernel-package
Hello,
if i do
make-kpkg kernel_image
and then
dpkg -i
linux-image-2.6.18kay-wlan2_2.6.18kay-wlan2-10.00.Custom_amd64.deb
there is an error:
Missing Required paramater 'Old' at
/var/lib/dpkg/info/linux-image-2.6.18kay-wlan2.postinst line 393
Using a revision tag don't work aroun
Dear,
When I use make-kpkg when loadable module support is disabled, make-kpkg is
generating errors. However compiling it with make works fine.
Here is the error I am getting... Enabling loadable module support makes the
error go away...
I am using kernel-package version: 8.135
test ! -s
Michelle Konzack([EMAIL PROTECTED]) is reported to have said:
> Am 2006-10-03 17:47:26, schrieb Wayne Topa:
> > Hi all
> >
> > I have been trying to find the answer to this problem on and off for
> > a month or so. I can't compile a kernel using kpkg wi
Am 2006-10-03 17:47:26, schrieb Wayne Topa:
> Hi all
>
> I have been trying to find the answer to this problem on and off for
> a month or so. I can't compile a kernel using kpkg without getting
> these errors:
> I have also tried different version of the k
Wayne Topa([EMAIL PROTECTED]) is reported to have said:
> Hi all
>
> I have been trying to find the answer to this problem on and off for
> a month or so. I can't compile a kernel using kpkg without getting
> these errors:
>
> VT3 root-3-ETCH:/usr/src/linu
On 10/03/2006 09:35 PM, Wayne Topa wrote:
Mumia W..([EMAIL PROTECTED]) is reported to have said:
On 10/03/2006 04:47 PM, Wayne Topa wrote:
Hi all
I have been trying to find the answer to this problem on and off for
a month or so. I can't compile a kernel using kpkg without getting
Mumia W..([EMAIL PROTECTED]) is reported to have said:
> On 10/03/2006 04:47 PM, Wayne Topa wrote:
> >Hi all
> >
> > I have been trying to find the answer to this problem on and off for
> > a month or so. I can't compile a kernel using kpkg without getting
> &
On 10/03/2006 04:47 PM, Wayne Topa wrote:
Hi all
I have been trying to find the answer to this problem on and off for
a month or so. I can't compile a kernel using kpkg without getting
these errors:
[...]
Quick question: did you do a "make-kpkg clean" first?
--
[
Hi all
I have been trying to find the answer to this problem on and off for
a month or so. I can't compile a kernel using kpkg without getting
these errors:
VT3 root-3-ETCH:/usr/src/linux-source-2.6.17# make-kpkg --revision
1:buddy.2.2.17 --initrd kernel_image
exec make -f /usr/
Sridhar M.A. wrote:
On Thu, Sep 21, 2006 at 02:49:19PM -0500, Hugo Vanwoerkom wrote:
>
> Suddenly "make-kpkg --revision 1 kernel_image" fails with kernel 2.6.18.
> (attached)
>
> That worked OK with 2.6.17 5 days ago.
>
> Anybody do ma
1 - 100 of 908 matches
Mail list logo
