I'm using the current Debian Wheezy. With the default 3.2.x kernel, and also with vanilla 3.5.3 I get a hard crash as soon as the drm module is loaded. Disabling the drm module makes it boot normally. I'm using the open source driver 6.14.4-5 and Xorg 7.7+1. Hardware is a HP DM1 4100ed laptop with a AMD HD 6320 GPU on an AMD Fusion E-450. If you need any more info then I'm willing to provide it. But I wouldn't know how to get any more info out of the machine after the crash :).
Created attachment 79611 [details] lspci -vv
On a sidenote, when Xorg runs (without drm/radeon) and I switch to a virtual console, nothing happens really. Switching back to the graphical console makes the screen split, the left half shows up right, and the right half shows up left. Restarting Xorg doesn't help, it just makes Xorg have an unusable black screen. Rebooting over the network still works though.
Make sure you have the firmware packages installed. IIRC debian does not install the by default. Can you get the dmesg output by loading the radeon module after the system is booted?
If you don't have necessary firmware installed the kernel firmware requester will wait for several minutes before timing out.
Also possibly related: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=d8636a2717bb3da2a7ce2154bf08de90bb8c87b0 or: http://lists.freedesktop.org/archives/dri-devel/2012-September/027545.html
Ah, thanks. I should have thought of that, firmware. With loading the firmware it now boots up fine. I will attach some dmesg parts with and without firmware.
Created attachment 79711 [details] dmesg with loading drm/radeon without firmware Dmesg part with loading drm/radeon without having firmware installed and loaded.
Created attachment 79721 [details] dmesg with loading drm/radeon with the firmware dmesg part when loading drm/radeon during boot when firmware is installed and gets loaded.
I thought about it for a while. For me personally the bug is fixed. But it should be that if the driver doesn't find the software, then it should degrade gracefully. Maybe not load the driver, or just do nothing.
(In reply to comment #9) > I thought about it for a while. For me personally the bug is fixed. But it > should be that if the driver doesn't find the software, then it should > degrade > gracefully. Maybe not load the driver, or just do nothing. It's not the driver, it's the kernel fw loader.
The firmware loading behaviour for the ke