Difference between revisions of "Bug/gma3100driver"

From LinuxMCE
Jump to: navigation, search
Line 1: Line 1:
 +
{{stub}}
 +
[[category: tutorials]]
 
==description==
 
==description==
 
with some drivers/installation, booting may lead to modifying its xorg.conf file. that happened with lmce 7.10 DVD installation and an md with intel gma 3100 chipset. <br />
 
with some drivers/installation, booting may lead to modifying its xorg.conf file. that happened with lmce 7.10 DVD installation and an md with intel gma 3100 chipset. <br />

Revision as of 17:32, 28 July 2008

This article is a stub and requires expansion

description

with some drivers/installation, booting may lead to modifying its xorg.conf file. that happened with lmce 7.10 DVD installation and an md with intel gma 3100 chipset.
it seems to be a matter of driver not allowed to handle the card.

recognize the bug

try

lshwd | grep ' VGA ' | head -1 | sed 's/^.*(\([^()]*\)).*$/\1/'

if you get 'vesa' then you may have the bug; try then

lspci | grep ' VGA ' |  sed 's/^.*controller: //' | sed 's/ (.*$//'

if you get something like Intel Corporation 82G33/G31 Express Integrated Graphics Controller then you are using the driver and having the bug

one solution(preventing xorg.conf rebuilding)

this solution is not good but works. at least, so far that i tryed it

  1. log (ssh) in the media director as root
  2. follow prevent lmce from changing xorg (basically, insert a new line with exit 0 on 2nd line of /usr/pluto/bin/Xconfigure.sh ).
  3. run dpkg-reconfigure xserver-xorg to generate a clean new xorg.conf. follow instructions. if you don't know, keep default values
  4. reboot the md: reboot

using other drivers

i am testing this atm(guigolum)