linux-kernel - newer non-distro kernels don't boot / unpack?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <6024051.1254325345120.JavaMail.root@elwamui-rubis.atl.sa.earthlink.net>
Date:	Wed, 30 Sep 2009 11:42:24 -0400 (EDT)
From:	"Steven A. DuChene" <linux-clusters@...dspring.com>
To:	linux-kernel@...r.kernel.org
Subject: newer non-distro kernels don't boot / unpack?

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

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