On Wednesday 24 December 2008, Dave Airlie wrote: [...] >> I found the one in xf86-video-radeonhd-1.2.4, and copied it to the src >> tree beside the other .h files, and it built, and I've installed it and >> running it, although not much is changed. glxgears is still moping along >> at about 875 fps, and glxinfo says no drm?dri. >> >> But now this exposes a new problem I don't recall in these exact words, >> when I do a startx, it cannot load the kernel radeon module >> (this from the Xorg.0.log)
Any comment on this? >> (WW) RADEON(0): Direct rendering for RN50/RS600/R600 forced on -- This is >> NOT officially supported at the hardware level and may cause instability >> or lockups >> drmOpenDevice: node name is /dev/dri/card0 >> drmOpenDevice: open result is -1, (No such device) >> drmOpenDevice: open result is -1, (No such device) >> drmOpenDevice: Open failed >> [drm] failed to load kernel module "radeon" >> (EE) RADEON(0): [dri] RADEONDRIGetVersion failed to open the DRM >> [dri] Disabling DRI. >> >> So, just for giggles: >> >> [r...@coyote ~]# modprobe radeon >> WARNING: Error inserting drm >> (/lib/modules/2.6.28-rc9/kernel/drivers/gpu/drm/drm.ko): Invalid argument >> FATAL: Error inserting radeon >> (/lib/modules/2.6.28-rc9/kernel/drivers/gpu/drm/radeon/radeon.ko): Invalid >> argument >> >> I can also recall not too far back in the 2.6.28-rc cycle, seeing dmesg >> reporting that the firmware for the card had been loaded from >> the /lib/firmware/radeon directory, but that appears to be on the missing >> list too for an rcN or 2. The firmware is there from previous kernel >> builds, but is no longer being installed by this line of my "./makeit" >> script: >> >> make firmware_install && \ >> >> Which tells me something has changed in the Makefiles or .config's. >> >> How important is this firmware for the health & well being of an >> HD2400-Pro (rv610) card? >> >> From the .config that built this kernel: >> >> [r...@coyote linux-2.6.28-rc9]# grep FIRMWARE .config >> # CONFIG_PREVENT_FIRMWARE_BUILD is not set >> # CONFIG_FIRMWARE_IN_KERNEL is not set >> CONFIG_EXTRA_FIRMWARE="radeon/R100_cp.bin.ihex radeon/R200_cp.bin.ihex >> radeon/R300_cp.bin.ihex radeon/R420_cp.bin.ihex radeon/R520_cp.bin.ihex >> radeon/RS600_cp.bin.ihex radeon/RS690_cp.bin.ihex" >> CONFIG_EXTRA_FIRMWARE_DIR="firmware" >> # CONFIG_DVB_AV7110_FIRMWARE is not set >> # CONFIG_FIRMWARE_EDID is not set >> CONFIG_FIRMWARE_MEMMAP=y >> >> And: >> >> [r...@coyote linux-2.6.28-rc9]# grep DRM .config >> CONFIG_DRM=m >> # CONFIG_DRM_TDFX is not set >> # CONFIG_DRM_R128 is not set >> CONFIG_DRM_RADEON=m >> # CONFIG_DRM_MGA is not set >> # CONFIG_DRM_SIS is not set >> # CONFIG_DRM_VIA is not set >> # CONFIG_DRM_SAVAGE is not set >> >> Also: >> >> [r...@coyote linux-2.6.28-rc9]# grep RADEON .config >> CONFIG_DRM_RADEON=m >> CONFIG_FB_RADEON=m >> CONFIG_FB_RADEON_I2C=y >> CONFIG_FB_RADEON_BACKLIGHT=y >> CONFIG_FB_RADEON_DEBUG=y >> >> >> I've been poking around in my logs, but they apparently don't go back far >> enough to have the radeon firmware loading report else I'd quote that and >> when it worked for what kernel version. >> >> Can you see anything obviously wrong? Or suggest a fix? >> Thanks Dave & Merry Christmas. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Sysadmins unavailable because they are in a meeting talking about why they are unavailable so much. _______________________________________________ xorg mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/xorg
