On Sun, Mar 11, 2012 at 07:37:51PM +0400, Boris Pek wrote:
> Hi,
>
> > > startx command launched LXDE (I have both KDE and LXDE) and it
> > > worked normally.
> >
> > Thanks --- this is a very useful detail. So probably non-accelarated
> > rendering works fine, and it is something in 3d codepath
Hi,
> > startx command launched LXDE (I have both KDE and LXDE) and it
> > worked normally.
>
> Thanks --- this is a very useful detail. So probably non-accelarated
> rendering works fine, and it is something in 3d codepaths that makes it
> freeze.
Ok. I saw interesting instructions in bug repo
severity 663379 important
merge 663269 663379
quit
Boris Pek wrote:
>startx command launched LXDE (I have both KDE and LXDE) and it
> worked normally.
Thanks --- this is a very useful detail. So probably non-accelarated
rendering works fine, and it is something in 3d codepaths t
> Which is the newest working version you tested?
Sorry I missed the word `working'. Unfortunately, I don't remember this.
It was the latest version of linux-image-3.2.0-1-rt-686-pae package just
before it was deleted from Sid.
Regards,
Boris
Jonathan Nieder wrote:
> Does a text-only (e.g., "single user mode") boot work ok? If so,
> does running
>
> dmesg >dmesg.before; startx; dmesg >dmesg.after
Erm, that idea was insane. I guess the simplest way to get diagnostic
info from after starting X would be to look in /var/log/dmesg
Hi Boris,
Boris Pek wrote:
> During launching KDM system freezes and don't react of anything.
> Only reset solves the problem.
Can you toggle capslock, use ctrl-alt-delete or the magic sysrq key,
or ssh into the machine in this state?
Does a text-only (e.g., "single user mode") boot work ok? I
6 matches
Mail list logo
