[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#503947: marked as done (Lenny X.org does not detect/setup VIA graphics chips)



Your message dated Mon, 02 Feb 2009 22:46:38 +0100
with message-id <498769BE.6010509@ens-lyon.org>
and subject line Re: Bug#503947: Lenny X.org does not detect/setup VIA graphics chips
has caused the Debian Bug report #503947,
regarding Lenny X.org does not detect/setup VIA graphics chips
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
503947: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=503947
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: xserver-xorg
Version: 1:7.3+18

Installed a fresh copy of Debian Lenny on a VIA C3 powered laptop with
a CLE266 graphics chip. X.org failed to start. A description of the
problem can be found in this post of another person with the identical
problem: http://forums.debian.net/viewtopic.php?p=182006&sid=3a4ceaee52c267725c8df56fcb292f83

It looketh like some special detection will be needed for VIA graphics
chips in order to create an xorg.conf file for them. As a note, Debian
Etch worked fine on this laptop using the VIA driver
xserver-xorg-video-via.

The driver used in Lenny is xserver-xorg-video-via (1:0.2.2-6).

Thanks,
Aaron Johnson



--- End Message ---
--- Begin Message ---
Aaron Johnson wrote:
> Hello Brice,
>
> Unfortunately, my laptop was stolen so I no longer am able to get thee
> the Xorg.0.log. Fortunately, my xorg.conf file was the ilch as the one
> listed in the link:
>   

Thanks for the reply. There's nothing wrong in the xorg.conf, it looks
like the VIA chipset was correctly detected. So I guess something wrong
happened during X startup after the installation, probably a wrong mode
was chosen.

We can't do anything without the log unfortunately. So since your laptop
has been stolen, we won't be able to debug, so I am closing this bug. If
anybody ever reproduces, please reopen and send your config and log.

Brice



--- End Message ---

Reply to: