From: szonyi calin <caszonyi@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: BUG ? and questions
Date: Sun, 20 May 2001 08:09:45 -0700 (PDT) [thread overview]
Message-ID: <20010520150945.66552.qmail@web13907.mail.yahoo.com> (raw)
Hello
My name is Calin
I have a Cx 486/66 with 12 Megs of ram AST computer
gcc 2.95.3, glibc 2.1.3, make 3.79.1 binutils 2.11 ??
Problems:
1. When I try to run multiple (2) compilations on a
2.4.4 kernel usually one
of them dies -- if it's gcc - signal 11 , if it's sh
or rarely make -
segmentation fault.
It is not a hardware problem (with kernel 2.2.x it
does not do this
and I have a cooler on my cpu)
2. I compiled a kernel 2.4.3 with XFS and sound as a
module (I use alsa
sound driver), and when I try to insmod soundcore.o it
says about some
unresolved symbols (one of them is printk )
I don't have this problem with any of the originals
2.4.x kernels
(downloaded from kernel.org)
Questions:
1. I have a vlb system and the kernel does not report
an IDE controler
I presume there is one. Is there a way to find out
what type it is
because a read about buggy 486 motherboards and I want
to be sure
that mine is not (It does not seems to be -- I have my
system
from about a year and a half and I have no problems )
2. I saw in .config in the root of kernel tree
"#CONFIG_BLK_DEV_IDEDISK_SEAGATE
is not set ";
the same for IBM, Maxtor etc. If I set this will be
any performance inprovements ?
3. I noticed that if I compile RTC in the kernel my
system runs smootly ?
Is this just an illusion ?
Sorry for bothering you
Sorry if the questions are silly
Bye
__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/
next reply other threads:[~2001-05-20 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-20 15:09 szonyi calin [this message]
2001-05-20 16:02 ` Christian Bornträger
2001-05-21 20:21 ` Erik Mouw
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010520150945.66552.qmail@web13907.mail.yahoo.com \
--to=caszonyi@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®