Fedora Wont Boot Directly on Asus Laptop

Ask Fedora
1

I’ve tried plenty of Linux distro since 2020. Every shot was failure so far. I could only installed Zorin OS in 2024 and Fedora 2025. The problem starts after installation.
I cant start directly the linux distro. I have to first boot Windows10, then restart the computer and choose Fedora in grub menu. Otherwise, my fans make too much noise, and in the background, some system commands, or whatever it is, consumes so much cpu which makes my system to freeze. I am attaching some screenshots of some commands.

You can see system information below:
~$ uname -a
Linux fedora 6.14.0-63.fc42.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Mar 24 19:53:37 UTC 2025 x86_64 GNU/Linux
~$ cat /etc/fedora-release
Fedora release 42 (Adams)
~$ lspci -k | grep -EA3 'VGA|3D'
00:02.0 VGAcompatible controller: Intel Corporation HD Graphics 630 (rev 04)
Subsystem: ASUSTeK Computer Inc. Device 18a0
Kernel driver in use: i915
Kernel modules: i915
--
01:00.0 3Dcontroller: NVIDIA Corporation GM107M [GeForce GTX 950M] (rev a2)
Subsystem: ASUSTeK Computer Inc. Device 18a0
Kernel driver in use: nvidia
Kernel modules: nouveau, nvidia_drm, nvidia
~$ lsmod | grep nvidia
nvidia_drm 159744 0
nvidia_modeset 1843200 1 nvidia_drm
nvidia_uvm 4079616 0
nvidia 112271360 2nvidia_uvm,nvidia_modeset
drm_ttm_helper 16384 1 nvidia_drm
video 81920 4 asus_wmi,asus_nb_wmi,i915,nvidia_modeset

You may see the output of journalctl command in a screenshout, however, I also wanna add the output below since outputs are different.

~$ journalctl -f
Aug 31 09:47:55 fedora kernel: pcieport 0000:00:1c.2: device [8086:a112] error status/mask=00000001/00002000
Aug 31 09:47:55 fedora systemd-journald[872]: Missed 73 kernel messages
Aug 31 09:47:55 fedora kernel: pcieport 0000:00:1c.2: AER: Correctable error message received from 0000:00:1c.2
Aug 31 09:47:55 fedora systemd-journald[872]: Missed 69 kernel messages
Aug 31 09:47:55 fedora kernel: pcieport 0000:00:1c.2: AER: Correctable error message received from 0000:00:1c.2
Aug 31 09:47:55 fedora systemd-journald[872]: Missed 75 kernel messages
Aug 31 09:47:55 fedora kernel: pcieport 0000:00:1c.2: device [8086:a112] error status/mask=00000001/00002000
Aug 31 09:47:55 fedora systemd-journald[872]: Missed 90 kernel messages
Aug 31 09:47:55 fedora kernel: pcieport 0000:00:1c.2: [ 0] RxErr (First)
Aug 31 09:47:55 fedora systemd-journald[872]: Missed 73 kernel messages
Aug 31 09:47:55 fedora kernel: pcieport 0000:00:1c.2: AER: found no error details for 0000:00:1c.2
Aug 31 09:47:55 fedora systemd-journald[872]: Missed 75 kernel messages
Aug 31 09:47:55 fedora kernel: pcieport 0000:00:1c.2: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Aug 31 09:47:55 fedora systemd-journald[872]: Missed 64 kernel messages
Aug 31 09:47:55 fedora kernel: pcieport 0000:00:1c.2: AER: Correctable error message received from 0000:00:1c.2
Aug 31 09:47:55 fedora systemd-journald[872]: Missed 90 kernel messages
Aug 31 09:47:55 fedora kernel: pcieport 0000:00:1c.2: [ 0] RxErr (First)

Screenshot_20250829_192028
Screenshot_20250829_192028895×160 38.7 KB

Screenshot_20250829_193026
Screenshot_20250829_1930261902×760 222 KB

Screenshot_20250831_094704
Screenshot_20250831_0947041920×1009 225 KB

Lastly, I can add output of lshw and lspci -v commands, but the output is too long so I will add if you ask.
Thank you for your replies in advance.

2

It is going to be much easier if you take the leap and fully replace Windoze.
Fedora should work well on any non-really-new laptop, and te behaviour you describe is not normal.

The fact yo can show system info means you ave the technical ability to get Fedora to the place you want it to be.

I gave up on Windoze some years ago and I don’t regret it at all. I now run Fedora on both old cheap laptops and newish speccy CPUs.

Nvidia will work, but then you need to follow the steps on RPM Fusion to make it work properly.

If you do get rid of Windoze and fully embrace Fedora - be assured that we will help you on the journey. (I would help with dual booting too but I can’t test anything and my knowledge is not up to scratch).

3

First of all, thank you for your response.
I wanna leave windows too, that’s my goal. However, there are some programs I need to use on windows so it is better dual boot till I get a second computer.
Lastly, actually I dont think I have technical knowloedge as much as you think. I did about all of these with Gemini, and some recommendations from reddit and the other forums.

4

What windoze programs do you need? Some work well with Wine, somedo not.

We all learnt somehow. I would recommend forums and instruction tutorials over LLMs, but I guess they work well enough for simple commands. Linux is a journey, it takes time.

If you are unsure what to do, make a new thread ‘how do I install Wine’ for example.

5

Have you disabled “Fast Startup” in Windows, and “Fast Boot” in the BIOS?

If these are left enabled, they can leave hardware devices in the wrong state when Linux starts up.

I have a 2018-ish Asus laptop, and everything works smoothly on Fedora. The hardware all works out of the box (wifi, Bluetooth, webcam, touchpad, Fn+key controls for screen brightness, keyboard backlight etc). The fan is slightly loud under load, but not in normal operation.

I now have only Fedora on the machine, but initially I dualbooted with W10 (with Fast Startup and Fast Boot disabled), and that was fine too.

So hopefully it’s going to be possible to have a much better Fedora experience on this machine than you are currently having.

1 Like
6

Thank you. I am trying what you recommend but you know they are faster than starting a thread and waiting answers.
I know wine actually, but I didnt have time to test it with my programs. I am an electrical engineer and wanna use Altium, Quartus, etc.

I got an answer from a thread I started on another forum:
$ lspci -nnk -s 00:1c
Will show info about all devices on pci bus ‘1c’, and clearly identify the device ‘0000:00:1c.2’ which is the one causing all the errors.
It’s likely something like your Nvidia card or your Realtek ethernet chip.
I already installed Nvidia drivers. Do you think it could be my ethernet chip?

7

Yeah I have already done that. Fast boot and startup are disabled.