On Sat, 2011-06-25 at 15:20 +0200, Francesco Muzio wrote: > I have tried to set CONFIG_DRM_RADEON=y (I think you're referring to > this being also mentioned CONFIG_FIRMWARE_IN_KERNEL) configured > CONFIG_EXTRA_FIRMWARE and the path correctly but the kernel hangs again > > Hence I'm back to the previous configuration with CONFIG_DRM_RADEON=m > for do other test: > > I have also tried to set CONFIG_AGP=y and CONFIG_AGP_AMD64=y without success > > But if I set CONFIG_AGP=y, CONFIG_AGP_AMD64=y and CONFIG_AGP_ATI=y the > kernel boot and seems to work all. I managed to boot 3 times of 3 with > success. > > It is strange because: > - radeon HD6670 is a PCI-Express card > - I have also a radeon chip integrated on the motherboard (ASUS M4A89GTD > PRO) but is disabled from AMI BIOS and obviously a "lspci | grep VGA" > does not find it The AGP GART is still important for PCI Express cards, though the GPU drivers should work without it (with lower performance). The Debian official kernel packages all have the GART drivers built-in. > No, I was wrong, freeze on KMS also with CONFIG_AGP=y, > CONFIG_AGP_AMD64=y and CONFIG_AGP_ATI=y Please report this upstream at <https://bugs.freedesktop.org> under product 'DRI', component 'DRM/Radeon'. Include the kernel log that you sent to this bug. Let us know the new bug number or URL, so we can track it. Ben. -- Ben Hutchings It is impossible to make anything foolproof because fools are so ingenious.
Attachment:
signature.asc
Description: This is a digitally signed message part