Very Computer

1. new kernel build works in one computer but not another

Hello,

I have a laptop whose only communication with the outside world is a
parallel-port ZIP drive (no floppy, no CDROM).  So, I have been doing the
OS installs by transferring the hard drive to my desktop system (which is
mostly SCSI).  This worked well until I tried to update to a customized
kernel 2.2.18. Since then, the laptop drive will boot up fine in the
desktop machine, but hangs when placed back in the laptop. I have tried to
go back to the old 2.2.16 image but that doesn't fix the problem.

The hang occurs after all the kernel boot messages up to "Freeing kernel
memory 48k" (sorry, can't remember the exact line.) but does _not_ go
ahead into init.  I am confused because I made no changes to /etc/inittab.
I would save the kernel messages but don't know how. As they flash by, it
looks like there's some failed attempt to look for the SCSI devices.

I've spent two days on this and I am completely stumped! Thanks in advance
for any help here... more details are at the end of this message.

Jean

The original setup:
1. Dual boot Win98SE/Red Hat Linux 7.0
2. Boot loader is Loadlin.exe:
loadlin c:/linux/vmlinuz root=/dev/hda6 ro mem=126M
   initrd=c:/linux/initrd.img ro
 (an additional weirdness is that since the new kernel, I get a
bad crash unless I drop mem=128M down to mem=126M)

3. Red Hat installed on laptop drive in desktop computer, no problems but
took up too much space so I decided to compile a custom, updated kernel
with only needed drivers

Changes I made recently:
1. Shared Linux/Windows swap partition  using the method described
in the mini-HOW-TO...  works just dandy when the hard drive is in the
desktop.  It involved some very minor editing of sysinit file.

2. Recompilation of modular kernel: SCSI drivers only as modules, no
experimental drivers chosen... laptop drive set up as hda in desktop
computer during compilation (though not replacing the desktop's main
hard drive (/dev/sda) since I could manipulate booting through the BIOS.)

3. New bzImage copied to /boot/vmlinuz, c:/linux/vmlinuz. During debugging
some other things, I may have copied the /boot directory from my desktop
drive right over my laptop's /boot directory just because I had run out of
ideas.

4. Tried to make a new initrd.img without SCSI modules.  Tried using
"noinitrd" option to loadlin line-- Replaced kernels in /boot/vmlinuz and
c:/linux with old 2.2.16 kernel-- replaced /usr/src/linux with old linux
directory backup-- tried rdev on the image file-- no change in the boot
hang.

2. Software(s) to manage a LETS under Linux ?

3. 3.4 New kernel build - panic cpu type not configured

4. Matrox Mystique...

5. BUILD KERNEL SUSE 5.2 DOES NOT WORK!!!

6. Hi KevCo About that Viper V770 and 300X200 mode.

7. compile new kernel => compile new iptables ?

8. install

9. Kernel Panic: Can't mount root - after building new kernel

10. How to increase the kernel vs user memory when building a new kernel

11. file command not working properly under new 2.0.x kernels

12. NAT Not working after new kernel compiled

13. IBM chars not working in new kernels (TRY #3 !!!)