Suspending my laptop computer breaks ethernet over firewire, exist regulates which can repair it?

As stated in this question I am making use of a firewire wire to give an exclusive network in between my laptop computer and also my desktop computer, due to the fact that it uses the screen sharing program synergy much better than making use of WIFI.

Nonetheless when I leave my workplace for the day and also I suspend my laptop computer, when I return the next day, the desktop computer and also the laptop computer can not connect over firewire any longer. The firewire0 tool still has an IP address. yet when I attempt and also sound the desktop computer I get no route to host

I'm making use of bit 2.6.35-24-generic #42-Ubuntu SMP x86_64 on Ubuntu 10.10.

Exists some means I can treat this without a reboot? Like, getting rid of some bit components and also re - putting them?

EDIT: Here is what I have actually attempted until now and also the outcomes:

[email protected]:~# dmesg|tail -n 1
[592525.204024] firewire_core: phy config: card 0, new root=ffc1, gap_count=5

[email protected]:~# modprobe -r firewire_net firewire_ohci firewire_core
[email protected]:~# modprobe -v firewire_ohci
insmod /lib/modules/2.6.35-24-generic/kernel/lib/crc-itu-t.ko 
insmod /lib/modules/2.6.35-24-generic/kernel/drivers/firewire/firewire-core.ko 
insmod /lib/modules/2.6.35-24-generic/kernel/drivers/firewire/firewire-ohci.ko 

[email protected]:~# dmesg|tail
[592525.204024] firewire_core: phy config: card 0, new root=ffc1, gap_count=5
[592563.410868] firewire_ohci: Removed fw-ohci device.
[592579.160086] firewire_ohci: Added fw-ohci device 0000:02:00.0, OHCI v1.10, 4 IR + 8 IT contexts, quirks 0x2
[592579.160137] firewire_ohci: isochronous cycle inconsistent
[592579.660294] firewire_core: created device fw0: GUID 0000000000000000, S400
[592579.663805] firewire_core: created device fw1: GUID 0017f2fffe89bce6, S400
[592579.663813] firewire_core: phy config: card 0, new root=ffc1, gap_count=5
[592579.700720] firewire_core: phy config: card 0, new root=ffc1, gap_count=5
[592579.700842] firewire_core: refreshed device fw0
[592579.702603] firewire_net: firewire0: IPv4 over FireWire on device 0000000000000000

[email protected]:~# ping stan.firewire
PING stan.firewire (192.168.100.1) 56(84) bytes of data.
From token.local (192.168.100.3) icmp_seq=1 Destination Host Unreachable
From token.local (192.168.100.3) icmp_seq=2 Destination Host Unreachable
From token.local (192.168.100.3) icmp_seq=3 Destination Host Unreachable

EDIT 2 : I additionally attempted getting rid of the components before putting on hold, and also re - putting after returning to. This did not function either: - (

EDIT 3: If I disconnect and also replug the firewire wire after returning to from suspend, I see the message:

firewire_core: BM lock failed, making local node (ffc0) root

I do not see this message when I unplug/replug prior to suspend ...

0
2019-05-13 03:59:30
Source Share
Answers: 3

I assume that ARP - table simply comes to be vacant. Attempt this:

arping -c 1 -I firewire0 remote_ip
0
2019-05-31 08:39:58
Source

Have you attempted making use of modprobe?

Running dmesg | grep firewire, I get:

[    1.192574] firewire_ohci 0000:0a:04.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
[    1.192585] firewire_ohci 0000:0a:04.0: setting latency timer to 64
...

This claims that the name of the component is firewire_ohci .

So I run (as root) modprobe -vr firewire_ohci && modprobe -v firewire_ohci. There gets rid of and also inserts the components, specifically.

0
2019-05-17 16:42:25
Source

Have you attempted getting rid of the physical wire. it needs to signal the pile that the link requires to be restored.

Disabling the firewire link and also re - allowing it might function too. You can add a script that does that automagically on resume.

DC

0
2019-05-17 16:12:20
Source