Re patch 4.6.99.17-4.6.99.18.diff.bz2 breaks i810 driver on Dell machines
Thanks for the output. I'm almost certain I know what the problem is,
but
I'd like to confirm my hunch. Please send me a copy of this system's
/proc/bus/pci/devices file.
Hello,
Here it is (I replaced tab by spaces).
Loïc
==
80862570 0 f008
0800
0010 80862572 10 e808 feb8 ed99
0800 0008 0008
00e8 808624d2 10 ff81
0020
usb-uhci
00e9 808624d4 13 ff61
0020
usb-uhci
00ea 808624d7 12 ff41
0020
usb-uhci
00eb 808624de 10 ff21
0020
usb-uhci
00ef 808624dd 17 ffa80800
0400
ehci_hcd
00f0 8086244e 0
PCI Bridge
00f8 808624d0 0
00f9 808624db 12 ffa1 feb7fc00
0010 0400
PIIX IDE
00fa 808624d1 12 fe01 fe11 fe21 fe31 fea1
0008 0004 0008 0004 0010
ata_piix
00fb 808624d3 11 eda1
0020
00fd 808624d5 11 ee01 edc1 feb7fa00 feb7f900
0100 0040 0200 0100
0160 8086100e 12 feae df41
0002 0040
e1000
Re: Re patch 4.6.99.17-4.6.99.18.diff.bz2 breaks i810 driver on Dell machines
On Tue, 3 Jul 2007, [EMAIL PROTECTED] wrote: Thanks for the output. I'm almost certain I know what the problem is, but I'd like to confirm my hunch. Please send me a copy of this system's /proc/bus/pci/devices file. Here it is (I replaced tab by spaces). Thanks. This confirms my hunch. I've just committed a change to fix this. It'll show up tomorrow (CVSWeb, cvsup, etc.) and in 4.6.99.27. Thanks. Marc. +--+--+ | Marc Aurele La France | work: 1-780-492-9310 | | Academic Information and| fax:1-780-492-1729 | |Communications Technologies | email: [EMAIL PROTECTED] | | 352 General Services Building +--+ | University of Alberta | | | Edmonton, Alberta |Standard disclaimers apply| | T6G 2H1 | | | CANADA | | +--+--+ XFree86 developer and VP. ATI driver and X server internals. ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re Re: Re patch 4.6.99.17-4.6.99.18.diff.bz2 breaks i810 driver on Dell machines
Thanks. This confirms my hunch. I've just committed a change to fix this. It'll show up tomorrow (CVSWeb, cvsup, etc.) and in 4.6.99.27. Okay, I'll try it as soon as possible. Thanks ! Loïc Mahé - ATOS ORIGIN INTEGRATION AMO DTI/ATM/VIG/LdBO-expertise calculateur Bureau M77 / [EMAIL PROTECTED] / +33 (0) 5 62 14 34 90
Re: Re patch 4.6.99.17-4.6.99.18.diff.bz2 breaks i810 driver on Dell machines
On Mon, 2 Jul 2007, [EMAIL PROTECTED] wrote: Without the output from `scanpci -v -v` that I asked you for, there is nothing I can rework it to. This is strange, my second message, submitted on 22/06, was sent by the list only on 30/06, along with you first answer. This is the reason I didn't saw the question about the scanpci. Yes, there appears to have been a glitch in our mailing lists, which seems to have been resolved now. Anyway, here it is (on the Dell GX270). This is the scanpci shipped with the faulty XFree86, which displays the INVALID IO ALLOCATION error. Thanks for the output. I'm almost certain I know what the problem is, but I'd like to confirm my hunch. Please send me a copy of this system's /proc/bus/pci/devices file. Thanks. Marc. +--+--+ | Marc Aurele La France | work: 1-780-492-9310 | | Academic Information and| fax:1-780-492-1729 | |Communications Technologies | email: [EMAIL PROTECTED] | | 352 General Services Building +--+ | University of Alberta | | | Edmonton, Alberta |Standard disclaimers apply| | T6G 2H1 | | | CANADA | | +--+--+ XFree86 developer and VP. ATI driver and X server internals. ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re patch 4.6.99.17-4.6.99.18.diff.bz2 breaks i810 driver on Dell machines
Okay, more investigation on this error. I noticed the same message (INVALID IO ALLOCATION) in the logfile for another chipset (ATI Technologies Inc RS480 [Radeon Xpress 200G Series]) on a Nec VL350 computer. I noticed a beep when starting XFree86, which this time doesn't fail. This beep probably comes from the BIOS. I tested again on the Dell GX270 and Dell GX280 and, indeed, they emit the beep too (but, as said, XFree86 fails on the computers). I looked deeper into the patch 4.6.99.17-4.6.99.18.diff.bz2 and found that this file modified by the patch is the culprit : xc/programs/Xserver/hw/xfree86/os-support/bus/linuxPci.c (1.14) bugfixes : 111. Various PCI-related changes (Marc La France): [...] So it has to be reworked, I think. Loïc, Toulouse, France [EMAIL PROTECTED] Envoyé par : [EMAIL PROTECTED] 18/06/2007 08:58 Veuillez répondre à devel@xfree86.org A devel@xfree86.org cc Objet patch 4.6.99.17-4.6.99.18.diff.bz2 breaks i810 driver on Dell machines Hello, I'm building XFree86 4.6+patches for a selection of computers with various video chipsets. The kernel is a 2.4.34. I found that the patch 4.6.99.17-4.6.99.18.diff.bz2 breaks the i810 driver for the Intel graphic chipset on these two Dell computers : - Dell Optiplex GX270 / i865G - Dell Optiplex GX280 / i915G But note that this computer works well : Dell Optiplex GX260 / i845G The syndrome : as soon as X startx, the screen becomes dark and the text consoles become unusable too (but the system doesn't crash). I can see this in /var/log/XFree86.0.log (this example is for the i915G) : [...] (--) Chipset 915G found (II) resource ranges after xf86ClaimFixedResources() call: [...] (II) Found conflict at: 0x3df (II) Found conflict at: 0x3bb (WW) INVALID IO ALLOCATION b: 0xe898 e: 0xe89f correcting^G (II) window: [0] -1 0 0x - 0x (0x1) IX[B] (II) resSize: [0] -1 0 0x - 0x (0x0) IX[B] (II) window fixed: [0] -1 0 0x - 0x (0x1) IX[B] and the log file stops here. Moreover, I have the same graphic chipsets (i865G and i915G) on non-Dell motherboards (MSI or Intel motherboards) and they work perfectly here. So I suspect that the problem comes from the Dell BIOS. Dell BIOSes are mostly not configurable, as you may know, and I didn't find a parameter which could be related to the problem. There are some pci-related files which are altered by the patch, the error probably comes from there. Loïc, Toulouse, France
Re: Re patch 4.6.99.17-4.6.99.18.diff.bz2 breaks i810 driver on Dell machines
On Fri, 22 Jun 2007, [EMAIL PROTECTED] wrote: Okay, more investigation on this error. I noticed the same message (INVALID IO ALLOCATION) in the logfile for another chipset (ATI Technologies Inc RS480 [Radeon Xpress 200G Series]) on a Nec VL350 computer. I noticed a beep when starting XFree86, which this time doesn't fail. This beep probably comes from the BIOS. I tested again on the Dell GX270 and Dell GX280 and, indeed, they emit the beep too (but, as said, XFree86 fails on the computers). The beep is part of the message... I looked deeper into the patch 4.6.99.17-4.6.99.18.diff.bz2 and found that this file modified by the patch is the culprit : xc/programs/Xserver/hw/xfree86/os-support/bus/linuxPci.c (1.14) bugfixes : 111. Various PCI-related changes (Marc La France): [...] So it has to be reworked, I think. Without the output from `scanpci -v -v` that I asked you for, there is nothing I can rework it to. Marc. +--+--+ | Marc Aurele La France | work: 1-780-492-9310 | | Academic Information and| fax:1-780-492-1729 | |Communications Technologies | email: [EMAIL PROTECTED] | | 352 General Services Building +--+ | University of Alberta | | | Edmonton, Alberta |Standard disclaimers apply| | T6G 2H1 | | | CANADA | | +--+--+ XFree86 developer and VP. ATI driver and X server internals. ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
