Difference between revisions of "Bug/gma3100driver"

From LinuxMCE
Jump to: navigation, search
(New page: with some drivers/installation, booting a media director may lead to modifying its xorg.conf file. that happened with lmce 7.10 DVD installation and an md with '''Intel Corporation 82G33/G...)
 
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
with some drivers/installation, booting a media director may lead to modifying its xorg.conf file. that happened with lmce 7.10 DVD installation and an md with '''Intel Corporation 82G33/G31 Express Integrated Graphics Controller''' and led to using the vesa drivers <br />
+
{{stub}}
one solution is:
+
[[Category:LinuxMCE Configuration]]
#log (ssh) in the media director. to do so:
+
 
##get the media director's ip (md_IP)in webadmin->wizard->devices->media director. you just get its name and you have a field named 'IP' which gives you the required ip. (something like 192.168.80.X, where X is a number).
+
 
## log yourself as root on the core: sudo bash, enter password
+
==description==
## once you got ot, just type ssh <md_IP>
+
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 />
#follow [[Custom_Display_Resolutions#Step_4:_Prevent_LinuxMCE_from_changing_the_Xorg_config|prevent lmce from changing xorg]] (basically, insert a new line with exit 0 on 2nd line of ''/usr/pluto/bin/Xconfigure.sh'' ). to edit you can use vi:
+
it seems to be a matter of driver not allowed to handle the card.
## '''vi /usr/pluto/bin/Xconfigure.sh''' to open the file
+
 
## place the cursor on the beginning of line 2, press'i' , and add 'exit 0', enter, to add the line
+
==recognize the bug==
## press ':x', enter.to save the file
+
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
 +
#log (ssh) in the media director as root
 +
#follow [[Custom_Display_Resolutions#Step_4:_Prevent_LinuxMCE_from_changing_the_Xorg_config|prevent lmce from changing xorg]] (basically, insert a new line with exit 0 on 2nd line of ''/usr/pluto/bin/Xconfigure.sh'' ).
 
#run '''dpkg-reconfigure xserver-xorg''' to generate a clean new xorg.conf. follow instructions. if you don't know, keep default values
 
#run '''dpkg-reconfigure xserver-xorg''' to generate a clean new xorg.conf. follow instructions. if you don't know, keep default values
 
#reboot the md: '''reboot'''
 
#reboot the md: '''reboot'''
 +
 +
==using other drivers==
 +
i am testing this atm(guigolum)

Latest revision as of 21:53, 19 October 2012

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)