Hi to Everyone,
With my old SARGE system, as stated here last week, I was unable to boot
newly compiled kernels, most likely because of the faulty initrd.img
that I got using 'mkinitrd'. For this reason, I decided to install
Lenny.
Now, with Lenny, I haven't so far been able to go any further
bdebreil 写道:
Hi to Everyone,
With my old SARGE system, as stated here last week, I was unable to boot
newly compiled kernels, most likely because of the faulty initrd.img
that I got using 'mkinitrd'. For this reason, I decided to install
Lenny.
Now, with Lenny, I haven't so far been able to go
On Fri, 28 Aug 2009 19:07:45 +0800
Niu Kun haoniu...@gmail.com wrote:
bdebreil 写道:
...
Now, with Lenny, I haven't so far been able to go any further in
recompiling usable kernels. 2.6.30.4 did compile without errors, but
then I found that I had no 'mkinitrd' on my new system. How am I to
On Fri, Aug 28 2009, Celejar wrote:
Assuming that you're building kernel packages with kernel-package, you
may be being hit by this:
The image postinst no longer runs the initramfs creation commands.
Instead, there are example scripts provided that will perform the task.
These scripts will
Hi list,
there is one thing I never did before and that is compiling a kernel.
I've got an old 266er dual board and would like to compile the kernel that
it will also use the second cpu, in addition to that I'd like to use lvm-mod and
the LVM10, so that I can build logical volume groups.
Jens Simmoleit wrote:
Hi list,
there is one thing I never did before and that is compiling a kernel.
I've got an old 266er dual board and would like to compile the kernel
that it will also use the second cpu, in addition to that I'd like to
use lvm-mod and the LVM10, so that I can build
new kernel
Jens Simmoleit wrote:
Hi list,
there is one thing I never did before and that is compiling a kernel.
I've got an old 266er dual board and would like to compile the kernel
that it will also use the second cpu, in addition to that I'd like to
use lvm-mod and the LVM10, so
Jens Simmoleit simmel at anymotion.de writes:
Does somebody know a really good Howto, which explains how
to compile a kernel step by step?
Yes, check the Kernel Compiling How-to at the Newbiedoc project:
http://newbiedoc.sourceforge.net
--M. Kirchhoff
--
To UNSUBSCRIBE, email to [EMAIL
Travis Crump wrote:
As I wrote above, some instructions suggest deleting it and recreating
it to my new kernel directory. So if I do not have it, I was wondering
if I should create it (of course I cannot recreate it).
In any case, I was also expecting someone who says I *should* have
that
sön 2003-12-07 klockan 00.11 skrev H. S.:
Hi,
While doing a google search to read pages on who to compile a new Linux
kernel the Debian way, I see some of them mentioning that I should first
delete a symlink linux in /usr/src if it exists before I untar and
unzip a download kernel file,
Markku Kellberg wrote:
sön 2003-12-07 klockan 00.11 skrev H. S.:
Hi,
While doing a google search to read pages on who to compile a new Linux
kernel the Debian way, I see some of them mentioning that I should first
delete a symlink linux in /usr/src if it exists before I untar and
unzip a
Hi,
While doing a google search to read pages on who to compile a new Linux
kernel the Debian way, I see some of them mentioning that I should first
delete a symlink linux in /usr/src if it exists before I untar and
unzip a download kernel file, and then recreate it. Some pages do not
suggest
Em Sat, 06 Dec 2003 18:11:13 -0500, H. S. escreveu:
some of them mentioning that I should first
delete a symlink linux in /usr/src if it exists before I untar and unzip
a download kernel file, and then recreate it. Some pages do not suggest
this. Is this a step crucial?
[...]
clean, then
Leandro Guimares Faria Corsetti Dutra wrote:
Em Sat, 06 Dec 2003 18:11:13 -0500, H. S. escreveu:
some of them mentioning that I should first
delete a symlink linux in /usr/src if it exists before I untar and unzip
a download kernel file, and then recreate it. Some pages do not suggest
this. Is
H. S. [EMAIL PROTECTED] writes:
While doing a google search to read pages on who to compile a new
Linux kernel the Debian way, I see some of them mentioning that I
should first delete a symlink linux in /usr/src if it exists before
I untar and unzip a download kernel file, and then recreate
Björn Lindström wrote:
H. S. [EMAIL PROTECTED] writes:
While doing a google search to read pages on who to compile a new
Linux kernel the Debian way, I see some of them mentioning that I
should first delete a symlink linux in /usr/src if it exists before
I untar and unzip a download kernel file,
H. S. wrote:
Leandro Guimares Faria Corsetti Dutra wrote:
Em Sat, 06 Dec 2003 18:11:13 -0500, H. S. escreveu:
some of them mentioning that I should first
delete a symlink linux in /usr/src if it exists before I untar and
unzip
a download kernel file, and then recreate it. Some pages do not
H. S. [EMAIL PROTECTED] writes:
I guess I am missing something here. I have a file
kernel-source-2.4.22.tar.bz2 in /usr/src, and when I do:
{src} tar -jtf kernel-source-2.4.22.tar.bz2
I get the listing as:
{src} tar -jtf kernel-source-2.4.22.tar.bz2
kernel-source-2.4.22/
Alex Malinovich [EMAIL PROTECTED] writes:
I've been rolling my own kernel using make-kpkg and the other wonderful
tools we Debianites have at our disposal for over a year now, yet
something just occured to me. Is it possible to compile individual
kernel modules outside of the actual kernel
I've been rolling my own kernel using make-kpkg and the other wonderful
tools we Debianites have at our disposal for over a year now, yet
something just occured to me. Is it possible to compile individual
kernel modules outside of the actual kernel compilation? I still have
the full source
Alex Malinovich wrote:
I've been rolling my own kernel using make-kpkg and the other wonderful
tools we Debianites have at our disposal for over a year now, yet
something just occured to me. Is it possible to compile individual
kernel modules outside of the actual kernel compilation? I still have
: Thursday, July 12, 2001 4:22 AM
Subject: Re: weird problem with init after compiling new kernel
Did you ever find a solution to this problem? I'm having a similar
problem with a Pentium system. If you did find a solution, could you
please let me know what it was? Thanks,
Peter
On Mon, Jun 11, 2001 at 12:45:03AM +0200, Mythiq wrote:
hello everyone,
I have compiled a new kernel for an 486 which was going to be a filtering
firewall. Not for a while I'm afraid, because it won't boot up anymore. (btw:
I started with a clean freshly installed system with debian
configuration.
??que?? I'm confused of this.
Help!
Mythiq.
- Original Message -
From: ktb [EMAIL PROTECTED]
To: debian-user@lists.debian.org
Sent: Monday, June 11, 2001 8:58 AM
Subject: Re: weird problem with init after compiling new kernel
On Mon, Jun 11, 2001 at 12:45:03AM +0200, Mythiq wrote
Wouter == Wouter Bakker [EMAIL PROTECTED] writes:
Wouter to try and make things a little more clear: the kernel boots!
Wouter Lilo works fine! it is the init part where all activity halts
Wouter at the point where normally the supplementary hardware (sound,
Wouter network, mice, special
hello everyone,
I have compiled a new kernel for an 486 which was
going to be a filtering firewall. Not for a while I'm afraid, because it won't
boot up anymore. (btw: I started with a clean freshly installed system with
debian 2.2.18pre21)
Lilo works fine; it boots the kernel;
after the
hi
it worked thanks
Yes I had to enable CONFIG_EKSPERIMENTAL
/jens
On Wed, 13 Dec 2000, Erik Steffl wrote:
seach for dmfe.c in dirver/net/Makefile, you'll find that it is
compiled if CONFIG_DM9102 is set. Then (in kernel source root):
find . -name Makefile -print|xargs grep
hi
I'm about to recompile my potato 2.2.17 kernel.
But how do I include dmfe (netcard driver) so I can load it
as a module???
thanks in advance
---
Jens Lauterbach
[EMAIL PROTECTED]
Roskilde University
use make-kpkg, read the docs (it's quite simple). at one point it asks
you to configure kernel - do it by run make config (command line), make
menuconfig (ncurses required, text based gui), make xconfig (x windows
interface, I think you need tk and wish for this). there you have a
chance to
I'm using make menuconfig and thats working fine, but I cant find dmfe
under the netcard drivers, all though I can find the file
/usr/src/kernel-source-2.2.17/drivers/net/dmfe.c
So its there, so how do I include it, when I'm compiling.
with potato, 2.2.17-compact it works fine!
what is wrong??
seach for dmfe.c in dirver/net/Makefile, you'll find that it is
compiled if CONFIG_DM9102 is set. Then (in kernel source root):
find . -name Makefile -print|xargs grep CONFIG_DM9102
and you'll find that ./drivers/net/Config.in says:
if [ $CONFIG_EXPERIMENTAL = y ]; then
tristate
I have just installed Debian GNU/Linux 2.1 with kernel 2.0.36 and wanted to
update the kernel to 2.2
I downloaded the source code for the Linux kernel 2.2.15
I was reading the Documentation/Changes document to make sure I had the
necessary versions of the various software packages. I found that
package dselect version recommended version
== ==
Procps 1.2.9-3 2.0.3
Util-linux 2.9g-6 2.9z
I have updated my dselect packages list, and it appears that no newer
versions are available. Do I need to
Sean 'Shaleh' Perry wrote:
procps has what you need. To get the versions 2.2.15 wants, you need to
upgrade your system to debian 2.2 (potato). potato is currently frozen and in
not necessarily. on my system:
ii procps 2.0.6-6The /proc file system utilities.
ii util-linux
Hello,
Before anything else, I'd like to thank the people who have helped
me before. This has been really nice... And so far, support here in
this list has been really efficient. Thank you all.
Ok - now, to my little problem:
I have a Pentium II 400Mh with 64Mb RAM; my motherboard
well, some people ( myself included ) rarely if ever use dselect
and should not be bound to do so just get this standard package
installed.
i've compiled enough kernels and done enough installs and could argue
that i myself would install this package by rote but that has yet to
be the case and
/i386/boot'
make: *** [bzImage] Error 2
and doesn't create the bzImage file
why?
- Original Message -
From: John Leget [EMAIL PROTECTED]
To: Beavis [EMAIL PROTECTED]; debian-user@lists.debian.org
Sent: Monday, March 06, 2000 9:10 PM
Subject: Re: compiling new kernel
Ughh, just run
ok first off, it is 'I heard Beavis say' not said u nerd!
second, translate this into english please:
#dpkg -S as86
bin86: /usr/share/doc/bin86/examples/as86_encap
bin86: /usr/bin/as86
bin86: /usr/share/man/man1/as86.1.gz
pretend I am a newbie, which i am.please don't tell anybody!
how
Once upon a time, I heard Nick Barron say
ok first off, it is 'I heard Beavis say' not said u nerd!
Terribly sorry for my bad English, I hope that I get it right this time!
second, translate this into english please:
I'm not sure whether I could translate this into a good English or not.
Nick Barron wrote:
ok first off, it is 'I heard Beavis say' not said u nerd!
second, translate this into english please:
#dpkg -S as86
bin86: /usr/share/doc/bin86/examples/as86_encap
bin86: /usr/bin/as86
bin86: /usr/share/man/man1/as86.1.gz
pretend I am a newbie, which i
He means:
Nick Barron wrote:
second, translate this into english please:
#dpkg -S as86
as the root user (# prompt) run the command 'dpkg -S as86'
bin86: /usr/share/doc/bin86/examples/as86_encap
bin86: /usr/bin/as86
bin86: /usr/share/man/man1/as86.1.gz
This is the output of the dpkg
Once upon a time, I heard Nick Barron say
ok, so we everyone is clear
i am trying to get the make bzImage command to write this
/usr/src/linux-2.2.x/arch/i386/boot/bzImage
but it doesn't, it gives me an error
make[1]: as86: Command not found
Is
Quoting Nick Barron ([EMAIL PROTECTED]):
ok, so we everyone is clear
i am trying to get the make bzImage command to write this
/usr/src/linux-2.2.x/arch/i386/boot/bzImage
but it doesn't, it gives me an error
make[1]: as86: Command not found
make[1]: *** [bbootsect.o] Error 127
First thing I did after my install was remove all unused packages that didn't
cause dselect to have kittens. bin86 was one of them. found that out quick
enough. The second thing I tried to do after install was recompile he kernel.
Bryan
I can't understand how so many people seem to lose
this is what i am doing:
Once that is all done and you choose Exit and save your config file, you
must run make dep followed by make clean. And now the fun begins, type make
bzImage to build your kernel. This will take awhile (15mins+) so go browse
our site a little and send us some feedback ;).
i am trying to compile the kernel 2.2.14 on to my i386 machine
please help if u can, thnakx
update:
after doing make bzImage, it starts to compile, which takes about 10 mins
or
so right.
then at the end it says:
as86 -0 -a -o bbootsect.o bbootsect.s
make[1]: as86: Command not found
make[1]:
i am trying to compile the kernel 2.2.14 on to my i386 machine
please help if u can, thnakx
update:
after doing make bzImage, it starts to compile, which takes about 10 mins or
so right.
then at the end it says:
as86 -0 -a -o bbootsect.o bbootsect.s
make[1]: as86: Command not found
Youre missing a package on your system
( Well what do you know im actually learning this stuff )
did a dpkg -S as86
you need to install the bin86 package
cheers
Beavis wrote:
i am trying to compile the kernel 2.2.14 on to my i386 machine
please help if u can, thnakx
update:
after
Ughh, just run an additional command ( after youve installed bin86 re previous
email)
make install
does the work of copying and running lilo at the end.
Id suggest you modify /etc/lilo.conf to also point to a known working kernel
and
have a resue disk and maybe even a boot disk handy.
Beavis == Beavis [EMAIL PROTECTED] writes:
i am trying to compile the kernel 2.2.14 on to my i386 machine
please help if u can, thnakx
update:
after doing make bzImage, it starts to compile, which takes
about 10 mins or so right. then at the end it says:
On Mon, Mar 06, 2000 at 03:18:52PM -0800, Beavis wrote:
this is what i am doing:
Once that is all done and you choose Exit and save your config file, you
must run make dep followed by make clean. And now the fun begins, type make
bzImage to build your kernel. This will take awhile
You are missing the assembler. Install bin86.
On Mon, Mar 06, 2000 at 03:55:08PM -0800, Beavis wrote:
i am trying to compile the kernel 2.2.14 on to my i386 machine
please help if u can, thnakx
update:
after doing make bzImage, it starts to compile, which takes about 10 mins or
so
Hello there,
On 7 Mar 2000, Marshal Wong wrote:
If I may inquire, why are you trying to compile a 2.2.x kernel for a
i386? That's going to hurt. I compiled a 2.0.x kernel on my old 486
and it took over 5 hours!
What kind of kernel did you compile, and on what kind of machine?
I compiled
486/33 8MB 2.0.36
Daniel == Daniel Reuter [EMAIL PROTECTED] writes:
Hello there, On 7 Mar 2000, Marshal Wong wrote:
If I may inquire, why are you trying to compile a 2.2.x kernel
for a i386? That's going to hurt. I compiled a 2.0.x kernel
on my old 486 and it took over 5
On Sat, 19 Jun 1999, Pollywog wrote:
After compiling kernel 2.2.10 and trying to install new software, I got:
make all-recursive
make[1]: Entering directory `/home/pollywog/ksnuffle-0.2'
Making all in libpcap-0.4
make[2]: Entering directory `/home/pollywog/ksnuffle-0.2/libpcap-0.4'
gcc
After compiling kernel 2.2.10 and trying to install new software, I got:
make all-recursive
make[1]: Entering directory `/home/pollywog/ksnuffle-0.2'
Making all in libpcap-0.4
make[2]: Entering directory `/home/pollywog/ksnuffle-0.2/libpcap-0.4'
gcc -g -I. -Ilinux-include -DHAVE_MALLOC_H=1
Pollywog wrote:
After compiling kernel 2.2.10 and trying to install new software, I got:
...
./pcap-linux.c:31: net/if.h: No such file or directory
...
Why does this happen? Am I doing something wrong? It seems I frequently
lose if.h
In the 2.2.x kernels, if.h is in include/linux/, so
57 matches
Mail list logo
