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.
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
>
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
chang
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
> 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 th
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 ke
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
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
>
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
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!
-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:
stamp
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).
Jocke <[EMAIL PROTECTED]> writes:
[...]
> install: debian/changelog: No such file or directory
> make: *** [kernel-image-deb] Error 1
[...]
This is either a bug or feature in the latest kernel-package; I
suspect it's a bug, but don't know yet.
To work around it, you can create two new text files
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 necessar
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 g
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
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. P
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.
--
--- - - --- - - -
-BEGIN PGP SIGNED MESSAGE-
On Tue, 10 Sep 1996, Vadik V. Vygonets wrote:
vadik>Crazy -- yes, hacker -- not yet :)
don't beleave him!
vadik>Borik you promised me RedHat fortune ;)
fortune
(RedHat)
___
Boris Beletsky <[EMAIL PROTECTED]>
For pgp public key, e-mail me
with subject
On Tue, 10 Sep 1996, Boris Beletsky wrote:
> gsolis>now my question is which gcc (what version ?) or what i have to do
> gsolis>for 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 cou
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 t
-BEGIN PGP SIGNED MESSAGE-
On Mon, 9 Sep 1996, Guillermo Solis wrote:
gsolis>I want to update my linux kernel to one which can run
gsolis>ELF format. I get the linux kernel 2.0.18 i think is the newest
gsolis>version??.
yes, but that will change
gsolis>when i try to compile i receive a mes
22 matches
Mail list logo
