Re: openssh server remote access

[Semih Ozlem]

Are there specific tutorials websites that you can recommend, how about
port forwarding. From where which sites in particular can I learn about
these topics?

Joe , 22 Eki 2021 Cum, 00:08 tarihinde şunu yazdı:

> On Thu, 21 Oct 2021 23:48:38 +0300
> Semih Ozlem  wrote:
>
> > I think it was something like "ssh: connect to host  port 22:
> > Connection refused" It will take me a little while to get the same
> > error message again.
> >
> >
>
> Ideally you need to do more than open the ssh port, particularly if you
> intend to connect from the Internet. ssh is one of the most commonly
> attacked services, for obvious reasons.
>
> You need a tutorial on setting up ssh with keys, and disabling password
> access. There are many such on the Net.
>
>
> --
> Joe
>
>

Re: [SOLVED] SDDM doesn't show up at boot

[Cmdte Alpha Tigre Z]

Hi,

El vie, 22 oct 2021 a las 10:50, David Wright
() escribió:
> That may depend on whether you ran it on a "real" VC (rather an
> oxymoron) or on an Alt-Ctrl-Fn console reached from X. I've
> certainly had aspects not work when run in the latter manner,
> particularly /etc/console-setup/remap.inc stuff IIRC.

Excuse me, Mr. Wright, what do you mean by a "real" virtual console?
Those ones you reach by pressing Ctrl+Alt+Fn are virtual consoles,
right?

Well, it is a little confusing.

Have a good day.

-- 
Time zone: GMT-4

Re: eMail Com Between Hosts on a Private Net

[David Wright]

On Fri 22 Oct 2021 at 11:09:14 (-0500), Martin McCormick wrote:

>   I was all ready to use .local as our domain name and then
> I looked that up and there is a good wikipedia article which
> explains how that is problematic and recommends using something
> like .lan, .office or something else that isn't likely to be
> registered as a top-level resolvable domain name.

The three strings that are the most certain never to be registered
as TLDs are .corp, .home and .mail.

https://features.icann.org/addressing-new-gtld-program-applications-corp-home-and-mail

I use .corp merely because it's not a Common Word, and so grepping
for it will hit the least number of false matches.

Cheers,
David.

Re: eMail Com Between Hosts on a Private Net

[Nicholas Geovanis]

On Fri, Oct 22, 2021 at 11:09 AM Martin McCormick 
wrote:

> .
> When I was researching, the article in wikipedia I read
> said that many commercial systems have email clients which
> understand imap, pop3, etc.  The systems likely to do this on our
> network are a windows10 box, an iMac and maybe an iPad.  The idea
>
>
Many corporate environments that are not committed to Microsoft
Exchange/Outlook take this approach.
Even when everyone in the corp uses a Microsoft client to read their mail,
it still may be served internally
with Pop/IMAP. Microsoft email software is not cheap. Of course many corps
use Google mail and it can be used privately, internally. Interactive
messaging and meeting is highly important today: Slack, Bluejeans, skype,
Microsoft Teams.

Thanks again.
>
> Martin McCormick
>
>

Re: eMail Com Between Hosts on a Private Net

[Nicholas Geovanis]

On Wed, Oct 20, 2021 at 8:21 PM Martin McCormick 
wrote:

> 
> My thanks to all who replied and thanks for reminding me of some
> of the considerations one needs to think of when setting this all
> up since that's what I used to do as part of my job before
> retiring in 2015.  As for there being 16 subnets in the
> 192.168.x.x number space, one can use variable-width subnet masks
> 
>
> I remember early in the nineties our campus went from a
> single Class C to a Class B network and the whole campus used the
> Class B subnet mask with bridges holding the whole thing
> together.  You should have seen some of the arp storms that would
> 
> By the time I left, we were using the huge private
> network space of 10.0.0.0 with aNAT or Network Address
> Translation to parts of the old Class B network and it generally
> worked well.
>

Yeah I did that transition a few times in a few organizations :-)


> I wrote a C then a perl program which would assign IP
> addresses for hosts on our networks that knew the sizes of all
> the subnet masks so assigning IP addresses was something anybody
>

Recommending ipcalc to you. You can run it locally standalone or locally
web-served, or invoke it remotely.
Can pretty easily be embedded in your larger perl app. And naturally there
are many perl modules available
to you which do the same in many different ways, contexts, environments.


>
> Martin
>
>

Re: openssh server remote access

[Eric S Fraga]

On Friday, 22 Oct 2021 at 09:46, David Wright wrote:
> I'm guessing it was a BT Home Hub. 

EE *before* bought by BT but maybe same supplier even then.

> One might suspect that 100 lies at the lower boundary of its DHCP
> range, leaving 99 static addresses free. But no guess at a product.

I cannot remember any longer which one supplied this one.  Might have
been Tiscali?

And, yes, leaving 99 static addresses free might be a reason.


-- 
Eric S Fraga via Emacs 28.0.60 & org 9.5 on Debian 11.1

Re: eMail Com Between Hosts on a Private Net

[Joe]

On Fri, 22 Oct 2021 11:09:14 -0500
"Martin McCormick"  wrote:


> 
>   Shouldn't I be able to install an imap server on the
> debian box and forward messages of interest to it, then reach
> imap4 on the private net from any system that speaks imap or has
> an imap client?
>

Yes, certainly. An IMAP server can stand alone and act as an email
repository or archive, accessed by many clients. It doesn't have to be
plumbed into a live email system, it can just appear as an additional
account in email clients which have separate real email accounts
elsewhere.

-- 
Joe

Re: eMail Com Between Hosts on a Private Net

[Martin McCormick]

One more question I should know the answer to but am not sure of.
The debian Buster system I use for email presently uses fetchmail
to get mail from the ISP and is configured to use that ISP's
smarthost for out-going mail.  I do not want to  effect
(= muck this up) this  functionality because  it works well for
now.

Shouldn't I be able to install an imap server on the
debian box and forward messages of interest to it, then reach
imap4 on the private net from any system that speaks imap or has
an imap client?

That would do what I need to do.

When I was researching, the article in wikipedia I read
said that many commercial systems have email clients which
understand imap, pop3, etc.  The systems likely to do this on our
network are a windows10 box, an iMac and maybe an iPad.  The idea
would be to forward an email message needing this attention to
imap on the linux box, contact the Linux box from one of the
devices I mentioned, and download the message at which point it
would e as if that system had been hooked up to the ISP and
received it.

I was all ready to use .local as our domain name and then
I looked that up and there is a good wikipedia article which
explains how that is problematic and recommends using something
like .lan, .office or something else that isn't likely to be
registered as a top-level resolvable domain name.

The machine I receive email on presently would be a good
candidate for running a mdns but our netgear router advertises
whatever dns's the isp uses for obvious reasons and that's fine
but it would be nice if the mdns's address could also be known to clients
on our network which could make DNS queries to each other's names
that would resolve properly.

Is there a way to advertise the mdns so that the router
picks it up but doesn't drop the internet DNS's that we all need
to resolve the rest of the world?

I do remember when I was working, we explored open-source
network authentication systems which involved fake DNS's that one
had to advertise as such so their information wouldn't corrupt
the proper working DNS's which could really mess things up if
somebody happened to pickup and cache the wild card * that sent
all new supplicants to the authentication server after they were
already up and running.

In our case, the corruption would be okay and done for
good reasons but the dhcp server in our router  already advertises two
domain name servers so ours would have to be learned about by
discovery.

Thanks again.

Martin McCormick

Re: computer screen blink

[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

[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: xhost-command in Debian11

[Reco]

Hi.

On Fri, Oct 22, 2021 at 08:25:36AM -0600, Charles Curley wrote:
> charles@jhegaala:~$ su --whitelist-environment=DISPLAY -

It won't be enough. You need this:

su --whitelist-environment=DISPLAY,XAUTHORITY -

Reco

Re: A .profile puzzle

[David Wright]

On Sun 17 Oct 2021 at 17:36:19 (+), Andrew M.A. Cater wrote:
> On Sun, Oct 17, 2021 at 01:23:34PM -0400, Gene Heskett wrote:
> > On Sunday 17 October 2021 12:35:01 deloptes wrote:
> > 
> > > Gene Heskett wrote:
> > > > 1. Before the latest failure I could do all this as me because the
> > > > mount point for the card is in my home directory, I own it all. And
> > > > didn't have to be root to do any of it.  This was not fixed by a 2nd
> > > > reboot.
> > >
> > > I guess this problem is not related to the .profile issue you are
> > > having below.
> > 
> > Agreed.
> > 
> > > Check the permissions on the mount point
> > 
> > done, I still own it.

"done" doesn't quite cover it. We don't know whether something was
mounted on the mount point (which means that the ownership/permissions
apply to the something, not to the mount point), or not (in which case
you see the ownership/permissions of the mount point itself). You made
this error back in February.

> > > and the fstab
> > 
> > its not in fstab, never was.

Which suggests that the real mount point ownership/permissions will be
important.

> > I touched a file in 
> > home/gene/Downloads/3dp.stf named sdb1 to create a mount I didn't have 
> > to search thru /media to access.
> > 
> 
> What on EARTH? This is a very [s]trange way to do this, I think.

Yes, no idea what all that is about.

> Either put it in fstab at which point it will alwsays be found or learn
> where it's mounted under /media - which will be consistent, maybe? 
> Interestingly,mounting an SD card that fits an SD card slot gave me one path, 
> a micro-SDin a holder gave me another but they were always consistent.

My own experience is that the ID (/dev/disk/by-id) varies by what the SD
is pushed into, whereas the Path (/dev/disk/by-path) varies by the PC's
socket that it's plugged into (which could of course be the same).

So any card that's pushed into an SD→USB holder will get the ID of
the holder, but its Path will depend on the USB socket plugged into.

In the absence of any more specific information (ie, a known LABEL or
UUID), I configure fstab to mount the device on /media/slot or
/media/white as appropriate. I find that the easiest way to avoid
confusing two "foreign" SD cards. (The holder is white.)

I assume that microSD→SD converters are passive, as they all behave
as effectively "invisible". I'm not sure how I would test this,
though, because the only microSD slots I have are in mobile phones
and Rokus etc.

> > Up until this 5 second power failure, I could, as me, mount that SD card 
> > there, and use mc, as me, to overwrite a file on that card, then sync; 
> > eject sdb1. Led on card adapter goes out, pull the card, take it back to 
> > the printer and select and print the updated file.  Now I have to be 
> > root to do any of it except the printer. The card is vfat, which has no 
> > concept of file ownership.

Not intrinsically, but ownership/permissions can be imposed upon
mounting it (uid,gid,umask,fmask,dmask).

I think you were using usbmount at one time, and also that you were
having problems with undesired automounting, but I haven't looked
back for details, as I think your configuration is probably too
different from mine for me to be any help with this specific power
outage symptom.

> > > The SD card might also need a fsck.
> > 
> > by whose fsck?
> 
> Make sure it's not mounted, then fsck the device. Probably dosfstools is
> needed.

In my experience, cards and sticks that want a fsck just emit a
message in the logs, rather than refusing to be mounted:

  FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. 
Please run fsck.

That may differ with gross corruption, but I'd expect a lot more noise
in the logs, were that the case.

> > > > 2. and another pesky thing is starting a konsole to do work, needs a
> > > > $PATH modification that we used to put in ~.profile. But opening a
> > > > terminal hasn't called a ". .profile" since about jessie.  So thats
> > > > another PITA.
> > > >
> > > > So, what has replaced .profile as the function for such as that in
> > > > recent releases?
> > >
> > > AFAIK bash is not reading profile when you login, but not sure - it
> > > could be also that it is not a login shell.
> > 
> > XFCe login, I think. I only see it once on that machine. logging in 
> > remotely with "ssh -Y machine-name" or 'user1000'@machine-name is how I 
> > generally run things from a comfy chair.
> > 
> > > AFAIK you should open the terminal with "bash --login" to read the
> > > profile. So try in the terminal "bash --login"

Perhaps start at https://lists.debian.org/debian-user/2020/08/msg00196.html
and work up the thread. That might answer thing (2.), and could even
suggest why a power outage followed by a reboot could change things,
if you'd altered the configuration since the last boot.

Cheers,
David.

Re: [SOLVED] SDDM doesn't show up at boot

[David Wright]

On Wed 20 Oct 2021 at 23:38:05 (-0400), Cmdte Alpha Tigre Z wrote:

> Just after updating Debian to 10.11, the problem was solved.

Good to hear, but sorry it didn't stick. Your next post looks all
to do with DEs and greeters, so out of my experience.

> I tried "dpkg-reconfigure keyboard-configuration" and I have to admit
> it was much easier to use.  It has very well explained steps with full
> keyboard configuration and a straightforward selection process
> among the options.
> 
> Unfortunately, it did not work on the virtual terminal, only on the
> X Window System.

That may depend on whether you ran it on a "real" VC (rather an
oxymoron) or on an Alt-Ctrl-Fn console reached from X. I've
certainly had aspects not work when run in the latter manner,
particularly /etc/console-setup/remap.inc stuff IIRC.

> "localectl" also sets some configuration
> in "/etc/vconsole.conf" but it does not work either.

I've never seen that file, and running localectl didn't create it
either. This part of systemd is as yet unexplored by me. I can only
keep up with a certain amount of change at one time.

> However,
> one of the last steps in the keyboard-configuration
> of dpkg-reconfigure suggested that I could use the keys combination
> Ctrl + . (period) as a compose key (no matter whether I chose
> another key as a compose key); thanks to that, I can now write
> accented letters in the console.

Well, that came as a surprise to me.

Cheers,
David.

Re: openssh server remote access

[David Wright]

On Fri 22 Oct 2021 at 11:59:40 (+0100), Eric S Fraga wrote:
> On Friday, 22 Oct 2021 at 13:40, Andrei POPESCU wrote:
> > Typically modems and home routers use the .1 address for themselves.
> 
> Interesting.  My last 2 routers have had *.254 (!)

I'm guessing it was a BT Home Hub. It's idiosyncratic, but setting
itself to the highest address is as logical as the lowest, is it not.

> and *.100 as their address. 

One might suspect that 100 lies at the lower boundary of its DHCP
range, leaving 99 static addresses free. But no guess at a product.

Cheers,
David.

Re: xhost-command in Debian11

[David Wright]

On Fri 22 Oct 2021 at 08:25:36 (-0600), Charles Curley wrote:
> On Tue, 15 Jun 2021 21:51:28 +0200
>  wrote:
> 
> > Try adding
> > the option `--whitelist-environment=DISPLAY to your su command (hint:
> > you can add more variables to that whitelist, comma separated).
> 
> I just tried this. No joy.
> 
> charles@jhegaala:~$ echo $DISPLAY 
> :0.0
> charles@jhegaala:~$ su -
> Password: 
> 
> Today is Setting Orange, the 3rd of The Aftermath, 3187. P'tang! 
> root@jhegaala:~# exit
> logout
> charles@jhegaala:~$ su --whitelist-environment=DISPLAY -
> Password: 
> 
> Today is Setting Orange, the 3rd of The Aftermath, 3187. This statement is 
> false. 
> root@jhegaala:~# echo $DISPLAY 
> :0.0
> root@jhegaala:~# xclock &
> [1] 311078
> root@jhegaala:~# No protocol specified
> Error: Can't open display: :0.0
> 
> [1]+  Exit 1  xclock
> root@jhegaala:~# emacs &
> [1] 311095
> root@jhegaala:~# No protocol specified
> Display :0.0 unavailable, simulating -nw
> fg
> emacs
> root@jhegaala:~#

I think you need su --whitelist-environment=DISPLAY,XAUTHORITY -

Cheers,
David.

Re: xhost-command in Debian11

[Charles Curley]

On Tue, 15 Jun 2021 21:51:28 +0200
 wrote:

> Try adding
> the option `--whitelist-environment=DISPLAY to your su command (hint:
> you can add more variables to that whitelist, comma separated).

I just tried this. No joy.

charles@jhegaala:~$ echo $DISPLAY 
:0.0
charles@jhegaala:~$ su -
Password: 

Today is Setting Orange, the 3rd of The Aftermath, 3187. P'tang! 
root@jhegaala:~# exit
logout
charles@jhegaala:~$ su --whitelist-environment=DISPLAY -
Password: 

Today is Setting Orange, the 3rd of The Aftermath, 3187. This statement is 
false. 
root@jhegaala:~# echo $DISPLAY 
:0.0
root@jhegaala:~# xclock &
[1] 311078
root@jhegaala:~# No protocol specified
Error: Can't open display: :0.0

[1]+  Exit 1  xclock
root@jhegaala:~# emacs &
[1] 311095
root@jhegaala:~# No protocol specified
Display :0.0 unavailable, simulating -nw
fg
emacs
root@jhegaala:~#

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/


pgplbNOU68qiN.pgp
Description: OpenPGP digital signature

Re: How to install official AMDGPU linux driver on Debian 11?

[Markos]

Em 21-10-2021 21:19, Linux-Fan escreveu:

Markos writes:


Em 17-10-2021 19:47, piorunz escreveu:

On 17/10/2021 22:27, Markos wrote:

Hi,

Please, could someone suggest a tutorial (for a basic user) on how to
install the driver for the graphics card for a laptop Lenovo IdeaPad
S145 with AMD Ryzen™ 5 3500U and AMD Radeon RX Vega 8 running 
Debian 11

(Bullseye).

I found a more complete tutorial just for Stretch and Buster:

https://wiki.debian.org/AMDGPUDriverOnStretchAndBuster2

What are the possible risks of problems using these AMD drivers?


[...]


No reply so far.

So, it seems that no one is interested in this question. :-(

Or none managed to do this installation, yet.


[...]

Before your initial post, there was already some discussion about a 
very similar case in the following thread:

https://lists.debian.org/debian-user/2021/10/msg00700.html

Summary: Just following AMDs instructions may lead to compile errors
(see https://lists.debian.org/debian-user/2021/10/msg00738.html)
whereas it worked for my GPU and downloaded driver:
(see https://lists.debian.org/debian-user/2021/10/msg00738.html)

I am interested in the questions of yours, but unfortunately cannot 
provide much of an assistance beyond what I already wrote in the other 
thread.


HTH
Linux-Fan

öö





Hi Linux-Fan,

Thank you for your comments.

Reading the messages I realized that this is a too big challenge for my 
level of knowledge.


And in the tutorial at 
https://linuxconfig.org/install-opencl-for-the-amdgpu-open-source-drivers-on-debian-and-ubuntu


I found an answer to my question about the risks of problems using these 
AMD drivers:


"WARNING: This may interfere with your existing drivers, resulting in 
poor performance and instability. Proceed with caution."


I even posted the same question on the AMD forum, but I haven't had an 
answer so far.


https://community.amd.com/t5/drivers-software/how-to-install-official-amdgpu-linux-driver-on-debian-11/td-p/493903

Thank you for your attention.

Best Regards,
Markos

Buster -> Bullseye: cups printing

[Grzesiek Sójka]

Hi there,

I have cups configured to print to smb shared printer. Required user id 
and password is included in printer configuration. Before upgrading to 
Bullseye printing worked as expected (any app, no password required). 
After the upgrade apps like LibreOffice, Firefox, Evince ask for smb 
share password (which is included in cups printer configuration). Even 
more interesting is that xpdf prints without asking for passwd.


Is there any way to restore previous behaviour (from Buster) and make 
apps other than xpdf print without asking for password??


--
Pozdriówka
Grzesiek
Najlepszym przyjacielem człowieka wcale nie jest pies a ..
... kolonia drożdży.
Duża kolonia => mnóstwo (% ;) ) radości.

Re: computer screen blink

[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

[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

[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: openssh server remote access

[Eric S Fraga]

On Friday, 22 Oct 2021 at 13:40, Andrei POPESCU wrote:
> Typically modems and home routers use the .1 address for themselves.

Interesting.  My last 2 routers have had *.254 (!) and *.100 as their
address. 

-- 
Eric S Fraga via Emacs 28.0.60 & org 9.5 on Debian 11.1

Re: openssh server remote access

[Andrei POPESCU]

On Jo, 21 oct 21, 22:52:37, Semih Ozlem wrote:
> I am unable to access my modem settings page when writing 192.168.1.100 to
> check if there is a firewall.

Are you sure this is the correct address? How did you establish that?

Typically modems and home routers use the .1 address for themselves.

Even if the firewall is disabled on the modem (it shouldn't be, and you 
should probably leave it enabled), systems connecting to the internet 
via the modem are usually inaccessible from the internet.

To connect to them from the internet you need a "port forwarding".

https://en.wikipedia.org/wiki/Port_forwarding

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: computer screen blink

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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
> > >
> > >
>
>