In my case I had uninstalled xserver-xorg after the recent update,
possibly because the description:
"This package depends on the full suite of the server and drivers for
the X.Org X server. It does not provide the actual server itself."
suggested it was not required. Clearly it is. Reinsta
I am getting this problem as well. I had two computers one of which was
working after the recent set of updates in stretch and the other was crashing.
I decided to check on differences in the installations and on the computer that
was working I had all the xserver video packages installed and
If the problem I had was unrelated then I would have filed a separate
bug. However the problem I had was exactly as described and discussed
above.
I have found that the problem, certainly on my two netbooks, is that the
package now requires
CONFIG_DRM_I915_KMS=y
to be set.
This was evidentl
This bug has come up on two different netbooks. The options in the kernel
configurations:
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
are set.
The kernels are the latest 2.6.32 from Debian.
Julien wrote:
>That sounds like an issue with your kernel. If you have trouble
Evgeny M. Zubok wrote:
> For 0.6.0 version you need to set the DefaultDepth to 16 (man xorg.conf) in
> "Screen" section of xorg.conf.
That worked.
Many thanks.
John
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@li
Package: xserver-xorg-video-s3
Version: 1:0.6.0-1
Severity: important
As soon as X is started the screen switches to power saving mode, the
same when running gdm or xorg. If I use the vesa driver this does not
happen (but it is slow).
This happened after installing Lenney, it worked all right
Hi
Raphael Geissert wrote:
The problem you are facing appears to be a hardware problem, and according to
Xavier Bachelot (one of the openchrome devs) it is likely to be in the i2c
bus. He suggests forcing the only active output to be the CRT, to try to
workaround the incorrect mode used when
Raphael Geissert wrote:
Yes, if you use nm you will see the via_hook_segment symbol in via_dma.ko:
$ nm /lib/modules/$(uname -r)/kernel/drivers/char/drm/via.ko | grep
via_hook_segment
0e94 t via_hook_segment
But IIRC (based on other messages found via google) the bug is caused
by the DRI d
Raphael Geissert wrote:
The problem is in the 3d driver (unichrome DRI in Mesa), not with the
2d driver (openchrome).
I'm leaving it assigned to this package (and not libgl1-mesa-dri) as
it might be possible for someone at -openchrome to fix it.
OK. I noted that comment although there is no re
I am getting the same problem. I am using Lenny on a Mini ITX desktop.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
10 matches
Mail list logo
