WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: TC and acpi_osi strangeness in /var/log/messages  (Read 139 times)

Offline PDP-8

  • Full Member
  • ***
  • Posts: 242
TC and acpi_osi strangeness in /var/log/messages
« on: March 15, 2018, 02:03:24 AM »
One for you kernel hackers ...

I've been investigating the use of booting TC with a few different kernel boot parameters (to avoid manufacturer botched bios patch bugs) such as

acpi_osi=
and
acpi_osi=Linux

and seeing if they are accepted or rejected when also using the syslog parameter and taking a peek at /var/log/messages after boot.

At first I used syslog by itself with no other parameters on a stock TC, and found this when I grepped Linux from /var/log/messages:

<snip>
Code: [Select]
Mar 15 08:25:01 box user.notice.kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored <snip>

Does this mean that the acpi_osi=Linux parameter is *already* hardcoded into the TC kernel and is getting ignored/munged somehow, or is this normal for a stock install?

Note that when I DO pass the kernel parameter manually at boot time, acpi_osi=Linux by myself

I get this out of /var/log/messages:

Code: [Select]
Mar 15 08:16:31 box user.info.kernel: ACPI: Added _OSI(Linux)
Mar 15 08:16:31 box user.notice.kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query honored via cmdline

Just wondering if I caught something, or if I'm just observing normal behaviour in the stock TC boot.
« Last Edit: March 15, 2018, 02:05:29 AM by PDP-8 »
cat -v Considered Harmful  -- Rob Pike

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 9741
Re: TC and acpi_osi strangeness in /var/log/messages
« Reply #1 on: March 15, 2018, 02:25:40 AM »
The TC kernel does not differ from upstream on those parameters.
The only barriers that can stop you are the ones you create yourself.

Offline PDP-8

  • Full Member
  • ***
  • Posts: 242
Re: TC and acpi_osi strangeness in /var/log/messages
« Reply #2 on: March 15, 2018, 04:02:35 PM »
Ok, thanks for making me dig :)

Right - not a TC thing, but a general kernel thing.  That default kernel response to the bios is actually the smartest response for various reasons, as is in conversation:

Kernel: "Don't probe me bro, you just keep thinking you are talking to a windows whatever box, and we'll take it from there..thanks."

TC makes me learn something every day...

cat -v Considered Harmful  -- Rob Pike