LAN network connection is not re-established when awaking from suspend

[Wikinaut]

Qubes OS version (e.g., R3.2):

• 3.2

Hardware

• INTEL NUC i5 D54250WYKH

Problem/bug

When awaking from hibernation, the LAN network connection is not established, even when the connection checkbox (in the settings in the top right-hand corner) is still activated.

I have then to deactivate and reactivate the network checkbox to re-establish the network connection.

Suggestion

Add code to check and reconnect when awaking from hibernation.

[andrewdavidwong]

I assume you mean "suspend," since Xen doesn't support hibernation.

Appears to be related to #1663.

[andrewdavidwong]

I assume you mean "suspend," since Xen doesn't support hibernation.

Appears to be related to #1663.

[Wikinaut]

@andrewdavidwong

In my German Qubes system I (currently) see

• Bildschirm sperren (lock screen)
• Bereitschaft (standby)
• Ruhezustand
• shutdown
• restart

I indeed mean "Ruhezustand". German wikipedia translates with "Hibernation", but also "suspend to...."

So you are right.

[Wikinaut]

@andrewdavidwong

In my German Qubes system I (currently) see

• Bildschirm sperren (lock screen)
• Bereitschaft (standby)
• Ruhezustand
• shutdown
• restart

I indeed mean "Ruhezustand". German wikipedia translates with "Hibernation", but also "suspend to...."

So you are right.

[Wikinaut]

Please find a solution. Everytime when my computer is awakening from suspense, I have to close/open the LAN connection in order to get it working. This could be done automagically... please

[Wikinaut]

Please find a solution. Everytime when my computer is awakening from suspense, I have to close/open the LAN connection in order to get it working. This could be done automagically... please

[jpouellet]

See if reloading your network card's driver(s) works around the problem. Instructions here apply equally to other devices besides wireless cards.

[jpouellet]

See if reloading your network card's driver(s) works around the problem. Instructions here apply equally to other devices besides wireless cards.

[Wikinaut]

note to myself: Try https://www.qubes-os.org/doc/wireless-troubleshooting/#automatically-reloading-drivers-on-suspendresume

[Wikinaut]

note to myself: Try https://www.qubes-os.org/doc/wireless-troubleshooting/#automatically-reloading-drivers-on-suspendresume

[Wikinaut]

Your tip was helpful, apparently. However, I think, the setting should be automatically activated (sorry, I cannot help in this core issue, but will help testing new versions, if this is wanted.)

[Wikinaut]

Your tip was helpful, apparently. However, I think, the setting should be automatically activated (sorry, I cannot help in this core issue, but will help testing new versions, if this is wanted.)

[Wikinaut]

(reopened, because the issue was tagged for being solved/handled in the next release.)

[Wikinaut]

(reopened, because the issue was tagged for being solved/handled in the next release.)

[jpouellet]

I would just close. This is not qubes' bug, this is a problem with the combination of {hardware, network card driver, kernel version} you use, which is upstream's issue.

Also, I do not think reloading drivers automatically is something we should do by default, because whether or not we should (and which drivers we should - which is not easy to automatically determine) depends on the hw model and version of things, and such lists become quickly unmaintained.

[jpouellet]

I would just close. This is not qubes' bug, this is a problem with the combination of {hardware, network card driver, kernel version} you use, which is upstream's issue.

Also, I do not think reloading drivers automatically is something we should do by default, because whether or not we should (and which drivers we should - which is not easy to automatically determine) depends on the hw model and version of things, and such lists become quickly unmaintained.

[Wikinaut]

@jpouellet I want the decision to close - or to let it open - up to the Qubes Core maintainers.
Thanks for help, I understand the issue, but perhaps more users may have the same problem and you cannot expect everyone to go the hard way ...

[Wikinaut]

@jpouellet I want the decision to close - or to let it open - up to the Qubes Core maintainers.
Thanks for help, I understand the issue, but perhaps more users may have the same problem and you cannot expect everyone to go the hard way ...

[andrewdavidwong]

Being either an upstream bug or a hardware-configuration-specific problem would be sufficient by itself to merit closing.

[andrewdavidwong]

Being either an upstream bug or a hardware-configuration-specific problem would be sufficient by itself to merit closing.