Re: GRUB update problems

[Henry W. Peters]

Felix Zielcke wrote:
> Am Dienstag, den 05.01.2010, 13:07 -0500 schrieb Henry W. Peters:
>   
> > I run Debian Lenny sid/squeeze, the updater this morning just
> > "updated" 
> > my GRUB2 version... (not sure of the version).
> >     
>
> normally it doestn't make sense to have stable (lenny), testing
> (squeeze) and unstable (sid) in /etc/apt/sources.list
> Usually you only use one of them.
>
>   
> > I probably need to get the display resolution in GRUB to correspond to
> >
> > my ACTUAL desktop resolution... I'm guessing; so, until GRUB  works
> > out 
> > what appears to me, to be a 'bug' (?), or I can know what to do to 
> > remedy... perhaps there is a workaround someone can suggest?
> >     
>
> I think you didn't set a device in the debconf prompt which asked for
> one.
> You need to run grub-install to update it. Else the graphical terminal
> won't get anymore enabled by update-grub/grub-mkconfig.
>
> And also check GRUB_GFXMODE in /etc/default/grub, which is the
> resolution for GRUB if the graphical terminal is enabled.
>
>   
Not to seem ungrateful, but grubspeak is not too helpful at the moment, 
but nonetheless, I did try several of your suggestions (perhaps not 
correctly, because of maybe not understanding too well?)"

# grub-install
install_device not specified.
Usage: grub-install [OPTION] install_device
Install GRUB on your drive.

 -h, --help              print this message and exit
 -v, --version           print the version information and exit
 --modules=MODULES       pre-load specified modules MODULES
 --root-directory=DIR    install GRUB images under the directory DIR
                         instead of the root directory
 --grub-setup=FILE       use FILE as grub-setup
 --grub-mkimage=FILE     use FILE as grub-mkimage
 --grub-mkdevicemap=FILE use FILE as grub-mkdevicemap
 --grub-probe=FILE       use FILE as grub-probe
 --no-floppy             do not probe any floppy drive
 --recheck               probe a device map even if it already exists
 --force                 install even if problems are detected
 --disk-module=MODULE    disk module to use

INSTALL_DEVICE can be a GRUB device name or a system device filename.

grub-install copies GRUB images into the DIR/boot directory specified by
--root-directory, and uses grub-setup to install grub into the boot
sector.

Report bugs to <address@hidden>.

This was the message I got... I have no clue as to what "grub-install 
[OPTION] install_device" means... this is to say, what is the option?

Then I did check the /etc/default/grub file, & this is what I got (I 
took out the '# at the GRUB_GFXMODE=1440x900' & changed the 
resolution... I tried doing an '#update-grub' both in the terminal while 
booted & at startup in the recovery mode. Nothing seems to change... 
maybe it's the 'install_device not specified.' problem??


# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.

GRUB_DEFAULT=0
GRUB_TIMEOUT=30
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX="splash vga=795"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE=1440x900

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to 
Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_LINUX_RECOVERY="true"
> > & one more note, I also had a problem with GRUB (or what ever...) when
> > I 
> > hit the restart/shut down routine... it would sometimes only do a log 
> > off, & then I would have to do a restart from the log on screen,
> > well... 
> > it's back with this recent version of GRUB.
> >     
>
> This has nothing to do with GRUB.
>   
> > Any helpful help appreciated.
> >
> > Henry
> >
> >
> > _______________________________________________
> >     
>
>