FedoraForum.org - Fedora Support Forums and Community
Page 1 of 2 12 LastLast
Results 1 to 15 of 25
  1. #1
    Join Date
    Mar 2011
    Posts
    26
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    [f18] The nvidia mystery

    Hi,


    Here is the riddle for f18 and nvidia. I dont have any drivers:
    Code:
    rpm -qa | grep nvidia
    nvidia-settings-1.0-26.fc18.x86_64
    Code:
    rpm -qa | grep nouv
    The second command gives empty ansewer.
    But...
    Code:
    glxinfo | grep direct
    direct rendering: Yes
    What is going on?

    Code:
    glxgears 
    5215 frames in 5.0 seconds = 1042.892 FPS
    5940 frames in 5.0 seconds = 1187.809 FPS
    5630 frames in 5.0 seconds = 1125.961 FPS
    5577 frames in 5.0 seconds = 1115.276 FPS
    6168 frames in 5.0 seconds = 1233.488 FPS
    6771 frames in 5.0 seconds = 1354.196 FPS
    7011 frames in 5.0 seconds = 1402.192 FPS
    6852 frames in 5.0 seconds = 1370.264 FPS
    6505 frames in 5.0 seconds = 1300.921 FPS
    6178 frames in 5.0 seconds = 1235.505 FPS
    6610 frames in 5.0 seconds = 1321.950 FPS
    6985 frames in 5.0 seconds = 1396.932 FPS
    6500 frames in 5.0 seconds = 1299.917 FPS
    6182 frames in 5.0 seconds = 1236.376 FPS
    7141 frames in 5.0 seconds = 1428.043 FPS
    5728 frames in 5.0 seconds = 1145.592 FPS
    6628 frames in 5.0 seconds = 1325.525 FPS
    6745 frames in 5.0 seconds = 1348.947 FPS
    7144 frames in 5.0 seconds = 1428.681 FPS
    5912 frames in 5.0 seconds = 1182.362 FPS
    7121 frames in 5.0 seconds = 1424.179 FPS
    6385 frames in 5.0 seconds = 1276.983 FPS
    6755 frames in 5.0 seconds = 1350.973 FPS
    7190 frames in 5.0 seconds = 1437.968 FPS
    What is more the /etc/X11/xorg.conf is removed ie. does not exist.

    I do have two monitors but the second is not accepted by driver acceleration.

    When i instal the nvidia drivers from RPMFUsion i get the TwinView grayed out and Separate X Session plus xinerama (to drag windows between monitors) disables the acceleration.

    Again what is going on? I can't turn off the GPU acceleration

  2. #2
    Join Date
    Dec 2009
    Posts
    255
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: [f18] The nvidia mystery

    I would like to know about this myself. All the other Fedora updates, I go back FC2, required installing Nvidia drivers and Akmod. F 18 just works and very well.

  3. #3
    Join Date
    Aug 2005
    Posts
    718
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: [f18] The nvidia mystery

    xorg.conf went a long time ago. If you want to know whatt is happening look at /var/log/Xorg.0.log and do an lsmod which should show the nouveau kernel module. The userspace driver should be xorg-x11-drv-nouveau-1.0.6-1.fc18.i686.

    ---------- Post added at 03:23 PM ---------- Previous post was at 03:11 PM ----------

    I must confess I have never used the Nvidia drivers. You may have to blacklist the nouveau driver. There is a lot of discussion on this forum of nvidia issues.
    Try:-
    http://forums.fedoraforum.org/showthread.php?t=280750

  4. #4
    Join Date
    Mar 2011
    Posts
    26
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: [f18] The nvidia mystery

    Ok so my Xorg.0.log looks like this:
    Code:
     
    [    35.635] (**) Logitech USB-PS/2 Optical Mouse: Applying InputClass "evdev pointer catchall"
    [    35.635] (II) Using input driver 'evdev' for 'Logitech USB-PS/2 Optical Mouse'
    [    35.635] (**) Logitech USB-PS/2 Optical Mouse: always reports core events
    [    35.635] (**) evdev: Logitech USB-PS/2 Optical Mouse: Device: "/dev/input/event3"
    [    35.635] (--) evdev: Logitech USB-PS/2 Optical Mouse: Vendor 0x46d Product 0xc01e
    [    35.635] (--) evdev: Logitech USB-PS/2 Optical Mouse: Found 12 mouse buttons
    [    35.635] (--) evdev: Logitech USB-PS/2 Optical Mouse: Found scroll wheel(s)
    [    35.635] (--) evdev: Logitech USB-PS/2 Optical Mouse: Found relative axes
    [    35.635] (--) evdev: Logitech USB-PS/2 Optical Mouse: Found x and y relative axes
    [    35.635] (II) evdev: Logitech USB-PS/2 Optical Mouse: Configuring as mouse
    [    35.635] (II) evdev: Logitech USB-PS/2 Optical Mouse: Adding scrollwheel support
    [    35.635] (**) evdev: Logitech USB-PS/2 Optical Mouse: YAxisMapping: buttons 4 and 5
    [    35.635] (**) evdev: Logitech USB-PS/2 Optical Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [    35.635] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/input/input3/event3"
    [    35.635] (II) XINPUT: Adding extended input device "Logitech USB-PS/2 Optical Mouse" (type: MOUSE, id 9)
    [    35.635] (II) evdev: Logitech USB-PS/2 Optical Mouse: initialized for relative axes.
    [    35.635] (**) Logitech USB-PS/2 Optical Mouse: (accel) keeping acceleration scheme 1
    [    35.635] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration profile 0
    [    35.635] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration factor: 2.000
    [    35.635] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration threshold: 4
    [    35.636] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/mouse0)
    [    35.636] (II) No input driver specified, ignoring this device.
    [    35.636] (II) This device may have been added with another device file.
    [    35.636] (II) config/udev: Adding input device Eee PC WMI hotkeys (/dev/input/event4)
    [    35.636] (**) Eee PC WMI hotkeys: Applying InputClass "evdev keyboard catchall"
    [    35.636] (**) Eee PC WMI hotkeys: Applying InputClass "anaconda-keyboard"
    [    35.636] (**) Eee PC WMI hotkeys: Applying InputClass "Keyboard Defaults"
    [    35.636] (II) Using input driver 'evdev' for 'Eee PC WMI hotkeys'
    [    35.636] (**) Eee PC WMI hotkeys: always reports core events
    [    35.636] (**) evdev: Eee PC WMI hotkeys: Device: "/dev/input/event4"
    [    35.636] (--) evdev: Eee PC WMI hotkeys: Vendor 0 Product 0
    [    35.636] (--) evdev: Eee PC WMI hotkeys: Found keys
    [    35.636] (II) evdev: Eee PC WMI hotkeys: Configuring as keyboard
    [    35.636] (**) Option "config_info" "udev:/sys/devices/platform/eeepc-wmi/input/input4/event4"
    [    35.636] (II) XINPUT: Adding extended input device "Eee PC WMI hotkeys" (type: KEYBOARD, id 10)
    [    35.636] (**) Option "xkb_rules" "evdev"
    [    35.636] (**) Option "xkb_model" "evdev"
    [    35.636] (**) Option "xkb_layout" "us,pl"
    [    35.636] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
    [   431.526] (II) modesetting(0): EDID vendor "ENC", prod id 8465
    [   431.526] (II) modesetting(0): Using EDID range info for horizontal sync
    [   431.526] (II) modesetting(0): Using EDID range info for vertical refresh
    [   431.526] (II) modesetting(0): Printing DDC gathered Modelines:
    [   431.526] (II) modesetting(0): Modeline "1920x1200"x0.0  154.00  1920 1968 2000 2080  1200 1203 1209 1235 +hsync -vsync (74.0 kHz eP)
    [   431.526] (II) modesetting(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
    [   431.526] (II) modesetting(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
    [   431.526] (II) modesetting(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
    [   431.526] (II) modesetting(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
    [   431.526] (II) modesetting(0): Modeline "1600x1200"x0.0  162.00  1600 1664 1856 2160  1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
    [   431.526] (II) modesetting(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [   431.526] (II) modesetting(0): Modeline "1280x960"x0.0  108.00  1280 1376 1488 1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [   431.526] (II) modesetting(0): Modeline "1680x1050"x0.0  119.00  1680 1728 1760 1840  1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
    [   444.458] (II) modesetting(0): EDID vendor "ENC", prod id 8465
    [   444.458] (II) modesetting(0): Using hsync ranges from config file
    [   444.458] (II) modesetting(0): Using vrefresh ranges from config file
    [   444.458] (II) modesetting(0): Printing DDC gathered Modelines:
    [   444.458] (II) modesetting(0): Modeline "1920x1200"x0.0  154.00  1920 1968 2000 2080  1200 1203 1209 1235 +hsync -vsync (74.0 kHz eP)
    [   444.458] (II) modesetting(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
    [   444.458] (II) modesetting(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
    [   444.458] (II) modesetting(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
    [   444.458] (II) modesetting(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
    [   444.458] (II) modesetting(0): Modeline "1600x1200"x0.0  162.00  1600 1664 1856 2160  1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
    [   444.458] (II) modesetting(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [   444.458] (II) modesetting(0): Modeline "1280x960"x0.0  108.00  1280 1376 1488 1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [   444.458] (II) modesetting(0): Modeline "1680x1050"x0.0  119.00  1680 1728 1760 1840  1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
    and here is lsmod:
    Code:
    lsmod | grep nouveau
    nouveau               937628  3 
    i2c_algo_bit           13258  1 nouveau
    ttm                    79761  1 nouveau
    drm_kms_helper         44759  1 nouveau
    drm                   264190  5 ttm,drm_kms_helper,nouveau
    i2c_core               38354  5 drm,i2c_i801,drm_kms_helper,i2c_algo_bit,nouveau
    mxm_wmi                12866  1 nouveau
    video                  18992  2 nouveau,asus_wmi
    wmi                    18698  3 mxm_wmi,nouveau,asus_wmi
    but no nouveau:
    Code:
    rpm -qa | grep nou
    empty result.
    I did removed the nouveau with:
    Code:
    mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r)-nouveau.img
    dracut /boot/initramfs-$(uname -r).img $(uname -r)
    after the driver instalation from RPMFusion (but did not change it after nvidia drivers removal) and the kmod-nvidia instalation doeas the blaclist in grub automtically and after uninstalling nvidia the blaclist info in grub is removed.
    Ok so if brings some acceleration preventing nvidia to run TwinView (it is geyd out in nvidia-settings)
    .... how can I bring two monitors to work with nouveau?
    Last edited by Bastian123; 7th February 2013 at 04:59 PM.

  5. #5
    Join Date
    Aug 2005
    Posts
    718
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: [f18] The nvidia mystery

    As I said in my previous post, when I realised you were using the proprietary drivers, I have never actually used them and I am using a 32 bit machine.
    Clearly you do not have the nouveau userspace driver installed but the kernel space module is in the kernel package and is clearly loaded and I do not think it is supposed to be if you are using the proprietary driver which is what your Xorg.0.log implies.
    I am somewhat out of my depth here which is why I suggested you look at the link I gave. That
    is the F17 Nvidia guide under the Guides & Solutions forum.

  6. #6
    Join Date
    Mar 2011
    Posts
    26
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: [f18] The nvidia mystery

    1. Ok i Understand that if I would like to use the nvidia drivers I should look in the F17 thread? BUt it says that for questions I need to start new thread so I don't think I am allowed to ask the lack of dual monitors and nvidia there?

    2. Excuse my lack of knowledge but I don't understand the difference between the user- and the kernel- space. So how can i then install the nouveau for my userspace?

    3. Is there any graphical or console configurator for nouveau similar to eg nvidia-settings?

    4. If not can You help me with the nouveau recognition of my both monitors becouse now i have only one working (DVI) and one not working uses the D-SUB to DVI connector.
    Last edited by Bastian123; 7th February 2013 at 08:10 PM.

  7. #7
    Join Date
    Aug 2005
    Posts
    718
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: [f18] The nvidia mystery

    When you installed F18 you would have installed the package xorg-x11-drv-nouveau which contains the user space xserver module at
    /usr/lib/xorg/modules/drivers/nouveau_drv.so
    which is loaded by the xserver when it starts up. This action would appear in Xorg.0.log.
    Long before this happens, however, at boot time, and before much of the system has been started, the nouveau kernel module
    /usr/lib/modules/????/kernel/drivers/gpu/drm/nouveau/nouveau.ko
    is loaded into the kernel by dracut from a copy in the initrd. This enables mode setting to be done (and probably other things besides) while the system is being brought up. The nouveau you see in the output from lsmod is this kernel module. It is designed to work with the xserver module nouveau_drv.so.
    At some point you have installed the proprietary driver from rpmfusion. This moves a lot of things around which I do not understand and backing out of it would require care but I would guess should be done with yum remove. I do not know if the nouveau drivers are reinstated. Not having done this myself I can only refer you to the F17 Nvidia guide. Posts at the end of the thread refer to F18.
    Once you get back to nouveau, the normal controls under System Settings may do what you need or you may have to use xrandr

  8. #8
    Join Date
    Mar 2011
    Posts
    26
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: [f18] The nvidia mystery

    ok I have installed the xorg-x11-drv-nouveau.x86_64
    but under System Settings -> Monitor there is only one DVI-I-1. The grayed out sections are: DVI-D-1 and DP, whatever they are.
    Code:
    xrandr -q
    Screen 0: minimum 320 x 200, current 1920 x 1200, maximum 8192 x 8192
    DVI-I-1 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 519mm x 324mm
       1920x1200      60.0*+
       1920x1080      60.0  
       1600x1200      60.0  
       1680x1050      59.9  
       1680x945       60.0  
       1400x1050      59.9  
       1600x900       60.0  
       1280x1024      60.0  
       1440x900       59.9  
       1280x960       60.0  
       1366x768       60.0  
       1360x768       60.0  
       1280x800       59.9  
       1280x768       60.0  
       1024x768       60.0  
       1024x576       60.0  
       800x600        60.3  
       848x480        60.0  
       640x480        60.0  
       720x400        70.1  
    DVI-D-1 disconnected (normal left inverted right x axis y axis)
    DP-1 disconnected (normal left inverted right x axis y axis)
    But both monitors are connected.

    At this stage I would prefer the nouveau becouse nvidia drivers failed but hot to achieve it? What else can I do?
    Last edited by Bastian123; 7th February 2013 at 09:47 PM.

  9. #9
    Join Date
    Aug 2005
    Posts
    718
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: [f18] The nvidia mystery

    These are the three outputs on your video card:-

    DVI-I-1 Output that can carry both DVI-A, analog, or DVI-D, digital, signals
    DVI-D-1 Normal DVI only, i.e digital
    DP-1 DisplayPort

    So, the question arises, do you know that the monitors support the same standard as the connector they are plugged into?

    ---------- Post added at 04:08 PM ---------- Previous post was at 04:05 PM ----------

    DVI Digital Visual Interface

    ---------- Post added at 05:13 PM ---------- Previous post was at 04:08 PM ----------

    Try:-

    http://nouveau.freedesktop.org/wiki/MultiMonitorDesktop
    http://en.gentoo-wiki.com/wiki/X.Org...th_ZaphodHeads

  10. #10
    Join Date
    Mar 2011
    Posts
    26
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: [f18] The nvidia mystery

    I have already investigated the links you have provided.I got two monitors eizo 24'' and Dell 17''.
    Well I got two nvidia 690 in SLI. Both got 3 slots. My both monitors are pllugged to one card. So if I understand your post well only 3 slots from card that the monitors are plugged to are vidible. So the second card is not visible?

    With the nvidia drivers both monitors work so I gues they support the connector. Only the 17 '' monitor has the D-SUB_to_DVI physical connector (its just a plug with different slots on both ends).

    Can this be the case that I should experiment with connecting the 17'' to other GPU slots(6 of htem)?

  11. #11
    Join Date
    Aug 2005
    Posts
    718
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: [f18] The nvidia mystery

    It is possible that xrandr does not report cards with no monitor plugged in.
    What does lspci say and what is reported in the Xorg.0.log?
    If your adaptor is passive, your 17" monitor would only work in the DVI-I socket.
    I am assuming the 17" monitor is VGA. I am not sure if a DVI-I connector supports the EDID line, by which the video card discovers the monitor capabilities. The Xorg.0.log should reveal all.

  12. #12
    Join Date
    Mar 2011
    Posts
    26
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: [f18] The nvidia mystery

    Code:
    lspci 
    00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09)
    00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
    00:01.1 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
    00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
    00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
    00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network Connection (rev 04)
    00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
    00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
    00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
    00:1c.4 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 5 (rev c4)
    00:1c.6 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 7 (rev c4)
    00:1c.7 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 8 (rev c4)
    00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
    00:1f.0 ISA bridge: Intel Corporation Z77 Express Chipset LPC Controller (rev 04)
    00:1f.2 SATA controller: Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
    00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
    01:00.0 PCI bridge: PLX Technology, Inc. Device 8747 (rev ba)
    02:08.0 PCI bridge: PLX Technology, Inc. Device 8747 (rev ba)
    02:10.0 PCI bridge: PLX Technology, Inc. Device 8747 (rev ba)
    03:00.0 VGA compatible controller: NVIDIA Corporation GK104 [GeForce GTX 690] (rev a1)
    03:00.1 Audio device: NVIDIA Corporation GK104 HDMI Audio Controller (rev a1)
    04:00.0 3D controller: NVIDIA Corporation GK104 [GeForce GTX 690] (rev a1)
    04:00.1 Audio device: NVIDIA Corporation GK104 HDMI Audio Controller (rev a1)
    05:00.0 PCI bridge: PLX Technology, Inc. Device 8747 (rev ba)
    06:08.0 PCI bridge: PLX Technology, Inc. Device 8747 (rev ba)
    06:10.0 PCI bridge: PLX Technology, Inc. Device 8747 (rev ba)
    07:00.0 3D controller: NVIDIA Corporation GK104 [GeForce GTX 690] (rev a1)
    07:00.1 Audio device: NVIDIA Corporation GK104 HDMI Audio Controller (rev a1)
    08:00.0 VGA compatible controller: NVIDIA Corporation GK104 [GeForce GTX 690] (rev a1)
    08:00.1 Audio device: NVIDIA Corporation GK104 HDMI Audio Controller (rev a1)
    09:00.0 Audio device: Creative Labs Device 0012 (rev 01)
    0a:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller
    0b:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller                                                                                                                               
    0c:00.0 PCI bridge: PLX Technology, Inc. PEX 8608 8-lane, 8-Port PCI Express Gen 2 (5.0 GT/s) Switch (rev ba)                                                                                                        
    0d:01.0 PCI bridge: PLX Technology, Inc. PEX 8608 8-lane, 8-Port PCI Express Gen 2 (5.0 GT/s) Switch (rev ba)                                                                                                        
    0d:04.0 PCI bridge: PLX Technology, Inc. PEX 8608 8-lane, 8-Port PCI Express Gen 2 (5.0 GT/s) Switch (rev ba)
    0d:05.0 PCI bridge: PLX Technology, Inc. PEX 8608 8-lane, 8-Port PCI Express Gen 2 (5.0 GT/s) Switch (rev ba)
    0d:06.0 PCI bridge: PLX Technology, Inc. PEX 8608 8-lane, 8-Port PCI Express Gen 2 (5.0 GT/s) Switch (rev ba)
    0d:07.0 PCI bridge: PLX Technology, Inc. PEX 8608 8-lane, 8-Port PCI Express Gen 2 (5.0 GT/s) Switch (rev ba)
    0d:08.0 PCI bridge: PLX Technology, Inc. PEX 8608 8-lane, 8-Port PCI Express Gen 2 (5.0 GT/s) Switch (rev ba)
    0d:09.0 PCI bridge: PLX Technology, Inc. PEX 8608 8-lane, 8-Port PCI Express Gen 2 (5.0 GT/s) Switch (rev ba)
    10:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01)
    11:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9128 PCIe SATA 6 Gb/s RAID controller with HyperDuo (rev 11)
    12:00.0 Network controller: Atheros Communications Inc. AR5418 Wireless Network Adapter [AR5008E 802.11(a)bgn] (PCI-Express) (rev 01)
    13:00.0 Network controller: Broadcom Corporation BCM43228 802.11a/b/g/n
    14:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 09)
    And the Xorg.log in attachement becouse it seems to be to large for code.
    Attached Files Attached Files
    Last edited by Bastian123; 9th February 2013 at 05:27 PM.

  13. #13
    Join Date
    Aug 2005
    Posts
    718
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: [f18] The nvidia mystery

    I just looked up SLI. I would presume that the outputs of the slave card would be disabled so xrandr not seeing them is perhaps not surprising.
    This is a very new card so the support in nouveau may not be so good. Xorg.0.log on my machine reports it supports:-
    Code:
    [    47.976] 	RIVA TNT        (NV04)
    [    47.976] 	RIVA TNT2       (NV05)
    [    47.977] 	GeForce 256     (NV10)
    [    47.977] 	GeForce 2       (NV11, NV15)
    [    47.977] 	GeForce 4MX     (NV17, NV18)
    [    47.977] 	GeForce 3       (NV20)
    [    47.980] 	GeForce 4Ti     (NV25, NV28)
    [    47.980] 	GeForce FX      (NV3x)
    [    47.980] 	GeForce 6       (NV4x)
    [    47.981] 	GeForce 7       (G7x)
    [    47.981] 	GeForce 8       (G8x)
    [    47.981] 	GeForce GTX 200 (NVA0)
    [    47.984] 	GeForce GTX 400 (NVC0)

  14. #14
    Join Date
    Mar 2011
    Posts
    26
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: [f18] The nvidia mystery

    Quote Originally Posted by kldixon
    I just looked up SLI. I would presume that the outputs of the slave card would be disabled so xrandr not seeing them is perhaps not surprising.
    Both monitors are connected to one card.
    Quote Originally Posted by kldixon
    If your adaptor is passive, your 17" monitor would only work in the DVI-I socket.
    So are you saying that I should move it to the second card DVI-I slot ?
    Quote Originally Posted by kldixon
    I am assuming the 17" monitor is VGA.
    Yes
    Quote Originally Posted by kldixon
    I am not sure if a DVI-I connector supports the EDID line, by which the video card discovers the monitor capabilities.
    The kmod-nvidia drivers saw the monitor at present configuration so the technically it is possible.

  15. #15
    Join Date
    Jan 2011
    Posts
    152
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: [f18] The nvidia mystery

    I get a little lost in reading this thread but I would simply say that I have a laptop on which I run the nvidia proprietary driver and I have no problem driving an external monitor in addition to the laptop screen.

    On my laptop (lenovo) I have to go into BIOS and enable "discrete" graphics instead of "integrated" graphics. I followed the install directions for nvidia (use akmod - it's the way to go) and the external monitor basically just works. The whole process is really quite easy.

Page 1 of 2 12 LastLast

Similar Threads

  1. The mystery of <<<
    By sluge in forum Using Fedora
    Replies: 2
    Last Post: 28th August 2012, 03:00 PM
  2. It's a mystery to me ...
    By Dan in forum Hardware
    Replies: 12
    Last Post: 27th April 2012, 07:02 PM

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
  •