> On Wed, 21 Jun 2000, Daniel Woods wrote:
> > > Daniel Woods wrote:
> > > > Since I had to change the memory setting from 126 to 124
> > > > (more for onboard video), I changed lilo.conf to set
> > > > mem=126M, ran /sbin/lilo and now lilo shows up on bootup.
> > > >
> > > > So how do I reset things to use Grub instead ?
> > > > (and with my senith monitor problems, please give me a
> > > > command line answer, not X).
> > >
> > > use DrakBoot in DrakConf.
> >
> > I knew that, but my message did ask for non-X method.
> > (ie: command line command, or vi a file)
>
> fussy fussy fussy ;)
Yes, yes, yes.
> from a 'command line' type 'mc' and navigate to /boot/grub,
> .. ^^^^^^^^^^^^
> scroll to 'menu.lst'. Edit <F4> the line ....(here's mine):
I am so fussy, I still use vi (Lemmy-vi on windows). :)
> kernel (hd1,4)/vmlinuz root=/dev/hdb6 hdc=ide-scsi
>
> just put in mem=(the amount of ram I've got left after buyin
> a bogus 'onboard video' motherboard ;)... where mine says
> 'hdc=...', or add to it in case you've got a burner too ;) Be sure
> to put a space in between multiple args
>
> goin back to the 'command line', type 'whereis grub'. You'll
> prob'ly get that the answer is ' /usr/sbin/grub ' So from a
> 'command line', run grub. Sort'a kind'a like you'd rerun 'lilo'
> after editin that .conf :) Reboot, or from a 'command line' run
> 'info grub' to see if i'm full of sh!+ ;->
>
> seriously, there's a lot (maybe too much) in 'info grub'. I just
> started usin grub, and had to do just a little reading to figure
> out how to add the 'ide-scsi' line to get my burner goin.
> Difference is I'm not stuck on a 'command line' ;->>>>>>>>>>
> ~~ Tom Brinkman [EMAIL PROTECTED]
Using DrakBoot did not work since it never gives you an option to use
lilo or grub. So instead it just updated lilo.conf (I saw date change)
and rebooting goes into lilo mode.
So combining all the answers, I went into /boot/grub and edited
menu.lst to add the proper memory setting. Tried running ./install.sh
but it did not work because of permissions. chmod700 the file
(don't want users touching it), and ran it just fine. I tried
running /usr/sbin/grub but it seemed to only go into a menu mode.
Quit out of there, and rebooted... everything is good again.
Thanks... Dan.
