Errors logged on Starting

When starting and before even the login screen I see three lines of errors on the screen:-

2017-10-10T15:31:23.138993+01:00 localhost kernel: 4.037489] ACPI Error: Field [TBF3] at bit offset/length 188416/196608 exceeds size of target Buffer (368640 bits) (20170531/dsopcode-235)
2017-10-10T15:31:23.138995+01:00 localhost kernel: 4.038455] ACPI Error: Method parse/execution failed _SB.PCI0.PEG.VID.GETB, AE_AML_BUFFER_LIMIT (20170531/psparse-550)
2017-10-10T15:31:23.138996+01:00 localhost kernel: 4.039295] ACPI Error: Method parse/execution failed _SB.PCI0.PEG.VID._ROM, AE_AML_BUFFER_LIMIT (20170531/psparse-550)

What is wrong, should I fix it, can I fix it and is this a reason why I must log in twice on starting?

Hi
BIOS and DSDT… system has the latest BIOS?

Try adding to the grub kernel options via YaST Bootloader;


acpi_osi="!Windows2012"

All the function keys working as expected?

Hi Malcolm,
I have updated the BIOS and that made some starting problems go.
I have no idea what to expect with Fn keys, I use them so rarely but keyboard now seems OK.

Out of interest what does the grub kernel option you suggest do? Will try it now.

There is only one other issue which might be relevant. This laptop had to be returned because of a screen fault. It appears they have given me a different machine as some of the hardware add-ons are different. They must have just swapped out the hard drive.

Would it be worth doing a new installation of Tumbleweed so low level detection is correct and doesn’t look for devices that are not there?

Regards,

Hi
The Fn keys like screen brightness, volume up/down cycle through bluetooth(if present) and wifi (equals rfkill soft block on/off).

So what errors went away, what are you seeing now?

It’s just an ACPI setting that the hardware may/maynot set/override the operating system detection process, there are lots… but if it does fix it then a kernel bug can be raised for this along with the output from dmidecode so it can be fixed…

Hi Malcolm,
Well the same errors are still there so none that I noticed have gone away.
The Fn keys seem to be working but I think they were before.

I have now given the machine a hostname and this seems to have stopped the double log in.