[Kernel-packages] [Bug 1886230] Re: Thinkpad P1 Gen2 HDMI doesn't work after log out or reboot
OK, I've filed a bug at https://gitlab.freedesktop.org/drm/intel/-/issues/2145 I'll keep this bug report updated. ** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #2145 https://gitlab.freedesktop.org/drm/intel/-/issues/2145 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886230 Title: Thinkpad P1 Gen2 HDMI doesn't work after log out or reboot Status in linux package in Ubuntu: Confirmed Bug description: I have a Thinkpad P1 Gen 2. This specific machine was customized to NOT have a discrete Nvidia GPU. It ONLY has an integrated Intel UHD 630 GPU. This is not a hardware issue as Windows seems to handle things correctly. With an external monitor connected via HDMI, boot proceeds OK with the external monitor displaying the boot process. I log in to a Gnome session using X. After login, I am able to open the display settings GUI and set mode to "single display" with the built-in LCD disabled and the external monitor enabled. This works correctly. However, if I then reboot the machine with the external monitor connected: 1. Boot proceeds correctly with the boot process shown on the external monitor. 2. After login, the external monitor is powered off and the built-in LCD is enabled. The "display settings" GUI shows the external monitor as a connected "Unknown Display" with the wrong resolution of 1024x768. Attempting to use the GUI to set "single display" as above results in the external monitor still being powered off, and the built-in LCD also powered off. I have to press esc to cancel the display changes. At this point, the relevant output of `xrandr` is: DP1 connected 1024x768+3840+0 (normal left inverted right x axis y axis) 600mm x 340mm 1024x768 60.00* 800x600 60.3256.25 848x480 60.00 640x480 59.94 DP1 is the HDMI output, and it is listed at the wrong resolutions. If I disconnect the HDMI cable then run `xrandr` again, the output of `xrandr` is unchanged: it still lists DP1 as connected (!) even though the cable is disconnected. This bug also occurs if instead of rebooting, I simply log out and log back in again. The only solution appears to be to unplug the HDMI cable, shut down the machine (not reboot or log out), power on, log in, and at the desktop plug in the HDMI cable. At that point it works again. Rebooting does not solve the issue. It seems that a complete shutdown is required. I tested on Ubuntu 20.04's stock kernel 5.4.0 and also kernel 5.7.7 and the issue is present on both versions. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 1888 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Jul 3 16:00:55 2020 InstallationDate: Installed on 2020-07-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20QTCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=f8b7e5a7-d866-4a48-aef0-b430465ab66d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET42W (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 Gen 2 dmi.product.name: 20QTCTO1WW dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2 dmi.product.version: ThinkPad P1 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886230] Re: Thinkpad P1 Gen2 HDMI doesn't work after log out or reboot
Re. the bug report in the email thread, they state that "if HDMI cable isn't plugged before boot, the HDMI port becomes useless and never responds to cable hotplugging" However my situation seems to be the reverse: If the HDMI cable is plugged in before cold boot, then the port appears to work through boot, GDM, and desktop. But on log out to GDM or soft reboot, it breaks. The interesting thing is that the port breaks after log out to GDM, not just reboot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886230 Title: Thinkpad P1 Gen2 HDMI doesn't work after log out or reboot Status in linux package in Ubuntu: Confirmed Bug description: I have a Thinkpad P1 Gen 2. This specific machine was customized to NOT have a discrete Nvidia GPU. It ONLY has an integrated Intel UHD 630 GPU. This is not a hardware issue as Windows seems to handle things correctly. With an external monitor connected via HDMI, boot proceeds OK with the external monitor displaying the boot process. I log in to a Gnome session using X. After login, I am able to open the display settings GUI and set mode to "single display" with the built-in LCD disabled and the external monitor enabled. This works correctly. However, if I then reboot the machine with the external monitor connected: 1. Boot proceeds correctly with the boot process shown on the external monitor. 2. After login, the external monitor is powered off and the built-in LCD is enabled. The "display settings" GUI shows the external monitor as a connected "Unknown Display" with the wrong resolution of 1024x768. Attempting to use the GUI to set "single display" as above results in the external monitor still being powered off, and the built-in LCD also powered off. I have to press esc to cancel the display changes. At this point, the relevant output of `xrandr` is: DP1 connected 1024x768+3840+0 (normal left inverted right x axis y axis) 600mm x 340mm 1024x768 60.00* 800x600 60.3256.25 848x480 60.00 640x480 59.94 DP1 is the HDMI output, and it is listed at the wrong resolutions. If I disconnect the HDMI cable then run `xrandr` again, the output of `xrandr` is unchanged: it still lists DP1 as connected (!) even though the cable is disconnected. This bug also occurs if instead of rebooting, I simply log out and log back in again. The only solution appears to be to unplug the HDMI cable, shut down the machine (not reboot or log out), power on, log in, and at the desktop plug in the HDMI cable. At that point it works again. Rebooting does not solve the issue. It seems that a complete shutdown is required. I tested on Ubuntu 20.04's stock kernel 5.4.0 and also kernel 5.7.7 and the issue is present on both versions. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 1888 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Jul 3 16:00:55 2020 InstallationDate: Installed on 2020-07-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20QTCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=f8b7e5a7-d866-4a48-aef0-b430465ab66d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET42W (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 Gen 2 dmi.product.name: 20QTCTO1WW dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2 dmi.product.version: ThinkPad P1 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886230/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1886230] Re: Thinkpad P1 Gen2 HDMI doesn't work after log out or reboot
The patch did not fix the issue. However, during boot, some error text appeared that did not appear before: [1.868916] [drm:drm_lspcon_set_mode [drm_kms_helper]] *ERROR* LSPCON mode change timed out [1.868970] [drm:lspcon_change_mode.constprop.0 [i915]] *ERROR* LSPCON mode change failed [1.868998] [drm:lspcon_resume [i915]] *ERROR* LSPCON mode change to PCON failed [1.869024] [drm:lspcon_resume [i915]] *ERROR* Failed to probe lspcon [1.869049] [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port B dmesg from patched kernel 5.8.0-rc3 attached. ** Attachment added: "dmesg-custom" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886230/+attachment/5389742/+files/dmesg-custom -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886230 Title: Thinkpad P1 Gen2 HDMI doesn't work after log out or reboot Status in linux package in Ubuntu: Confirmed Bug description: I have a Thinkpad P1 Gen 2. This specific machine was customized to NOT have a discrete Nvidia GPU. It ONLY has an integrated Intel UHD 630 GPU. This is not a hardware issue as Windows seems to handle things correctly. With an external monitor connected via HDMI, boot proceeds OK with the external monitor displaying the boot process. I log in to a Gnome session using X. After login, I am able to open the display settings GUI and set mode to "single display" with the built-in LCD disabled and the external monitor enabled. This works correctly. However, if I then reboot the machine with the external monitor connected: 1. Boot proceeds correctly with the boot process shown on the external monitor. 2. After login, the external monitor is powered off and the built-in LCD is enabled. The "display settings" GUI shows the external monitor as a connected "Unknown Display" with the wrong resolution of 1024x768. Attempting to use the GUI to set "single display" as above results in the external monitor still being powered off, and the built-in LCD also powered off. I have to press esc to cancel the display changes. At this point, the relevant output of `xrandr` is: DP1 connected 1024x768+3840+0 (normal left inverted right x axis y axis) 600mm x 340mm 1024x768 60.00* 800x600 60.3256.25 848x480 60.00 640x480 59.94 DP1 is the HDMI output, and it is listed at the wrong resolutions. If I disconnect the HDMI cable then run `xrandr` again, the output of `xrandr` is unchanged: it still lists DP1 as connected (!) even though the cable is disconnected. This bug also occurs if instead of rebooting, I simply log out and log back in again. The only solution appears to be to unplug the HDMI cable, shut down the machine (not reboot or log out), power on, log in, and at the desktop plug in the HDMI cable. At that point it works again. Rebooting does not solve the issue. It seems that a complete shutdown is required. I tested on Ubuntu 20.04's stock kernel 5.4.0 and also kernel 5.7.7 and the issue is present on both versions. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 1888 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Jul 3 16:00:55 2020 InstallationDate: Installed on 2020-07-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20QTCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=f8b7e5a7-d866-4a48-aef0-b430465ab66d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET42W (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 Gen 2 dmi.product.name: 20QTCTO1WW dmi.product.sku:
[Kernel-packages] [Bug 1886230] Re: Thinkpad P1 Gen2 HDMI doesn't work after log out or reboot
Should I report this to upstream instead? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886230 Title: Thinkpad P1 Gen2 HDMI doesn't work after log out or reboot Status in linux package in Ubuntu: Confirmed Bug description: I have a Thinkpad P1 Gen 2. This specific machine was customized to NOT have a discrete Nvidia GPU. It ONLY has an integrated Intel UHD 630 GPU. This is not a hardware issue as Windows seems to handle things correctly. With an external monitor connected via HDMI, boot proceeds OK with the external monitor displaying the boot process. I log in to a Gnome session using X. After login, I am able to open the display settings GUI and set mode to "single display" with the built-in LCD disabled and the external monitor enabled. This works correctly. However, if I then reboot the machine with the external monitor connected: 1. Boot proceeds correctly with the boot process shown on the external monitor. 2. After login, the external monitor is powered off and the built-in LCD is enabled. The "display settings" GUI shows the external monitor as a connected "Unknown Display" with the wrong resolution of 1024x768. Attempting to use the GUI to set "single display" as above results in the external monitor still being powered off, and the built-in LCD also powered off. I have to press esc to cancel the display changes. At this point, the relevant output of `xrandr` is: DP1 connected 1024x768+3840+0 (normal left inverted right x axis y axis) 600mm x 340mm 1024x768 60.00* 800x600 60.3256.25 848x480 60.00 640x480 59.94 DP1 is the HDMI output, and it is listed at the wrong resolutions. If I disconnect the HDMI cable then run `xrandr` again, the output of `xrandr` is unchanged: it still lists DP1 as connected (!) even though the cable is disconnected. This bug also occurs if instead of rebooting, I simply log out and log back in again. The only solution appears to be to unplug the HDMI cable, shut down the machine (not reboot or log out), power on, log in, and at the desktop plug in the HDMI cable. At that point it works again. Rebooting does not solve the issue. It seems that a complete shutdown is required. I tested on Ubuntu 20.04's stock kernel 5.4.0 and also kernel 5.7.7 and the issue is present on both versions. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 1888 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Jul 3 16:00:55 2020 InstallationDate: Installed on 2020-07-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20QTCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=f8b7e5a7-d866-4a48-aef0-b430465ab66d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET42W (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 Gen 2 dmi.product.name: 20QTCTO1WW dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2 dmi.product.version: ThinkPad P1 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886230] Re: Thinkpad P1 Gen2 HDMI doesn't work after log out or reboot
Tested on stock Ubuntu kernel 5.4.0, then 5.7.7, then 5.8.0-rc3 with same results. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886230 Title: Thinkpad P1 Gen2 HDMI doesn't work after log out or reboot Status in linux package in Ubuntu: Confirmed Bug description: I have a Thinkpad P1 Gen 2. This specific machine was customized to NOT have a discrete Nvidia GPU. It ONLY has an integrated Intel UHD 630 GPU. This is not a hardware issue as Windows seems to handle things correctly. With an external monitor connected via HDMI, boot proceeds OK with the external monitor displaying the boot process. I log in to a Gnome session using X. After login, I am able to open the display settings GUI and set mode to "single display" with the built-in LCD disabled and the external monitor enabled. This works correctly. However, if I then reboot the machine with the external monitor connected: 1. Boot proceeds correctly with the boot process shown on the external monitor. 2. After login, the external monitor is powered off and the built-in LCD is enabled. The "display settings" GUI shows the external monitor as a connected "Unknown Display" with the wrong resolution of 1024x768. Attempting to use the GUI to set "single display" as above results in the external monitor still being powered off, and the built-in LCD also powered off. I have to press esc to cancel the display changes. At this point, the relevant output of `xrandr` is: DP1 connected 1024x768+3840+0 (normal left inverted right x axis y axis) 600mm x 340mm 1024x768 60.00* 800x600 60.3256.25 848x480 60.00 640x480 59.94 DP1 is the HDMI output, and it is listed at the wrong resolutions. If I disconnect the HDMI cable then run `xrandr` again, the output of `xrandr` is unchanged: it still lists DP1 as connected (!) even though the cable is disconnected. This bug also occurs if instead of rebooting, I simply log out and log back in again. The only solution appears to be to unplug the HDMI cable, shut down the machine (not reboot or log out), power on, log in, and at the desktop plug in the HDMI cable. At that point it works again. Rebooting does not solve the issue. It seems that a complete shutdown is required. I tested on Ubuntu 20.04's stock kernel 5.4.0 and also kernel 5.7.7 and the issue is present on both versions. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 1888 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Jul 3 16:00:55 2020 InstallationDate: Installed on 2020-07-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20QTCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=f8b7e5a7-d866-4a48-aef0-b430465ab66d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET42W (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 Gen 2 dmi.product.name: 20QTCTO1WW dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2 dmi.product.version: ThinkPad P1 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886230] Re: Thinkpad P1 Gen2 HDMI doesn't work after log out or reboot
Note, this occurs in both Wayland and X. Thus I think it's probably a kernel issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886230 Title: Thinkpad P1 Gen2 HDMI doesn't work after log out or reboot Status in linux package in Ubuntu: Confirmed Bug description: I have a Thinkpad P1 Gen 2. This specific machine was customized to NOT have a discrete Nvidia GPU. It ONLY has an integrated Intel UHD 630 GPU. This is not a hardware issue as Windows seems to handle things correctly. With an external monitor connected via HDMI, boot proceeds OK with the external monitor displaying the boot process. I log in to a Gnome session using X. After login, I am able to open the display settings GUI and set mode to "single display" with the built-in LCD disabled and the external monitor enabled. This works correctly. However, if I then reboot the machine with the external monitor connected: 1. Boot proceeds correctly with the boot process shown on the external monitor. 2. After login, the external monitor is powered off and the built-in LCD is enabled. The "display settings" GUI shows the external monitor as a connected "Unknown Display" with the wrong resolution of 1024x768. Attempting to use the GUI to set "single display" as above results in the external monitor still being powered off, and the built-in LCD also powered off. I have to press esc to cancel the display changes. At this point, the relevant output of `xrandr` is: DP1 connected 1024x768+3840+0 (normal left inverted right x axis y axis) 600mm x 340mm 1024x768 60.00* 800x600 60.3256.25 848x480 60.00 640x480 59.94 DP1 is the HDMI output, and it is listed at the wrong resolutions. If I disconnect the HDMI cable then run `xrandr` again, the output of `xrandr` is unchanged: it still lists DP1 as connected (!) even though the cable is disconnected. This bug also occurs if instead of rebooting, I simply log out and log back in again. The only solution appears to be to unplug the HDMI cable, shut down the machine (not reboot or log out), power on, log in, and at the desktop plug in the HDMI cable. At that point it works again. Rebooting does not solve the issue. It seems that a complete shutdown is required. I tested on Ubuntu 20.04's stock kernel 5.4.0 and also kernel 5.7.7 and the issue is present on both versions. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 1888 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Jul 3 16:00:55 2020 InstallationDate: Installed on 2020-07-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20QTCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=f8b7e5a7-d866-4a48-aef0-b430465ab66d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET42W (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 Gen 2 dmi.product.name: 20QTCTO1WW dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2 dmi.product.version: ThinkPad P1 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886230] Re: Thinkpad P1 Gen2 HDMI doesn't work after log out or reboot
dmesg output after reboot, and HDMI is broken ** Attachment added: "dmesg-broken-post-reboot" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886230/+attachment/5389518/+files/dmesg-broken-post-reboot -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886230 Title: Thinkpad P1 Gen2 HDMI doesn't work after log out or reboot Status in linux package in Ubuntu: New Bug description: I have a Thinkpad P1 Gen 2. This specific machine was customized to NOT have a discrete Nvidia GPU. It ONLY has an integrated Intel UHD 630 GPU. This is not a hardware issue as Windows seems to handle things correctly. With an external monitor connected via HDMI, boot proceeds OK with the external monitor displaying the boot process. I log in to a Gnome session using X. After login, I am able to open the display settings GUI and set mode to "single display" with the built-in LCD disabled and the external monitor enabled. This works correctly. However, if I then reboot the machine with the external monitor connected: 1. Boot proceeds correctly with the boot process shown on the external monitor. 2. After login, the external monitor is powered off and the built-in LCD is enabled. The "display settings" GUI shows the external monitor as a connected "Unknown Display" with the wrong resolution of 1024x768. Attempting to use the GUI to set "single display" as above results in the external monitor still being powered off, and the built-in LCD also powered off. I have to press esc to cancel the display changes. At this point, the relevant output of `xrandr` is: DP1 connected 1024x768+3840+0 (normal left inverted right x axis y axis) 600mm x 340mm 1024x768 60.00* 800x600 60.3256.25 848x480 60.00 640x480 59.94 DP1 is the HDMI output, and it is listed at the wrong resolutions. If I disconnect the HDMI cable then run `xrandr` again, the output of `xrandr` is unchanged: it still lists DP1 as connected (!) even though the cable is disconnected. This bug also occurs if instead of rebooting, I simply log out and log back in again. The only solution appears to be to unplug the HDMI cable, shut down the machine (not reboot or log out), power on, log in, and at the desktop plug in the HDMI cable. At that point it works again. Rebooting does not solve the issue. It seems that a complete shutdown is required. I tested on Ubuntu 20.04's stock kernel 5.4.0 and also kernel 5.7.7 and the issue is present on both versions. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 1888 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Jul 3 16:00:55 2020 InstallationDate: Installed on 2020-07-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20QTCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=f8b7e5a7-d866-4a48-aef0-b430465ab66d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET42W (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 Gen 2 dmi.product.name: 20QTCTO1WW dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2 dmi.product.version: ThinkPad P1 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886230] Re: Thinkpad P1 Gen2 HDMI doesn't work after log out or reboot
dmesg output when HDMI is working ** Attachment added: "dmesg-working" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886230/+attachment/5389517/+files/dmesg-working -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886230 Title: Thinkpad P1 Gen2 HDMI doesn't work after log out or reboot Status in linux package in Ubuntu: New Bug description: I have a Thinkpad P1 Gen 2. This specific machine was customized to NOT have a discrete Nvidia GPU. It ONLY has an integrated Intel UHD 630 GPU. This is not a hardware issue as Windows seems to handle things correctly. With an external monitor connected via HDMI, boot proceeds OK with the external monitor displaying the boot process. I log in to a Gnome session using X. After login, I am able to open the display settings GUI and set mode to "single display" with the built-in LCD disabled and the external monitor enabled. This works correctly. However, if I then reboot the machine with the external monitor connected: 1. Boot proceeds correctly with the boot process shown on the external monitor. 2. After login, the external monitor is powered off and the built-in LCD is enabled. The "display settings" GUI shows the external monitor as a connected "Unknown Display" with the wrong resolution of 1024x768. Attempting to use the GUI to set "single display" as above results in the external monitor still being powered off, and the built-in LCD also powered off. I have to press esc to cancel the display changes. At this point, the relevant output of `xrandr` is: DP1 connected 1024x768+3840+0 (normal left inverted right x axis y axis) 600mm x 340mm 1024x768 60.00* 800x600 60.3256.25 848x480 60.00 640x480 59.94 DP1 is the HDMI output, and it is listed at the wrong resolutions. If I disconnect the HDMI cable then run `xrandr` again, the output of `xrandr` is unchanged: it still lists DP1 as connected (!) even though the cable is disconnected. This bug also occurs if instead of rebooting, I simply log out and log back in again. The only solution appears to be to unplug the HDMI cable, shut down the machine (not reboot or log out), power on, log in, and at the desktop plug in the HDMI cable. At that point it works again. Rebooting does not solve the issue. It seems that a complete shutdown is required. I tested on Ubuntu 20.04's stock kernel 5.4.0 and also kernel 5.7.7 and the issue is present on both versions. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 1888 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Jul 3 16:00:55 2020 InstallationDate: Installed on 2020-07-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20QTCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=f8b7e5a7-d866-4a48-aef0-b430465ab66d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET42W (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 Gen 2 dmi.product.name: 20QTCTO1WW dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2 dmi.product.version: ThinkPad P1 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886230] Re: Thinkpad P1 Gen2 HDMI doesn't work after log out or reboot
xrandr output when HDMI is working correctly ** Attachment added: "xrandr-working" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886230/+attachment/5389515/+files/xrandr-working -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886230 Title: Thinkpad P1 Gen2 HDMI doesn't work after log out or reboot Status in linux package in Ubuntu: New Bug description: I have a Thinkpad P1 Gen 2. This specific machine was customized to NOT have a discrete Nvidia GPU. It ONLY has an integrated Intel UHD 630 GPU. This is not a hardware issue as Windows seems to handle things correctly. With an external monitor connected via HDMI, boot proceeds OK with the external monitor displaying the boot process. I log in to a Gnome session using X. After login, I am able to open the display settings GUI and set mode to "single display" with the built-in LCD disabled and the external monitor enabled. This works correctly. However, if I then reboot the machine with the external monitor connected: 1. Boot proceeds correctly with the boot process shown on the external monitor. 2. After login, the external monitor is powered off and the built-in LCD is enabled. The "display settings" GUI shows the external monitor as a connected "Unknown Display" with the wrong resolution of 1024x768. Attempting to use the GUI to set "single display" as above results in the external monitor still being powered off, and the built-in LCD also powered off. I have to press esc to cancel the display changes. At this point, the relevant output of `xrandr` is: DP1 connected 1024x768+3840+0 (normal left inverted right x axis y axis) 600mm x 340mm 1024x768 60.00* 800x600 60.3256.25 848x480 60.00 640x480 59.94 DP1 is the HDMI output, and it is listed at the wrong resolutions. If I disconnect the HDMI cable then run `xrandr` again, the output of `xrandr` is unchanged: it still lists DP1 as connected (!) even though the cable is disconnected. This bug also occurs if instead of rebooting, I simply log out and log back in again. The only solution appears to be to unplug the HDMI cable, shut down the machine (not reboot or log out), power on, log in, and at the desktop plug in the HDMI cable. At that point it works again. Rebooting does not solve the issue. It seems that a complete shutdown is required. I tested on Ubuntu 20.04's stock kernel 5.4.0 and also kernel 5.7.7 and the issue is present on both versions. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 1888 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Jul 3 16:00:55 2020 InstallationDate: Installed on 2020-07-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20QTCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=f8b7e5a7-d866-4a48-aef0-b430465ab66d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET42W (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 Gen 2 dmi.product.name: 20QTCTO1WW dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2 dmi.product.version: ThinkPad P1 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886230] Re: Thinkpad P1 Gen2 HDMI doesn't work after log out or reboot
xrandr output after the bug occurs (i.e. HDMI is broken) ** Attachment added: "xrandr-broken" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886230/+attachment/5389516/+files/xrandr-broken -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886230 Title: Thinkpad P1 Gen2 HDMI doesn't work after log out or reboot Status in linux package in Ubuntu: New Bug description: I have a Thinkpad P1 Gen 2. This specific machine was customized to NOT have a discrete Nvidia GPU. It ONLY has an integrated Intel UHD 630 GPU. This is not a hardware issue as Windows seems to handle things correctly. With an external monitor connected via HDMI, boot proceeds OK with the external monitor displaying the boot process. I log in to a Gnome session using X. After login, I am able to open the display settings GUI and set mode to "single display" with the built-in LCD disabled and the external monitor enabled. This works correctly. However, if I then reboot the machine with the external monitor connected: 1. Boot proceeds correctly with the boot process shown on the external monitor. 2. After login, the external monitor is powered off and the built-in LCD is enabled. The "display settings" GUI shows the external monitor as a connected "Unknown Display" with the wrong resolution of 1024x768. Attempting to use the GUI to set "single display" as above results in the external monitor still being powered off, and the built-in LCD also powered off. I have to press esc to cancel the display changes. At this point, the relevant output of `xrandr` is: DP1 connected 1024x768+3840+0 (normal left inverted right x axis y axis) 600mm x 340mm 1024x768 60.00* 800x600 60.3256.25 848x480 60.00 640x480 59.94 DP1 is the HDMI output, and it is listed at the wrong resolutions. If I disconnect the HDMI cable then run `xrandr` again, the output of `xrandr` is unchanged: it still lists DP1 as connected (!) even though the cable is disconnected. This bug also occurs if instead of rebooting, I simply log out and log back in again. The only solution appears to be to unplug the HDMI cable, shut down the machine (not reboot or log out), power on, log in, and at the desktop plug in the HDMI cable. At that point it works again. Rebooting does not solve the issue. It seems that a complete shutdown is required. I tested on Ubuntu 20.04's stock kernel 5.4.0 and also kernel 5.7.7 and the issue is present on both versions. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 1888 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Jul 3 16:00:55 2020 InstallationDate: Installed on 2020-07-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20QTCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=f8b7e5a7-d866-4a48-aef0-b430465ab66d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET42W (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 Gen 2 dmi.product.name: 20QTCTO1WW dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2 dmi.product.version: ThinkPad P1 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886230] [NEW] Thinkpad P1 Gen2 HDMI doesn't work after log out or reboot
Public bug reported: I have a Thinkpad P1 Gen 2. This specific machine was customized to NOT have a discrete Nvidia GPU. It ONLY has an integrated Intel UHD 630 GPU. This is not a hardware issue as Windows seems to handle things correctly. With an external monitor connected via HDMI, boot proceeds OK with the external monitor displaying the boot process. I log in to a Gnome session using X. After login, I am able to open the display settings GUI and set mode to "single display" with the built-in LCD disabled and the external monitor enabled. This works correctly. However, if I then reboot the machine with the external monitor connected: 1. Boot proceeds correctly with the boot process shown on the external monitor. 2. After login, the external monitor is powered off and the built-in LCD is enabled. The "display settings" GUI shows the external monitor as a connected "Unknown Display" with the wrong resolution of 1024x768. Attempting to use the GUI to set "single display" as above results in the external monitor still being powered off, and the built-in LCD also powered off. I have to press esc to cancel the display changes. At this point, the relevant output of `xrandr` is: DP1 connected 1024x768+3840+0 (normal left inverted right x axis y axis) 600mm x 340mm 1024x768 60.00* 800x600 60.3256.25 848x480 60.00 640x480 59.94 DP1 is the HDMI output, and it is listed at the wrong resolutions. If I disconnect the HDMI cable then run `xrandr` again, the output of `xrandr` is unchanged: it still lists DP1 as connected (!) even though the cable is disconnected. This bug also occurs if instead of rebooting, I simply log out and log back in again. The only solution appears to be to unplug the HDMI cable, shut down the machine (not reboot or log out), power on, log in, and at the desktop plug in the HDMI cable. At that point it works again. Rebooting does not solve the issue. It seems that a complete shutdown is required. I tested on Ubuntu 20.04's stock kernel 5.4.0 and also kernel 5.7.7 and the issue is present on both versions. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 1888 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Jul 3 16:00:55 2020 InstallationDate: Installed on 2020-07-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20QTCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=f8b7e5a7-d866-4a48-aef0-b430465ab66d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET42W (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 Gen 2 dmi.product.name: 20QTCTO1WW dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2 dmi.product.version: ThinkPad P1 Gen 2 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "xrandr-broken" https://bugs.launchpad.net/bugs/1886230/+attachment/5389496/+files/xrandr-broken -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886230 Title: Thinkpad P1 Gen2 HDMI doesn't work after log out or reboot Status in linux package in Ubuntu: New Bug description: I have a Thinkpad P1 Gen 2. This specific machine was customized to NOT have a discrete Nvidia GPU. It ONLY has an integrated Intel UHD 630 GPU. This is not a hardware issue as Windows seems to handle things correctly. With an external monitor connected via HDMI, boot proceeds OK with the external monitor displaying the boot process. I log in to a Gnome session using X. After login, I am able to open the display settings GUI and set mode to "single display" with the built-in LCD disabled and the external monitor enabled.
[Kernel-packages] [Bug 1854896] Re: Synaptics TM3336-004 Touchpad Stopped working after update to the latest kernel 4.15.0-72 generic
Note, I'm running vanilla Ubuntu 18.04.3, *not* Mint. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854896 Title: Synaptics TM3336-004 Touchpad Stopped working after update to the latest kernel 4.15.0-72 generic Status in linux package in Ubuntu: Incomplete Bug description: Please see to it, my touchpad all of a sudden stopped working after reboot. it happened after updating to the latest kernel 4.15.0-72, i am using linux mint 19.2. Pointer version: Synaptics TM3336-004 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854896/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854896] Re: Synaptics TM3336-004 Touchpad Stopped working after update to the latest kernel 4.15.0-72 generic
This hit me today on Ubuntu 18.04. Upgraded to kernel 4.15.0-72-generic and the touchpad does not move. The touchpad *buttons* do work, but I cannot move the cursor. Booting in to 4.15.0-70-generic makes them work again. I tried running apport-collect 1854896 but it says I can't do so because I'm not the owner of the bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854896 Title: Synaptics TM3336-004 Touchpad Stopped working after update to the latest kernel 4.15.0-72 generic Status in linux package in Ubuntu: Incomplete Bug description: Please see to it, my touchpad all of a sudden stopped working after reboot. it happened after updating to the latest kernel 4.15.0-72, i am using linux mint 19.2. Pointer version: Synaptics TM3336-004 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854896/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1315360] Re: [Razer Blade] Trackpad detected as mouse only
I spoke with Andrew Duggan and he figured out that as of kernel 4.0 the touchpad is incorrectly detected as a clickpad. That's why the touchpad works, but in a flaky way. The good news is that this seems solvable. All you have to do is: synclient ClickPad=0 Palm detection is also off by default and I find it basically unusuable without it, so also do: synclient PalmDetect=1 These changes aren't saved after a reboot, but to make them permanent, create a configuration file in /usr/share/X11/xorg.conf.d/. You can do it with this one-liner: echo -e Section \InputClass\\n\tIdentifier \touchpad catchall\\n\tDriver \synaptics\\n\tMatchIsTouchpad \on\\n\tMatchDevicePath \/dev/input/event*\\n\n\tOption \PalmDetect\ \1\\n\tOption \ClickPad\ \0\\nEndSection | sudo tee /usr/share/X11/xorg.conf.d/60-synaptics-options.conf /dev/null So to summarize, we can get 100% touchpad functionality by installing Linux kernel = 4.0, then running both synclient ClickPad=0 synclient PalmDetect=1 Not sure who to go to to correct this default misconfiguration, but at least we can get everything working! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1315360 Title: [Razer Blade] Trackpad detected as mouse only Status in linux package in Ubuntu: Confirmed Bug description: The trackpad works as a mouse and tap-to-click works, but no scrolling (neither two-finger nor edge) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mike 1570 F pulseaudio /dev/snd/controlC1: mike 1570 F pulseaudio CurrentDesktop: Unity Date: Fri May 2 08:45:39 2014 HibernationDevice: RESUME=UUID=ba977027-c742-470c-9a92-199f27ebea08 InstallationDate: Installed on 2014-04-30 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Razer Blade ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=c72e4937-c906-4466-8990-b28729f9d39d ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2014 dmi.bios.vendor: RAZER dmi.bios.version: 2.24 dmi.board.asset.tag: NULL dmi.board.name: RAZER dmi.board.vendor: RAZER dmi.board.version: 1.00 dmi.chassis.asset.tag: ABCDEF dmi.chassis.type: 10 dmi.chassis.vendor: RAZER dmi.chassis.version: N/A dmi.modalias: dmi:bvnRAZER:bvr2.24:bd03/24/2014:svnRazer:pnBlade:pvr2.04:rvnRAZER:rnRAZER:rvr1.00:cvnRAZER:ct10:cvrN/A: dmi.product.name: Blade dmi.product.version: 2.04 dmi.sys.vendor: Razer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1315360/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1315360] Re: [Razer Blade] Trackpad detected as mouse only
FYI kernel 4.0-rc3 seems to add full trackpad support, including scrolling and multitouch, out of the box for the RB 2015. However there's a problem with the mouse buttons--left click is randomly dropped about 50% of the time. Left click by tapping seems to work consistently though. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1315360 Title: [Razer Blade] Trackpad detected as mouse only Status in linux package in Ubuntu: Confirmed Bug description: The trackpad works as a mouse and tap-to-click works, but no scrolling (neither two-finger nor edge) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mike 1570 F pulseaudio /dev/snd/controlC1: mike 1570 F pulseaudio CurrentDesktop: Unity Date: Fri May 2 08:45:39 2014 HibernationDevice: RESUME=UUID=ba977027-c742-470c-9a92-199f27ebea08 InstallationDate: Installed on 2014-04-30 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Razer Blade ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=c72e4937-c906-4466-8990-b28729f9d39d ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2014 dmi.bios.vendor: RAZER dmi.bios.version: 2.24 dmi.board.asset.tag: NULL dmi.board.name: RAZER dmi.board.vendor: RAZER dmi.board.version: 1.00 dmi.chassis.asset.tag: ABCDEF dmi.chassis.type: 10 dmi.chassis.vendor: RAZER dmi.chassis.version: N/A dmi.modalias: dmi:bvnRAZER:bvr2.24:bd03/24/2014:svnRazer:pnBlade:pvr2.04:rvnRAZER:rnRAZER:rvr1.00:cvnRAZER:ct10:cvrN/A: dmi.product.name: Blade dmi.product.version: 2.04 dmi.sys.vendor: Razer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1315360/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1315360] Re: [Razer Blade] Trackpad detected as mouse only
I tried installing the 3.16 kernel on Trusty. The touchpad was still detected as a mouse. I then tried applying the patch in #8 from the Github repo and the touchpad stopped responding entirely--no movement or clicks. Is there anything I can contribute to help get this fixed? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1315360 Title: [Razer Blade] Trackpad detected as mouse only Status in “linux” package in Ubuntu: Incomplete Bug description: The trackpad works as a mouse and tap-to-click works, but no scrolling (neither two-finger nor edge) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mike 1570 F pulseaudio /dev/snd/controlC1: mike 1570 F pulseaudio CurrentDesktop: Unity Date: Fri May 2 08:45:39 2014 HibernationDevice: RESUME=UUID=ba977027-c742-470c-9a92-199f27ebea08 InstallationDate: Installed on 2014-04-30 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Razer Blade ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=c72e4937-c906-4466-8990-b28729f9d39d ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2014 dmi.bios.vendor: RAZER dmi.bios.version: 2.24 dmi.board.asset.tag: NULL dmi.board.name: RAZER dmi.board.vendor: RAZER dmi.board.version: 1.00 dmi.chassis.asset.tag: ABCDEF dmi.chassis.type: 10 dmi.chassis.vendor: RAZER dmi.chassis.version: N/A dmi.modalias: dmi:bvnRAZER:bvr2.24:bd03/24/2014:svnRazer:pnBlade:pvr2.04:rvnRAZER:rnRAZER:rvr1.00:cvnRAZER:ct10:cvrN/A: dmi.product.name: Blade dmi.product.version: 2.04 dmi.sys.vendor: Razer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1315360/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1310798] Re: JMicron JMC250 ethernet: networking always disconnected
Jim, I solved the issue by disabling gigabit ethernet on the network card with: $ sudo ethtool -s eth0 speed 100 duplex full This command has to be run on startup. Here's the relevant lshw -c if you're still interested, run after the above fix: description: Ethernet interface product: JMC250 PCI Express Gigabit Ethernet Controller vendor: JMicron Technology Corp. physical id: 0.5 bus info: pci@:02:00.5 logical name: eth0 version: 03 size: 100Mbit/s capacity: 1Gbit/s width: 32 bits clock: 33MHz capabilities: pm pciexpress msix msi bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=jme driverversion=1.0.8 duplex=full ip=192.168.1.2 latency=0 link=yes multicast=yes port=MII speed=100Mbit/s resources: irq:45 memory:feaf8000-feafbfff ioport:dc00(size=128) ioport:d800(size=256) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1310798 Title: JMicron JMC250 ethernet: networking always disconnected Status in “linux” package in Ubuntu: Confirmed Bug description: Summary: Ubuntu version: 14.04 desktop x64 Problem hardware: JMicron JMC250 ethernet controller (jme drivers) Expected behavior: Ethernet networking works when cable connected. Actual behavior: Networking always shows disconnected, even when cable connected. Details: In Ubuntu 14.04 with a JMicron JMC250 ethernet controller, the ethernet link is always shown as disconnected, even when the cable is connected and networking is otherwise working. In Ubuntu 12.04, this same ethernet controller also exhibited the same problem. However it was fixable by downloading and manually compiling a new version of the jme drivers from here: ftp://driver.jmicron.com.tw/Ethernet/Linux/jmebp-1.0.8.5.tar.bz In 14.04, the above 1.0.8.5 driver no longer compiles and is thus not installable. I tried downloading and compiling the latest source for the driver from https://github.com/torvalds/linux/blob/master/drivers/net/ethernet/jme.c. This driver does compile, but after installation still doesn't work, with the wired network status always showing disconnected. There is a related Launchpad bug #880316 but that one is for *missing* drivers in an older Ubuntu version, not *broken* drivers. (The drivers are now included in 14.04, but are totally broken.) These drivers haven't worked out of the box since 2012... can we get a little love here? Output of dmesg | grep jme [2.044151] jme: JMicron JMC2XX ethernet driver version 1.0.8 [2.044209] jme :02:00.5: can't disable ASPM; OS doesn't have ASPM control [2.045351] jme :02:00.5 eth0: JMC250 Gigabit Ethernet chiprev:23 pcirev:3 macaddr:80:ee:73:13:68:7d [ 22.302804] jme :02:00.5: irq 45 for MSI/MSI-X [ 22.302930] jme :02:00.5 eth0: Link is down [ 22.328814] jme :02:00.5 eth0: Link is down Relevant lspci line: 02:00.5 Ethernet controller: JMicron Technology Corp. JMC250 PCI Express Gigabit Ethernet Controller (rev 03) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 1540 F pulseaudio CurrentDesktop: Unity Date: Mon Apr 21 16:06:41 2014 HibernationDevice: RESUME=UUID=9a76734d-f4e5-48af-9ba2-c86f712f39d9 InstallationDate: Installed on 2014-04-18 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Standard XS35 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=347d51ff-61a3-4f81-bcc4-125707703d1e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: B10IE01 dmi.board.vendor: Shuttle dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Shuttle dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias:
[Kernel-packages] [Bug 880316] Re: Ubuntu installer can't setup network on Shuttle XS35GTV2
I think I may have found a possible workaround. The stock drivers on 14.04 don't work out of the box for *gigabit ethernet*. If you're connecting to a gigabit router, then open a terminal and run: $ sudo ethtool -s eth0 speed 100 duplex full If you don't have ethtool installed, install with: $ sudo apt-get install ethtool Once you run that command, your link should be detected immediately. The catch is that you'll be running at 100Mbps, not gigabit. I think what happened was that there was some kind of kernel networking API change between 12.04 and 14.04. Whatever changed broke this driver's ability to deal with gigabit connections. It's a bummer that this doesn't work out-of-the-box and that it's been ignored for so long, but at least we have a crappy workaround. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/880316 Title: Ubuntu installer can't setup network on Shuttle XS35GTV2 Status in “linux” package in Ubuntu: Confirmed Bug description: I'm trying to install Ubuntu on a Shuttle XS35GTV2. The installer can't set up the network connection. I've tried Ubuntu 10.04 32 and 64 bit netinstall, minimal and server, Ubuntu 11.10 32 bit netinstall. The Debian Squeeze 64 bit netinstall installer has no problem. (I've now installed openELEC which has no problems too) I was able to install Ubuntu 10.04 64 bit server but only without network connection. I then could load the jme module: # modprobe jme # depmod -a without errors. But I can't get eth0 running. The output of lspci is: 02:00.5 Ethernet controller: JMicron Technology Corp. JMC250 PCI Express Gigabit Ethernet Controller (rev 03) 03:00.0 Network controller: Realtek Semiconductor C., Ltd Device 8176 (rev 01) # lshw -C network *-network DISABLED description: Ethernet interface product: JMC250 PCI Express Gigabit Ethernet Controller vendor: JMicron Technology Corp. physical id: 0.5 bus info: pci@:02:00.5 logical name: eth0 version: 03 serial: 80:ee:73:1f:ef:df size: 10MB/s capacity: 1GB/s width: 32 bits clock: 33MHz capabilities: pm pciexpress msix msi bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=off broadcast=yes driver=jme driverversion=1.0.5 duplex=half latency=0 link=no multicast=yes port=MII speed=10MB/s resources: irq:17 memory:feaf4000-feaf7fff ioport:dc00(size=128) ioport:d800(size=256) *-network UNCLAIMED description: Network controller product: Realtek Semiconductor Co., Ltd. vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 version: 01 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: latency=0 resources: ioport:e800(size=256) memory:febfc000-febf I've posted my problem at the Ubuntu users mailing list: http://www.linux-archive.org/ubuntu-user/588603-jme-module-missing-netboot-installation.html Edit: Unfortunately I couldn't reassign it as it has nothing to do with gnome-nettools (see post #1). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/880316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1310798] [NEW] JMicron JMC250 ethernet: networking always disconnected
Public bug reported: Summary: Ubuntu version: 14.04 desktop x64 Problem hardware: JMicron JMC250 ethernet controller (jme drivers) Expected behavior: Ethernet networking works when cable connected. Actual behavior: Networking always shows disconnected, even when cable connected. Details: In Ubuntu 14.04 with a JMicron JMC250 ethernet controller, the ethernet link is always shown as disconnected, even when the cable is connected and networking is otherwise working. In Ubuntu 12.04, this same ethernet controller also exhibited the same problem. However it was fixable by downloading and manually compiling a new version of the jme drivers from here: ftp://driver.jmicron.com.tw/Ethernet/Linux/jmebp-1.0.8.5.tar.bz In 14.04, the above 1.0.8.5 driver no longer compiles and is thus not installable. I tried downloading and compiling the latest source for the driver from https://github.com/torvalds/linux/blob/master/drivers/net/ethernet/jme.c. This driver does compile, but after installation still doesn't work, with the wired network status always showing disconnected. There is a related Launchpad bug #880316 but that one is for *missing* drivers in an older Ubuntu version, not *broken* drivers. (The drivers are now included in 14.04, but are totally broken.) These drivers haven't worked out of the box since 2012... can we get a little love here? Output of dmesg | grep jme [2.044151] jme: JMicron JMC2XX ethernet driver version 1.0.8 [2.044209] jme :02:00.5: can't disable ASPM; OS doesn't have ASPM control [2.045351] jme :02:00.5 eth0: JMC250 Gigabit Ethernet chiprev:23 pcirev:3 macaddr:80:ee:73:13:68:7d [ 22.302804] jme :02:00.5: irq 45 for MSI/MSI-X [ 22.302930] jme :02:00.5 eth0: Link is down [ 22.328814] jme :02:00.5 eth0: Link is down Relevant lspci line: 02:00.5 Ethernet controller: JMicron Technology Corp. JMC250 PCI Express Gigabit Ethernet Controller (rev 03) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 1540 F pulseaudio CurrentDesktop: Unity Date: Mon Apr 21 16:06:41 2014 HibernationDevice: RESUME=UUID=9a76734d-f4e5-48af-9ba2-c86f712f39d9 InstallationDate: Installed on 2014-04-18 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Standard XS35 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=347d51ff-61a3-4f81-bcc4-125707703d1e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: B10IE01 dmi.board.vendor: Shuttle dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Shuttle dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd03/21/2011:svnStandard:pnXS35:pvrToBeFilledByO.E.M.:rvnShuttle:rnB10IE01:rvrTobefilledbyO.E.M.:cvnShuttle:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: XS35 dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: Standard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1310798 Title: JMicron JMC250 ethernet: networking always disconnected Status in “linux” package in Ubuntu: New Bug description: Summary: Ubuntu version: 14.04 desktop x64 Problem hardware: JMicron JMC250 ethernet controller (jme drivers) Expected behavior: Ethernet networking works when cable connected. Actual behavior: Networking always shows disconnected, even when cable connected. Details: In Ubuntu 14.04 with a JMicron JMC250 ethernet controller, the ethernet link is always shown as disconnected, even when the cable is connected and networking is otherwise working. In Ubuntu 12.04, this same ethernet controller also exhibited the same problem. However it was fixable by downloading and manually compiling a new version of the jme drivers from here: ftp://driver.jmicron.com.tw/Ethernet/Linux/jmebp-1.0.8.5.tar.bz In 14.04, the above 1.0.8.5 driver no longer compiles and is thus not installable. I tried
[Kernel-packages] [Bug 880316] Re: Ubuntu installer can't setup network on Shuttle XS35GTV2
I opened a new Launchpad bug #1310798 because this one seems to be about missing drivers in an older Ubuntu version, not broken drivers. Maybe by getting this re-focused we can get some love for this almost 3-year- old bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/880316 Title: Ubuntu installer can't setup network on Shuttle XS35GTV2 Status in “linux” package in Ubuntu: Confirmed Bug description: I'm trying to install Ubuntu on a Shuttle XS35GTV2. The installer can't set up the network connection. I've tried Ubuntu 10.04 32 and 64 bit netinstall, minimal and server, Ubuntu 11.10 32 bit netinstall. The Debian Squeeze 64 bit netinstall installer has no problem. (I've now installed openELEC which has no problems too) I was able to install Ubuntu 10.04 64 bit server but only without network connection. I then could load the jme module: # modprobe jme # depmod -a without errors. But I can't get eth0 running. The output of lspci is: 02:00.5 Ethernet controller: JMicron Technology Corp. JMC250 PCI Express Gigabit Ethernet Controller (rev 03) 03:00.0 Network controller: Realtek Semiconductor C., Ltd Device 8176 (rev 01) # lshw -C network *-network DISABLED description: Ethernet interface product: JMC250 PCI Express Gigabit Ethernet Controller vendor: JMicron Technology Corp. physical id: 0.5 bus info: pci@:02:00.5 logical name: eth0 version: 03 serial: 80:ee:73:1f:ef:df size: 10MB/s capacity: 1GB/s width: 32 bits clock: 33MHz capabilities: pm pciexpress msix msi bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=off broadcast=yes driver=jme driverversion=1.0.5 duplex=half latency=0 link=no multicast=yes port=MII speed=10MB/s resources: irq:17 memory:feaf4000-feaf7fff ioport:dc00(size=128) ioport:d800(size=256) *-network UNCLAIMED description: Network controller product: Realtek Semiconductor Co., Ltd. vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 version: 01 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: latency=0 resources: ioport:e800(size=256) memory:febfc000-febf I've posted my problem at the Ubuntu users mailing list: http://www.linux-archive.org/ubuntu-user/588603-jme-module-missing-netboot-installation.html Edit: Unfortunately I couldn't reassign it as it has nothing to do with gnome-nettools (see post #1). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/880316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1310798] Re: JMicron JMC250 ethernet: networking always disconnected
*** This bug is a duplicate of bug 880316 *** https://bugs.launchpad.net/bugs/880316 This is not a duplicate, bug #880316 was solved in the comments (see comment #4 and #5) because the drivers weren't included in the distribution at all. The fact that the drivers are totally broken deserves a different bug-- they were working for a brief while until 12.04, and they've been included in the distro since 12.04, they just don't work at all and they haven't worked for years. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1310798 Title: JMicron JMC250 ethernet: networking always disconnected Status in “linux” package in Ubuntu: Confirmed Bug description: Summary: Ubuntu version: 14.04 desktop x64 Problem hardware: JMicron JMC250 ethernet controller (jme drivers) Expected behavior: Ethernet networking works when cable connected. Actual behavior: Networking always shows disconnected, even when cable connected. Details: In Ubuntu 14.04 with a JMicron JMC250 ethernet controller, the ethernet link is always shown as disconnected, even when the cable is connected and networking is otherwise working. In Ubuntu 12.04, this same ethernet controller also exhibited the same problem. However it was fixable by downloading and manually compiling a new version of the jme drivers from here: ftp://driver.jmicron.com.tw/Ethernet/Linux/jmebp-1.0.8.5.tar.bz In 14.04, the above 1.0.8.5 driver no longer compiles and is thus not installable. I tried downloading and compiling the latest source for the driver from https://github.com/torvalds/linux/blob/master/drivers/net/ethernet/jme.c. This driver does compile, but after installation still doesn't work, with the wired network status always showing disconnected. There is a related Launchpad bug #880316 but that one is for *missing* drivers in an older Ubuntu version, not *broken* drivers. (The drivers are now included in 14.04, but are totally broken.) These drivers haven't worked out of the box since 2012... can we get a little love here? Output of dmesg | grep jme [2.044151] jme: JMicron JMC2XX ethernet driver version 1.0.8 [2.044209] jme :02:00.5: can't disable ASPM; OS doesn't have ASPM control [2.045351] jme :02:00.5 eth0: JMC250 Gigabit Ethernet chiprev:23 pcirev:3 macaddr:80:ee:73:13:68:7d [ 22.302804] jme :02:00.5: irq 45 for MSI/MSI-X [ 22.302930] jme :02:00.5 eth0: Link is down [ 22.328814] jme :02:00.5 eth0: Link is down Relevant lspci line: 02:00.5 Ethernet controller: JMicron Technology Corp. JMC250 PCI Express Gigabit Ethernet Controller (rev 03) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 1540 F pulseaudio CurrentDesktop: Unity Date: Mon Apr 21 16:06:41 2014 HibernationDevice: RESUME=UUID=9a76734d-f4e5-48af-9ba2-c86f712f39d9 InstallationDate: Installed on 2014-04-18 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Standard XS35 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=347d51ff-61a3-4f81-bcc4-125707703d1e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: B10IE01 dmi.board.vendor: Shuttle dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Shuttle dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd03/21/2011:svnStandard:pnXS35:pvrToBeFilledByO.E.M.:rvnShuttle:rnB10IE01:rvrTobefilledbyO.E.M.:cvnShuttle:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: XS35 dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: Standard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310798/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 880316] Re: Ubuntu installer can't setup network on Shuttle XS35GTV2
So after some more digging it turns out that the 3.14 kernel line has sources for the jme drivers, updated just 20 days ago, that can be compiled on 14.04: https://github.com/torvalds/linux/blob/master/drivers/net/ethernet/jme.c These sources apply the fixes in #24 (weirdly committed over a year ago) and my own stab-in-the-dark in #34 along with many other differences. So I downloaded the new jme.c and jme.h from there and was able to successfully compile and install the driver on Ubuntu 14.04. But it still doesn't work, eth0 still shows as disconnected. Not sure what to do next. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/880316 Title: Ubuntu installer can't setup network on Shuttle XS35GTV2 Status in “linux” package in Ubuntu: Confirmed Bug description: I'm trying to install Ubuntu on a Shuttle XS35GTV2. The installer can't set up the network connection. I've tried Ubuntu 10.04 32 and 64 bit netinstall, minimal and server, Ubuntu 11.10 32 bit netinstall. The Debian Squeeze 64 bit netinstall installer has no problem. (I've now installed openELEC which has no problems too) I was able to install Ubuntu 10.04 64 bit server but only without network connection. I then could load the jme module: # modprobe jme # depmod -a without errors. But I can't get eth0 running. The output of lspci is: 02:00.5 Ethernet controller: JMicron Technology Corp. JMC250 PCI Express Gigabit Ethernet Controller (rev 03) 03:00.0 Network controller: Realtek Semiconductor C., Ltd Device 8176 (rev 01) # lshw -C network *-network DISABLED description: Ethernet interface product: JMC250 PCI Express Gigabit Ethernet Controller vendor: JMicron Technology Corp. physical id: 0.5 bus info: pci@:02:00.5 logical name: eth0 version: 03 serial: 80:ee:73:1f:ef:df size: 10MB/s capacity: 1GB/s width: 32 bits clock: 33MHz capabilities: pm pciexpress msix msi bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=off broadcast=yes driver=jme driverversion=1.0.5 duplex=half latency=0 link=no multicast=yes port=MII speed=10MB/s resources: irq:17 memory:feaf4000-feaf7fff ioport:dc00(size=128) ioport:d800(size=256) *-network UNCLAIMED description: Network controller product: Realtek Semiconductor Co., Ltd. vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 version: 01 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: latency=0 resources: ioport:e800(size=256) memory:febfc000-febf I've posted my problem at the Ubuntu users mailing list: http://www.linux-archive.org/ubuntu-user/588603-jme-module-missing-netboot-installation.html Edit: Unfortunately I couldn't reassign it as it has nothing to do with gnome-nettools (see post #1). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/880316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 880316] Re: Ubuntu installer can't setup network on Shuttle XS35GTV2
In 12.04 this problem was fixable by downloading and compiling the JME drivers (jmebp-1.0.8.5.tar.bz) from the JMicron web site. However on 14.04 compiling the driver fails; it seems like there was an API change in a newer version of the kernel. Consequently I can't get ethernet working at all for my JMC250 Ethernet card on 14.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/880316 Title: Ubuntu installer can't setup network on Shuttle XS35GTV2 Status in “linux” package in Ubuntu: Confirmed Bug description: I'm trying to install Ubuntu on a Shuttle XS35GTV2. The installer can't set up the network connection. I've tried Ubuntu 10.04 32 and 64 bit netinstall, minimal and server, Ubuntu 11.10 32 bit netinstall. The Debian Squeeze 64 bit netinstall installer has no problem. (I've now installed openELEC which has no problems too) I was able to install Ubuntu 10.04 64 bit server but only without network connection. I then could load the jme module: # modprobe jme # depmod -a without errors. But I can't get eth0 running. The output of lspci is: 02:00.5 Ethernet controller: JMicron Technology Corp. JMC250 PCI Express Gigabit Ethernet Controller (rev 03) 03:00.0 Network controller: Realtek Semiconductor C., Ltd Device 8176 (rev 01) # lshw -C network *-network DISABLED description: Ethernet interface product: JMC250 PCI Express Gigabit Ethernet Controller vendor: JMicron Technology Corp. physical id: 0.5 bus info: pci@:02:00.5 logical name: eth0 version: 03 serial: 80:ee:73:1f:ef:df size: 10MB/s capacity: 1GB/s width: 32 bits clock: 33MHz capabilities: pm pciexpress msix msi bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=off broadcast=yes driver=jme driverversion=1.0.5 duplex=half latency=0 link=no multicast=yes port=MII speed=10MB/s resources: irq:17 memory:feaf4000-feaf7fff ioport:dc00(size=128) ioport:d800(size=256) *-network UNCLAIMED description: Network controller product: Realtek Semiconductor Co., Ltd. vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 version: 01 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: latency=0 resources: ioport:e800(size=256) memory:febfc000-febf I've posted my problem at the Ubuntu users mailing list: http://www.linux-archive.org/ubuntu-user/588603-jme-module-missing-netboot-installation.html Edit: Unfortunately I couldn't reassign it as it has nothing to do with gnome-nettools (see post #1). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/880316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 880316] Re: Ubuntu installer can't setup network on Shuttle XS35GTV2
FYI the driver I mentioned in #32 is here: ftp://driver.jmicron.com.tw/Ethernet/Linux/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/880316 Title: Ubuntu installer can't setup network on Shuttle XS35GTV2 Status in “linux” package in Ubuntu: Confirmed Bug description: I'm trying to install Ubuntu on a Shuttle XS35GTV2. The installer can't set up the network connection. I've tried Ubuntu 10.04 32 and 64 bit netinstall, minimal and server, Ubuntu 11.10 32 bit netinstall. The Debian Squeeze 64 bit netinstall installer has no problem. (I've now installed openELEC which has no problems too) I was able to install Ubuntu 10.04 64 bit server but only without network connection. I then could load the jme module: # modprobe jme # depmod -a without errors. But I can't get eth0 running. The output of lspci is: 02:00.5 Ethernet controller: JMicron Technology Corp. JMC250 PCI Express Gigabit Ethernet Controller (rev 03) 03:00.0 Network controller: Realtek Semiconductor C., Ltd Device 8176 (rev 01) # lshw -C network *-network DISABLED description: Ethernet interface product: JMC250 PCI Express Gigabit Ethernet Controller vendor: JMicron Technology Corp. physical id: 0.5 bus info: pci@:02:00.5 logical name: eth0 version: 03 serial: 80:ee:73:1f:ef:df size: 10MB/s capacity: 1GB/s width: 32 bits clock: 33MHz capabilities: pm pciexpress msix msi bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=off broadcast=yes driver=jme driverversion=1.0.5 duplex=half latency=0 link=no multicast=yes port=MII speed=10MB/s resources: irq:17 memory:feaf4000-feaf7fff ioport:dc00(size=128) ioport:d800(size=256) *-network UNCLAIMED description: Network controller product: Realtek Semiconductor Co., Ltd. vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 version: 01 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: latency=0 resources: ioport:e800(size=256) memory:febfc000-febf I've posted my problem at the Ubuntu users mailing list: http://www.linux-archive.org/ubuntu-user/588603-jme-module-missing-netboot-installation.html Edit: Unfortunately I couldn't reassign it as it has nothing to do with gnome-nettools (see post #1). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/880316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 880316] Re: Ubuntu installer can't setup network on Shuttle XS35GTV2
Re. #24, I was able to get the driver to compile, but not actually work, by adding your changes and additionally changing __vlan_hwaccel_put_tag(skb, vid) to __vlan_hwaccel_put_tag(skb, htons(ETH_P_8021Q), vid); I saw that they used the same value in fixing the Realtek driver here: https://bugs.launchpad.net/ubuntu/+source/r8168/+bug/1216906 The constant they use is defined in this block: http://lxr.free- electrons.com/source/drivers/staging/rtl8188eu/include/if_ether.h#L35 Admittedly I have no idea what that addition means or does, I'm just stabbing in the dark. And it obviously didn't work. But maybe it'll put someone on the right path. I also tried contacting the author of the driver for guidance but no doubt he's moved on to other things by now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/880316 Title: Ubuntu installer can't setup network on Shuttle XS35GTV2 Status in “linux” package in Ubuntu: Confirmed Bug description: I'm trying to install Ubuntu on a Shuttle XS35GTV2. The installer can't set up the network connection. I've tried Ubuntu 10.04 32 and 64 bit netinstall, minimal and server, Ubuntu 11.10 32 bit netinstall. The Debian Squeeze 64 bit netinstall installer has no problem. (I've now installed openELEC which has no problems too) I was able to install Ubuntu 10.04 64 bit server but only without network connection. I then could load the jme module: # modprobe jme # depmod -a without errors. But I can't get eth0 running. The output of lspci is: 02:00.5 Ethernet controller: JMicron Technology Corp. JMC250 PCI Express Gigabit Ethernet Controller (rev 03) 03:00.0 Network controller: Realtek Semiconductor C., Ltd Device 8176 (rev 01) # lshw -C network *-network DISABLED description: Ethernet interface product: JMC250 PCI Express Gigabit Ethernet Controller vendor: JMicron Technology Corp. physical id: 0.5 bus info: pci@:02:00.5 logical name: eth0 version: 03 serial: 80:ee:73:1f:ef:df size: 10MB/s capacity: 1GB/s width: 32 bits clock: 33MHz capabilities: pm pciexpress msix msi bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=off broadcast=yes driver=jme driverversion=1.0.5 duplex=half latency=0 link=no multicast=yes port=MII speed=10MB/s resources: irq:17 memory:feaf4000-feaf7fff ioport:dc00(size=128) ioport:d800(size=256) *-network UNCLAIMED description: Network controller product: Realtek Semiconductor Co., Ltd. vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 version: 01 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: latency=0 resources: ioport:e800(size=256) memory:febfc000-febf I've posted my problem at the Ubuntu users mailing list: http://www.linux-archive.org/ubuntu-user/588603-jme-module-missing-netboot-installation.html Edit: Unfortunately I couldn't reassign it as it has nothing to do with gnome-nettools (see post #1). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/880316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
