ArcoLinux -D -B 19.5 iso's have been released

[SOLVED] Hwclock error 70 preventing install

defpdx
Crewman
Posts: 15
Joined: Mon Dec 11, 2017 5:57 am
United States of America
Re: [FOLLOWUP] Hwclock error 70 preventing install

Post by defpdx » Tue Dec 12, 2017 6:03 pm

Update: I ran "hwclock --test --directisa -D" under sudo with clearer (maybe) results:

Code: Select all

$ sudo hwclock --test --directisa -D
[sudo] password for fred: 
hwclock from util-linux 2.31
System Time: 1513097868.496013
Using direct ISA access to the clock
Last drift adjustment done at 1511853623 seconds after 1969
Last calibration done at 1511853623 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2017/12/12 16:57:49
Hw clock time : 2017/12/12 16:57:49 = 1513097869 seconds since 1969
Time since last adjustment is 1244246 seconds
Calculated Hardware Clock drift is 0.000000 seconds
2017-12-12 08:57:48.463959-0800
Test mode: nothing was changed.
Looks like an 8 hr discrepancy?..

abucodonosor
Crewman
Posts: 6
Joined: Tue Dec 12, 2017 4:31 pm
Germany
Re: [FOLLOWUP] Hwclock error 70 preventing install

Post by abucodonosor » Tue Dec 12, 2017 7:41 pm

Well you need set the time right in BIOS I guess however there is
some hope for your box at least. ISA bus seems OK..

defpdx
Crewman
Posts: 15
Joined: Mon Dec 11, 2017 5:57 am
United States of America
Re: [FOLLOWUP] Hwclock error 70 preventing install

Post by defpdx » Tue Dec 12, 2017 9:42 pm

After doing a bit of searching around, I found some forum posts highlighting a possible rtc issue with Arch itself.
https://www.startpage.com/rvd/search?qu ... guage=auto

Upon stumbling upon this, I decided to jump over to another install on a different partition. This one being an Ubuntu install.
Not sure the amount of pertinence to the issue at hand, but thought I'd share the info with you anyways.

From Kubuntu 17.04 on the same rig, here are some of the same outputs you had asked for previously:

hwclock --test -D

Code: Select all

sudo hwclock --test -D
[sudo] password for fred: 
hwclock from util-linux 2.29
Using the /dev interface to the clock.
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2017/12/12 19:56:51
Hw clock time : 2017/12/12 19:56:51 = 1513108611 seconds since 1969
Time since last adjustment is 1513108611 seconds
Calculated Hardware Clock drift is 0.000000 seconds
2017-12-12 11:56:50.952150-0800
hwclock --systohc --utc -D

Code: Select all

sudo hwclock --systohc --utc -D
hwclock from util-linux 2.29
Using the /dev interface to the clock.
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2017/12/12 20:00:44
Hw clock time : 2017/12/12 20:00:44 = 1513108844 seconds since 1969
Time since last adjustment is 1513108844 seconds
Calculated Hardware Clock drift is 0.000000 seconds
missed it - 1513108843.722479 is too far past 1513108843.500000 (0.222479 > 0.001000)
1513108844.500000 is close enough to 1513108844.500000 (0.000000 < 0.002000)
Set RTC to 1513108844 (1513108843 + 1; refsystime = 1513108843.000000)
Setting Hardware Clock to 20:00:44 = 1513108844 seconds since 1969
ioctl(RTC_SET_TIME) was successful.
Not adjusting drift factor because the --update-drift option was not used.
hwclock --test --directisa -D

Code: Select all

sudo hwclock --test --directisa -D
[sudo] password for fred: 
hwclock from util-linux 2.29
Using direct I/O instructions to ISA clock.
Last drift adjustment done at 1513108843 seconds after 1969
Last calibration done at 1513108843 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2017/12/12 20:37:25
Hw clock time : 2017/12/12 20:37:25 = 1513111045 seconds since 1969
Time since last adjustment is 2202 seconds
Calculated Hardware Clock drift is 0.000000 seconds
2017-12-12 12:37:24.202774-0800

Leads me to believe that it may not a problem with the rtc module missing or being broken, but rather something up with Arch itself. Just a couple things I noticed.

