Re: boot screen

[Philip Bernstein <ppberns@hvc.rr.com>]

Hi,

  Thanks again for your input.  Alas I am doomed to just dealing with 
it at this point.  I ran dmesg | grep vesafb and got the command prompt 
back empty.  I also just tried modifying the menu.lst with some of your 
suggestions from below and a couple of variations of them all with no 
luck.  At this point I have to put this on the back burner because this 
is more of a nit-pick with me as opposed to it being a system problem 
and the wife has got a "honey do" list I need to tackle.
  Thanks for your help and I will try to keep along this path to see if 
there's anything I can do.



Anders Lövgren wrote:
> On Friday 23 May 2008 23.56.31 Philip Bernstein wrote:
> > Hi,
> >
> >     Thanks but I probably should have given out more info here.  That
> > file or path does not exist on my system.  I am running on an AMD64 bit
> > machine with a Nvidia graphics card (GeForce 7300GT) 2 gig memory.  In
> > my /usr/src directory I have the following:
> > "linux-headers-2.6.24-17-generic"  I ran find on it and came up with:
> > /usr/src/linux-headers-2.6.24-17-generic/include/config/fb/vesa.h which
> > in this case is a zero byte file.  I am running Kubuntu 8.04 with all
> > the latest updates (this worked this way even in Kubuntu 7.10).
>
> Hi,
>
> The file vesafb.txt is from the documentation bundled with the kernel source.
> Heres an excerpt from vesafb.txt that documents the possible VESA video
> modes:
>
>      | 640x480  800x600  1024x768 1280x1024
> ----+-------------------------------------
> 256 |  0x301    0x303    0x305    0x307
> 32k |  0x310    0x313    0x316    0x319
> 64k |  0x311    0x314    0x317    0x31A
> 16M |  0x312    0x315    0x318    0x31B
>
> I don't know anything about Kubuntu's kernel configuration, but you can check
> the output from the vesafb kernel code by running 'dmesg | grep vesafb' in an
> terminal to verify that the kernel supports vesafb and can access the video
> memory direct.
>
> // Anders
>
> > Anders Lövgren wrote:
> > > On Tuesday 20 May 2008 12.49.03 Philip Bernstein wrote:
> > > > Hi,
> > > >
> > > >        I have several systems and on them when I boot I can see all the
> > > > info scroll across the screen with OK or FAIL (on the right hand side)
> > > > depending on how things go (in menu.lst I have removed from the boot
> > > > lines "splash" so I don't get the boot splash).
> > > > But on my amd64 system the boot messages are quite large and I can't see
> > > > the OK or FAIL indicators (on the right hand side of the display).  Now
> > > > on the other systems I see that there is on the boot line in menu.lst
> > > > "vga=791". I tried to put that in the amd64 menu.lst and all I get is a
> > > > blank screen during boot up.  After the system boots, everything is fine
> > > > and  get my graphics back and all works.  Anyone notice this during
> > > > there boot up and found how to reduce the graphics on boot up so you can
> > > > see whats going on?
> > > >
> > > > --
> > > > Philip Bernstein
> > > > ppberns@hvc.rr.com
> > > Hi,
> > >
> > > The vga=xxx values usually depends on the monitor, look inside the
> > > file /usr/src/linux/Documentation/fb/vesafb.txt. For my 19" LCD I use
> > > vga=0x31b (1280x1024, 32-bit).
> > >
> > > You may also need something like video=vesafb:1280x1024-32 to get it
> > > working.
> > >
> > > // Anders
> > --
> > Philip Bernstein
> > ppberns@hvc.rr.com

--
Philip Bernstein
ppberns@hvc.rr.com