* Bill Davidsen <[EMAIL PROTECTED]> [2002 Mar 07 16:27 -0600]:
>
> I shudder to think that you really "did a direct copy" from one machine
> and are running the same kernel on a new machine with a different
> architecture. Try building a 2.4.17 or 2.4.19-pre2-ac2 kernel for this
> and see if the problem goes away.
Actually, it worked quite well as the previous system was quite generic
and I'd never compiled chipset specific features in the 2.2.19 kernel.
It was built for a K6 kernel and I really wondered if it would boot at
all. But, Linux is quite forgiving, IMO.
> When you go to a bright shiney new machine, with a very recent chipset,
> going to a very recent kernel is highly recommended. I don't promise that
> this is fixed, but at least a kernel which fits your hardware will give
> you a fighting chance.
I now have that kernel. :-)
> I bet you're still running your old config files as well, doing
> whatever hardware setup was a good idea for the old machine...
I've slowly merged things over and now I performed the most dramatic
tune-up and things are running nicely. Oh, and I'm back to torching CDs
at 12X again. Oh, happy day!
- Nate >>
--
Wireless | Amateur Radio Station N0NB | "We have awakened a
Internet | [EMAIL PROTECTED] | sleeping giant and
Location | Bremen, Kansas USA EM19ov | have instilled in him
Amateur radio exams; ham radio; Linux info @ | a terrible resolve".
http://www.qsl.net/n0nb/ | - Admiral Yamomoto
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