abucodonosor
Crewman
Posts: 6
Joined: Tue Dec 12, 2017 4:31 pm
Germany
Re: [FOLLOWUP] Hwclock error 70 preventing install

Post by abucodonosor » Tue Dec 12, 2017 11:37 pm

you are right .. AchLinux's kernel config is utter crap..

RTC is not usable in ArchLinux as is ..

These drivers *need* to be at least 'm'..

crazy@devnull:~$ grep -i rtc arch.config | grep "^# CONFIG"
# CONFIG_RTC_DEBUG is not set
# CONFIG_RTC_DRV_TEST is not set
# CONFIG_RTC_DRV_ABB5ZES3 is not set
# CONFIG_RTC_DRV_ABX80X is not set
# CONFIG_RTC_DRV_DS1307 is not set
# CONFIG_RTC_DRV_DS1374 is not set
# CONFIG_RTC_DRV_DS1672 is not set
# CONFIG_RTC_DRV_MAX6900 is not set
# CONFIG_RTC_DRV_RS5C372 is not set
# CONFIG_RTC_DRV_ISL1208 is not set
# CONFIG_RTC_DRV_ISL12022 is not set
# CONFIG_RTC_DRV_X1205 is not set
# CONFIG_RTC_DRV_PCF8523 is not set
# CONFIG_RTC_DRV_PCF85063 is not set
# CONFIG_RTC_DRV_PCF8563 is not set
# CONFIG_RTC_DRV_PCF8583 is not set
# CONFIG_RTC_DRV_M41T80 is not set
# CONFIG_RTC_DRV_BQ32K is not set
# CONFIG_RTC_DRV_S35390A is not set
# CONFIG_RTC_DRV_FM3130 is not set
# CONFIG_RTC_DRV_RX8010 is not set
# CONFIG_RTC_DRV_RX8581 is not set
# CONFIG_RTC_DRV_RX8025 is not set
# CONFIG_RTC_DRV_EM3027 is not set
# CONFIG_RTC_DRV_RV8803 is not set
# CONFIG_RTC_DRV_M41T93 is not set
# CONFIG_RTC_DRV_M41T94 is not set
# CONFIG_RTC_DRV_DS1302 is not set
# CONFIG_RTC_DRV_DS1305 is not set
# CONFIG_RTC_DRV_DS1343 is not set
# CONFIG_RTC_DRV_DS1347 is not set
# CONFIG_RTC_DRV_DS1390 is not set
# CONFIG_RTC_DRV_MAX6916 is not set
# CONFIG_RTC_DRV_R9701 is not set
# CONFIG_RTC_DRV_RX4581 is not set
# CONFIG_RTC_DRV_RX6110 is not set
# CONFIG_RTC_DRV_RS5C348 is not set
# CONFIG_RTC_DRV_MAX6902 is not set
# CONFIG_RTC_DRV_PCF2123 is not set
# CONFIG_RTC_DRV_MCP795 is not set
# CONFIG_RTC_DRV_DS3232 is not set
# CONFIG_RTC_DRV_PCF2127 is not set
# CONFIG_RTC_DRV_RV3029C2 is not set
# CONFIG_RTC_DRV_DS1286 is not set
# CONFIG_RTC_DRV_DS1511 is not set
# CONFIG_RTC_DRV_DS1553 is not set
# CONFIG_RTC_DRV_DS1685_FAMILY is not set
# CONFIG_RTC_DRV_DS1742 is not set
# CONFIG_RTC_DRV_DS2404 is not set
# CONFIG_RTC_DRV_STK17TA8 is not set
# CONFIG_RTC_DRV_M48T86 is not set
# CONFIG_RTC_DRV_M48T35 is not set
# CONFIG_RTC_DRV_M48T59 is not set
# CONFIG_RTC_DRV_MSM6242 is not set
# CONFIG_RTC_DRV_BQ4802 is not set
# CONFIG_RTC_DRV_RP5C01 is not set
# CONFIG_RTC_DRV_V3020 is not set
# CONFIG_RTC_DRV_PCF50633 is not set
# CONFIG_RTC_DRV_FTRTC010 is not set
# CONFIG_RTC_DRV_MC13XXX is not set

