search

kfechter / LegionY530Ubuntu

Guide for installing Ubuntu on the Legion Y530
GNU General Public License v3.0
178 stars 31 forks source link

HDMI, Ubuntu 18.04 & Y530 #50

Closed pinheirof closed 4 years ago

pinheirof commented 5 years ago

Hello folks,

Still struggling to have my HDMI recognized and be able to connect my Y530 to an external monitor.

Any idea? Have been reading about, but cannot find a solution yet.

18.04.02 Kernel 5.0.0-050000-generic Gnome 3.28.2 nvidia-driver-415

andreypaa commented 5 years ago

Follow this instruction I can connect monitor very well, but use only fresh LinuxMint

pinheirof commented 5 years ago

Which instruction? The one from @kfechter? Well, I did. Actually, except minor, but annoying issues, such as some fkeys not working, Ubuntu 18.04 is running fine. The only big issue that I'm facing right now concerns the HDMI.

Additionally, not sure if the USB-C is working. That's the output I get from lsusb:

-lenovo-y530:~$ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 5986:2113 Acer, Inc Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

kfechter commented 5 years ago

running Kernel 5.0 may be causing your issues.

kfechter commented 5 years ago

The type C port is probably part of the 3.0 root hub. I can get lsusb output on the stock kernel once I make a new live stick. Currently running Windows cause I needed it.

pinheirof commented 5 years ago

running Kernel 5.0 may be causing your issues.

Not sure about that. I've tried kernel 4.15, 4.18, 4.20.... and now 5.0. Had no issue with them. The one problem that remains stable seams to be the HDMI issue.

pinheirof commented 5 years ago

The type C port is probably part of the 3.0 root hub. I can get lsusb output on the stock kernel once I make a new live stick. Currently running Windows cause I needed it.

Got it. Will try soon. But I think you're right about it.

kfechter commented 5 years ago

It's weird that so many people are having issues with the HDMI, because other than one hiccup that was fixed with a reboot, all of my video outputs work when using nvidia-prime in nvidia mode. It's annoying because without reproduction, I don't know where to fix it.

pinheirof commented 5 years ago

It's weird that so many people are having issues with the HDMI, because other than one hiccup that was fixed with a reboot, all of my video outputs work when using nvidia-prime in nvidia mode. It's annoying because without reproduction, I don't know where to fix it.

Yes, I know. Since I'm a newbie, I was wondering which kind of output/log should I share with the users community that could held them to have a better picture of my case... Since I've followed most the online instructions, I feel that it may be something quite silly...

Anyway, thanks the help and to provide to all of us the step-by-step instruction on github.

kfechter commented 5 years ago

dmesg is generally a good one.

dmesg | grep -i nvidia dmesg | grep -i vga dmesg | grep -i xorg

maybe one of these will give us meaningful data.

Did you install the kernel before or after installing the nvidia driver? cause that can break things too.

pinheirof commented 5 years ago

dmesg is generally a good one.

dmesg | grep -i nvidia dmesg | grep -i vga dmesg | grep -i xorg

maybe one of these will give us meaningful data.

Did you install the kernel before or after installing the nvidia driver? cause that can break things too.

I installed the kernel after.. but then I've ran "sudo apt install --reinstall nvidia-driver-415 nvidia-prime" everytime I update the kernel..

About the commands, here is output -- nothing appears after -i nvidia and -i xorg

flavio@flavio-lenovo-y530:~$ dmesg | grep -i nvidia flavio@flavio-lenovo-y530:~$ dmesg | grep -i vga [ 0.348760] pci 0000:00:02.0: vgaarb: setting as boot VGA device [ 0.348760] pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none [ 0.348760] pci 0000:01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=none,locks=none [ 0.348760] pci 0000:00:02.0: vgaarb: no bridge control possible [ 0.348760] pci 0000:01:00.0: vgaarb: bridge control possible [ 0.348760] vgaarb: loaded [ 1.186107] fb0: EFI VGA frame buffer device [ 2.638644] fb0: switching to inteldrmfb from EFI VGA [ 2.638714] [drm] Replacing VGA console driver [ 2.642275] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem flavio@flavio-lenovo-y530:~$ dmesg | grep -i xorg

kfechter commented 5 years ago

yeah that doesn't give me anything :/

try just dmesg

there will be a whole lot more but maybe something is there.

and ok, the reinstall should trigger the module rebuild.

pinheirof commented 5 years ago

The only mention to HDMI was the following:

[ 0.171997] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)

[ 2.788092] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input11 [ 2.788157] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input12 [ 2.788251] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input13 [ 2.788369] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input14 [ 2.788419] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input15

And bellow, the entries are errors. But must say that I don't understand the meaning.

[ 0.233006] ACPI BIOS Error (bug): Failure creating [_SB.PCI0.XHC.RHUB.TPLD], AE_ALREADY_EXISTS (20181213/dswload2-324) [ 0.233016] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20181213/psobject-221) [ 0.233020] ACPI: Skipping parse of AML opcode: Method (0x0014) [ 0.233076] ACPI BIOS Error (bug): Could not resolve [_SB.PCI0.XHC.RHUB.HS01], AE_NOT_FOUND (20181213/dswload2-160) [ 0.233082] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20181213/psobject-221) [ 0.233085] ACPI: Skipping parse of AML opcode: Scope (0x0010) [ 0.233115] ACPI BIOS Error (bug): Could not resolve [_SB.PCI0.XHC.RHUB.HS02], AE_NOT_FOUND (20181213/dswload2-160) [ 0.233120] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20181213/psobject-221) [ 0.233123] ACPI: Skipping parse of AML opcode: Scope (0x0010) [ 0.233152] ACPI BIOS Error (bug): Could not resolve [_SB.PCI0.XHC.RHUB.HS03], AE_NOT_FOUND (20181213/dswload2-160) [ 0.233157] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20181213/psobject-221) [ 0.233160] ACPI: Skipping parse of AML opcode: Scope (0x0010) [ 0.233188] ACPI BIOS Error (bug): Could not resolve [_SB.PCI0.XHC.RHUB.HS04], AE_NOT_FOUND (20181213/dswload2-160) [ 0.233193] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20181213/psobject-221) [ 0.233196] ACPI: Skipping parse of AML opcode: Scope (0x0010) [ 0.233224] ACPI BIOS Error (bug): Could not resolve [_SB.PCI0.XHC.RHUB.HS05], AE_NOT_FOUND (20181213/dswload2-160) [ 0.233229] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20181213/psobject-221) [ 0.233232] ACPI: Skipping parse of AML opcode: Scope (0x0010) [ 0.233260] ACPI BIOS Error (bug): Could not resolve [_SB.PCI0.XHC.RHUB.HS06], AE_NOT_FOUND (20181213/dswload2-160) [ 0.233266] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20181213/psobject-221) [ 0.233269] ACPI: Skipping parse of AML opcode: Scope (0x0010) [ 0.233297] ACPI BIOS Error (bug): Could not resolve [_SB.PCI0.XHC.RHUB.HS07], AE_NOT_FOUND (20181213/dswload2-160) [ 0.233302] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20181213/psobject-221) [ 0.233306] ACPI: Skipping parse of AML opcode: Scope (0x0010) [ 0.233334] ACPI BIOS Error (bug): Could not resolve [_SB.PCI0.XHC.RHUB.HS08], AE_NOT_FOUND (20181213/dswload2-160) [ 0.233339] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20181213/psobject-221) [ 0.233343] ACPI: Skipping parse of AML opcode: Scope (0x0010) [ 0.233371] ACPI BIOS Error (bug): Could not resolve [_SB.PCI0.XHC.RHUB.HS09], AE_NOT_FOUND (20181213/dswload2-160) [ 0.233376] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20181213/psobject-221) [ 0.233379] ACPI: Skipping parse of AML opcode: Scope (0x0010) [ 0.233408] ACPI BIOS Error (bug): Could not resolve [_SB.PCI0.XHC.RHUB.HS10], AE_NOT_FOUND (20181213/dswload2-160) [ 0.233413] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20181213/psobject-221) [ 0.233416] ACPI: Skipping parse of AML opcode: Scope (0x0010) [ 0.233444] ACPI BIOS Error (bug): Could not resolve [_SB.PCI0.XHC.RHUB.HS11], AE_NOT_FOUND (20181213/dswload2-160) [ 0.233449] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20181213/psobject-221) [ 0.233453] ACPI: Skipping parse of AML opcode: Scope (0x0010) [ 0.233481] ACPI BIOS Error (bug): Could not resolve [_SB.PCI0.XHC.RHUB.HS12], AE_NOT_FOUND (20181213/dswload2-160) [ 0.233486] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20181213/psobject-221) [ 0.233489] ACPI: Skipping parse of AML opcode: Scope (0x0010) [ 0.233517] ACPI BIOS Error (bug): Could not resolve [_SB.PCI0.XHC.RHUB.HS13], AE_NOT_FOUND (20181213/dswload2-160) [ 0.233523] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20181213/psobject-221) [ 0.233526] ACPI: Skipping parse of AML opcode: Scope (0x0010) [ 0.233555] ACPI BIOS Error (bug): Failure creating [_SB.PCI0.XHC.RHUB.HS14._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324) [ 0.233561] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20181213/psobject-221) [ 0.233565] ACPI: Skipping parse of AML opcode: Method (0x0014) [ 0.233567] ACPI BIOS Error (bug): Failure creating [_SB.PCI0.XHC.RHUB.HS14._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324) [ 0.233572] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20181213/psobject-221) [ 0.233575] ACPI: Skipping parse of AML opcode: Method (0x0014) [ 0.235528] ACPI BIOS Error (bug): Could not resolve [_SB.PCI0.XHC.RHUB.USR1], AE_NOT_FOUND (20181213/dswload2-160) [ 0.235534] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20181213/psobject-221) [ 0.235537] ACPI: Skipping parse of AML opcode: Scope (0x0010) [ 0.235540] ACPI BIOS Error (bug): Could not resolve [_SB.PCI0.XHC.RHUB.USR2], AE_NOT_FOUND (20181213/dswload2-160) [ 0.235545] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20181213/psobject-221) [ 0.235548] ACPI: Skipping parse of AML opcode: Scope (0x0010) [ 0.235580] ACPI BIOS Error (bug): Could not resolve [_SB.PCI0.XHC.RHUB.SS01], AE_NOT_FOUND (20181213/dswload2-160) [ 0.235585] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20181213/psobject-221) [ 0.235589] ACPI: Skipping parse of AML opcode: Scope (0x0010) [ 0.235618] ACPI BIOS Error (bug): Could not resolve [_SB.PCI0.XHC.RHUB.SS02], AE_NOT_FOUND (20181213/dswload2-160) [ 0.235623] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20181213/psobject-221) [ 0.235626] ACPI: Skipping parse of AML opcode: Scope (0x0010) [ 0.235655] ACPI BIOS Error (bug): Could not resolve [_SB.PCI0.XHC.RHUB.SS03], AE_NOT_FOUND (20181213/dswload2-160) [ 0.235660] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20181213/psobject-221) [ 0.235663] ACPI: Skipping parse of AML opcode: Scope (0x0010) [ 0.235692] ACPI BIOS Error (bug): Could not resolve [_SB.PCI0.XHC.RHUB.SS04], AE_NOT_FOUND (20181213/dswload2-160) [ 0.235697] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20181213/psobject-221) [ 0.235700] ACPI: Skipping parse of AML opcode: Scope (0x0010) [ 0.235729] ACPI BIOS Error (bug): Could not resolve [_SB.PCI0.XHC.RHUB.SS05], AE_NOT_FOUND (20181213/dswload2-160) [ 0.235734] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20181213/psobject-221) [ 0.235737] ACPI: Skipping parse of AML opcode: Scope (0x0010) [ 0.235765] ACPI BIOS Error (bug): Could not resolve [_SB.PCI0.XHC.RHUB.SS06], AE_NOT_FOUND (20181213/dswload2-160) [ 0.235771] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20181213/psobject-221) [ 0.235774] ACPI: Skipping parse of AML opcode: Scope (0x0010) [ 0.235802] ACPI BIOS Error (bug): Could not resolve [_SB.PCI0.XHC.RHUB.SS07], AE_NOT_FOUND (20181213/dswload2-160) [ 0.235807] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20181213/psobject-221) [ 0.235810] ACPI: Skipping parse of AML opcode: Scope (0x0010) [ 0.235838] ACPI BIOS Error (bug): Could not resolve [_SB.PCI0.XHC.RHUB.SS08], AE_NOT_FOUND (20181213/dswload2-160) [ 0.235843] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20181213/psobject-221) [ 0.235847] ACPI: Skipping parse of AML opcode: Scope (0x0010) [ 0.235875] ACPI BIOS Error (bug): Could not resolve [_SB.PCI0.XHC.RHUB.SS09], AE_NOT_FOUND (20181213/dswload2-160) [ 0.235880] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20181213/psobject-221) [ 0.235883] ACPI: Skipping parse of AML opcode: Scope (0x0010) [ 0.235913] ACPI BIOS Error (bug): Could not resolve [_SB.PCI0.XHC.RHUB.SS10], AE_NOT_FOUND (20181213/dswload2-160) [ 0.235919] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20181213/psobject-221) [ 0.235922] ACPI: Skipping parse of AML opcode: Scope (0x0010) [ 0.236879] ACPI BIOS Error (bug): Could not resolve [_SB.PCI0.I2C2.TPD0], AE_NOT_FOUND (20181213/dswload2-160) [ 0.236886] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20181213/psobject-221) [ 0.236889] ACPI: Skipping parse of AML opcode: Scope (0x0010) [ 0.236923] ACPI BIOS Error (bug): Could not resolve [_SB.PCI0.I2C3.TPL1], AE_NOT_FOUND (20181213/dswload2-160) [ 0.236928] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20181213/psobject-221) [ 0.236932] ACPI: Skipping parse of AML opcode: Scope (0x0010) [ 0.240268] ACPI BIOS Error (bug): Failure creating [_SB.PCI0.PEG0.PEGP._ON], AE_ALREADY_EXISTS (20181213/dswload2-324) [ 0.240281] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20181213/psobject-221) [ 0.240284] ACPI: Skipping parse of AML opcode: Method (0x0014) [ 0.240287] ACPI BIOS Error (bug): Failure creating [_SB.PCI0.PEG0.PEGP._OFF], AE_ALREADY_EXISTS (20181213/dswload2-324) [ 0.240292] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20181213/psobject-221)

This last part was just in red, but no indication of errors.

[ 5.250320] iwlwifi 0000:07:00.0: BIOS contains WGDS but no WRDS [ 1319.460805] iwlwifi 0000:07:00.0: BIOS contains WGDS but no WRDS

kfechter commented 5 years ago

yeah I get the WGDS but no WRDS thing. that's just a wifi driver thing, and I don't think it affects anything adversely.

none of the other errors appear to be for graphics devices.

m-kotsiuruba commented 5 years ago

Hello folks,

Still struggling to have my HDMI recognized and be able to connect my Y530 to an external monitor.

Any idea? Have been reading about, but cannot find a solution yet.

18.04.02 Kernel 5.0.0-050000-generic Gnome 3.28.2 nvidia-driver-415

I fixed HDMI on my Y530 by changing "options nvidia-drm modeset" : https://devtalk.nvidia.com/default/topic/1044770/hdmi-output-missing-in-xrandr-command-and-external-monitor-does-not-work/

kfechter commented 5 years ago

@Kotsyuruba If that fix works for the people having issues I will add it to the guide.

pinheirof commented 5 years ago

Hello folks, Still struggling to have my HDMI recognized and be able to connect my Y530 to an external monitor. Any idea? Have been reading about, but cannot find a solution yet. 18.04.02 Kernel 5.0.0-050000-generic Gnome 3.28.2 nvidia-driver-415

I fixed HDMI on my Y530 by changing "options nvidia-drm modeset" : https://devtalk.nvidia.com/default/topic/1044770/hdmi-output-missing-in-xrandr-command-and-external-monitor-does-not-work/

Didn't work. I remove and reinstall the nvidia driver 415.... nothing. Made combinations with other kernel.. nothing. That's the result I get from $ xrandr

Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm

m-kotsiuruba commented 5 years ago

Hello folks, Still struggling to have my HDMI recognized and be able to connect my Y530 to an external monitor. Any idea? Have been reading about, but cannot find a solution yet. 18.04.02 Kernel 5.0.0-050000-generic Gnome 3.28.2 nvidia-driver-415

I fixed HDMI on my Y530 by changing "options nvidia-drm modeset" : https://devtalk.nvidia.com/default/topic/1044770/hdmi-output-missing-in-xrandr-command-and-external-monitor-does-not-work/

Didn't work. I remove and reinstall the nvidia driver 415.... nothing. Made combinations with other kernel.. nothing. That's the result I get from $ xrandr

Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm

This work only with "prime-select nvidia". External video out conected to nvidia. P.S. I use Ubuntu 18.04 with default kernel (Linux Legion 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb 7 14:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux )

xrandr: Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767 DP-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) HDMI-0 connected primary 1920x1080+1920+0 (normal left inverted right x axis y axis) 527mm x 296mm 1920x1080 60.00+ 59.94 50.00 60.00 50.04
1680x1050 59.95
1440x900 59.89
1280x1024 75.02 60.02
1280x960 60.00
1280x720 60.00 59.94 50.00
1024x768 75.03 70.07 60.00
800x600 75.00 72.19 60.32 56.25
720x576 50.00
720x480 59.94
640x480 75.00 72.81 59.94 59.93
eDP-1-1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm 1920x1080 60.03 + 60.01 59.97 59.96 59.93
1680x1050 59.95 59.88
1600x1024 60.17
1400x1050 59.98
1600x900 59.99 59.94 59.95 59.82
1280x1024 60.02
1440x900 59.89
1400x900 59.96 59.88
1280x960 60.00
1440x810 60.00 59.97
1368x768 59.88 59.85
1360x768 59.80 59.96
1280x800 59.99 59.97 59.81 59.91
1152x864 60.00
1280x720 60.00 59.99 59.86 59.74
1024x768 60.04 60.00
960x720 60.00
928x696 60.05
896x672 60.01
1024x576 59.95 59.96 59.90 59.82
960x600 59.93 60.00
960x540 59.96 59.99 59.63 59.82
800x600 60.00 60.32 56.25
840x525 60.01 59.88
864x486 59.92 59.57
800x512 60.17
700x525 59.98
800x450 59.95 59.82
640x512 60.02
720x450 59.89
700x450 59.96 59.88
640x480 60.00 59.94
720x405 59.51 58.99
684x384 59.88 59.85
680x384 59.80 59.96
640x400 59.88 59.98
576x432 60.06
640x360 59.86 59.83 59.84 59.32
512x384 60.00
512x288 60.00 59.92
480x270 59.63 59.82
400x300 60.32 56.34
432x243 59.92 59.57
320x240 60.05
360x202 59.51 59.13
320x180 59.84 59.32
1680x1050 (0x49) 146.250MHz -HSync +VSync h: width 1680 start 1784 end 1960 total 2240 skew 0 clock 65.29KHz v: height 1050 start 1053 end 1059 total 1089 clock 59.95Hz 1280x1024 (0x51) 108.000MHz +HSync +VSync h: width 1280 start 1328 end 1440 total 1688 skew 0 clock 63.98KHz v: height 1024 start 1025 end 1028 total 1066 clock 60.02Hz 1440x900 (0x52) 106.500MHz -HSync +VSync h: width 1440 start 1520 end 1672 total 1904 skew 0 clock 55.93KHz v: height 900 start 903 end 909 total 934 clock 59.89Hz 1280x960 (0x55) 108.000MHz +HSync +VSync h: width 1280 start 1376 end 1488 total 1800 skew 0 clock 60.00KHz v: height 960 start 961 end 964 total 1000 clock 60.00Hz 1024x768 (0x66) 65.000MHz -HSync -VSync h: width 1024 start 1048 end 1184 total 1344 skew 0 clock 48.36KHz v: height 768 start 771 end 777 total 806 clock 60.00Hz 800x600 (0x75) 40.000MHz +HSync +VSync h: width 800 start 840 end 968 total 1056 skew 0 clock 37.88KHz v: height 600 start 601 end 605 total 628 clock 60.32Hz 800x600 (0x76) 36.000MHz +HSync +VSync h: width 800 start 824 end 896 total 1024 skew 0 clock 35.16KHz v: height 600 start 601 end 603 total 625 clock 56.25Hz 640x480 (0x84) 25.175MHz -HSync -VSync h: width 640 start 656 end 752 total 800 skew 0 clock 31.47KHz v: height 480 start 490 end 492 total 525 clock 59.94Hz

