Dual Boot Problems with Windows and Manjaro

I have a dualboot system with Windows 10 and Manjaro. Theoretically it works but there are some strange errors that occur and I want to ask, if somebody allready came across them or have an explanation.

Two errors are in conection with switching the os with a simple reboot instead of a shutdown:

  1. If I switch from Manjaro to windows the Soundblaster does not work correctly. The sounds, voices and music are strange.
  2. If I switch from Windows to Manjaro there are Problems with the graphic card in Steam. (As far as I can see only Steam.) Any game as well as the launcher itself lets the system crash completly. The display freezes keyboard and mouse are not reacting. The logs showed a problem with the AMD Graphic card. (Unfortunatly I haven’t saved the logs.)

In both cases I have to shut down the system completly to solve the problem. I know how to awoid these problems so the are not very serious (I hope) but I have mentioned them because of the more problematic third error:

Since the installation of Linux Windows starts with boot loops. If I shut down the Manjaro system and boot Windows the system reboots a few seconds after pressing enter in grub. Normaly the second start works. It does not matter if a have shut down Linux the day before or a few hours ago. The next few Win boots will show the problem.

A more problematic variant sometimes occur when I have shuted down Windows with a program (eg Sleep timer Ultimate). Then the boot loop does not end. I have to press the power button boot Linux shut it down and reboot Windows. Logs and Halt on error ar enabled but the boot loop starts to early.

These problems started with the Linux installation. Each OS has its own SSD. The system is running in Legacy (Bios) mode.

I’ve moved this to the Support section as your post is in English; however, it can be moved again if you would prefer to communicate in your native language.

First thing I’d check is that Windows’ Fast Startup “feature” is disabled.

In an elevated command prompt in Windows:

powercfg /h off

Of course, system info will help (from Manjaro):

inxi -zv8

will tell us useful things about your Manjaro installation.

That looks to me to be a not untypical effect based on the difference between cold versus warm boot, see reference:

So, in case of your specific hardware/BIOS it seems to be required to execute a cold boot to avoid the mentioned issues. Usually, this does not take nameable more time and is therefore the best available solution.

3 Likes

In case of the Soundblaster and Graphiccard problems yes, but the bootloops are different as they appear in case of cold reboots.

Win fast startup was allways disabled. I have checked it.

I shall run the inxi command as quick as my work let me use the Linuxinstallation again.

1 Like

Quick question, are you using Windows for Gaming or just Linux with Steam?

1 Like

At the moment: Both. I try to switch from Windows to Linux completly but I am not trained enough to solve all the problems. So I start slowly…

The reason I asked is, if you were not using Windows for games, you could more easily run Windows in a VM, thereby avoiding all these dual boot issues.

Can you please not ignore posts?:


Is Fast Startup disabled in Windows?


Your detailed system information will assist others to help you find a resolution to your issue.


Please provide system information as described (below): :eyes:

Once you have provided that and acknowledged other questions/suggestions this topic will be re-listed.

Regards.


Welcome to the Manjaro community

As a new or infrequent forum user, please take some time to familiarise yourself with Forum requirements, and the many ways to use the forum to your benefit.

To that end, links are provided (below) - Please use them.


Be prepared to provide outputs from various commands when asked. It’s equally important to provide as much actionable information as possible in your first post, rather than simply indicating there is a problem.

Waiting for others to blindly ask questions can be counter-productive – typically, nobody has a :crystal_ball: at their disposal – Instead, please help others to make informed suggestions, based on information you provide.


Update Announcements

The Update Announcements contain important information and a Known Issues and Solutions section that should generally be checked before posting a request for support.

System Information

While information from *-fetch type apps might be fine for someone wishing to buy your computer, for Support purposes it’s better to ask your system directly; :eyes:

Output of the inxi command (with appropriate parameters, and formatted according to forum guidelines) will generate information useful for those wishing to help:

inxi --filter --verbosity=8

or the short form (preferred):

inxi -zv8
Highly Recommended
Technical Resources
Required Reading

I have not ignored the post but I have answered BG405 two days ago!

Fast Startup is disabled.

