OMV Reboots on Shutdown after upgrade from Sardaukar to Stone Burner

Happy new year

I was thinking that the problem was related with specific hardware/components... but as I see here and on Internet, it isn't.
I saw a few posts where people got this problem five years ago (ubuntu 12.04) !
For some of them, disabling WOL resolved the problem.
I saw other posts which recommends to add something into grub config file... or new systemd services or scripts...

I tried most of them, none works.

Zitat von maxou2600

Happy new year

I was thinking that the problem was related with specific hardware/components... but as I see here and on Internet, it isn't.
I saw a few posts where people got this problem five years ago (ubuntu 12.04) !
For some of them, disabling WOL resolved the problem.
I saw other posts which recommends to add something into grub config file... or new systemd services or scripts...

I tried most of them, none works.

Alles anzeigen

Yeah the editing of grub, etc. didnt work for me also, but this helps:

apt-get install laptop-mode-tools

Hmm... well, it's weird.
If I was the only one having this bug on an old computer, happy to have a WOL function on certainly one of the first GB onboard Marvell controller...
Ok, no Luck...

But as I see on other forums, it's something like a common bug : there are many components, old, recents, cheap, expensive that have this bug.

I think that if it was a Hardware/BIOS related problem, in ten years it Would be resolved...

There must be something else. If it was only a BIOS bug, pc would keep restarting after shutdown. But after the reboot, shutdown works fine...

PS : laptop-mode-tools does not change anything for me

Thanks

Envoyé de mon FRD-L09 en utilisant Tapatalk

Thanks,

In my case, a bad/creepy/old/shitty/.../ BIOS may be thé problem.

I did some changes about ACPI (tried to disable it as well as some power management options...) At boot, OMV gives me some errors [Firmware bug] BIOS [ ...] Problem

Make sure that AMD cool and quiet Is enabled [...]...

For my computer, You're certainly right but I have some doubt about nuttah's Dell T20 which is certainly less than one year old and has i think UEFI and less bugs than my old e380

Envoyé de mon FRD-L09 en utilisant Tapatalk

There must be a solution or at least a bandaid (even if it's a BIOS bug, i'm pretty sure that There Is a way to override it...)
Especially if the problem does not appear with Windows and/or the computer shutdown normally a second Time --> it's capable to do it...

If at a second Time the computer shutdown properly (via WebGUI or shutdown -h now), there Is no reason that it can't do the same thing at a first Time.

Perhaps checking logs will help to find a weird thing...

Idea : Maybe, when we send a Magic packet, it "stays" over the system and then when we shutdown, the NIC see/receive the packet and it restarts the computer of course...

The second boot uses this packet, then when we shutdown it works, and it does not restarts because There Is no more packet...

It's not a major problem but if it can be corrected

Envoyé de mon FRD-L09 en utilisant Tapatalk

T20 WOL Shutdown after reboot Problem is solved.

Deactivate the USB 3.0 Settings in Bios and its working :-).

My actual Bios (Version A05) Settings are:
-NIC on - only LAN
-DeepSleep off
-WOL on - only LAN

i will test the Settings with DeepSleep S4/s5 an with other Bios Versions.

I will send an email to the dell support. But hopefully this can be fixed with a bios update.

Zitat von nuttah

T20 WOL Shutdown after reboot Problem is solved.

Deactivate the USB 3.0 Settings in Bios and its working :-).

My actual Bios (Version A05) Settings are:
-NIC on - only LAN
-DeepSleep off
-WOL on - only LAN

i will test the Settings with DeepSleep S4/s5 an with other Bios Versions.

I will send an email to the dell support. But hopefully this can be fixed with a bios update.

Alles anzeigen

Heya nuttah,

I just try to follow your mini guide ;-). Where in the BIOS settings did you deactivate the USB 3.0 settings/support?

Thanks!!

Zitat von nuttah

T20 WOL Shutdown after reboot Problem is solved.

Deactivate the USB 3.0 Settings in Bios and its working :-).

My actual Bios (Version A05) Settings are:
-NIC on - only LAN
-DeepSleep off
-WOL on - only LAN

i will test the Settings with DeepSleep S4/s5 an with other Bios Versions.

I will send an email to the dell support. But hopefully this can be fixed with a bios update.

Alles anzeigen

With disabled usb 3.0 at the dell t20 the shutdown command is working!
Cheers Robert

Zitat von nomax

Heya nuttah,
I just try to follow your mini guide ;-). Where in the BIOS settings did you deactivate the USB 3.0 settings/support?

Thanks!!

Please see attached picture

Zitat von no_Legend

With disabled usb 3.0 at the dell t20 the shutdown command is working!Cheers Robert

Please see attached picture

Thanks, just did, will move now the USB thumb drive where I have OMV installed to the other ports and hopefully it will work. Does anyone know why there is the correlation between the WOL and USB 3.0? Are they both on the same bus?

I installed OMV3 (last BETA) on fresh Debian 8.6 in UEFI mode on my T20 (Bios A11). Disabled USB 3.0.
But the shutdown isnt working. Installing laptop-mode-tools also doesnt help as modding GRUB with apm=power_off, etc..

That s****.

EDIT: Ok here my solution:
Add xhci_hcd.quirks=270336 to kernel boot options. Now shutdown is working.

i'm completely new with uefi.
Is it the normal way to add the kernel boot parameter?
edit /etc/default/grub
update-grub

Cheers Robert

Zitat von no_Legend

i'm completely new with uefi.
Is it the normal way to add the kernel boot parameter?
edit /etc/default/grub
update-grub

Cheers Robert

Yes, that´s correct.

nano /etc/default/grub
#look for this line an add it
GRUB_CMDLINE_LINUX_DEFAULT="quiet xhci_hcd.quirks=270336"
#save and update grub
update-grub

Zitat von krys4all

Yes, that´s correct.

Code

nano /etc/default/grub
#look for this line an add it
GRUB_CMDLINE_LINUX_DEFAULT="quiet xhci_hcd.quirks=270336"
#save and update grub
update-grub

Thanks, worked fine with me!!

How do you normally make use of WoL with the T20? Which program do you use and do you have/use different IPs for the Intel AMT interface and OMV? I tried so far WoL2 and it seems like this is causing some issues.

Thanks!

Zitat von nomax

1. How do you normally make use of WoL with the T20?
2. Which program do you use and do you have/use different IPs for the Intel AMT interface and OMV? I tried so far WoL2 and it seems like this is causing some issues.

Thanks!

1. We have only Androids at my home so we use this app.
2. For AMT I use MeshCommander. And yes the IP for AMT and OMV are diffrent.

Zitat von krys4all

1. We have only Androids at my home so we use this app.2. For AMT I use MeshCommander. And yes the IP for AMT and OMV are diffrent.

Are you able to connect to the console by intelamt?
I want to connect the console by intelamt on osx.

I found this "After booting with the additional kernel parameter console=ttyS1,115200n8, I was able to use amtterm to connect to the computer:"
Over here https://blog.philippklaus.de/2…0-with-xeon-e3-1225v3-cpu

He changed the boot option with this parameter:
GRUB_CMDLINE_LINUX_DEFAULT="quiet pci=assign-busses console=tty0 console=ttyS1,115200n8"

I'm have no idea why he add the three commands after quiet.Can somebody explain me what i need to add to enable the console to intelamt?

BR Robert

Zitat von no_Legend

Are you able to connect to the console by intelamt?I want to connect the console by intelamt on osx.

Yes, I can use the console via AMT through MeshCommander.
I used that guide.