From: "Henry W. Peters" <hwpeters@jamadots.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: GRUB update problems
Date: Tue, 05 Jan 2010 13:58:18 -0500 [thread overview]
Message-ID: <4B438BCA.60805@jamadots.com> (raw)
In-Reply-To: <1262715378.2635.8.camel@fz.local>
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 <bug-grub@gnu.org>.
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
>>
>>
>> _______________________________________________
>>
>
>
next prev parent reply other threads:[~2010-01-05 19:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 6:08 GRUB Faq Bruce Dubbs
2010-01-05 16:12 ` Lapohos Tibor
2010-01-05 18:07 ` GRUB update problems Henry W. Peters
2010-01-05 18:16 ` Felix Zielcke
2010-01-05 18:58 ` Henry W. Peters [this message]
2010-01-05 20:50 ` Felix Zielcke
2010-01-06 0:23 ` Henry W. Peters
2010-01-06 21:50 ` Henry W. Peters
2010-01-08 15:39 ` Henry W. Peters
2010-01-08 16:13 ` Robert Millan
2010-01-08 17:01 ` Henry W. Peters
2010-01-08 19:26 ` Henry W. Peters
2010-01-05 19:16 ` GRUB Faq Lapohos Tibor
2010-01-06 2:50 ` Bruce Dubbs
2010-01-07 19:40 ` Robert Millan
2010-01-07 19:52 ` Bruce Dubbs
2010-01-08 22:12 ` richardvoigt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B438BCA.60805@jamadots.com \
--to=hwpeters@jamadots.com \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.