- This topic has 153 replies, 10 voices, and was last updated May 5-10:25 pm by Brian Masinick.
-
Posts
-
christophe
Regarding booting from a UEFI computer: UEFI computers boot the usb with a grub bootloader. Here, you’ll select your persistence/other boot options and save it, the first time you boot with the live-usb’s grub bootloader. Thereafter, your custom defaults will be set on either type.
confirmed antiX frugaler, since 2019
dugin
demo@antix1:~ $ ls -l /etc/localtime lrwxrwxrwx 1 root root 36 Apr 12 00:12 /etc/localtime -> /usr/share/zoneinfo/America/New_Yorkchristophe
My thought was this: So long as your bios is set to local time, if you changed the setting in control centre to UTC, maybe that would keep whatever time your bios says, but change the antiX time to America/Eastern. Just a thing I think someone else mentioned in the forums before, when I had the same or similar issue long ago. If I remember correctly, that fixed it. Maybe give that a try?
- This reply was modified 1 year ago by christophe.
confirmed antiX frugaler, since 2019
I can’t change to UTC from Control Center (System), but I can change to UTC if I right-click the clock in the systray. Thereafter, the clock shows UTC time, but a mouseover shows day, date, and local time. I would rather the clock show local time. And there is also the missing setting for Daylight Saving Time, which changes my time zone from GMT-5 to GMT-4. Smartphones don’t seem to have this problem with local time, local time DST. Right now, with the clock set to local time (DST), the clock time zone is labeled “EDT”, as opposed to ET, so perhaps determination of DST is automatic. Now that my systray clock is all set up and accurate for local time, when I boot up my other distro, it’s local EDT time will be 4 hours ahead, requiring correction. Sigh, at least it’s predictable.
EDIT: I went into the computer’s BIOS, and changed the clock to UTC time, although the setting was not designated “UTC”. Then I booted up the other distro got a fairly logical dialog, as follows. I changed the HW clock to UTC, and then it prompted me to declare what the systray clock should show, HW clock or software clock. I selected software clock, whereupon the clock showed accurate local time, DST. Then I booted back into antiX, and the clock was correct for local time, DST. So maybe that fixes the clocks.
- This reply was modified 1 year ago by dugin.
- This reply was modified 1 year ago by dugin.
- This reply was modified 1 year ago by dugin.
ModdIt
Hi dugin, you give us the time setting for antiX, now pls result of same command for your other disstro.
It should work correctly on all debian based systems.If there is any difference in time settings between the distros you are using that is what causes trouble.
Very important also pls confoirm on bios clock and battery, latter can fail overnight, even new ones.
Just using a voltmeter often gives a false sense of serviceability. Voltage looking correct but add the
tiniest of loads and a bad battery will drop to 0 Volts or so low that out of range for hardware.distro 1
root# ls -l /etc/localtime lrwxrwxrwx 1 root root 30 Nov 21 2017 /etc/localtime -> /usr/share/zoneinfo/US/EasternantiX-32
demo@antix1:~ $ ls -l /etc/localtime lrwxrwxrwx 1 root root 36 Apr 12 00:12 /etc/localtime -> /usr/share/zoneinfo/America/New_Yorkdistro 3
root# ls -l /etc/localtime lrwxrwxrwx 1 root root 29 Apr 12 2022 /etc/localtime -> /usr/share/zoneinfo/Etc/GMT-5- This reply was modified 1 year ago by dugin.
- This reply was modified 1 year ago by dugin.
- This reply was modified 1 year ago by dugin.
Although distro_1 and antiX seemed okay, distro 3 came up with a time change from 16h (UTC) to 21h, ie +5 hours. The clock was reading 21h 51m (9 hours later than local time) when I booted distro_3. Don’t have a clue why it did that. And distro_1 was affected by that as well, with an incorrect local time +4 hours.
- This reply was modified 1 year ago by dugin.
- This reply was modified 1 year ago by dugin.
- This reply was modified 1 year ago by dugin.
PPC
I needed to select HW clock in distro_3, and deal with the changes. The dialog to change the clocks to be based on UTC is most intelligible in distro_1. distro 3 was not as simple and straightforward.
Yes, been running distro 1, singly, for over 4 years. Nov 21, 2017 makes perfect sense. No problem with clocks using a single distro.
EDIT: Ah, after all that clock adjustment, antiX still keeps correct local time. That’s an improvement.
- This reply was modified 1 year ago by dugin.
@dugin- sorry I should have read the complete contents of your post. I though you were using all the distros in the same way (as “frugals”)
One piece of info that may be useful for you (or not), my installed antiX 19.X output for the same command was:… /etc/localtime -> /usr/share/zoneinfo/
P.
Edit: I just read your “Edit” – so I guess the problem with antiX is solved… You have to take care of distro3…
- This reply was modified 1 year ago by PPC.
Why is that, executing the toram step in bootup of antiX, copying 759 MB to RAM takes 3 times longer from USB than from DVD?
- This reply was modified 1 year ago by dugin.
Why is that,
executing the toram step in bootup of antiX, copying 759 MB to RAM takes 3 times longer from USB than from DVD?
You could search and figure that out faster than others can answer…Slow USB Port or Stick has low read speed. Or both.
DVD is connected to IDE Or SATA depending on Hardware.
Pls take a read, huge differences between USB 1, 2, 3, 3.1
A lot of sticks do not provide decent long read speeds.
Same goes for write once the cache is full.And CD DVD device read rates.
I’m concerned that appending xorg.conf in antiX to increase video-graphics acceleration may overheat my onboard graphics chip, which does have a small heatsink. Opinions?
- This reply was modified 1 year ago by dugin.
Brian Masinick
I’m concerned that appending xorg.conf in antiX to increase video acceleration may overheat my onboard graphics chip. Opinions?
1) Is the current setting in a “comfortable” temperature range?
2) Is the video acceleration you are considering within the range that your onboard graphics chip supports?As long as you are not pushing or exceeding the specifications and you are not already dealing with heat issues, you MAY be OK, but that’s not a certainty by any means. If it were me, I’d do as much research as possible, beginning with the graphics chip vendor information and also any information from your computer manufacturer. Unless you know the correct specifications, if it were me doing this, I’d do my own homework first.
Other thoughts and comments?
--
Brian MasinickBrian Masinick
Although distro_1 and antiX seemed okay, distro 3 came up with a time change from 16h (UTC) to 21h, ie +5 hours. The clock was reading 21h 51m when I booted distro_3. Don’t have a clue why it did that. And distro_1 was affected by that as well, with an incorrect local time +4 hours.
I see this fairly often. For me personally, I choose to use my local time zone; some distributions either insist or modify the time zone, either switching to UTC, or fail to save the hardware time correctly as I prefer it, so from time to time when I change distributions, I experience this too. I simply change it to what I prefer; this doesn’t harm anything; it simply modifies the hardware clock time, which is exactly what I want it to do. Your scenario is different than mine because you prefer UTC and I prefer local time. Whenever it changes, just change it back. AntiX has a convenient tool to update the time; most convenient distributions have their own clock or time modification tool.
--
Brian Masinick
- You must be logged in to reply to this topic.
