** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Changed in: mesa (Ubuntu)
Status: Incomplete => New
** Summary changed:
- [nouveau] screen background overlaid with scan type artifact in red
+ [nouveau, GeForce 7300 LE] screen background overlaid with scan type artifact
Yes. Re-installed. uname reports 5.5.0. and the screen is back to
the red raster diagonal mess.
On 1/23/20 11:58 PM, Daniel van Vugt wrote:
> Please run:
>
>uname -a
>
> to confirm the newer kernel version is active.
>
--
You received this bug notification because you are a member of
Doesn't look like it - uname returned 4.16.0-74-generic #84-Ubuntu SMP.
May have overlaid the new generic by running APT upgrade. I'll try
re-installing.
On 1/23/20 11:39 PM, Daniel van Vugt wrote:
> Please run:
>
>uname -a
>
> to confirm the newer kernel version is active.
>
--
You
Please run:
uname -a
to confirm the newer kernel version is active.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860483
Title:
[nouveau] screen background overlaid with scan type artifact in
** Attachment added: "Screenshot from 2020-01-23 23-40-25.png"
https://bugs.launchpad.net/bugs/1860483/+attachment/5322561/+files/Screenshot%20from%202020-01-23%2023-40-25.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
OTOH, I tried APT update and upgrade after the installation didn't
change things and I did get a screen change. Attached is a post-restart
screenshot.
On 1/23/20 11:29 PM, Paul Collinsworth wrote:
> Installed and that wasn't the root cause. Still the same problem.
>
> On 1/23/20 8:03 PM,
Please run:
uname -a
to confirm the newer kernel version is active.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860483
Title:
[nouveau] screen background overlaid with scan type artifact in
Installed and that wasn't the root cause. Still the same problem.
On 1/23/20 8:03 PM, Daniel van Vugt wrote:
> It's not important whether dkms is in use or not. You can just assume
> the worst case and install the four packages in comment #17.
>
--
You received this bug notification because you
It's not important whether dkms is in use or not. You can just assume
the worst case and install the four packages in comment #17.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860483
Title:
I thought that might be the case, and looked in a couple of the /var
subdirectories and didn't see dkms. I may run a more exhaustive search
before trying the new linux install. I'll be doing that within an hour
or so; had to be out most of the day on other business.
At the moment the system
It would be putting files in /var/lib/dkms if it was in use. You would
also have a deb package called 'dkms' installed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860483
Title:
[nouveau] screen
If dkms is installed, where is it in the filesystem? I checked /var and
it isn't there - and I run a (more-or-less) standard system, with regard
to file organization; don't know that I have any modules that require dkms.
On 1/23/20 12:34 AM, Timo Aaltonen wrote:
> and can skip the headers too,
Thanks. I'll try the install shortly.
On 1/23/20 12:23 AM, Daniel van Vugt wrote:
> I know, this is a common question and we should do better to make it
> clear. You only need the non-lowlatency packages:
>
> https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5-rc7/linux-
>
and can skip the headers too, if there are no dkms modules that need
those
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860483
Title:
[nouveau] screen background overlaid with scan type artifact
I know, this is a common question and we should do better to make it
clear. You only need the non-lowlatency packages:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5-rc7/linux-
headers-5.5.0-050500rc7_5.5.0-050500rc7.202001192030_all.deb
Should I try all the amd64 packages, i.e. headers, images, and modules
in both generic and low latency flavors, or is there a specific package?
I've pulled down the entire amd64 set, and the headers-all as well.
On 1/22/20 6:55 PM, Daniel van Vugt wrote:
> Thanks. This is starting to sound
Thanks. This is starting to sound like general problems with the nouveau
kernel driver, or maybe GPU memory corruption, since multiple desktop
environments are broken.
Next please try the latest kernel packages from
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5-rc7/
** No longer affects:
I tried "Ubuntu on Wayland". Crash. Logged in. Screen loaded improperly
and keyboard and mouse froze; handlers blocked and who knows what else.
The screen didn't have the red artifact though; it had a cluster of
diagonal black and white scan lines covering about the middle third of
the screen,
I encountered an issue after advising you that 18.04.3 works. Perhaps it
sheds some light on the problem.
It occurred to me that perhaps there is a graphics issue and that part
of what I was seeing is contamination of the background image I was
using. So I tried to open "Settings" in order to
OK, thanks. Assuming the bug isn't just hiding and wouldn't reappear
later in 18.04.3 if used long enough, then this implies a fix exists
somewhere in the HWE packages (which are the difference between 18.04
fully updated and 18.04.3 fully updated).
The only two sets of HWE packages I can think
Loaded a USB with 18.04.3 and the problem wasn't there. The screen,
apart from the tool bars, was the default Ubuntu screen with nothing
unusual about it.
On 1/21/20 11:00 PM, Paul Collinsworth wrote:
> OK. I'm back and loading a USB with bootable images. Back later.
>
>
> On 1/21/20 8:28 PM,
OK. I'm back and loading a USB with bootable images. Back later.
On 1/21/20 8:28 PM, Daniel van Vugt wrote:
> Please also try booting Ubuntu 18.04.3 from USB. It's slightly different
> to what you have and might have fixed this issue already...
> http://releases.ubuntu.com/18.04/
>
--
You
I'll try that shortly or in a little while. May be a couple of hours.
On 1/21/20 8:06 PM, Daniel van Vugt wrote:
> OK then. We'll treat this as a pure nouveau driver bug, because that's
> the most plausible and common explanation for issues like this.
>
> Please try booting Ubuntu 20.04 from USB
Please also try booting Ubuntu 18.04.3 from USB. It's slightly different
to what you have and might have fixed this issue already...
http://releases.ubuntu.com/18.04/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
OK then. We'll treat this as a pure nouveau driver bug, because that's
the most plausible and common explanation for issues like this.
Please try booting Ubuntu 20.04 from USB (don't need to install it) and
tell us if that has the same problem: http://cdimage.ubuntu.com/daily-
live/current/
**
Did not get a positive result. Additional drivers displays a "No
Additional Drivers Available" message, and the only active button on
that page is "Close".
On 1/21/20 7:48 PM, Paul Collinsworth wrote:
> I considered that. Went to the Nvidia web page before I pushed the bug
> report out and got
I considered that. Went to the Nvidia web page before I pushed the bug
report out and got some sort of null message there. I'll check software
& updates and see if I get a positive result.
On 1/21/20 7:00 PM, Daniel van Vugt wrote:
> I suspect you will be able to avoid the problem if you can
I suspect you will be able to avoid the problem if you can switch to the
Nvidia proprietary driver. Please look in Software & Updates >
Additional Drivers > ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
28 matches
Mail list logo
