Summary: | media-libs/mesa-7.7-r1: do_ioctls: Failed to get GB pipe count, error number -22 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Martin Mokrejš <mmokrejs> |
Component: | Current packages | Assignee: | Gentoo X packagers <x11> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | MostAwesomeDude |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
xdm.log
dmesg xdm.log (mesa-7.5.2) Xorg.log.0 (mesa-7.5.2) |
Description
Martin Mokrejš
2010-01-03 12:05:40 UTC
Created attachment 215006 [details]
xdm.log
BTW, have no /etc/X11/xorg.conf, I rely completely on autodetection as the upgrade from 1.6 series xorg-server to 1.7 somehow did not work with my xorg.conf.
Created attachment 215007 [details]
dmesg
This has to do with my upgrade away from x11-base/xorg-server-1.7.3 to x11-base/xorg-server-1.7.3.902 (I cannot revert as the original ebuild is now gone from portage), or x11-libs/libdrm-2.4.15 to x11-libs/libdrm-2.4.17 transition or lest likely with app-laptop/radeontool-1.5-r3 to app-laptop/radeontool-1.6. upgrade. Recompilation of x11-drivers/ libdrm, xorg-server, mesa does not help. I will re-try downgrade of libdrm although I did that without any luck. BTW, I have x11-drivers/xf86-video-ati-6.12.4 for about two months so that cannot e the cause. (In reply to comment #3) > > Recompilation of x11-drivers/ libdrm, xorg-server, mesa does not help. I will > re-try downgrade of libdrm although I did that without any luck. > > BTW, I have x11-drivers/xf86-video-ati-6.12.4 for about two months so that > cannot be the cause. So, I tried downgrade of libdrm, xorg-server to 1.7.3-901-r1, recompiled x11-drivers/, mesa-7.7-r1, no luck. I finally have a functional system (getting xdm login) after downgrade to media-libs/mesa-7.5.2. I will attach xdm.log and X.org.log files for this working situation. Created attachment 215050 [details]
xdm.log (mesa-7.5.2)
Created attachment 215052 [details]
Xorg.log.0 (mesa-7.5.2)
And, decent upgrade of mesa to media-libs/mesa-7.6.1 did not break my system so I conclude the bug got introduced between 7.6.1 and 7.7. You are using Radeon Gallium without KMS enabled. This will never work. Not sure how to properly close this. Please file Radeon Gallium bugs upstream and keep in mind that it is testing-quality and not meant for production use. Also, if the ebuild is enabling Radeon Gallium by default (without USE="gallium") then I would consider that a bug on the ebuild. If you mean the nomodeset kernel options I can drop then. I was just hoping they they would help. See ArchLinux nice wikipages. They disabled KMS for the whole distro recently until it stabilizes. Yes, I believe this is an ebuild issue as I do not alter any USE flag for the KMS/gallium stuff. It must come from my profile. # emerge -pv mesa These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] media-libs/mesa-7.7-r1 [7.6.1] USE="gallium* motif -debug -nptl -pic (-selinux) -xcb" VIDEO_CARDS="radeon -intel -mach64 -mga -none -nouveau% -r128 -radeonhd -savage -sis (-sunffb) -svga% -tdfx -via (-s3virge%) (-trident%)" 0 kB # Nevertheless, would you please comment on the "do_ioctls: Failed to get GB pipe count, error number -22" problem? In which version of what package should be the fix. Any clues when was that problem introduced, if it did not exist since e.g. KMS support started to accumulate in that package. Is that really in mesa? So "USE=-gallium emerge mesa" should work for me? Does it have to do with the modeset kernel options at all? Thanks. The error is in Mesa, in src/gallium/winsys/drm/radeon/core/radeon_drm.c, and it means that either your video card isn't a Radeon, or that you don't have KMS enabled. This is not a bug. I explicitly did not write DRI1/UMS/legacy support into the Radeon Gallium code. You must be using KMS and a DRI2-capable Xserver. To resolve the error, go kick the ebuild and/or profile maintainers, and notify them that there is no good reason to enable Gallium yet, since no Gallium drivers are production-quality at this time. Also, the version of the Radeon Gallium drivers in Mesa 7.7 is not very stable; even if the USE flag remains on, I would highly encourage removing --enable-gallium-radeon from the configure line for that version of the ebuild. Thanks for clarifications. I do see some DRI2 messages in the Xorg.log and do not think I asked for that. The chip is from 2001 or so, probably DRI1 only. Maintainers are now CCed so they should have received already their copies. Thanks once again. All gallium masked for <=-7.8 |