Not to sound rude, but could you copy/paste the exact grub line? If it
turns out to be correct, you should probably file a bug.
Priceless,
Wasn't at all rude, but needed! I had been editing it so many times I
never noticed an extraneous character:) My bad!
Now that 1600x1000 works, it looks
I have a mobo with an Intel 3100, when I edit the grub conf with the closest
mode to what I want, 0x34B
it fails and asks me to scan. I scan and see its listed, and type it in
manually and it boots? Is this what's
expected with the Intel chips, or is there something I can do?
Thanks!
jlc
--
Joseph L. Casale wrote:
I have a mobo with an Intel 3100, when I edit the grub conf with the closest
mode to what I want, 0x34B
it fails and asks me to scan. I scan and see its listed, and type it in
manually and it boots? Is this what's
expected with the Intel chips, or is there something I
Try appending vga=0x34B without the quotes in grub.conf right after
rhgb quiet.
Sorry,
I guess it was ambiguous. That's what I have at which point it fails on booting
and when
I type 0x34B at the prompt, it then works.
Thanks!
jlc
--
fedora-list mailing list
fedora-list@redhat.com
To
Joseph L. Casale wrote:
Sorry,
I guess it was ambiguous. That's what I have at which point it fails on booting
and when
I type 0x34B at the prompt, it then works.
Not to sound rude, but could you copy/paste the exact grub line? If it
turns out to be correct, you should probably file a
On Sat, Dec 20, 2008 at 11:09 AM, Michael Cronenworth m...@cchtml.com wrote:
Joseph L. Casale wrote:
Sorry,
I guess it was ambiguous. That's what I have at which point it fails on
booting and when
I type 0x34B at the prompt, it then works.
Not to sound rude, but could you copy/paste the
Richard Shaw wrote:
On Sat, Dec 20, 2008 at 11:09 AM, Michael Cronenworth m...@cchtml.com wrote:
Joseph L. Casale wrote:
Sorry,
I guess it was ambiguous. That's what I have at which point it fails on
booting and when
I type 0x34B at the prompt, it then works.
Not to sound rude, but could
On Sat, Dec 20, 2008 at 8:19 PM, Mikkel L. Ellertson
mik...@infinity-ltd.com wrote:
Richard Shaw wrote:
On Sat, Dec 20, 2008 at 11:09 AM, Michael Cronenworth m...@cchtml.com
wrote:
Joseph L. Casale wrote:
Sorry,
I guess it was ambiguous. That's what I have at which point it fails on
