Messages in this thread | | | Subject | Re: Kernel Panic at Boot | Date | Mon, 07 Aug 2000 13:16:23 +0200 | From | Karl Hammar <> |
| |
You can access tha disk via the bios, that is how the kernel in first place can loaded.
Next we can make a kernel with initrd support. It gives the boot loader (note not the kernel) the possibility to load a RAM disk (with bios calls), which the kernel can mount as root. The kernel can then load the required scsi driver as a module and then mount the real root fs from disk.
Regards, /Karl
----------------------------------------------------------------------- Karl Hammar Aspö Data karl@kalle.csb.ki.se Lilla Aspö 2340 +46 173 140 57 Networks S-742 94 Östhammar +46 70 511 97 84 Computers Sweden Consulting -----------------------------------------------------------------------
From: andy thomas <andy@ic.ac.uk> Subject: Re: Kernel Panic at Boot Date: Mon, 7 Aug 2000 11:01:03 +0100 (BST)
> > > On Sun, 6 Aug 2000, Mahesh Mahadevan wrote: > > > Hi All, > > > > Please ignore my previous mail. > > > > I figured out the cause and solution of the problem (I > > had to compile the scsi controller driver into the > > kernel, rather than having it as a module -- which is > > the default).. sorry for that junk mail.. > > Systems that boot from a SCSI disk should always have the SCSI driver > compiled into the kernel. Loading it as a module won't work as how can > the kernel access the module file from the disk if it has no SCSI driver? > > I've seen this happen ;-) > > cheers, > > Andy > > > - > To unsubscribe from this list: send the line "unsubscribe linux-scsi" in > the body of a message to majordomo@vger.rutgers.edu
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |