On 2024-01-10, Herb Garcia wrote:
> Does this method also create the modules?
>> make menuconfig
this one permits you to change kernel parameters if needed
>> make bindeb-pkg
this one compiles kernel and produces
linux-headers-*.deb
linux-image-*.deb
linux-image contains kernel and internal
Does this method also create the modules?
-Herb
On Tue, 2024-01-09 at 13:17 +0100, Michel Verdier wrote:
> On 2024-01-08, Herb Garcia wrote:
>
> > I was able to compile Linux kernel 6.1.X.
> >
> > When I tried compiling kernel 6.5.x and ran into issues.
> >
> > I download the required depen
On 2024-01-09, HP Garcia wrote:
> What dependencies did you install?
All are installed with those commands, thanks Debian :)
apt build-dep linux
apt install build-essential libncurses-dev
(last one for running menuconfig with ncurses)
What dependencies did you install?
~Herb
On Tue, Jan 9, 2024, 7:23 AM Michel Verdier wrote:
> On 2024-01-08, Herb Garcia wrote:
>
> > I was able to compile Linux kernel 6.1.X.
> >
> > When I tried compiling kernel 6.5.x and ran into issues.
> >
> > I download the required dependencies as requir
On 2024-01-08, Herb Garcia wrote:
> I was able to compile Linux kernel 6.1.X.
>
> When I tried compiling kernel 6.5.x and ran into issues.
>
> I download the required dependencies as required per
> https://www.kernel.org/doc/html/v6.7/process/changes.html#changes
To compile 6.5 I do
apt build-
I was able to compile Linux kernel 6.1.X.
When I tried compiling kernel 6.5.x and ran into issues.
I download the required dependencies as required per
https://www.kernel.org/doc/html/v6.7/process/changes.html#changes
I'm just looking to see if I missed any steps. Here is the list of
commands
Hello everybody.
I hope someone can help me out of this (hopefully) simple problem.
Currently iam working on a new kernel (4.12.13) for my debian server.
The kernel compiles fine, the initrd will be created using
mkinitramfs -o /boot/initrd.img-4.12.13 4.12.13
but on a reboot and booting wit
gt; it.
For kernel compiling I followed these instructions:
http://www.debian.org/releases/stable/i386/ch08s06.html.en
It worked like a charm with few modifications.
For general software compiling, just read the corresponding "README"
files before proceeding :-)
Greetings,
--
Camaleó
thanks everyone :)
On Fri, Jan 27, 2012 at 9:30 PM, Stephen Powell wrote:
> On Thu, 26 Jan 2012 14:30:39 -0500 (EST), Ralf Mardorf wrote:
>>
>> I usually run
>>
>> make-kpkg clean
>> make-kpkg --rootcmd fakeroot --initrd kernel-image kernel-headers
>>
>> headers are often needed.
>
> I only build
On Thu, 26 Jan 2012 14:30:39 -0500 (EST), Ralf Mardorf wrote:
>
> I usually run
>
> make-kpkg clean
> make-kpkg --rootcmd fakeroot --initrd kernel-image kernel-headers
>
> headers are often needed.
I only build a headers package if I really need one. Most of the
time I don't. That is one of t
On Thu, 26 Jan 2012 04:54:12 -0500 (EST), Jon Dowland wrote:
> On 25/01/12 23:38, Stephen Powell wrote:
>> Did you use the --initrd option when you invoked make-kpkg?
>
> I thought make-kpkg was deprecated years ago?
> ...
That depends on who you talk to. The kernel team used to use it
to build
On Thu, 2012-01-26 at 14:42 +0100, maderios wrote:
> On 01/25/2012 09:21 PM, Syed Hasan Atizaz wrote:
> > I am able to compile the kernel for i386, however no initial ram disk
> > image is created, i did with the help of mkinitramfs though it was
> > empty, still unable to boot.
> You need both ma
On Thu, 2012-01-26 at 09:55 +, Jon Dowland wrote:
> On 26/01/12 09:38, Lisi wrote:
> > What, in this context, does pae mean?
>
> pae means "physical address extensions", was otherwise known as "bigmem"
> in Debian packaging until recently. It's necessary to
> see/use ≥ 4G of RAM on a 32bit ke
On 01/25/2012 09:21 PM, Syed Hasan Atizaz wrote:
I am able to compile the kernel for i386, however no initial ram disk
image is created, i did with the help of mkinitramfs though it was
empty, still unable to boot.
You need both make-kpkg and initramfs-tools
Then:
make-kpkg kernel_image --initr
On Thursday 26 January 2012 09:55:02 Jon Dowland wrote:
> On 26/01/12 09:38, Lisi wrote:
> > What, in this context, does pae mean?
>
> pae means "physical address extensions", was otherwise known as "bigmem"
> in Debian packaging until recently. It's necessary to
> see/use ≥ 4G of RAM on a 32bit ke
On 26/01/12 09:38, Lisi wrote:
What, in this context, does pae mean?
pae means "physical address extensions", was otherwise known as "bigmem"
in Debian packaging until recently. It's necessary to
see/use ≥ 4G of RAM on a 32bit kernel.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.de
On 25/01/12 23:38, Stephen Powell wrote:
Did you use the --initrd option when you invoked make-kpkg?
I thought make-kpkg was deprecated years ago?
Last time I built a kernel I did via a git clone from the linux git
repository. When I installed it, some magic somewhere automatically
ran mkin
On Wednesday 25 January 2012 15:22:30 kei...@strucktower.com wrote:
> The best tutorial I have found describing the Debian way to compile the
> kernel is Steve Powell's pae:
Just clicked. It is a typo for page. Doh! :-( Considering how many typos I
make, you'd think that I ought to be able to
On Wednesday 25 January 2012 15:22:30 kei...@strucktower.com wrote:
> The best tutorial I have found describing the Debian way to compile the
> kernel is Steve Powell's pae:
What, in this context, does pae mean?
Lisi
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subj
On Wed, 25 Jan 2012 15:21:46 -0500 (EST), Syed Hasan Atizaz wrote:
>
> I am able to compile the kernel for i386, however no initial ram disk
> image is created, i did with the help of mkinitramfs though it was
> empty, still unable to boot.
Did you use the --initrd option when you invoked make-kp
I am able to compile the kernel for i386, however no initial ram disk
image is created, i did with the help of mkinitramfs though it was
empty, still unable to boot.
On Wed, Jan 25, 2012 at 8:27 PM, Syed Hasan Atizaz
wrote:
> isnt it suppose to be
>
> /boot/config-$(uname -r) .config ?
> plus wha
The best tutorial I have found describing the Debian way to compile the
kernel is Steve Powell's pae:
http://users.wowway.com/~zlinuxman/Kernel.htm
There are lots of others, just google around, but be wary of older pages
and read Steve's page first.
I have no idea how using virtual box may affec
isnt it suppose to be
/boot/config-$(uname -r) .config ?
plus what type of configuration it stores ? just curious.
On Wed, Jan 25, 2012 at 8:22 PM, wrote:
> The best tutorial I have found describing the Debian way to compile the
> kernel is Steve Powell's pae:
>
> http://users.wowway.com/~zlinu
On 25/01/12 10:40, Syed Hasan Atizaz wrote:
I like to know where can i get the information in detail for compiling
kernel, loading modules and installing programs from scratch. i never
did it before. I installed virtual box recently and looking to play
with it.
Download the kernel sources from
Hello
I like to know where can i get the information in detail for compiling
kernel, loading modules and installing programs from scratch. i never
did it before. I installed virtual box recently and looking to play
with it.
Thank you
Syed Hasan Atizaz
--
To UNSUBSCRIBE, email to debian-user-requ
Hi again
I found three choices to get my PVR-500 to work properly on Squeeze
(2.6.32-5-amd64):
The first option would be installing at least 2.6.37-4-amd64. This
kernel should be a stable release where the ivtv patch is applied
(Commit 0ab29c52f9efdd645d565f8be3915183819a6c3e).
I found this
Wackojacko wrote:
Arthur Marsh wrote:
bzip2 -dc linux-source-2.6.17.tar.bz2|tar -xvf /dev/fd/0
bzip2 -dc alsa-driver.tar.bz2|tar -xvf /dev/fd/0
bzip2 -dc realtime-lsm.tar.bz2|tar -xvf /dev/fd/0
Minor point but this can be done in one step with
tar -xvjf filename.tar.bz2
or
tar -xvzf filename
Arthur Marsh wrote:
bzip2 -dc linux-source-2.6.17.tar.bz2|tar -xvf /dev/fd/0
bzip2 -dc alsa-driver.tar.bz2|tar -xvf /dev/fd/0
bzip2 -dc realtime-lsm.tar.bz2|tar -xvf /dev/fd/0
Minor point but this can be done in one step with
tar -xvjf filename.tar.bz2
or
tar -xvzf filename.tar.gz
see man ta
On Sun, Jul 30, 2006 at 06:46:53 -0400, Chuckk Hubbard wrote:
> Thank you so much. But...
>
> On 7/30/06, Arthur Marsh <[EMAIL PROTECTED]> wrote:
> >At the end, assuming that you had all the required disk space and
> >packages, you have a package created:
> >
> >/usr/src/linux-image-2.6.17_2.6.17
Thank you so much. But...
On 7/30/06, Arthur Marsh <[EMAIL PROTECTED]> wrote:
At the end, assuming that you had all the required disk space and
packages, you have a package created:
/usr/src/linux-image-2.6.17_2.6.17-10.00.Custom_i386.deb
This can be installed using:
dpkg -i /usr/src/linux-i
Chuckk Hubbard wrote:
On 7/24/06, John O'Hagan <[EMAIL PROTECTED]> wrote:
My suggestion would be to google for some recent and more Debian-specific
kernel-compile how-to's; for example, using make-kpkg makes it a lot
simpler
by making a .deb kernel package you can then install just like a reg
On 7/24/06, John O'Hagan <[EMAIL PROTECTED]> wrote:
My suggestion would be to google for some recent and more Debian-specific
kernel-compile how-to's; for example, using make-kpkg makes it a lot simpler
by making a .deb kernel package you can then install just like a regular
package. You do have
On Monday 24 July 2006 09:13, Chuckk Hubbard wrote:
> I just stumbled on these instructions:
> http://www.linuxplanet.com/linuxplanet/tutorials/202/1/
>
> I'm mainly interested in fixing my kernel timer resolution to be fine
> enough for Rosegarden MIDI, but I'm curious about kernel making all
> th
I just stumbled on these instructions:
http://www.linuxplanet.com/linuxplanet/tutorials/202/1/
I'm mainly interested in fixing my kernel timer resolution to be fine
enough for Rosegarden MIDI, but I'm curious about kernel making all
the same.
I'm using the AGNULA 2.6.14-1-multimedia kernel header
On Fri, Mar 31, 2006 at 06:57:29PM +0530, Sridhar M.A. wrote:
> On Thu, Mar 30, 2006 at 10:14:15PM -0600, Matthew R. Dempsky wrote:
>> On Fri, Mar 31, 2006 at 07:38:04AM +0530, Sridhar M.A. wrote:
>> > CC sound/soundcore.mod.o
>> > LD [M] sound/soundcore.ko
>> >
On Thu, Mar 30, 2006 at 10:14:15PM -0600, Matthew R. Dempsky wrote:
> On Fri, Mar 31, 2006 at 07:38:04AM +0530, Sridhar M.A. wrote:
> > CC sound/soundcore.mod.o
> > LD [M] sound/soundcore.ko
> > make[1]: Leaving directory `/home/software/kernel/linux-2.6.16'
> > COLUMNS=150 dpk
On Fri, Mar 31, 2006 at 07:38:04AM +0530, Sridhar M.A. wrote:
> CC sound/soundcore.mod.o
> LD [M] sound/soundcore.ko
> make[1]: Leaving directory `/home/software/kernel/linux-2.6.16'
> COLUMNS=150 dpkg -l 'gcc*' perl dpkg 'libc6*' binutils ldso make dpkg-dev |\
> awk '$1 ~ /[hi]i/ {
Hi,
I am running debian sarge on an AMD-Athlon machine. The kernel is 2.6.16
which I compiled from the vanilla source.
Yesterday I wanted to add a couple of modules and so had to recompile.
But, now the process is ending with the following error message:
...
CC sound/soundcore.mod.o
LD [M]
Trying to do my first kernel compile because my nic isn't supported on
any of the ones on the distribution CD's. Anyway I have an onboard
Broadcom 4401. When I run make menuconfig it isn't listed but a Tigon
9 is.
1) Is the Tigon 9 the name of the boxed-plugin card with the same
chipset IOW is t
> portion mine wasn't listed. I have the source from the manufacturer.
> How do I add that to the mix?
Just compile the manufacturers source as a module after you finish
compiling the kernel and load in at boot up by adding it to
/etc/modules.
>
>
> Mark Healey
> [EMAIL PROTECTED]
>
> Giving
Preamble: I no working networking or X please don't send suggestions
that require those to be working.
I'm going to go through Kents 10 step procedure to compiling the linux
kernel. I ran into trouble at step 7. I was pretty much taking the
default questions I don't understand. Anyway when it
a proper
.deb, it should work fine. As root, of course.
> A quick view at the messages this morning told me about problems with modules,
> and an info were given that modules will be moved to another directory but I don't
> remember further details exactly now.
I'm almost cer
-i /usr/src/kernel-image-2.4.20_10.00.Custom_i386.deb
won't succeed too.
A quick view at the messages this morning told me about problems with modules,
and an info were given that modules will be moved to another directory but I don't
remember further details exactly now.
Does anyone
Hi I compiled kernel 2.4.18 on Compaq Evo N1015v but I couldn't make the
sound and the
CDROM to work at the same time (it I compile the sound module the CDROM
will not work).
When looking in the output of dmseg I that I have some IRQ conflicts but I
couldn't understand
what devices are conflicts.
H
You know, I'm attaching it as is, but as far as I can tell each custom
kernel boot never event got to the point where it started logging.
Joachim Fahnenmueller wrote:
Hi Curtis,
your procedure seems ok. Can you boot with the previous kernel? If so, look for
the messages on booting the new ke
Hi Curtis,
your procedure seems ok. Can you boot with the previous kernel? If so, look for
the messages on booting the new kernel (e. g. /var/log/kern.log) and maybe post
these.
Regards, Joachim
On Wed, May 08, 2002 at 05:31:04PM -0700, curtis wrote:
> Ok, here I go again!
>
> I am trying t
Ok, here I go again!
I am trying to compile a kernel with FreeS/WAN.
Here are the procedures I have followed, but after completing them on
the reboot my computer starts the loading process and then reboots over
and over, ad nauseam.
I downloaded FreeSWAN source and kernel-source-2.4.18
add
Romuald DELAVERGNE <[EMAIL PROTECTED]> writes:
> Le 2001.10.17 02:49, Glyn Millington a écrit :
>> bash-2.03$ make-kpkg clean
>> dpkg: warning, architecture `i386-none' not in remapping table
>
> 'make-kpkg' from potato have problem.
> Use 'make-kpkg' from woody.
Many thanks - that did the tric
Le 2001.10.17 02:49, Glyn Millington a écrit :
>
> I've replaced all sorts of goodies on my home machine - above all the CPU
> which is now a Duron 900. I'm trying to recompile the 2.2.17 kernel
> source for sound support but don't get far. _Whichever_ processor family
> I go for (even 386) I ge
I've replaced all sorts of goodies on my home machine - above all the CPU
which is now a Duron 900. I'm trying to recompile the 2.2.17 kernel
source for sound support but don't get far. _Whichever_ processor family
I go for (even 386) I get this error message at make-kpkg clean
Hi Kurdt,
I have no idea what is wrong. Anyway, I have a similar system and recently
compiled a 2.4.10 kernel, using the debian kernel source package. I also
included ac97_codec support and it works quite well.
Regards,
Joachim
--
Joachim Fahnenmüller
Lehrer für Mathematik und Physik
Herder
Craig Dickson <[EMAIL PROTECTED]> writes:
> Brian Nelson wrote:
> > Also, it's usually advisable to use the debian kernel packages rather
> > than the kernel.org sources.
>
> I see no reason to prefer the debian-packaged kernel sources. They
> usually differ only in very minor ways, adding a few
Brian Nelson wrote:
> That's an upstream kernel source problem, which I think is supposed to
> be fixed in 2.4.17.
It isn't, at least not completely. There have been several reports on
this list of people failing to build 2.4.17 with similar errors. The
problem appears to be highly dependent on t
Kurdt <[EMAIL PROTECTED]> writes:
> Hi
>
> My debian woody is now working a few weeks. Some things don't work
> yet. Like my sound. Most describings say to compile my kernel with the
> new soundmodule enabled. I downloaded the latest stable kernel on
> kernel.org
> So far, I untar in /usr/src/l
Hi
My debian woody is now working a few weeks. Some things don't work yet.
Like my sound. Most describings say to compile my kernel with the new
soundmodule enabled. I downloaded the latest stable kernel on kernel.org
So far, I untar in /usr/src/linux, do a make menuconfig (or make
xconfig),
Yes,
exactly what I am thinking so I disabled the initrd support works much better for me thank you
Oliver
On Sonntag, 16. Dez. 2001 at 14:59:02, [EMAIL PROTECTED] wrote:
>is there a special procedure compiling a debian kernel-image (with make-kpkg)
>with initrd support and is it worth to handle it with this support. I don't
>receive the right information from the kernel-initrd-documentation.
Hello Ol
Hi,
is there a special procedure compiling a debian kernel-image (with make-kpkg) with initrd support and is it worth to handle it with this support. I don't receive the right information from the kernel-initrd-documentation.
Oliver
for any who are curious:
http://goats.gnue.org/~chillywilly/debian-kernel-mini-howto.txt
happy hacking
-jeff
--
Q: Why do ducks have big flat feet?
A: To stamp out forest fires.
Q: Why do elephants have big flat feet?
A: To stamp out flaming ducks.
On Tue, Aug 07, 2001 at 12:29:44PM -0300, GARGIULO Eduardo INGDESI muttered:
--> > > > I'd performed a clean woody installation from CDs and added
--> > > > kernel-package to compile 2.4.4 kernel. I'd followed the
Care to mention a few good and inexpensive web sites for ordering a
woody CD?
--
> > > I'd performed a clean woody installation from CDs and added
> > > kernel-package to compile 2.4.4 kernel. I'd followed the
> steps from
> > > kernel-package documentation and after make-kpkg without
> errors, there
> > > was not any .deb file!!??? Which could be my error? How
> can I solve
On Tue, Aug 07, 2001 at 08:47:39AM -0500, Brendon Colby wrote:
> On Tue, Aug 07, 2001 at 09:17:21AM -0300, GARGIULO Eduardo INGDESI wrote:
> > Hi all.
> >
> > I'd performed a clean woody installation from CDs and added
> > kernel-package to compile 2.4.4 kernel. I'd followed the steps from
> > ker
>kernel-package documentation and after make-kpkg without errors, there
>was not any .deb file!!??? Which could be my error? How can I solve it?
>
In a lot of ways, the boring old make..make bzlilo way of doing kernels
offers an easier way because every linux howto on the web covers it.
Patrick
On Tue, Aug 07, 2001 at 09:17:21AM -0300, GARGIULO Eduardo INGDESI wrote:
> Hi all.
>
> I'd performed a clean woody installation from CDs and added
> kernel-package to compile 2.4.4 kernel. I'd followed the steps from
> kernel-package documentation and after make-kpkg without errors, there
> was n
Hi all.
I'd performed a clean woody installation from CDs and added
kernel-package to compile 2.4.4 kernel. I'd followed the steps from
kernel-package documentation and after make-kpkg without errors, there
was not any .deb file!!??? Which could be my error? How can I solve it?
--ejg:wq!
On Monday 23 April 2001 12:28, Sebastiaan wrote:
>
> Perhaps you have mentioned it somewhere, but it may be worthy noting that
> you can compile kernels on a fast machine for a slower machine (with the
> correct config files), copy the .deb file and install the package on the
> slower machine.
Th
On Sunday 22 April 2001 11:26, Jesse Goerz wrote:
> I wrote a basic document intended to help Debian newbies compile custom
> kernels using kernel-package. I'd really appreciate any and all comments,
> suggestions, additions, subtractions you may have. (constructive
> welcomed, the rest accepted)
Hi,
I must say, it is a very exhaustive document, but I think detailed enough
for a newbie, BUT:
everything you describe, is done as root. This is not needed, and
certainly for newbies somewhat dangerous. I would do the following:
As root:
- install kernel source with apt
- addgroup src (this giv
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 22 April 2001 08:13, David Raeker-Jordan wrote:
> Jesse
>
> In "Making sure you have everything you need," you wrote:
>
> "This should create a directory called kernel-source-2.2.19. Inside that
> directory you should find another called Docu
On Sun, Apr 22, 2001 at 05:26:01AM -0400, Jesse Goerz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I wrote a basic document intended to help Debian newbies compile custom
> kernels using kernel-package. I'd really appreciate any and all comments,
> suggestions, additions, subtra
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I wrote a basic document intended to help Debian newbies compile custom
kernels using kernel-package. I'd really appreciate any and all comments,
suggestions, additions, subtractions you may have. (constructive
welcomed, the rest accepted)
You ca
You need to compile in any capabilities required for boot. For
example, if you have a SCSI only system, the appropriate SCSI
capabilities need to be compiled into the kernel.
Other capabilities you might want to compile in are items that you know
the kernel will be using. For example, if you k
Hi Jimmy,
Thanks for your email. Therefore, is it generally safe to compile
everything as a module (given that the option exists)?
Thanks,
Bryan
On Mon, Apr 02, 2001 at 02:43:52PM -0600, Jimmy Richards wrote:
> Hi Bryan,
>
> The main advantage is the when you compile something as
Hi Bryan,
The main advantage is the when you compile something as a module it
does not
take up any memory unless it gets loaded by the kernel. If you compile
something into the kernel then it gets loaded into memory as part of the
kernel since it is part of the kernel. For instance, yo
I am sure that there are many different ideas on this topic, and would like
to here people's thoughts. When compiling kernels, I can compile many
things into the kernel. But I often have the option to compile many things
as a module.
What are the pros and cons of compiling things as modul
Hi Stefan,
Quoth Stefan Srdic,
> My goal is to compile a kernel which performs greatly but is also very
> small with only the basic requirements compiled into the kernel and
> everything else compiled as modules.
Sometimes the way the system is set up makes it a little redundant to
compile thing
I got the source, I've read some of the kernel documentation, now its
time to compile this thing.
I've got a few questions though. Currently I'm running Debian 2.2 with
Helix Gnome and XFree86-4.0.2. I'm running this self-modified distro on
a Asus K7M mobo with an Athlon 550Mhz cpu/128MB of RAM.
Correct. Install kernel-package and take a look at
/usr/share/doc/kernel-package/README.gz. There is a recommendation
there to use an epoch when creating your package, which will prevent it
from being overwritten during an upgrade.
For your question regarding CD-Writing, I would recommend that y
Is this part of "kernel-package" ?? I just looked at it in aptitude and it does
appear so.
Reason I want to recompile is that vmlinuz is over 1mb in size, so it
apparently has a lot compiled in, instead of modules. My older, customer
kernels were usually less than 500k. I see on bootup, or via
What is the "debian way" of compiling a kernel ?? I've read mentions of
using something like "kernel-pkg" or similar. Can someone point to a
website with details ?? Or, can I simply download the kernel source and
do it the way I've always done it with "lesser" distros ;-) ??
Thanks in advance
Hall
On Sat, Dec 09, 2000 at 04:10:45PM -0800, Nick wrote:
> what packages are needed to compile a kernel
>
> after make menuconfig
> i get the following error:
>
> lxdialog.o Error 1
>
> something about curses.h
>
> any idea? thanks -nick
>
Perhaps this: (dialog)
ProteoTien:/# dpkg -l | grep d
try installing libncuses5-dev
On Sat, Dec 09, 2000 at 04:10:45PM -0800, Nick wrote:
> what packages are needed to compile a kernel
>
> after make menuconfig
> i get the following error:
>
> lxdialog.o Error 1
>
> something about curses.h
>
> any idea? thanks -nick
>
>
> --
> To UNSUBSCRIBE
what packages are needed to compile a kernel
after make menuconfig
i get the following error:
lxdialog.o Error 1
something about curses.h
any idea? thanks -nick
On Dec 05 2000, Ethan Benson wrote:
> just to toss my personal preference in... i created a dedicated
> user account for building things like kernels and locally installed
> software
I did something similar to this, but not only to build things.
I use a dummy user for evaluating p
On Wed, Dec 06, 2000 at 12:29:55AM +0100, paolo massei wrote:
>
> Is there a reason to copy /tmp/kernel_image in /home/user/ before installing?
> and
yes, when you reboot everything in /tmp is deleted, you may want to
keep the .deb around in which case you must move it out of /tmp
> Do you know
On Tue, Dec 05, 2000 at 07:53:30PM +0100, Sebastiaan wrote:
> Hi,
> I have read a very different way to compile a new kernel.
>
> $ cd /tmp
> $ tar -xIvf /usr/src/kernel-souce-2.2.17.tar.bz2
> $ c cd 2.2.17
> $ make-kpkg clean
> $ make menuconfig
> $ fakeroot make-kpkg --revision=9:mykernel kerne
Hi,
I have read a very different way to compile a new kernel.
$ cd /tmp
$ tar -xIvf /usr/src/kernel-souce-2.2.17.tar.bz2
$ c cd 2.2.17
$ make-kpkg clean
$ make menuconfig
$ fakeroot make-kpkg --revision=9:mykernel kernel_image
If it is correct, there is a net .deb packet in /tmp:
cp /tmp/kernel-
On Tue, Dec 05, 2000 at 06:03:16PM +0100, paolo massei wrote:
> I read sometimes ago in this list that i can compile my custom-kernel
> being an ordinary user and not using root account (before installing it);
> well, when i try run "make *config" in /usr/src/linux directory,
> i receive this erro
I read sometimes ago in this list that i can compile my custom-kernel
being an ordinary user and not using root account (before installing it);
well, when i try run "make *config" in /usr/src/linux directory,
i receive this error message:
bash-2.03$ make xconfig
rm -f include/asm
rm: impossibile
Jonathan,
I think you should be fine with gcc 2.95.2 but maybe you'd be safer
with 2.91.66 if you can get it as easily. You should know, though,
that I'm not at all an expert in these areas. The only time I've
recompiled my kernel was linux-2.2.17pre20 using gcc 2.95.2 on my only
non-Debian box
Hi,
Thanks for getting back to me. I've gotten a coupple getting back to me
saying I do it and I've had no problems. I was looking for someone who knows
why Debian wrote that up and if the problem's been resolved so it's no
longer the case... I don't want to have to recompile if I don't have to. D
Hello!
I've always compiled my kernels with gcc295 for over a year now and never
run into problems. Seems to work.
Regards,
Stephan
- Original Message -
From: "Jonathan Gift" <[EMAIL PROTECTED]>
To: "Debian"
Sent: Tuesday, November 14, 2000 8:45 PM
Sub
According to kernel traffic this week (kt.linuxcare.com), if my memory
serves, gcc272 will _not_ properly compile the newest kernels, even
though the documents explicitly states that gcc272 is in fact the most
compatible compiler. Further searching of the kernel mailing lists
could probably dig up
On Tue, Nov 14, 2000 at 08:45:50PM +0100, Jonathan Gift wrote:
> Hi,
>
> I recently compiled my kernel. However, reading through the docs that came
> with gcc it says clearly that compiling the kernel should be done with
> gcc272 and not gcc295. I had gcc295 loaded by tasksel and the fine print
>
Hi,
I recently compiled my kernel. However, reading through the docs that came
with gcc it says clearly that compiling the kernel should be done with
gcc272 and not gcc295. I had gcc295 loaded by tasksel and the fine print
said not to worry if you had gcc295 because if you used the kernel-pacage i
thx to mr. norris, my problem is fixed.
bentley taylor.
//
"Gregory T. Norris" wrote:
> Make sure you have libncurses[45]-dev installed...
>
> On Mon, Sep 11, 2000 at 06:26:08PM -0600, cls-colo spgs wrote:
> > debs,
> >
> > my deskbox likes the taste of kernel 2.2.17; but my
> > lapbox is getti
Make sure you have libncurses[45]-dev installed...
On Mon, Sep 11, 2000 at 06:26:08PM -0600, cls-colo spgs wrote:
> debs,
>
> my deskbox likes the taste of kernel 2.2.17; but my
> lapbox is getting stuck:
>
> Script started on Mon Sep 11 17:53:15 2000
> EBUSINESS:/tmp/linux# makemenu
debs,
my deskbox likes the taste of kernel 2.2.17; but my
lapbox is getting stuck:
Script started on Mon Sep 11 17:53:15 2000
EBUSINESS:/tmp/linux# makemenu menuconfig
rm -f include/asm
( cd include ; ln -sf asm-i386 asm)
make -C scripts/lxdialog all
make[1]: Entering directory
`/tmp/
On Sun, Sep 10, 2000 at 09:59:13PM +0400, Rino Mardo wrote:
> for me i'd rename it to /lib/modules/2.2.17-old in case i need 'em back ;-)
Actually, I do the same, until I get the new kernel tested and working.
Otherwise, in cases where I go from one version to another, like
2.2.15-2.2.17, I woul
twork Systems
e-mail: mailto:[EMAIL PROTECTED]
Visit us at: http://www.astro.com.my
- -Original Message-
From: Gutierrez Family [SMTP:[EMAIL PROTECTED]
Sent: Sunday, September 10, 2000 8:23 AM
To: debian-user@lists.debian.org
Subject:Weird messages after kernel compiling...
1 - 100 of 152 matches
Mail list logo
