Arch Linux

What errors do you get, I can't reproduce this and without a log this bugreport is useless.

Where can I get a log? I looked for it in /var/log but I did not find anything..

There's /var/log/Xorg.0.log and Xorg.0.log.old. You're also talking about an error message that is repeated many times, but you don't tell us which error message it is.

Because I did not remember it.. It said about:

INTEL 0
INTEL 0
INTEL 0
...

Please provide a detailed log.

Same here, the screen just goes blank when starting up Xorg on i686/intel x4500.

Last working packages are xorg-server-1.5.1-1 and xf86-video-intel-2.4.2-1.

I have written down the error, in Xorg.0.log seems all good, in fact all works right (application on startup, daemons, ecc)

After 20-30 seconds i can read this:

(EE) intel (0) underrun on pipe B!
(EE) intel (0) underrun on pipe B!
(EE) intel (0) underrun on pipe B!
... ecc

And later a single line with:
Error: Malformed line (no filename) - Ignoring entry.

Then I read again (EE) intel ... for (too) many lines..

Please ignore my comment and Xorg.0.log above. Its actually another bug, this one: http://bugs.archlinux.org/task/11875

I'm unsure if this is the same problem. I have an 845G and with UXA+Tiling, the display is corrupted. With tiling disabled, the display is partially rendered, many elements don't appear (ie, only parts of a line of text, buttons and icons missing.) The freekdestop bug is here: https://bugs.freedesktop.org/show_bug.cgi?id=18060

Attached is an Xorg log with tiling disabled.

Having the same issues as the thread starter. I'm running Arch on the Acer Aspire One 150L.

lscpi output and xorg log are attached.

In the meantime, downgrading to xf86-video-intel 2.4.2-1 solves the problem.

Found!
The real problem is Compiz!! Perhaps we have to update it..

Try starting X keeping compiz disabled!

Simone, what videochip do you have? On some chipsets the 2.5.0 driver fails to initialize correctly, causing X.Org to use swrast_dri instead of the intel dri driver. GL Compositing doesn't work with swrast_dri at this moment.

00:00.0 Host bridge: Intel Corporation Mobile 945GME Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)

What could i do? Wait for support?

I have the exact same chip as Simone - but I do NOT have compiz installed. I use openbox and still get the underrun errors with 2.5.0.

Some interesting bits from the Xorg.0.log:

(EE) intel(0): I830 Dma Initialization Failed

(II) AIGLX: Screen 0 is not DRI capable
(II) AIGLX: Loaded and initialized /usr/lib/xorg/modules/dri/swrast_dri.so
(II) GLX: Initialized DRISWRAST GL provider for screen 0

From poking around on the xorg mailing lists from this month, I suspect that the problem I'm having is actually a different bug than the G4x crowd here is having.

There's a kernel patch that goes hand in hand with 2.5.0 that affects the G4x series. Maybe that's what's needed to fix the G4x problems? http://lists.freedesktop.org/archives/xorg/2008-October/039599.html I checked my kernel git repo, this patch went into Linus' tree Oct 14. This patch hasn't made it into the 2.6.27.y maintenance tree (at least not as of v2.6.27.4) so I don't think it's in the kernel arch is using.

Should I open a new bug, or keep my issue here in the "intel 2.5.0 is made of fail" bug?

From poking around on the xorg mailing lists from this month, I suspect that the problem I'm having is actually a different bug than the G4x crowd here is having.

There's a kernel patch that goes hand in hand with 2.5.0 that affects the G4x series. Maybe that's what's needed to fix the G4x problems? http://lists.freedesktop.org/archives/xorg/2008-October/039599.html I checked my kernel git repo, this patch went into Linus' tree Oct 14. This patch hasn't made it into the 2.6.27.y maintenance tree (at least not as of v2.6.27.4) so I don't think it's in the kernel arch is using.

Should I open a new bug, or keep my issue here in the "intel 2.5.0 is made of fail" bug?

Matthew: Doesn't UXA require a custom kernel patch at the moment, or is this already in the arch 2.6.27 kernel?

Either way, I think your bug is different but I'm a noob at this. However, I've learnt it's better to file a new bug if you are unsure. They are easy to close if it turns out to be a duplicate, and it generally helps keeping things organized. The other scenario, posting different bugs under same ticket is more of a hassle to work with for everybody.

Joel, Matthew: A bug has been filed already: http://bugs.archlinux.org/task/11875

However, this patch only solves the crash on G4x but not the other issues like broken DRI or this one here...

Jan: I thought that #11875 was a duplicate of this bug.
Joel: As I understand it, this version of the intel driver requires a corresponding patch to the kernel that fixes G4x memory allocation problems. That is, this fix requires complementary fixes in both the kernel (intel-agp) and the driver, and it seems that in shipping this version of the driver without a patched kernel, the G4x series has been disabled.

From the 2.4.98 changelog:
Eric Anholt (12):
*snip*
Fix broken stolen memory counting on G4X.
*snip*

This fix requires this patch: http://git.kernel.org/?p=linux/kernel/git/anholt/drm-intel.git;a=commit;h=2052746fc8397130c120f0194a89938b0b62b6cb The patch is from Anholt's tree, and he states on the commit log that this patch corresponds to the patch introduced into 2.4.98.

I think I'll go open a new bug for the 845 problem so that this bug can be closed if/when the G4x problems are resolved.