I'll try rebuilding the kernel, but it'll take all night so I'll report tomorrow on that. The kernel install runs lilo by itself, right? I don't have the old source tree, it came from the debian boot floppy and the four driver disks. I'll reconfigure now, and build.
On Thursday, September 18, 2003, at 03:47 PM, Terry Carney wrote:
On Wed, 17 Sep 2003, Steven Schlansker wrote:------------------
error messages printed, the screen clears too fast. I, however, can
boot LinuxOLD to get the old kernel back. How can I debug this kind of
problem?
Boot LinuxOLD and scan the kernel boot messages /var/log/messages for the two kernels and see if you can find differences. The boot process very probably doesn't get this far so you can try CTRL-s CTRL-q to try and stop/start the boot messages before they go by.
Possibilities I can think of:
* In 'make menuconfig':
- the processor type may have inadvertently been set wrong. - hardware you need getting missed
* Failure to rerun Lilo after compilation.
If you have the old source tree you can copy the .config file to the new
tree and run 'make oldconfig' which will transfer your old settings to
the new kernel while getting prompted for the differences.
Hoping this helps,
Terry.
[EMAIL PROTECTED] http://haven.selterra.com/ ----------------------------------------------------------------- Public GPG Key: http://www.selterra.com/pubkeys/tcarney.asc
Microsoft Windows: Proof that P.T. Barnum was correct.
Steven Schlansker Tech Support & Programming
Flamin' Ghost Software http://www.fgsoft.net/
[EMAIL PROTECTED] [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
