vincent Posted January 5, 2008 Share Posted January 5, 2008 (edited) I ran an update to 7.10 from 7.04 and i hosed my xserver, when i boot up and hit esc. I get alot of 7.10 options some with an older kernel version but each one with a (recovery mode) option. i selected recovery mode on each and login as root But i can't locate xorg.conf when i do a ls -a in /etc/X11 What do i do? :h edit: update ok, found my xorg.conf but a sudo dpkg-reconfigure xorg.conf doesn't work Edited January 8, 2008 by ripgut Link to comment Share on other sites More sharing options...
zivan56 Posted January 5, 2008 Share Posted January 5, 2008 sudo dpkg-reconfigure xserver-xorg? Link to comment Share on other sites More sharing options...
vincent Posted January 5, 2008 Author Share Posted January 5, 2008 sudo dpkg-reconfigure xserver-xorg? ?That doesn't work either i get a xserver-org is not installed and no info is available Link to comment Share on other sites More sharing options...
vincent Posted January 5, 2008 Author Share Posted January 5, 2008 FIXED It's a dpkg-reconfigure xserver-xorg instead of dpkg-reconfigure xserver-org :pinch: Link to comment Share on other sites More sharing options...
vincent Posted January 6, 2008 Author Share Posted January 6, 2008 trying to remove xorg-driver-fglrx from my system to start over and i get the following error Link to comment Share on other sites More sharing options...
Farstrider Posted January 6, 2008 Share Posted January 6, 2008 Hi Ripgut, I am a novice when it comes to this sort of thing, but perhaps this will help. Go here and have a look, it may just help! You can also try this: There's no need to remove the module. If you want to use the open source driver just set the driver to "ati" (instead of fglrx) in the Section Device of your /etc/X11/xorg.conf. Then log out and press CTRL+ALT+Backspace Link to comment Share on other sites More sharing options...
vincent Posted January 6, 2008 Author Share Posted January 6, 2008 I tried removing it in Terminal and get the following: dpkg-divert: rename involves overwriting `/etc/xdg/compiz/compiz-manager' with different file `/etc/xdg/compiz/compiz-manager.ubuntu', not allowed dpkg: error processing xorg-driver-fglrx (--remove): subprocess post-removal script returned error exit status 2 Errors were encountered while processing: xorg-driver-fglrx E: Sub-process /usr/bin/dpkg returned an error code (1) Hi Ripgut, I am a novice when it comes to this sort of thing, but perhaps this will help. Go here and have a look, it may just help!You can also try this: There's no need to remove the module. If you want to use the open source driver just set the driver to "ati" (instead of fglrx) in the Section Device of your /etc/X11/xorg.conf. Then log out and press CTRL+ALT+Backspace No dice, here's my xorg.conf: # xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "Files" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device" "/dev/input/mice" Option "Protocol" "ImPS/2" Option "ZAxisMapping" "4 5" Option "Emulate3Buttons" "true" EndSection Section "InputDevice" Identifier "Synaptics Touchpad" Driver "synaptics" Option "SendCoreEvents" "true" Option "Device" "/dev/psaux" Option "Protocol" "auto-dev" Option "HorizEdgeScroll" "0" EndSection Section "InputDevice" Driver "wacom" Identifier "stylus" Option "Device" "/dev/input/wacom" Option "Type" "stylus" Option "ForceDevice" "ISDV4" # Tablet PC ONLY EndSection Section "InputDevice" Driver "wacom" Identifier "eraser" Option "Device" "/dev/input/wacom" Option "Type" "eraser" Option "ForceDevice" "ISDV4" # Tablet PC ONLY EndSection Section "InputDevice" Driver "wacom" Identifier "cursor" Option "Device" "/dev/input/wacom" Option "Type" "cursor" Option "ForceDevice" "ISDV4" # Tablet PC ONLY EndSection Section "Device" Identifier "Generic Video Card" Driver "vesa" BusID "PCI:1:0:0" EndSection Section "Monitor" Identifier "Generic Monitor" Option "DPMS" HorizSync 30-70 VertRefresh 50-160 EndSection Section "Screen" Identifier "Default Screen" Device "Generic Video Card" Monitor "Generic Monitor" DefaultDepth 24 EndSection Section "ServerLayout" Identifier "Default Layout" Screen "Default Screen" InputDevice "Generic Keyboard" InputDevice "Configured Mouse" # Uncomment if you have a wacom tablet # InputDevice "stylus" "SendCoreEvents" # InputDevice "cursor" "SendCoreEvents" # InputDevice "eraser" "SendCoreEvents" InputDevice "Synaptics Touchpad" EndSection Link to comment Share on other sites More sharing options...
Farstrider Posted January 6, 2008 Share Posted January 6, 2008 I have had a look but do not really have enough info so I phoned one of my Linux buds who is an Ubuntu nut and he said that when he gets home he will be prepared to chat with you on IRC and talk you through the repair procedure. Perhaps you can post again if you come right before he gets back to help! I will also keep looking to see if I have missed anything. Cheers. Link to comment Share on other sites More sharing options...
vincent Posted January 8, 2008 Author Share Posted January 8, 2008 Update: I've managed to purge everything compiz and all the fglrx drivers. I've installed the xserver-xorg-driver-ati package, and ran a dpkg-reconfigure xserver-xorg and i selected "ati" so now i think i need to do is edit my xorg.conf because when i do a glxinfo | grep vendor i get the following: Xlib: extension "ATIFGLRXDRI" missing on display ":0.0". Error: couldn't find RGB GLX visual So i know i'm close to being able to play Urban Terror 4 (which is why i'm posting ) :p Link to comment Share on other sites More sharing options...
vincent Posted January 12, 2008 Author Share Posted January 12, 2008 Ok so i've started with this guide. And everything seems to work, until i get to step 2, in which i run a sudo gedit /etc/default/linux-restricted-modules-common. (gedit instead of nano, because i'm running Gnome) And i get a blank text file. What am i doing wrong? Link to comment Share on other sites More sharing options...
Niels. Posted January 12, 2008 Share Posted January 12, 2008 Try running it in nano, i don't know if GEdit supports an input parameter so try nano. Link to comment Share on other sites More sharing options...
vincent Posted January 12, 2008 Author Share Posted January 12, 2008 Try running it in nano, i don't know if GEdit supports an input parameter so try nano. nano still comes up blank Link to comment Share on other sites More sharing options...
Barney T. Administrators Posted January 12, 2008 Administrators Share Posted January 12, 2008 Ok so i've started with this guide.And everything seems to work, until i get to step 2, in which i run a sudo gedit /etc/default/linux-restricted-modules-common. (gedit instead of nano, because i'm running Gnome) And i get a blank text file. What am i doing wrong? I wonder if you should execute that command without the "period" at the end? sudo gedit /etc/default/linux-restricted-modules-common Link to comment Share on other sites More sharing options...
vincent Posted January 12, 2008 Author Share Posted January 12, 2008 I wonder if you should execute that command without the "period" at the end? :pinch: hey it's 10am here :p thanks Barney Link to comment Share on other sites More sharing options...
Barney T. Administrators Posted January 12, 2008 Administrators Share Posted January 12, 2008 :laugh: NP Link to comment Share on other sites More sharing options...
vincent Posted January 12, 2008 Author Share Posted January 12, 2008 :laugh: NP Ok, so when i get to the the sudo modprobe fglrx part, and run that i get the following: Not loading fglrx module; not used in /etc/X11/xorg.conf So do i have to put this in the driver section of my xorg.conf? Edit: here's my xorg.conf by the way: # xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "Files" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device" "/dev/input/mice" Option "Protocol" "ImPS/2" Option "ZAxisMapping" "4 5" Option "Emulate3Buttons" "true" EndSection Section "InputDevice" Identifier "Synaptics Touchpad" Driver "synaptics" Option "SendCoreEvents" "true" Option "Device" "/dev/psaux" Option "Protocol" "auto-dev" Option "HorizEdgeScroll" "0" EndSection Section "InputDevice" Driver "wacom" Identifier "stylus" Option "Device" "/dev/input/wacom" Option "Type" "stylus" Option "ForceDevice" "ISDV4" # Tablet PC ONLY EndSection Section "InputDevice" Driver "wacom" Identifier "eraser" Option "Device" "/dev/input/wacom" Option "Type" "eraser" Option "ForceDevice" "ISDV4" # Tablet PC ONLY EndSection Section "InputDevice" Driver "wacom" Identifier "cursor" Option "Device" "/dev/input/wacom" Option "Type" "cursor" Option "ForceDevice" "ISDV4" # Tablet PC ONLY EndSection Section "Device" Identifier "ATI Mobility 9000" Driver "vesa" BusID "PCI:1:00:0" VideoRam 64 EndSection Section "Monitor" Identifier "Generic Monitor" Option "DPMS" HorizSync 30-70 VertRefresh 50-160 EndSection Section "Screen" Identifier "Default Screen" Device "ATI Mobility 9000" Monitor "Generic Monitor" DefaultDepth 24 EndSection Section "ServerLayout" Identifier "Default Layout" Screen "Default Screen" InputDevice "Generic Keyboard" InputDevice "Configured Mouse" # Uncomment if you have a wacom tablet # InputDevice "stylus" "SendCoreEvents" # InputDevice "cursor" "SendCoreEvents" # InputDevice "eraser" "SendCoreEvents" InputDevice "Synaptics Touchpad" EndSection Link to comment Share on other sites More sharing options...
Rob2687 Posted January 12, 2008 Share Posted January 12, 2008 fglrx only supports Radeon 9500 and up. Link to comment Share on other sites More sharing options...
vincent Posted January 14, 2008 Author Share Posted January 14, 2008 Did a bit of playing around and now, when i enter glxinfo | grep vendor, i get: server glx vendor string: SGI client glx vendor string: ATI OpenGL vendor string: Tungsten Graphics, Inc. So i know i'm a bit closer to getting this working. Link to comment Share on other sites More sharing options...
vincent Posted January 15, 2008 Author Share Posted January 15, 2008 Bump, anyone? Link to comment Share on other sites More sharing options...
vincent Posted January 16, 2008 Author Share Posted January 16, 2008 Bump again. Link to comment Share on other sites More sharing options...
markwolfe Veteran Posted January 16, 2008 Veteran Share Posted January 16, 2008 Does glxinfo report that direct rendering is being used? glxinfo | grep -i direct If the "Tungsten Graphics" being reported by your vendor string is THIS Tungsten Graphics, then it seems that your chipset is well-supported by the vendor. Link to comment Share on other sites More sharing options...
vincent Posted January 16, 2008 Author Share Posted January 16, 2008 Does glxinfo report that direct rendering is being used?glxinfo | grep -i direct If the "Tungsten Graphics" being reported by your vendor string is THIS Tungsten Graphics, then it seems that your chipset is well-supported by the vendor. glxinfo | grep "direct rendering" direct rendering: Yes magallon@magallon-laptop:~$ glxinfo | grep vendor server glx vendor string: SGI client glx vendor string: SGI OpenGL vendor string: Tungsten Graphics, Inc. Link to comment Share on other sites More sharing options...
markwolfe Veteran Posted January 16, 2008 Veteran Share Posted January 16, 2008 Then you have sweet 3D-accelerated goodness :) Link to comment Share on other sites More sharing options...
vincent Posted January 17, 2008 Author Share Posted January 17, 2008 Then you have sweet 3D-accelerated goodness :) Actually, i don't... :( Following this guide results in my screen turning off and going completely black. Following this one results in my screen going grey with a bunch of white code text flashing on and off at a real low res. I have to boot into recovery mode, and run a dpkg-reconfigure xserver-sorg, and start all over each time. And these were the only two guides taht i can find for my chipset. Link to comment Share on other sites More sharing options...
markwolfe Veteran Posted January 17, 2008 Veteran Share Posted January 17, 2008 Does your xorg.conf specify a PCI Bus ID? If so, is it correct? You can do an lspci to list out what items are on your bus, and the ID'd location of each. An lspci | grep VGA should single out your video card. Link to comment Share on other sites More sharing options...
Recommended Posts