mt7615e 0000:01:00.0: Failed to get patch semaphore
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 888
- Forks
- 436
- PR merge metrics
- No merged PRs in 30d
Description
[ 11.170452] mt7615e 0000:01:00.0: card - bus=0x1, slot = 0x0 irq=4
[ 11.233668] urngd: jent-rng init failed, err: 2
[ 11.245011] mt7615e 0000:01:00.0: Invalid MAC address, using random address ea:47:3f:16:9e:fc
[ 11.267880] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 11.369304] PPP generic driver version 2.4.2
[ 11.381196] NET: Registered protocol family 24
[ 11.428316] rt2800_wmac 10180000.wmac: loaded eeprom from mtd device "factory"
[ 11.442790] ieee80211 phy1: rt2x00_set_rt: Info - RT chipset 6352, rev 0500 detected
[ 11.458240] ieee80211 phy1: rt2x00_set_rf: Info - RF chipset 7620 detected
[ 11.472699] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
[ 11.496105] kmodloader: done loading kernel modules from /etc/modules.d/*
[ 31.555841] mt7615e 0000:01:00.0: Message 16 (seq 1) timeout
[ 31.567145] mt7615e 0000:01:00.0: Failed to get patch semaphore
Why is the file mt7663pr2h.bin missing?
Who has the file mt7663pr2h.bin?
I use the latest commit ID 03daa60ca69c40bf3e87c70221da57465634440f
Thank you very much.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by investigating the mt7615e boot log and the referenced mt7663pr2h.bin firmware name at commit 03daa60ca69c40bf3e87c70221da57465634440f. Determine whether the firmware is expected to be present and what causes the patch semaphore failure; done means the missing-file question and resulting driver error are resolved or clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux
- Domain
- embedded-iot, networking, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100