Re: port-amd64/53286: hdaudio(4), iwm(4) and rtsx(4) detections fail in UEFI case

[Robert Elz <kre%munnari.OZ.AU@localhost>]

The following reply was made to PR port-amd64/53286; it has been noted by GNATS.

From: Robert Elz <kre%munnari.OZ.AU@localhost>
To: Frank Kardel <kardel%netbsd.org@localhost>
Cc: gnats-bugs%NetBSD.org@localhost, netbsd-bugs%netbsd.org@localhost
Subject: Re: port-amd64/53286: hdaudio(4), iwm(4) and rtsx(4) detections fail in UEFI case
Date: Tue, 15 May 2018 02:52:42 +0700

     Date:        Mon, 14 May 2018 19:51:06 +0200
     From:        Frank Kardel <kardel%netbsd.org@localhost>
     Message-ID:  <a7d44efe-9ef1-35a7-5700-af0f060a8383%netbsd.org@localhost>
 
   | I also have such a UEFI system.
 
 Me too... (3? 4? ...)
 
   | The main difference is that UEFI boot does not enable all devices and 
 
 Yes, that's what I see as well.
 
   | our options to enable devices via ACPI do not improve anything.
 
 Haven't tried that (don't know how) but I have tried all the PCI_xxx
 options.   Those don't work any better for me than they do for you.
 
 I can't easily get the UEFI dmesg, as then the kernel cannot find a
 console (nothing serial exists, and the neither the graphics card,
 nor the integrated intel graphics in the CPU chip, are found, or at
 least are not in a state where they work as a console).
 
 I could take video or photos, but tha would be extremely tedious...
 
   | options         ACPI_ACTIVATE_DEV       # If set, activate inactive devices
 
 Ah, now I know how...
 
   | did give an improvement. I didn't see an BIOS options/knobs to force 
   | UEFI boot to enable all devices like they are in the CSM case.
 
 I suspect that's just a difference between UEFI and BIOS firmware, and
 what they promise.
 
 kre