On Sam, 2012-03-17 at 21:45 +0400, Goga wrote: > > [ 65.686] (++) using VT number 7 > > [ 65.711] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so
A more detailed description of the problem than just the subject line would have been nice, but my guess would be that the X server dies, and the log file ends abruptly at this point? Check the X server stderr output, e.g. by starting it manually from a remote shell. Usually this is due to an unresolved symbol, e.g. due to stale libraries getting picked up from /usr/local/lib or so. > [ 2501.510] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so > [ 2501.510] vesa: Ignoring device with a bound kernel driver > [ 2501.510] (WW) Falling back to old probe method for vesa > [ 2501.510] (II) UnloadModule: "vesa" > [ 2501.510] (II) Unloading vesa > [ 2501.510] (EE) Screen(s) found, but none have a usable configuration. > [ 2501.510] > Fatal server error: > [ 2501.510] no screens found This is expected, the vesa driver can't work with an active KMS kernel driver. > After aptitude safe-upgrade aptitude full-upgrade I can't start X correctly. Which packages were upgraded? -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Debian, X and DRI developer -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1332149879.4597.517.camel@thor.local
