No HDMI detection

Please execute `apport-collect 1914670` to attach the system logs.

mind also share does the hdmi works with any other os, to exclude HW issue

Hi Ian,

We sometime get compatibility issue form different external device and even the HDMI cord(e.g. LP: #1890772).

To check if it's a external device issue, could you please help to do some test:
1. Will BIOS shows on external HDMI monitor if you plugged HDMI before booting up your machine?
2. If lower resolution make you HDMI monitor light up?
   - I saw you make it light up after manually xrander command, how if you change the resolution up and down? (I'm wondering if it related to LP: #1890772)

Hi thanks for replying back!

To answer your questions:

1. 'apport-collect 1914670' --> command not found

2. If I boot up into windows, the HDMI port, but not if boot up with Linux.

3. I've tried other HDMI cables and other external monitors. Nothing works.

4. BIOS does not show up on external HDMI monitor if plugged in before booting up machine.

5. Lowering resolution or changing it any other resolution does not display HDMI.

Edit for point 2: If i boot up with windows, the HDMI port works*, but does not* work with linux

Hi Ian, could you please also provide us the report of what #1 needed?

And if convenient, please also provide the tarball created by `sosreport` and `oem-getlogs`.

I'm curious about the content of your `lspci -vvvnnk`

Sorry I'm not sure what #1 is referring to. Is 'apport-collect 1914670', and 'sosreport', and 'oem-getlogs' suppose to be terminal commands? If so all of them are returning 'command not found'. This is my firt time on this site, so I'm not sure what those are referring to.

`lspci -vvvnnk` output:
0000:00:00.0 Host bridge [0600]: Intel Corporation Device [8086:9a14] (rev 01)
 Subsystem: Dell Device [1028:0a01]
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0
 Capabilities: <access denied>

0000:00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 DeviceName: Onboard - Video
 Subsystem: Dell Device [1028:0a01]
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0
 Interrupt: pin A routed to IRQ 163
 Region 0: Memory at 601e000000 (64-bit, non-prefetchable) [size=16M]
 Region 2: Memory at 4000000000 (64-bit, prefetchable) [size=256M]
 Region 4: I/O ports at 3000 [size=64]
 Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
 Capabilities: <access denied>
 Kernel driver in use: i915
 Kernel modules: i915

0000:00:04.0 Signal processing controller [1180]: Intel Corporation Device [8086:9a03] (rev 01)
 Subsystem: Dell Device [1028:0a01]
 Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Interrupt: pin A routed to IRQ 16
 Region 0: Memory at 601f240000 (64-bit, non-prefetchable) [size=128K]
 Capabilities: <access denied>
 Kernel driver in use: proc_thermal
 Kernel modules: processor_thermal_device

0000:00:06.0 System peripheral [0880]: Intel Corporation Device [8086:09ab]
 Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-

0000:00:07.0 PCI bridge [0604]: Intel Corporation Device [8086:9a23] (rev 01) (prog-if 00 [Normal decode])
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0
 Interrupt: pin A routed to IRQ 123
 Bus: primary=00, secondary=01, subordinate=2a, sec-latency=0
 I/O behind bridge: 00004000-00004fff [size=4K]
 Memory behind bridge: 74000000-801fffff [size=194M]
 Prefetchable memory behind bridge: 0000006000000000-000000601bffffff [size=448M]
 Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
 BridgeCtl: Parity- SERR+ NoISA- VGA- VGA16- MAbort- >Reset- FastB2B-
  PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
 Capabilities: <access denied>
 Kernel driver in use: pcieport

0000:00:0a.0 Signal processing controller [1180]: Int...

apport information

apport information

apport information

`sudo apt install apport` should install the tool.

Update: I ran `sudo apt-get install apport` and ran `apport-collect 1914670`, then pressed the 'Send Report' option. Hopefully the report has been sent to you

the certification page for target platform for reference : https://certification.ubuntu.com/hardware/202007-28054

The certification was tested on an older BIOS version (Dell 1.0.0), whereas I bought the machine and BIOS 1.1.3 was installed, and now I have the latest 1.1.7. For both, HDMI still not showing up.

(Also I have the sosreport generated, but I'm getting errors when trying to upload the tar file as an attachment to this site

Hello,

Can you try the following debug command when you plug the HDMI monitor?

1. check if udev event emit from kernel
$ udevadm monitor -s drm
2. check if the connector change status
$ cat /sys/class/drm/card0-*/status
3. try to dump the display info
# cat /sys/kernel/debug/dri/0/i915_display_info
4. If the driver thinks no display attached
upload /sys/kernel/debug/dri/0/i915_vbt to this bug, I can check if vbios is revised, since the BIOS version is different from what we certified.

The driver won't change state, if it can't retrieve EDID properly.
Would like to confirm if kernel did aware a output is attached.

Thanks,

1. "udevadm monitor -s drm" -->
```
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
```

2. "cat /sys/class/drm/card0-*/status" -->
```
disconnected
connected
disconnected
```

3. "cat /sys/kernel/debug/dri/0/i915_display_info" -->
```
CRTC info
---------
[CRTC:91:pipe A]:
 uapi: enable=no, active=no, mode="": 0 0 0 0 0 0 0 0 0 0 0x0 0x0
 [PLANE:31:plane 1A]: type=PRI
  uapi: fb=0,n/a,0x0, src=1920.000000x1080.000000+0.000000+682.000000, dst=1920x1080+0+0, rotation=0 (0x00000001)
 [PLANE:39:plane 2A]: type=OVL
  uapi: fb=0,n/a,0x0, src=0.000000x0.000000+0.000000+0.000000, dst=0x0+0+0, rotation=0 (0x00000001)
 [PLANE:47:plane 3A]: type=OVL
  uapi: fb=0,n/a,0x0, src=0.000000x0.000000+0.000000+0.000000, dst=0x0+0+0, rotation=0 (0x00000001)
 [PLANE:55:plane 4A]: type=OVL
  uapi: fb=0,n/a,0x0, src=0.000000x0.000000+0.000000+0.000000, dst=0x0+0+0, rotation=0 (0x00000001)
 [PLANE:63:plane 5A]: type=OVL
  uapi: fb=0,n/a,0x0, src=0.000000x0.000000+0.000000+0.000000, dst=0x0+0+0, rotation=0 (0x00000001)
 [PLANE:71:plane 6A]: type=OVL
  uapi: fb=0,n/a,0x0, src=0.000000x0.000000+0.000000+0.000000, dst=0x0+0+0, rotation=0 (0x00000001)
 [PLANE:79:plane 7A]: type=OVL
  uapi: fb=0,n/a,0x0, src=0.000000x0.000000+0.000000+0.000000, dst=0x0+0+0, rotation=0 (0x00000001)
 [PLANE:87:cursor A]: type=CUR
  uapi: fb=0,n/a,0x0, src=0.000000x0.000000+0.000000+0.000000, dst=0x0+0+0, rotation=0 (0x00000001)
 underrun reporting: cpu=yes pch=yes
[CRTC:152:pipe B]:
 uapi: enable=yes, active=yes, mode="": 0 141380 1920 1968 2000 2142 1080 1083 1089 1100 0x0 0x9
 hw: active=yes, adjusted_mode="1920x1080": 60 141380 1920 1968 2000 2142 1080 1083 1089 1100 0x48 0x9
 pipe src size=1920x1080, dither=yes, bpp=18
 num_scalers=2, scaler_users=0 scaler_id=-1, scalers[0]: use=no, mode=0, scalers[1]: use=no, mode=0
 [ENCODER:275:DDI A]: connectors:
  [CONNECTOR:276:eDP-1]
 [PLANE:92:plane 1B]: type=PRI
  uapi: fb=277,XR24 little-endian (0x34325258),1920x1080, src=1920.000000x1080.000000+0.000000+0.000000, dst=1920x1080+0+0, rotation=0 (0x00000001)
  hw: fb=277,XR24 little-endian (0x34325258),1920x1080, visible=yes, src=1920.000000x1080.000000+0.000000+0.000000, dst=1920x1080+0+0, rotation=0 (0x00000001)
 [PLANE:100:plane 2B]: type=OVL
  uapi: fb=0,n/a,0x0, src=0.000000x0.000000+0.000000+0.000000, dst=0x0+0+0, rotation=0 (0x00000001)
 [PLANE:108:plane 3B]: type=OVL
  uapi: fb=0,n/a,0x0, src=0.000000x0.000000+0.000000+0.000000, dst=0x0+0+0, rotation=0 (0x00000001)
 [PLANE:116:plane 4B]: type=OVL
  uapi: fb=0,n/a,0x0, src=0.000000x0.000000+0.000000+0.000000, dst=0x0+0+0, rotation=0 (0x00000001)
 [PLANE:124:plane 5B]: type=OVL
  uapi: fb=0,n/a,0x0, src=0.000000x0.000000+0.000000+0.000000, dst=0x0+0+0, rotation=0 (0x00000001)
 [PLANE:132:plane 6B]: type=OVL
  uapi: fb=0,n/a,0x0, src=0.000000x0.000000+0.000000+0.000000, dst=0x0+0+0, rotation=0 (0x00000001)
 [PLANE:140:plane 7B]: type=OVL
  uapi: fb=0,n/a,0x0, src=0.000000x0.000000+0.000000+0.000000, dst=0x0+0+0, rotation=0 (0x00000001)
 [PLANE:148:cursor B]: type=CUR
  uapi: fb=0,n/a,0x0, src=0.000000x0.000000+0.000000+0.000000, dst=0x0+0+0, rotation=0 (0x0000...

4. /sys/kernel/debug/dri/0/i915_display_info -->

Sorry, correct #4 -->

Upload vbt decode of #19 for record. I'll check BIOS 1.0.0's vbt to see if it has any modification.

Hello,

I try to reproduce your issue locally, but I found my graphic card pci id is different from yours.
Do you mind to share more hardware info?

$ cat /sys/class/dmi/id/product_sku
$ cat /sys/class/dmi/id/product_name

I can check if we have the same model as yours locally.

Thanks,

1. "cat /sys/class/dmi/id/product_sku" --> 0A01
2. "cat /sys/class/dmi/id/product_name" --> Inspiron 5402

Hi just checking in, are there any follow ups to this issue?

Hello,

Would you please try this kernel to see if it works for you?
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/

Based on your experiment, it works when there is a type-C dongle in between, which might be the ddc bus and ddi port mapping issue. I'd like check if Intel development tree contains a correct mapping for you.

Sorry that I am now on CNY vacation, I'll see if I can find the same model as yours, then get back to you ASAP.

Thanks,

I'm not sure how to update the kernel with the given url. I've done some method of updating my kernel manually and then was unable to boot. Fortunately I was able to recover, but now I'm scared to update my kernel without knowing 100% what I'm doing.

Hello,

to install kernel in https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/
You need to download

linux-headers-5.11.0-051100drmtip20210217-generic_5.11.0-051100drmtip20210217.202102170205_amd64.deb
linux-headers-5.11.0-051100drmtip20210217_5.11.0-051100drmtip20210217.202102170205_all.deb
linux-image-unsigned-5.11.0-051100drmtip20210217-generic_5.11.0-051100drmtip20210217.202102170205_amd64.deb
linux-modules-5.11.0-051100drmtip20210217-generic_5.11.0-051100drmtip20210217.202102170205_amd64.deb

put them to the same folder, under the folder execute:
$ sudo dpkg -i *.deb
$ sudo reboot

The system will reboot, after reboot, please use $ uname -r to check kernel version.
It should be like 5.11.0-xxxxx, then try to use HDMI again.

I'm having trouble booting with the 5.11 kernel. After manually selecting to boot into 5.11 from the advanced boot options page, I'm getting 'invalid signature' error. From the link you've provided, I've downloaded the following packages:

1)

amd64/linux-headers-5.11.0-051100drmtip20210223-generic_5.11.0-051100drmtip20210223.202102230209_amd64.deb

2)

amd64/linux-headers-5.11.0-051100drmtip20210223_5.11.0-051100drmtip20210223.202102230209_all.deb

3)

amd64/linux-image-unsigned-5.11.0-051100drmtip20210223-generic_5.11.0-051100drmtip20210223.202102230209_amd64.deb

4)

amd64/linux-modules-5.11.0-051100drmtip20210223-generic_5.11.0-051100drmtip20210223.202102230209_amd64.deb

Then proceeded to put them under the same folder and ran "$ sudo dpkg -i *.deb"
The problems I'm seeing now is the default boot version at the very top of the grub boot loader is still 5.8, and unable to boot when manually selecting 5.11 (which is located much lower with a weird name like 5.11.0-051100drmtip20210223

reply #47

Hello,

it is because the secure boot. would you please disable secure boot in your bios?

Thanks for the tip, I've disabled secure boot, restarted into 5.11 but still no HDMI connection.

$ uname -r
5.11.0-051100drmtip20210223-generic

Based on your result, the hardware also can't work with Intel's development branch, then the Ubuntu's kernel doesn't work for you as expect.

I have verified on two certified hardwares.

https://certification.canonical.com/hardware/202007-28055/
https://certification.canonical.com/hardware/202006-27982/

The HDMI output works both on oem kernel 5.6 and 5.10.
It seems I can't reproduce your problem, but your hardware config is a bit different from what I have in hand.

Could you file a bug to Dell customer support? They will provide me the hardware if they expect the hardware can work with open platform.

Thanks,

I've already tried reaching out to Dell's customer support (https://community.intel.com/t5/Processors/No-HDMI-output-using-Linux-Mint/m-p/1244240#M48905), but they replied with:

"Please be aware that Intel does not provide direct downloads and technical support for Linux drivers. The Intel Graphics Linux driver is primarily supported through the original equipment manufacturer (OEM), the Linux distribution vendor, or by the Intel Open Source Technology Center at https://01.org/linuxgraphics."

Ok I've sent a message at https://01.org/ asking for more help or directions stating you need more hardware information!

Ian

20.04.2 just released, have you ever tested with stock Ubuntu image?