All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roger <rogerx.oss-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: Display goes off when framebuffer enabled and Kernel Panic with fbset
Date: Fri, 3 Dec 2010 22:59:25 -0900	[thread overview]
Message-ID: <20101204075925.GB4170@localhost2.local> (raw)
In-Reply-To: <20101204072803.GA4170-bi+AKbBUZKbUbxaO3c2PGA@public.gmane.org>

I yanked the compiled in nouveau-drm from kernel 2.6.35 and reinstalled the
snapshot =x11-base/nouveau-drm-20100811 package providing kernel drivers.

Framebuffer mode works fine and dandy along with fbset -i:
mode "1680x1050"
    geometry 1680 1050 1680 1050 32
    timings 0 0 0 0 0 0 0
    rgba 8/16,8/8,8/0,0/0
endmode

Frame buffer device information:
    Name        : nouveaufb
    Address     : 0xd0048000
    Size        : 7258112
    Type        : PACKED PIXELS
    Visual      : TRUECOLOR
    XPanStep    : 1
    YPanStep    : 1
    YWrapStep   : 0
    LineLength  : 6912
    MMIO Address: 0xd0000000
    MMIO Size   : 134217728
    Accelerator : No


Looks like I have some newer masked 2.6.36 kernel versions I can try, to see if
this bug still exists?


On Fri, Dec 03, 2010 at 10:28:03PM -0900, Roger wrote:
>Kernel 2.6.35 (gentoo sources)
>
>I get a LCD Display with initial console output, but when Nouveau starts and
>framebuffer is initiated, the LCD display powers off.
>
>
>I then get the following panic when using fbset -i/-a:
># cat /proc/kmsg
><1>BUG: unable to handle kernel NULL pointer dereference at (null)
><1>IP: [<c126e717>] fb_open+0x67/0x140
><4>*pde = 00000000

-- 
Roger
http://rogerx.freeshell.org/

  parent reply	other threads:[~2010-12-04  7:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-04  7:28 Display goes off when framebuffer enabled and Kernel Panic with fbset Roger
     [not found] ` <20101204072803.GA4170-bi+AKbBUZKbUbxaO3c2PGA@public.gmane.org>
2010-12-04  7:59   ` Roger [this message]
     [not found]     ` <20101204075925.GB4170-bi+AKbBUZKbUbxaO3c2PGA@public.gmane.org>
2010-12-04 11:33       ` Pekka Paalanen
2010-12-05  7:02       ` Roger
     [not found]         ` <20101205070234.GB4102-bi+AKbBUZKbUbxaO3c2PGA@public.gmane.org>
2010-12-05 11:38           ` Pekka Paalanen
     [not found]             ` <20101205133804.5430594f-cxYvVS3buNOdIgDiPM52R8c4bpwCjbIv@public.gmane.org>
2010-12-06  1:12               ` Roger
     [not found]                 ` <20101206011231.GC4122-bi+AKbBUZKbUbxaO3c2PGA@public.gmane.org>
2010-12-08  9:34                   ` Roger
     [not found]                     ` <20101208093458.GA11429-bi+AKbBUZKbUbxaO3c2PGA@public.gmane.org>
2010-12-08 12:23                       ` rogerx.oss-Re5JQEeQqe8AvxtiuMwx3w
     [not found]                         ` <20101208122300.GA4480-bi+AKbBUZKbUbxaO3c2PGA@public.gmane.org>
2010-12-09  0:42                           ` Roger
     [not found]                             ` <20101209004202.GA4477-bi+AKbBUZKbUbxaO3c2PGA@public.gmane.org>
2010-12-09  2:13                               ` Roger
2010-12-09 15:38                               ` Francisco Jerez
     [not found]                                 ` <8762v3ards.fsf-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org>
2010-12-10 10:43                                   ` Roger
     [not found]                                     ` <20101210104352.GA4505-bi+AKbBUZKbUbxaO3c2PGA@public.gmane.org>
2010-12-11  2:24                                       ` Emil Velikov
2010-12-11  7:57                                         ` Roger
2010-12-11  1:54                                   ` Roger
2010-12-06  1:04           ` Roger
     [not found]             ` <20101206010422.GB4122-bi+AKbBUZKbUbxaO3c2PGA@public.gmane.org>
2010-12-06  5:35               ` Roger

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=20101204075925.GB4170@localhost2.local \
    --to=rogerx.oss-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.