[Xen-bugs] [Bug 1156] New: Xorg failed to start on Intel Corporation 82G33/G31 Express Integrated Graphics Controller (Couldn't allocate video memory)

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1156

           Summary: Xorg failed to start on Intel Corporation 82G33/G31
                    Express Integrated Graphics Controller (Couldn't
                    allocate video memory)
           Product: Xen
           Version: unstable
          Platform: x86
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Hardware Support
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: nscheibl@xxxxxxxxx


On Fedora 8, 
i get the mercury repo from xen-3.2-testing.hg yesterday and it build properly
but when i boot with the kernel-2.6.18.8-xen i can't start Xorg due to a video
memory allocation problem.

xen-3.2-testing 
kernel-2.6.18.8-xen
( kernel-xen fedora packages have the same behaviour, whereas basic kernel
works)

Xorg failed to start on Intel Corporation 82G33/G31 Express Integrated Graphics
Controller using the kernel-xen Kernel.

I think the solution is something who looks like this: 
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=dc7a93190c21edbf3ed23e678ad04f852b9cff28


#########################################
EE from Xorg.log
(EE) GARTInit: Unable to open /dev/agpgart (No such file or directory)
(EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low?
(EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low?
(EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low?
(EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low?
(EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low?
(EE) intel(0): Couldn't allocate video memory

#########################################
lspci -vv
00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express
Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller])
        Subsystem: Giga-byte Technology Unknown device d000
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 16
        Region 0: Memory at e2300000 (32-bit, non-prefetchable) [size=512K]
        Region 1: I/O ports at d200 [size=8]
        Region 2: Memory at d0000000 (32-bit, prefetchable) [size=256M]
        Region 3: Memory at e2100000 (32-bit, non-prefetchable) [size=1M]
        Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- Queue=0/0
Enable-
                Address: 00000000  Data: 0000
        Capabilities: [d0] Power Management version 2
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-



Same behaviour to this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=430315
(Xorg.0.log file attached)


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs