home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!sun-barr!olivea!charnel!csusac!citrus!ianj
- From: ianj@citrus.SAC.CA.US ( Ian Justman )
- Newsgroups: comp.os.linux
- Subject: Re: Clue to why 0.98.6 won't boot
- Message-ID: <Bz3E35.8I6@citrus.SAC.CA.US>
- Date: 11 Dec 92 11:18:39 GMT
- References: <li9p6vINNjeb@ozona.cs.utexas.edu>
- Organization: Citrus Grove Public Access ( 916 ) 381-5822 Sacramento CA. USA
- Lines: 27
- X-Newsreader: Tin 1.1 PL4
-
- jefftep@cs.utexas.edu (Jeffrey Grills) writes:
- : Some short time ago I wrote:
- : >I've been trying to track down why 0.98.6 doesn't boot
- : >for me. Unfortunately, I have some exams this week
- : >and I can't complete the investigation for a while, but
- : >I thought I'd announce what I've found.
- : >
- : >Booting hangs right before the partition table gets
- : >printed to the screen. So, i tracked down that, and
- : >added a printk() in the top of sys_setup() in
- : >kernel/blk_drv/genhd.c, just after the callable = 0;
- : >statement. Well, this printk() gets displayed on the
- : >screen, and then nothing else happens. it never
- : >shows the partition table and never says the partition
- : >table is okay.
-
- Have you made that image chain to your root device? Better try
- this before trying anything else. Here's how you go about doing it:
-
- rootdev (or rdev) [imagename] [rootdevice]
-
- where imagename is what file (or device if you're booting from
- a floppy) you want to modify, and rootdevice is where your root
- filesystem resides.
-
- --
- Born to void warranties! ianj@ijpc.UUCP
-