Also this is what they have ON:

crazy@devnull:~$ grep -i rtc arch.config | grep ^CONFIG
CONFIG_HPET_EMULATE_RTC=y
CONFIG_PM_TRACE_RTC=y
CONFIG_RTC_LIB=y
CONFIG_RTC_MC146818_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
CONFIG_RTC_SYSTOHC=y
CONFIG_RTC_SYSTOHC_DEVICE="rtc0"
CONFIG_RTC_NVMEM=y
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
CONFIG_RTC_INTF_DEV_UIE_EMUL=y
CONFIG_RTC_I2C_AND_SPI=y
CONFIG_RTC_DRV_CMOS=y
CONFIG_RTC_DRV_HID_SENSOR_TIME=m

.. and that is useless as is without any drivers turned on..

Anyway we should workaround that in Calamares some sort ... since there are HP Laptops
without a Linux RTC implementation at all ( older ones but still )..

defpdx
Crewman
Posts: 15
Joined: Mon Dec 11, 2017 5:57 am
United States of America
Re: [FOLLOWUP] Hwclock error 70 preventing install

Post by defpdx » Wed Dec 13, 2017 7:46 am

Yeah, there is a lot of 'not set' there. Not that I know what half of that stuff does..but still..

Well, I am glad to at least have found something of some usefulness, even though it looks like it may be a chore to fix. Hope you find a relatively painless fix for those HPs.
And about my clock...lol...yeah, that's another issue, for bios doesn't want to save any change to it-may have to unplug the battery or something. For me to worry about though:)

Other than getting past the install, Archmerge has been great otherwise. And for that--Thanks!

abucodonosor
Crewman
Posts: 6
Joined: Tue Dec 12, 2017 4:31 pm
Germany
Re: [FOLLOWUP] Hwclock error 70 preventing install

Post by abucodonosor » Wed Dec 13, 2017 1:05 pm

I changed how hwclock module works. It should now probe both methods RTC/ISA but won't
error out when nothing works. That way even on ArchLinux broken kernels the installation
will continue.

See :

https://github.com/calamares/calamares/ ... 0f94f4e970

User avatar
erikdubois
Captain
Posts: 2125
Joined: Tue Nov 07, 2017 3:45 pm
Location: Belgium
Contact:
Belgium
Re: [FOLLOWUP] Hwclock error 70 preventing install

Post by erikdubois » Wed Dec 13, 2017 5:40 pm

sounds promising....
in what version will that be incorporated
Learn, have fun and enjoy.
But first use the power of the Arch Wiki
use the tutorials on https://www.youtube.com/erikdubois
then use the power of google
then use the power of our moderators.

abucodonosor
Crewman
Posts: 6
Joined: Tue Dec 12, 2017 4:31 pm
Germany
Re: [FOLLOWUP] Hwclock error 70 preventing install

Post by abucodonosor » Wed Dec 13, 2017 7:11 pm

Should be in next stable , 3.1.11 .. but you can ofc get the patch and patch up your version.

However you may want to fix your kernel config and enable RTC modules :)

defpdx
Crewman
Posts: 15
Joined: Mon Dec 11, 2017 5:57 am
United States of America
Re: [FOLLOWUP] Hwclock error 70 preventing install

Post by defpdx » Thu Dec 14, 2017 12:34 am

Took the mods you wrote and applied them to the liveISO. No snags on install:) I'll probably keep it on metal for a couple days, in case you want to see any outputs.

User avatar
erikdubois
Captain
Posts: 2125
Joined: Tue Nov 07, 2017 3:45 pm
Location: Belgium
Contact:
Belgium
Re: [FOLLOWUP] Hwclock error 70 preventing install

Post by erikdubois » Thu Dec 14, 2017 5:59 am

That is great news indeed.
Thanks to all concerned.
Learn, have fun and enjoy.
But first use the power of the Arch Wiki
use the tutorials on https://www.youtube.com/erikdubois
then use the power of google
then use the power of our moderators.


Post Reply

Return to “Calamares installer”