linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "George J. Mpitsos" <gmpitsos@slugo.hmsc.orst.edu>
To: linuxppc-user@lists.linuxppc.org,
	linuxppc-dev@lists.linuxppc.org, ningerso@d.umn.edu
Subject: Re: Kernel 2.1.131
Date: Thu, 10 Dec 1998 14:52:05 -0800 (PST)	[thread overview]
Message-ID: <199812102252.OAA06277@Slugo.hmsc.orst.edu> (raw)


 
Comment out the line "SMP=1" in the make file.


> 
> 
> Has anyone successfully compiled and used the 2.1.131 kernel from
> ftp.kernel.org? I downloaded it and compiled it without error, but when I
> try to boot all I get is a black screen with the line "Welcome to Linux
> kernel 2.1.131" or something like that. Nothing happens after this. I did
> forget to compile and install the modules, but I don't think that would
> cause the system to hang right off the bat. Any ideas on the problem?
> 
> Thanks,
> 
> Nathan
> 
> 
> 

[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

             reply	other threads:[~1998-12-10 22:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-12-10 22:52 George J. Mpitsos [this message]
1998-12-11  1:53 ` Kernel 2.1.131 nathan ingersoll
  -- strict thread matches above, loose matches on Subject: below --
1998-12-10 22:27 Piotr_Muszynski
1998-12-14  7:06 ` nathan ingersoll
1998-12-10  4:48 Blank screen bootx 2.1.127 satadru pramanik
1998-12-10 15:22 ` Kernel 2.1.131 nathan ingersoll
1998-12-10 17:11   ` john s anderson
1998-12-10 17:15     ` nathan ingersoll
1998-12-10 23:24   ` Donn Ezekiel Wheeler

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=199812102252.OAA06277@Slugo.hmsc.orst.edu \
    --to=gmpitsos@slugo.hmsc.orst.edu \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=linuxppc-user@lists.linuxppc.org \
    --cc=ningerso@d.umn.edu \
    /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;
as well as URLs for NNTP newsgroup(s).