Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.
Admin message
The migration is almost done, at least the rest should happen in the background. There are still a few technical difference between the old cluster and the new ones, and they are summarized in this issue. Please pay attention to the TL:DR at the end of the comment.
Created attachment 53026
dmesg log of radeon errors
I have an ASRock A75M motherboard with an A8-3850.
Booting a 3.1 kernel (also tried 3.06), my screen goes blank with modesetting enabled. If I disable modesetting, I am able to boot fine but then X won't work because the X11 driver requires modesetting.
Attachment 53026, "dmesg log of radeon errors": examples.desktop
The problem is happening right at boot. With DRM_RADEON_KMS enabled in my kernel config, the screen goes black immediately after exiting the bootloader. The machines is not wedged because <ctrl-alt-delete> still works.
If recompile with DRM_RADEON_KMS=n, the screen goes black (for longer than I'm used to) but then I see the kernel printks and then a login prompt. When I try to run X with xf86-video-ati I get an error message telling me that SUMO requires KMS. So I'm currently working around by running with the VESA X drivers.
This is a brand new machine which I just brought up yesterday. Windows seems to work fine so I don't think its a hardware issue.
The motherboard comes with a VGA and an HDMI connector. I'm currently using the VGA connector.
I probably should have assigned this to Product:DRI instead Product:xorg since the problem I'm seeing is in the kernel driver and not in the xorg driver.
The DP to VGA bridge chips on a llano APUs are problematic in a lot of cases. You might try a newer kernel or use a digital port (HDMI, DP, DVI) in the meantime.
Seeing this here on an Acer Aspire am3470g-uw10p with Radeon HD 6530D. The vga output dies as soon as radeon with KMS is loaded. In process of acquiring HDMI cable to test with HDMI output.
I have tried with 3.3.1 and 3.3.2 and same problem. Using xorg 1.12.1, xf86-video-ati 6.14.4, ati-dri/mesa 8.0.2 on brand new Arch Linux. Also tried Ubuntu 11.10 Live CD and same results.
Adding vga=775 radeon.modeset=0 to kernel boot line gives me a usable console interface and Xorg will actually start that way, but Xorg display is highly corrupted with bands of bright green and red lines.
Ubuntu 12.04 beta 2 gives same result except that it can successfully start a non-corrupted (but incorrect resolution) Xorg server with the kernel boot line above.
I have an identical snippet in my dmesg as the one posted by Mandeep Baines above.
This bug is marked fixed for Ubuntu in Launchpad ( https://bugs.launchpad.net/ubuntu/+source/linux/+bug/825777 ) but it doesn't work with a fully up-to-date Arch Linux. I haven't had occasion to try the specific Ubuntu kernel build (3.0.0-17.30) cited as resolving the problem (and it seems to be based on one positive result) and I don't seem to see a patch that would be applicable to a mainline kernel.
lspci:
VGA compatible controller: Advanced Micro Devices [AMD] nee ATI BeaverCreek [Radeon HD 6530D]
So it turns out the monitor didn't have an HDMI input.
The only way I could get it working without an HDMI-DVI cable was to downgrade to Xorg 1.11 and install Catalyst. I'm looking forward to the arrival of an HDMI-capable monitor at that station so I can test the open-source driver more thoroughly (get some quite annoying crashes with Catalyst).
Mine is and the patch doesn't correct the problem.
(please ignore the nouveau stuff this is because I want a dual screen so I put a second card in the machine if not for this problem with the VGA I wouldn't have it)
Attachment 60758, "dmesg with proposed patch and drm.debug=4": dmesg-3.3.1_patch.log