Re: 2.6.10-mm2

[Dave Airlie]

> 
> 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.

Attachment: my_agp_debug_patch
Description: Binary data