Ubuntu 20.04: display wrong after recovering from suspend mode
after recovering from suspend mode, the display lose its colour and starts flickering and is quite unreadable, being very luminous. After restarting the PC, everything OK
Question information
- Language:
- English Edit question
- Status:
- Expired
- For:
- Ubuntu Edit question
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Revision history for this message
|
#1 |
Does the system have a make and model?
Do you have the latest BIOS?
Revision history for this message
|
#2 |
here is my hardware configuration:
claudio@
00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 12)
00:01.0 PCI bridge: Intel Corporation Core Processor PCI Express x16 Root Port (rev 12)
00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 06)
00:1c.2 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 3 (rev 06)
00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a6)
00:1f.0 ISA bridge: Intel Corporation H57 Chipset LPC Interface Controller (rev 06)
00:1f.2 RAID bus controller: Intel Corporation SATA Controller [RAID mode] (rev 06)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 06)
01:00.0 VGA compatible controller: NVIDIA Corporation GT215 [GeForce GT 320] (rev a2)
01:00.1 Audio device: NVIDIA Corporation High Definition Audio Controller (rev a1)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02)
ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02)
ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02)
ff:02.1 Host bridge: Intel Corporation 1st Generation Core i3/5/7 Processor QPI Physical 0 (rev 02)
ff:02.2 Host bridge: Intel Corporation 1st Generation Core i3/5/7 Processor Reserved (rev 02)
ff:02.3 Host bridge: Intel Corporation 1st Generation Core i3/5/7 Processor Reserved (rev 02)
claudio@
Revision history for this message
|
#3 |
OK the question is tricky for you. What is the output of:
sudo dmidecode -t 1
Thanks
Revision history for this message
|
#4 |
BIOS Information
Vendor: American Megatrends Inc.
Version: P01-A4
Release Date: 02/15/2011
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 1024 kB
Characteristics:
ISA is supported
PCI is supported
PNP is supported
APM is supported
BIOS is upgradeable
BIOS shadowing is allowed
ESCD support is available
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
CGA/mono video services are supported (int 10h)
ACPI is supported
USB legacy is supported
LS-120 boot is supported
ATAPI Zip drive boot is supported
BIOS boot specification is supported
Targeted content distribution is supported
BIOS Revision: 8.15
Revision history for this message
|
#5 |
laudio@
# dmidecode 3.2
Getting SMBIOS data from sysfs.
SMBIOS 2.6 present.
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: Acer
Product Name: Aspire M5910
Version:
Serial Number: PTSDWE215303401
UUID: cdfc8744-
Wake-up Type: Power Switch
SKU Number: To Be Filled By O.E.M.
Family: Acer Desktop
Revision history for this message
|
#6 |
I put again the PC in suspend mode and, after recovering, the screen is
as shown in the attached file
Il 16/05/20 10:21, actionparsnip ha scritto:
> Your question #690755 on Ubuntu changed:
> https:/
>
> Status: Open => Needs information
>
> actionparsnip requested more information:
> OK the question is tricky for you. What is the output of:
>
> sudo dmidecode -t 1
>
> Thanks
>
Revision history for this message
|
#7 |
Replying to the automated email and attaching a file doesn't work. You need to use something like imageshack to host the image and post a URL as an update
Revision history for this message
|
#8 |
OK, you are right, here is the link to the "printscreen"
https:/
I hope you can access it
In any case I just wanted to inform you that the problem happens everytime I recover from suspend mode
Revision history for this message
|
#9 |
https:/
Seems to be an older system. Latest BIOS is May 2011. Do you have this installed?
Revision history for this message
|
#10 |
BIOS Information
Vendor: American Megatrends Inc.
Version: P01-A4
Release Date: 02/15/2011
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 1024 k
Revision history for this message
|
#11 |
Another information that may be useful to solve the problem.
1. Whichever is the way I put the system in suspend mode, i.e. after a programmed time or with the power switch, after recovering in normal mode, the display is always damaged.
2. but if I rightclick the display in an empty space and I check the "change background" instruction, it accepts a good one, but not the previous, that is the standard Ubuntu 20.04.
3. After the dispaly is again a good one, I can change it again and resume the original one.
I hope this can help you, wizards of Ubuntu,
Thanks for the attention.
Claudio
Revision history for this message
|
#12 |
This question was expired because it remained in the 'Open' state without activity for the last 15 days.
Revision history for this message
|
#13 |
The problem is still there.
After recovering from suspend mode, the screen is corrupted, as shown in
this picture:
https:/
<https:/
It is possible to recover just right-clicking on the corrupted screem
and choosing another wallpaper. If the chosen one is not the same that
was corrupted, the screen will show a good picture.
After this, if the previous screen is chosen, it will come back correctly.
Il 02/06/20 10:51, Launchpad Janitor ha scritto:
> Your question #690755 on Ubuntu changed:
> https:/
>
> Status: Open => Expired
>
> Launchpad Janitor expired the question:
> This question was expired because it remained in the 'Open' state
> without activity for the last 15 days.
>
Revision history for this message
|
#14 |
This question was expired because it remained in the 'Open' state without activity for the last 15 days.