Samsung Smart TV "crashes" NVidia driver, can't detect TV any more?
Hi folks, I have a 43" Samsung Smart TV that I am using as a monitor with a ThinkPad P51, running Fedora 35 Workstation Edition. This laptop has a "NVIDIA Corporation GM206GLM [Quadro M2200 Mobile] / Mesa Intel® HD Graphics 630 (KBL GT2)" graphics subsystem. As far as I can make out, I am using the latest NVidia driver (495.46). What is unfortunately happening, is that if my laptop goes to sleep, the TV sees that the source disappears, and "tries to look for the laptop", repeatedly. This ends up waking up the laptop (sometimes), until the TV eventually gives up and turns itself off. The problem is then that the laptop no longer detects that the TV is connected to the HDMI port, and I have to reboot to allow the laptop to detect the screen again. Xrandr does not detect the display if run manually, and the Settings app Displays page also doesn't show the TV. This is a rather difficult thing to google, I have had zero results in my searching. I also tried looking for any logs that would indicate what went wrong, but I found nothing in the syslog, etc. Can anyone give me pointers on how I can start debugging this? I am fairly technical, so can certainly follow instructions. I'm guessing I need to enable verbose logging for the driver so it can report when new displays are connected or disconnected, as well as any actions around those events? Thanks Rogan ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Unable to Add Printer in Fedora 35
I had problems adding my Pantum printer, because Fedora was trying to use ipps:// URL's rather than the advertised ipp://. This resulted in the IP stack on the printer crashing (yay for crappy vendor firmware!), and any subsequent operations on the printer failing until it was manually rebooted. I ended up manually modifying the URLs to ipp:// and everything worked perfectly after that. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Samsung Smart TV "crashes" NVidia driver, can't detect TV any more?
I don't believe that this is a TV issue (other than its behaviour on input loss triggering the resulting behaviour on the laptop). This is because if I reboot the laptop, the TV is quite happy to recognise it again, while disconnecting and reconnecting the HDMI cable does not have the same effect. I can perhaps look at interposing a breakout board on the HDMI cable, and using a logic analyser on certain pins (i.e. those that carry the DDC protocol used to enumerate the display modes supported by the connected display). That might allow me to see that the laptop is or isn't recognising that the display is connected and performing the DDC interrogation. But I imagine this would also be possible by enabling verbose logging too, which would probably be a lot easier in the short term. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Samsung Smart TV "crashes" NVidia driver, can't detect TV any more?
Wow! That is awesome! Hopefully this will give me some pointers in the right direction (if it doesn't "just work"(tm)). From reading the script at /usr/bin/nvidia-sleep.sh, it seems that when it happens, I can try to change to a console VT, suspend and awaken the driver, then change back, and hopefully it will revive the display! Thanks! ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Samsung Smart TV "crashes" NVidia driver, can't detect TV any more?
That is excellent! Thanks for the pointer to this. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Samsung Smart TV "crashes" NVidia driver, can't detect TV any more?
If I don't find a software solution, I'm going with a smart power switch that will power the TV off whenever the laptop screen blanks. Taking no prisoners! :-) ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Samsung Smart TV "crashes" NVidia driver, can't detect TV any more?
I can attach the TV to my laptop long after boot, with no issues. However, once this sleep behaviour has triggered, I can disconnect and reconnect as many times as I like without resuscitating it. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Samsung Smart TV "crashes" NVidia driver, can't detect TV any more?
> Wow! That is awesome! Hopefully this will give me some pointers in the right > direction (if > it doesn't "just work"(tm)). > > From reading the script at /usr/bin/nvidia-sleep.sh, it seems that when it > happens, I can > try to change to a console VT, suspend and awaken the driver, then change > back, and > hopefully it will revive the display! > > Thanks! Unfortunately, this didn't work. I still sit with the same problem. Can anyone point me to some debug settings that I can enable, that will potentially give me some insight into what the two different graphics devices are seeing when this is happening? i.e. logs that would show e.g. external monitor connected, external monitor disconnected events, graphics wakeup events, etc? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Samsung Smart TV "crashes" NVidia driver, can't detect TV any more?
> Hi folks, > > I have a 43" Samsung Smart TV that I am using as a monitor with a ThinkPad > P51, > running Fedora 35 Workstation Edition. This laptop has a "NVIDIA Corporation > GM206GLM > [Quadro M2200 Mobile] / Mesa Intel® HD Graphics 630 (KBL GT2)" graphics > subsystem. As > far as I can make out, I am using the latest NVidia driver (495.46). > > What is unfortunately happening, is that if my laptop goes to sleep, the TV > sees that the > source disappears, and "tries to look for the laptop", repeatedly. This ends > up > waking up the laptop (sometimes), until the TV eventually gives up and turns > itself off. > The problem is then that the laptop no longer detects that the TV is > connected to the HDMI > port, and I have to reboot to allow the laptop to detect the screen again. > Xrandr does not > detect the display if run manually, and the Settings app Displays page also > doesn't > show the TV. Just to be absolutely clear, it doesn't seem to be a requirement that the TV eventually gives up and turns itself off before the behaviour manifests on my laptop. I have caught it "searching" for a signal (although not cycling between inputs), but I was too late to save my laptop from going into this state where it no longer detects the external display. Also, I can unplug and replug the HDMI cable, and the TV detects that there is a connection (display changes from "No signal" to a blue background, but eventually goes back to "No signal"), but the laptop does not detect the external display. Also, if I use a USB-C to HDMI adapter, it does detect the display being connected while in this state, but this is not a great solution because the laptop does not appear to like the USB-C to HDMI adapter being disconnected. This is what I get: [377553.263099] usb 3-1: USB disconnect, device number 2 [377553.363447] xhci_hcd :3d:00.0: xHCI host controller not responding, assume dead [377553.363451] xhci_hcd :3d:00.0: HC died; cleaning up [377553.380937] xhci_hcd :3d:00.0: remove, state 4 [377553.380940] usb usb4: USB disconnect, device number 1 [377553.381199] xhci_hcd :3d:00.0: USB bus 4 deregistered [377553.381346] xhci_hcd :3d:00.0: remove, state 1 [377553.381349] usb usb3: USB disconnect, device number 1 [377553.381725] xhci_hcd :3d:00.0: Host halt failed, -19 [377553.381729] xhci_hcd :3d:00.0: Host not accessible, reset failed. [377553.381846] xhci_hcd :3d:00.0: USB bus 3 deregistered [377553.394128] pci_bus :06: Allocating resources [377553.394140] pcieport :06:01.0: bridge window [io 0x1000-0x0fff] to [bus 08-3c] add_size 1000 [377553.394143] pcieport :06:02.0: bridge window [io 0x1000-0x0fff] to [bus 3d] add_size 1000 [377553.394144] pcieport :06:02.0: bridge window [mem 0x0010-0x000f 64bit pref] to [bus 3d] add_size 20 add_align 10 [377553.394146] pcieport :05:00.0: bridge window [io 0x1000-0x0fff] to [bus 06-3d] add_size 3000 [377553.394149] pcieport :05:00.0: BAR 13: no space for [io size 0x3000] [377553.394150] pcieport :05:00.0: BAR 13: failed to assign [io size 0x3000] [377553.394151] pcieport :05:00.0: BAR 13: no space for [io size 0x3000] [377553.394152] pcieport :05:00.0: BAR 13: failed to assign [io size 0x3000] [377553.394156] pcieport :06:02.0: BAR 15: no space for [mem size 0x0020 64bit pref] [377553.394157] pcieport :06:02.0: BAR 15: failed to assign [mem size 0x0020 64bit pref] [377553.394158] pcieport :06:01.0: BAR 13: no space for [io size 0x1000] [377553.394158] pcieport :06:01.0: BAR 13: failed to assign [io size 0x1000] [377553.394159] pcieport :06:02.0: BAR 13: no space for [io size 0x1000] [377553.394160] pcieport :06:02.0: BAR 13: failed to assign [io size 0x1000] [377553.394162] pcieport :06:02.0: BAR 15: no space for [mem size 0x0020 64bit pref] [377553.394163] pcieport :06:02.0: BAR 15: failed to assign [mem size 0x0020 64bit pref] [377553.394164] pcieport :06:02.0: BAR 13: no space for [io size 0x1000] [377553.394164] pcieport :06:02.0: BAR 13: failed to assign [io size 0x1000] [377553.394165] pcieport :06:01.0: BAR 13: no space for [io size 0x1000] [377553.394166] pcieport :06:01.0: BAR 13: failed to assign [io size 0x1000] [377558.553883] pcieport :06:00.0: can't change power state from D3cold to D0 (config space inaccessible) [377558.554278] pci_bus :07: busn_res: [bus 07] is released [377558.554418] pci_bus :08: busn_res: [bus 08-3c] is released [377558.554530] pci_bus :3d: busn_res: [bus 3d] is released [377558.554725] pci_bus :06: busn_res: [bus 06-3d] is released And reconnecting it does nothing immediately, but about two to three minutes later, the USB-C adapter is recognised again: [377710.601196] pci :05:00.0: [8086:15da] type 01 class 0x060400 [377710.601265] pci :05:00.0: enabling Extended Tags [377710.601403] pci :05:00.0: supports D1 D2
