Hi, 2010/12/27 Cyril Brulebois <k...@debian.org>
> Raffaele Morelli <raffaele.more...@gmail.com> (27/12/2010): > > Well yes I tried to istall amd/ati drivers for my video card cause I > > had to fix a problem with the lock screen. Actually activating a new > > session while another user is logged results in a weird message > > about drm modules. Here it is > > > > [drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB ! > > > [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(6). > > > [drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB ! > > > [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(7). > > > [drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB ! > > What did you actually do WRT those drivers? > Really I didn't know I was using them and either wanted to > > Anyway, you really should be using a packaged kernel instead of your > hand-built kernel. Lots of fixes get backported from stable releases, > and across distributions, which picked 2.6.32 as a basis. > I am actually (while we are writing each other) using a debian stock one. I use my hand built kernel because I need it for RT audio tasks (for audio production). > > If you notice a drm issue with the latest 2.6.32 kernel available in > Debian, report a bug against the kernel (source package is linux-2.6). > > KiBi. > regards -r
