I have here a Thinkpad T43 with radeon card: root@thinkpad:/root(23)# lspci | grep VGA 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV370 [Mobility Radeon X300] The following xf86-video drivers are installed: root@thinkpad:/root(24)# qlist -Iv xf86-video x11-drivers/xf86-video-ati-7.1.0 x11-drivers/xf86-video-modesetting-0.6.0 x11-drivers/xf86-video-v4l-0.2.0 root@thinkpad:/root(27)# qlist -Iv xorg x11-base/xorg-drivers-1.14 x11-base/xorg-server-1.14.0 x11-base/xorg-x11-7.4-r2 x11-misc/xorg-cf-files-1.0.4 'startx' fails with: ... Initializing built-in extension DRI2 Loading extension GLX (II) [KMS] drm report modesetting isn't supported. (II) [KMS] drm report modesetting isn't supported. (II) [KMS] drm report modesetting isn't supported. Fatal server error: no screens found (EE) In /var/log/Xorg.0.log I find: ... [ 2106.858] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 2106.858] (==) No Layout section. Using the first Screen section. [ 2106.858] (==) No screen section available. Using defaults. [ 2106.858] (**) |-->Screen "Default Screen Section" (0) [ 2106.858] (**) | |-->Monitor "<default monitor>" [ 2106.858] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. ... [ 2106.863] (II) LoadModule: "ati" [ 2106.864] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so ... [ 2106.864] ABI class: X.Org Video Driver, version 14.1 [ 2106.864] (II) LoadModule: "vesa" [ 2106.864] (WW) Warning, couldn't open module vesa [ 2106.864] (II) UnloadModule: "vesa" [ 2106.864] (II) Unloading vesa [ 2106.864] (EE) Failed to load module "vesa" (module does not exist, 0) [ 2106.864] (II) LoadModule: "modesetting" ... [ 2106.865] (EE) Failed to load module "fbdev" (module does not exist, 0) [ 2106.865] (II) RADEON: Driver for ATI Radeon chipsets: ATI Radeon Mobility X600 (M24) 3150 (PCIE), ATI FireMV 2400 (PCI), ATI Radeon Mobility X300 (M24) 3152 (PCIE), ... ATI Radeon X300 (RV370) 5B60 (PCIE), ... VERDE, VERDE, VERDE, VERDE, VERDE, VERDE [ 2106.870] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [ 2106.870] (--) using VT number 7 [ 2106.877] (II) [KMS] drm report modesetting isn't supported. [ 2106.877] (II) [KMS] drm report modesetting isn't supported. [ 2106.877] (II) [KMS] drm report modesetting isn't supported. [ 2106.877] (II) modesetting(2): using drv /dev/dri/card0 [ 2106.877] (EE) Screen 0 deleted because of no matching config section. [ 2106.877] (II) UnloadModule: "radeon" [ 2106.877] (EE) Screen 0 deleted because of no matching config section. [ 2106.877] (II) UnloadModule: "radeon" [ 2106.877] (II) modesetting(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 24/32 [ 2106.877] (==) modesetting(0): Depth 24, (--) framebuffer bpp 32 [ 2106.877] (==) modesetting(0): RGB weight 888 [ 2106.877] (==) modesetting(0): Default visual is TrueColor [ 2106.877] (II) modesetting(0): ShadowFB: preferred NO, enabled NO [ 2106.877] (EE) modesetting(0): KMS doesn't support dumb interface [ 2106.877] (EE) modesetting(0): KMS setup failed [ 2106.877] (II) UnloadModule: "modesetting" [ 2106.877] (II) UnloadModule: "radeon" [ 2106.877] (EE) Screen(s) found, but none have a usable configuration. [ 2106.877] Fatal server error: [ 2106.877] no screens found [ 2106.877] (EE)
Created attachment 342012 [details] emerge --info =xf86-video-ati-7.1.0
Created attachment 342014 [details] /var/log/Xorg.0.log
>=7.0.0 are KMS only, so likely INVALID.
>>=7.0.0 are KMS only, so likely INVALID. If you are the first to tell him that here, likely not INVALID; it needs to be documented more properly in that case. > (II) [KMS] drm report modesetting isn't supported. Why is this just informational and not a warning, error or even a package block?
Dropping support for UMS was explicitly mentioned in the release announcement of 7.0.0. Most Gentoo could do wold be to add a postinst message (and many people don't bother to read them anyway). 7.0.0 was released on 6.11.2012. :roll:
We could add a CONFIG_CHECK for DRM_RADEON_KMS to the ebuild, which will generate a warning. But this will not give fully accurate because kernel parameters can still override the KMS setting in the kernel config. Furthermore, we already tell users to enable KMS in our documentation http://www.gentoo.org/doc/en/xorg-config.xml and besides, mesa has not supported UMS setups since 7.10 or so (it would fallback to software rendering).
DRM_RADEON_KMS is now activated in the current kernel: root@thinkpad:/root(1)# gzip -cd /proc/config.gz | grep RADEON CONFIG_DRM_RADEON=y CONFIG_DRM_RADEON_KMS=y CONFIG_FB_RADEON=y CONFIG_FB_RADEON_I2C=y CONFIG_FB_RADEON_BACKLIGHT=y CONFIG_FB_RADEON_DEBUG=y Nevertheless 'startx' complains that modesetting isn't supported: root@thinkpad:/root(2)# startx xauth: file /root/.serverauth.1062 does not exist X.Org X Server 1.14.0 Release Date: 2013-03-05 X Protocol Version 11, Revision 0 Build Operating System: Linux 3.7.8-gentoo i686 Gentoo Current Operating System: Linux thinkpad 3.8.2-gentoo #2 PREEMPT Fri Mar 15 00:20:41 CET 2013 i686 Kernel command line: real_root=/dev/sda6 dolvm Build Date: 08 March 2013 11:07:57AM Current version of pixman: 0.29.2 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Mon Mar 18 09:57:59 2013 (==) Using system config directory "/usr/share/X11/xorg.conf.d" Initializing built-in extension Generic Event Extension Initializing built-in extension SHAPE Initializing built-in extension MIT-SHM Initializing built-in extension XInputExtension Initializing built-in extension XTEST Initializing built-in extension BIG-REQUESTS Initializing built-in extension SYNC Initializing built-in extension XKEYBOARD Initializing built-in extension XC-MISC Initializing built-in extension XINERAMA Initializing built-in extension XFIXES Initializing built-in extension RENDER Initializing built-in extension RANDR Initializing built-in extension COMPOSITE Initializing built-in extension DAMAGE Initializing built-in extension MIT-SCREEN-SAVER Initializing built-in extension DOUBLE-BUFFER Initializing built-in extension RECORD Initializing built-in extension DPMS Initializing built-in extension X-Resource Initializing built-in extension XVideo Initializing built-in extension XVideo-MotionCompensation Initializing built-in extension XFree86-VidModeExtension Initializing built-in extension XFree86-DGA Initializing built-in extension XFree86-DRI Initializing built-in extension DRI2 Loading extension GLX (II) [KMS] drm report modesetting isn't supported. vesa: Ignoring device with a bound kernel driver Fatal server error: no screens found (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. (EE) Server terminated with error (1). Closing log file. xinit: giving up xinit: unable to connect to X server: Connection refused xinit: server error root@thinkpad:/root(3)# grep -U2 EE /var/log/Xorg.0.log [292618.876] X Protocol Version 11, Revision 0 [292618.876] Build Operating System: Linux 3.7.8-gentoo i686 Gentoo [292618.876] Current Operating System: Linux thinkpad 3.8.2-gentoo #2 PREEMPT Fri Mar 15 00:20:41 CET 2013 i686 [292618.876] Kernel command line: real_root=/dev/sda6 dolvm [292618.876] Build Date: 08 March 2013 11:07:57AM -- [292618.877] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [292618.877] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Mar 18 09:57:59 2013 [292618.938] (==) Using system config directory "/usr/share/X11/xorg.conf.d" -- [292619.162] Initializing built-in extension COMPOSITE [292619.162] Initializing built-in extension DAMAGE [292619.162] Initializing built-in extension MIT-SCREEN-SAVER [292619.162] Initializing built-in extension DOUBLE-BUFFER [292619.162] Initializing built-in extension RECORD -- [292619.242] (II) UnloadModule: "fbdev" [292619.242] (II) Unloading fbdev [292619.242] (EE) Failed to load module "fbdev" (module does not exist, 0) [292619.242] (II) RADEON: Driver for ATI Radeon chipsets: ATI Radeon Mobility X600 (M24) 3150 (PCIE), ATI FireMV 2400 (PCI), -- [292619.269] vesa: Ignoring device with a bound kernel driver [292619.269] (WW) Falling back to old probe method for vesa [292619.269] (EE) open /dev/dri/card0: No such file or directory [292619.269] (WW) Falling back to old probe method for modesetting [292619.269] (EE) open /dev/dri/card0: No such file or directory [292619.270] (EE) Screen 0 deleted because of no matching config section. [292619.270] (II) UnloadModule: "radeon" [292619.270] (EE) Screen 0 deleted because of no matching config section. [292619.270] (II) UnloadModule: "vesa" [292619.270] (EE) Screen 0 deleted because of no matching config section. [292619.270] (II) UnloadModule: "modesetting" [292619.270] (EE) Device(s) detected, but none match those in the config file. [292619.270] Fatal server error: [292619.270] no screens found [292619.270] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [292619.270] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [292619.270] (EE) [292619.288] Server terminated with error (1). Closing log file.
A little guess: if CONFIG_DRM_RADEON=m, firmware must be somewhere it can be found; if CONFIG_DRM_RADEON=y, firmware must in in the kernel;
Please attach your dmesg and kernel config. For dmesg it would be good to have CONFIG_PRINTK_TIME enabled. (In reply to comment #8) 1002:5460 is RV370 which needs no extra firmware.
Created attachment 342518 [details] /proc/config.gz
Created attachment 342520 [details] /var/log/dmesg
Created attachment 342522 [details] output of 'dmesg'
I don't have any /dev/dri files: root@thinkpad:/root(11)# ll /dev/dri /bin/ls: cannot access /dev/dri: No such file or directory
Created attachment 342524 [details] /var/log/Xorg.0.log with 3.8.3-gentoo-r1
That dmesg is incomplete, it does not contain the radeon driver initialization. You can use log_buf_len=... kernel parameter to increase the size of the printk buffer.
(In reply to comment #9) > (In reply to comment #8) > 1002:5460 is RV370 which needs no extra firmware. ls /lib/firmware/radeon R100_cp.bin R600_pfp.bin RV610_pfp.bin RV635_pfp.bin RV730_pfp.bin R200_cp.bin RS600_cp.bin RV620_me.bin RV670_me.bin RV770_me.bin R300_cp.bin RS690_cp.bin RV620_pfp.bin RV670_pfp.bin RV770_pfp.bin R420_cp.bin RS780_me.bin RV630_me.bin RV710_me.bin R520_cp.bin RS780_pfp.bin RV630_pfp.bin RV710_pfp.bin R600_me.bin RV610_me.bin RV635_me.bin RV730_me.bin ...you were saying ?
Created attachment 342608 [details] The output of 'dmesg' with log_buf_len=65536
(In reply to comment #16) > ...you were saying ? extra firmware as in "needs to be passed to the kernel in CONFIG_EXTRA_FIRMWARE" which is not the case with r300 firmware. (In reply to comment #17) > [ 0.915453] radeonfb_pci_register BEGIN This is bad, radeonfb must be disabled. It should never have been enabled. Set CONFIG_FB_RADEON=n in your kernel.
A configuration check for radeon KMS and against radeonfb was now added to the ebuild.
(In reply to comment #18) > (In reply to comment #16) > > ...you were saying ? > extra firmware as in "needs to be passed to the kernel in > CONFIG_EXTRA_FIRMWARE" which is not the case with r300 firmware. > I might be missing something but how is R300_cp.bin different to i.e. R600_me.bin ? I do recall quite a few forum posts where adding the firmware of the more recent radeons (even once it was added to the vanilla sources) was needed if radeon driver was builtin. Also, in this particular case CONFIG_EXTRA_FIRMWARE="" is paired with CONFIG_PREVENT_FIRMWARE_BUILD=y which (AFAIU) would prevent firmware from being installed by 'make modules_install'.
Thanks Chí-Thanh Christopher Nguyễn, after setting CONFIG_FB_RADEON=n startx, gdm and gnome3 (at least in faulback mode) works now.
If there are still problems with 3D acceleration, you can open a new bug (with output of "LIBGL_DEBUG=verbose glxinfo" attached).
