NetBSD-10.0_BETA: clock: unknown CMOS layout
Hi to All! Sorry for my bad English... $ uname -a NetBSD aspire9.localnet 10.0_BETA NetBSD-10.0_BETA (GENERIC) #0: Fri Dec 23 12:41:20 +05 2022 root@aspire9.localnet:/root/sysbuild/amd64/obj/usr/src/sys/arch/amd64/compile/GENERIC amd64 On boot of NetBSD-10.0_BETA the message "clock: unknown CMOS layout" is printed. There is no this message at boot on NetBSD-9.x. Photo of screen: https://disk.yandex.ru/i/ashqmg563zGemQ The hardware: PC Acer Aspire XC-895 Intel Core i5-10400 The full dmesg: https://disk.yandex.ru/d/OktdpeJ3UuwuHA
Re: NetBSD-10.0_BETA: clock: unknown CMOS layout
On Fri, Dec 23, 2022 at 02:48:25PM +0500, Dmitrii Postolov wrote: > Hi to All! Sorry for my bad English... > > $ uname -a > NetBSD aspire9.localnet 10.0_BETA NetBSD-10.0_BETA (GENERIC) #0: Fri Dec 23 > 12:41:20 +05 2022 > root@aspire9.localnet:/root/sysbuild/amd64/obj/usr/src/sys/arch/amd64/compile/GENERIC > amd64 > > On boot of NetBSD-10.0_BETA the message "clock: unknown CMOS layout" is > printed. There is no this message at boot on NetBSD-9.x. > > Photo of screen: https://disk.yandex.ru/i/ashqmg563zGemQ > > The hardware: PC Acer Aspire XC-895 Intel Core i5-10400 Modern machines not always have the "pc compatible" parts like the cmos/clock or keyboard/mouse connector, but replace them with (typically) i2c connected devices. Windows stopped requiring that level of hardware compatibility some time ago and manufactures (naturally) use the new options. Parts of the "fallout" is hidden by ACPI glue. We are lacking a few drivers in that area, I see the same when booting NetBSD on my wife's notebook. Older NetBSD versions just did not print the message (but the CMOS/clock did not work any better with them). Martin
Re: NetBSD-10.0_BETA: clock: unknown CMOS layout
dposto...@yandex.ru (Dmitrii Postolov) writes: >On boot of NetBSD-10.0_BETA the message "clock: unknown CMOS layout" is >printed. There is no this message at boot on NetBSD-9.x. It's a DIAGNOSTIC message, if you run NetBSD-9.x release, the kernel is built without DIAGNOSTIC checks and messages, but NetBSD-10.0-BETA still is.
Re: NetBSD-10.0_BETA: clock: unknown CMOS layout
dposto...@yandex.ru (Dmitrii Postolov) writes: >"clock: unknown CMOS layout" The message says that no century information is found in the CMOS RAM, the hardware clock itself seems to keep only 2 year digits. The century is then deduced as 1900 if the year number is less than 70 and 2000 otherwise. This heuristic will fail 2030. Then the clock will start with a date 100 years in the past and gets corrected later during the boot process. Ugly, but probably not fatal.
Re: NetBSD and old nvidia laptop card / crash and unusable X11
Hi, Riccardo Mottola wrote: I can do that very easily on the 9.3 kernel sources which I have installed and the patch by Robert... because I have those sources already setup up and ready ro rebuild. I don't have the current kernel stuff here though. answering to my self after private with Robert: current needs to be build. I got the sources, upgraded to current. I have of course full 9.3 userland. Is a build possible at all without a switch? I configured the kernel, added the options you suggested and it dies with: In file included from ../../../../netipsec/ipsec.c:103:0: ../../../../netipsec/ipsec.c: In function 'ipsec_checkpcbcache': ../../../../netipsec/key_debug.h:64:8: error: expected ')' before '__VA_OPT__' __VA_OPT__(,) __VA_ARGS__); \ ^ ../../../../netipsec/ipsec.c:253:2: note: in expansion of macro 'KEYDEBUG_PRINTF' KEYDEBUG_PRINTF(KEYDEBUG_IPSEC_STAMP, ^~~ ../../../../netipsec/key_debug.h:63:19: error: format '%d' expects a matching 'int' argument [-Werror=format=] log(LOG_DEBUG, "%s: " fmt, __func__ \ ^ ../../../../netipsec/ipsec.c:253:2: note: in expansion of macro 'KEYDEBUG_PRINTF' KEYDEBUG_PRINTF(KEYDEBUG_IPSEC_STAMP, <..cut..> do I need to build full tools first? O did I get a bad release? Soon I need to move this discussion to "netbsd-current"... darn. Riccardo
Re: NetBSD and old nvidia laptop card / crash and unusable X11
It is entirely possible to build a full current or 10 release on 9. You can then run either kernel with 9 userland. To build, just "./build.sh release". The time you have to wait will be less than the time to figure out how to avoid that. But you can build tools, and then kernel, without building all of userland. signature.asc Description: PGP signature
