I'm not so sure. The system.map file is just a file with symbol names and addresses of the Linux kernel binary. It's primary use is for debugging kernel "oops" messages with ksymoops. It has no relevance to booting Linux and really doesn't even need to be there. I think you should make sure you have a menu.lst (that's .lst (list) NOT .1st (one-st) ) file in /boot/grub and that it follows proper syntax. The file should look something like this: #menu.lst default=0 timeout=10 title Linux 2.4.19 root (hd0,0) kernel /vmlinuz ro root=/dev/hda3 > -----Original Message----- > From: owner-kclug@marauder.illiana.net > [mailto:owner-kclug@marauder.illiana.net]On Behalf Of Brad Crotchett > Sent: Thursday, November 21, 2002 8:32 AM > To: kclug@kclug.org > Subject: Re: When does grub print 'GRUB' > > > I can boot into linux rescue and edit my grub file just fine. I am > thinking you are right about the system.map being the problem. I will > play around with that. Thanks for the help. > > Brad > > -----Forwarded Message----- > > > From: Dale > > To: kclug > > Subject: Re: When does grub print 'GRUB' > > Date: 21 Nov 2002 04:25:45 -0800 > > > > I would be willing to wager that the problem is in > > your grub config file. I remember playing with a > > mandrake distro one time and having that > > problem...Main reason I walked away from grub and back > > to the wonderful world of lilo... anyway.. if I > > remember right I had to use a rescue disk to get the > > system into maintanence mode. > > >From there I was able to mount the drive I needed and > > once I got the grubby config file edited to see the > > system.map correctly was finally able to boot. > > I know that isn't a lot of help.. but may give you a > > idea of the direction you need to go in. > > > > > > __________________________________________________ > > Do you Yahoo!? > > Yahoo! Mail Plus – Powerful. Affordable. Sign up now. > > http://mailplus.yahoo.com > > > > > > > > > >