Summary: | AIGLX on Juniper LE [AMD Radeon HD 6700 Series] | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Miroslav Suchy <miroslav> | ||||||
Component: | Driver/Radeon | Assignee: | xf86-video-ati maintainers <xorg-driver-ati> | ||||||
Status: | RESOLVED NOTOURBUG | QA Contact: | Xorg Project Team <xorg-team> | ||||||
Severity: | normal | ||||||||
Priority: | medium | ||||||||
Version: | 7.6 (2010.12) | ||||||||
Hardware: | x86-64 (AMD64) | ||||||||
OS: | Linux (All) | ||||||||
Whiteboard: | |||||||||
i915 platform: | i915 features: | ||||||||
Attachments: |
|
Description
Miroslav Suchy
2011-08-17 17:57:26 UTC
Created attachment 50337 [details]
full Xorg.0.log
Please attach the dmesg output. Created attachment 50352 [details]
dmesg output
There's no sign of the radeon kernel module being loaded. Do things work better if you load it manually before starting X for the first time after bootup? KMS is required for hw acceleration on evergreen and newer hardware. Does sid have a new enough kernel for evergreen support? $ uname -a Linux triple 3.0.0-1-amd64 #1 SMP Wed Aug 17 04:08:52 UTC 2011 x86_64 GNU/Linux Is it new enough? ;) after: # modprobe radeon dmesg add: [32362.119178] pci 0000:01:00.0: setting latency timer to 64 [32362.121003] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [32362.121012] [drm] No driver support for vblank timestamp query. [32362.121022] [drm] Initialized radeon 1.33.0 20080528 for 0000:01:00.0 on minor 0 [32407.114007] mtrr: no MTRR for d0000000,10000000 found glxinfo: name of display: :0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.4 server glx extensions: GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_OML_swap_method, GLX_SGI_make_current_read, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_MESA_copy_sub_buffer, GLX_INTEL_swap_event client glx vendor string: Mesa Project and SGI client glx version string: 1.4 client glx extensions: GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap, GLX_INTEL_swap_event GLX version: 1.4 GLX extensions: GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_INTEL_swap_event OpenGL vendor string: Mesa Project OpenGL renderer string: Software Rasterizer OpenGL version string: 2.1 Mesa 7.10.3 OpenGL shading language version string: 1.20 /var/log/Xorg.0.log still: ... [ 32408.743] (--) RandR disabled ... [ 32408.751] (II) AIGLX: Screen 0 is not DRI2 capable [ 32408.751] (II) AIGLX: Screen 0 is not DRI capable [ 32408.753] (II) AIGLX: Loaded and initialized /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so [ 32408.753] (II) GLX: Initialized DRISWRAST GL provider for screen 0 [ 32408.753] (II) RADEON(0): Setting screen physical size to 444 x 277 ... # lsmod |grep radeon # run from kde, so X is running radeon 652538 0 ttm 52979 1 radeon drm_kms_helper 27216 1 radeon i2c_algo_bit 12850 1 radeon power_supply 13475 3 radeon,battery,ac drm 163280 4 radeon,ttm,drm_kms_helper,via i2c_core 23909 25 radeon,drm_kms_helper,i2c_algo_bit,tda10048,tda10086,tda8083,tda10023,tda10021,tda826x,saa7134_dvb,saa7134,v4l2_common,videodev,tveeprom,drm,dvb_usb_dib0700,dib7000p,dib0090,dib7000m,dib0070,dvb_usb,dib8000,dib3000mc,dibx000_common,i2c_piix4 Hmm so it seem that Xorg does not use radeon driver at all... BTW: righn now I'm running without xorg.conf, but recently I've been using xorg.conf and it was the same. Looks like KMS is disabled for some reason, try modprobe radeon modeset=1 indeed, running: modprobe radeon modeset=1 helps. It is working now - from glxinfo: OpenGL renderer string: Gallium 0.4 on AMD JUNIPER So whose responsibility is to load this kernel module - and with this parameter set. Is it Xorg? Or should I file Debian bug? (In reply to comment #9) > So whose responsibility is to load this kernel module - udev. Maybe you have something like a stray /etc/modprobe.d/display_class file which blacklists the radeon module. > and with this parameter set. It's enabled by default. Maybe you have set it to 0 in /etc/modprobe.d/radeon-kms.conf . Anyway, this is most definitely not an upstream driver issue. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.