diff --git a/dm/dm-compatibility-catalog.md b/dm/dm-compatibility-catalog.md
index c7a28d31ed256..7c187a1a558fa 100644
--- a/dm/dm-compatibility-catalog.md
+++ b/dm/dm-compatibility-catalog.md
@@ -36,6 +36,8 @@ DM supports migrating data from different sources to TiDB clusters. Based on the
 
 - For MariaDB **10.5.11 and later**, the DM **precheck fails** due to privilege name changes (for example, `BINLOG MONITOR`, `REPLICATION SLAVE ADMIN`, `REPLICATION MASTER ADMIN`). The error appears as `[code=26005] fail to check synchronization configuration` in the replication privilege, dump privilege, and dump connection number checkers.
 - You can **bypass the precheck** by adding `ignore-checking-items: ["all"]` in the DM task. See [DM precheck](/dm/dm-precheck.md) for details.
+- For MariaDB 11.4 and later, you must set the [`binlog_legacy_event_pos`](https://mariadb.com/docs/server/ha-and-performance/standard-replication/replication-and-binary-log-system-variables#binlog_legacy_event_pos) variable to `ON`.
+- Starting DM on a new/fresh MariaDB instance with an empty `gtid_binlog_pos` can cause issues, avoid this by creating at least one transaction. See [GitHub pingcap/tiflow#12423](https://github.com/pingcap/tiflow/issues/12423).
 
 ## Target databases
 
diff --git a/migrate-from-mariadb.md b/migrate-from-mariadb.md
index bf70a1b950d5f..6b56ba82bcf06 100644
--- a/migrate-from-mariadb.md
+++ b/migrate-from-mariadb.md
@@ -12,7 +12,7 @@ This document describes how to migrate data from a MariaDB server installation t
 Choose the right migration strategy:
 
 - The first strategy is to [dump data with Dumpling and restore data with TiDB Lightning](#dump-data-with-dumpling-and-restore-data-with-tidb-lightning). This works for all versions of MariaDB. The drawback of this strategy is that it needs more downtime.
-- The second strategy is to [Replicate data with DM](#replicate-data-with-dm) from MariaDB to TiDB with DM. DM does not support all versions of MariaDB. Supported versions are listed on the [DM Compatibility Catalog](/dm/dm-compatibility-catalog.md#compatibility-catalog-of-tidb-data-migration).
+- The second strategy is to [Replicate data with DM](#replicate-data-with-dm). DM does not support all versions of MariaDB. Supported versions and required settings are listed on the [DM Compatibility Catalog](/dm/dm-compatibility-catalog.md#compatibility-catalog-of-tidb-data-migration).
 
 Besides these two strategies, there might be other strategies available specifically to your situation. For example: