[Bug 1901505] Re: upgrade to 20.10 broke haswell laptop (no regular boot, no /dev/dri/card0)
I was able to build 5.8.0-25-generic with this patch and is working excellent with Ubuntu (Gnome-shell) For some reason i can't get the source of latest Ubuntu Kernel 5.8.0-26-generic because is unavailable in unsigned version... so I get previous which is available and do compiling. So for me with Intel Pentium G3258 CPU - Haswell Generation this fix things. Patch is referenced in my previous message. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901505 Title: upgrade to 20.10 broke haswell laptop (no regular boot, no /dev/dri/card0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901505] Re: upgrade to 20.10 broke haswell laptop (no regular boot, no /dev/dri/card0)
It result in hang and freeze of graphic system during animation in gnome shell when I click on icon to launch an application from left side menu, but I can switch to VT. switching to VT and when looking at dmesg I see i915 GPU HANG... I will try to apply patch to the current ubuntu 5.8 kernel from Chris Wilson(@ickle) at intel for 5.7+ Kernels form this bug report https://gitlab.freedesktop.org/drm/intel/-/issues/2024 This is the patch https://patchwork.freedesktop.org/patch/395580/?series=82783=1 And will report back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901505 Title: upgrade to 20.10 broke haswell laptop (no regular boot, no /dev/dri/card0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901505] Re: upgrade to 20.10 broke haswell laptop (no regular boot, no /dev/dri/card0)
As I said in previous post i'm not sure that this is the same problem as with me, but look very similar because of the Haswell Processor and I'm unable to get a working Desktop environment. Same computer works just fine with Ubuntu 20.04, which have older kernel. My experience with Ubuntu 20.10 live is that it cannot boot every time and its locks up, but it boots fine in safe gfx mode. In safe gfx mode I installed it on clean disk, and when try boot it - sometimes just log into gnome shell and it locks up. Error in dmesg is i915 GPU hang. In wayland it works better so I can click on menus but sometimes it freeze for few seconds and continue( GPU reset) and when you run program that use xwayland it got a total lock up. I installed cinnamon desktop and it locks immediately after login, Cinnamon with software rendering works just fine. I tried Xubuntu it hang as well. With "nomodeset" kernel parameter it works fine but only in 1024x768, tested it with Ubuntu, Cinnamon and Xubuntu. So I search for solution and find this thread over FDO, with a lot of people with Haswell GT1 video having the same problem since kernel 5.6 I think. https://gitlab.freedesktop.org/drm/intel/-/issues/2024 Other peoples with same problem, also there are several threads over Arch linux forums https://bugzilla.redhat.com/show_bug.cgi?id=1843274 https://bugzilla.redhat.com/show_bug.cgi?id=1886438 My Processor is Intel Pentium G3258 AE and is Desktop CPU. Other components I think doesn't really matter in this case. and my errors from DMESG [ 31.037041] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc79, in gnome-shell [1441] [ 31.037044] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 31.037045] Please file a _new_ bug report at https://gitlab.freedesktop.org/drm/intel/issues/new. [ 31.037047] Please see https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs for details. [ 31.037048] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 31.037049] The GPU crash dump is required to analyze GPU hangs, so please always attach it. [ 31.037050] GPU crash dump saved to /sys/class/drm/card0/error [ 31.037859] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [ 31.140859] i915 :00:02.0: [drm] gnome-shell[1441] context reset due to GPU hang [ 34.080734] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc79, in Xorg [1290] [ 34.080924] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [ 34.183350] i915 :00:02.0: [drm] Xorg[1290] context reset due to GPU hang [ 39.819821] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc79, in gnome-shell [1441] [ 39.821530] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [ 39.924378] i915 :00:02.0: [drm] gnome-shell[1441] context reset due to GPU hang [ 45.912749] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc79, in gnome-shell [1441] [ 45.912822] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [ 46.014840] i915 :00:02.0: [drm] gnome-shell[1441] context reset due to GPU hang I can attach crash dump ass well. ** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #2024 https://gitlab.freedesktop.org/drm/intel/-/issues/2024 ** Bug watch added: Red Hat Bugzilla #1843274 https://bugzilla.redhat.com/show_bug.cgi?id=1843274 ** Bug watch added: Red Hat Bugzilla #1886438 https://bugzilla.redhat.com/show_bug.cgi?id=1886438 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901505 Title: upgrade to 20.10 broke haswell laptop (no regular boot, no /dev/dri/card0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901505] Re: upgrade to 20.10 broke haswell laptop (no regular boot, no /dev/dri/card0)
I have similar or same problem and I have haswell too... I will explain my problem at large in next post but first try these things. First when boot and it hangs, try go switch to different VT - ctrl+alt + F3 or F4 then enter sudo dmesg at the bottom you will ikely find this... i915 :00:02.0: [drm] GPU HANG Then try another one - boot kernel with "nomodeset" parameter (without quotes) - for me it produce a working system but only with 1024x768 resolution And third one - can you specify what Haswell processor you have? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901505 Title: upgrade to 20.10 broke haswell laptop (no regular boot, no /dev/dri/card0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890815] Re: vainfo requires a nvidia sofile not in repositories
Canonical doesn't even care about its users. This is a bad support. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890815 Title: vainfo requires a nvidia sofile not in repositories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libva-utils/+bug/1890815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890815] Re: vainfo requires a nvidia sofile not in repositories
When will they fix this error? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890815 Title: vainfo requires a nvidia sofile not in repositories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libva-utils/+bug/1890815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 238118] Re: linux-image-2.6.24-* w/ aic79xx crash under heavy I/O load
This patch is included in kernel 2.6.24-20.37 from your log I've seen you are running 2.6.24-19.x New kernel is available for testing in proposed but it's not automatically upgraded by Linux meta package, you have to do it yourself. You can see bug fix mentioned in changelog. https://launchpad.net/ubuntu/hardy/+source/linux/2.6.24-20.37 -- linux-image-2.6.24-* w/ aic79xx crash under heavy I/O load https://bugs.launchpad.net/bugs/238118 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 245954] Re: gnome-system-monitor segfault
*** This bug is a duplicate of bug 244903 *** https://bugs.launchpad.net/bugs/244903 ** This bug has been marked a duplicate of bug 244903 gnome-system-monitor crashes/segfaults if clicked on the tab file systems -- gnome-system-monitor segfault https://bugs.launchpad.net/bugs/245954 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 243682] Re: [Intrepid] Usplash Screen Corruption
Today installed Intrepid Alpha2 and I got the same on my laptop. model: Lenovo Z61m Display: 1680x1050 Videocard: ATI X1400 Connected to docking station with DVI connected to another monitor, but for now I use laptop display as primary. /etc/usplash.conf doesn't contain resolution only two comments Here problem is showed only in first two boot/reboot, in all latter restarts problem is gone, but resolution is the lowest avalible 320x240 or 640x480 I can say exactly because screen is with pretty high dpi. After installation of all available updates, some package rebuild initramfs and problem is back but again only on first reboot, in all latter it is showed correct but with the lowest resolution. -- [Intrepid] Usplash Screen Corruption https://bugs.launchpad.net/bugs/243682 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 246321] [NEW] check and close buttons have the same accelerator key if check for automatically updates is disabled
Public bug reported: Binary package hint: update-manager check and close buttons have the same accelerator key if check for automatically updates is disabled. so you can't use them reasonable, alt+C just switch between check and close buttons and again and again because they have the same accelerator key. Ubuntu Hardy 8.04 steps to reproduce: just switch off automatically updates and start update-manager ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New -- check and close buttons have the same accelerator key if check for automatically updates is disabled https://bugs.launchpad.net/bugs/246321 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 246321] Re: check and close buttons have the same accelerator key if check for automatically updates is disabled
** Attachment added: update-manager.png http://launchpadlibrarian.net/15873282/update-manager.png -- check and close buttons have the same accelerator key if check for automatically updates is disabled https://bugs.launchpad.net/bugs/246321 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 246321] Re: check and close buttons have the same accelerator key if check for automatically updates is disabled
Furthermore in the screenshot accelerator key for Check is 'C' but in main program screen is 'K' if there is any need for I will attach screenshot. -- check and close buttons have the same accelerator key if check for automatically updates is disabled https://bugs.launchpad.net/bugs/246321 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