m-kotsiuruba commented 5 years ago

@pinheirof " prime-select query"?

pinheirof commented 5 years ago

prime-select query

flavio@flavio-lenovo-y530:~$ prime-select query nvidia

Any ideas, @Kotsyuruba ? Any log/command I should you to share with you guys?

I'm using dual boot with Windows, and HDMI works perfectly. I'm thinking about reinstalling ubuntu.

Oh, and one important piece of information: after I got the Y530, I changed its hard drive for a SSD which was in use in my old (but not that old) laptop. With the exception of minor problems, that were easily solved following the instructions provided here by @kfechter .... and as far as I'm concern, everything seems fine... except the HDMI...

kfechter commented 5 years ago

could you post a screenshot of the nvidia control panel?

m-kotsiuruba commented 5 years ago

First time - i solve my problem by Ubuntu reinstall. But later, after some ubuntu updates, I lost hdmi again. And fix it by modeset.

m-kotsiuruba commented 5 years ago

screenshot from 2019-03-07 20-10-54 I use HDMI on work only

pinheirof commented 5 years ago

could you post a screenshot of the nvidia control panel?

Here it is:

image

image

image

pinheirof commented 5 years ago

First time - i solve my problem by Ubuntu reinstall. But later, after some ubuntu updates, I lost hdmi again. And fix it by modeset.

