Linux Framebuffer Layer development
 help / color / mirror / Atom feed
From: David J Ring Jr <n1ea@arrl.net>
To: linux-fbdev@vger.kernel.org
Subject: Re: Getting FB to work in Console
Date: Mon, 14 Nov 2011 01:10:45 +0000	[thread overview]
Message-ID: <alpine.DEB.2.00.1111140107280.2510@localhost.localdomain> (raw)
In-Reply-To: <CADO5RbhunU1X7mWwGDbVRc1FSPKBaLudAVav0TMkBoQ_1zp0Mw@mail.gmail.com>

I found a line in /etc/default/grub which has nomodeset in it and I 
disabled it.

Here is what I have in that file now.

I have a feeling that something in grub is not right.

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

GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
#GRUB_CMDLINE_LINUX_DEFAULT="nomodeset"
GRUB_CMDLINE_LINUX=""

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# 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_GFXMODEd0x480

# 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"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"

What do you think?  Is this where nomodeset is and does it look like this 
should work?  I still cannot get /dev/fb0

David


  parent reply	other threads:[~2011-11-14  1:10 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-12 23:42 Getting FB to work in Console D.J.J. Ring, Jr.
2011-11-13  1:00 ` Florian Tobias Schandinat
2011-11-13  2:46 ` David J Ring Jr
2011-11-13 16:57 ` Anatolij Gustschin
2011-11-13 18:58 ` David J Ring Jr
2011-11-13 19:11 ` David J Ring Jr
2011-11-13 20:00 ` Geert Uytterhoeven
2011-11-13 20:11 ` Anatolij Gustschin
2011-11-13 20:53 ` Anatolij Gustschin
2011-11-13 21:17 ` David J Ring Jr
2011-11-13 21:21 ` David J Ring Jr
2011-11-13 21:39 ` Anatolij Gustschin
2011-11-13 21:44 ` Bruno Prémont
2011-11-13 22:48 ` David J Ring Jr
2011-11-13 22:50 ` David J Ring Jr
2011-11-14  0:15 ` Anatolij Gustschin
2011-11-14  0:32 ` Anatolij Gustschin
2011-11-14  1:10 ` David J Ring Jr [this message]
2011-11-14 18:58 ` Anatolij Gustschin
2011-11-14 20:09 ` D.J.J. Ring, Jr.
2011-11-14 20:25 ` Bruno Prémont
2011-11-14 21:50 ` David J Ring Jr
2011-11-14 23:38 ` D.J.J. Ring, Jr.

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=alpine.DEB.2.00.1111140107280.2510@localhost.localdomain \
    --to=n1ea@arrl.net \
    --cc=linux-fbdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox