Thanks for your reply. Actually, I am not using LILO at all because I am aware of the large disk problem with LILO. I learnt it the hard way when my partition table got wiped out.
I am using loadlin, which I heard could be used with the EZ Drive disk manager. Actually, loadlin works great with my custom 2.0.36 kernel but with the custom 2.2.14 kernel I get a kernel panic. I only have one IDE hard drive. The only reason I am using the Adaptec scsi card is for my scsi scanner. I am also builing the generic and scsi emulation support as modules so that I can make the kernel see my CDRW drive as a SCSI device instead of an IDE ATAPI device so that I can use the cdrecord utility to record CDs. Maybe SCSI support in the kernel instead of as modules is the way to go - though frankly I don't understand why since I don't have SCSI hard drives. Also, why should the kernel behave differently from 2.0 to 2.2 in this case ? > > > > I am using loadlin to load up a kernel from from > > Windows 95 partition. Since my BIOS is old and my > hard > > disk is new, I am using the EZ Drive disk manager > for > > my 10 GB hard drive. > > You may have a problem with the large disk. RTFM > LILO WRT "linear" > option. > > What kind of drive is this? IDE or SCSI (more > below). From the > /dev/hda references, I'm assuming IDE. > > > I have a Pentium 200 CPU with MMX and 32 MB > memory. > > Buy more RAM! <g> Not related to your current > problem, but.... > > > I compiled a custom 2.0.36 before and it worked > > without a problem. > > > > I then wiped the linux partition, installed the > base > > slink system again and used apt-get dist-upgrade > to > > upgrade > > to a potato system. The kernel did not get > upgraded > > even though it was a stock 2.0.36 kernel. > > > > Anyway, I downloaded the 2.2.14 kernel source deb > > package and used a config similar to the one I had > > used > > for my 2.0.36 kernel. > > You need to re-run LILO when you install a new > kernel, if you're booting > with LILO. > > > The 2.2.14 kernel starts ok but right after : > > > > Freeing unused kernel memory : 36k freed > > > > it says: > > > > Kernel panic. init not found. Pass init= option to > the > > kernel. > > > > I tried using rdev on my custom 2.0.36 kernel > (which > > works) > > > > rdev linux.20 > > > > Root device /dev/hda5 > > > > rdev linux.22 > > > > Root device /dev/hda5 > > > > and /dev/hda5 is where / is located so that does > not > > seem > > to be the problem. > > > > What am I doing wrong or is this a kernel bug ? > > > > > > Here is the config file for 2.2.14 > > Hmmm... Looking at the SCSI options, you've > configured AIC7XXX as > a module. Are you using a SCSI disk? If so, you'll > need an initrd > to mount your HD, as modules are loaded from disk > *after* you boot. > Note the dilemma -- need module to read disk, need > to read disk to > get module.... Better yet, compile the SCSI support > into the kernel. > If you don't need the support, drop the SCSI stuff. > > > # > > # Automatically generated by make menuconfig: > don't > > edit > > # > > > > # > > # Code maturity level options > > # > > # CONFIG_EXPERIMENTAL is not set > > > > # > > # Processor type and features > > # > > # CONFIG_M386 is not set > > # CONFIG_M486 is not set > > # CONFIG_M586 is not set > > CONFIG_M586TSC=y > > # CONFIG_M686 is not set > > CONFIG_X86_WP_WORKS_OK=y > > CONFIG_X86_INVLPG=y > > CONFIG_X86_BSWAP=y > > CONFIG_X86_POPAD_OK=y > > CONFIG_X86_TSC=y > > CONFIG_1GB=y > > # CONFIG_2GB is not set > > # CONFIG_MATH_EMULATION is not set > > CONFIG_MTRR=y > > # CONFIG_SMP is not set > > > > # > > # Loadable module support > > # > > CONFIG_MODULES=y > > # CONFIG_MODVERSIONS is not set > > # CONFIG_KMOD is not set > > > > # > > # General setup > > # > > CONFIG_NET=y > > CONFIG_PCI=y > > # CONFIG_PCI_GOBIOS is not set > > # CONFIG_PCI_GODIRECT is not set > > CONFIG_PCI_GOANY=y > > CONFIG_PCI_BIOS=y > > CONFIG_PCI_DIRECT=y > > CONFIG_PCI_QUIRKS=y > > CONFIG_PCI_OLD_PROC=y > > # CONFIG_MCA is not set > > # CONFIG_VISWS is not set > > CONFIG_SYSVIPC=y > > CONFIG_BSD_PROCESS_ACCT=y > > CONFIG_SYSCTL=y > > # CONFIG_BINFMT_AOUT is not set > > # CONFIG_BINFMT_ELF is not set > > CONFIG_BINFMT_MISC=y > > CONFIG_PARPORT=m > > CONFIG_PARPORT_PC=m > > # CONFIG_PARPORT_OTHER is not set > > # CONFIG_APM is not set > > > > # > > # Plug and Play support > > # > > CONFIG_PNP=y > > # CONFIG_PNP_PARPORT is not set > > > > # > > # Block devices > > # > > CONFIG_BLK_DEV_FD=y > > CONFIG_BLK_DEV_IDE=y > > # CONFIG_BLK_DEV_HD_IDE is not set > > CONFIG_BLK_DEV_IDEDISK=y > > CONFIG_BLK_DEV_IDECD=m > > # CONFIG_BLK_DEV_IDETAPE is not set > > # CONFIG_BLK_DEV_IDEFLOPPY is not set > > CONFIG_BLK_DEV_IDESCSI=m > > CONFIG_BLK_DEV_CMD640=y > > CONFIG_BLK_DEV_CMD640_ENHANCED=y > > CONFIG_BLK_DEV_RZ1000=y > > CONFIG_BLK_DEV_IDEPCI=y > > CONFIG_BLK_DEV_IDEDMA=y > > # CONFIG_BLK_DEV_OFFBOARD is not set > > CONFIG_IDEDMA_AUTO=y > > # CONFIG_IDE_CHIPSETS is not set > > CONFIG_BLK_DEV_LOOP=m > > # CONFIG_BLK_DEV_NBD is not set > > # CONFIG_BLK_DEV_MD is not set > > # CONFIG_BLK_DEV_RAM is not set > > # CONFIG_BLK_DEV_XD is not set > > # CONFIG_BLK_DEV_DAC960 is not set > > CONFIG_PARIDE_PARPORT=m > > # CONFIG_PARIDE is not set > > # CONFIG_BLK_CPQ_DA is not set > > # CONFIG_BLK_DEV_HD is not set > > > > # > > # Networking options > > # > > CONFIG_PACKET=m > > # CONFIG_NETLINK is not set > > # CONFIG_FIREWALL is not set > > # CONFIG_FILTER is not set > > CONFIG_UNIX=y > > CONFIG_INET=y > > # CONFIG_IP_MULTICAST is not set > > # CONFIG_IP_ADVANCED_ROUTER is not set > > # CONFIG_IP_PNP is not set > > # CONFIG_IP_ROUTER is not set > === message truncated === __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com
