Booting after install - Mother Board Series X170KM-G

[Black.Widow]

Hello

Just got my new Laptop

Based on:

insyde Bios
I9 10900 CPU
32gb
Mother Board Series X170KM-G
NVIDIA GEFORCE RTX 3070 8GB

The install goes without a hitch. But when it goes to reboot. I do that and it comes up with the BIOS LOGO and then it just stays there, and after 90 seconds it will then boot up.

Does anyone have any ideas

regards

Mark

[Black.Widow]

I have tried a number of other KDE/PLASMA based distro's and all have this problem. Some of them the only way I can get in, is to go to Advanced Options in boot up and then choose the Recovery Option it will then boot it.

[jlittle]

But when it goes to reboot. I do that and it comes up with the BIOS LOGO and then it just stays there, and after 90 seconds it will then boot up.

That sounds like a systemd timeout; they often default to 90 s. I often got one when shutting down, (because kwin doesn't terminate when told to) until I changed the timeout.

The BIOS logo suggests that your delay is happening after the start up, not shutting down.

I suggest allowing the start-up messages, it might give a clue. To do so, edit the /etc/default/grub file to remove the words "quiet splash" where they appear, and update grub. Maybe:

cp /etc/default/grub ~/default-grub-backup
sudo nano /etc/default/grub
sudo update-grub

[Black.Widow]

That sounds like a systemd timeout; they often default to 90 s. I often got one when shutting down, (because kwin doesn't terminate when told to) until I changed the timeout.

The BIOS logo suggests that your delay is happening after the start up, not shutting down.

I suggest allowing the start-up messages, it might give a clue. To do so, edit the /etc/default/grub file to remove the words "quiet splash" where they appear, and update grub. Maybe:

cp /etc/default/grub ~/default-grub-backup
sudo nano /etc/default/grub
sudo update-grub

Hello

Thank you so much for the reply. So sorry it took so long to reply. Not been so well.

Mark

Here is the screen shot

[jlittle]

(I've seen the screenshot, I presume it's the one your PM was about.)

google turns up this post, looks a lot like your problem.

For a one off test of that fix, you can press "e" while on the grub menu, and move the cursor to the "linux" line and add "intel_iommu=off" to the end.

To apply that more persistently, you could edit /etc/default/grub (with, say, sudo nano in a konsole) and add that to the GRUB_CMDLINE_LINUX variable, and run sudo update-grub

[oshunluvr]

Nice work jlittle.

[Black.Widow]

Thank you so much I will give it a go in a while. I had trouble logging into the forums. I have so missed using Kubuntu since getting my new nice power machine

[Black.Widow]

(I've seen the screenshot, I presume it's the one your PM was about.)

google turns up this post, looks a lot like your problem.

For a one off test of that fix, you can press "e" while on the grub menu, and move the cursor to the "linux" line and add "intel_iommu=off" to the end.

To apply that more persistently, you could edit /etc/default/grub (with, say, sudo nano in a konsole) and add that to the GRUB_CMDLINE_LINUX variable, and run sudo update-grub

Hello again

Thank you so much for your reply. This made no difference. You know this only happens with KDE/PLASMA based Distro. I tried Linux Mint and do not get the DRHD/DMA Wite Faults.

Just wish the admins of Kubuntu would see this

[oshunluvr]

Kubuntu admins

Sounds like it could be a conflict with the nvidia card and the internal GPU. Have you tried turning off the on-board video or removing the nvidia card to see if the boot changes?

You should probably look at your Xorg log and xsession errors as well for more clues.

[Black.Widow]

Kubuntu admins

Sounds like it could be a conflict with the nvidia card and the internal GPU. Have you tried turning off the on-board video or removing the nvidia card to see if the boot changes?

You should probably look at your Xorg log and xsession errors as well for more clues.

I have had no reply's from a single Kubuntu Admin and have no idea how to contact them directly.

[jglen490]

Have you tried the bug reporting site?

[Black.Widow]

Hello All

I have sorted it for now. I disabled my Thunder Bolt Port in my BIOS. And seems to have fix it.

For sure I will send in a bug

Mark