On Mon, 2011-06-06 at 01:00 +0200, burek pekaric wrote: > On 06/05/2011 04:49 AM, Ben Hutchings wrote: > > On Sun, 2011-06-05 at 02:46 +0200, burek pekaric wrote: > >> Package: firmware-linux-nonfree > >> Severity: critical > >> Justification: breaks the whole system > >> > >> I'm trying for several days to get my display up and running on fresh install > >> of Debian Squeeze. I was looking to find the original drivers from the OEM here > >> http://support.amd.com/us/gpudownload/Pages/linux64-radeon-prer200.aspx but > >> there are just .rpm packages so I've checked here > >> http://wiki.debian.org/AtiHowTo in order to finally get my screen to display > >> more than a couple of colors, but.. > >> > >> After installing the package firmware-linux-nonfree and reboot, I couldn't even > >> get to the login screen, because display would stuck just before the background > >> image of the login screen was fully displayed (animated/faded out). The display > >> would just freeze and that's it. The mouse would respond for the next couple of > >> seconds and it would also die. From that moment on only physical reset button > >> could be of any help :( > >> > >> Trying to figure out what the problem is (and how to stop loading of gnome to > >> have the simple shell login, so I can remove the package), I've found the key > >> combination Ctrl+Alt+F1 and Ctrl+Alt+Backspace. > > You should boot to single-user mode. In the GRUB menu, this is labelled > > as 'recovery mode'. If you use LILO, add an entry with 'append=single'. > > > >> On next reboot I tried > >> constantly pressing these combinations and finally somehow I've got the console > >> login without GUI, which has let me to login just to show me the message like > >> this one (several seconds after the login): "... [drm:radeon_fence_wait] > >> *ERROR* fence(...) 510ms timeout going to reset GPU" and after that, again it > >> just froze. > > Please provide the complete messages. > > > >> I don't really know what is wrong here, maybe even I've made some wrong steps, > >> but this really influenced me to stop thinking about switching to Linux, > >> although I'd really like to give it a try and not give up this easy, but when > >> the most basic stuff can't work out-of-the-box (like the display driver) it > >> really makes me feel uncomfortable to proceed any further :/ No offence.. > >> > >> Is there any command I can type or anything I can do to give you a more > >> detailed report, so that this issue can be resolved? > > 'lspci -vnn' would be helpful, in additional to the kernel log messages. > > > > Ben. > > > > Hi, > > 1. Thanks for the tip for single user mode. > 2. How to provide complete messages? What command should I type or what > log file should I attach? [...] 1. Boot to single-user mode. If you can, add the kernel parameter 'debug' as well as 'single'. 2. Load the radeon driver with the command 'modprobe radeon'. 3. If you are still able to run commands, then run 'dmesg' (directing output to a file) to get the full kernel log messages. Otherwise, send a photo of the screen, which should include most of the kernel log messages. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
Attachment:
signature.asc
Description: This is a digitally signed message part