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
Whoops, I screwed up and did not include one additional line I see
during the failed boot up of my self compiled kernels.
So the actual messages are:
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
[Linux-bzImage, setup=0x3000, size=0x2815c0]
--
Steven DuChene
OK, so after removing rhgb and quiet from the menu.lst
for this kernel the last few messages it prints are:
sdb:
sdb1 sdb2
sd 1:0:0:0: [sdb] Attached SCSI disk
XFS mounting filesystem sda3
VFS: Mounted root (xfs filesystem) readonly on device 8:3.
Freeing unused kernel memory: 416k freed
Warning: unable to open an initial console.
Since it does not seem to be reaching the init stage but
does seem to be finding the disks and mounting the filesystems
it is getting much further along than I thought. I guess
I have a problem with the console/terminal parts of the
kernel compile/configuration.
-----Original Message-----
>From: Arjan van de Ven <[email protected]>
>Sent: Sep 30, 2009 11:47 AM
>To: "Steven A. DuChene" <[email protected]>
>Subject: Re: newer non-distro kernels don't boot / unpack?
>
>first remove rhgb and quiet.. that way you get at least the kernel log
>on the screen... to see where you get stuck.
>
>
>--
>Arjan van de Ven Intel Open Source Technology Centre
>For development, discussion and tips for power savings,
>visit http://www.lesswatts.org