Bug 1470476

Same here. Super IO chips were detected in my initial installation of Fedora 25, but not now with the latest installed kernels, probably because /dev/port has vanished between kernel version 4.8 and 4.11.

Hi,

(In reply to Norbert Jurkeit from comment #1)
> Same here. Super IO chips were detected in my initial installation of Fedora
> 25, but not now with the latest installed kernels, probably because
> /dev/port has vanished between kernel version 4.8 and 4.11.

Hmm, are you using secure boot by any chance ? Can you try turning it off ?

I think this is caused by secureboot (rightfully so) disallowing userspace accesses to io-ports...

Regards,

Hans

(In reply to Hans de Goede from comment #2)
> I think this is caused by secureboot (rightfully so) disallowing userspace
> accesses to io-ports...

Good point, but secureboot doesn't seem to cause the problem. My new notebook has enabled secureboot by default, but /dev/port is also missing with disabled secureboot and on 2 older computers of mine with legacy BIOS (in fact, the built-in Winbond Super I/O chips are no longer detected on those old boxes). On the other side, /dev/port is present even with enabled secureboot when I boot a Fedora 25 live image with kernel 4.8.6.

Recently I noticed another bug report 1451220 which also addresses this issue and indicates that it will be resolved with the next kernel update.

BR,
Norbert

Hi,

(In reply to Norbert Jurkeit from comment #3)
> (In reply to Hans de Goede from comment #2)
> > I think this is caused by secureboot (rightfully so) disallowing userspace
> > accesses to io-ports...
> 
> Good point, but secureboot doesn't seem to cause the problem. My new
> notebook has enabled secureboot by default, but /dev/port is also missing
> with disabled secureboot and on 2 older computers of mine with legacy BIOS
> (in fact, the built-in Winbond Super I/O chips are no longer detected on
> those old boxes). On the other side, /dev/port is present even with enabled
> secureboot when I boot a Fedora 25 live image with kernel 4.8.6.
> 
> Recently I noticed another bug report 1451220 which also addresses this
> issue and indicates that it will be resolved with the next kernel update.

Tip if you refer to other bugs do so as bug <nr> e.g. bug 1451220 then bugzilla will make it a clickable link.

OK, so bug 1451220 shows that this is a kernel-config issue. Would be interesting to know if the fixed kernel will work with secure boot (that would actually be a secure-boot bug I think).

Regards,

Hans

(In reply to Hans de Goede from comment #4)
> OK, so bug 1451220 shows that this is a kernel-config issue. Would be
> interesting to know if the fixed kernel will work with secure boot (that
> would actually be a secure-boot bug I think).

I just installed kernel 4.11.11 on Fedora 26 and that fixes the issue for me.

Regarding secure boot, it doesn't matter whether it is enabled or disabled on my new notebook: /dev/port is present and sensors-detect says "Found unknown chip with ID 0xfc11" (which is not unusual for lm-sensors on new hardware, but future support is uncertain as the project seems to be abandoned).

Regards,

Norbert

Hi,

(In reply to Norbert Jurkeit from comment #5)
> (In reply to Hans de Goede from comment #4)
> > OK, so bug 1451220 shows that this is a kernel-config issue. Would be
> > interesting to know if the fixed kernel will work with secure boot (that
> > would actually be a secure-boot bug I think).
> 
> I just installed kernel 4.11.11 on Fedora 26 and that fixes the issue for me.
> 
> Regarding secure boot, it doesn't matter whether it is enabled or disabled
> on my new notebook: /dev/port is present and sensors-detect says "Found
> unknown chip with ID 0xfc11"

Hmm, that is unexpected. /dev/port access really should be blocked when secure-boot is used. I've mailed our secure-boot maintainer about this.

Regards,

Hans

(In reply to Hans de Goede from comment #6)
> Hmm, that is unexpected. /dev/port access really should be blocked when
> secure-boot is used. I've mailed our secure-boot maintainer about this.

I have to correct myself. Due to a non-standard bootloader configuration, I have used the grub2 files installed with Fedora 25 also to boot Fedora 26. A closer look revealed that gcdx64.efi and grubx64.efi differ between both releases and I just copied the Fedora 26 versions to the EFI system partition.

With secure boot enabled, /dev/port is still present, but now sensors-detect says "/dev/port: operation not permitted". This is probably what you expected.

Sorry for causing confusion!

Regards,

Norbert

Updated to kernel 4.11.11 - problem solved!

This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

From the discussion it seems that the original issue has been resolved and that the problem with secureboot is in fact not present, so I'm closing this. Please reopen if there's anything else to be done.