i am using garuda for a while now, everything worked fine until recently something broke and my pc reboot every time i try to shut it down.
it happened when i was trying to install and use Xrdp. (but i don't know if its related)
i did some research and i realized there is something wrong with my network adaptor and Wake-on-lan future!
i use dual boot and windows 11 works just fine and there is no problem shutting down with windows.
i even tried to test shutting down throw a live garuda OS on a flash drive, it also did not worked and the pc rebooted again!
after this happened i disabled the Wake on lan on both windows and garuda, and disabled the fast boot option in windows but it didn't worked again!
the only fix that i found is to disable the Power On by PCIE in bios options witch disables the wake on lan function also, but i can't do it because i desperately need it(Wake-on-Lan)!
things that i've tried and did not worked:
resetting the bios
adding the xhci_hcd.quirks=270336 to Kernel Parameters
trying to shut down from live garuda OS
completely disconnecting the Lan cable and then try to shut down( yes! the network adapter instantly turns the pc on even without a lan cable connected )
even shutting down from GRUB boot menu did not worked.
my Network adaptor is Intel 82579LM Gigabit Network connection and the driver i use is e1000e
I should mention again that i know there is other topics that said disabling WOL from bios fixed their problem. but what if someone needs the WOL function like me?
Lets figure it out once and for all
I just noticed something rather bizarre in your inxi output:
Did you install your driver using ndiswrapper? This should not be required as your driver is included in the kernel. If you used ndiswrapper then please uninstall that package and driver now. Try the e1000e-dkms driver package I linked earlier if the e1000e kernel module was not working properly for you. Under no circumstances would I recommend using the ndiswrapper driver these days.
I second TBG here, no one should use NDISWrapper in Linux these days. Anyone attempting to use one will just enter untested waters (given that Garuda by default uses the cutting-edge Zen kernel)
Is this a variant of the "you said reboot but I will restart" error? In that one shutdown works, but any reboot attempt bypasses 'bios' and grub (or other boot manager) to just restart. My Garuda used to do it, my MxLinux still does, but perhaps new kernels helped there too?
i was new to garuda and kinda wanted to test everything, now that i think more, the problem may have appeared when i installed a windows driver with ndiswrapper! (witch did not worked and the adaptor gone completely down)
and then i inserted the e1000e again using the modprob command and removed the windows driver.
now after you said, i completely uninstalled the ndiswrapper but the problem still exists, so im going to give other options a shot.
inxi -Faz now return
I tested e1000e-dkms driver
i also removed the previous default installed linux-firmware and instead installed linux-firmware-git
and i tested these three kernels
but weirdly none did not worked! (wake on lan is still disabled and even with the lan cable not connected the problem still persists)
i am sure that the fault is with my network adapter because when i turn in off from bios the shutdown function works fine and there will be no instant reboot.
and there is high probability that the ndiswrapper was the cause because both kernel and driver was working fine before i messed with ndiswrapper out of curiosity.
what else can i try to test? is there any specific kernel that might fix the problem? would reinstalling garuda fix the problem?
is there a chance that Windows11 (and the drivers installed on it) is the cause?
the inxi -Faz output of three kernels that i tested:
Hi, i just discovered something else! When the Turn on by PCIE from bios is disabled the garuda shutdown works well with no issue, but the shutdown button from Grub boot menu still have the reboot issue!
This can mean that its not just the network card that is faulty!
I reinstalled the garuda (from a flahs drive that i installed it in the first place with no issue)
But the problem STILL persist! I want to cry right now
Next thing i will try is disconnecting all SATA hard drives, reseting the bios and then booting into a live garuda os. If the problem fixes (wich i think will) i will uninstall that ***** windows 11 forever because it will show that that's the cause.
I'll keep in touch and update the topic in case anyone facing same issue.
i appreciate any suggestion
I checked, the manufacture is a Chinese old (not so popular) company who did not support the product. Im in Iran and because of economic problems its not that easy to find another motherboard( i know its so old ) and beside that im so curios why should this happen!
i tried to install linux-lts from octopi but it gives 404 http error code while downloading!
but i will give the rest a shot.
now that im writing this im in live garuda os, i disconnected all SATA storage devices, reseted the bios and booted here, the problem unbelievably still persist! im going crazy!
i disconnected every thing! now there is nothing here but me, live garuda and the zen kernel witch all used to work well even with the wake on lan enabled few weeks ago!
could it really be a kernel issue? if yes why does it worked fine few weeks earlier?
or is it a hardware or bios problem? and again if yes why the windows 11 works well?
my mind is blowing!
looks unfixable!
i still appreciate any suggestions.
though i guess the windows works well because of the driver it uses, but i dont know, can i simulate windows shutdown function or something like that?
I noticed something! When i shutdown the system, on that screen witch prints the log while shutting down, there is some lines of gray color having the word "can't", they fade soon and i can't read them, i think its good to investigate them also, but where can i find last shutdown log containing those lines?
I’m seeing this again on my X230. I’m pretty sure this is a kernel (or systemd?) regression, and so there’s nothing to be done but wait until it’s fixed.
)
) and beside that im so curios why should this happen!