mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Steven A. DuChene" <linux-clusters@mindspring.com>
To: linux-kernel@vger.kernel.org
Subject: newer non-distro kernels don't boot / unpack?
Date: Wed, 30 Sep 2009 11:42:24 -0400 (EDT)	[thread overview]
Message-ID: <6024051.1254325345120.JavaMail.root@elwamui-rubis.atl.sa.earthlink.net> (raw)

I have a A13G motherboard from PCChips that has a AMD Athlon 3600+
dual core CPU in it. I have fedora core 9 installed and running
fine on it. FC9 comes with a 2.6.25-14.fc9.x86_64 kernel installed.
The motherboard has a NVidia MCP61 chipset on it and as I said
everything built onto the motherboard including sound, usb, and
network chips work just fine with the FC9 included kernel.

I have 15+ years of Linux experience and have built many kernels
of my own in the past however I have been frustrated for a few
months now (since Jan/Feb of this year) at getting a self-compiled
kernel to run on this system. I have built 2.6.25.5, 2.6.28.1 and
yesterday 2.6.31.1 and nothing seems to work.

When I try booting the kernel after making the usual grub entry
it does the following:

Booting 'deskamd30mne (2.6.31.1-amddesk1)'

root (hd0,0)
Filesystem type is ext2fs, partition type 0x83
kernel /vmlinux-2.5.31.1-amddesk1 ro root=/dev/sda3 rhgb quiet

and then the whole thing just sits there forever with no additional
activity. I have tried turning off and on various debugging
stuff during the compile but nothing seems to have any affect
on this. When the regular FC9 distro kernel boots the next lines
I would normally see on the screen would be about the initrd.

I can try booting some live-cd type of thing but I am guessing
they will work fine. BTW, I have built the various filesystem
and device drivers I need so as to not need an initrd file.

Anyone have any suggestions or thoughts?

Also I am not subscribed to the linux-kernel mailing list so please
CC me on any replies. I will try to watch the LKML archives however.

Thanks for any help, suggestions or assistance.
--
Steven DuChene



             reply	other threads:[~2009-09-30 15:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-30 15:42 Steven A. DuChene [this message]
2009-09-30 15:47 Steven A. DuChene
2009-09-30 15:55 Steven A. DuChene

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=6024051.1254325345120.JavaMail.root@elwamui-rubis.atl.sa.earthlink.net \
    --to=linux-clusters@mindspring.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®