Page 7 of 7 FirstFirst ... 567
Results 61 to 69 of 69

Thread: openSUSE Graphic Card Practical Theory Guide for Users

  1. #61
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,264
    Blog Entries
    1

    Default Re: openSUSE Graphic Card Practical Theory Guide for Users

    ... and I came to the conclusion that this is NOT a driver that one would use in nominal ATI, nVidia, nor Intel hardware.
    No, its for video capture. At a company (that I used to work for as a contractor) which was involved with manufacture of outdoor LED screens, the v4l driver was used in their Linux video servers to overlay text on captured graphics, before being processed and sent over ethernet to the LED panels. They did use nvidia GPU's to process the data, but the servers were often running headless.

  2. #62
    Join Date
    Mar 2008
    Location
    Phuket, Thailand
    Posts
    26,549
    Blog Entries
    37

    Default Re: openSUSE Graphic Card Practical Theory Guide for Users

    This post of user Reg_gie on how to setup 3+ screens using nVidia was quite interesting:
    RandR / Xinerama - how to make work in OSE 11.2
    This was for openSUSE-11.2 but since openSUSE-11.3 and 11.4 will use an xorg.conf file if it is present, I suspect there is a reasonable possibility this will work with openSUSE-11.3 or 11.4.

    I've linked/copied the post here so a lot of time does not need to be spent searching for this.

    Quote Originally Posted by Reg_gie View Post
    For anyone who needs a 3+ monitor setup (this is for 4) here is an example of what works for me with NVIDIA drivers. The nice this thing is that it's much less code now.

    Code:
    Section "Files"
    	ModulePath   "/usr/lib64/xorg/modules/updates"
    	ModulePath   "/usr/lib64/xorg/modules"
    	FontPath     "/usr/share/fonts/misc:unscaled"
    	FontPath     "/usr/share/fonts/truetype/"
    	FontPath     "/usr/share/fonts/TTF/"
    	FontPath     "/usr/share/fonts/OTF"
    	FontPath     "/usr/share/fonts/Type1/"
    	FontPath     "/usr/share/fonts/100dpi:unscaled"
    	FontPath     "/usr/share/fonts/75dpi:unscaled"
    EndSection
    
    Section "Module"
    	Load  "glx"
    	Load  "vnc"
    	Load  "dri2"
    	Load  "dri"
    	Load  "extmod"
    	Load  "dbe"
    	Load  "record"
    	Load  "glx"
    EndSection
    
    Section "InputDevice"
    	Identifier  "Keyboard0"
    	Driver      "kbd"
    EndSection
    
    Section "InputDevice"
    	Identifier  "Mouse0"
    	Driver      "mouse"
    	Option	    "Protocol" "auto"
    	Option	    "Device" "/dev/input/mice"
    	Option	    "ZAxisMapping" "4 5 6 7"
    EndSection
    
    Section "ServerLayout"
    	Identifier     "Layout All"
        	Screen      0  "Screen0" 0 0
        	Screen      1  "Screen1" RightOf "Screen0"
        	Screen      2  "Screen2" LeftOf  "Screen0"
        	Screen      3  "Screen3" Above   "Screen0"
    	InputDevice    "Mouse0" "CorePointer"
    	InputDevice    "Keyboard0" "CoreKeyboard"
    EndSection
    
    Section "ServerFlags"
      # Uncomment the following option to reenable kbd/mouse driver input sections. 
      # Otherwise evdev driver is used. 
      #Option       "AutoAddDevices" "off"
        	Option     "Xinerama" "on"
    EndSection
    
    Section "Modes"
        Identifier      "Modes0"
        ModeLine        "1680x1050" 146.00 1680 1784 1960 2240 1050 1053 1059 1089 +hsync -vsync
    EndSection
    
    #    	Option       "CalcAlgorithm" "XServerPool"
    Section "Monitor"
    	Identifier   "Monitor0"
        	VendorName   "GSM"
        	ModelName    "LG ELECTRONICS L227W"
        	UseModes     "Modes0"
        	DisplaySize  474 296
        	HorizSync    30-83
       	VertRefresh  50-75                                                              
        	Option       "DPMS"
        	Option       "PreferredMode" "1680x1050"
    EndSection
    
    Section "Monitor"
    	Identifier   "Monitor1"
        	VendorName   "GSM"
        	ModelName    "LG ELECTRONICS L227W"
        	UseModes     "Modes0"
        	DisplaySize  474 296
        	HorizSync    30-83
       	VertRefresh  50-75                                                              
        	Option       "DPMS"
        	Option       "PreferredMode" "1680x1050"
    EndSection
    
    Section "Monitor"
    	Identifier   "Monitor2"
        	VendorName   "GSM"
        	ModelName    "LG ELECTRONICS L227W"
        	UseModes     "Modes0"
        	DisplaySize  474 296
        	HorizSync    30-83
       	VertRefresh  50-75                                                              
        	Option       "DPMS"
        	Option       "PreferredMode" "1680x1050"
    EndSection
    
    Section "Monitor"
    	Identifier   "Monitor3"
        	VendorName   "GSM"
        	ModelName    "LG ELECTRONICS L227W"
        	UseModes     "Modes0"
        	DisplaySize  474 296
        	HorizSync    30-83
       	VertRefresh  50-75                                                              
        	Option       "DPMS"
        	Option       "PreferredMode" "1680x1050"
    EndSection
    
    Section "Device"
    	Identifier  "Card0"
    	Driver      "nvidia"
        	BoardName   "GeForce 8600 GT"
        	VendorName  "NVidia"
    	BusID       "PCI:1:0:0"
        	Screen      0
        	Option     "CoolBits"         "On"
    EndSection
    Section "Device"
    	Identifier  "Card1"
    	Driver      "nvidia"
        	BoardName   "GeForce 8600 GT"
        	VendorName  "NVidia"
    	BusID       "PCI:1:0:0"
        	Screen      1
    EndSection
    
    Section "Device"
    	Identifier  "Card2"
    	Driver      "nvidia"
        	BoardName   "GeForce 8600 GTS"
        	VendorName  "NVidia"
    	BusID       "PCI:2:0:0"
        	Screen      0
    EndSection
    Section "Device"
    	Identifier  "Card3"
    	Driver      "nvidia"
        	BoardName   "GeForce 8600 GTS"
        	VendorName  "NVidia"
    	BusID       "PCI:2:0:0"
        	Screen      1
    EndSection
    
    #	Option	   "ConnectedMonitor" "DFP"  # Digital Flat Panel (doesn't come on, don't use)
    #   	Option     "MultiGPU"         "Auto" # Causes only one screen to come on, don't use
    #   	Option     "SLI"              "Auto" # Causes only one screen to come on, don't use
    
    #    	Option     "TripleBuffer"     "True" #	This decreases the time an application stalls
    #		    while waiting for vblank events, but increases latency slightly (delay
    #		    between user input and displayed result).
    Section "Screen"
    	Identifier "Screen0"
    	Device     "Card0"
    	Monitor    "Monitor0"
    	DefaultDepth 24
    	SubSection "Display"
    		Viewport  0 0
    		Depth     24
    		modes     "1680x1050"
    	EndSubSection
        	Option     "CursorShadow"     "On"
        	Option     "RenderAccel"      "True"
        	Option     "TripleBuffer"     "False"
        	Option 	   "RandRRotation"    "True"
    	Option 	   "OnDemandVBlankInterrupts" "On"  # Experimental
    EndSection
    
    Section "Screen"
    	Identifier "Screen1"
    	Device     "Card1"
    	Monitor    "Monitor1"
    	DefaultDepth 24
    	SubSection "Display"
    		Viewport  0 0
    		Depth     24
    		modes     "1680x1050"
    	EndSubSection
        	Option     "CursorShadow"     "On"
        	Option     "RenderAccel"      "True"
        	Option     "TripleBuffer"     "False"
        	Option 	   "RandRRotation"    "True"
    	Option 	   "OnDemandVBlankInterrupts" "On"  # Experimental
    EndSection
    
    Section "Screen"
    	Identifier "Screen2"
    	Device     "Card2"
    	Monitor    "Monitor2"
    	DefaultDepth 24
    	SubSection "Display"
    		Viewport  0 0
    		Depth     24
    		modes     "1680x1050"
    	EndSubSection
        	Option     "CursorShadow"     "On"
        	Option     "RenderAccel"      "True"
        	Option     "TripleBuffer"     "False"
        	Option 	   "RandRRotation"    "True"
    	Option 	   "OnDemandVBlankInterrupts" "On"  # Experimental
    EndSection
    
    Section "Screen"
    	Identifier "Screen3"
    	Device     "Card3"
    	Monitor    "Monitor3"
    	DefaultDepth 24
    	SubSection "Display"
    		Viewport  0 0
    		Depth     24
    		modes     "1680x1050"
    	EndSubSection
        	Option     "CursorShadow"     "On"
        	Option     "RenderAccel"      "True"
        	Option     "TripleBuffer"     "False"
        	Option 	   "RandRRotation"    "True"
    	Option 	   "OnDemandVBlankInterrupts" "On"  # Experimental
    EndSection

  3. #63
    Join Date
    Mar 2008
    Location
    Phuket, Thailand
    Posts
    26,549
    Blog Entries
    37

    Default Re: openSUSE Graphic Card Practical Theory Guide for Users

    For users struggling a bit with a radeon open source driver, I found this article of interest: X.Org Wiki - radeonBuildHowTo

  4. #64
    Join Date
    Mar 2008
    Location
    Phuket, Thailand
    Posts
    26,549
    Blog Entries
    37

    Default Re: openSUSE Graphic Card Practical Theory Guide for Users

    Quote Originally Posted by oldcpu View Post
    This post of user Reg_gie on how to setup 3+ screens using nVidia was quite interesting:
    Further to the above post (which proposes edits to /etc/X11/xorg.conf on an openSUSE-11.2 system), here is a link to a thread with a user using the radeon driver to drive 4 monitors on openSUSE-11.4 and instead contains edits to the /etc/x11/xorg.conf.d/ 50-device.conf, 50-monitor.conf and 50-screen.conf configuration files:
    Config Problem - ATI v4800 running Quad Monitors on OpenSuSE 11.4
    ...
    I'll repost salient parts of it here so users do not have to struggle looking for it:

    Quote Originally Posted by JWMerrow View Post
    I went to the FirePro Beta Drivers and it was able to install. However, after I did that, the box would not run xdm/kdm anymore (post reboot). In X.Org.log.0 it showed that fglrx would always throw errors and crash.

    ... I was able to get my xorg.conf.d files squared away and am now running four monitors with Xinerama enabled.

    Files I modified under xorg.conf.d:

    50-screen.conf:
    Code:
    Section "Screen"
      Identifier "Default Screen"
    
      Device "Default Device"
    
      ## Doesn't help for radeon/radeonhd drivers; use magic in
      ## 50-device.conf instead
      Monitor "Default Monitor"
    
    EndSection
    
    Section "ServerLayout"
            Identifier "Layout[all]"
            Screen 0 "Screen0" 0 1050
            Screen 1 "Screen1" 1680 1050
            Screen 2 "Screen2" 0 0
            Screen 3 "Screen3" 1680 0
            Option  "Clone" "off"
            Option  "Xinerama" "1"
    EndSection
    
    Section "Screen"
            Identifier "Screen0"
            Device     "Card0"
            Monitor    "Monitor0"
            DefaultDepth 24
            SubSection "Display"
                    Viewport  0 0
                    Depth     24
                    modes     "1680x1050"
            EndSubSection
            Option     "CursorShadow"     "On"
            Option     "RenderAccel"      "True"
            Option     "TripleBuffer"     "False"
            Option     "RandRRotation"    "True"
            Option     "OnDemandVBlankInterrupts" "On"  # Experimental
    EndSection
    
    Section "Screen"
            Identifier "Screen1"
            Device     "Card1"
            Monitor    "Monitor1"
            DefaultDepth 24
            SubSection "Display"
                    Viewport  0 0
                    Depth     24
                    modes     "1680x1050"
            EndSubSection
            Option     "CursorShadow"     "On"
            Option     "RenderAccel"      "True"
            Option     "TripleBuffer"     "False"
            Option     "RandRRotation"    "True"
            Option     "OnDemandVBlankInterrupts" "On"  # Experimental
    EndSection
    
    Section "Screen"
            Identifier "Screen2"
            Device     "Card2"
            Monitor    "Monitor2"
            DefaultDepth 24
            SubSection "Display"
                    Viewport  0 0
                    Depth     24
                    modes     "1680x1050"
            EndSubSection
            Option     "CursorShadow"     "On"
            Option     "RenderAccel"      "True"
            Option     "TripleBuffer"     "False"
            Option     "RandRRotation"    "True"
            Option     "OnDemandVBlankInterrupts" "On"  # Experimental
    EndSection
    
    Section "Screen"
            Identifier "Screen3"
            Device     "Card3"
            Monitor    "Monitor3"
            DefaultDepth 24
            SubSection "Display"
                    Viewport  0 0
                    Depth     24
                    modes     "1680x1050"
            EndSubSection
            Option     "CursorShadow"     "On"
            Option     "RenderAccel"      "True"
            Option     "TripleBuffer"     "False"
            Option     "RandRRotation"    "True"
            Option     "OnDemandVBlankInterrupts" "On"  # Experimental
    EndSection
    50-monitor.conf
    Code:
    #Section "Monitor"
     # Identifier "Default Monitor"
    
      ## If your monitor doesn't support DDC you may override the
      ## defaults here
      #HorizSync 28-85
      #VertRefresh 50-100
    
      ## Add your mode lines here, use e.g the cvt tool
    
    #EndSection
    
    Section "Monitor"
            Identifier   "Monitor0"
            VendorName   "HP"
            ModelName    "HP LA2205"
            UseModes     "Modes0"
            DisplaySize  478 299
            HorizSync    24.0 - 83.0
            VertRefresh  50 - 76                                                              
            Option       "DPMS"
            Option       "PreferredMode" "1680x1050"
    EndSection
    
    Section "Monitor"
            Identifier   "Monitor1"
            VendorName   "HP"
            ModelName    "HP LA2205"
            UseModes     "Modes0"
            DisplaySize  478 299
            HorizSync    24.0 - 83.0
            VertRefresh  50 - 76                                                            
            Option       "DPMS"
            Option       "PreferredMode" "1680x1050"
    EndSection
    
    Section "Monitor"
            Identifier   "Monitor2"
            VendorName   "HP"
            ModelName    "HP LA2205"
            UseModes     "Modes0"
            DisplaySize  478 299
            HorizSync    24.0 - 83.0
            VertRefresh  50 - 76                                                            
            Option       "DPMS"
            Option       "PreferredMode" "1680x1050"
    EndSection
    
    Section "Monitor"
            Identifier   "Monitor3"
            VendorName   "HP"
            ModelName    "HP LA2205"
            UseModes     "Modes0"
            DisplaySize  478 299
            HorizSync    24.0 - 83.0
            VertRefresh  50 - 76                                                            
            Option       "DPMS"
            Option       "PreferredMode" "1680x1050"
    EndSection
    50-device.conf
    Code:
    Section "Device"
      Identifier "Default Device"
    
      Driver "radeon"
    
      ## Required magic for radeon/radeonhd drivers; output name
      ## (here: "DVI-0") can be figured out via 'xrandr -q'
      #Option "monitor-DVI-0" "Default Monitor"
    
    EndSection
    
    Section "Device"
            Identifier  "Card0"
            Driver      "radeon"
            BoardName   "ATI FirePro V4800"
            VendorName  "ATI"
            BusID       "PCI:15:00:0"
            Screen      0
            #Option     "CoolBits"         "On"
    EndSection
    
    Section "Device"
            Identifier  "Card1"
            Driver      "radeon"
            BoardName   "ATI FirePro V4800"
            VendorName  "ATI"
            BusID       "PCI:15:00:0"
            Screen      1
            #Option     "CoolBits"         "On"
    EndSection
    
    Section "Device"
            Identifier  "Card2"
            Driver      "radeon"
            BoardName   "ATI FirePro V4800"
            VendorName  "ATI"
            BusID       "PCI:40:00:0"
            Screen      0
            #Option     "CoolBits"         "On"
    EndSection
    
    Section "Device"
            Identifier  "Card3"
            Driver      "radeon"
            BoardName   "ATI FirePro V4800"
            VendorName  "ATI"
            BusID       "PCI:40:00:0"
            Screen      1
            #Option     "CoolBits"         "On"
    EndSection
    90-keytable.conf
    Code:
    Section "InputClass"
            Identifier "LocalKeyboard"
            MatchIsKeyboard "on"
            Option  "XkbLayout"     "us"
    EndSection
    
    Section "Modes"
            Identifier "Modes0"
    EndSection
    Now if only I could figure out how to get this working without using Xinerama... Moving windows is much less responsive with Xinerama enabled (ie. Firefox).

    My only remaining problem is that it seems like XRandR just has problems working with multiple graphics cards... Or perhaps it's something I've done (or not done). Any ideas if this can work using XRandR, or should I stick with Xinerama and call it a day?

  5. #65
    Join Date
    Mar 2008
    Location
    Phuket, Thailand
    Posts
    26,549
    Blog Entries
    37

    Default Re: openSUSE Graphic Card Practical Theory Guide for Users

    Quote Originally Posted by own3dbydsquared View Post
    Hey guys, I have an nvidia optimus laptop. It is cool in Windows but opensuse, not so much due to the fact that the nvidia card is always running. Look here:
    Code:
    lspci | grep VGA
    00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 18)
    01:00.0 VGA compatible controller: nVidia Corporation GT215 [GeForce GT 335M] (rev a2)
    So how can I disable the nvidia card? I am running Intel fine. Or maybe I should do the vise versa?
    This reply is a bit late, but be certain to check out "bumblebee" : Where Basketball and OpenSource meets | Martin Juhl's Blog

    If you search here: software.opensuse.org: Search Results you will find bumblebee rpms packaged for openSUSE.

  6. #66
    Join Date
    Mar 2008
    Location
    Phuket, Thailand
    Posts
    26,549
    Blog Entries
    37

    Default Re: openSUSE Graphic Card Practical Theory Guide for Users

    Quote Originally Posted by markbilk View Post
    4. In order to have the xrandr commands executed automatically
    when X starts, add them to the init file or directory of
    your display manager, gdm, xdm or kdm
    Further to this post of markbilk, I thought it useful to reference the method chosen by user polbrian in this thread: Display config issue on 11.4 (radeon) ... note any mistakes in this interpretation are likely mine, and I apologize in advance for those ....

    The situation was polbrian was not obtaining the proper resolution that both his monitor and graphic card supported (and that the graphic driver supported). He could tell the inappropriate maximum resolution available in his PC as inappropriately configured by typing in a terminal:
    Code:
    xrandr
    So he conducted the following:
    1. check his hardware:
      Code:
      /sbin/lspci -nnk | grep VGA -A2
      which will tell one if one has a 'radeon' or 'nvidia' or 'intel' or other hardware.
      .
    2. check his loaded driver. The best way to do this is to look at the content of the /var/log/Xorg.0.log file. Another way to check (by listing loaded modules during a boot) is noted below:
      • Typically for radeon graphic hardware one will have the 'radeon' or 'radeonhd' or 'fglrx' driver. One can check to see what kernel module from the driver is loaded by typing (for example for the 'radeon' driver):
        Code:
        lsmod | grep radeon
      • Typically for nVidia graphic hardware one will have the 'nv' or 'nouveau' or 'nvidia' graphic driver module installed. One can check to see what kernel module from the driver is installed by typing (for example for the 'nouveau' driver is loaded by typing
        Code:
        lsmod | grep nouveau
        however in the case of the nouveau driver (and in fact this is the case for all drivers) it is best to see what driver is truely being used by checking the content of the /var/log/Xorg.0.log file
      • Typically for nVidia graphic hardware one will have the 'nv' or 'nouveau' or 'nvidia' graphic driver module installed. One can check to see what kernel module from the driver is installed by typing (for example for the 'intel' driver is loaded by typing
        Code:
        lsmod | grep intel
        note the intel module may in fact be the 'i915' or other
    3. check the available resolutions by typing:
      Code:
      xrandr
      and assuming the resolution one wants is NOT there then proceed. If the resolution one wants IS listed there, then stop now, as this post is NOT intended to address that easier situation.
      .
    4. check to see what modelines will be required to provide the desired resolution. Lets say from research, one knows that their monitor will support a resolution of 1920x1080 @ 60 hz. Then type:
      Code:
      gtf 1920 1080 60
      one will get something like:
      Code:
        # 1920x1080 @ 60.00 Hz (GTF) hsync: 67.08 kHz; pclk: 172.80 MHz
        Modeline "1920x1080_60.00"  172.80  1920 2040 2248 2576  1080 1081 1084 1118  -HSync +Vsync
      .
    5. Apply modeline in a test with xrandr. Type the following as a test with that information (using xrandr) :
      Code:
      xrandr --newmode "1920x1080_60.00" 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -HSync +Vsync
      xrandr --addmode VGA-0 1920x1080_60.00
      xrandr --output VGA-0 --mode 1920x1080_60.00
      and if everything work with the proper resolution then the test was a success. Note this setting will be lost at the first reboot.
      .
    6. To apply this permanently (using the 'radeon' driver on RV280 5961 hardware as an example), polbrian applied the following edits to an /etc/X11/xorg.conf.d/50-device.conf, 50-monitor.conf and 50-screen.conf files:

      50-device.conf
      appended:
      Code:
      Section "Device"                                                             
                                                                                   
        Identifier     "Device-0"                                                  
        BoardName      "RV280 5961"                                                
        Driver         "radeon"                                                    
        Screen         0                                                           
        VendorName     "ATI"                                                       
      # BusID          PCI:01:00.0                                                 
                                                                                   
      EndSection
      plbrian had also determined his graphic card was in PCI slot 01:00.0

      50-monitor.conf
      appended
      Code:
      Section "Monitor"
      
        Identifier      "Monitor-VGA"
        DisplaySize     305 230
        HorizSync       30-81
        ModelName       "SYNCMASTER BM1943/943TM SYNCMASTER MAGIC CX943B/CX943BM(DIGITAL)"
        Option          "Monitor-VGA" "VGA-display"
        Option          "PreferredMode" "1920x1080"
        VendorName      "SAMSUNG"
        VertRefresh     56-75
        ModeLine        "1920x1080"  172.80  1920 2040 2248 2576  1080 1081 1084 1118  -HSync +Vsync
      
      EndSection
      Polbrian had obtained the information for the monitor (DisplaySize and ModelName and VendorName) comes from a legacy xorg.conf. However this information should not be too difficult to determine without a legacy xorg.conf. Sometimes the information will be inside the /var/log/Xorg.0.log file (assuming the monitor is correctly identified).

      and 50-screen.conf
      appended:
      Code:
      Section "Screen"
      
        Identifier    "VGA-display"
        Device        "Device-0"
        Monitor       "Monitor-VGA"
      
        SubSection "Display"
      
         Depth   24
      
        EndSubSection
      
      EndSection


    and then he rebooted and the radeon driver was loaded with the correct resolution being displayed on his monitor.

    I may have made some mistakes in the above, attempting to read between the lines and when attempting to simplify and make more generic (to all graphic cards) the explanation, so please comments/corrections are welcome.

    Ultimately the goal, if I succeed, is to reference this example in the more mature practical theory guide here: openSUSE Graphic Card Practical Theory Guide for Users

    Also note there is development work going on in a new sax3 which may eventually address this: SaX3 – Monitor Module completed

  7. #67

    Default Re: openSUSE Graphic Card Practical Theory Guide for Users

    Significant reduction in used power with proprietary ATI driver
    A few days ago I found out that the repository for the proprietary driver for an ATI card was changed. So I decided to see if that one is working. After installation it did work and the most interesting thing was that it dramatically reduced the power used by the system. In a quiet system the power used was 53% of the maximum load of the UPS, after using fglrx it reduced to 43%.

  8. #68
    Join Date
    Sep 2010
    Location
    Poland
    Posts
    1,918

    Default Re: openSUSE Graphic Card Practical Theory Guide for Users

    Quote Originally Posted by fdekruijf View Post
    Significant reduction in used power with proprietary ATI driver
    A few days ago I found out that the repository for the proprietary driver for an ATI card was changed. So I decided to see if that one is working. After installation it did work and the most interesting thing was that it dramatically reduced the power used by the system. In a quiet system the power used was 53% of the maximum load of the UPS, after using fglrx it reduced to 43%.
    I think You could also be interested in this thread :

    Possible Power Management regressions in recent Linux kernels ?

    PCIe, power management, and problematic BIOSes [LWN.net]

    The second link describes the powermanagement problem in more detail, especially read the comments under the article
    This of course may be or might not be related to your problem.

    I know I have it on my laptop. The easy way to check is :
    Code:
    # dmesg | grep ASPM
    If You are affected You should get something similar to this :
    Code:
    [ 0.000000] PCIe ASPM is forcedly enabled
    [ 0.439490] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
    
    Best regards,
    Greg
    Best regards,
    Greg

  9. #69

    Default Re: openSUSE Graphic Card Practical Theory Guide for Users

    Quote Originally Posted by oldcpu View Post
    Look for occurrences of:
    (==) FBDEV(0):
    which would indicate FBDEV driver in use. The following command may work (note syntax/spaces) to confirm this driver:
    Code:
    cat /var/log/Xorg.0.log | grep '('II')'' 'FBDEV
    Thanks for the great work on this guide, but the grep commands you provide are needlessly complex and error-prone. Instead you could write:

    Code:
    grep '(II) FBDEV' /var/log/Xorg.0.log
    and similarly for the other drivers (although I notice that the fglrx one is already partially simplified).

    You could even grep for all drivers in one go:

    Code:
    egrep '\(II\) (FBDEV|VESA|RADEON|fglrx|NV|NOUVEAU|NVIDIA|intel)' /var/log/Xorg.0.log
    However, on my openSUSE 12.1 system, this reveals a mix of lines containing FBDEV, VESA, and intel, so it doesn't make it particularly clear which one is active. So ideally the guide should go into more detail to explain exactly how to identify the active driver in these situations.

Page 7 of 7 FirstFirst ... 567

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •