Re: computer screen blink

2021-10-22 Thread lina
Thanks all, I have changed the source.list

I need to reboot the computer but I'm still waiting for some jobs to finish
before I can reboot.

Thanks all, lina

On Fri, Oct 22, 2021 at 5:12 PM David Wright 
wrote:

> On Fri 22 Oct 2021 at 11:40:28 (+0200), lina wrote:
> > # dmesg | grep -i nouveau
> > [1.656164] fb0: switching to nouveaufb from EFI VGA
> > [1.656250] nouveau :01:00.0: vgaarb: deactivate vga console
> > [1.657164] nouveau :01:00.0: NVIDIA GK208B (b06070b1)
> > [1.766995] nouveau :01:00.0: bios: version 80.28.78.00.30
> > [1.767490] nouveau :01:00.0: fb: 2048 MiB DDR3
> > [1.778993] nouveau :01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT
> > domain=0x000d address=0x0 flags=0x]
> > [3.117074] nouveau :01:00.0: DRM: VRAM: 2048 MiB
> > [3.117075] nouveau :01:00.0: DRM: GART: 1048576 MiB
> > [3.117076] nouveau :01:00.0: DRM: TMDS table version 2.0
> > [3.117077] nouveau :01:00.0: DRM: DCB version 4.0
> > [3.117078] nouveau :01:00.0: DRM: DCB outp 00: 01000f02 00020030
> > [3.117078] nouveau :01:00.0: DRM: DCB outp 01: 02011f62 00020010
> > [3.117079] nouveau :01:00.0: DRM: DCB outp 02: 02022f10 
> > [3.117080] nouveau :01:00.0: DRM: DCB conn 00: 1031
> > [3.117080] nouveau :01:00.0: DRM: DCB conn 01: 2161
> > [3.117081] nouveau :01:00.0: DRM: DCB conn 02: 0200
> > [3.117401] nouveau :01:00.0: DRM: MM: using COPY for buffer
> copies
> > [3.369837] nouveau :01:00.0: DRM: allocated 1920x1080 fb:
> 0x8,
> > bo fd740eca
> > [3.369966] fbcon: nouveaudrmfb (fb0) is primary device
> > [3.417039] nouveau :01:00.0: [drm] fb0: nouveaudrmfb frame buffer
> > device
> > [3.432556] [drm] Initialized nouveau 1.3.1 20120801 for :01:00.0
> on
> > minor 0
> > [4.294574] snd_hda_intel :01:00.1: bound :01:00.0 (ops
> > nv50_audio_component_bind_ops [nouveau])
> > [   52.719911] nouveau :01:00.0: firmware: failed to load
> > nouveau/nv106_fuc084 (-2)
> > [   52.719918] nouveau :01:00.0: Direct firmware load for
> > nouveau/nv106_fuc084 failed with error -2
> > [   52.719926] nouveau :01:00.0: firmware: failed to load
> > nouveau/nv106_fuc084d (-2)
> > [   52.719928] nouveau :01:00.0: Direct firmware load for
> > nouveau/nv106_fuc084d failed with error -2
> > [   52.719930] nouveau :01:00.0: msvld: unable to load firmware data
> > [   52.719931] nouveau :01:00.0: msvld: init failed, -19
> > [16000.312421] nouveau :01:00.0: gr: TRAP ch 2 [007fb03000
> Xorg[2420]]
> > [16000.312434] nouveau :01:00.0: gr: GPC0/TPC0/MP trap: global
> 
> > [] warp 3c0009 [ILLEGAL_INSTR_ENCODING]
> > [16000.332583] nouveau :01:00.0: fifo: fault 00 [READ] at
> > 009f05b4 engine 00 [GR] client 0d [GPC0/GCC] reason 00 [PDE] on
> > channel 2 [007fb03000 Xorg[2420]]
> > [16000.332591] nouveau :01:00.0: fifo: channel 2: killed
> > [16000.332593] nouveau :01:00.0: fifo: runlist 0: scheduled for
> recovery
> > [16000.332597] nouveau :01:00.0: fifo: engine 0: scheduled for
> recovery
> > [16000.332603] nouveau :01:00.0: fifo: engine 6: scheduled for
> recovery
> > [16000.332626] nouveau :01:00.0: Xorg[2420]: channel 2 killed!
> > [16014.029755] nouveau :01:00.0: firmware: failed to load
> > nouveau/nv106_fuc084 (-2)
> > [16014.029764] nouveau :01:00.0: Direct firmware load for
> > nouveau/nv106_fuc084 failed with error -2
> > [16014.029782] nouveau :01:00.0: firmware: failed to load
> > nouveau/nv106_fuc084d (-2)
> > [16014.029786] nouveau :01:00.0: Direct firmware load for
> > nouveau/nv106_fuc084d failed with error -2
> > [16014.029789] nouveau :01:00.0: msvld: unable to load firmware data
> > [16014.029792] nouveau :01:00.0: msvld: init failed, -19
> > [86845.159048] WARNING: CPU: 109 PID: 897 at
> > drivers/gpu/drm/nouveau/nvif/vmm.c:68 nvif_vmm_put+0x6a/0x80 [nouveau]
> > [86845.159209]  x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic
> > hid_apple uas usb_storage sd_mod hid_generic usbhid hid nouveau mxm_wmi
> > nvme video ahci ttm libahci nvme_core xhci_pci drm_kms_helper libata
> t10_pi
> > crc32_pclmul igb xhci_hcd cec crc32c_intel crc_t10dif e1000e dca
> > crct10dif_generic scsi_mod crct10dif_pclmul ptp drm usbcore
> > crct10dif_common pps_core i2c_algo_bit i2c_piix4 usb_common wmi button
> > [last unloaded: cpuid]
> > [86845.159348] Workqueue: events nouveau_cli_work [nouveau]
> > [86845.159380] RIP: 0010:nvif_vmm_put+0x6a/0x80 [nouveau]
> > [86845.159439]  nouveau_vma_del+0x78/0xc0 [nouveau]
> > [86845.159480]  nouveau_gem_object_delete_work+0x36/0x60 [nouveau]
> > [86845.159526]  nouveau_cli_work+0xcc/0x120 [nouveau]
> >
> >  #1 SMP Debian 5.10.70-1 (2021-09-30) x86_64 GNU/Linux
>
> I'm not sure what this is meant to show. Looking at the timestamps,
> this machine was booted at about tea-time yesterday, but some of
> the software tha

Re: computer screen blink

2021-10-22 Thread David Wright
On Fri 22 Oct 2021 at 11:40:28 (+0200), lina wrote:
> # dmesg | grep -i nouveau
> [1.656164] fb0: switching to nouveaufb from EFI VGA
> [1.656250] nouveau :01:00.0: vgaarb: deactivate vga console
> [1.657164] nouveau :01:00.0: NVIDIA GK208B (b06070b1)
> [1.766995] nouveau :01:00.0: bios: version 80.28.78.00.30
> [1.767490] nouveau :01:00.0: fb: 2048 MiB DDR3
> [1.778993] nouveau :01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT
> domain=0x000d address=0x0 flags=0x]
> [3.117074] nouveau :01:00.0: DRM: VRAM: 2048 MiB
> [3.117075] nouveau :01:00.0: DRM: GART: 1048576 MiB
> [3.117076] nouveau :01:00.0: DRM: TMDS table version 2.0
> [3.117077] nouveau :01:00.0: DRM: DCB version 4.0
> [3.117078] nouveau :01:00.0: DRM: DCB outp 00: 01000f02 00020030
> [3.117078] nouveau :01:00.0: DRM: DCB outp 01: 02011f62 00020010
> [3.117079] nouveau :01:00.0: DRM: DCB outp 02: 02022f10 
> [3.117080] nouveau :01:00.0: DRM: DCB conn 00: 1031
> [3.117080] nouveau :01:00.0: DRM: DCB conn 01: 2161
> [3.117081] nouveau :01:00.0: DRM: DCB conn 02: 0200
> [3.117401] nouveau :01:00.0: DRM: MM: using COPY for buffer copies
> [3.369837] nouveau :01:00.0: DRM: allocated 1920x1080 fb: 0x8,
> bo fd740eca
> [3.369966] fbcon: nouveaudrmfb (fb0) is primary device
> [3.417039] nouveau :01:00.0: [drm] fb0: nouveaudrmfb frame buffer
> device
> [3.432556] [drm] Initialized nouveau 1.3.1 20120801 for :01:00.0 on
> minor 0
> [4.294574] snd_hda_intel :01:00.1: bound :01:00.0 (ops
> nv50_audio_component_bind_ops [nouveau])
> [   52.719911] nouveau :01:00.0: firmware: failed to load
> nouveau/nv106_fuc084 (-2)
> [   52.719918] nouveau :01:00.0: Direct firmware load for
> nouveau/nv106_fuc084 failed with error -2
> [   52.719926] nouveau :01:00.0: firmware: failed to load
> nouveau/nv106_fuc084d (-2)
> [   52.719928] nouveau :01:00.0: Direct firmware load for
> nouveau/nv106_fuc084d failed with error -2
> [   52.719930] nouveau :01:00.0: msvld: unable to load firmware data
> [   52.719931] nouveau :01:00.0: msvld: init failed, -19
> [16000.312421] nouveau :01:00.0: gr: TRAP ch 2 [007fb03000 Xorg[2420]]
> [16000.312434] nouveau :01:00.0: gr: GPC0/TPC0/MP trap: global 
> [] warp 3c0009 [ILLEGAL_INSTR_ENCODING]
> [16000.332583] nouveau :01:00.0: fifo: fault 00 [READ] at
> 009f05b4 engine 00 [GR] client 0d [GPC0/GCC] reason 00 [PDE] on
> channel 2 [007fb03000 Xorg[2420]]
> [16000.332591] nouveau :01:00.0: fifo: channel 2: killed
> [16000.332593] nouveau :01:00.0: fifo: runlist 0: scheduled for recovery
> [16000.332597] nouveau :01:00.0: fifo: engine 0: scheduled for recovery
> [16000.332603] nouveau :01:00.0: fifo: engine 6: scheduled for recovery
> [16000.332626] nouveau :01:00.0: Xorg[2420]: channel 2 killed!
> [16014.029755] nouveau :01:00.0: firmware: failed to load
> nouveau/nv106_fuc084 (-2)
> [16014.029764] nouveau :01:00.0: Direct firmware load for
> nouveau/nv106_fuc084 failed with error -2
> [16014.029782] nouveau :01:00.0: firmware: failed to load
> nouveau/nv106_fuc084d (-2)
> [16014.029786] nouveau :01:00.0: Direct firmware load for
> nouveau/nv106_fuc084d failed with error -2
> [16014.029789] nouveau :01:00.0: msvld: unable to load firmware data
> [16014.029792] nouveau :01:00.0: msvld: init failed, -19
> [86845.159048] WARNING: CPU: 109 PID: 897 at
> drivers/gpu/drm/nouveau/nvif/vmm.c:68 nvif_vmm_put+0x6a/0x80 [nouveau]
> [86845.159209]  x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic
> hid_apple uas usb_storage sd_mod hid_generic usbhid hid nouveau mxm_wmi
> nvme video ahci ttm libahci nvme_core xhci_pci drm_kms_helper libata t10_pi
> crc32_pclmul igb xhci_hcd cec crc32c_intel crc_t10dif e1000e dca
> crct10dif_generic scsi_mod crct10dif_pclmul ptp drm usbcore
> crct10dif_common pps_core i2c_algo_bit i2c_piix4 usb_common wmi button
> [last unloaded: cpuid]
> [86845.159348] Workqueue: events nouveau_cli_work [nouveau]
> [86845.159380] RIP: 0010:nvif_vmm_put+0x6a/0x80 [nouveau]
> [86845.159439]  nouveau_vma_del+0x78/0xc0 [nouveau]
> [86845.159480]  nouveau_gem_object_delete_work+0x36/0x60 [nouveau]
> [86845.159526]  nouveau_cli_work+0xcc/0x120 [nouveau]
> 
>  #1 SMP Debian 5.10.70-1 (2021-09-30) x86_64 GNU/Linux

I'm not sure what this is meant to show. Looking at the timestamps,
this machine was booted at about tea-time yesterday, but some of
the software that might be required was only downloaded and installed
this morning. I think it needs rebooting.

Cheers,
David.



Re: computer screen blink

2021-10-22 Thread Greg Wooledge
On Fri, Oct 22, 2021 at 11:55:12AM +0200, Jerome BENOIT wrote:
> My mistake, you are using the stable Debian:
> you may replace the buster-backports by  bullseye-backports

If she's running bullseye (or trying to do so), she'll need to change
the security line as well.  It's still in the old "buster/updates" format.



Re: computer screen blink

2021-10-22 Thread Greg Wooledge
On Fri, Oct 22, 2021 at 11:38:56AM +0200, lina wrote:
> ## Debian Main Repos
> deb http://deb.debian.org/debian/ stable main contrib non-free
> deb-src http://deb.debian.org/debian/ stable main contrib non-free
> 
> deb http://deb.debian.org/debian/ stable-updates main contrib non-free
> deb-src http://deb.debian.org/debian/ stable-updates main contrib non-free
> 
> deb http://deb.debian.org/debian-security stable/updates main
> deb-src http://deb.debian.org/debian-security stable/updates main
> 
> deb http://ftp.debian.org/debian buster-backports main
> deb-src http://ftp.debian.org/debian buster-backports main

You should never use the word "stable" in your sources.list.  This
is going to cause you immense problems when a new version of Debian
is released.  (This may already have happened to you.)

If you're running a stable (or older) version of Debian, you should
use its release codename in the sources.list file instead.  E.g.
"buster" or "bullseye", where you have "stable".

This looks like it's the sources.list from a buster (Debian 10) system.
I can tell, not only because you have buster-backports listed, but
also because of the format of the debian-security line.  This file is
still using the older "releasename/updates" field, rather than the
newer "releasename-security" field which began with bullseye (Debian 11).

If this is the case, I would urge you to change all instance of "stable"
to "buster" immediately.  Before you break anything (more?) by accident.



Re: computer screen blink

2021-10-22 Thread Dan Ritter
Hans wrote: 
> Am Freitag, 22. Oktober 2021, 11:38:56 CEST schrieb lina:
> If you do not want to use the nvidia-drivers, then make sure, the driver 
> correct GPU is adressed. There are sometimes notebooks with 2 graphics cards: 
> one is built within the cpu (especially intel and amd), and the other one is 
> external. Make sure, that only one graphics card is accessable (I would 
> choose 
> the better one withg 3d acceleration). To do so, you might either deactivate 
> it in BIOS (but that may not work!) or use some software solutiuon like 
> bb-switch or similar (it is in the repo).

This cpu does not have a built-in GPU, so this is not a problem.

-dsr-



Re: computer screen blink

2021-10-22 Thread Hans
Am Freitag, 22. Oktober 2021, 11:38:56 CEST schrieb lina:

Ok, did you install the nvidia-packages for your graphics card? 
If yes, please make sure, you blacklist the nouveau kernel module.

If not, you may try these.

If you do not want to use the nvidia-drivers, then make sure, the driver 
correct GPU is adressed. There are sometimes notebooks with 2 graphics cards: 
one is built within the cpu (especially intel and amd), and the other one is 
external. Make sure, that only one graphics card is accessable (I would choose 
the better one withg 3d acceleration). To do so, you might either deactivate 
it in BIOS (but that may not work!) or use some software solutiuon like 
bb-switch or similar (it is in the repo).

Also check, if you set the correct solution. This can be forded by using 
xorg.conf (today xorg.conf is generally no more needed), but with an existing 
xorg.conf you are able to force things.

When you have got a blank screen only at boot time but then it is ok when 
starting X, then two reasons might be reponsible: 1. Your graphics card or 
mnonitor can not switch to vesa-mode (this problem appeared at my system), or 
your monitor can not work the choosen resolution.

If your monitor is blank at all, then it looks like a wrong set resolution. 
Play with xorg.conf.

If your internal monitor is blank, and the external is working fine, it is 
either a bios setting problem or a setting in your window manager.

If the internal is fine and the external is blank, check the settings in your 
window manager.

On my own system I can not show both screens at boot, only the external is 
shown. This is a bios problem by the manufacturer (Siemens Amilo Notebook) and 
can not be fixed.

Hope this helps a little bit.

Best regards and good luck!

Hans




signature.asc
Description: This is a digitally signed message part.


Re: computer screen blink

2021-10-22 Thread Jerome BENOIT

Hi Again,
nouveau failed to load some firmware.

On 22/10/2021 11:40, lina wrote:

# dmesg | grep -i nouveau
[    1.656164] fb0: switching to nouveaufb from EFI VGA
[    1.656250] nouveau :01:00.0: vgaarb: deactivate vga console
[    1.657164] nouveau :01:00.0: NVIDIA GK208B (b06070b1)
[    1.766995] nouveau :01:00.0: bios: version 80.28.78.00.30
[    1.767490] nouveau :01:00.0: fb: 2048 MiB DDR3
[    1.778993] nouveau :01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT 
domain=0x000d address=0x0 flags=0x]
[    3.117074] nouveau :01:00.0: DRM: VRAM: 2048 MiB
[    3.117075] nouveau :01:00.0: DRM: GART: 1048576 MiB
[    3.117076] nouveau :01:00.0: DRM: TMDS table version 2.0
[    3.117077] nouveau :01:00.0: DRM: DCB version 4.0
[    3.117078] nouveau :01:00.0: DRM: DCB outp 00: 01000f02 00020030
[    3.117078] nouveau :01:00.0: DRM: DCB outp 01: 02011f62 00020010
[    3.117079] nouveau :01:00.0: DRM: DCB outp 02: 02022f10 
[    3.117080] nouveau :01:00.0: DRM: DCB conn 00: 1031
[    3.117080] nouveau :01:00.0: DRM: DCB conn 01: 2161
[    3.117081] nouveau :01:00.0: DRM: DCB conn 02: 0200
[    3.117401] nouveau :01:00.0: DRM: MM: using COPY for buffer copies
[    3.369837] nouveau :01:00.0: DRM: allocated 1920x1080 fb: 0x8, bo 
fd740eca
[    3.369966] fbcon: nouveaudrmfb (fb0) is primary device
[    3.417039] nouveau :01:00.0: [drm] fb0: nouveaudrmfb frame buffer device
[    3.432556] [drm] Initialized nouveau 1.3.1 20120801 for :01:00.0 on 
minor 0
[    4.294574] snd_hda_intel :01:00.1: bound :01:00.0 (ops 
nv50_audio_component_bind_ops [nouveau])
[   52.719911] nouveau :01:00.0: firmware: failed to load 
nouveau/nv106_fuc084 (-2)
[   52.719918] nouveau :01:00.0: Direct firmware load for 
nouveau/nv106_fuc084 failed with error -2
[   52.719926] nouveau :01:00.0: firmware: failed to load 
nouveau/nv106_fuc084d (-2)
[   52.719928] nouveau :01:00.0: Direct firmware load for 
nouveau/nv106_fuc084d failed with error -2
[   52.719930] nouveau :01:00.0: msvld: unable to load firmware data
[   52.719931] nouveau :01:00.0: msvld: init failed, -19
[16000.312421] nouveau :01:00.0: gr: TRAP ch 2 [007fb03000 Xorg[2420]]
[16000.312434] nouveau :01:00.0: gr: GPC0/TPC0/MP trap: global  [] 
warp 3c0009 [ILLEGAL_INSTR_ENCODING]
[16000.332583] nouveau :01:00.0: fifo: fault 00 [READ] at 009f05b4 
engine 00 [GR] client 0d [GPC0/GCC] reason 00 [PDE] on channel 2 [007fb03000 
Xorg[2420]]
[16000.332591] nouveau :01:00.0: fifo: channel 2: killed
[16000.332593] nouveau :01:00.0: fifo: runlist 0: scheduled for recovery
[16000.332597] nouveau :01:00.0: fifo: engine 0: scheduled for recovery
[16000.332603] nouveau :01:00.0: fifo: engine 6: scheduled for recovery
[16000.332626] nouveau :01:00.0: Xorg[2420]: channel 2 killed!
[16014.029755] nouveau :01:00.0: firmware: failed to load 
nouveau/nv106_fuc084 (-2)
[16014.029764] nouveau :01:00.0: Direct firmware load for 
nouveau/nv106_fuc084 failed with error -2
[16014.029782] nouveau :01:00.0: firmware: failed to load 
nouveau/nv106_fuc084d (-2)
[16014.029786] nouveau :01:00.0: Direct firmware load for 
nouveau/nv106_fuc084d failed with error -2
[16014.029789] nouveau :01:00.0: msvld: unable to load firmware data
[16014.029792] nouveau :01:00.0: msvld: init failed, -19
[86845.159048] WARNING: CPU: 109 PID: 897 at 
drivers/gpu/drm/nouveau/nvif/vmm.c:68 nvif_vmm_put+0x6a/0x80 [nouveau]
[86845.159209]  x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic 
hid_apple uas usb_storage sd_mod hid_generic usbhid hid nouveau mxm_wmi nvme 
video ahci ttm libahci nvme_core xhci_pci drm_kms_helper libata t10_pi 
crc32_pclmul igb xhci_hcd cec crc32c_intel crc_t10dif e1000e dca 
crct10dif_generic scsi_mod crct10dif_pclmul ptp drm usbcore crct10dif_common 
pps_core i2c_algo_bit i2c_piix4 usb_common wmi button [last unloaded: cpuid]
[86845.159348] Workqueue: events nouveau_cli_work [nouveau]
[86845.159380] RIP: 0010:nvif_vmm_put+0x6a/0x80 [nouveau]
[86845.159439]  nouveau_vma_del+0x78/0xc0 [nouveau]
[86845.159480]  nouveau_gem_object_delete_work+0x36/0x60 [nouveau]
[86845.159526]  nouveau_cli_work+0xcc/0x120 [nouveau]

  #1 SMP Debian 5.10.70-1 (2021-09-30) x86_64 GNU/Linux

On Fri, Oct 22, 2021 at 11:23 AM Jerome BENOIT mailto:sphericaltrian...@rezozer.net>> wrote:

Hi Lina, so you are mainly playing with a server and you are certnaily used 
an external monitor.
Have you tried with a totally different monitor ?
Are using a VGA terminal or Xorg windows ?
What does dmesg gives against nouveau ?
As root:
# dmesg | grep -i nouveau
What is you actual kernel:
# uname -a
Best whises,
Jerome


On 22/10/2021 10:09, lina wrote:
 > Hi Jerome,
 >
 > It is not a Mac computer.
 >
 > It has only one System, Linux.
 >
 > The hardware should b

Re: computer screen blink

2021-10-22 Thread Jerome BENOIT

My mistake, you are using the stable Debian:
you may replace the buster-backports by  bullseye-backports
Jerome

On 22/10/2021 11:47, Jerome BENOIT wrote:

Hi Lina,
your Debian is actually the old-stable (Buster).
You may consider to upgrade to the new stable (Bullseye)
since you seem to use recent hardware.
Jerome

On 22/10/2021 11:38, lina wrote:

Hi Andrew,

#--#
#                   OFFICIAL DEBIAN REPOS
#--#

## Debian Main Repos
deb http://deb.debian.org/debian/  stable main 
contrib non-free
deb-src http://deb.debian.org/debian/  stable 
main contrib non-free

deb http://deb.debian.org/debian/  
stable-updates main contrib non-free
deb-src http://deb.debian.org/debian/  
stable-updates main contrib non-free

deb http://deb.debian.org/debian-security 
 stable/updates main
deb-src http://deb.debian.org/debian-security 
 stable/updates main

deb http://ftp.debian.org/debian  
buster-backports main
deb-src http://ftp.debian.org/debian  
buster-backports main

#--#
#                      UNOFFICIAL  REPOS
#--#

## 3rd Party Binary Repos
###Debian Multimedia
deb [arch=amd64,i386] https://www.deb-multimedia.org 
 bullseye main non-free


I have just installed the firmware-misc-nonfree and
firmware-linux-nonfree and nvidia-driver.





Re: computer screen blink

2021-10-22 Thread Jerome BENOIT

Hi Lina,
your Debian is actually the old-stable (Buster).
You may consider to upgrade to the new stable (Bullseye)
since you seem to use recent hardware.
Jerome

On 22/10/2021 11:38, lina wrote:

Hi Andrew,

#--#
#                   OFFICIAL DEBIAN REPOS
#--#

## Debian Main Repos
deb http://deb.debian.org/debian/  stable main 
contrib non-free
deb-src http://deb.debian.org/debian/  stable 
main contrib non-free

deb http://deb.debian.org/debian/  
stable-updates main contrib non-free
deb-src http://deb.debian.org/debian/  
stable-updates main contrib non-free

deb http://deb.debian.org/debian-security 
 stable/updates main
deb-src http://deb.debian.org/debian-security 
 stable/updates main

deb http://ftp.debian.org/debian  
buster-backports main
deb-src http://ftp.debian.org/debian  
buster-backports main

#--#
#                      UNOFFICIAL  REPOS
#--#

## 3rd Party Binary Repos
###Debian Multimedia
deb [arch=amd64,i386] https://www.deb-multimedia.org 
 bullseye main non-free


I have just installed the firmware-misc-nonfree and
firmware-linux-nonfree and nvidia-driver.

Thanks and hope it will work.

Best regards, lina

On Fri, Oct 22, 2021 at 11:18 AM Andrew M.A. Cater mailto:amaca...@einval.com>> wrote:

Hi Lina,

This is a relatively new computer. Do you have the non-free AMD firmware
isntalled?

The packages you probably want are firmware-misc-nonfree and
firmware-linux-nonfree

Does the /etc/apt/sources.list file include entries for contrib and 
non-free?

What is the model of your video adapter: if I remember, you have an NVidia
card in there? [Nvidia GT730]. Optionally, you can install proprietary
Nvidia drivers -
https://wiki.debian.org/NvidiaGraphicsDrivers#Version_460.91.03 


Hope this helps narrow down the problem.

All the very best, as ever,

Andy Cater


On Fri, Oct 22, 2021 at 10:09:53AM +0200, lina wrote:
 > Hi Jerome,
 >
 > It is not a Mac computer.
 >
 > It has only one System, Linux.
 >
 > The hardware should be fine as it happens after A BIG UPdating of the
 > system.
 >
 > Howere, below is the hardware info. for your information,
 >
 > # lspci
 > 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
 > Root Complex
 > 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU
 > 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
 > PCIe Dummy Host Bridge
 > 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse 
GPP
 > Bridge
 > 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
 > PCIe Dummy Host Bridge
 > 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
 > PCIe Dummy Host Bridge
 > 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
 > PCIe Dummy Host Bridge
 > 00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
 > PCIe Dummy Host Bridge
 > 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
 > PCIe Dummy Host Bridge
 > 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
 > Internal PCIe GPP Bridge 0 to bus[E:B]
 > 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
 > PCIe Dummy Host Bridge
 > 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
 > Internal PCIe GPP Bridge 0 to bus[E:B]
 > 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller 
(rev
 > 61)
 > 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge 
(rev
 > 51)
 > 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 
24;
 > Function 0
 > 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 
24;
 > Function 1
 > 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 
24;
 > Function 2
 > 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 
24;
 > Function 3
 > 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 
24;
 > Function 4
 > 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 
24;
 > Function 5
 > 00:18.6 

Re: computer screen blink

2021-10-22 Thread lina
# dmesg | grep -i nouveau
[1.656164] fb0: switching to nouveaufb from EFI VGA
[1.656250] nouveau :01:00.0: vgaarb: deactivate vga console
[1.657164] nouveau :01:00.0: NVIDIA GK208B (b06070b1)
[1.766995] nouveau :01:00.0: bios: version 80.28.78.00.30
[1.767490] nouveau :01:00.0: fb: 2048 MiB DDR3
[1.778993] nouveau :01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT
domain=0x000d address=0x0 flags=0x]
[3.117074] nouveau :01:00.0: DRM: VRAM: 2048 MiB
[3.117075] nouveau :01:00.0: DRM: GART: 1048576 MiB
[3.117076] nouveau :01:00.0: DRM: TMDS table version 2.0
[3.117077] nouveau :01:00.0: DRM: DCB version 4.0
[3.117078] nouveau :01:00.0: DRM: DCB outp 00: 01000f02 00020030
[3.117078] nouveau :01:00.0: DRM: DCB outp 01: 02011f62 00020010
[3.117079] nouveau :01:00.0: DRM: DCB outp 02: 02022f10 
[3.117080] nouveau :01:00.0: DRM: DCB conn 00: 1031
[3.117080] nouveau :01:00.0: DRM: DCB conn 01: 2161
[3.117081] nouveau :01:00.0: DRM: DCB conn 02: 0200
[3.117401] nouveau :01:00.0: DRM: MM: using COPY for buffer copies
[3.369837] nouveau :01:00.0: DRM: allocated 1920x1080 fb: 0x8,
bo fd740eca
[3.369966] fbcon: nouveaudrmfb (fb0) is primary device
[3.417039] nouveau :01:00.0: [drm] fb0: nouveaudrmfb frame buffer
device
[3.432556] [drm] Initialized nouveau 1.3.1 20120801 for :01:00.0 on
minor 0
[4.294574] snd_hda_intel :01:00.1: bound :01:00.0 (ops
nv50_audio_component_bind_ops [nouveau])
[   52.719911] nouveau :01:00.0: firmware: failed to load
nouveau/nv106_fuc084 (-2)
[   52.719918] nouveau :01:00.0: Direct firmware load for
nouveau/nv106_fuc084 failed with error -2
[   52.719926] nouveau :01:00.0: firmware: failed to load
nouveau/nv106_fuc084d (-2)
[   52.719928] nouveau :01:00.0: Direct firmware load for
nouveau/nv106_fuc084d failed with error -2
[   52.719930] nouveau :01:00.0: msvld: unable to load firmware data
[   52.719931] nouveau :01:00.0: msvld: init failed, -19
[16000.312421] nouveau :01:00.0: gr: TRAP ch 2 [007fb03000 Xorg[2420]]
[16000.312434] nouveau :01:00.0: gr: GPC0/TPC0/MP trap: global 
[] warp 3c0009 [ILLEGAL_INSTR_ENCODING]
[16000.332583] nouveau :01:00.0: fifo: fault 00 [READ] at
009f05b4 engine 00 [GR] client 0d [GPC0/GCC] reason 00 [PDE] on
channel 2 [007fb03000 Xorg[2420]]
[16000.332591] nouveau :01:00.0: fifo: channel 2: killed
[16000.332593] nouveau :01:00.0: fifo: runlist 0: scheduled for recovery
[16000.332597] nouveau :01:00.0: fifo: engine 0: scheduled for recovery
[16000.332603] nouveau :01:00.0: fifo: engine 6: scheduled for recovery
[16000.332626] nouveau :01:00.0: Xorg[2420]: channel 2 killed!
[16014.029755] nouveau :01:00.0: firmware: failed to load
nouveau/nv106_fuc084 (-2)
[16014.029764] nouveau :01:00.0: Direct firmware load for
nouveau/nv106_fuc084 failed with error -2
[16014.029782] nouveau :01:00.0: firmware: failed to load
nouveau/nv106_fuc084d (-2)
[16014.029786] nouveau :01:00.0: Direct firmware load for
nouveau/nv106_fuc084d failed with error -2
[16014.029789] nouveau :01:00.0: msvld: unable to load firmware data
[16014.029792] nouveau :01:00.0: msvld: init failed, -19
[86845.159048] WARNING: CPU: 109 PID: 897 at
drivers/gpu/drm/nouveau/nvif/vmm.c:68 nvif_vmm_put+0x6a/0x80 [nouveau]
[86845.159209]  x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic
hid_apple uas usb_storage sd_mod hid_generic usbhid hid nouveau mxm_wmi
nvme video ahci ttm libahci nvme_core xhci_pci drm_kms_helper libata t10_pi
crc32_pclmul igb xhci_hcd cec crc32c_intel crc_t10dif e1000e dca
crct10dif_generic scsi_mod crct10dif_pclmul ptp drm usbcore
crct10dif_common pps_core i2c_algo_bit i2c_piix4 usb_common wmi button
[last unloaded: cpuid]
[86845.159348] Workqueue: events nouveau_cli_work [nouveau]
[86845.159380] RIP: 0010:nvif_vmm_put+0x6a/0x80 [nouveau]
[86845.159439]  nouveau_vma_del+0x78/0xc0 [nouveau]
[86845.159480]  nouveau_gem_object_delete_work+0x36/0x60 [nouveau]
[86845.159526]  nouveau_cli_work+0xcc/0x120 [nouveau]

 #1 SMP Debian 5.10.70-1 (2021-09-30) x86_64 GNU/Linux

On Fri, Oct 22, 2021 at 11:23 AM Jerome BENOIT <
sphericaltrian...@rezozer.net> wrote:

> Hi Lina, so you are mainly playing with a server and you are certnaily
> used an external monitor.
> Have you tried with a totally different monitor ?
> Are using a VGA terminal or Xorg windows ?
> What does dmesg gives against nouveau ?
> As root:
> # dmesg | grep -i nouveau
> What is you actual kernel:
> # uname -a
> Best whises,
> Jerome
>
>
> On 22/10/2021 10:09, lina wrote:
> > Hi Jerome,
> >
> > It is not a Mac computer.
> >
> > It has only one System, Linux.
> >
> > The hardware should be fine as it happens after A BIG UPdating of the
> system.
> >
> > Howere, below is the hardware info. for your information,
> >
> > # lspci
> > 00:00.0

Re: computer screen blink

2021-10-22 Thread lina
Hi Andrew,

#--#
#   OFFICIAL DEBIAN REPOS
#--#

## Debian Main Repos
deb http://deb.debian.org/debian/ stable main contrib non-free
deb-src http://deb.debian.org/debian/ stable main contrib non-free

deb http://deb.debian.org/debian/ stable-updates main contrib non-free
deb-src http://deb.debian.org/debian/ stable-updates main contrib non-free

deb http://deb.debian.org/debian-security stable/updates main
deb-src http://deb.debian.org/debian-security stable/updates main

deb http://ftp.debian.org/debian buster-backports main
deb-src http://ftp.debian.org/debian buster-backports main

#--#
#  UNOFFICIAL  REPOS
#--#

## 3rd Party Binary Repos
###Debian Multimedia
deb [arch=amd64,i386] https://www.deb-multimedia.org bullseye main non-free


I have just installed the firmware-misc-nonfree and
firmware-linux-nonfree and nvidia-driver.

Thanks and hope it will work.

Best regards, lina

On Fri, Oct 22, 2021 at 11:18 AM Andrew M.A. Cater 
wrote:

> Hi Lina,
>
> This is a relatively new computer. Do you have the non-free AMD firmware
> isntalled?
>
> The packages you probably want are firmware-misc-nonfree and
> firmware-linux-nonfree
>
> Does the /etc/apt/sources.list file include entries for contrib and
> non-free?
>
> What is the model of your video adapter: if I remember, you have an NVidia
> card in there? [Nvidia GT730]. Optionally, you can install proprietary
> Nvidia drivers -
> https://wiki.debian.org/NvidiaGraphicsDrivers#Version_460.91.03
>
> Hope this helps narrow down the problem.
>
> All the very best, as ever,
>
> Andy Cater
>
>
> On Fri, Oct 22, 2021 at 10:09:53AM +0200, lina wrote:
> > Hi Jerome,
> >
> > It is not a Mac computer.
> >
> > It has only one System, Linux.
> >
> > The hardware should be fine as it happens after A BIG UPdating of the
> > system.
> >
> > Howere, below is the hardware info. for your information,
> >
> > # lspci
> > 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
> > Root Complex
> > 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU
> > 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
> > PCIe Dummy Host Bridge
> > 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
> GPP
> > Bridge
> > 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
> > PCIe Dummy Host Bridge
> > 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
> > PCIe Dummy Host Bridge
> > 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
> > PCIe Dummy Host Bridge
> > 00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
> > PCIe Dummy Host Bridge
> > 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
> > PCIe Dummy Host Bridge
> > 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
> > Internal PCIe GPP Bridge 0 to bus[E:B]
> > 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
> > PCIe Dummy Host Bridge
> > 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
> > Internal PCIe GPP Bridge 0 to bus[E:B]
> > 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller
> (rev
> > 61)
> > 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge
> (rev
> > 51)
> > 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device
> 24;
> > Function 0
> > 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device
> 24;
> > Function 1
> > 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device
> 24;
> > Function 2
> > 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device
> 24;
> > Function 3
> > 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device
> 24;
> > Function 4
> > 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device
> 24;
> > Function 5
> > 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device
> 24;
> > Function 6
> > 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device
> 24;
> > Function 7
> > 01:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT
> > 730] (rev a1)
> > 01:00.1 Audio device: NVIDIA Corporation GK208 HDMI/DP Audio Controller
> > (rev a1)
> > 02:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices,
> Inc.
> > [AMD] Starship/Matisse PCIe Dummy Function
> > 03:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices,
> Inc.
> > [AMD] Starship/Matisse Reserved SPP
> > 03:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Starship USB
> 3.0
> > Host Controller
> > 20:00.0 Host bridge: Advanced Micro Devices, Inc

Re: computer screen blink

2021-10-22 Thread Jerome BENOIT

Hi Lina, so you are mainly playing with a server and you are certnaily used an 
external monitor.
Have you tried with a totally different monitor ?
Are using a VGA terminal or Xorg windows ?
What does dmesg gives against nouveau ?
As root:
# dmesg | grep -i nouveau
What is you actual kernel:
# uname -a
Best whises,
Jerome


On 22/10/2021 10:09, lina wrote:

Hi Jerome,

It is not a Mac computer.

It has only one System, Linux.

The hardware should be fine as it happens after A BIG UPdating of the system.

Howere, below is the hardware info. for your information,

# lspci
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root 
Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe 
Dummy Host Bridge
00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP 
Bridge
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe 
Dummy Host Bridge
00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe 
Dummy Host Bridge
00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe 
Dummy Host Bridge
00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe 
Dummy Host Bridge
00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe 
Dummy Host Bridge
00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse 
Internal PCIe GPP Bridge 0 to bus[E:B]
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe 
Dummy Host Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse 
Internal PCIe GPP Bridge 0 to bus[E:B]
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; 
Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; 
Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; 
Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; 
Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; 
Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; 
Function 5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; 
Function 6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; 
Function 7
01:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT 730] 
(rev a1)
01:00.1 Audio device: NVIDIA Corporation GK208 HDMI/DP Audio Controller (rev a1)
02:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. 
[AMD] Starship/Matisse PCIe Dummy Function
03:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. 
[AMD] Starship/Matisse Reserved SPP
03:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0 
Host Controller
20:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root 
Complex
20:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU
20:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe 
Dummy Host Bridge
20:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe 
Dummy Host Bridge
20:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe 
Dummy Host Bridge
20:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe 
Dummy Host Bridge
20:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe 
Dummy Host Bridge
20:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe 
Dummy Host Bridge
20:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse 
Internal PCIe GPP Bridge 0 to bus[E:B]
20:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe 
Dummy Host Bridge
20:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse 
Internal PCIe GPP Bridge 0 to bus[E:B]
21:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. 
[AMD] Starship/Matisse PCIe Dummy Function
22:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. 
[AMD] Starship/Matisse Reserved SPP
22:00.1 Encryption controller: Advanced Micro Devices, Inc. [AMD] 
Starship/Matisse Cryptographic Coprocessor PSPCPP
22:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0 
Host Controller
22:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD 
Audio Controller
40:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root 
Complex
40:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU
40:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe 
Dummy Host Bridge
40:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starshi

Re: computer screen blink

2021-10-22 Thread Andrew M.A. Cater
Hi Lina,

This is a relatively new computer. Do you have the non-free AMD firmware
isntalled?

The packages you probably want are firmware-misc-nonfree and 
firmware-linux-nonfree

Does the /etc/apt/sources.list file include entries for contrib and non-free?

What is the model of your video adapter: if I remember, you have an NVidia
card in there? [Nvidia GT730]. Optionally, you can install proprietary
Nvidia drivers - 
https://wiki.debian.org/NvidiaGraphicsDrivers#Version_460.91.03

Hope this helps narrow down the problem.

All the very best, as ever,

Andy Cater


On Fri, Oct 22, 2021 at 10:09:53AM +0200, lina wrote:
> Hi Jerome,
> 
> It is not a Mac computer.
> 
> It has only one System, Linux.
> 
> The hardware should be fine as it happens after A BIG UPdating of the
> system.
> 
> Howere, below is the hardware info. for your information,
> 
> # lspci
> 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
> Root Complex
> 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU
> 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
> PCIe Dummy Host Bridge
> 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP
> Bridge
> 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
> PCIe Dummy Host Bridge
> 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
> PCIe Dummy Host Bridge
> 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
> PCIe Dummy Host Bridge
> 00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
> PCIe Dummy Host Bridge
> 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
> PCIe Dummy Host Bridge
> 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
> Internal PCIe GPP Bridge 0 to bus[E:B]
> 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
> PCIe Dummy Host Bridge
> 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
> Internal PCIe GPP Bridge 0 to bus[E:B]
> 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev
> 61)
> 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev
> 51)
> 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24;
> Function 0
> 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24;
> Function 1
> 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24;
> Function 2
> 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24;
> Function 3
> 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24;
> Function 4
> 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24;
> Function 5
> 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24;
> Function 6
> 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24;
> Function 7
> 01:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT
> 730] (rev a1)
> 01:00.1 Audio device: NVIDIA Corporation GK208 HDMI/DP Audio Controller
> (rev a1)
> 02:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc.
> [AMD] Starship/Matisse PCIe Dummy Function
> 03:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc.
> [AMD] Starship/Matisse Reserved SPP
> 03:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0
> Host Controller
> 20:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
> Root Complex
> 20:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU
> 20:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
> PCIe Dummy Host Bridge
> 20:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
> PCIe Dummy Host Bridge
> 20:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
> PCIe Dummy Host Bridge
> 20:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
> PCIe Dummy Host Bridge
> 20:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
> PCIe Dummy Host Bridge
> 20:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
> PCIe Dummy Host Bridge
> 20:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
> Internal PCIe GPP Bridge 0 to bus[E:B]
> 20:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
> PCIe Dummy Host Bridge
> 20:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
> Internal PCIe GPP Bridge 0 to bus[E:B]
> 21:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc.
> [AMD] Starship/Matisse PCIe Dummy Function
> 22:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc.
> [AMD] Starship/Matisse Reserved SPP
> 22:00.1 Encryption controller: Advanced Micro Devices, Inc. [AMD]
> Starship/Matisse Cryptographic Coprocessor PSPCPP
> 22:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0
> Host Controll

Re: computer screen blink

2021-10-22 Thread lina
Hi Jerome,

It is not a Mac computer.

It has only one System, Linux.

The hardware should be fine as it happens after A BIG UPdating of the
system.

Howere, below is the hardware info. for your information,

# lspci
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
Root Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
PCIe Dummy Host Bridge
00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP
Bridge
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
PCIe Dummy Host Bridge
00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
PCIe Dummy Host Bridge
00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
PCIe Dummy Host Bridge
00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
PCIe Dummy Host Bridge
00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
PCIe Dummy Host Bridge
00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
Internal PCIe GPP Bridge 0 to bus[E:B]
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
PCIe Dummy Host Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
Internal PCIe GPP Bridge 0 to bus[E:B]
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev
61)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev
51)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24;
Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24;
Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24;
Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24;
Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24;
Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24;
Function 5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24;
Function 6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24;
Function 7
01:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT
730] (rev a1)
01:00.1 Audio device: NVIDIA Corporation GK208 HDMI/DP Audio Controller
(rev a1)
02:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc.
[AMD] Starship/Matisse PCIe Dummy Function
03:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc.
[AMD] Starship/Matisse Reserved SPP
03:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0
Host Controller
20:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
Root Complex
20:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU
20:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
PCIe Dummy Host Bridge
20:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
PCIe Dummy Host Bridge
20:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
PCIe Dummy Host Bridge
20:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
PCIe Dummy Host Bridge
20:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
PCIe Dummy Host Bridge
20:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
PCIe Dummy Host Bridge
20:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
Internal PCIe GPP Bridge 0 to bus[E:B]
20:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
PCIe Dummy Host Bridge
20:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
Internal PCIe GPP Bridge 0 to bus[E:B]
21:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc.
[AMD] Starship/Matisse PCIe Dummy Function
22:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc.
[AMD] Starship/Matisse Reserved SPP
22:00.1 Encryption controller: Advanced Micro Devices, Inc. [AMD]
Starship/Matisse Cryptographic Coprocessor PSPCPP
22:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0
Host Controller
22:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
HD Audio Controller
40:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
Root Complex
40:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU
40:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
PCIe Dummy Host Bridge
40:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP
Bridge
40:01.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP
Bridge
40:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
PCIe Dummy Host Bridge
40:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
PCIe Dummy Host Bridge
40:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse
PCIe Dummy Host Bridge
40:05.0 H

Re: computer screen blink

2021-10-22 Thread lina
Hi Andrew,

I have fixed the updating system. Now it looks like this:

# aptitude full-upgrade
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.



It is just blinking, nothing warning signs shows up.

It happened after my last update.

On Thu, Oct 21, 2021 at 10:58 AM Andrew M.A. Cater 
wrote:

> On Thu, Oct 21, 2021 at 09:50:06AM +0200, lina wrote:
> > # aptitude full-upgrade
> > The following NEW packages will be installed:
> >   libebook-1.2-20{a} libebook-contacts-1.2-3{a} libedata-book-1.2-26{a}
> >   libedata-cal-2.0-1{a} libphonenumber8{a} libprotobuf23{a}
> > The following packages will be REMOVED:
> >   libgweather-3-15{u}
> > The following packages will be upgraded:
> >   evolution-data-server libcamel-1.2-62 libebackend-1.2-10
> libebook-1.2-19
> >   libebook-contacts-1.2-2 libecal-1.2-19 libedata-book-1.2-25{b}
> >   libedata-cal-1.2-29{b} libedataserver-1.2-23 libedataserverui-1.2-2
> > 10 packages upgraded, 6 newly installed, 1 to remove and 0 not upgraded.
> > Need to get 4,070 kB of archives. After unpacking 5,918 kB will be used.
> > The following packages have unmet dependencies:
> >  libedata-book-1.2-25 : Depends: libebackend-1.2-10 (=
> 3.30.5-1.1~bpo10+1)
> > but 3.38.3-1 is to be installed
> >  libedata-cal-1.2-29 : Depends: libebackend-1.2-10 (= 3.30.5-1.1~bpo10+1)
> > but 3.38.3-1 is to be installed
> > The following actions will resolve these dependencies:
> >
> >   Keep the following packages at their current version:
> > 1)  evolution-data-server [3.30.5-1+deb10u1 (now)]
> > 2)  libcamel-1.2-62 [3.30.5-1+deb10u1 (now)]
> > 3)  libebackend-1.2-10 [3.30.5-1+deb10u1 (now)]
> > 4)  libebook-1.2-19 [3.30.5-1+deb10u1 (now)]
> > 5)  libebook-1.2-20 [Not Installed]
> > 6)  libebook-contacts-1.2-2 [3.30.5-1+deb10u1 (now)]
> > 7)  libecal-1.2-19 [3.30.5-1+deb10u1 (now)]
> > 8)  libedata-book-1.2-25 [3.30.5-1+deb10u1 (now)]
> > 9)  libedata-book-1.2-26 [Not Installed]
> > 10) libedata-cal-1.2-29 [3.30.5-1+deb10u1 (now)]
> > 11) libedata-cal-2.0-1 [Not Installed]
> > 12) libedataserver-1.2-23 [3.30.5-1+deb10u1 (now)]
> > 13) libedataserverui-1.2-2 [3.30.5-1+deb10u1 (now)]
> > 14) libgweather-3-15 [3.28.2-2 (now)]
> >
>
> Hi Lina
>
> Try running aptitude update - to pull the updated list of packages - then
> aptitude full-upgrade - you shouldn't see those sorts of inconsistencies.
>
> Bullseye - Debian 11 - OK.
>
> Temperature issue - only thinking that if it was something that only
> happens after a long time, it might be because a componetn inside your
> screen warms up / misbehaves.
>
> Does anything else happen just before it all locks up?
>
> All the very best, as ever,
>
> Andy Cater
> >
> >
> > Accept this solution? [Y/n/q/?] Y
> > No packages will be installed, upgraded, or removed.
> > 0 packages upgraded, 0 newly installed, 0 to remove and 10 not upgraded.
> > Need to get 0 B of archives. After unpacking 0 B will be used.
> >
> > Distributor ID: Debian
> > Description: Debian GNU/Linux 11 (bullseye)
> > Release: 11
> > Codename: bullseye
> >
> > How do I know it is a temperature issue?
> >
> >
> >
> > On Wed, Oct 20, 2021 at 3:22 PM Andrew M.A. Cater 
> > wrote:
> >
> > > On Wed, Oct 20, 2021 at 02:42:11PM +0200, lina wrote:
> > > > Hi all,
> > > >
> > > > After using the computer for a long while, my screen will blink.
> > > >
> > > > It has been months since the last time I upgraded the system.
> > > >
> > > > I don't know how to start checking, every time I have to reboot the
> > > > computer,
> > > >
> > > > would be great to get your advice,
> > > >
> > > > thanks,
> > >
> > > First things first: update your computer. Security fixes and fixes for
> > > other problems come out all the time.
> > >
> > > What Debian version are you running?
> > >
> > > On what sort of computer?
> > >
> > > Do you have screensavers or similar kicking in?
> > >
> > > is there a temperature issue?
> > >
> > > Are there logs?
> > >
> > > A little more information would be helpful.
> > >
> > > All the very best, as ever,
> > >
> > > Andy Cater
> > >
> > >
>
>


Re: computer screen blink

2021-10-21 Thread Jerome BENOIT

Hi,
you may fist determine if it is a hardware issue or a software issue.
Some Mac screens are known to flicker after a while.
What is your computer ? Can you boot on Windows/MacOS to see if the same thing 
happens ?
Knowing your hardware may help a lot.
hth,
Jerome

On 21/10/2021 10:51, lina wrote:

k10temp-pci-00c3
Adapter: PCI adapter
Tctl:         +62.6°C
Tdie:         +62.6°C
Tccd1:        +45.2°C
Tccd2:        +62.8°C
Tccd3:        +60.8°C
Tccd4:        +45.8°C
Tccd5:        +43.8°C
Tccd6:        +45.2°C
Tccd7:        +43.5°C
Tccd8:        +43.5°C

nvme-pci-4800
Adapter: PCI adapter
Composite:    +34.9°C  (low  =  -0.1°C, high = +89.8°C)
                        (crit = +94.8°C)

nouveau-pci-0100
Adapter: PCI adapter
GPU core:    912.00 mV (min =  +0.80 V, max =  +1.19 V)
temp1:        +34.0°C  (high = +95.0°C, hyst =  +3.0°C)
                        (crit = +105.0°C, hyst =  +5.0°C)
                        (emerg = +135.0°C, hyst =  +5.0°C)

On Wed, Oct 20, 2021 at 3:22 PM Andrew M.A. Cater mailto:amaca...@einval.com>> wrote:

On Wed, Oct 20, 2021 at 02:42:11PM +0200, lina wrote:
 > Hi all,
 >
 > After using the computer for a long while, my screen will blink.
 >
 > It has been months since the last time I upgraded the system.
 >
 > I don't know how to start checking, every time I have to reboot the
 > computer,
 >
 > would be great to get your advice,
 >
 > thanks,

First things first: update your computer. Security fixes and fixes for
other problems come out all the time.

What Debian version are you running?

On what sort of computer?

Do you have screensavers or similar kicking in?

is there a temperature issue?

Are there logs?

A little more information would be helpful.

All the very best, as ever,

Andy Cater





Re: computer screen blink

2021-10-21 Thread Andrew M.A. Cater
On Thu, Oct 21, 2021 at 09:50:06AM +0200, lina wrote:
> # aptitude full-upgrade
> The following NEW packages will be installed:
>   libebook-1.2-20{a} libebook-contacts-1.2-3{a} libedata-book-1.2-26{a}
>   libedata-cal-2.0-1{a} libphonenumber8{a} libprotobuf23{a}
> The following packages will be REMOVED:
>   libgweather-3-15{u}
> The following packages will be upgraded:
>   evolution-data-server libcamel-1.2-62 libebackend-1.2-10 libebook-1.2-19
>   libebook-contacts-1.2-2 libecal-1.2-19 libedata-book-1.2-25{b}
>   libedata-cal-1.2-29{b} libedataserver-1.2-23 libedataserverui-1.2-2
> 10 packages upgraded, 6 newly installed, 1 to remove and 0 not upgraded.
> Need to get 4,070 kB of archives. After unpacking 5,918 kB will be used.
> The following packages have unmet dependencies:
>  libedata-book-1.2-25 : Depends: libebackend-1.2-10 (= 3.30.5-1.1~bpo10+1)
> but 3.38.3-1 is to be installed
>  libedata-cal-1.2-29 : Depends: libebackend-1.2-10 (= 3.30.5-1.1~bpo10+1)
> but 3.38.3-1 is to be installed
> The following actions will resolve these dependencies:
> 
>   Keep the following packages at their current version:
> 1)  evolution-data-server [3.30.5-1+deb10u1 (now)]
> 2)  libcamel-1.2-62 [3.30.5-1+deb10u1 (now)]
> 3)  libebackend-1.2-10 [3.30.5-1+deb10u1 (now)]
> 4)  libebook-1.2-19 [3.30.5-1+deb10u1 (now)]
> 5)  libebook-1.2-20 [Not Installed]
> 6)  libebook-contacts-1.2-2 [3.30.5-1+deb10u1 (now)]
> 7)  libecal-1.2-19 [3.30.5-1+deb10u1 (now)]
> 8)  libedata-book-1.2-25 [3.30.5-1+deb10u1 (now)]
> 9)  libedata-book-1.2-26 [Not Installed]
> 10) libedata-cal-1.2-29 [3.30.5-1+deb10u1 (now)]
> 11) libedata-cal-2.0-1 [Not Installed]
> 12) libedataserver-1.2-23 [3.30.5-1+deb10u1 (now)]
> 13) libedataserverui-1.2-2 [3.30.5-1+deb10u1 (now)]
> 14) libgweather-3-15 [3.28.2-2 (now)]
> 

Hi Lina

Try running aptitude update - to pull the updated list of packages - then
aptitude full-upgrade - you shouldn't see those sorts of inconsistencies.

Bullseye - Debian 11 - OK.

Temperature issue - only thinking that if it was something that only
happens after a long time, it might be because a componetn inside your
screen warms up / misbehaves.

Does anything else happen just before it all locks up?

All the very best, as ever,

Andy Cater
> 
> 
> Accept this solution? [Y/n/q/?] Y
> No packages will be installed, upgraded, or removed.
> 0 packages upgraded, 0 newly installed, 0 to remove and 10 not upgraded.
> Need to get 0 B of archives. After unpacking 0 B will be used.
> 
> Distributor ID: Debian
> Description: Debian GNU/Linux 11 (bullseye)
> Release: 11
> Codename: bullseye
> 
> How do I know it is a temperature issue?
> 
> 
> 
> On Wed, Oct 20, 2021 at 3:22 PM Andrew M.A. Cater 
> wrote:
> 
> > On Wed, Oct 20, 2021 at 02:42:11PM +0200, lina wrote:
> > > Hi all,
> > >
> > > After using the computer for a long while, my screen will blink.
> > >
> > > It has been months since the last time I upgraded the system.
> > >
> > > I don't know how to start checking, every time I have to reboot the
> > > computer,
> > >
> > > would be great to get your advice,
> > >
> > > thanks,
> >
> > First things first: update your computer. Security fixes and fixes for
> > other problems come out all the time.
> >
> > What Debian version are you running?
> >
> > On what sort of computer?
> >
> > Do you have screensavers or similar kicking in?
> >
> > is there a temperature issue?
> >
> > Are there logs?
> >
> > A little more information would be helpful.
> >
> > All the very best, as ever,
> >
> > Andy Cater
> >
> >



Re: computer screen blink

2021-10-21 Thread lina
k10temp-pci-00c3
Adapter: PCI adapter
Tctl: +62.6°C
Tdie: +62.6°C
Tccd1:+45.2°C
Tccd2:+62.8°C
Tccd3:+60.8°C
Tccd4:+45.8°C
Tccd5:+43.8°C
Tccd6:+45.2°C
Tccd7:+43.5°C
Tccd8:+43.5°C

nvme-pci-4800
Adapter: PCI adapter
Composite:+34.9°C  (low  =  -0.1°C, high = +89.8°C)
   (crit = +94.8°C)

nouveau-pci-0100
Adapter: PCI adapter
GPU core:912.00 mV (min =  +0.80 V, max =  +1.19 V)
temp1:+34.0°C  (high = +95.0°C, hyst =  +3.0°C)
   (crit = +105.0°C, hyst =  +5.0°C)
   (emerg = +135.0°C, hyst =  +5.0°C)

On Wed, Oct 20, 2021 at 3:22 PM Andrew M.A. Cater 
wrote:

> On Wed, Oct 20, 2021 at 02:42:11PM +0200, lina wrote:
> > Hi all,
> >
> > After using the computer for a long while, my screen will blink.
> >
> > It has been months since the last time I upgraded the system.
> >
> > I don't know how to start checking, every time I have to reboot the
> > computer,
> >
> > would be great to get your advice,
> >
> > thanks,
>
> First things first: update your computer. Security fixes and fixes for
> other problems come out all the time.
>
> What Debian version are you running?
>
> On what sort of computer?
>
> Do you have screensavers or similar kicking in?
>
> is there a temperature issue?
>
> Are there logs?
>
> A little more information would be helpful.
>
> All the very best, as ever,
>
> Andy Cater
>
>


Re: computer screen blink

2021-10-21 Thread lina
# aptitude full-upgrade
The following NEW packages will be installed:
  libebook-1.2-20{a} libebook-contacts-1.2-3{a} libedata-book-1.2-26{a}
  libedata-cal-2.0-1{a} libphonenumber8{a} libprotobuf23{a}
The following packages will be REMOVED:
  libgweather-3-15{u}
The following packages will be upgraded:
  evolution-data-server libcamel-1.2-62 libebackend-1.2-10 libebook-1.2-19
  libebook-contacts-1.2-2 libecal-1.2-19 libedata-book-1.2-25{b}
  libedata-cal-1.2-29{b} libedataserver-1.2-23 libedataserverui-1.2-2
10 packages upgraded, 6 newly installed, 1 to remove and 0 not upgraded.
Need to get 4,070 kB of archives. After unpacking 5,918 kB will be used.
The following packages have unmet dependencies:
 libedata-book-1.2-25 : Depends: libebackend-1.2-10 (= 3.30.5-1.1~bpo10+1)
but 3.38.3-1 is to be installed
 libedata-cal-1.2-29 : Depends: libebackend-1.2-10 (= 3.30.5-1.1~bpo10+1)
but 3.38.3-1 is to be installed
The following actions will resolve these dependencies:

  Keep the following packages at their current version:
1)  evolution-data-server [3.30.5-1+deb10u1 (now)]
2)  libcamel-1.2-62 [3.30.5-1+deb10u1 (now)]
3)  libebackend-1.2-10 [3.30.5-1+deb10u1 (now)]
4)  libebook-1.2-19 [3.30.5-1+deb10u1 (now)]
5)  libebook-1.2-20 [Not Installed]
6)  libebook-contacts-1.2-2 [3.30.5-1+deb10u1 (now)]
7)  libecal-1.2-19 [3.30.5-1+deb10u1 (now)]
8)  libedata-book-1.2-25 [3.30.5-1+deb10u1 (now)]
9)  libedata-book-1.2-26 [Not Installed]
10) libedata-cal-1.2-29 [3.30.5-1+deb10u1 (now)]
11) libedata-cal-2.0-1 [Not Installed]
12) libedataserver-1.2-23 [3.30.5-1+deb10u1 (now)]
13) libedataserverui-1.2-2 [3.30.5-1+deb10u1 (now)]
14) libgweather-3-15 [3.28.2-2 (now)]



Accept this solution? [Y/n/q/?] Y
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 10 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.

Distributor ID: Debian
Description: Debian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye

How do I know it is a temperature issue?



On Wed, Oct 20, 2021 at 3:22 PM Andrew M.A. Cater 
wrote:

> On Wed, Oct 20, 2021 at 02:42:11PM +0200, lina wrote:
> > Hi all,
> >
> > After using the computer for a long while, my screen will blink.
> >
> > It has been months since the last time I upgraded the system.
> >
> > I don't know how to start checking, every time I have to reboot the
> > computer,
> >
> > would be great to get your advice,
> >
> > thanks,
>
> First things first: update your computer. Security fixes and fixes for
> other problems come out all the time.
>
> What Debian version are you running?
>
> On what sort of computer?
>
> Do you have screensavers or similar kicking in?
>
> is there a temperature issue?
>
> Are there logs?
>
> A little more information would be helpful.
>
> All the very best, as ever,
>
> Andy Cater
>
>


Re: computer screen blink

2021-10-20 Thread Andrew M.A. Cater
On Wed, Oct 20, 2021 at 02:42:11PM +0200, lina wrote:
> Hi all,
> 
> After using the computer for a long while, my screen will blink.
> 
> It has been months since the last time I upgraded the system.
> 
> I don't know how to start checking, every time I have to reboot the
> computer,
> 
> would be great to get your advice,
> 
> thanks,

First things first: update your computer. Security fixes and fixes for
other problems come out all the time.

What Debian version are you running?

On what sort of computer?

Do you have screensavers or similar kicking in?

is there a temperature issue?

Are there logs?

A little more information would be helpful.

All the very best, as ever,

Andy Cater



computer screen blink

2021-10-20 Thread lina
Hi all,

After using the computer for a long while, my screen will blink.

It has been months since the last time I upgraded the system.

I don't know how to start checking, every time I have to reboot the
computer,

would be great to get your advice,

thanks,