Re: The Custom Kernel that Wouldn't Boot.
* Timothy R. Butler (tbutler@uninetsolutions.com) spake thusly:
> Hi Dima,
> > Of course, if it refuses to boot without fb, the problem is
> > somewhere else.
>
> It seems to refuse to boot even without fb. :-( As with the last kernel, I
> get the following in kern.log:
>
> ---------------
> Feb 28 11:59:21 dellbert kernel: PCI: Found IRQ 9 for device 00:10.0
> Feb 28 11:59:21 dellbert kernel: PCI: Sharing IRQ 9 with 00:07.2
> Feb 28 11:59:24 dellbert kernel: Kernel logging (proc) stopped.
> Feb 28 11:59:24 dellbert kernel: Kernel log daemon terminating.
> ---------------
On my box I get a message from 3c59x after "PCI:" ones.
> Any ideas what I might be selecting wrong?
NIC driver? But no, not really. There are too many things
you might (or might not) be selecting wrong.
...Is it that I'm doing something
> wrong with initrd?
I wouldn't know, I don't remember using initrd in home-built
kernels, ever.
...Perhaps it's the fact that it's 686 optimized?
Well, that should be backwards-compatible: if you optimize
for 686 and run on a 586, you may have a problem, but other
way around should work (and usually does).
So, to make sure, compile for 386. If you're using menuconfig,
select "Help" on processor type while you're there, and read it.
Dima
Reply to: