Porteus Kernel Builder

[Blaze]

hwclock iopl() port access failed: function not implemented - the same on the 5.5.2 kernel build by neko

Отправлено спустя 1 день 2 часа 51 минуту 39 секунд:

hwclock iopl() port access failed: function not implemented - the same on the 5.5.2 kernel build by neko

The same error on the 5.4.19 kernel build by neko

[neko]

@evergreen
@Blaze
Please tell me the procedure to reproduce the message.

Thanks.
-------------------------------------------------------------------------------
Boot Porteus-OPENBOX-v5.0rc1-x86_64.iso + 5.5.2/5.6.0-rc1

Code: Select all

% su
# hwclock

[evergreen]

Dear @neko

In my case it appear after modules are loaded it is when everything is booting, previously to start x.
I did a second try with a clean system Porteus-OPENBOX-v5.0rc1-x86_64.iso + 5.6.0-rc1
using this modules http://www.mediafire.com/file/3x1bm9k2y ... .6-rc1.tar
Maybe there is some changues with your script to compile Kernel, I would like to have better knowledges to support you.
Thanks to give us the latest Kernel out of the box to use I really appreciate a lot your work

[Blaze]

Every boots up of Porteus on the init step - X does not started, I see this error and I start X manually.

[Rava]

Every boots up of Porteus on the init step - X does not started, I see this error and I start X manually.

I always start Porteus is text mode (cheatcode "3") and start it manually from a guest virtual terminal, I presume that's the reason why I did not get any errors running the 5.4.19 kernel.

[beny]

someone can try haveged from sbo maybe can help..

[ncmprhnsbl]

i think maybe:
CONFIG_RTC_HCTOSYS=y
some possible relevant discussion here: https://bugs.gentoo.org/434410
something to do with whether hw clock(cmos) is set to utc or local?
don't know if setting:
CONFIG_RTC_HCTOSYS=n
would cause some problem if hwclock is set to local..
should be noted, that apart from that message (hwclock iopl() port access failed: function not implemented) .. there doesn't appear to be any other ill effect...

[neko]

@evergreen
@Blaze
@Rava
@beny
@ncmprhnsbl

The cause of the kernel build due to the "hwclock" problem has not yet been identified.
Therefore I will hold this issue and update the new build example.


Thanks.
----------------------------------------------------------------------------------------------------------------------
Most recent version of build examples was updated.

=== XZ version ===
Kernel Version: 5.5.4, 5.4.20, 4.19.104


New Compiler version is gcc-9.2.1+20200130-x86_64-2.


Please refer to the top article of this thread.
Porteus Kernel Builder


Thanks.

[Blaze]

neko, I fixed this issue via update glibc from Slackware-current.

[neko]

@Blaze
Thanks for your wonderful analysis !!


Thanks.

[neko]

Most recent version of build examples was updated.

=== XZ version ===
Kernel Version: 5.6-rc2

Note 1: AUFS patch "5.6" is not yet ready, and
AUFS patch "5.x-rcN-20200203" is not yet ready for kernel version 5.6-rc2.
"fs/Kconfig" and "fs/Makefile" were patched same as "Note 3" of Porteus Kernel Builder (Post by neko #75872)

Note 2: syntax error of "fs/aufs/procfs.c"
"fs/aufs/procfs.c" was patched same as "Note 4" of Porteus Kernel Builder (Post by neko #75872)

These patches are not guaranteed.


Please refer to the top article of this thread.
Porteus Kernel Builder


Thanks.

[neko]

Most recent version of build examples was updated.
=== XZ version ===
Kernel Version: 5.5.5, 5.4.21, 4.19.105



Please refer to the top article of this thread.
Porteus Kernel Builder


Thanks.

[neko]

Thank you for referring to this thread.

Suddenly, I will rest for a while.
I hope you build your own kernel.

Good luck !!

[babam]

neko, thank you very much. I hope you come back soon.

[Rava]

Thank you for referring to this thread.

Suddenly, I will rest for a while.

neko, thanks for all you done, your kernel builder is an amazing piece of software.

Take all the time you need.