Bug#528684: (no subject)
On Sun, 07 Mar 2010 10:14:17 +0100, Brice Goglin brice.gog...@ens-lyon.org wrote: You probably should enable KMS in your kernel. Tried this now by passing radeon.modeset=1 to the kernel. This resulted in the following failure in the X.org log: (EE) RADEON(0): [dri] RADEONDRIGetVersion failed because of a version mismatch. [dri] This chipset requires a kernel module version of 1.17.0, [dri] but the kernel reports a version of 2.0.0.[dri] If using legacy modesetting, upgrade your kernel. [dri] If using kernel modesetting, make sure your module is [dri] loaded prior to starting X, and that this driver was built [dri] with support for KMS. [dri] Disabling DRI. ...and subsequently a black screen (that wouldn't go away even when switching consoles). Relevant part of the kernel log: Mar 7 13:31:22 sandwich kernel: [ 23.013466] [drm] Initialized drm 1.1.0 20060810 Mar 7 13:31:22 sandwich kernel: [ 23.066580] [drm] radeon kernel modesetting enabled. Mar 7 13:31:22 sandwich kernel: [ 23.066748] radeon :02:00.0: setting latency timer to 64 Mar 7 13:31:22 sandwich kernel: [ 23.073756] [drm] radeon: Initializing kernel modesetting. Mar 7 13:31:22 sandwich kernel: [ 23.073822] [drm] register mmio base: 0xCFEF Mar 7 13:31:22 sandwich kernel: [ 23.073830] [drm] register mmio size: 65536 Mar 7 13:31:22 sandwich kernel: [ 23.074097] ATOM BIOS: Acer_JV50_PU_M92M2_XT_DDR2 Mar 7 13:31:22 sandwich kernel: [ 23.074113] [drm] Clocks initialized ! Mar 7 13:31:22 sandwich kernel: [ 23.074793] [drm] Detected VRAM RAM=256M, BAR=256M Mar 7 13:31:22 sandwich kernel: [ 23.074809] [drm] RAM width 64bits DDR Mar 7 13:31:22 sandwich kernel: [ 23.077253] [TTM] Zone kernel: Available graphics memory: 436872 kiB. Mar 7 13:31:22 sandwich kernel: [ 23.077269] [TTM] Zone highmem: Available graphics memory: 1622028 kiB. Mar 7 13:31:22 sandwich kernel: [ 23.077321] [drm] radeon: 256M of VRAM memory ready Mar 7 13:31:22 sandwich kernel: [ 23.077329] [drm] radeon: 512M of GTT memory ready. Mar 7 13:31:22 sandwich kernel: [ 23.077493] [drm] Loading RV710 CP Microcode Mar 7 13:31:22 sandwich kernel: [ 23.077505] platform radeon_cp.0: firmware: requesting radeon/RV710_pfp.bin Mar 7 13:31:22 sandwich kernel: [ 23.121711] platform radeon_cp.0: firmware: requesting radeon/RV710_me.bin Mar 7 13:31:22 sandwich kernel: [ 23.137889] [drm] GART: num cpu pages 131072, num gpu pages 131072 Mar 7 13:31:22 sandwich kernel: [ 23.172085] [drm] ring test succeeded in 1 usecs Mar 7 13:31:22 sandwich kernel: [ 23.172692] [drm] radeon: ib pool ready. Mar 7 13:31:22 sandwich kernel: [ 23.172921] [drm] ib test succeeded in 0 usecs Mar 7 13:31:22 sandwich kernel: [ 23.177821] [drm] Radeon Display Connectors Mar 7 13:31:22 sandwich kernel: [ 23.177834] [drm] Connector 0: Mar 7 13:31:22 sandwich kernel: [ 23.177841] [drm] LVDS Mar 7 13:31:22 sandwich kernel: [ 23.177853] [drm] DDC: 0x7f68 0x7f68 0x7f6c 0x7f6c 0x7f70 0x7f70 0x7f74 0x7f74 Mar 7 13:31:22 sandwich kernel: [ 23.177861] [drm] Encoders: Mar 7 13:31:22 sandwich kernel: [ 23.177867] [drm] LCD1: INTERNAL_UNIPHY2 Mar 7 13:31:22 sandwich kernel: [ 23.177874] [drm] Connector 1: Mar 7 13:31:22 sandwich kernel: [ 23.177880] [drm] VGA Mar 7 13:31:22 sandwich kernel: [ 23.177890] [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c Mar 7 13:31:22 sandwich kernel: [ 23.177897] [drm] Encoders: Mar 7 13:31:22 sandwich kernel: [ 23.177903] [drm] CRT1: INTERNAL_KLDSCP_DAC1 Mar 7 13:31:22 sandwich kernel: [ 23.177910] [drm] Connector 2: Mar 7 13:31:22 sandwich kernel: [ 23.177916] [drm] HDMI-A Mar 7 13:31:22 sandwich kernel: [ 23.177926] [drm] DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c Mar 7 13:31:22 sandwich kernel: [ 23.177933] [drm] Encoders: Mar 7 13:31:22 sandwich kernel: [ 23.177940] [drm] DFP1: INTERNAL_UNIPHY Mar 7 13:31:23 sandwich kernel: [ 24.54] wifi: no IPv6 routers present Mar 7 13:31:23 sandwich kernel: [ 24.247673] [drm] fb mappable at 0xD0141000 Mar 7 13:31:23 sandwich kernel: [ 24.247677] [drm] vram apper at 0xD000 Mar 7 13:31:23 sandwich kernel: [ 24.247680] [drm] size 4325376 Mar 7 13:31:23 sandwich kernel: [ 24.247682] [drm] fb depth is 24 Mar 7 13:31:23 sandwich kernel: [ 24.247684] [drm]pitch is 5632 Mar 7 13:31:23 sandwich kernel: [ 24.248973] Console: switching to colour frame buffer device 170x48 Mar 7 13:31:23 sandwich kernel: [ 24.248993] fb0: radeondrmfb frame buffer device Mar 7 13:31:23 sandwich kernel: [ 24.248996] registered panic notifier Mar 7 13:31:23 sandwich kernel: [ 24.249007] [drm] Initialized radeon 2.0.0 20080528 for :02:00.0 on minor 0 Complete X.org log: X.Org X Server 1.7.5 Release Date: 2010-02-16 X Protocol Version 11, Revision 0 Build Operating System:
Bug#528684: (no subject)
On Sun, 2010-03-07 at 13:46 +0100, Alexey Feldgendler wrote: On Sun, 07 Mar 2010 10:14:17 +0100, Brice Goglin brice.gog...@ens-lyon.org wrote: You probably should enable KMS in your kernel. Tried this now by passing radeon.modeset=1 to the kernel. This resulted in the following failure in the X.org log: (EE) RADEON(0): [dri] RADEONDRIGetVersion failed because of a version mismatch. [dri] This chipset requires a kernel module version of 1.17.0, [dri] but the kernel reports a version of 2.0.0.[dri] If using legacy modesetting, upgrade your kernel. [dri] If using kernel modesetting, make sure your module is [dri] loaded prior to starting X, and that this driver was built [dri] with support for KMS. [dri] Disabling DRI. Looks like the driver wasn't built with KMS support. Maybe the build dependencies are too lax. -- Earthling Michel Dänzer |http://www.vmware.com Libre software enthusiast | Debian, X and DRI developer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#528684: (no subject)
On Sun, 07 Mar 2010 15:50:24 +0100, Michel Dänzer daen...@debian.org wrote: Looks like the driver wasn't built with KMS support. Maybe the build dependencies are too lax. Any hint as to what I should rebuild and with what settings? -- Alexey Feldgendler ale...@feldgendler.ru [ICQ: 115226275] http://feldgendler.livejournal.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#528684: (no subject)
Michel Dänzer wrote: On Sun, 2010-03-07 at 13:46 +0100, Alexey Feldgendler wrote: On Sun, 07 Mar 2010 10:14:17 +0100, Brice Goglin brice.gog...@ens-lyon.org wrote: You probably should enable KMS in your kernel. Tried this now by passing radeon.modeset=1 to the kernel. This resulted in the following failure in the X.org log: (EE) RADEON(0): [dri] RADEONDRIGetVersion failed because of a version mismatch. [dri] This chipset requires a kernel module version of 1.17.0, [dri] but the kernel reports a version of 2.0.0.[dri] If using legacy modesetting, upgrade your kernel. [dri] If using kernel modesetting, make sure your module is [dri] loaded prior to starting X, and that this driver was built [dri] with support for KMS. [dri] Disabling DRI. Looks like the driver wasn't built with KMS support. Maybe the build dependencies are too lax. He's using i386, that's what I uploaded. I see Kernel modesetting: yes at the end of my build log, and I get KMS on my r300 machines. Strange... Brice -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#528684: (no subject)
On Sun, 07 Mar 2010 16:13:32 +0100, Brice Goglin brice.gog...@ens-lyon.org wrote: Looks like the driver wasn't built with KMS support. Maybe the build dependencies are too lax. He's using i386, that's what I uploaded. I see Kernel modesetting: yes at the end of my build log, and I get KMS on my r300 machines. Strange... I could try to build it myself to help investigate the issue. What package are we talking about building? Should I get the sources right from the version control? FWIW, it's an R700 (Mobility Radeon HD 4500 Series) built into an Acer Aspire 5536G laptop. -- Alexey Feldgendler ale...@feldgendler.ru [ICQ: 115226275] http://feldgendler.livejournal.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#528684: (no subject)
On Sun, 2010-03-07 at 16:13 +0100, Brice Goglin wrote: Michel Dänzer wrote: On Sun, 2010-03-07 at 13:46 +0100, Alexey Feldgendler wrote: On Sun, 07 Mar 2010 10:14:17 +0100, Brice Goglin brice.gog...@ens-lyon.org wrote: You probably should enable KMS in your kernel. Tried this now by passing radeon.modeset=1 to the kernel. This resulted in the following failure in the X.org log: (EE) RADEON(0): [dri] RADEONDRIGetVersion failed because of a version mismatch. [dri] This chipset requires a kernel module version of 1.17.0, [dri] but the kernel reports a version of 2.0.0.[dri] If using legacy modesetting, upgrade your kernel. [dri] If using kernel modesetting, make sure your module is [dri] loaded prior to starting X, and that this driver was built [dri] with support for KMS. [dri] Disabling DRI. Looks like the driver wasn't built with KMS support. Maybe the build dependencies are too lax. He's using i386, that's what I uploaded. I see Kernel modesetting: yes at the end of my build log, and I get KMS on my r300 machines. Strange... Hmm, the line (II) [KMS] drm report modesetting isn't supported. in the X log file indicates that drmCheckModesettingSupported() fails, i.e. can't find some files in /sys . Alexey, what does find /sys/bus/pci/devices/*/ -name \*controlD\* say for you? Note that the asterisk and slash at the end of the second term are critical, otherwise there will be no results. -- Earthling Michel Dänzer |http://www.vmware.com Libre software enthusiast | Debian, X and DRI developer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#528684: (no subject)
On Sun, 07 Mar 2010 16:33:53 +0100, Michel Dänzer daen...@debian.org wrote: Hmm, the line (II) [KMS] drm report modesetting isn't supported. in the X log file indicates that drmCheckModesettingSupported() fails, i.e. can't find some files in /sys . Alexey, what does find /sys/bus/pci/devices/*/ -name \*controlD\* say for you? Note that the asterisk and slash at the end of the second term are critical, otherwise there will be no results. You guessed right! It wasn't finding anything until I loaded the radeon module manually, after which it found /sys/bus/pci/devices/:00:02.0/:02:00.0/drm/controlD64 /sys/bus/pci/devices/:02:00.0/drm/controlD64 ...and KMS in general started working. With KMS enabled, I've got DRI2, and the original issue of this bug disappeared. I've added radeon to /etc/modules for now, but I guess I should file a bug for udev, what do you think? Now, when I enabled KMS, I got a significant performance degradation compared to no KMS and no DRI2, but that's a different issue, I'm filing a new bug about it. Thanks for your help on this one! -- Alexey Feldgendler ale...@feldgendler.ru [ICQ: 115226275] http://feldgendler.livejournal.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#528684: (no subject)
On Sun, 07 Mar 2010 17:30:55 +0100, Brice Goglin brice.gog...@ens-lyon.org wrote: No need, it should be fixed in the next kernel upload. Are you sure? I'm using the newest linux-image from experimental (2.6.33-1~experimental.2), do you mean the next upload to experimental? -- Alexey Feldgendler ale...@feldgendler.ru [ICQ: 115226275] http://feldgendler.livejournal.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#528684: (no subject)
Alexey Feldgendler wrote: On Sun, 07 Mar 2010 16:33:53 +0100, Michel Dänzer daen...@debian.org wrote: Hmm, the line (II) [KMS] drm report modesetting isn't supported. in the X log file indicates that drmCheckModesettingSupported() fails, i.e. can't find some files in /sys . Alexey, what does find /sys/bus/pci/devices/*/ -name \*controlD\* say for you? Note that the asterisk and slash at the end of the second term are critical, otherwise there will be no results. You guessed right! It wasn't finding anything until I loaded the radeon module manually, after which it found /sys/bus/pci/devices/:00:02.0/:02:00.0/drm/controlD64 /sys/bus/pci/devices/:02:00.0/drm/controlD64 ...and KMS in general started working. With KMS enabled, I've got DRI2, and the original issue of this bug disappeared. I've added radeon to /etc/modules for now, but I guess I should file a bug for udev, what do you think? No need, it should be fixed in the next kernel upload. Brice -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#528684: (no subject)
Anyway, this bug should probably be closed. I've added a found-in-version to this bug and now I'm not sure how to take it back. See bug #572911 for the performance issue I'm experiencing. -- Alexey Feldgendler ale...@feldgendler.ru [ICQ: 115226275] http://feldgendler.livejournal.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#528684: (no subject)
This problem appears for me as described in the original report. Upgrading to experimental version 1:6.12.191-1 doesn't help. (The rest of X.org is from testing.) X.org configuration (the relevant bits): Section ServerFlags Option DRI2 on EndSection Section Device Identifier Graphics Device Driver radeon Option Monitor-LVDS LVDS monitor Option Monitor-VGA-0 VGA-0 monitor Option Monitor-HDMI-0 HDMI-0 monitor BusID PCI:2:0:0 EndSection X.org log follows. Note the “(II) AIGLX: Screen 0 is not DRI2 capable” message. X.Org X Server 1.7.5 Release Date: 2010-02-16 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32-trunk-686 i686 Debian Current Operating System: Linux sandwich 2.6.32-trunk-686 #1 SMP Sun Jan 10 06:32:16 UTC 2010 i686 Kernel command line: BOOT_IMAGE=//vmlinuz-2.6.32-trunk-686 root=UUID=1c1ecd24-ae38-4fb3-9020-78b2405e559e ro i8042.noloop=1 quiet Build Date: 16 February 2010 08:37:23AM xorg-server 2:1.7.5-1 (bgog...@debian.org) Current version of pixman: 0.16.4 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: Sun Mar 7 03:12:17 2010 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout Default Layout (**) |--Screen Virtual Screen (0) (**) | |--Monitor default monitor (**) | |--Device Graphics Device (==) No monitor specified for screen Virtual Screen. Using a default monitor configuration. (**) Option BlankTime 0 (**) Option StandbyTime 0 (**) Option SuspendTime 0 (**) Option OffTime 0 (**) Option DRI2 on (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, built-ins (==) ModulePath set to /usr/lib/xorg/modules (II) Cannot locate a core pointer device. (II) Cannot locate a core keyboard device. (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. (II) Loader magic: 0x81e7020 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 6.0 X.Org XInput driver : 7.0 X.Org Server Extension : 2.0 (++) using VT number 7 (--) PCI:*(0:2:0:0) 1002:9553:1025:0206 ATI Technologies Inc M92 [Mobility Radeon HD 4500 Series] rev 0, Mem @ 0xd000/268435456, 0xcfef/65536, I/O @ 0x9000/256, BIOS @ 0x/131072 (II) Open ACPI successful (/var/run/acpid.socket) (II) LoadModule: extmod (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so (II) Module extmod: vendor=X.Org Foundation compiled for 1.7.5, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension SELinux (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: dbe (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so (II) Module dbe: vendor=X.Org Foundation compiled for 1.7.5, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: glx (II) Loading /usr/lib/xorg/modules/extensions/libglx.so (II) Module glx: vendor=X.Org Foundation compiled for 1.7.5, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (==) AIGLX enabled (II) Loading extension GLX (II) LoadModule: record (II) Loading /usr/lib/xorg/modules/extensions/librecord.so (II) Module record: vendor=X.Org Foundation compiled for 1.7.5, module version = 1.13.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension RECORD (II) LoadModule: dri (II) Loading /usr/lib/xorg/modules/extensions/libdri.so (II) Module dri: vendor=X.Org Foundation compiled for 1.7.5, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (II) Loading extension XFree86-DRI (II) LoadModule: dri2 (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so (II) Module dri2: vendor=X.Org
