• \[Solved\]Troubleshooting Video with "optimus" based laptop


    Clean install of Antergos test image “antergos-2014.03.23-x86_64.iso” selected KDE. Upon reboot cleaned up my GRUB 2.0 menu to use new UUIDs. Antegros boots to black screen. It stayed that way for a few minutes I think as I ignored it to refresh my coffee. But all of a sudden a very low resoluion greeter screen showed up and I was able to log into KDE. After a few more minutes the screen saver kicked in screen went black and I was not able to get it to turn back on. Tried FN + Brightness key too…

    CRTL-ALT-F2 did wake the screen up and brought me back to the greeter screen.

    Hardware: Lenovo Y510P - core i7 based, 16GB RAM, 1TB drive. I know the video configuration for this will be difficult (other threads here). It actually has 3 GPUs:

    *Integrated Graphics is the 4600HD
    *Dual discrete Nvidia GT755M in SLI.

    Using the default video drivers… have not installed anything else yet.

      
    lspci | grep VGA:  
    01:00.0 VGA compatible controller: NVIDIA Corporation GK107M [GeForce GT 755M] (rev al)
    

    It doesn’t list anything else which is interesting. I was assuming it would list at least 2 maybe 3 items. Before I wander too far off in the Wiki’s I’d appeaciate some feedback if this is expected.

    The BIOS does not offer any configuration about enable/disable or even selecting a default between integrated or discrete. Boot logs attached.

  • Clean install of Antergos test image “antergos-2014.03.23-x86_64.iso” selected KDE. Upon reboot cleaned up my GRUB 2.0 menu to use new UUIDs. Antegros boots to black screen. It stayed that way for a few minutes I think as I ignored it to refresh my coffee. But all of a sudden a very low resoluion greeter screen showed up and I was able to log into KDE. After a few more minutes the screen saver kicked in screen went black and I was not able to get it to turn back on. Tried FN + Brightness key too…

    CRTL-ALT-F2 did wake the screen up and brought me back to the greeter screen.

    Hardware: Lenovo Y510P - core i7 based, 16GB RAM, 1TB drive. I know the video configuration for this will be difficult (other threads here). It actually has 3 GPUs:

    *Integrated Graphics is the 4600HD
    *Dual discrete Nvidia GT755M in SLI.

    Using the default video drivers… have not installed anything else yet.

      
    lspci | grep VGA:  
    01:00.0 VGA compatible controller: NVIDIA Corporation GK107M [GeForce GT 755M] (rev al)
    

    It doesn’t list anything else which is interesting. I was assuming it would list at least 2 maybe 3 items. Before I wander too far off in the Wiki’s I’d appeaciate some feedback if this is expected.

    The BIOS does not offer any configuration about enable/disable or even selecting a default between integrated or discrete. Boot logs attached.

  • Need some help understanding this… I installed only the nouveau driver “xf86-video-nouveau”. Rebooted… black screen.

    On a hunch I try these 3 kernel parameters: nomodeset i915.modeset=0 nouveau.modeset=0

    And KDE boots right up into 1080P resoultion… no delay. I’m glad I made some progress, but I don’t understand it.

  • Hi,

    Adding >nomodeset i915.modeset=0 nouveau.modeset=0
    disables kms, so you’re working now with the VESA driver… which I think is not what you want.

    You can see it in your xorg.log (that you had kms disabled and VESA was used). Please, remove those parameters and try booting again and post here the xorg.log file.

    Cheers!

  • @“karasu”:vduh37of said:

    Please, remove those parameters and try booting again and post here the xorg.log file.[/quote:vduh37of]
    Here you go… thanks for looking.

  • Hi,

    Don’t know why, but still no KMS available:

    [ 91.649] (EE) [drm] KMS not enabled"
    

    and what’s worst, is that X is crashing:

    [ 94.450] (EE) Segmentation fault at address 0xa0
    

    You should focus in having KMS.

    I’ll google a bit and get back to you because I’ve never setup a dual system like yours. Maybe somebody else with more experience can jump in and help us.

    Cheers!

    EDIT:

    “With recent nouveau, KMS is on by default, unless you disable it with modeset=0 option.”

    Are you sure you didn’t run Antergos with this option on?

  • @“karasu”:6k5dg918 said:

    I’ll google a bit and get back to you because I’ve never setup a dual system like yours. Maybe somebody else with more experience can jump in and help us.[/quote:6k5dg918]
    The help is appreciated.

    “With recent nouveau, KMS is on by default, unless you disable it with modeset=0 option.”

    Are you sure you didn’t run Antergos with this option on?

    I just doublechecked the GRUB config file. no kernel options are being passed. One of the first few lines of the xorg.log file shows the kernel command line:

    [ 91.646] Kernel command line: BOOT\_IMAGE=/vmlinuz-linux root=UUID=b7470748-d864-4451-a291-c73e162a4889 rw resume=UUID=baa97ca8-209b-4dee-ade9-8d407da59d46
    

    I just deleted the Xorg.0.log file, and rebooted to make sure it wasn’t something old.

    It still shows “[drm] KMS not enabled” and stll has the segment fault.

    The /etc/nouveau.conf only has a single line “options nouveau modeset=1”.

    The mkinitcpio.conf does not have any modules listed yet.

  • Hi,

    Just curious, have you tested the closed driver nvidia? I think it doesn’t need KMS.

  • The next logical thing to try I think is adding
    [code:2tbwzzeq]MODULES=“nouveau”[/code:2tbwzzeq] To /etc/mkinitcpio.conf and running “mkinitcpio -p linux”.

    After reboot… it kind of hangs at the “udev” first line. I don’t get the rest of the screen full of [OK] xxxxx messages and then it goes to a black screen. The xorg.log file still has reference to “KMS not enabled” and still get a segment fault at the end.

  • @“karasu”:14xanbzu said:

    Just curious, have you tested the closed driver nvidia? I think it doesn’t need KMS.[/quote:14xanbzu]
    just before this clean install (this morning) I tried removing the nouveau drivers and installed the latest closed drivers. It would also go to black screen, but the CPU fan started to scream and then the laptop would power off in about 15 seconds on its own. So that is when I decided to start this clean install and start this thread. I didn’t bother reviewing log files.

  • Hi,

    The thing I was finding the most strange about this was the fact that the system did not give any indication of having an intel graphics chip in the logs. I finally found out why. Lenovo has disabled the intel chip in the firmware and there is currently no way to get around that. So as far as the OS is concerned, your system does not have an intel chip. No need to install intel drivers or add any i915 modules/parameters. The built-in switching done by PRIME is designed to switch between intel and nvidia AFAICT, so in this case I think it is confused that there are two nvidia cards. I think you should try using Bumblebee which I believe will allow you to set one card as primary and the other as discreet. I don’t have any real experience with nvidia cards though so I’m only giving you my best guess. Hope it helps!

  • @“lots.0.logs”:5bfsildc said:

    Hi,

    The thing I was finding the most strange about this was the fact that the system did not give any indication of having an intel graphics chip in the logs. I finally found out why. Lenovo has disabled the intel chip in the firmware and there is currently no way to get around that. So as far as the OS is concerned, your system does not have an intel chip. No need to install intel drivers or add any i915 modules/parameters. The built-in switching done by PRIME is designed to switch between intel and nvidia AFAICT, so in this case I think it is confused that there are two nvidia cards. I think you should try using Bumblebee which I believe will allow you to set one card as primary and the other as discreet. I don’t have any real experience with nvidia cards though so I’m only giving you my best guess. Hope it helps![/quote:5bfsildc]

    Where did you find a reference that it was disabled? I haven’t come across that yet.

    Before I can focus on bumblebee, I have to get the basics working. Right now I can’t get anything but the VESA drivers working or are you suggesting I should switch to nvidia drivers?

  • When I look at this:

     lspci | grep VGA  
    01:00.0 VGA compatible controller: NVIDIA Corporation GK107M [GeForce GT 755M] (rev a1)
    

    I assume I can use that 01:00.0 BusID as a reference to the journal logs, which I find:

      
    Mar 25 06:18:07 lin-y510p kernel: nouveau [ DEVICE][0000:01:00.0] BOOT0 : 0x0e70d0a2  
    Mar 25 06:18:07 lin-y510p kernel: nouveau [ DEVICE][0000:01:00.0] Chipset: GK107 (NVE7)  
    Mar 25 06:18:07 lin-y510p kernel: nouveau [ DEVICE][0000:01:00.0] Family : NVE0  
    Mar 25 06:18:07 lin-y510p kernel: nouveau [ VBIOS][0000:01:00.0] checking PRAMIN for image...  
    Mar 25 06:18:07 lin-y510p kernel: nouveau [ VBIOS][0000:01:00.0] ... signature not found  
    Mar 25 06:18:07 lin-y510p kernel: nouveau [ VBIOS][0000:01:00.0] checking PROM for image...  
    Mar 25 06:18:07 lin-y510p kernel: nouveau [ VBIOS][0000:01:00.0] ... signature not found  
    Mar 25 06:18:07 lin-y510p kernel: nouveau [ VBIOS][0000:01:00.0] checking ACPI for image...  
    Mar 25 06:18:07 lin-y510p kernel: nouveau [ VBIOS][0000:01:00.0] ... signature not found  
    Mar 25 06:18:07 lin-y510p kernel: nouveau [ VBIOS][0000:01:00.0] checking PCIROM for image...  
    Mar 25 06:18:07 lin-y510p kernel: nouveau 0000:01:00.0: Invalid ROM contents  
    Mar 25 06:18:07 lin-y510p kernel: nouveau [ VBIOS][0000:01:00.0] ... appears to be valid  
    Mar 25 06:18:07 lin-y510p kernel: nouveau [ VBIOS][0000:01:00.0] using image from PCIROM  
    Mar 25 06:18:07 lin-y510p kernel: nouveau [ VBIOS][0000:01:00.0] BIT signature found  
    Mar 25 06:18:07 lin-y510p kernel: nouveau [ VBIOS][0000:01:00.0] version 80.07.a8.00.2e  
    Mar 25 06:18:07 lin-y510p kernel: nouveau E[ VBIOS][0000:01:00.0] 0x9115[ ]: unknown opcode 0xff  
    Mar 25 06:18:07 lin-y510p kernel: nouveau E[ DEVINIT][0000:01:00.0] init failed, -22  
    Mar 25 06:18:07 lin-y510p kernel: nouveau E[ DRM] failed to create 0x80000080, -22  
    Mar 25 06:18:07 lin-y510p kernel: nouveau: probe of 0000:01:00.0 failed with error -22  
    
    

    The GK107 (NVE7) is the correct code name for this GPU.

    While not listed by lspci, I suspect this is the second nvidia GPU:

    Mar 25 06:18:07 lin-y510p kernel: nouveau 0000:07:00.0: enabling device (0006 -\> 0007)  
    Mar 25 06:18:07 lin-y510p kernel: nouveau [ DEVICE][0000:07:00.0] BOOT0 : 0x0e70d0a2  
    Mar 25 06:18:07 lin-y510p kernel: nouveau [ DEVICE][0000:07:00.0] Chipset: GK107 (NVE7)  
    Mar 25 06:18:07 lin-y510p kernel: nouveau [ DEVICE][0000:07:00.0] Family : NVE0  
    Mar 25 06:18:07 lin-y510p kernel: nouveau [ VBIOS][0000:07:00.0] checking PRAMIN for image...  
    Mar 25 06:18:07 lin-y510p kernel: nouveau [ VBIOS][0000:07:00.0] ... signature not found  
    Mar 25 06:18:07 lin-y510p kernel: nouveau [ VBIOS][0000:07:00.0] checking PROM for image...  
    Mar 25 06:18:08 lin-y510p kernel: nouveau [ VBIOS][0000:07:00.0] ... appears to be valid  
    Mar 25 06:18:08 lin-y510p kernel: nouveau [ VBIOS][0000:07:00.0] using image from PROM  
    Mar 25 06:18:08 lin-y510p kernel: nouveau [ VBIOS][0000:07:00.0] BIT signature found  
    Mar 25 06:18:08 lin-y510p kernel: nouveau [ VBIOS][0000:07:00.0] version 80.07.a8.00.32  
    Mar 25 06:18:08 lin-y510p kernel: nouveau [ DEVINIT][0000:07:00.0] adaptor not initialised  
    Mar 25 06:18:08 lin-y510p kernel: nouveau [ VBIOS][0000:07:00.0] running init tables  
    Mar 25 06:18:08 lin-y510p kernel: nouveau 0000:07:00.0: irq 49 for MSI/MSI-X  
    Mar 25 06:18:08 lin-y510p kernel: nouveau [ PMC][0000:07:00.0] MSI interrupts enabled  
    Mar 25 06:18:08 lin-y510p kernel: nouveau [ PFB][0000:07:00.0] RAM type: GDDR5  
    Mar 25 06:18:08 lin-y510p kernel: nouveau [ PFB][0000:07:00.0] RAM size: 2048 MiB  
    Mar 25 06:18:08 lin-y510p kernel: nouveau [ PFB][0000:07:00.0] ZCOMP: 0 tags  
    Mar 25 06:18:08 lin-y510p kernel: nouveau [ VOLT][0000:07:00.0] GPU voltage: 600000uv  
    Mar 25 06:18:08 lin-y510p kernel: nouveau [ PTHERM][0000:07:00.0] FAN control: none / external  
    Mar 25 06:18:08 lin-y510p kernel: nouveau [ PTHERM][0000:07:00.0] fan management: automatic  
    Mar 25 06:18:08 lin-y510p kernel: nouveau [ PTHERM][0000:07:00.0] internal sensor: yes  
    Mar 25 06:18:08 lin-y510p kernel: nouveau [ CLK][0000:07:00.0] 07: core 405 MHz memory 405 MHz   
    Mar 25 06:18:08 lin-y510p kernel: nouveau [ CLK][0000:07:00.0] 0a: core 405-1097 MHz memory 800 MHz   
    Mar 25 06:18:08 lin-y510p kernel: nouveau [ CLK][0000:07:00.0] 0f: core 405-1097 MHz memory 2700 MHz   
    Mar 25 06:18:08 lin-y510p kernel: nouveau [ CLK][0000:07:00.0] --: core 405 MHz memory 405 MHz   
    Mar 25 06:18:08 lin-y510p kernel: nouveau [ DRM] VRAM: 2048 MiB  
    Mar 25 06:18:08 lin-y510p kernel: nouveau [ DRM] GART: 1048576 MiB  
    Mar 25 06:18:08 lin-y510p kernel: nouveau [ DRM] TMDS table version 2.0  
    Mar 25 06:18:08 lin-y510p kernel: nouveau [ DRM] DCB version 4.0  
    Mar 25 06:18:08 lin-y510p kernel: nouveau [ DRM] DCB outp 01: 08011f82 00020010  
    Mar 25 06:18:08 lin-y510p kernel: nouveau [ DRM] DCB outp 02: 02044f00 00000000  
    Mar 25 06:18:08 lin-y510p kernel: nouveau [ DRM] DCB conn 01: 01000161  
    Mar 25 06:18:08 lin-y510p kernel: nouveau [ DRM] DCB conn 04: 00000400  
    Mar 25 06:18:08 lin-y510p kernel: nouveau [ DRM] ACPI backlight interface available, not registering our own  
    Mar 25 06:18:08 lin-y510p kernel: nouveau [ DRM] MM: using COPY for buffer copies  
    Mar 25 06:18:08 lin-y510p kernel: [drm] Initialized nouveau 1.1.1 20120801 for 0000:07:00.0 on minor 0
    

    But then even that leads to an error:

      
    Mar 25 06:18:09 lin-y510p kernel: nouveau E[ PBUS][0000:07:00.0] MMIO read of 0x00000000 FAULT at 0x300000 [ IBUS ]  
    Mar 25 06:18:09 lin-y510p kernel: nouveau E[ PIBUS][0000:07:00.0] GPC0: 0x419eb4 0xbadf1000 (0x3800820c)  
    Mar 25 06:18:09 lin-y510p kernel: nouveau E[ PBUS][0000:07:00.0] MMIO write of 0xbadf1000 FAULT at 0x419eb4 [ IBUS ]  
    Mar 25 06:18:11 lin-y510p kernel: nouveau E[ PGRAPH][0000:07:00.0] HUB\_INIT timed out  
    Mar 25 06:18:11 lin-y510p kernel: nouveau E[ PGRAPH][0000:07:00.0] 409000 - done 0x00000244  
    Mar 25 06:18:11 lin-y510p kernel: nouveau E[ PGRAPH][0000:07:00.0] 409000 - stat 0x00000000 0x00000000 0x00000000 0x00000000  
    Mar 25 06:18:11 lin-y510p kernel: nouveau E[ PGRAPH][0000:07:00.0] 409000 - stat 0x00000000 0x00000000 0x00000002 0x00000009  
    Mar 25 06:18:11 lin-y510p kernel: nouveau E[ PGRAPH][0000:07:00.0] 502000 - done 0x00000300  
    Mar 25 06:18:11 lin-y510p kernel: nouveau E[ PGRAPH][0000:07:00.0] 502000 - stat 0x00000000 0x00000000 0x00000000 0x00000000  
    Mar 25 06:18:11 lin-y510p kernel: nouveau E[ PGRAPH][0000:07:00.0] 502000 - stat 0x00000000 0x00000000 0x00000000 0x00000000  
    Mar 25 06:18:11 lin-y510p kernel: nouveau E[ PGRAPH][0000:07:00.0] init failed, -16  
    
    
  • I cant find the link to where I saw the info about the intel card being disabled in the firmware, it’s as though I completely made it up…but I swear I seen it! lol

    This may seem like a silly question, but do you have xf86-video-modesetting installed?

    Also from what I am reading you will want to disable secure boot but don’t enable legacy mode (in the BIOS)…

    Another update…from the little information I have found on google it seems that no one has successfully configured this system to work without disabling KMS (so they’re using VESA), The 3.14 kernel will be available soon so perhaps things will improve. If it were me I would probably give the closed source driver’s a go with bumblebee…(i’m stubborn when it comes to these things hehe)

    Cheers!

  • @“lots.0.logs”:fxovivnh said:

    I cant find the link to where I saw the info about the intel card being disabled in the firmware, it’s as though I completely made it up…but I swear I seen it! lol
    I believe you. I was starting to wonder myself because nothing in the documentation or sales literature says anything about an Intel graphics card or that it is an optimus based laptop. I only learned about it it from other Linux fourms and assumed they know what they were talking about.

    @“lots.0.logs”:fxovivnh said:

    This may seem like a silly question, but do you have xf86-video-modesetting installed?[/quote:fxovivnh]
    Not a silly question. I don’t have it installed. I was on the Arch repository site for it trying to figure out if I needed it but was unable to figure that out. I didn’t see it listed in any of the threads or HOW-TOs. It’s on my list of things to try, but I wanted to wait to see what was suggested. Since you bring it up, should it be installed?

    @“lots.0.logs”:fxovivnh said:

    Also from what I am reading you will want to disable secure boot but don’t enable legacy mode (in the BIOS)…[/quote:fxovivnh]
    Yes, I have secure boot disabled, but EUFI enabled. Legacy boot was only enabled for Antergos installation as the ISO does not work with my EUFI. After installing it, I manually added to my existing GRUB 2.

    @“lots.0.logs”:fxovivnh said:

    Another update…from the little information I have found on google it seems that no one has successfully configured this system to work without disabling KMS (so they’re using VESA), The 3.14 kernel will be available soon so perhaps things will improve. If it were me I would probably give the closed source driver’s a go with bumblebee…(i’m stubborn when it comes to these things hehe)[/quote:fxovivnh]

    I have Windows 8.1, Ubuntu 14.04, and Antergos tripple boot configuraion. The Ubuntu needed “nomodeset” for initial installation, then installed closed source drivers and everything “just worked”. But that’s not what I want to use. I used the “nomodeset” to get Antergos installed as well. Then tried closed source driver, upon reboot I had a black screen, CPU fan screaming and it powers off on its own in about 8 seconds. So then I tried the open source drivers. Still get black screen, but do not get the CPU fan screaming or power off. Seemed like it was closer to working.

    In looking at the ubuntu Xorg.log I do see it also says “(EE) [drm] KMS not enabled” and the closed source driver detects the card

      
    > > > > [ 9.623] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20130102)  
    > > > > [ 9.624] (II) NVIDIA(0): NVIDIA GPU GeForce GT 755M (GK107) at PCI:1:0:0 (GPU-0)  
    > > > > [ 9.624] (--) NVIDIA(0): Memory: 2097152 kBytes  
    > > > > [ 9.624] (--) NVIDIA(0): VideoBIOS: 80.07.a8.00.2e
    

    And unloads the VESA driver:

    [ 9.873] (II) UnloadModule: "vesa"  
    > > > > [ 9.873] (II) Unloading vesa
    

    And finds the second GPU:

    [ 10.465] (II) NVIDIA(GPU-1): Found DRM driver nvidia-drm (20130102)  
    > > > > [ 10.470] (II) NVIDIA(GPU-1): NVIDIA GPU GeForce GT 755M (GK107) at PCI:7:0:0 (GPU-1)  
    > > > > [ 10.470] (--) NVIDIA(GPU-1): Memory: 2097152 kBytes  
    > > > > [ 10.470] (--) NVIDIA(GPU-1): VideoBIOS: 80.07.a8.00.32  
    > > > > ...  
    > > > > [ 10.619] (II) NVIDIA(0): [DRI2] Setup complete  
    > > > > [ 10.619] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia  
    > > > > [ 10.619] (--) RandR disabled  
    > > > > 
    

    So it sounds like I should try removing the open source drivers and try the closed source driver and put some logs here.

  • Before you do that, install the modesetting package that I mentioned and grab those logs.

    Cheers!

  • Installed… see attached log file.

  • @“lots.0.logs”:6b4h24pn said:

    Lenovo has disabled the intel chip in the firmware and there is currently no way to get around that. So as far as the OS is concerned, your system does not have an intel chip. [/quote:6b4h24pn]
    I found out what happens. When dual NVIDIA GPUs are installed then the OPTIMUS technology (Intel Graphics) is disabled. If I disable SLI and remove the 2nd GPU from the UltraBay then the Intel Graphics is enabled and OPTIMUS technology can be used.

  • I’ve switch to the NVIDIA close source driver using the following:

    $ sudo /bin/sed -i 's/options nouveau modeset=1/\#options nouveau modeset=1/' /etc/modprobe.d/modprobe.conf  
    $ sudo /bin/sed -i 's/MODULES="nouveau"/\#MODULES="nouveau"/' /etc/mkinitcpio.conf  
    $ sudo /usr/bin/pacman -Rdds --noconfirm nouveau-dri xf86-video-nouveau mesa-libgl  
    $ sudo /usr/bin/pacman -S --noconfirm nvidia nvidia-utils  
    $ sudo /sbin/mkinitcpio -p linux
    

    Still not reaching the greeter. Logs attached.

  • Hi,

    Grab the journal from the previous 2 boots so I can look for what’s causing this:

     (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA GPU at PCI:1:0:0\. Please  
    [ 76.937] (EE) NVIDIA(GPU-0): check your system's kernel log for additional error  
    [ 76.937] (EE) NVIDIA(GPU-0): messages and refer to Chapter 8: Common Problems in the  
    [ 76.937] (EE) NVIDIA(GPU-0): README for additional information.  
    [ 76.937] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA graphics device!  
    [ 76.937] (EE) NVIDIA(0): Failing initialization of X screen 0  
    [ 76.937] (II) UnloadModule: "nvidia"  
    [ 76.937] (II) UnloadSubModule: "wfb"  
    [ 76.937] (II) UnloadSubModule: "fb"  
    [ 76.937] (EE) Screen(s) found, but none have a usable configuration.  
    [ 76.937] (EE)   
    Fatal server error:  
    [ 76.937] (EE) no screens found(EE)   
    [ 76.937] (EE)   
    Please consult the The X.Org Foundation support   
    at http://wiki.x.org  
    for help.   
    [ 76.937] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.  
    [ 76.937] (EE)   
    [ 76.943] (EE) Server terminated with error (1). Closing log file.
    
Posts 34Views 3967
Log in to reply