What have you now modified exactly? Was it that additional line which was missing existing in mainline but not in official? You’ve said reset patch does not help…
i created the official package, but it really can’t solve the problem. I checked mtk-sd.c and the device tree, and they were also modified, but to no avail. Then I changed the mtk-sd.sd and device tree of the main line in your way and it succeeded…
Reset patches are already in 5.4.64…so using mainline should work too…i only need to know if the additional line removal makes any difference
I tested 5.4.66 and there was no problem. The previous problem was 5.4.63. I guess it should be the same.
Ok then you had tested before without reset patches…wonder why you had problem with my tree because i had patches in 5.4-main earlier…
I have deleted it, and now only your patch and mainline branch are left. Because of problems, I will conduct multiple branch tests, including your source code, official and the patch you mentioned.
As only my repo does support the most hardware (official and mainline 5.4 does not support dsa,bluetooth,thermal,pwm,…),you should go with it.
Well, thank you very much, I will do i2s audio development next, why don’t you submit it to the mainline!
most already sent, but some of them not merged or merged after 5.4
dsa-driver was already sent to mainline and goes in 5.10, bluetooth depends on some patches that already sent (btif termios, v5 does not work, have contacted sean, but no response). mt7622 wifi is merged till 5.8 i guess
i have send many patches for r2, but need to do some work with r2 internal wifi and some of my stuff (currently try to upgrade my router to buster). and my time is also limited…
Okay, thanks, do you have an instant chat tool? whatsapp or fm!
I do,but not whatsapp. And if anyone send me messages i can do less. Just use the forum…so question need to be answered once (in theory)
okay , thank you!! 
Hi! I have the same problem with eMMC in Proxmox kernel 5.4.65-1-pve. Proxmox is based on debian. Can I hope that problem will be fixed when proxmox switches to kernel 5.4.66? Or there is no chance and the only way to fix the problem is to compile kernel myself (which scares me =) ? Thank you =)
Which exact problem do you have (please provide logs)? Mmc issue should be fixed in 5.4.65. Maybe your uuid in fstab is wrong? Or does proxmox use mtd like openwrt…afaik this is not yet fixed
Here is logs:
[ 405.582848] blk_update_request: I/O error, dev mmcblk0, sector 12860400 op 0x1:(WRITE) flags 0x20800 phys_seg 1 prio class 0
[ 405.594078] Aborting journal on device mmcblk0p1-8.
lk_update_request: I/O error, dev mmcblk0, sector 12855320 op 0x1:(WRITE) flags 0x20800 phys_seg 1 prio class 0mat M-P Prepend ^T To Files
[ 406.355774] Buffer I/O error on dev mmcblk0p1, logical block 1606659, lost sync page write
[ 406.364137] JBD2: Error -5 detected when updating journal superblock for mmcblk0p1-8.
[ 406.364346] blk_update_request: I/O error, dev mmcblk0, sector 2048 op 0x1:(WRITE) flags 0x20800 phys_seg 1 prio class 0
[ 406.382877] Buffer I/O error on dev mmcblk0p1, logical block 0, lost sync page write
[ 406.390673] EXT4-fs (mmcblk0p1): I/O error while writing superblock
[ 406.390936] EXT4-fs (mmcblk0p1): previous I/O error to superblock detected
[ 406.396967] EXT4-fs error (device mmcblk0p1): ext4_journal_check_start:61: Detected aborted journal
[ 406.396971] EXT4-fs (mmcblk0p1): Remounting filesystem read-only
I checked mmcblk0 for bad blocks: “badblocks -v /dev/mmcblk0” and found that drive is ok.
basicly the emmc-patches are merged with v5.4.64
a69047c01eb4 mmc: dt-bindings: Add resets/reset-names for Mediatek MMC bindings
5876ee035ba6 mmc: mediatek: add optional module reset property
2816ccd07145 arm64: dts: mt7622: add reset node for mmc device
git log --oneline --ancestry-path --merges a69047c01eb4..5.4-main | tail -1
6685f3c3ce28 Merge tag 'v5.4.64' into 5.4-mainSo it is something wrong with my mmcblk0, and I need deeper testing…
Do you have kernelsource of proxmox kernel? Then you can look if the changes are there…maybe proxmox have own dot-releases
Or you can try booting my kernel (binary is on github releases)
Seems like this is kernel sources:
there is no kernel-source only a hint in readme that ubuntu kernel is used…maybe it is fetched by makefile. please try kernel from my github to make sure it also happens there