@Kotsyuruba which kernel version are you using?

m-kotsiuruba commented 5 years ago

First time - i solve my problem by Ubuntu reinstall. But later, after some ubuntu updates, I lost hdmi again. And fix it by modeset.

@Kotsyuruba which kernel version are you using?

Linux version 4.18.0-16-generic (buildd@lcy01-amd64-006) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #17~18.04.1-Ubuntu SMP Tue Feb 12 13:35:51 UTC 2019

k3marek commented 5 years ago

Hi, after whole day struggling with broken external monitor connection I finally managed to launch it with dual boot with windows 10 and secure boot enabled. My config: kernel 4.18.0-16-generic ubuntu 18.10 nvidia 418 External monitor with HDMI and Display Port

What I did:

  1. Leave Secure boot enabled
  2. Install Ubuntu with option "Install third party software for graphics (...)" Set secureboot password
  3. Continue with kfetcher's instructions to 8. "Install Nvidia drivers and Nvidia-prime packages." What I did firstly was to install as it was written with given commands, Then I've set the secure bios password, rebooted and clicked boot in the MOK management. Now I think that was the problem, because I didn't enrolled the key in MOK. So the drivers wasn't working. Then I purged nvidia drivers and used the Ubuntu's Additional drivers to install the drivers. It prompted again for the secureboot password. Then I rebooted and this time I've enrolled the key in the MOK management with secureboot pass.

  4. Set the options nvidia-drm modeset=0 $ grep modeset /lib/modprobe.d/* /lib/modprobe.d/nvidia-kms.conf

    $ sudo update-initramfs -u $ sudo reboot

  5. Reboot and enjoy Cosmic Cuttlefish on external monitor :D

This is my third ubuntu installation and the first that has properly configured nvidia drivers... I've never enrolled the key in MOK managment before, and so the drivers wasn't loading properly.

ocio28 commented 5 years ago

Hello folks, Still struggling to have my HDMI recognized and be able to connect my Y530 to an external monitor. Any idea? Have been reading about, but cannot find a solution yet. 18.04.02 Kernel 5.0.0-050000-generic Gnome 3.28.2 nvidia-driver-415

I fixed HDMI on my Y530 by changing "options nvidia-drm modeset" : https://devtalk.nvidia.com/default/topic/1044770/hdmi-output-missing-in-xrandr-command-and-external-monitor-does-not-work/

work for me! thanks!

kfechter commented 5 years ago

the graphics stack and nvidia-prime seem to be way improved in 19.04, and the 19.04 setup will automatically configure the graphics stack if selected.

Until 18.04.3 comes out (and I can test to make sure everything works as it does on 19.04), I would recommend using 19.04 if you want everything working with minimal fuss

midjean commented 5 years ago

Hello !

I had the same issue with my lenovo legion y540, couldn't get the hdmi working and it was not listed with command "xrandr -q". I followed instructions from https://devtalk.nvidia.com/default/topic/1044770/hdmi-output-missing-in-xrandr-command-and-external-monitor-does-not-work/ by changing options nvidia-drm modeset to 0 and everything is working perfectly now ! Hmdi port is listed under xrandr and I can control my display settings with "Fn+F7" keyboard combo. Thanks a lot !

Ubuntu 19.04 Kernel 5.0.0-23-generic #24-Ubuntu SMP nvidia-driver-430

lenarddome commented 5 years ago

Hi, Everyone!

I had the same problem with the HDMI output, although I followed the install instructions.

My setup:

Lenovo Legion y530 Ubuntu 19.04 (no windows) Kernel 5.0.0-23-generic #24-Ubuntu SMP nvidia-driver-430

I had no nvidia-kms.conf file to begin with, so the solutions provided by @midjean and @Kotsyuruba were out of the question (tried to create the file manually to no avail). As I figured it out later, the problem was similar to this: stackoverflow link

I managed to get it working by doing the following things in that order:

  1. Reinstalling the driver: sudo apt-get install --reinstall.
  2. Disabling Secureboot in Bios.

Best

kfechter commented 5 years ago

Secureboot shouldn't cause issues, but then again it shouldn't do a lot of things. I'll remove the "Leave secureboot on" from the guide with my 18.04.3 guide changes. I generally turn it off anyway.

lei-fp-robotics commented 5 years ago

Hey Guys With this project I now managed to get my screen running twice. Thank you for that. You might find this information useful: I bought my Lenovo Y530 back in April and was able to make the screen working with the guide that said to install nvidia-driver-415 (which has since been removed https://github.com/kfechter/LegionY530Ubuntu/tree/18.04.2-Install-Guide). My screen then worked beautifully until August 6th. I assume that my kernel was updated to 5.0 on August 5th and after the next reboot the screen did no longer work.

I then removed nvidia-driver-415 and ran

sudo apt update && sudo apt dist-upgrade sudo ubuntu-drivers autoinstall

which installed ndvidia-driver-430. Screen still would not work. However I also was able to get it running by then changing the modeset to 0 and running.

sudo update-initramfs -u

Thank you so much for this guide.

utajum commented 5 years ago

Always check valve's list of requirements https://github.com/ValveSoftware/Proton/wiki/Requirements

They update it constantly for the LTS version

nerycordova commented 4 years ago

Hello folks, Still struggling to have my HDMI recognized and be able to connect my Y530 to an external monitor. Any idea? Have been reading about, but cannot find a solution yet. 18.04.02 Kernel 5.0.0-050000-generic Gnome 3.28.2 nvidia-driver-415

I fixed HDMI on my Y530 by changing "options nvidia-drm modeset" : https://devtalk.nvidia.com/default/topic/1044770/hdmi-output-missing-in-xrandr-command-and-external-monitor-does-not-work/

This worked for me too. Meaning:

  1. Set the following in /lib/modprobe.d/nvidia-kms.conf : options nvidia-drm modeset=0
  2. sudo update-initramfs -u
  3. reboot

My setup is as follows:

Kernel 5.0.0-27-generic Gnome 3.32.1 Nvidia driver 418.56 Lenovo Legion Y730

guigs commented 4 years ago

I have Y540 on Ubuntu 19.04 and external monitor was working fine for a week and then it stopped working, apparently with no reason.

I've tried to reinstall nvidia drivers with no success.

Then I found this thread and I confirm the following solution also worked for me:

Set options nvidia-drm modeset=0 in /lib/modprobe.d/nvidia-kms.conf : sudo update-initramfs -u reboot

The only issue I have (that I already had when it was working in the beginning) is that the brightness keys (Fn+F5/F6) are not working. When I press them, an icon with the blue bar is shown on the screen, but it actually not change the brightness. But I can still set the brightness with xrandr --output DP-2 --brightness 0.5.

Without the options nvidia-drm modeset=0 configuration, the brightness keys do work, but I can't connect external monitor.

qvanphong commented 4 years ago

Sorry for a late party, I was getting the same problem, and all solution above doesn't work for me.

So I decide to work around and find a solution, then I found some helpful information from: https://forums.lenovo.com/t5/Gaming-Laptops-Knowledge-Base/Installing-Ubuntu-on-the-Legion-Y530/tac-p/4457972/highlight/true#M213 https://askubuntu.com/questions/1004461/is-gdm3-preferred-to-lightdm?rq=1

Problem: gdm3 kills the nvidia card from displaying to external monitors when your use modeset=1. Bug still exists in Ubuntu 19.04. Speculation is that gdm3 sees the driver in modesetting operation, and decides wayland must be in use, and there is no way to get it to behave otherwise. It must be a hard bug to fix. "

So I decide switch to lightdm and nothing change. Then i decide to uninstall and reinstall different nvidia driver version (i tried 390, 435 before) with a little bit different install method by using nvidia PPA, then install driver from software & update's addition driver, i choose nvdia driver version 430.

then use set options nvidia-drm modeset=0 in /lib/modprobe.d/nvidia-kms.conf : sudo update-initramfs -u reboot. Then it works.

So, in short:

kfechter commented 4 years ago

That is an interesting gdm bug. Are there any adverse side effects to switching the desktop manager?

That guide on the lenovo forums is slightly out of date, I haven't had a chance to update it because I've been focusing on the guide here on github. The guide on github is far easier to update.

guigs commented 4 years ago

After 2 weeks it stops working for me again (probably a kernel upgrade).

I had to remove blacklist-nvidia.conf file from /lib/modprobe.d, then run sudo update-initramfs -u and reboot to make it work again.

dergachovda commented 4 years ago

HDMI started working for my only after disabling secure boot!

qvanphong commented 4 years ago

A little update:

I would recommend you try ubuntu-drivers devices to see which driver version is recommended for you PC before doing my steps above. I didn''t check if hdmi working on v440 (nvidia driver that is recommended in my case), i update about hdmi status after school.

RobertRozic commented 4 years ago

A little update:

  • So i just reinstall ubuntu after take back my laptop from warranty services. I followed my steps above but this time i getting random annoy freezing. And solved by reinstall with recommended driver version.

I would recommend you try ubuntu-drivers devices to see which driver version is recommended for you PC before doing my steps above. I didn''t check if hdmi working on v440 (nvidia driver that is recommended in my case), i update about hdmi status after school.

I updated to 440 Nvidia drivers usign 5.3.15 kernel and HDMI is working ( Ubuntu 19.04 ) I tried to install to latest 5.4.2 kernel but failed because dkms is broken there.

stale[bot] commented 4 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

pinheirof commented 4 years ago

Kernel 5.6.7 working fine.

On Sat, Apr 25, 2020 at 10:52 PM stale[bot] notifications@github.com wrote:

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/kfechter/LegionY530Ubuntu/issues/50#issuecomment-619466359, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC7QMEWSKH7A364GF5BMPTTROOHXDANCNFSM4G3V6CLQ .

-- Flávio Pinheiro E: pinheiro.f@ufabc.edu.br +pinheiro.f@ufabc.edu.br E: pinheiro.f@gmail.com +pinheiro.f@gmail.com P: +55 11 95792-2357

qvanphong commented 4 years ago

The latest kernel on Ubuntu 20.04 look like working good enough right now.

Anyway, if you make a fresh install 20.04, Ubuntu will automatically install nvidia-driver-440 (right now), but the HDMI might not working, even if you try these above tricks.

To fix this, you need to downgrade to 435 and then upgrade to 440, the HDMI will work perfectly. sudo apt-get install nvidia-driver-435 reboot #reboot after it done Then the HDMI will work, if you want to update to latest, just go ahead sudo apt-get install nvidia-driver-440 reboot #reboot after it done

stale[bot] commented 4 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] commented 4 years ago

This issue has been automatically closed due to inactivity. Feel free to open a new issue if you are still having issues