The results of the inxi-command will follow as quick as I have the time to boot Linux on that PC again.

I thought of this too but in this case I would have to buy some programmes again. A new PC just for Linux gaming would be cheeper than that…

My mistake. We look forward to seeing the inxi output.

Regards.

2 Likes

The inixi output:

System:
Kernel: 6.12.48-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.12-x86_64
root=UUID=7577eecb-23f7-4a07-8eac-a01a3d8d9240 rw quiet splash
resume=UUID=8708d9e9-4e5b-490b-b93e-465abbd4a30a udev.log_priority=3
Desktop: KDE Plasma v: 6.3.6 tk: Qt v: N/A info: frameworks v: 6.18.0
wm: kwin_x11 vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
Type: Desktop Mobo: Micro-Star model: X399 SLI PLUS (MS-7B09) v: 2.0
serial:  uuid: 
UEFI-\[Legacy\]: American Megatrends v: A.00 date: 09/21/2017
Battery:
Message: No system battery data found. Is one present?
Memory:
System RAM: total: 128 GiB available: 125.69 GiB used: 6.78 GiB (5.4%)
Message: For most reliable report, use superuser + dmidecode.
Array-1: capacity: 512 GiB slots: 8 modules: 4 EC: None
max-module-size: 64 GiB note: est.
Device-1: Channel-A DIMM 0 type: no module installed
Device-2: Channel-A DIMM 1 type: DDR4 detail: synchronous unbuffered
(unregistered) size: 32 GiB speed: spec: 2133 MT/s actual: 1067 MT/s
volts: note: check curr: 1 min: 1 max: 1 width (bits): data: 64 total: 64
manufacturer: Corsair part-no: CMK128GX4M4A2666C16 serial: N/A
Device-3: Channel-B DIMM 0 type: no module installed
Device-4: Channel-B DIMM 1 type: DDR4 detail: synchronous unbuffered
(unregistered) size: 32 GiB speed: spec: 2133 MT/s actual: 1067 MT/s
volts: note: check curr: 1 min: 1 max: 1 width (bits): data: 64 total: 64
manufacturer: Corsair part-no: CMK128GX4M4A2666C16 serial: N/A
Device-5: Channel-C DIMM 0 type: no module installed
Device-6: Channel-C DIMM 1 type: DDR4 detail: synchronous unbuffered
(unregistered) size: 32 GiB speed: spec: 2133 MT/s actual: 1067 MT/s
volts: note: check curr: 1 min: 1 max: 1 width (bits): data: 64 total: 64
manufacturer: Corsair part-no: CMK128GX4M4A2666C16 serial: N/A
Device-7: Channel-D DIMM 0 type: no module installed
Device-8: Channel-D DIMM 1 type: DDR4 detail: synchronous unbuffered
(unregistered) size: 32 GiB speed: spec: 2133 MT/s actual: 1067 MT/s
volts: note: check curr: 1 min: 1 max: 1 width (bits): data: 64 total: 64
manufacturer: Corsair part-no: CMK128GX4M4A2666C16 serial: N/A
PCI Slots:
Permissions: Unable to run dmidecode. Root privileges required.
CPU:
Info: model: AMD Ryzen Threadripper 1920X bits: 64 type: MT MCP arch: Zen
level: v3 note: check built: 2017-19 process: GF 14nm family: 0x17 (23)
model-id: 1 stepping: 1 microcode: 0x8001129
Topology: cpus: 1x dies: 1 clusters: 1 cores: 12 threads: 24 tpc: 2
smt: enabled cache: L1: 1.1 MiB desc: d-12x32 KiB; i-12x64 KiB L2: 6 MiB
desc: 12x512 KiB L3: 32 MiB desc: 4x8 MiB
Speed (MHz): avg: 2843 min/max: 2200/3500 boost: disabled scaling:
driver: acpi-cpufreq governor: schedutil cores: 1: 2843 2: 2843 3: 2843
4: 2843 5: 2843 6: 2843 7: 2843 8: 2843 9: 2843 10: 2843 11: 2843 12: 2843
13: 2843 14: 2843 15: 2843 16: 2843 17: 2843 18: 2843 19: 2843 20: 2843
21: 2843 22: 2843 23: 2843 24: 2843 bogomips: 168069
Flags: 3dnowprefetch abm adx aes amd_dcm aperfmperf apic arat avic avx
avx2 bmi1 bmi2 bpext clflush clflushopt clzero cmov cmp_legacy
constant_tsc cpb cpuid cr8_legacy cx16 cx8 de decodeassists extapic
extd_apicid f16c flushbyasid fma fpu fsgsbase fxsr fxsr_opt ht hw_pstate
lahf_lm lbrv lm mca mce misalignsse mmx mmxext monitor movbe msr mtrr
mwaitx nonstop_tsc nopl npt nrip_save nx osvw overflow_recov pae pat
pausefilter pclmulqdq pdpe1gb perfctr_core perfctr_llc perfctr_nb
pfthreshold pge pni popcnt pse pse36 rapl rdrand rdseed rdtscp rep_good
sep sev sha_ni skinit smap smca smep ssbd sse sse2 sse4_1 sse4_2 sse4a
ssse3 succor svm svm_lock syscall tce topoext tsc tsc_scale
v_vmsave_vmload vgif vmcb_clean vme vmmcall wdt xgetbv1 xsave xsavec
xsaveerptr xsaveopt
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: indirect_target_selection status: Not affected
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: reg_file_data_sampling status: Not affected
Type: retbleed mitigation: untrained return thunk; SMT vulnerable
Type: spec_rstack_overflow status: Vulnerable: Safe RET, no microcode
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and \__user pointer
sanitization
Type: spectre_v2 mitigation: Retpolines; STIBP: disabled; RSB filling;
PBRSB-eIBRS: Not affected; BHI: Not affected
Type: srbds status: Not affected
Type: tsa status: Not affected
Type: tsx_async_abort status: Not affected
Type: vmscape status: Vulnerable
Graphics:
Device-1: Advanced Micro Devices \[AMD/ATI\] Navi 48 \[Radeon RX 9070/9070
XT/9070 GRE\] vendor: Sapphire driver: amdgpu v: kernel arch: RDNA-4
code: Navi-4x process: TSMC n4 (4nm) built: 2025+ pcie: gen: 5
speed: 32 GT/s lanes: 16 ports: active: DP-1 empty: DP-2, HDMI-A-1,
HDMI-A-2, Writeback-1 bus-ID: 0c:00.0 chip-ID: 1002:7550 class-ID: 0300
Display: x11 server: X.Org v: 21.1.18 with: Xwayland v: 24.1.8
compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting,radeon
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 1680x1050 s-dpi: 96 s-size: 444x277mm (17.48x10.91")
s-diag: 523mm (20.6")
Monitor-1: DP-1 mapped: DisplayPort-0 model: EIZO NANAO S2233W
serial:  built: 2009 res: mode: 1680x1050 hz: 60 scale: 100% (1)
dpi: 90 gamma: 1.2 chroma: red: x: 0.659 y: 0.325 green: x: 0.216 y: 0.682
blue: x: 0.145 y: 0.071 white: x: 0.314 y: 0.329
size: 474x297mm (18.66x11.69") diag: 566mm (22.3") ratio: 16:10
modes: 1680x1050, 1280x1024, 1440x900, 1280x960, 1280x800, 1152x864,
1280x720, 1024x768, 800x600, 640x480, 720x400
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi x11:
drv: radeonsi inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.2.3-arch1.2
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 9070 (radeonsi
gfx1201 LLVM 20.1.8 DRM 3.61 6.12.48-1-MANJARO) device-ID: 1002:7550
memory: 15.62 GiB unified: no
API: Vulkan v: 1.4.321 layers: 8 device: 0 type: discrete-gpu name: AMD
Radeon RX 9070 (RADV GFX1201) driver: mesa radv v: 25.2.3-arch1.2
device-ID: 1002:7550 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: lact,radeontop wl: wayland-info
x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Creative Labs CA0132 Sound Core3D \[Sound Blaster Recon3D /
Z-Series BlasterX AE-5 Plus\] driver: snd_hda_intel v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 1102:0012 class-ID: 0403
Device-2: Advanced Micro Devices \[AMD/ATI\] Navi 48 HDMI/DP Audio
driver: snd_hda_intel v: kernel pcie: gen: 5 speed: 32 GT/s lanes: 16
bus-ID: 0c:00.1 chip-ID: 1002:ab40 class-ID: 0403
API: ALSA v: k6.12.48-1-MANJARO status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: JACK v: 1.9.22 status: off tools: N/A
Server-3: PipeWire v: 1.4.8 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel I211 Gigabit Network vendor: Micro-Star MSI driver: igb
v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 7000 bus-ID: 08:00.0
chip-ID: 8086:1539 class-ID: 0200
IF: enp8s0 state: up speed: 1000 Mbps duplex: full mac: 
Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: TP-LINK TG-3468 driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: f000 bus-ID: 43:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp67s0 state: down mac: 
Info: services: NetworkManager
WAN IP: No WAN IP found. Connected to web? SSL issues? Try enabling dig
Bluetooth:
Message: No bluetooth data found.
Logical:
Message: No logical block device data found.
RAID:
Message: No RAID data found.
Drives:
Local Storage: total: 10.92 TiB used: 5.58 TiB (51.1%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial:  fw-rev: 5B2QGXA7 temp: 34.9 C
scheme: MBR
ID-2: /dev/nvme1n1 maj-min: 259:4 vendor: Western Digital
model: WD BLACK SN770 2TB size: 1.82 TiB block-size: physical: 512 B
logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: 
fw-rev: 731130WD temp: 32.9 C scheme: MBR
ID-3: /dev/sda maj-min: 8:0 vendor: Seagate model: ST8000NM000A-2KE101
size: 7.28 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 7200 serial:  fw-rev: SC03 scheme: GPT
ID-4: /dev/sdb maj-min: 8:16 vendor: Western Digital
model: WD1003FZEX-00MK2A0 size: 931.51 GiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 7200 serial: 
fw-rev: 1A01 scheme: MBR
Optical-1: /dev/sr0 vendor: HL-DT-ST model: DVDRAM GH24NSD1 rev: LG00
dev-links: cdrom
Features: speed: 12 multisession: yes audio: yes dvd: yes
rw: cd-r,cd-rw,dvd-r,dvd-ram state: running
Partition:
ID-1: / raw-size: 1.81 TiB size: 1.78 TiB (98.37%) used: 381.63 GiB (20.9%)
fs: ext4 dev: /dev/nvme1n1p1 maj-min: 259:5 label: N/A
uuid: 7577eecb-23f7-4a07-8eac-a01a3d8d9240
ID-2: /run/media/pb/Volume raw-size: 7.28 TiB size: 7.28 TiB (100.00%)
used: 5.21 TiB (71.6%) fs: ntfs dev: /dev/sda2 maj-min: 8:2 label: Volume
uuid: C8465A87465A7662
Swap:
Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: partition size: 8.8 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/nvme1n1p2 maj-min: 259:6 label: swap
uuid: 8708d9e9-4e5b-490b-b93e-465abbd4a30a
Unmounted:
ID-1: /dev/nvme0n1p1 maj-min: 259:1 size: 549 MiB fs: ntfs
label: System-reserviert uuid: 707C2F317C2EF190
ID-2: /dev/nvme0n1p2 maj-min: 259:2 size: 930.46 GiB fs: ntfs label: N/A
uuid: 886E30756E305E5E
ID-3: /dev/nvme0n1p3 maj-min: 259:3 size: 530 MiB fs: ntfs label: N/A
uuid: 1CB842C1B84298E2
ID-4: /dev/sda1 maj-min: 8:1 size: 128 MiB fs: 
label: N/A uuid: N/A
ID-5: /dev/sdb1 maj-min: 8:17 size: 931.51 GiB fs: ntfs label: Volume
uuid: 3AFD0023FCFFD6DB
USB:
Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 14 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Device-1: 1-12:2 info: \[Maxxter\] USB GAMING MOUSE type: mouse,keyboard
driver: hid-generic,usbhid interfaces: 2 rev: 1.1
speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0 power: 100mA
chip-ID: 18f8:1286 class-ID: 0300
Hub-2: 2-0:1 info: super-speed hub ports: 8 rev: 3.1
speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
class-ID: 0900
Hub-3: 3-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Hub-4: 4-0:1 info: super-speed hub ports: 2 rev: 3.1
speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
class-ID: 0900
Hub-5: 5-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Hub-6: 6-0:1 info: super-speed hub ports: 4 rev: 3.0
speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 1d6b:0003
class-ID: 0900
Hub-7: 7-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Hub-8: 8-0:1 info: super-speed hub ports: 4 rev: 3.0
speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 1d6b:0003
class-ID: 0900
Sensors:
System Temperatures: cpu: 35.0 C mobo: N/A gpu: amdgpu temp: 41.0 C
mem: 40.0 C
Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Repos:
Packages: pm: pacman pkgs: 1886 libs: 451 tools: octopi,pamac,yay
pm: flatpak pkgs: 0
Active pacman repo servers in: /etc/pacman.d/mirrorlist
1: https://manjaro.ynh.ovh/stable/$repo/$arch
2: https://mirror.netcologne.de/manjaro/stable/$repo/$arch
3: https://ftp.tsukuba.wide.ad.jp/Linux/manjaro/stable/$repo/$arch
4: https://manjaro.mirrors.uk2.net/stable/$repo/$arch
5: https://mirror.init7.net/manjaro/stable/$repo/$arch
6: https://ftp.belnet.be/mirrors/manjaro/repos/stable/$repo/$arch
7: https://coresite.mm.fcix.net/manjaro/stable/$repo/$arch
8: https://mirror.alpix.eu/manjaro/stable/$repo/$arch
9: https://distrohub.kyiv.ua/manjaro/stable/$repo/$arch
10: https://repo.ialab.dsu.edu/manjaro/stable/$repo/$arch
11: https://mirror.datacenter.by/pub/mirrors/manjaro/stable/$repo/$arch
12: https://mirrors.dotsrc.org/manjaro/stable/$repo/$arch
13: https://ftp.psnc.pl/linux/manjaro/stable/$repo/$arch
14: https://manjaro.syxpi.fr/manjaro/stable/$repo/$arch
15: https://mirrors.nic.cz/manjaro/stable/$repo/$arch
16: https://mirrors.ucr.ac.cr/manjaro/stable/$repo/$arch
17: https://mirror.it4i.cz/manjaro/stable/$repo/$arch
18: http://ossmirror.mycloud.services/os/linux/manjaro/stable/$repo/$arch
19: https://mirrors2.manjaro.org/stable/$repo/$arch
20: https://ftp.snt.utwente.nl/pub/linux/manjaro/stable/$repo/$arch
21: https://mirror.alwyzon.net/manjaro/stable/$repo/$arch
22: https://cofractal-ewr.mm.fcix.net/manjaro/stable/$repo/$arch
23: https://mirror.vinehost.net/manjaro/stable/$repo/$arch
24: https://ct.mirror.garr.it/mirrors/manjaro/stable/$repo/$arch
25: https://mirrors.sonic.net/manjaro/stable/$repo/$arch
26: https://quantum-mirror.hu/mirrors/pub/manjaro/stable/$repo/$arch
27: https://ftp.cc.uoc.gr/mirrors/linux/manjaro/stable/$repo/$arch
28: https://manjaro.mirror.wearetriple.com/stable/$repo/$arch
29: https://edgeuno-bog2.mm.fcix.net/manjaro/stable/$repo/$arch
30: https://manjaro.c3sl.ufpr.br/stable/$repo/$arch
31: https://mirror.bouwhuis.network/manjaro/stable/$repo/$arch
32: https://mirror.koddos.net/manjaro/stable/$repo/$arch
33: https://bd.mirror.vanehost.com/Manjaro/stable/$repo/$arch
34: https://mirrors.up.pt/pub/manjaro/stable/$repo/$arch
35: https://forksystems.mm.fcix.net/manjaro/stable/$repo/$arch
36: https://mirror.ibakerserver.pt/manjaro/stable/$repo/$arch
37: https://ftpmirror1.infania.net/mirror/manjaro/stable/$repo/$arch
38: https://mirror.nju.edu.cn/manjaro/stable/$repo/$arch
39: https://irltoolkit.mm.fcix.net/manjaro/stable/$repo/$arch
40: https://ohioix.mm.fcix.net/manjaro/stable/$repo/$arch
41: https://www.mirrorservice.org/sites/repo.manjaro.org/repos/stable/$repo/$arch
42: https://gsl-syd.mm.fcix.net/manjaro/stable/$repo/$arch
43: https://ftp.caliu.cat/pub/distribucions/manjaro/stable/$repo/$arch
44: https://mirror.aarnet.edu.au/pub/manjaro/stable/$repo/$arch
45: https://linorg.usp.br/manjaro/stable/$repo/$arch
46: https://free.nchc.org.tw/manjaro/stable/$repo/$arch
47: https://mirror.meowsmp.net/manjaro/stable/$repo/$arch
48: https://mirror.truenetwork.ru/manjaro/stable/$repo/$arch
49: https://mirror.futureweb.be/manjaro/stable/$repo/$arch
50: https://manjaro.grena.ge/stable/$repo/$arch
51: https://ipng.mm.fcix.net/manjaro/stable/$repo/$arch
52: https://mirrors.jlu.edu.cn/manjaro/stable/$repo/$arch
53: https://manjaro.mirror.garr.it/manjaro/stable/$repo/$arch
54: https://manjarolinux-mirror.cloud.mu/stable/$repo/$arch
55: https://manjaro.kurdy.org/stable/$repo/$arch
56: https://nocix.mm.fcix.net/manjaro/stable/$repo/$arch
57: https://mnvoip.mm.fcix.net/manjaro/stable/$repo/$arch
58: https://mirror.xeonbd.com/manjaro/stable/$repo/$arch
59: https://mirror.komelt.dev/manjaro/stable/$repo/$arch
60: https://mirror.csclub.uwaterloo.ca/manjaro/stable/$repo/$arch
61: https://ftp.free.org/mirrors/repo.manjaro.org/repos/stable/$repo/$arch
62: https://manjaro.mirror.liquidtelecom.com/stable/$repo/$arch
63: https://mirrors.ocf.berkeley.edu/manjaro/stable/$repo/$arch
64: https://mirror.dkm.cz/manjaro/stable/$repo/$arch
65: https://ask4.mm.fcix.net/manjaro/stable/$repo/$arch
66: https://mirror.math.princeton.edu/pub/manjaro/stable/$repo/$arch
67: https://mirrors.cicku.me/manjaro/stable/$repo/$arch
68: https://mirror.2degrees.nz/manjaro/stable/$repo/$arch
69: https://volico.mm.fcix.net/manjaro/stable/$repo/$arch
70: https://manjaro.repo.cure.edu.uy/stable/$repo/$arch
71: https://ftp.gwdg.de/pub/linux/manjaro/stable/$repo/$arch
72: https://mirror1.sox.rs/manjaro/stable/$repo/$arch
73: https://southfront.mm.fcix.net/manjaro/stable/$repo/$arch
74: https://mirror.xenyth.net/manjaro/stable/$repo/$arch
75: https://mirror.telepoint.bg/manjaro/stable/$repo/$arch
76: https://ftp.halifax.rwth-aachen.de/manjaro/stable/$repo/$arch
77: https://mirror.phoepsilonix.love/manjaro/stable/$repo/$arch
78: https://mirror.freedif.org/Manjaro/stable/$repo/$arch
79: https://codingflyboy.mm.fcix.net/manjaro/stable/$repo/$arch
80: https://ftp.linux.org.tr/manjaro/stable/$repo/$arch
81: https://nnenix.mm.fcix.net/manjaro/stable/$repo/$arch
82: https://mirror.easyname.at/manjaro/stable/$repo/$arch
83: https://fosszone.csd.auth.gr/manjaro/stable/$repo/$arch
84: https://mirror.kamtv.ru/manjaro/stable/$repo/$arch
85: https://mirror.fcix.net/manjaro/stable/$repo/$arch
86: http://ftp.uni-kl.de/pub/linux/manjaro/stable/$repo/$arch
87: https://mirror.23m.com/manjaro/stable/$repo/$arch
88: https://mirrors.eric.ovh/manjaro/stable/$repo/$arch
89: https://mirrors.gigenet.com/manjaro/stable/$repo/$arch
90: https://mirror.hostiko.network/manjaro/stable/$repo/$arch
91: https://mirror.raiolanetworks.com/manjaro/stable/$repo/$arch
92: https://opencolo.mm.fcix.net/manjaro/stable/$repo/$arch
93: https://mirrors.sjtug.sjtu.edu.cn/manjaro/stable/$repo/$arch
94: https://manjaro.mirrors.lavatech.top/stable/$repo/$arch
95: https://mirror.mobinhost.com/manjaro/stable/$repo/$arch
96: https://muug.ca/mirror/manjaro/stable/$repo/$arch
97: https://mirrors.atlas.net.co/manjaro/stable/$repo/$arch
98: https://mirrors.xtom.jp/manjaro/stable/$repo/$arch
99: https://ftp.rz.tu-bs.de/pub/mirror/manjaro.org/repos/stable/$repo/$arch
100: https://manjaro.ipacct.com/manjaro/stable/$repo/$arch
101: https://ziply.mm.fcix.net/manjaro/stable/$repo/$arch
102: https://ftp.lysator.liu.se/pub/manjaro/stable/$repo/$arch
103: https://ftp.tu-chemnitz.de/pub/linux/manjaro/stable/$repo/$arch
104: https://mirrors.manjaro.org/repo/stable/$repo/$arch
105: https://kartolo.sby.datautama.net.id/manjaro/stable/$repo/$arch
106: https://ba.mirror.garr.it/mirrors/manjaro/stable/$repo/$arch
Processes:
CPU top: 5 of 489
1: cpu: 200% command: ps pid: 13038 mem: 4.07 MiB (0.0%)
2: cpu: 99.2% command: clamscan pid: 4047 mem: 1405.4 MiB (1.0%)
3: cpu: 7.0% command: QtWebEngineProcess pid: 11321 mem: 419.5 MiB (0.3%)
4: cpu: 6.3% command: ksgrd_network_helper pid: 5397 mem: 6.78 MiB (0.0%)
5: cpu: 6.0% command: plasmashell pid: 1239 mem: 515.2 MiB (0.4%)
Memory top: 5 of 489
1: mem: 1405.4 MiB (1.0%) command: clamscan pid: 4047 cpu: 99.2%
2: mem: 832.8 MiB (0.6%) command: konqueror pid: 5744 cpu: 4.2%
3: mem: 515.2 MiB (0.4%) command: plasmashell pid: 1239 cpu: 6.0%
4: mem: 473.9 MiB (0.3%) command: plasma-systemmonitor pid: 5363 cpu: 4.6%
5: mem: 419.5 MiB (0.3%) command: QtWebEngineProcess pid: 11321 cpu: 7.0%
Info:
Processes: 489 Power: uptime: 2h 12m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 50.25 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
tool: systemctl
Compilers: clang: 20.1.8 gcc: 15.2.1 Shell: Zsh v: 5.9 default: Bash
v: 5.3.3 running-in: konsole inxi: 3.3.39

Mod edit (scotty65): changed quoted terminal output to correctly formatted code. In future, please do not use the “Quote” button for terminal output. Instead, place 3 backticks (```) on the lines before and after the terminal output, or highlight the output in the editor and click on the “Preformatted text” (</>) button. You can also use the shortcut Ctrl+E.

Mod edit:- Please see How to Post Command Output as Preformatted Text :eyes:

The link has been given previously (above). By virtue of using the forum you are expected to follow appropriate guidelines for presentation of content.


Maybe important: The bootprotokoll in Windows is activated. But the boot-loops are not listed. Whatever the reason is, it is between grub and the start of the bootprotokoll of Windows.

Using Google Translate bootprotokoll translates from German as “boot log”, or when the word is properly separated as boot protokoll, it translates as “boot protocol”.

In either case, this makes little sense - Could you please explain what you mean by “bootprotokoll” and “boot loops”?

The latter sounds like a breakfast cereal.


If I am understanding your description properly – and I should mention your use of English is sometimes difficult to interpret – it could be that one OS is booting as UEFI and the other is not.

We can quickly test for each OS.


Manjaro:

In Manjaro, please provide the output of the following command (enter it exactly as written) – it will print either UEFI or BIOS:

[ -d /sys/firmware/efi ] && echo UEFI || echo BIOS

Windows:

In Windows, please open an administrative CMD/PowerShell prompt and enter the following command:

bcdedit

Look for PATH below the “Windows Boot Loader” section:

  • If it contains \EFI\MICROSOFT\BOOT then Windows has booted as UEFI (preferred).
  • If it contains \Windows\system32\winload.exe then Windows has booted using CSM (Legacy mode).

Knowing that both Manjaro and Windows are booting as UEFI will rule out this possible cause.


Note that both Manjaro and Windows are expected to boot with the same technology – either UEFI or BIOS – in order to co-exist efficiently; otherwise, Windows will force a reboot, which is what your description seems to imply.


If this problem is a result of using “Sleep Timer Ultimate” on Windows, then I’m afraid it has nothing to do with Manjaro and no support should be offered. :eyes:

All that can really be suggested in to uninstall “Sleep Timer Ultimate” and never use it again.


However, one possible contributor might be that you have Windows Fast Startup enabled – this must be disabled when multi-booting with any flavour of Linux.

Note: Despite the popularity of multi-booting Linux and Windows, it is not a supported scenario.


Disable Fast Startup:

In Windows, please open an administrative CMD/PowerShell prompt and enter the following command:

powercfg /h off

That’s it. Fast Startup should now be disabled.


Regards.

1 Like

Boot loop: It means, that Windows doesn’t finish the boot process but reboots permanently. The phraseology to describe the problem is used by texts written in English, so i used it.

Boot protocol: If activated it will log the boot process of windows.

Meanwhile I Windows started in a infinite boot loop without the use of Sleep Timer the day before.

As I have written in the first post, the problems started after the installation of Manjaro. The last seven years the PC worked without a serious problem.

As I have already written twice: Fast Start ist disabled.

In Manjaro, please provide the output of the following command (enter it exactly as written) – it will print either UEFI or BIOS:

You will get the answer as soon as possible.

Checked: Windows and Linux are both booting as BIOS.

Btw: Could you please explain me the Linux command? I know the echo command but you use it in a different way than I have seen it.

[ -d /sys/firmware/efi ] && echo UEFI || echo BIOS

translation of the command:

if the directory /sys/firmware/efi exists, print (echo) “UEFI” -
if it doesn’t, print (echo) “BIOS”

it all depends on whether the the first part is true
it’s just evaluating the first part
[ -d /sys/firmware/efi ]
and, depending on it’s logical value, prints either the first or the second string

This one would also work in the same way:

[ -d /sys/firmware/efi ] && echo the_directory_exists || echo some_random_string

It just checks for the existence of the directory /sys/firmware/efi

If it does exist, the system is UEFI - it’s not if it’s not.

ls /sys/firmware/efi

would also serve the same purpose -
it either gives the contents of the directory,
or it says:
ls: cannot access '/sys/firmware/efi': No such file or directory

1 Like

The command is ready to be optionally placed into a script. What it does is to check whether /sys/firmware/efi exists - if it does, UEFI is echoed - if it doesn’t, BIOS is echoed.

Edit:- I see @Nachlese has already answered. :wink:

Its’s actually a shorthand for… :backhand_index_pointing_down:

if [ -d /sys/firmware/efi ]
then
   echo UEFI
else
   echo BIOS
fi

:wink:

1 Like

… what I said - with a lot more words as would have been needed - as usual :wink:

The idea was to explain the logic of the command structure to the newbie. :wink:

“Give a man a fish”, versus “teach a man to fish”, and all that. :wink: