lkml.org 
[lkml]   [2003]   [Mar]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: vesafb problem
    On Thu, 27 Mar 2003 11:34:25 -0800
    Walt H <waltabbyh@comcast.net> wrote:

    > Jurriaan wrote:
    >
    > >
    > > I had a similar problem with 1 Gb Ram, and received this answer on the
    > > linux-kernel mailinglist:

    <sip>

    > > thunder7> framebuffer just fine (well, it doesn't work and writes
    > > thunder7> funky patters to the screen, but at least
    > > thunder7> ioremap_nocache() works fine).
    > >
    > > thunder7> What is the reason ioremap_nocache() fails? Is this
    > > thunder7> something that can be prevented? I am not entirely clear
    > > thunder7> on what is happening anyway (real memory, virtual
    > > thunder7> memory, nocache-memory, io-memory - a little bit above

    <snip>

    > > This means with "mem=512M", you will probably have about 500M of
    > > vmalloc space, which is more than enough to ioremap the framebuffer.
    > >

    <snip>

    > > To see if this is it, booting with mem=512M would be a good test.
    > >
    > > Kind regards,
    > > Jurriaan
    >
    > Thanks for the reply. That is indeed what is doing it. When I added
    > mem=512M, I had two smiling penguins on boot :) My vid card does have
    > 128MB Ram, but I also tend to agree that I'm not sure that the
    > framebuffer needs to remap *all* of its memory. But, for now, I think
    > I'll add the hack (256 << 20) to make it work. Any ideas if this might
    > have unforseen bad effects? Might it screw up highmem I/O? Thanks again,
    >
    > -Walt


    Strange I'm having the same problem, but I only have 256MB of memory and my GeForce 2 only has 32MB. This is what's on my messages file:


    vesafb: framebuffer at 0xe0000000, mapped to 0xd0807000, size 32768k
    vesafb: mode is 800x600x16, linelength=1600, pages=3
    vesafb: protected mode interface info at c000:c060
    vesafb: scrolling: redraw
    vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0
    Looking for splash picture.... found (800x600, 13683 bytes).
    Console: switching to colour frame buffer device 82x30
    fb0: VESA VGA frame buffer device

    [unhandled content-type:application/pgp-signature]
    \
     
     \ /
      Last update: 2005-03-22 13:34    [W:0.021 / U:30.928 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site