DRI doesn't work on 2.4.0 but does on prerelease-ac5
I was testing the 2.4.0 kernel by running "make exec" in the Mesa-3.4 sources, which builds and runs a bunch of demos, and was suprised to see one of the tests emit a message that said DRI wasn't available. It had been working before.
Just to make sure I then booted off of 2.4.0-prerelease-ac5 and it was working again.
This is with XFree86 4.0.1 on Slackware 7.1. I have an ATI Rage Millenium card on a machine with a 667 MHz Pentium III and 128 MB of 133 MHz RAM. The motherboard is an ASUS P3V4X. It has an ACPI bios but ACPI is disabled in the config.
Could XFree86 4.0.2 fix this? I had been waiting until the binary packages were available from ftp.slackware.com because Patrick Volkerding lays out the directories in a slightly different manner that he argues pretty convincingly is preferable, but it would be a drag for me to reproduce by building it myself.
AGP, VIA support, DRM, and r128 DRM are all compiled in statically rather than as modules.
In the /var/log/XFree86.0.log file I see the following under 2.4.0 final release:
(EE) r128(0): R128DRIScreenInit failed (DRM version = 2.1.2, expected 1.0.x). Disabling DRI.
(0): [drm] failed to remove DRM signal handler
(0): failed to destroy server context
(0): [drm] removed 1 reserved context for kernel
(0): [drm] unmapping 4096 bytes of SAREA 0xc5bb3000 at 0x40014000
in the corresponding point of the same file under 2.4.0-prerelease-ac5 I have:
(II) r128(0): [agp] Mode 0x1f000203 [AGP 0x1106/0x0691; Card 0x1002/0x5246] (II) r128(0): [agp] 8192 kB allocated with handle 0xcc82b000 (II) r128(0): [agp] ring handle = 0xe4000000
(II) r128(0): [agp] Ring mapped at 0x421d9000
(II) r128(0): [agp] ring read ptr handle = 0xe4101000
(II) r128(0): [agp] Ring read ptr mapped at 0x40015000
(II) r128(0): [agp] vertex buffers handle = 0xe4102000
(II) r128(0): [agp] Vertex buffers mapped at 0x422da000
(II) r128(0): [agp] indirect buffers handle = 0xe4202000
(II) r128(0): [agp] Indirect buffers mapped at 0x423da000
(II) r128(0): [agp] AGP texture map handle = 0xe4302000
(II) r128(0): [agp] AGP Texture map mapped at 0x424da000
(II) r128(0): [drm] register handle = 0xdd000000
(II) r128(0): [drm] Added 64 16384 byte vertex buffers
(II) r128(0): [drm] Mapped 64 vertex buffers
The relevant parts of my .config file are as follows (and are identical between the two kernel versions, I used "make oldconfig" and didn't change any options):
CONFIG_AGP=y
# CONFIG_AGP_INTEL is not set
# CONFIG_AGP_I810 is not setCONFIG_AGP_VIA=y
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_ALI is not setCONFIG_DRM=y
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_GAMMA is not setCONFIG_DRM_R128=y
# CONFIG_DRM_I810 is not set
# CONFIG_DRM_MGA is not set
If you want my whole .config file I could mail it in or post it on my website.
Mike
Signature · 10 lines
Michael D. Crawford GoingWare Inc. - Expert Software Development and Consulting http://www.goingware.com/ [email protected] Tilting at Windmills for a Better Tomorrow. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] Please read the FAQ at http://www.tux.org/lkml/
Quoted 2 lines · Michael D. Crawford
AGP, VIA support, DRM, and r128 DRM are all compiled in statically rather than as modules.
AGPGART doe *not* work if compiled statically. Compile it as a module. You will be much happier. (i.e. It might actually work.) I would also compile DRM and the r128 drivers as modules as well.
[email protected] | Note to AOL users: for a quick shortcut to reply
Alan Olsen | to my mail, just hit the ctrl, alt and del keys.
"In the future, everything will have its 15 minutes of blame."
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
On Saturday 06 January 2001 10:30 pm, Alan Olsen wrote:
| AGPGART doe *not* work if compiled statically. Compile it as a | module. You will be much happier. (i.e. It might actually work.) I | would also compile DRM and the r128 drivers as modules as well.
it's worked fine compiled into the kernel here, along with the dri and mga stuff since test4.
Signature · 9 lines
dep -- bipartisanship: an illogical construct not unlike the idea that if half the people like red and half the people like blue, the country's favorite color is purple. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] Please read the FAQ at http://www.tux.org/lkml/
Alan Olsen said once upon a time (Sat, 6 Jan 2001):
Quoted 8 lines · Michael D. Crawford
Quoted 3 lines
AGP, VIA support, DRM, and r128 DRM are all compiled in statically rather than as modules.
AGPGART doe *not* work if compiled statically. Compile it as a module. You will be much happier. (i.e. It might actually work.) I would also compile DRM and the r128 drivers as modules as well.
AGPGART works fine for me compiled in.
Dax
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 5 lines
Could XFree86 4.0.2 fix this? I had been waiting until the binary packages were available from ftp.slackware.com because Patrick Volkerding lays out the directories in a slightly different manner that he argues pretty convincingly is preferable, but it would be a drag for me to reproduce by building it myself.
XFree 4.0.2 will fix this.
Quoted 1 line
(EE) r128(0): R128DRIScreenInit failed (DRM version = 2.1.2, expected 1.0.x). Disabling DRI.
We made binary incompatible device interface changes with 4.0.2. These driver changes resulted in a more stable / faster / cleaner Rage 128 driver.
-Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/