All of lore.kernel.org
 help / color / mirror / Atom feed
From: joy <gracecott@sancharnet.in>
To: Ray Olszewski <ray@comarre.com>
Cc: linux-newbie <linux-newbie@vger.kernel.org>, PachecoJ@Npt.NUWC.Navy.Mil
Subject: Re: kernel compilation problem
Date: Wed, 24 Dec 2003 10:15:37 +0530	[thread overview]
Message-ID: <3FE919F1.6010600@sancharnet.in> (raw)
In-Reply-To: 5.1.0.14.1.20031223084227.01f4cec0@celine

Sorry to find a trivial answer to the Q. The settings were alright .
thanks a lot , Jason and Ray, All I needed to do was to to copy the
System.map as this Kernel does not use the other two System.map(s)  in
/boot (they are for kernels compiled with diff options).
But still ,I would like to get rid of the irritating
              spurious 8259A interrupt : IRQ7
message I get on Boottime.
I run an athlon 2400+ , with a biostar nforce2 mobo and the normal
peripherals, nothing out of the ordinary.


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  reply	other threads:[~2003-12-24  4:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3BEEE23D31CAD2118D920008C75D8946059FF59E@NPRI54EXC21.NPT.N UWC.NAVY.MIL>
2003-12-23 16:51 ` kernel compilation problem Ray Olszewski
2003-12-24  4:45   ` joy [this message]
2003-12-24  6:46     ` Beolach
2007-02-22 13:01 Kernel " Zgembo Adislic
2007-02-22 13:10 ` Woodruff, Richard
  -- strict thread matches above, loose matches on Subject: below --
2003-12-24 13:22 kernel " Pacheco Jason NPRI
2003-12-23 13:46 Pacheco Jason NPRI
2003-12-23 10:46 joy
2001-08-25 12:18 Kernel " Ben Hague
2001-08-25 10:37 ` Ralf Baechle
1999-04-15  4:20 kernel " Charles Lepple
1999-04-15  4:37 ` Ralf Baechle
1999-04-15  4:48 ` Matthias Kleinschmidt

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=3FE919F1.6010600@sancharnet.in \
    --to=gracecott@sancharnet.in \
    --cc=PachecoJ@Npt.NUWC.Navy.Mil \
    --cc=linux-newbie@vger.kernel.org \
    --cc=ray@comarre.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.