[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: moving to the 2.6 kernel?



Jules Dubois wrote:

On Thu, 24 Jun 2004 02:22:07 -0700, Paul Scott wrote:

I don't want to spend the time to build a new kernel right now and I have spent quite a bit of time Googling, searching this list and reading kernel-docs.

How about a pragmatic approach.  Which takes more time: searching
Google, list archives, and kernel documentation; or building a custom
kernel?
I certainly considered that and I don't have the incentive at the moment since my 2.4 kernel works fine.

One large concern justifying my research was whether something about the way the 2.6 kernels had changed from the 2.4 kernels (like udev) and was causing my problem and would be something I would also have to solve with a custom kernel.

Is there a way to fix this with a stock kernel.

I spent a few hours on my problem.  I'm not an expert on modules and I
know little about initrd, so I simply built a new kernel and rebooted.  It
booted the first time.
That's good to hear.

Is there a better choice than 386 for AMD K6-II?

Isn't the K6-II an i686?  (I don't know what difference it would make.)
It probably would be fine. The description for 686 mentions Celeron and once I had a problem building a custom 2.4 kernel because of some Celeron option. It's probably unrelated but I can always switch to 686 when I get the current problem solved.

Is there more information I can provide?

I see that there are no bugs filed against your 386 package.  I take this
to mean that something about the configuration of your system and my
system is improper.
I would, of course, be good to find that out.

Do you get two warning (or error) messages when you installed the package,
saying cpio was unable to find:

 /etc/modprobe.conf
 /lib/modules/modprobe.conf

If your kernel won't boot properly, I think it's safe to remove and
reinstall the package to check for the error messages.
I don't remember those messages and I have tried at least two versions (2.6.6-1 and 2.6.6-2). Actually I believe I had a previous 2.6 kernel running and I stupidly let an upgrade from aptitude install a 2.4 kernel over it.

Thanks,

Paul



Reply to: