|
Dpkg Reconfigure Xserver Xorg
Intel Edition For : Mepis Linux 6.x by : je.saist Typically, there isn't a need to do a dpkg-reconfigure on Intel's Integrated graphics. Unlike all Nvidia cards, as well as more recent ATi cards, 3D support for Intel graphics is part of the X.org graphics system. However, there are cases where using the dpkg-reconfigure process can be of benifit to a user. #1:
The first case is changing the base X.org resolution. This is
useful if the default resolution of the display device in use was not
detected properly. For example, an LCD that supports 1280*1024, but was
detected as 1024*768. This is also useful if changing from a 4:3
resolution screen to a 16:9 resolution screen. For example, if you
replace your LCD monitor and your base resolutions changed from
1280*1024 to 1440*900.
#2: The second case is more forced, specifically, when you are changing drivers. Examples of this would be if when an add-in ATi or Nvidia graphics card might be a potential culprit for crashes and systems lock ups. In this scenario, the add-in card would be removed and the system would default to the onboard graphics. As such, X.org would need to be changed to either VESA, or the onboard graphics driver. #3: The third case is a rarer one, specifically, when moving an installation of Mepis Linux from one computer to another. I did this with a Sager NP2885. So, enough yapping, lets get started. Unlike the original dpkg-reconfigure guide, this is done under the KDE Window manager while using the VESA driver. If you are in case style #2, you'll probably want to follow the first 10 steps on the original guide.
1: To start with, go ahead and open up Terminal Program (Konsole) in the system menu.  2: Your terminal will probably not come up maximized. I've set mine already to make this a little easier to read.  3: In the termainl type in the letters su Then hit Enter on the Keyboard.  4: Enter your /root password, then hit enter on the keyboard.  5: Now we should be in /root.  6: Type out the command dpkg-reconfigure xserver-xorg Then hit enter on the keyboard.  7: We should now be in the current Ubuntu Configuration. Hit enter on the keyboard to have X.org try to automatically detect the graphic card.  8: X.org has correctly identified this system as using the i810 driver. As is usual in this guide, Hit Enter on the keyboard to continue.  9: Again, X.org has correctly labeled this card. Yes, Hit Enter on the keyboard again.  10: Hit Enter on the keyboard.  11: Yet another Enter on the keyboard.  12: X.org is fairly intelligent about setting memory amounts. If you are running in a VM though, probably a good idea to limit the memory. Do keep in mind though, Mepis is meant to be run on actual Hardware, not in a virtual machine. Hit Enter on the keyboard.  13: I still don't know the difference between these two. For now, I've just been selecting no. Hit enter on the keyboard to continue.  14: This, sadly, is where X.org is not actually that good. So far it's had a 100% failure rate to detect the keyboard type. So, I normally leave it on No... And hit enter on the keyboard.  15: X.org should go ahead and fill this in with US. If you live in another country, input your code, then hit enter on the keyboard.  16: Most of the time, this should be filled in with xorg, which is what it defaults to. Hit enter on the keyboard.  17: Might want to read this page because this information is required on the next entry. Hit enter on the keyboard  18: Enter the Keyboard model number. If you are not sure, do what I do and put in pc104. Hit enter on the keyboard to continue.  20: Another enter on the keyboard.  21: Still yet another enter on the keyboard.  22: I have no idea what options can go here. So, yes, hit enter on the keyboard.  23: Still don't know the difference. ImPS/2 always seems to work, so... yes. Another hit to enter on the keyboard.  24: I'm really trying to come up with a good reason to hit no here and can't. About the only time where I think this could be a problem is in Unreal Tournament when using the modified rocket launcher firing mechanism to bunch the rockets up... Hit enter on the keyboard to continue.  25: X.org will now list out the various modules used in the graphics system. Hit Enter on the keyboard to continue.  26: Most of these should already be checked. Another Enter on the keyboard please.  27: X.org will now ask if it is alright to write the configuration files to disk. ... um... yes? Is that not why we are doing this? Hit Enter on the keyboard.  28: X.org will now ask if can attempt to identify the monitor. Might as well hit enter on the keyboard.  29: Don't be very surprised if the display semi-corrupts during the detection.  30: Of course, this being a laptop, I got a Generic Monitor ID. Unless you are planning on running dual monitors, this really isn't a concern right now... So, yes, hit enter on the keyboard.  31: At this point X.org will list the available resolutions to render in.  32: You can can scroll down the list with the arrow keys on the keyboard.  33: For this laptop, I need to select 1024x768, 800x600, and 640x480. If your resolution is not marked, use the spacebar on the keyboard to select the resolution. Once the resolutions are selected, hit enter on the keyboard to continue.  34: X.org always defaults to the Advanced monitor refresh rate setting. Hit the UP arrow on the keyboard's arrow keys to move to Medium.  35: With Medium selected, hit Enter on the keyboard.  36: Here is where we can choose the starting resolution for X.org. Use the arrow keys on the keyboard to select the desired starting resolution. Then hit Enter on the keyboard to continue.  37: Of course we want to write the configuration files to the keyboard. Another hit to Enter on the keyboard.  38: Truth be told, the Intel chips are several times faster in 16bit color than in 24bit color.  39: But, seriously, as slow as the Intel chips are, it's not like we will be running UT. I went with the higher quality 24bit rendering And, yes, one final enter on the keyboard.  40: We are done with this... so  41: yes, reboot.  Take me back to the Guides. |