ikely ;)
>
> Anyway
>
> 1. try vanilla-compile: make mrproper;cp myconfig .config; make bzImage
> 2. try make-kpkg --verbose
Vanilla compilation was better but still failed. However after
increasing memory to 92Mo (and changing the CMOS battery), the problem
is fixed :-)
Thanks
--
M
On Thu, Aug 21, 2008 at 12:26:23AM +0200, Mathieu Peltier wrote:
> old Compaq Presario 1234 Notebook PC (K6 MMX 266 MHz, 32MB RAM, swap
...
> Any idea? Maybe I simply need more memory?
likely ;)
Anyway
1. try vanilla-compile: make mrproper;cp myconfig .config; make bzImage
2. try mak
Hi,
I am trying to recompile the linux kernel (Debian etch 4.0r4) on an
old Compaq Presario 1234 Notebook PC (K6 MMX 266 MHz, 32MB RAM, swap
760MB, wm2 window manager). Even the "make-kpg clean" command seems to
hang:
# cd /usr/src/linux-source-2.6.18
# make-kpkg --verbose clean
ex
Karl Ebener a écrit :
Hi!
I have an IBM Thinkpad R50 and I want to use the tpctl tools. I
installed thinkpad-source and thinkpad-base. As far as I understood it,
when compiling a kernel with make-kpkg, the thinkpad-modules should be
compiles from thinkpad-source "automatically". Unf
On Wed, 09 Mar 2005 16:00:16 +0100, Karl Ebener wrote:
> I have an IBM Thinkpad R50 and I want to use the tpctl tools. I
> installed thinkpad-source and thinkpad-base. As far as I understood it,
> when compiling a kernel with make-kpkg, the thinkpad-modules should be
> compiles f
Karl Ebener wrote:
> Hi!
>
> I have an IBM Thinkpad R50 and I want to use the tpctl tools. I
> installed thinkpad-source and thinkpad-base. As far as I understood it,
> when compiling a kernel with make-kpkg, the thinkpad-modules should be
> compiles from thinkpad-source "a
Hi!
I have an IBM Thinkpad R50 and I want to use the tpctl tools. I
installed thinkpad-source and thinkpad-base. As far as I understood it,
when compiling a kernel with make-kpkg, the thinkpad-modules should be
compiles from thinkpad-source "automatically". Unfortunately, when I execut
This one time, at band camp, Kenneth D. Weinert wrote:
>Followed up on my own post to thank the respondents - somehow it never
>occurred to me that I had to go "outside" make-kpkg to do the
>configuration. Thanks for letting me know that's the right way to do
>it. I
* Kenneth D. Weinert <[EMAIL PROTECTED]> [2003-05-12 04:38] :
> Followed up on my own post to thank the respondents - somehow it never
> occurred to me that I had to go "outside" make-kpkg to do the
> configuration. Thanks for letting me know that's the right way to d
Followed up on my own post to thank the respondents - somehow it never
occurred to me that I had to go "outside" make-kpkg to do the
configuration. Thanks for letting me know that's the right way to do
it. I've built kernels for years now, it's just that this is my fir
he new kernel, but I think I know
> why. I believe that because I installed the bf2.4 kernel and my root
> filesystem is EXT3, when I used make-kpkg I didn't tell it to build
> ext3 in, not use it as a module. So far I've failed to find out how to
> do that.
You are probably rig
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 11 May 2003 08:15 pm, Kenneth D. Weinert wrote:
> Short story - I can't boot into the new kernel, but I think I know
> why. I believe that because I installed the bf2.4 kernel and my root
> filesystem is EXT3, when I used make
y root
filesystem is EXT3, when I used make-kpkg I didn't tell it to build
ext3 in, not use it as a module. So far I've failed to find out how to
do that.
Any help in pointing me in the right direction will be greatly
appreciated.
Thanks in advance.
--
/~\ The ASCIIKen Wein
OK, thanks for that.
I'm really a lazy bugger who would prefer to automate all this stuff. :)
Kevin
On Sun, 09 Feb 2003 23:44:49 -0600
Manoj Srivastava <[EMAIL PROTECTED]> wrote:
> >>"ntrfug" == ntrfug <[EMAIL PROTECTED]> writes:
>
> > The reason the above works is that I've flouted Debian o
OK, thanks for that.
I'm really a lazy bugger who would prefer to automate all this stuff. :)
Kevin
On Sun, 09 Feb 2003 23:44:49 -0600
Manoj Srivastava <[EMAIL PROTECTED]> wrote:
> >>"ntrfug" == ntrfug <[EMAIL PROTECTED]> writes:
>
> > The reason the above works is that I've flouted Debian o
Manoj Srivastava (Montag, 10. Februar 2003 01:09 ) :
> Oww. This looks complicaed, and I am not sure what it buys
> one, as opposed to appending to the version.
Yes, from your point of view, probably you're right.
>From my point, finally I've got 2 commands:
mkern -x to built and instal
>>"ntrfug" == ntrfug <[EMAIL PROTECTED]> writes:
> The reason the above works is that I've flouted Debian orthodoxy and
> defined EXTRAVERSION myself. If I did things the Debian Way, I'd get
> kernel packages with mile-long names and they wouldn't be sorted
> automagically by update-grub.
>>"ntrfug" == ntrfug <[EMAIL PROTECTED]> writes:
>>
>> cd to the directory that you have the kernel sources in, and run
>> /usr/src/kernel-patches/all/apply/xfs. That will "manually" apply
^
>> the patch. See if it spits out any error messages.
>> From
/usr/bin/dh_installkpatches exists.
This script has nothing to do with installing kernel patches
with make-kpkg.
> I have modified /etc/kernel-pkg.conf to include "patch_the_kernel=yes" and
> "config_target=menuconfig".
Hmm. That looks OK too.
> I'
>From /usr/src/linux if I do /usr/src/kernel-patches/all/xfs the message
is:
-bash: /usr/src/kernel-patches/all/xfs is a directory
(I don't get this message when I do make-kpkg.)
Kevin
On Sun, 09 Feb 2003 23:15:01 -0500
Hubert Chan <[EMAIL PROTECTED]> wrote:
> >>
Manoj Srivastava (Montag, 10. Februar 2003 01:09 ) :
> Oww. This looks complicaed, and I am not sure what it buys
> one, as opposed to appending to the version.
Yes, from your point of view, probably you're right.
>From my point, finally I've got 2 commands:
mkern -x to built and instal
>>>>> "ntrfug" == ntrfug <[EMAIL PROTECTED]> writes:
[...]
ntrfug> I've invoked make-kpkg with and without the argument
ntrfug> "--added-patches xfs", and the result is the same -- menuconfig
ntrfug> is called without the patches being a
>>"ntrfug" == ntrfug <[EMAIL PROTECTED]> writes:
> The reason the above works is that I've flouted Debian orthodoxy and
> defined EXTRAVERSION myself. If I did things the Debian Way, I'd get
> kernel packages with mile-long names and they wouldn't be sorted
> automagically by update-grub.
>>"ntrfug" == ntrfug <[EMAIL PROTECTED]> writes:
>>
>> cd to the directory that you have the kernel sources in, and run
>> /usr/src/kernel-patches/all/apply/xfs. That will "manually" apply
^
>> the patch. See if it spits out any error messages.
>> From
/usr/bin/dh_installkpatches exists.
This script has nothing to do with installing kernel patches
with make-kpkg.
> I have modified /etc/kernel-pkg.conf to include "patch_the_kernel=yes" and
> "config_target=menuconfig".
Hmm. That looks OK too.
> I'
>From /usr/src/linux if I do /usr/src/kernel-patches/all/xfs the message
is:
-bash: /usr/src/kernel-patches/all/xfs is a directory
(I don't get this message when I do make-kpkg.)
Kevin
On Sun, 09 Feb 2003 23:15:01 -0500
Hubert Chan <[EMAIL PROTECTED]> wrote:
> >>
>>>>> "ntrfug" == ntrfug <[EMAIL PROTECTED]> writes:
[...]
ntrfug> I've invoked make-kpkg with and without the argument
ntrfug> "--added-patches xfs", and the result is the same -- menuconfig
ntrfug> is called without the patches being a
Perhaps you can help with something else. I'm not able to get kernel
patches applied using make-kpkg.
The package kernel-patch-xfs is installed, and the patches are in
/usr/src/kernel-patches/all/xfs.
The kernel patch script package dh-kpatches is installed, and the sctipt
/us
Kevin
On Sun, 9 Feb 2003 21:23:00 +0100
mi <[EMAIL PROTECTED]> wrote:
> Hi Kevin
> Sound good.
> I didn't know that piece about update-grub. It reads the package
> database then ? I'll do rtfm, also about configuring kernel-kpkg, and
> try something your way :-
>>"mi" == mi <[EMAIL PROTECTED]> writes:
> Since i started compiling different 'flavours' of the same
> kernel-version, i also use symlinks. In my case:
Generally, one uses the --append-to-version option for
make-kpkg to differentiate the images.
>>"mi" == mi <[EMAIL PROTECTED]> writes:
> Since i started compiling different 'flavours' of the same
> kernel-version, i also use symlinks. In my case:
Generally, one uses the --append-to-version option for
make-kpkg to differentiate the images.
>>"ronin2" == ronin2 <[EMAIL PROTECTED]> writes:
> I use make-kpkg to build several versions of a kernel, and this for me is
> much simpler: edit Makefile and define Extraversion as the date, so today
> Extraversion=.0209.
make-kpkg --append-to-version
Perhaps you can help with something else. I'm not able to get kernel
patches applied using make-kpkg.
The package kernel-patch-xfs is installed, and the patches are in
/usr/src/kernel-patches/all/xfs.
The kernel patch script package dh-kpatches is installed, and the sctipt
/us
Kevin
On Sun, 9 Feb 2003 21:23:00 +0100
mi <[EMAIL PROTECTED]> wrote:
> Hi Kevin
> Sound good.
> I didn't know that piece about update-grub. It reads the package
> database then ? I'll do rtfm, also about configuring kernel-kpkg, and
> try something your way :-
>>"mi" == mi <[EMAIL PROTECTED]> writes:
> Since i started compiling different 'flavours' of the same
> kernel-version, i also use symlinks. In my case:
Generally, one uses the --append-to-version option for
make-kpkg to differentiate the images.
>>"mi" == mi <[EMAIL PROTECTED]> writes:
> Since i started compiling different 'flavours' of the same
> kernel-version, i also use symlinks. In my case:
Generally, one uses the --append-to-version option for
make-kpkg to differentiate the images.
>>"ronin2" == ronin2 <[EMAIL PROTECTED]> writes:
> I use make-kpkg to build several versions of a kernel, and this for me is
> much simpler: edit Makefile and define Extraversion as the date, so today
> Extraversion=.0209.
make-kpkg --append-to-version
Hi Kevin
Sound good.
I didn't know that piece about update-grub. It reads the package database
then ? I'll do rtfm, also about configuring kernel-kpkg, and try something
your way :-)
micha.
[EMAIL PROTECTED] schrieb zu Re: make-kpkg, was: Getting PCMCIA to
work?:
> I use make-
> 'System.map' poinitng to /boot/kernel/vmlinuz-2.4.18
Sorry, of course it's /boot/kernel/System.map-2.4.18
> iddles out what's to be done, change kernels with a single command 'kernel
-5'.
..for example.
micha.
I use make-kpkg to build several versions of a kernel, and this for me is
much simpler: edit Makefile and define Extraversion as the date, so today
Extraversion=.0209.
If I made more than one version today I could extend it with .020901 or
something.
This has several desirable consequences:
1
Where did you get this idea? Running make-kpkg initiates the kernel and
modules compilation and packages the results. It can be configured to
construct either a zImage or bzImage kernel.
Kevin
On Sat, 08 Feb 2003 23:42:14 -0600
Manoj Srivastava <[EMAIL PROTECTED]> wrote:
> Can t
.map' poinitng to /boot/kernel/vmlinuz-2.4.18
( well this might be not necessary but else there's an ugly log)
and in /lib/modules:
'2.4.18' pointing to '2.4.18-x'
So, what i have to do for make-kpkg is:
pre install:
unlink '2.4.18' to protect the actual mo
Hi Kevin
Sound good.
I didn't know that piece about update-grub. It reads the package database
then ? I'll do rtfm, also about configuring kernel-kpkg, and try something
your way :-)
micha.
[EMAIL PROTECTED] schrieb zu Re: make-kpkg, was: Getting PCMCIA to
work?:
> I use make-
> 'System.map' poinitng to /boot/kernel/vmlinuz-2.4.18
Sorry, of course it's /boot/kernel/System.map-2.4.18
> iddles out what's to be done, change kernels with a single command 'kernel
-5'.
..for example.
micha.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe"
I use make-kpkg to build several versions of a kernel, and this for me is
much simpler: edit Makefile and define Extraversion as the date, so today
Extraversion=.0209.
If I made more than one version today I could extend it with .020901 or
something.
This has several desirable consequences:
1
Where did you get this idea? Running make-kpkg initiates the kernel and
modules compilation and packages the results. It can be configured to
construct either a zImage or bzImage kernel.
Kevin
On Sat, 08 Feb 2003 23:42:14 -0600
Manoj Srivastava <[EMAIL PROTECTED]> wrote:
> Can t
.map' poinitng to /boot/kernel/vmlinuz-2.4.18
( well this might be not necessary but else there's an ugly log)
and in /lib/modules:
'2.4.18' pointing to '2.4.18-x'
So, what i have to do for make-kpkg is:
pre install:
unlink '2.4.18' to protect the actual mo
>>"Carl" == Carl Baldwin <[EMAIL PROTECTED]> writes:
> Has anyone been successful in compiling a recent kernel with recent
> ACPI patches using make-kpkg.
Can the kernel be compiled using make bZImage? make-kpkg is
merely a thin wrapper on the top that t
>>"Ivar" == Ivar Alm <[EMAIL PROTECTED]> writes:
> For the record, I made my kernels the "Linux way" before, but as I got
> acquainted with make-kpkg, I stick to it. The only modification I need
> is that after the installation of created kernel packag
>>"Carl" == Carl Baldwin <[EMAIL PROTECTED]> writes:
> Has anyone been successful in compiling a recent kernel with recent
> ACPI patches using make-kpkg.
Can the kernel be compiled using make bZImage? make-kpkg is
merely a thin wrapper on the top that t
>>"Ivar" == Ivar Alm <[EMAIL PROTECTED]> writes:
> For the record, I made my kernels the "Linux way" before, but as I got
> acquainted with make-kpkg, I stick to it. The only modification I need
> is that after the installation of created kernel packag
Hi,
Carl Baldwin wrote:
> I am considering going to compiling the kernel from the kernel.org
> sources but I would like to avoid that if possible because I have
> several other patches and extra modules that are really easy to build
> using the make-kpkg system. I don't want to
Has anyone been successful in compiling a recent kernel with recent
ACPI patches using make-kpkg.
I am considering going to compiling the kernel from the kernel.org
sources but I would like to avoid that if possible because I have
several other patches and extra modules that are really easy to
Hi,
Carl Baldwin wrote:
> I am considering going to compiling the kernel from the kernel.org
> sources but I would like to avoid that if possible because I have
> several other patches and extra modules that are really easy to build
> using the make-kpkg system. I don't want to
Saturday 08 February 2003, alle 11:48, Ivar Alm:
: At 08:53 2003-02-08, Manoj Srivastava wrote:
: >>>"Mike" == Mike Leone <[EMAIL PROTECTED]> writes:
: >
: > > Well, it didn't work when I did it the make-kpkg way (I believe I was
: > > following the d
Has anyone been successful in compiling a recent kernel with recent
ACPI patches using make-kpkg.
I am considering going to compiling the kernel from the kernel.org
sources but I would like to avoid that if possible because I have
several other patches and extra modules that are really easy to
Ivar Alm ([EMAIL PROTECTED]) had this to say on 02/08/03 at 06:02:
> For the record, I made my kernels the "Linux way" before, but as I got
> acquainted with make-kpkg, I stick to it. The only modification I need is
> that after the installation of created kernel packag
Saturday 08 February 2003, alle 11:48, Ivar Alm:
: At 08:53 2003-02-08, Manoj Srivastava wrote:
: >>>"Mike" == Mike Leone <[EMAIL PROTECTED]> writes:
: >
: > > Well, it didn't work when I did it the make-kpkg way (I believe I was
: > > following the d
Ivar Alm ([EMAIL PROTECTED]) had this to say on 02/08/03 at 06:02:
> For the record, I made my kernels the "Linux way" before, but as I got
> acquainted with make-kpkg, I stick to it. The only modification I need is
> that after the installation of created kernel packag
At 08:53 2003-02-08, Manoj Srivastava wrote:
>>"Mike" == Mike Leone <[EMAIL PROTECTED]> writes:
> Well, it didn't work when I did it the make-kpkg way (I believe I was
> following the direction on the WIRELESS-LAN-HOWTO). Doing it the standard
> Linux
At 08:53 2003-02-08, Manoj Srivastava wrote:
>>"Mike" == Mike Leone <[EMAIL PROTECTED]> writes:
> Well, it didn't work when I did it the make-kpkg way (I believe I was
> following the direction on the WIRELESS-LAN-HOWTO). Doing it the standard
> Linux way (
I just tried to compile the ALSA modules using
make-kpkg modules_image
at the root of my kernel tree (and with the ALSA src unpacked at the
usual place) and got the following:
Generating debian/modules.d/control.module...done
install debian/modules.d/control-0.5.source debian/control
cat
l
> for the first time. If you make several versions and change the revision
> number (using --revision for make-kpkg) you'll face up with a dependency
> problem: your modules (pcmcia as well as others) will not be adapted to
> your new kernel.
As someone said here, the solution is
l
> for the first time. If you make several versions and change the revision
> number (using --revision for make-kpkg) you'll face up with a dependency
> problem: your modules (pcmcia as well as others) will not be adapted to
> your new kernel.
As someone said here, the solutio
The only danger is not beeing able to load the modules.
But if any problem occurs, one should of course always have a boot disk.
> >
> > [...]
> >
>
> Here's what I do and it works perfectly every time, with 2.2.18:
>
> - Install the kernel source and pcmcia so
The only danger is not beeing able to load the modules.
But if any problem occurs, one should of course always have a boot disk.
> >
> > [...]
> >
>
> Here's what I do and it works perfectly every time, with 2.2.18:
>
> - Install the kernel source and pcmcia so
On Tue, Mar 13, 2001 at 09:30:44AM -0800, Badiane Ka wrote:
> I have created a deb package with make-kpkg and upon
> executing dpkg -i I get a message saying that there is
> conflict between my custom 2.2.18pre1 image and
> pcmcia. How do I compile, install and get a kernel to
> r
On Tue, Mar 13, 2001 at 09:30:44AM -0800, Badiane Ka wrote:
> I have created a deb package with make-kpkg and upon
> executing dpkg -i I get a message saying that there is
> conflict between my custom 2.2.18pre1 image and
> pcmcia. How do I compile, install and get a kernel to
> r
On Tue, Mar 13, 2001 at 04:52:54PM -0400, Peter Cordes wrote:
> On Tue, Mar 13, 2001 at 09:44:47AM -0800, Francois BOTTIN wrote:
> >
> > --- Badiane Ka <[EMAIL PROTECTED]> wrote:
> > > I have created a deb package with make-kpkg and upon
> > > executing dp
On Tue, Mar 13, 2001 at 09:44:47AM -0800, Francois BOTTIN wrote:
>
> --- Badiane Ka <[EMAIL PROTECTED]> wrote:
> > I have created a deb package with make-kpkg and upon
> > executing dpkg -i I get a message saying that there is
> > conflict between my custom 2.2.18p
On Tue, Mar 13, 2001 at 04:52:54PM -0400, Peter Cordes wrote:
> On Tue, Mar 13, 2001 at 09:44:47AM -0800, Francois BOTTIN wrote:
> >
> > --- Badiane Ka <[EMAIL PROTECTED]> wrote:
> > > I have created a deb package with make-kpkg and upon
> > > executing dp
On Tue, Mar 13, 2001 at 09:44:47AM -0800, Francois BOTTIN wrote:
>
> --- Badiane Ka <[EMAIL PROTECTED]> wrote:
> > I have created a deb package with make-kpkg and upon
> > executing dpkg -i I get a message saying that there is
> > conflict between my custom 2.2.18p
--- Badiane Ka <[EMAIL PROTECTED]> wrote:
> I have created a deb package with make-kpkg and upon
> executing dpkg -i I get a message saying that there is
> conflict between my custom 2.2.18pre1 image and
> pcmcia. How do I compile, install and get a kernel to
> run under d
I have created a deb package with make-kpkg and upon
executing dpkg -i I get a message saying that there is
conflict between my custom 2.2.18pre1 image and
pcmcia. How do I compile, install and get a kernel to
run under debian without running into a bunch of
module problems. I would like to be
--- Badiane Ka <[EMAIL PROTECTED]> wrote:
> I have created a deb package with make-kpkg and upon
> executing dpkg -i I get a message saying that there is
> conflict between my custom 2.2.18pre1 image and
> pcmcia. How do I compile, install and get a kernel to
> run under d
I have created a deb package with make-kpkg and upon
executing dpkg -i I get a message saying that there is
conflict between my custom 2.2.18pre1 image and
pcmcia. How do I compile, install and get a kernel to
run under debian without running into a bunch of
module problems. I would like to be
I've just tried compiling pcmcia-source 3.1.22 using make-kpkg but it
fails, telling me:
make[4]: Entering directory `/usr/src/modules/pcmcia-cs/modules'
MD -O2 -Wall -Wstrict-prototypes -pipe -I../include
-I/usr/src/linux/include -D__KERNEL__ -DMODULE -c cs.c
make[4]: MD: Command
I've just tried compiling pcmcia-source 3.1.22 using make-kpkg but it
fails, telling me:
make[4]: Entering directory `/usr/src/modules/pcmcia-cs/modules'
MD -O2 -Wall -Wstrict-prototypes -pipe -I../include
-I/usr/src/linux/include -D__KERNEL__ -DMODULE -c cs.c
make[4]: MD: Command
> >>"Mark" == Mark Phillips <[EMAIL PROTECTED]> writes:
>
> Mark> I think this is the problem. I shouldn't have to do the configuring
> Mark> myself because make-kpkg should do it for me. For some reason it
> Mark> seems that it doesn'
>>"Mark" == Mark Phillips <[EMAIL PROTECTED]> writes:
Mark> I think this is the problem. I shouldn't have to do the configuring
Mark> myself because make-kpkg should do it for me. For some reason it
Mark> seems that it doesn't. It sounds like a bug
the kernel?
I think this is the problem. I shouldn't have to do the configuring
myself because make-kpkg should do it for me. For some reason it
seems that it doesn't. It sounds like a bug with make-kpkg.
I think I have got around it by first using make-kpkg to create a
kernel package
> Well I'm not sure what you've done, but I am using kernel 2.2.15
> (pre19-1) and I have the modversions.h file in:
Yes that's the same version as me (2.2.15pre19-1)
> /usr/src/kernel-source-2.2.15/include/config/modversions.h
> /usr/src/kernel-source-2.2.15/include/linux/modversions.h
Neither
/~pancreas
Work Email: [EMAIL PROTECTED]
On Sun, 30 Apr 2000, Mark Phillips wrote:
> Hi,
>
> I am trying to use make-kpkg to make a pcmcia-modules package for a
> laptop. It quits giving the following error:
>
> /usr/src/linux/include/linux/module.h:19: linux/modve
Hi,
I am trying to use make-kpkg to make a pcmcia-modules package for a
laptop. It quits giving the following error:
/usr/src/linux/include/linux/module.h:19: linux/modversions.h: No such file or
directory
and sure enough, I can't find a file called "modversions.h" anywhere
on
84 matches
Mail list logo
