Re: F10 and built-in Intel graphics [SOLVED]
On Mon, 2009-03-16 at 09:38 -0700, suvayu ali wrote: > 2009/3/16 M A Young > > > > I recommend that you do a text based install (add text to the boot line), > > and once you have it > >installed, boot to a text console (add 3 to the boot line), then add Option > >"NoAccel" "true" to the > >Device section of /etc/X11/xorg.conf > > > On a fresh install he probably won't have an xorg.conf since this is > F10. And the default install also doesn't include > system-config-display. What he needs to do is generate an xorg.conf > using either > > $ Xorg -configure > > or, install system-config-display using yum and use > > $ system-config-display --tui > > Hope that helps. > I can't find the other e-mail in which someone suggested using XAA acceleration, but that seems to have worked so far. Thanks, all! > -- > Suvayu > > Open source is the future. It sets us free. > > -- Matthew Saltzman Clemson University Math Sciences mjs AT clemson DOT edu http://www.math.clemson.edu/~mjs -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F10 and built-in Intel graphics [SOLVED]
On Tuesday 17 March 2009 19:18, Matthew Saltzman wrote: > > I can't find the other e-mail in which someone suggested using XAA > acceleration, but that seems to have worked so far. Thanks, all! It doesn't work. It improves the time between two crashes, but does not eliminate them. The only workaround that makes intel drivers stable atm is to add Option "NoAccel" "true" into xorg.conf, but that kind of defeats the purpose of having a supported, open source, 3D accelerated driver. I have also set XAA instead of EXA, and it does slightly improve the situation, but don't rely on it. The problem here seems not to be just the transition from the old XAA to the new EXA. The bug is somewhere deeper, and it looks like to be an interplay of various things in the intel driver itself, the kernel, the X, the usage of 3D acceleration by the apps on top of X and so on. That is why crashes appear to be random, why it is almost impossible to trigger the bug intentionally and why there is no fix for cca 5 months now. So much for the famous Open Source support. If it were a nVidia bug, it would be just fixed in the next release of their closed-source driver. Even ATI's buggy flgrx driver gets fixed when the bug is severe enough. And here we are having the source completely open for the intel driver, and a bug that so radically affects all Intel cards is not fixed for half a year now... Best, :-) Marko -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F10 and built-in Intel graphics [SOLVED]
Marko Vojinovic wrote: > and a bug that so radically affects all Intel cards is not fixed for half > a year now... It doesn't affect all Intel cards, only 945 and older. My GM965 works great in F10. Kevin Kofler -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F10 and built-in Intel graphics [SOLVED]
Marko Vojinovic wrote: On Tuesday 17 March 2009 19:18, Matthew Saltzman wrote: I can't find the other e-mail in which someone suggested using XAA acceleration, but that seems to have worked so far. Thanks, all! It doesn't work. It improves the time between two crashes, but does not eliminate them. The only workaround that makes intel drivers stable atm is to add Option "NoAccel" "true" into xorg.conf, but that kind of defeats the purpose of having a supported, open source, 3D accelerated driver. I have also set XAA instead of EXA, and it does slightly improve the situation, but don't rely on it. The problem here seems not to be just the transition from the old XAA to the new EXA. The bug is somewhere deeper, and it looks like to be an interplay of various things in the intel driver itself, the kernel, the X, the usage of 3D acceleration by the apps on top of X and so on. That is why crashes appear to be random, why it is almost impossible to trigger the bug intentionally and why there is no fix for cca 5 months now. So much for the famous Open Source support. If it were a nVidia bug, it would be just fixed in the next release of their closed-source driver. Even ATI's buggy flgrx driver gets fixed when the bug is severe enough. And here we are having the source completely open for the intel driver, and a bug that so radically affects all Intel cards is not fixed for half a year now... Best, :-) Marko well i've been using my aspire one on F10 since the day of the F10 release with the exa acceleration method, i'm scoring ~780 in glxgears with glxgears -geometry 300x300+360+150 as the command, i've yet to have a X lockup or crash either and i'm using compositing in xfwm4 too, and the plymouth solar boot works well too. obviously not everyone is having such a good time with their intel gfx hardware, but not everyone is having problems either ;) phil -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F10 and built-in Intel graphics [SOLVED]
On Thu, Mar 19, 2009 at 07:06:48PM +0100, Kevin Kofler wrote: > Marko Vojinovic wrote: > > and a bug that so radically affects all Intel cards is not fixed for half > > a year now... > > It doesn't affect all Intel cards, only 945 and older. My GM965 works great > in F10. While I can't recall, at the moment, which Intel graphics chipset is used in the eeepc 901, F10 works fine on mine. So it's not ALL intel graphics chips that are busted. -- Fred Smith -- fre...@fcshome.stoneham.ma.us - "For him who is able to keep you from falling and to present you before his glorious presence without fault and with great joy--to the only God our Savior be glory, majesty, power and authority, through Jesus Christ our Lord, before all ages, now and forevermore! Amen." - Jude 1:24,25 (niv) - pgp8VfPTm1Kk5.pgp Description: PGP signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F10 and built-in Intel graphics [SOLVED]
On Thursday 19 March 2009 19:06, Kevin Kofler wrote: > Marko Vojinovic wrote: > > and a bug that so radically affects all Intel cards is not fixed for half > > a year now... > > It doesn't affect all Intel cards, only 945 and older. My GM965 works great > in F10. I'd say you are just being lucky: [r...@yoda ~]# lspci -v 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Siemens Computers Device 110f Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at fc00 (64-bit, non-prefetchable) [size=1M] Memory at d000 (64-bit, prefetchable) [size=256M] I/O ports at 18f8 [size=8] Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- Count=1/1 Enable- Capabilities: [d0] Power Management version 3 Kernel modules: intelfb [r...@yoda ~]# less /var/log/Xorg.0.log.old Backtrace: 0: /usr/bin/X(xorg_backtrace+0x26) [0x4e7c96] 1: /usr/bin/X(mieqEnqueue+0x291) [0x4c87d1] 2: /usr/bin/X(xf86PostMotionEventP+0xc4) [0x4914c4] 3: /usr/bin/X(xf86PostMotionEvent+0xa9) [0x491699] 4: /usr/lib64/xorg/modules/input//evdev_drv.so [0x19f9472] 5: /usr/bin/X [0x47a795] 6: /usr/bin/X [0x46b337] 7: /lib64/libc.so.6 [0x3522232f90] 8: /lib64/libc.so.6(ioctl+0x7) [0x35222de037] 9: /usr/lib64/libdrm.so.2 [0x3538603023] 10: /usr/lib64/libdrm.so.2(drmCommandNone+0x16) [0x3538603326] 11: /usr/lib64/dri/i965_dri.so(intelSwapBuffers+0x44e) [0x13c5f95] 12: /usr/lib64/dri/i965_dri.so [0x13c03e2] 13: /usr/lib64/xorg/modules/extensions//libglx.so [0xa027ff] 14: /usr/lib64/xorg/modules/extensions//libglx.so [0x9f6656] 15: /usr/lib64/xorg/modules/extensions//libglx.so [0x9f98f2] 16: /usr/bin/X(Dispatch+0x364) [0x446904] 17: /usr/bin/X(main+0x45d) [0x42cd4d] 18: /lib64/libc.so.6(__libc_start_main+0xe6) [0x352221e576] 19: /usr/bin/X [0x42c129] [mi] mieqEnequeue: out-of-order valuator event; dropping. [mi] EQ overflowing. The server is probably stuck in an infinite loop. [mi] mieqEnequeue: out-of-order valuator event; dropping. [mi] EQ overflowing. The server is probably stuck in an infinite loop. Best, :-) Marko -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F10 and built-in Intel graphics [SOLVED]
On Thursday 19 March 2009 20:12, psmith wrote: > Marko Vojinovic wrote: > > On Tuesday 17 March 2009 19:18, Matthew Saltzman wrote: > > > > So much for the famous Open Source support. If it were a nVidia bug, it > > would be just fixed in the next release of their closed-source driver. > > Even ATI's buggy flgrx driver gets fixed when the bug is severe enough. > > And here we are having the source completely open for the intel driver, > > and a bug that so radically affects all Intel cards is not fixed for half > > a year now... > > well i've been using my aspire one on F10 since the day of the F10 > release with the exa acceleration method, i'm scoring ~780 in glxgears with > > glxgears -geometry 300x300+360+150 > > as the command, i've yet to have a X lockup or crash either and i'm > using compositing in xfwm4 too, and the plymouth solar boot works well > too. obviously not everyone is having such a good time with their intel > gfx hardware, but not everyone is having problems either ;) Ok, well, the "all Intel cards" part was under the . Of course there may be those unaffected. But nevertheless, this bug is far from an isolated case with one type of hardware or such. It does affect many people with a whole range of Intel hardware. Btw, the plymouth boot didn't work for me out of the box, I still see the text-mode progress bar. Did you do anything specific to enable graphical boot? Best, :-) Marko -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F10 and built-in Intel graphics [SOLVED]
Marko Vojinovic wrote: > Btw, the plymouth boot didn't work for me out of the box, I still see the > text-mode progress bar. Did you do anything specific to enable graphical > boot? vga=0x318 That's the ugly vesafb hack and it will also use only 1024×768 and not your native resolution, but it does get Plymouth to show its graphical UI. Kevin Kofler -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
