Re: 2.6.10-mm2

From: Dave Airlie (airlied_at_gmail.com)
Date: 01/09/05

  • Next message: Linus Torvalds: "Re: uselib() & 2.6.X?"
    Date:	Sun, 9 Jan 2005 12:38:33 +1100
    To: Benoit Boissinot <bboissin@gmail.com>
    
    
    

    >
    > Removing the framebuffer from the boot command line solved it... (with
    > the patch that Mike Werner posted ; without it, it oopsed).
    >

    That's a bit weird as nothing should be different, I've just built
    vesafb into my kernel and booted and it works fine.. (with the oops
    patch...)

    vesafb: framebuffer at 0xe0000000, mapped to 0xe0880000, using 3072k,
    total 131072k
    vesafb: mode is 1024x768x16, linelength=2048, pages=84
    vesafb: protected mode interface info at c000:56cd
    vesafb: scrolling: redraw
    vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
    Console: switching to colour frame buffer device 128x48
    fb0: VESA VGA frame buffer device
    ACPI: Processor [CPU1] (supports 8 throttling states)
    Linux agpgart interface v0.101 (c) Dave Jones
    agpgart: Detected an Intel 865 Chipset.
    agpgart: AGP aperture is 128M @ 0x28000000

    ....
    [drm] Initialized drm 1.0.0 20040925
    ACPI: PCI interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16
    [drm] Initialized radeon 1.11.0 20020828 on minor 0:
    agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
    agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode
    agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode
    [drm] Loading R200 Microcode

    all good here... I'm trying to see if this could be a via only issue,
    or something even more tricky....

    If you could apply the patch I've attached (just adds some debug...)
    it'll narrow it down a small bit where it is failing for me...

    Thanks,
    Dave.

    
    

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/



  • Next message: Linus Torvalds: "Re: uselib() & 2.6.X?"

    Relevant Pages

    • oops in aty128_bl_set_power in 2.6.18-rc5
      ... ATY Rage128 frame buffer device on Rage128 PF PRO AGP ... agpgart: Putting AGP V2 device at 0000:00:0b.0 into 1x mode ... Faulting instruction address: 0xc01a62e8 ...
      (Linux-Kernel)
    • Problem with framebuffer in 2.6.0-test3
      ... If I compile with framebuffer I get weird results during boot. ... vesafb: framebuffer at 0xe6000000, mapped to 0xcf802000, size ... VGA16 VGA frame buffer device ... switching to colour frame buffer device 80x30 ...
      (Linux-Kernel)
    • Re: [9fans] Plan 9 Terminal Target
      ... vesafb: Elpin Systems VGA BIOS, GEODE LX, Version 6.12 ... Console: switching to colour frame buffer device 128x48 ...
      (comp.os.plan9)
    • Re: Weird framebuffer bug?
      ... vesafb: ... switching to colour frame buffer device ... VESA VGA frame buffer device ... Visual: TRUECOLOR ...
      (Linux-Kernel)
    • Bugzilla: PCI resource address mismatch
      ... In the working kernel, vesafb correctly ioremap's the framebuffer memory ... lspci reports the same thing: ... switching to colour frame buffer device 100x37 ...
      (Linux-Kernel)