MX-21 timezone issue [Solved]

[tascoast]

I've repeated an install of MX-21, downloading the iso again by torrent the second time.

Choosing Australian/Melbourne for timezone I get the same issue, the clock showing 11 hours out.
Apart from this, I'm wondering if daylight savings time is also not registering, a secondary issue worth noting, as it currently applies here now.

For reference, I cannot update network time in MX Date and Time, have UTC selected, which corresponds to previous installs of MX-19 etc. Changing this to Local didn't seem to help the first time around and so have left things as default, pending advice, if anyone can offer their opinion?

There is one other small issue in Synaptic when updating that is not necessarily related but note also for reference:

Code: Select all

Release file for http://deb.debian.org/debian/dists/bullseye-updates/InRelease is not valid yet (invalid for another 9h 50min 57s). Updates for this repository will not be applied.Release file for http://mirror.datamossa.io/mxlinux/mx/repo/dists/bullseye/InRelease is not valid yet (invalid for another 5h 6min 26s). Updates for this repository will not be applied.

I appreciate this might be related to mirrors slowly populating? It defaults to the Australia, Sydney mirror for me.

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-9-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-9-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-21_x64 Wildflower October 20  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop Mobo: MSI model: H61M-P31/W8 (MS-7788) v: 1.0 serial: <filter> 
           BIOS: American Megatrends v: 3.6 date: 09/29/2013 
CPU:       Topology: Dual Core model: Intel Core i3-3220 bits: 64 type: MT MCP arch: Ivy Bridge 
           family: 6 model-id: 3A (58) stepping: 9 microcode: 21 L2 cache: 3072 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 26399 
           Speed: 1848 MHz min/max: 1600/3300 MHz Core speeds (MHz): 1: 1727 2: 1701 3: 1701 
           4: 1715 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, 
           STIBP: conditional, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel Xeon E3-1200 v2/3rd Gen Core processor Graphics 
           vendor: Micro-Star MSI driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0152 
           Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1440x900~60Hz, 1280x1024~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 2500 (IVB GT1) v: 4.2 Mesa 20.3.5 
           compat-v: 3.0 direct render: Yes 
Audio:     Device-1: Intel 6 Series/C200 Series Family High Definition Audio 
           vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
           chip ID: 8086:1c20 
           Sound Server: ALSA v: k5.10.0-9-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: Micro-Star MSI driver: r8169 v: kernel port: e000 bus ID: 02:00.0 
           chip ID: 10ec:8168 
           IF: eth0 state: down mac: <filter> 
           Device-2: Realtek RTL8191SU 802.11n WLAN Adapter type: USB driver: r8712u 
           bus ID: 1-1.2:3 chip ID: 0bda:8172 serial: <filter> 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 935.12 GiB used: 6.10 GiB (0.7%) 
           ID-1: /dev/sda vendor: Western Digital model: WD10EZEX-22MFCA0 size: 931.51 GiB 
           block size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s rotation: 7200 rpm 
           serial: <filter> rev: 1A01 scheme: MBR 
           ID-2: /dev/sdf type: USB vendor: Verbatim model: STORE N GO size: 3.61 GiB 
           block size: physical: 512 B logical: 512 B serial: <filter> rev: 5.00 scheme: MBR 
Partition: ID-1: / raw size: 34.00 GiB size: 33.17 GiB (97.56%) used: 6.10 GiB (18.4%) fs: ext4 
           dev: /dev/sda8 
           ID-2: swap-1 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda5 
Sensors:   System Temperatures: cpu: 22.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mirror.datamossa.io/mxlinux/mx/repo/ bullseye main non-free
Info:      Processes: 222 Uptime: 1h 10m Memory: 3.73 GiB used: 1.08 GiB (29.0%) Init: SysVinit 
           v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 

[Vipul88]

do you have a windows as a dual boot?

[SwampRabbit]

@tascoast i heard somewhere online that the Sydney Repo has issues, can you try the Los Angeles one?

[tascoast]

I'll definitely change mirrors as I usually do, with an LA or Salt Lake being my usual selection from experience. Poor old Aussie servers haven't been reliable for me over recent years, so easy done.
It's still nice that repo manager does default to a geographically local mirror, or one that promises the fastest connection, when installing.

This desktop machine is exclusively Linux, MX/antiX and a couple of others like Debian, for curiosity.

I only use W10 on my laptop for work purposes, with MX via Virtual Box or live USB with persistence.

[m_pav]

Coming from NZ, I can tell you exactly what you need to do.

When you boot the live media, ALWAYS select your language setting and timezone at the initial boot loader screens.

Here's what to do on any BIOS machine (non-uefi) where the Fn key selections are available to correct time issues that drive us crazy here in NZ because the US time zone on all Live ISO's that originate from the US is roughly 12H behind us and our clocks display the correct time, BUT the WRONG date for the first half of the day and the wrong phase all the time. At least with Australia, yours is very quickly spotted because it is 3 hours different!

The answer is so simple you'll kick yourself because it's been there all along.

Here's what I do the set the correct options for my local timezone before I run the installer.

Boot the Live media
F2 Language - set to "English (NZ)"
F3 Timezone - change to "Auckland"
F4 Options - change to "hwclock=local" ( for any dual boot Windows machine, not required for Apple or Linux only )
F8 Save - "save" the settings are written to the flash drive so you don't have to enter them again.

And on EFI boot machines, it's a little easier, albeit at first it may seem more confusing. Again, this needs to be done before you run the installer. NOTE: For those reading this and coming from a different locale, choose the options that match your own location.

Boot the Live Media
The pre-selected default boot entry is "Language - Keyboard - Timezone". Press <return> to select this option.
The next pre-selected option is "Language (lang=en_us)" - Press <return> to select this option.
The next pre-selected option is "Lang=en English - English" - Press <return> to select this option.
The next pre-selected option is "lang=en_AU: English (Australia)" - Press <return> to select this option or change it to one that matches your locale.

You will be taken to a 2nd level boot options screen displaying your selections from the last few steps. At this point, you can go ahead and boot the system with the options displayed in that screen, however, the option to use Local time is not yet set.

To set that, Press Esc and choose >>>Advanced Options<<<
Cursor down to Boot options: and choose the item "hwclock=local Hardware clock uses local time (Windows)"
Go back to the main menu and boot your system

With these settings set, the update mirrors will be set to those nearest you and the clock will display the right local time. There is still one gotcha you must keep in mind. The installer does not read user timezone selections, so it's imperative you set these when running the installer and watch for the option to set your clock to use local time too.

Lots of text to explain a 30-second process, but it's worth it.

[fehlix]

I've repeated an install of MX-21, downloading the iso again by torrent the second time.

Choosing Australian/Melbourne for timezone I get the same issue, the clock showing 11 hours out.

Perhaps, do select hwclock=local (if dual boot with Window) and timezone on the LiveBoot Menu. Also you can add/select "norepo" to keep default mx-repo's selected, instead of local repos.

[tascoast]

I think swapping to Local in Timezone settings actually sorted things, but only after a couple of reboots. It's possible booting into MX-19 and back contributed, besided completing updates etc.. I usually only need a bit of tinkering for timezone with a Live USB persist system, and previous instructions offered do resemble the setup I use there. Anyway, memory did suggest Local suited my older desktop in previous installs and it finally worked, although might have changed somewhere inside the operating system v the MX-19 partition settings used.

I'll mark this solved and note just how much faster MX-21 loads in comparison to MX-19 here.

My personal mission is to work out auto disk mounting settings without Disk Manager inc. by default now, something I've been too lazy to focus on in recent times, but am sure to work out over a coffee and a read up.
Kinds thanks
Mick