-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
USB device not working after restart, but appears after the laptop is suspended and woken up #5
Comments
I'm confused.
while
so the modem appears via its PCI interface (only)? On the other hand
which means that the modem is usable. |
I have a possibly related issue:
even when |
Thanks @DDvO for sharing details. After fresh reboot, I don't see the USB device, so I'm not even seeing the modem devices: After fresh reboot:
But I see the WWAN as the PCI device still:
My kernel also complains about a missing signing certificate during
From my
First I was wondering if my ACPI works, but it seems ok:
|
I think the whole issue is in the ACPI reset call. Following the original xmm2usb script, I was able to issue successfully: But the ACPI call is failing: with this error in So I think the suspect/resume basically does what this ACPI call should do. But I still don't know why, the
|
@juhovh I have tried suspending etc and banging on all sorts of the ACPI space with no luck. On the other thread [(https://github.com/xmm7360/xmm7360-usb-modeswitch/issues/2)] there is my DSDT decompiled. I'll keep trying but if I've missed anything obvious it would be nice to know. |
@neurotensin Do you have a link to the DKMS scripts? I could add them here as well. @kamilsamaj-accolade I'm not really that surprised if ACPI reset doesn't work for all systems, ACPI is occasionally a bit of a mess. The |
@juvoh I pasted my mini "tutorial" on the other thread - feel free to add it - I also did one for acpi_call ,simply regexp $MODULE_NAME and it works. All though both modules need to add "depmod -A" in the Makefile's "install" clause (after the install), as it's need to get the symbols into the kernel. |
To make this module work correctly it needs to handle powerstates -I found a curious error message on the other thread If you could add something to module so that when it sleeps/goes off , it doesn't wake up - the module keeps the PCI address but also propagates a wakeup cascade - ideally it would stay off and perhaps the USB interface would be activated as power is restored. |
Lenovo Thinkpad P53 here. Not having much luck:
Device only shows as PCI device. Not /dev/ttyAMA devices found. Suspend/resume not help.
|
@paaland I have the same results - I suspect the P53 has a more enterprise devices has some hotplug/docking features that wakes everything up. But the good news is I have isolated the following:
It might be possible to change the PCI routing in the DSDT to permanently disconnect the 00:53 link so it survives a suspend, but I am no expert, though I know where to look (PD06 or AR06 depending on interrupt choices) I've ordered some Kapton tape as a final backup... |
Hi @juhovh ,
first and foremost, BIG thanks for your project, my WWAN is finally working! I'm just having issues of not seeing the USB device right after reboot, but I have to suspend the laptop and wake it up.
That's what I did:
I followed the steps from @DDvO's issue:
After restart, the module gets loaded correctly, I can see it with:
But I still see the device being in PCI mode:
After I suspend and wake up the laptop, the USB device appears:
and of course the
lspci
doesn't see the device anymore:Just for clarity, I unlocked the FCC and switched to USB with:
Would you know why I don't see it immediately after the restart, please? I'm guessing it's a wrong order of loading modules but I don't know how to troubleshoot that.
Thanks a lot.
Kamil
The text was updated successfully, but these errors were encountered: