Bug 205851

Created attachment 286275 [details]
sudo lspci -vv

https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5-rc2/
Today I installed rc-2
Ubuntu booted up, the touch-pad, battery works, etc. But the video driver does not work.
When trying to install downloaded from NVIDIA, it gave an error

ERROR: Failed to run `/usr/sbin/dkms build -m nvidia -v 440.36 -k 5.5.0-050500rc2-generic`:
         Kernel preparation unnecessary for this kernel.  Skipping...
  
         Building module:                                                                                                              
         cleaning build area...                                             
         'make' -j16 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=5.5.0-050500rc2-generic IGNORE_CC_MISMATCH='' modules......(bad exit     
         status: 2)
         ERROR (dkms apport): binary package for nvidia: 440.36 not found
         Error! Bad return status for module build on kernel: 5.5.0-050500rc2-generic (x86_64)
         Consult /var/lib/dkms/nvidia/440.36/build/make.log for more information.

Created attachment 286349 [details]
new dmesg

new dmesg

Also don't work sound and microphone

Today I installed rc-3
The problems are the same as in rc2
display does not work
the microphone and sound do not work
I attach the dmesg file in the same way and a screenshot of the sound settings

Created attachment 286419 [details]
dmesg-5.5.0-rc3

dmesg-5.5.0-rc3

Created attachment 286421 [details]
sound settings

sound settings
Dummy Output don't work too

Only ACPI error I see in the last dmesg is this one:

[    0.240966] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.I2C2.TPD0], AE_NOT_FOUND (20191018/dswload2-159)
[    0.240976] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20191018/psobject-220)
[    0.240979] ACPI: Skipping parse of AML opcode: Scope (0x0010)
[    0.241003] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.I2C3.TPL1], AE_NOT_FOUND (20191018/dswload2-159)
[    0.241006] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20191018/psobject-220)

So touchpad and panel devices under I2C seem to be missing. This should not prevent the system from booting up, though.

Can you attach output of acpidump as well?

From your last dmesg, I don't see any messages from nouveau driver (I think that's the discrete card) so are you sure you have it enabled in your .config? Can you also attach 'sudo lspci -vv' from the v5.5-rc3 kernel?

(In reply to Mika Westerberg from comment #10)
> Only ACPI error I see in the last dmesg is this one:
> 
> [    0.240966] ACPI BIOS Error (bug): Could not resolve symbol
> [\_SB.PCI0.I2C2.TPD0], AE_NOT_FOUND (20191018/dswload2-159)
> [    0.240976] ACPI Error: AE_NOT_FOUND, During name lookup/catalog
> (20191018/psobject-220)
> [    0.240979] ACPI: Skipping parse of AML opcode: Scope (0x0010)
> [    0.241003] ACPI BIOS Error (bug): Could not resolve symbol
> [\_SB.PCI0.I2C3.TPL1], AE_NOT_FOUND (20191018/dswload2-159)
> [    0.241006] ACPI Error: AE_NOT_FOUND, During name lookup/catalog
> (20191018/psobject-220)
> 
> So touchpad and panel devices under I2C seem to be missing. This should not
> prevent the system from booting up, though.

1) touchpad works
2) not work 
2.1) normal video resolution 
2.2) sound 
2.3) microphone

> 
> Can you attach output of acpidump as well?

acpidump_5.5.0_rc3.log
 
> From your last dmesg, I don't see any messages from nouveau driver (I think
> that's the discrete card) so are you sure you have it enabled in your

The driver for video is not installed on the RC
gives an error message

ERROR: Failed to run `/usr/sbin/dkms build -m nvidia -v 440.44 -k 5.5.0-050500rc3-generic`:
         Kernel preparation unnecessary for this kernel.  Skipping...
  
         Building module:                                                                                                              
         cleaning build area...                                             
         'make' -j16 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=5.5.0-050500rc3-generic IGNORE_CC_MISMATCH='' modules......(bad exit     
         status: 2)
         ERROR (dkms apport): binary package for nvidia: 440.44 not found
         Error! Bad return status for module build on kernel: 5.5.0-050500rc3-generic (x86_64)
         Consult /var/lib/dkms/nvidia/440.44/build/make.log for more information.


And on rc1 the resolution was normal, but the system did not boot after login

> .config? Can you also attach 'sudo lspci -vv' from the v5.5-rc3 kernel?

lspci_5.5.0_rc3.log

Created attachment 286487 [details]
acpidump_5.5.0_rc3.log

acpidump_5.5.0_rc3.log

Created attachment 286489 [details]
sudo lspci -vv 5.5.0_rc3

sudo lspci -vv 5.5.0_rc3

$ grep TPD0 *.dsl
dsdt.dsl:        Device (TPD0)
dsdt.dsl:            CreateWordField (SBFB, \_SB.PCI0.I2C0.TPD0._Y38._ADR, BADR)  // _ADR: Address
dsdt.dsl:            CreateDWordField (SBFB, \_SB.PCI0.I2C0.TPD0._Y38._SPE, SPED)  // _SPE: Speed
dsdt.dsl:            CreateDWordField (SBFI, \_SB.PCI0.I2C0.TPD0._Y39._INT, INT2)  // _INT: Interrupts
dsdt.dsl:                    Return (SBFI) /* \_SB_.PCI0.I2C0.TPD0.SBFI */
ssdt1.dsl:    External (_SB_.PCI0.I2C0.TPD0, DeviceObj)
ssdt1.dsl:    External (_SB_.PCI0.I2C2.TPD0, DeviceObj)
ssdt1.dsl:    External (_SB_.PCI0.I2C2.TPD0._STA, MethodObj)    // 0 Arguments
ssdt1.dsl:        Scope (TPD0)
ssdt1.dsl:                    Return (TD_P) /* \_SB_.PCI0.I2C2.TPD0.TD_P */
ssdt1.dsl:                    Return (TD_P) /* \_SB_.PCI0.I2C2.TPD0.TD_P */

only \_SB.PCI0.I2C0.TPD0 is defined.

$ grep TPL1 *.dsl
ssdt1.dsl:    External (_SB_.PCI0.I2C1.TPL1, DeviceObj)
ssdt1.dsl:    External (_SB_.PCI0.I2C3.TPL1, DeviceObj)
ssdt1.dsl:    External (_SB_.PCI0.I2C3.TPL1._STA, MethodObj)    // 0 Arguments
ssdt1.dsl:        Scope (TPL1)
ssdt1.dsl:                    Return (TD_P) /* \_SB_.PCI0.I2C3.TPL1.TD_P */
ssdt1.dsl:                    Return (TD_P) /* \_SB_.PCI0.I2C3.TPL1.TD_P */

No TPC1 device object defined.

This looks like a BIOS bug to me.

(In reply to sealse from comment #11)
> 
> 1) touchpad works
> 2) not work 
> 2.1) normal video resolution 
> 2.2) sound 
> 2.3) microphone
> 
I don't see any problems related with ACPI except for the ACPI errors which I believe is a BIOS issue.
So I think we should close this bug report for the ACPI errors, as we can not fix it in Linux kernel.

For the other non-working part, please file separate bug reports against the driver components.

Surely feel free to reopen this bug report if you still have any questions.

> (In reply to sealse from comment #11)
> > 
> > 1) touchpad works
> > 2) not work 
> > 2.1) normal video resolution 
> > 2.2) sound 
> > 2.3) microphone
> > 
> I don't see any problems related with ACPI except for the ACPI errors which
> I believe is a BIOS issue.
> So I think we should close this bug report for the ACPI errors, as we can
> not fix it in Linux kernel.
> 
> For the other non-working part, please file separate bug reports against the
> driver components.
> 
> Surely feel free to reopen this bug report if you still have any questions.

Yes, I have a problem in that the ubuntu is completely unsuitable for my laptop (
Tell me in which particular sections should I open messages about these errors?

I put rc4 problems the same as on rc3 including those with acpi errors in bios

(In reply to sealse from comment #16)
> > (In reply to sealse from comment #11)
> > > 
> > > 1) touchpad works
> > > 2) not work 
> > > 2.1) normal video resolution 
> > > 2.2) sound 
> > > 2.3) microphone
> > > 
> > I don't see any problems related with ACPI except for the ACPI errors which
> > I believe is a BIOS issue.
> > So I think we should close this bug report for the ACPI errors, as we can
> > not fix it in Linux kernel.
> > 
> > For the other non-working part, please file separate bug reports against
> the
> > driver components.
> > 
> > Surely feel free to reopen this bug report if you still have any questions.
> 
> Yes, I have a problem in that the ubuntu is completely unsuitable for my
> laptop (

I think the main problems are about
2.1) normal video resolution 
2.2) sound 
2.3) microphone
right? is there any other problems?
if no, why not report this issues to the graphics people to get help from them?

The fact is that in the pk1 version, during the boot of the system, despite a greater number of ACPI errors, the screen resolution was determined and at least the sound was determined. However, I could not log in to verify this in more detail.
Of course, I don’t know whether this is related to ACPI or not, but after most of the errors of the ACPI disappeared, the screen ceased to be detected like the sound

If you think that ACPI has nothing to do with it, close the ticket, I will look for happiness in other sections.

Sorry i meant "The fact is that in the rc1 version ..."

(In reply to sealse from comment #19)
> The fact is that in the pk1 version,

what about -rc3? we should focuses on the latest version, in case some of the problems have already been fixed.

I don't see any other ACPI errors except the ones has been explained in comment #14.

> during the boot of the system, despite
> a greater number of ACPI errors, the screen resolution was determined and at
> least the sound was determined. However, I could not log in to verify this
> in more detail.
> Of course, I don’t know whether this is related to ACPI or not, but after
> most of the errors of the ACPI disappeared, the screen ceased to be detected
> like the sound
> 
I'm still curious about the symptom in -rc3, which does NOT have so much ACPI errors.

> If you think that ACPI has nothing to do with it, close the ticket, I will
> look for happiness in other sections.

> what about -rc3? we should focuses on the latest version, in case some of
> the problems have already been fixed.

During loading rc1, the screen resolution was successfully determined and at least the indicator showed that the sound was working. but the system did not login into desktop after first screen with login and password
However, after installing rc2, the screen ceased to be detected and sound ceased to be detected, but the system began to enter after login

>I'm still curious about the symptom in -rc3, which does NOT have so much ACPI
>>errors.

All versions further rc2,3,4,5 behave the same - do not determine screen resolution at boot time

Okay, this more seems like to be graphics issues.
Given that we have no ACPI errors but only graphics issues in the latest upstream kernel, I will close this bug. Please file a separate bug for the graphics issue.

5.7.0-rc1 same problem

Created attachment 288621 [details]
acpi errors in boot

acpi errors in boot