D&C GLug - Home Page

[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next date => thread => ]

Re: [LUG] Blinking Problem

 

On Fri, 29 Oct 2021 16:15:48 +0100
comrade meowski <mr.meowski@xxxxxxxx> wrote:

> On 28/10/2021 11:59, David Bell wrote:
> 
> > Here is the output Comrade. Appreciate your perusal.  
> 
> Ok there is actually some interesting stuff in here but as predicted, 
> nothing actually "wrong" and certainly not any obvious runaway
> problems that would indicate storage subsystem issues.
> 
> > root@Ermintrude-2:/home/grimpen# systemctl --failed
> >    UNIT LOAD ACTIVE SUB DESCRIPTION
> > 0 loaded units listed.  
> 
> Well that's a good start. Don't use root by the way, sudo exists for
> a reason.

I have always used root in a Debian terminal ensuring that I <exit>
when finished. However, point taken. 
> 
> > root@Ermintrude-2:/home/grimpen# journalctl -p err -b
> > -- Journal begins at Sat 2021-09-11 19:57:53 BST, ends at Thu
> > 2021-10-28 11:45:28 BST. -- Oct 28 08:43:08 Ermintrude-2 kernel:
> > ACPI BIOS Error (bug): Failure creating named object
> > [\_SB.PCI0.GPP0.VGA], AE_ALREADY_EXISTS (20200925/dswload2-326) Oct
> > 28 08:43:08 Ermintrude-2 kernel: ACPI Error: AE_ALREADY_EXISTS,
> > During name lookup/catalog (20200925/psobject-220) Oct 28 08:43:08
> > Ermintrude-2 kernel: ACPI BIOS Error (bug): Failure creating named
> > object [\_SB.PCI0.GPP0.HDAU], AE_ALREADY_EXISTS
> > (20200925/dswload2-326) Oct 28 08:43:08 Ermintrude-2 kernel: ACPI
> > Error: AE_ALREADY_EXISTS, During name lookup/catalog
> > (20200925/psobject-220) Oct 28 08:43:08 Ermintrude-2 kernel: ACPI
> > BIOS Error (bug): Could not resolve symbol
> > [\_SB.PCI0.GPP0.VGA.LCD._BCM.AFN7], AE_NOT_FOUND
> > (20200925/psargs-330) Oct 28 08:43:08 Ermintrude-2 kernel: ACPI
> > Error: Aborting method \_SB.PCI0.GPP0.VGA.LCD._BCM due to previous
> > error (AE_NOT_FOUND) (20200925/psparse-529) Oct 28 08:43:08
> > Ermintrude-2 kernel: ACPI Error: Evaluating _BCM failed
> > (20200925/video-357) Oct 28 08:43:08 Ermintrude-2 kernel: ACPI BIOS
> > Error (bug): Could not resolve symbol
> > [\_SB.PCI0.GP17.VGA.LCD._BCM.AFN7], AE_NOT_FOUND
> > (20200925/psargs-330) Oct 28 08:43:08 Ermintrude-2 kernel: ACPI
> > Error: Aborting method \_SB.PCI0.GP17.VGA.LCD._BCM due to previous
> > error (AE_NOT_FOUND) (20200925/psparse-529) Oct 28 08:43:08
> > Ermintrude-2 kernel: ACPI Error: Evaluating _BCM failed
> > (20200925/video-357) Oct 28 08:43:08  
> 
> Are you booting in BIOS or UEFI mode by the way? Switching to
> UEFI makes most of this stuff go away as well as being the correct
> way to run a computer in the 21st century.
>
It's twin SSD box with Win 11 on one and Debian 11 on the other, booting
in UEFI. I did a clean install yesterday with an updated version of
Debian 11. It made no difference. I preferred Debian 10 though. It
seemed to have a much faster boot-up and cleaner shut down on the same
machine.
> 
> > Ermintrude-2 kernel: iwlwifi 0000:04:00.0: firmware: failed to load
> > iwl-debug-yoyo.bin  
> 
> Nothing to worry about - looks like it might be a serious failure to 
> load wifi firmware but I imagine your wifi is working just fine. If
> not, now you know why it isn't. 
>
I always use Intel chipped wifi cards in my boxes and never had any
problems, nor with Devolo wifi/cable extenders. A quick search around
the www bazaars tells me iwl-debug-yoyo is missing from the kernel.
>  
> Virtualization is disabled in your firmware. This isn't technically a 
> problem if you don't ever use hypervisors but it really should be on: 
> technology increasingly calls out to low level stuff like this and 
> presumes it will always be there. Not a problem for you but Win10/11 
> require this feature to be enabled for things like WSL, WSA, 
> Virtualization platform features, Security Isolation, etc.
> 
Virtualization - about which, like most nix things, "I know nothing"!
> 
> THERE IS NOTHING WRONG WITH YOUR COMPUTER.
> 
Many thanks Comrade for taking the time to address my neurotic query.

David




-- 
The Mailing List for the Devon & Cornwall LUG
https://mailman.dcglug.org.uk/listinfo/list
FAQ: http://www.dcglug.org.uk/listfaq