Re: Messed up my rc.d/rc.6...badly

On Fri, 21 Sep 2012 21:04:39 +0700
Willy Sudiarto Raharjo <[email protected]> wrote:

> >   Any ideas what happened? I've not changed anything other than the rc.6
> > (which now works as it should) and the lilo.conf to have 'vga=318' (no
> > quotes) and of course as root did the 'lilo' command. I got something real
> > strange when I did that though:
> >
> > root@oogah:~# lilo
> > Warning: LBA32 addressing assumed
> > Warning: Unable to determine video adapter in use in the present system.
> > Warning: Video adapter does not support VESA BIOS extensions needed for
> >   display of 256 colors.  Boot loader will fall back to TEXT only operation.
> > Added Slackware *
> > Added SlackwareTOO
> > 3 warnings were issued.
> >
> >   Any idea how or why this is happening and how to fix it? It still does it
> >   when I put the vga=791 back in lilo.conf.
> 
> try
> vga = 773
> 

  That didn't work either, but I figured out something...

  If I used your suggestion above, I would still get the prompt about having to
  choose something, only this time the choice had no u or 318 but was a very
  short list of 1 through 6 of 60x34 etc.

  When I'd choose one of those (I went through all 6) I would get a kernel
  panic and would have to boot with the install disc doing the hugesmp.s thing.

  A month+ ago I rebuilt my kernel and things were working fine. My lilo.conf
  directed it to boot that kernel (which was 3.1MB smaller btw), and things
  were working fine.

  Today, with this new problem, for the heck of it, I had my lilo.conf boot the
  regular, normal-installed hugesmp kernel...and things worked just fine. I was
  able to boot right up with no panics or messages from lilo about unknown
  graphics cards or whatever.

  Very strange and unfortunately I have to either go through making another
  custom kernel or stick with the stock huge kernel until I (or someone else)
  figures out why suddenly I can't use my custom kernel anymore (I suspect it
  has something to do with the stock rc.6 you sent me and I'm now using. I'm
  not suggesting you did something malicious, I just think that it's not quite
  what my system had after I made my custom kernel and whatever else
  adjustments I made to it before the last one that messed it up). Oh
  well...life in the woods.

  Thank you for the help with this anyway, it's greatly appreciated.


  John