Driver Timeout at boot, dual MT7915E, UniElec U7621-06 (16M flash) Openwrt #644
Comments
|
I have the same issue, if you have openwrt in a vm is even worst, since it cant load the MT7915 sucessfully at all. |
|
The strange Thing is, the 7915 dual 2x2 2.4 and 5ghz works fine.
But little different setup, unielec 7523, and custom build with kernel
5.15.43
Greetings
Klojsch
brunosalezze ***@***.***> schrieb am Sa., 2. Juli 2022, 22:36:
… I have the same issue, if you have openwrt in a vm is even worst, since it
cant load the MT7915 sucessfully at all.
—
Reply to this email directly, view it on GitHub
<#644 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXP4KSNDUNISKR4XAOBBBQDVSCR3TANCNFSM5M73EI5Q>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I have the 7915 dual 2x2 2.4 and 5ghz, and I was not able yet to make it work in a VM or after a rmmod and modprobe. |
|
In VM? You can forget that, you need PCIE Forward from the root system.
As far as i know its only availible for AMD GPUs. I already wasted 2 days
of my life to find that out 6 months ago ;-)
brunosalezze ***@***.***> schrieb am Sa., 2. Juli 2022, 22:55:
… I have the 7915 dual 2x2 2.4 and 5ghz, and I was not able yet to make it
work in a VM or after a rmmod and modprobe.
—
Reply to this email directly, view it on GitHub
<#644 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXP4KSPQTFIRW6BA6Z754NTVSCUD7ANCNFSM5M73EI5Q>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Ok.. I'm using PCI PT with IOMMU on a Intel System, maybe its better to run barebones afterall. Stragely, this seems to work with with older wifi cards |
|
Yeah seems to be a driver prob, forward worked for me to. Could see the
card with lspci. But as far as i understand, you need a special driver on
the root system for communication. If the card would work with MHI it would
be doable in theory. Plus the forward is often only PCIE GEN 1 ( why have
no idea, but thats the case for vm Ware ).
brunosalezze ***@***.***> schrieb am Sa., 2. Juli 2022, 23:09:
… Ok.. I'm using PCI PT with IOMMU on a Intel System, maybe its better to
run barebones afterall. Stragely, this seems to work with with older wifi
cards
—
Reply to this email directly, view it on GitHub
<#644 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXP4KSLS6Q2VPPETNTNIVZDVSCVZ5ANCNFSM5M73EI5Q>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I have a dedecated System now for develope, makes life easy:-)
Intel celeron on a 1151 mainboard matx with 4gb ram and 4 pcie ports ( one
3.0 x16, 3 x1 ) for about 120 Euro:-)
Christopher Klojcnik ***@***.***> schrieb am Sa., 2.
Juli 2022, 23:18:
… Yeah seems to be a driver prob, forward worked for me to. Could see the
card with lspci. But as far as i understand, you need a special driver on
the root system for communication. If the card would work with MHI it would
be doable in theory. Plus the forward is often only PCIE GEN 1 ( why have
no idea, but thats the case for vm Ware ).
brunosalezze ***@***.***> schrieb am Sa., 2. Juli 2022,
23:09:
> Ok.. I'm using PCI PT with IOMMU on a Intel System, maybe its better to
> run barebones afterall. Stragely, this seems to work with with older wifi
> cards
>
> —
> Reply to this email directly, view it on GitHub
> <#644 (comment)>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AXP4KSLS6Q2VPPETNTNIVZDVSCVZ5ANCNFSM5M73EI5Q>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
|
I was able to make it work with a openwrt inside a proxmox by using IOMMU HW PT with a boot on startup option. I had to unplug power and power it again and the radios worked in OpenWRT and survived a VM reboot. |
|
https://unix.stackexchange.com/questions/73908/how-to-reset-cycle-power-to-a-pcie-device
Never tried it.
brunosalezze ***@***.***> schrieb am So., 3. Juli 2022, 14:52:
… I was able to make it work with a openwrt inside a proxmox by using IOMMU
HW PT with a boot on startup option. I had to unplug power and power it
again and the radios worked in OpenWRT and survived a VM reboot.
—
Reply to this email directly, view it on GitHub
<#644 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXP4KSKPSG5FHSU4LN4DJ2DVSGEHPANCNFSM5M73EI5Q>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Awsome! You could try reset power on the PCIE Port. I dont know if openwrt
can do that from inside vm. Depends on hw access.
brunosalezze ***@***.***> schrieb am So., 3. Juli 2022, 14:52:
… I was able to make it work with a openwrt inside a proxmox by using IOMMU
HW PT with a boot on startup option. I had to unplug power and power it
again and the radios worked in OpenWRT and survived a VM reboot.
—
Reply to this email directly, view it on GitHub
<#644 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXP4KSKPSG5FHSU4LN4DJ2DVSGEHPANCNFSM5M73EI5Q>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I believe this issue is the same one I am having which I have reported here: openwrt/openwrt#12359 The hint is |
|
I also have a VM setup with openwrt as guest under Ubuntu 22.04 with 6.1
Kernel. Machine is a HP Z240 SFF, I7 6700, 40gb ddr4 2400.
KVM/QEMU as Hypervisor. PCIE passthrough to MT7916 and the intel onboard
nic.
Also had some trouble after a few days that devices could no longer connect
or could connect but where kicked after some seconds. That is with snapshot
and testfw.
I build myself a 22.03 image on 5.10 Basis. Now everything works perfect
but at that state no 6e is availible.
Sadly nothing in the logs that would indicate why that happens.
Caleb James DeLisle ***@***.***> schrieb am Mi., 12. Apr.
2023, 10:52:
… I believe this issue is the same one I am having which I have reported
here: openwrt/openwrt#12359
<openwrt/openwrt#12359>
The hint is pci 0000:00:01.0: enabling device (0000 -> 0003) which means
the PCI bridge is coming up *without* bus mastering enabled.
—
Reply to this email directly, view it on GitHub
<#644 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXP4KSLPGT6FV2MHWATN67TXAZUNFANCNFSM5M73EI5Q>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Boot from poweroff works perfect, when I reboot the system the driver seems to have a problem. If i only use one of the two modules, everything is alright.
rmmod mt7915e
modprobe 7915e
--> same error
If I unplugg 12V and put it back in, the two radios work perfect again. if i click reboot it happens again.
--> driver only works once after poweroff reset
--> softreset leads to that error
Same thing on Openwrt 20.02.1 and current snap (28.01.22)
after reboot-->
Thu Jan 27 16:47:10 2022 user.info kernel: [ 13.779669] kmodloader: loading kernel modules from /etc/modules.d/*
Thu Jan 27 16:47:10 2022 kern.info kernel: [ 14.089957] Loading modules backported from Linux version v5.15.8-0-g43e577d7a2cb
Thu Jan 27 16:47:10 2022 kern.info kernel: [ 14.097482] Backport generated by backports.git v5.15.8-1-0-g83f664bb
Thu Jan 27 16:47:10 2022 kern.info kernel: [ 14.815303] mt7621-pci 1e140000.pcie: bus=2 slot=1 irq=24
Thu Jan 27 16:47:10 2022 kern.info kernel: [ 14.820778] pci 0000:00:01.0: enabling device (0000 -> 0003)
Thu Jan 27 16:47:10 2022 kern.info kernel: [ 14.826504] mt7915e 0000:02:00.0: enabling device (0000 -> 0002)
Thu Jan 27 16:47:10 2022 kern.err kernel: [ 35.183619] mt7915e 0000:02:00.0: Message 00000010 (seq 1) timeout
Thu Jan 27 16:47:10 2022 kern.err kernel: [ 35.189802] mt7915e 0000:02:00.0: Failed to get patch semaphore
Thu Jan 27 16:47:10 2022 kern.err kernel: [ 55.663612] mt7915e 0000:02:00.0: Message 00000010 (seq 2) timeout
Thu Jan 27 16:47:10 2022 kern.err kernel: [ 55.669786] mt7915e 0000:02:00.0: Failed to get patch semaphore
Thu Jan 27 16:47:10 2022 kern.warn kernel: [ 55.675942] mt7915e: probe of 0000:02:00.0 failed with error -11
Thu Jan 27 16:47:10 2022 kern.info kernel: [ 55.682031] mt7621-pci 1e140000.pcie: bus=3 slot=2 irq=25
Thu Jan 27 16:47:10 2022 kern.info kernel: [ 55.687480] pci 0000:00:02.0: enabling device (0000 -> 0003)
Thu Jan 27 16:47:10 2022 kern.info kernel: [ 55.693125] mt7915e 0000:03:00.0: enabling device (0000 -> 0002)
Thu Jan 27 16:47:10 2022 kern.err kernel: [ 76.143606] mt7915e 0000:03:00.0: Message 00000010 (seq 1) timeout
Thu Jan 27 16:47:10 2022 kern.err kernel: [ 76.149787] mt7915e 0000:03:00.0: Failed to get patch semaphore
Thu Jan 27 16:47:10 2022 kern.err kernel: [ 96.623585] mt7915e 0000:03:00.0: Message 00000010 (seq 2) timeout
Thu Jan 27 16:47:10 2022 kern.err kernel: [ 96.629743] mt7915e 0000:03:00.0: Failed to get patch semaphore
Thu Jan 27 16:47:10 2022 kern.warn kernel: [ 96.635884] mt7915e: probe of 0000:03:00.0 failed with error -11
Thu Jan 27 16:47:10 2022 kern.info kernel: [ 96.699024] PPP generic driver version 2.4.2
Thu Jan 27 16:47:10 2022 kern.info kernel: [ 96.705681] NET: Registered protocol family 24
Thu Jan 27 16:47:10 2022 user.info kernel: [ 96.718951] kmodloader: done loading kernel modules from /etc/modules.d/*
Clean poweroff boot-->
Thu Jan 27 16:45:50 2022 user.info kernel: [ 13.775271] kmodloader: loading kernel modules from /etc/modules.d/*
Thu Jan 27 16:45:50 2022 kern.info kernel: [ 14.062810] Loading modules backported from Linux version v5.15.8-0-g43e577d7a2cb
Thu Jan 27 16:45:50 2022 kern.info kernel: [ 14.070290] Backport generated by backports.git v5.15.8-1-0-g83f664bb
Thu Jan 27 16:45:50 2022 kern.info kernel: [ 14.783773] mt7621-pci 1e140000.pcie: bus=2 slot=1 irq=24
Thu Jan 27 16:45:50 2022 kern.info kernel: [ 14.789247] pci 0000:00:01.0: enabling device (0004 -> 0007)
Thu Jan 27 16:45:50 2022 kern.info kernel: [ 14.794979] mt7915e 0000:02:00.0: enabling device (0000 -> 0002)
Thu Jan 27 16:45:50 2022 kern.info kernel: [ 14.951811] mt7915e 0000:02:00.0: HW/SW Version: 0x8a108a10, Build Time: 20201105222230a
Thu Jan 27 16:45:50 2022 kern.info kernel: [ 14.951811]
Thu Jan 27 16:45:50 2022 kern.info kernel: [ 15.720032] mt7915e 0000:02:00.0: WM Firmware Version: ____000000, Build Time: 20201105222304
Thu Jan 27 16:45:50 2022 kern.info kernel: [ 15.893002] mt7915e 0000:02:00.0: WA Firmware Version: DEV_000000, Build Time: 20201105222323
Thu Jan 27 16:45:50 2022 kern.info kernel: [ 16.055388] mt7621-pci 1e140000.pcie: bus=3 slot=2 irq=25
Thu Jan 27 16:45:50 2022 kern.info kernel: [ 16.060909] pci 0000:00:02.0: enabling device (0004 -> 0007)
Thu Jan 27 16:45:50 2022 kern.info kernel: [ 16.066691] mt7915e 0000:03:00.0: enabling device (0000 -> 0002)
Thu Jan 27 16:45:50 2022 kern.info kernel: [ 16.093706] mt7915e 0000:03:00.0: HW/SW Version: 0x8a108a10, Build Time: 20201105222230a
Thu Jan 27 16:45:50 2022 kern.info kernel: [ 16.093706]
Thu Jan 27 16:45:50 2022 kern.info kernel: [ 16.122920] mt7915e 0000:03:00.0: WM Firmware Version: ____000000, Build Time: 20201105222304
Thu Jan 27 16:45:50 2022 kern.info kernel: [ 16.162588] mt7915e 0000:03:00.0: WA Firmware Version: DEV_000000, Build Time: 20201105222323
Thu Jan 27 16:45:50 2022 kern.info kernel: [ 16.382587] PPP generic driver version 2.4.2
Thu Jan 27 16:45:50 2022 kern.info kernel: [ 16.389072] NET: Registered protocol family 24
Thu Jan 27 16:45:50 2022 user.info kernel: [ 16.403858] kmodloader: done loading kernel modules from /etc/modules.d/*
The text was updated successfully, but these errors were encountered: