All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Henry W. Peters" <hwpeters@jamadots.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: GRUB update problems
Date: Tue, 05 Jan 2010 13:07:09 -0500	[thread overview]
Message-ID: <4B437FCD.4040609@jamadots.com> (raw)
In-Reply-To: <321078.3571.qm@web88205.mail.re2.yahoo.com>

I run Debian Lenny sid/squeeze, the updater this morning just "updated" 
my GRUB2 version... (not sure of the version).

Anyway, I have a Dell S1909 WX monitor at resolution 1440 x 900 
(analogue) at 60 Hz. (the recommended resolution). I do dual boot with 
Windows XP (sp3) & besides a GNOME desktop, I have xfce installed. So I 
use GRUB bootloader.

Since I got this monitor (I previously used Ubuntu distro), I have had a 
problem with it & Linux... (i.e., not in Windows). I discovered that I 
needed to change the display resolution via the 'Startup-Manager.' This 
apparently changes the resolution in GRUB. With the last two versions of 
GRUB, this worked fairly well, the  vertical lines (like a double 
shifted image) almost completely disappeared. This "newest" version of 
GRUB, the lines are back full force, & no parameter that I set in the 
'Startup-Manager' helps... (though, as a side note...  when set to so 
work with working monitor res. the text in the startup routine was too 
tiny for words (to be read)). It appears to be two display drivers 
conflicting... (????)

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?

& 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.

Any helpful help appreciated.

Henry



  reply	other threads:[~2010-01-05 18:07 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   ` Henry W. Peters [this message]
2010-01-05 18:16     ` GRUB update problems Felix Zielcke
2010-01-05 18:58       ` Henry W. Peters
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=4B437FCD.4040609@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.