Dear all,
i compiled kernel on debian etch (two times). But i have a same problem
No raid arrays. No Lvm
compiled 2.6.21 , 2.6.25 same problem
Begin: Assembling all Md arrays
mdadm : No array found in config file on automatically
failure : failed to assemble all arrays
Check root=bootarg cat
also sprach Murat Ugur EMINOGLU [EMAIL PROTECTED] [2008.05.04.1144 +0100]:
i compiled kernel on debian etch (two times). But i have a same problem
No raid arrays. No Lvm
You have not provided any details, such as the configuration and
command line used, so we can't really help you.
ALERT
On Mon, Mar 11, 2002 at 04:53:52PM -0600, Christopher M. Jones wrote:
I'm compiling for a K7/Athlon/Duron system. As far as I can tell, -all-
modules come up with unresolved symbols. In other words, any module I try to
load comes up with unresolved symbols, whether part of the kernel, or
On Tue, Mar 12, 2002 at 11:24:22AM +, Alan James wrote:
This may be a daft question but when you load modules are you using inmod or
Sorry I meant insmod there of course. Still modprobe is the one to use.
I am having a problem compiling from source 2.4.17 packaged for Debian. Using
make-kpkg kernel_image in the source dir, all my modules come up with
unresolved symbols.
What causes this? What am I doing wrong? What should I do to fix it?
Using gcc 2.95.4
I'm compiling for a K7/Athlon/Duron system. As far as I can tell, -all-
modules come up with unresolved symbols. In other words, any module I try to
load comes up with unresolved symbols, whether part of the kernel, or
standalone. Clearly, I am doing something very wrong, though I haven't
There is a binutils problem, I download binutils, binutils-dev and modutils
Potato version and it's compile :D There are my version's:
ii binutils 2.9.5.0.37-1 The GNU assembler, linker and binary
utiliti
ii binutils-dev 2.9.5.0.37-1 The GNU binary utilities (BFD development
fi
ii
Another one of those release many and release quick again
Uuughh...
I remember someone once said regarding the impending release of 2.4.0
and why it was taking so long...that Linus just has much higher
standards...oh oh...this is definitely not in the correct direction in
support of the
On Tue, Nov 06, 2001 at 02:11:52PM +0800, Patrick Cheong Shu Yang wrote:
Another one of those release many and release quick again
Uuughh...
I remember someone once said regarding the impending release of 2.4.0
and why it was taking so long...that Linus just has much higher
On Tue, Nov 06, 2001 at 02:11:52PM +0800, Patrick Cheong Shu Yang wrote:
Another one of those release many and release quick again
Uuughh...
I remember someone once said regarding the impending release of 2.4.0
and why it was taking so long...that Linus just has much higher
On Tue, Nov 06, 2001 at 08:53:51AM -0600, John Patton wrote:
On Tue, Nov 06, 2001 at 02:11:52PM +0800, Patrick Cheong Shu Yang wrote:
Another one of those release many and release quick again
Uuughh...
I remember someone once said regarding the impending release of 2.4.0
and why
On Tue, Nov 06, 2001 at 06:42:23AM -0500, Michael P. Soulier wrote:
On Tue, Nov 06, 2001 at 02:11:52PM +0800, Patrick Cheong Shu Yang wrote:
Another one of those release many and release quick again
Uuughh...
I remember someone once said regarding the impending release of 2.4.0
I have just tried to compile a clean source (without any patches) of
v2.4.14. I did a straight make oldconfig of a working v2.4.13 .config.
I get the following error message at that last part of the make bzImage
when it is creating the final kernel image:
ld -m elf_i386 -T
This is a kernel problem, nothing to do with Debian. It has been posted to
the linux-kernel list, but no fix has been posted yet. This may be another
case where they fix it and make another release in a SHORT period of time.
Commenting out the two references to the function and recompiling
On Mon, 5 Nov 2001, James D Freels wrote:
make: *** [vmlinux] Error 1
I suspect others will have the same problem. Any idea of a fix?
Quoting [EMAIL PROTECTED]:
If you're using pgcc, try getting a real less-buggy compiler, like
egcs1.1.2 or gcc-2.95.
--
Baloo
hi!
I tried to compile the kernel of my potato distro (kernel is quite old:
2.2.17) and I got the following error message:
as86: command not found;
or something like that. The main problem the as86 is seems to be missing from
my machine.
Does anyone some guess what the hell is this? Or which
hi!
I tried to compile the kernel of my potato distro (kernel is quite old:
2.2.17) and I got the following error message:
as86: command not found;
or something like that. The main problem the as86 is seems to be missing from
my machine.
Does anyone some guess what the hell is this? Or
On Mon, Sep 17, 2001 at 10:50:57AM +0200, pink panther wrote:
hi!
I tried to compile the kernel of my potato distro (kernel is quite old:
2.2.17) and I got the following error message:
as86: command not found;
or something like that. The main problem the as86 is seems to be missing from
When compile 2.4.9 kernel with gcc 3.0.2 :
#make-kpkg clean
#make-kpkg --append-to-version -tao3 kernel_image
#make-kpkg clean
#make-kpkg --append-to-version -tao4 kernel_image
#make-kpkg clean
#make-kpkg --append-to-version -tao5 kernel_image
(install the three kernels)
#cd /boot
#ls -l
High,
On Fri, 7 Sep 2001, Tao Liu wrote:
When compile 2.4.9 kernel with gcc 3.0.2 :
#make-kpkg clean
#make-kpkg --append-to-version -tao3 kernel_image
#make-kpkg clean
#make-kpkg --append-to-version -tao4 kernel_image
#make-kpkg clean
#make-kpkg --append-to-version -tao5
on Sat, Aug 04, 2001 at 04:51:06PM -0500, Jay Latham ([EMAIL PROTECTED]) wrote:
I was going to re-compile my kernel today to get rid of some of the
things I don't need but when I got to the network card driver modules,
mine was greyed out (Realtec 8139). This is on the 2.2.19pre17 kernel.
I
I was going to re-compile my kernel today to get rid of some of
the things I don't need but when I got to the network card
driver modules, mine was greyed out (Realtec 8139). This is on
the 2.2.19pre17 kernel. I then went to the 2.2.19 kernel which
offered two drivers (rtl8139 and 8139too), but
When I try to compile the kernel I get this error:
gcc: Internal compiler error: program cc1 got fatal signal 11
The compile then exits. It does not seem to matter which kernel I try. I
tried both gcc 2.95.2 and 2.7.2. It gets this error in different places.
In the most recent (kernel 2.2.15) it
http://www.bitwizard.nl/sig11/
Matthew Simpson wrote:
When I try to compile the kernel I get this error:
gcc: Internal compiler error: program cc1 got fatal signal 11
I am having problems with recompiling my kernel. I had kernel 2.2.12 and
recompiled it to thw same 2.2.12 but to include ip_masquerading. Now when I
boot I see
depmod: *** Unresolved symbols in /lib/modules/2.2.12/ipv4/ip_masq_quake.o
depmod: *** Unresolved symbols in
Jay Kelly wrote:
I am having problems with recompiling my kernel. I had kernel 2.2.12 and
recompiled it to thw same 2.2.12 but to include ip_masquerading. Now when I
boot I see
depmod: *** Unresolved symbols in /lib/modules/2.2.12/ipv4/ip_masq_quake.o
depmod: *** Unresolved symbols in
Here is the last lines of my make-kpkg --revision=custom.1.0 kernel_image
..snip..
install -p -d -o root -g root -m 755
debian/tmp-image/usr/share/doc/kernel-image-2.3.16
sed -e 's/=V/2.3.16/g'-e 's/=B//g' \
-e 's/=S//g' -e 's/=R//g' \
-e 's/=K/bzImage/g'
See also bug #47054, which suggests a one-line additon to the
kernel-package script that's probably a better fix to this problem
(though I haven't tested it).
-BEGIN PGP SIGNED MESSAGE-
On 10 Oct 1999, David Coe wrote:
See also bug #47054, which suggests a one-line additon to the
kernel-package script that's probably a better fix to this problem
(though I haven't tested it).
I got it to work by changing line 759 to the following:
Brad [EMAIL PROTECTED] writes:
On 10 Oct 1999, David Coe wrote:
See also bug #47054, which suggests a one-line additon to the...
I got it to work by changing line 759 to the following...
Thanks!
Roger Franz [EMAIL PROTECTED] writes:
I got a sound card (my wife insisted on having a sound card), and am now
trying to recompile the kernel to include support for it.
I've got the configuration set up, and everything appears to be correct.
I run make-kpkg, and it runs until I get this:
On Sun, Nov 29, 1998 at 07:06:29PM +, Roger Franz wrote:
gcc: Internal compiler error: Program cc1 got fatal signal 11.
Ohh, nasty. AFAIR this means you have some bad mem or cpu (more likely
memory). I could be wrong.
---
I once
On Mon, Nov 30, 1998 at 05:05:24 -0800, Kenneth Scharf wrote:
On Sun, Nov 29, 1998 at 07:06:29PM +, Roger Franz wrote:
gcc: Internal compiler error: Program cc1 got fatal signal 11.
Ohh, nasty. AFAIR this means you have some bad mem or cpu (more likely
memory).
Not necessarily,
I got a sound card (my wife insisted on having a sound card), and am now
trying to recompile the kernel to include support for it.
I've got the configuration set up, and everything appears to be correct.
I run make-kpkg, and it runs until I get this:
gcc: Internal compiler error:
On Sun, Nov 29, 1998 at 07:06:29PM +, Roger Franz wrote:
gcc: Internal compiler error: Program cc1 got fatal signal 11.
Ohh, nasty. AFAIR this means you have some bad mem or cpu (more likely
memory). I could be wrong.
--
--- - - --- - - -
On Sun, 29 Nov 1998 19:06:29 +, you wrote:
I run make-kpkg, and it runs until I get this:
gcc: Internal compiler error: Program cc1 got fatal signal 11.
This apparently occurs at random points during the run of the compile;
this particular one occurred while compiling init.o.
I thought I'd build a nice slim 'n trim kernel for one of
my machines... so I went and did a make config, then did
'make zImage' and got:
ld -m elf_i386 -Ttext 0x10 -e stext arch/i386/kernel/head.o init/main.o
init/version.o \
arch/i386/kernel/kernel.o arch/i386/mm/mm.o
On Mon, 30 Jun 1997 21:11:32 CDT Zachary DeAquila ([EMAIL PROTECTED]
.org) wrote:
I thought I'd build a nice slim 'n trim kernel for one of my
machines... so I went and did a make config, then did 'make zImage'
and got:
[snip]
And you probably forgot to make clean and make dep in the
-BEGIN PGP SIGNED MESSAGE-
On Tue, 10 Sep 1996, Vadik V. Vygonets wrote:
vadikCrazy -- yes, hacker -- not yet :)
don't beleave him!
vadikBorik you promised me RedHat fortune ;)
fortune
(RedHat)
___
Boris Beletsky [EMAIL PROTECTED]
For pgp public key, e-mail me
with subject get
i everybody.
I want to update my linux kernel to one which can run
ELF format. I get the linux kernel 2.0.18 i think is the newest
version??. when i try to compile i receive a message on the screen
telling me gcc is to old. Then i get the new gcc version
and when i try ro run it a see a new
-BEGIN PGP SIGNED MESSAGE-
On Mon, 9 Sep 1996, Guillermo Solis wrote:
gsolisI want to update my linux kernel to one which can run
gsolisELF format. I get the linux kernel 2.0.18 i think is the newest
gsolisversion??.
yes, but that will change
gsoliswhen i try to compile i receive a
On Mon, 9 Sep 1996, Guillermo Solis wrote:
i everybody.
I want to update my linux kernel to one which can run
ELF format. I get the linux kernel 2.0.18 i think is the newest
version??. when i try to compile i receive a message on the screen
telling me gcc is to old. Then i get the new
On Tue, 10 Sep 1996, Boris Beletsky wrote:
gsolisnow my question is which gcc (what version ?) or what i have to do
gsolisfor compile the new kernel.?
i whould say - reinstall the all system
there lots of thigs that u need to upgrade - libs , etc..
so i think thats the best thing u could do.
43 matches
Mail list logo
