Looks like the HNAT is working, otherwise the performance is not closed to 930Mbits/sec. HWNAT is for hardware acceleration, so I think pppoe connection will work fine too.
i compiled kernel 4.9.92 from 4.9-main it works good hw nat too.
cat /proc/interrupts
root@bpi-r2:~# cat /proc/interrupts
CPU0 CPU1 CPU2 CPU3
16: 3478 4880 2556 8292 GIC-0 29 Level arch_timer
17: 0 0 0 0 GIC-0 30 Level arch_timer
20: 0 0 0 0 MT_SYSIRQ 112 Level mtk_timer
169: 0 0 0 0 mt-eint 146 Edge 11240000.mmc cd
173: 0 0 0 0 mt-eint 150 Level mt6397-pmic
192: 0 0 0 0 MT_SYSIRQ 88 Edge mtk-wdt
193: 0 0 0 0 MT_SYSIRQ 115 Level mt-pmic-pwrap
194: 0 0 0 0 MT_SYSIRQ 87 Level mtk_cir
195: 670 0 0 0 MT_SYSIRQ 53 Level serial
196: 0 0 0 0 MT_SYSIRQ 44 Level i2c-mt65xx
198: 0 0 0 0 MT_SYSIRQ 78 Level 1100a000.spi
200: 540 0 0 0 MT_SYSIRQ 71 Level mtk btif tx dma irq
201: 561 0 0 0 MT_SYSIRQ 72 Level mtk btif rx dma irq
202: 0 0 0 0 MT_SYSIRQ 50 Level mtk btif irq
204: 13306 0 0 0 MT_SYSIRQ 40 Level 11240000.mmc
205: 333 0 0 0 MT_SYSIRQ 39 Level 11230000.mmc
206: 0 0 0 0 MT_SYSIRQ 185 Level BTIF_WAKEUP_IRQ
208: 59 0 0 0 MT_SYSIRQ 184 Level AHB_SLAVE_HIF
212: 0 257 0 0 MT_SYSIRQ 199 Level 1b100000.ethernet
213: 289 0 0 0 MT_SYSIRQ 198 Level 1b100000.ethernet
214: 0 0 0 0 MT_SYSIRQ 82 Level mtk-aes
215: 0 0 0 0 MT_SYSIRQ 83 Level mtk-aes
216: 0 0 0 0 MT_SYSIRQ 84 Level mtk-sha
217: 0 0 0 0 MT_SYSIRQ 91 Level mtk-sha
219: 0 0 0 0 MT_SYSIRQ 194 Level PCIe PME, ahci[0000:01:00.0]
IPI0: 0 1 1 1 CPU wakeup interrupts
IPI1: 0 0 0 0 Timer broadcast interrupts
IPI2: 2212 3322 2459 10835 Rescheduling interrupts
IPI3: 7 11 7 11 Function call interrupts
IPI4: 0 0 0 0 CPU stop interrupts
IPI5: 1 0 0 0 IRQ work interrupts
IPI6: 0 0 0 0 completion interrupts
Err: 0
1 Like
have uploaded a 4.14.53 with 2nd gmac and poweroff working (also hdmi and internal wifi) to my gdrive:
https://drive.google.com/open?id=1EGN1TvqCpDHdOAS-mjRg9ipi0kahnOUV
hnat for 4.14 is in hnat-branch…
@mifvi can you test it? in my tests, init seems to work well, but i see interrupts for ethernet on cpu0/1
@garywang how to check for working hnat? i see interrupts but how much are ok? how to check hnat-debugfs-table?
1 Like
help please Im not sure if this was set in the last build but is there a switch or way to turn off the evbug ?
I’m getting this build now to check out.
After looking at the code for the evbug I see there is no options that can be passed to the builtin module.
Frank on your next build could you please set it to M rather then Y so that it is built as a loadable module.
Which option do you mean? And what is the problem with it?
You mean this?
Yes, I pulled your latest build 4.14.53-Main
- CONFIG_INPUT_EVBUG=y
It is loaded as a builtin module and the evbug.c doesn’t seem to have any options for setting a debug level. My console has all input device outputting events
Maybe I’m missing something but I don’t know how else to turn off the events in the console. I thought if the this was built as module it could still be used for diagnosis if loaded as a module.
Just to give you a little background. I picked up this BPI-R2 to create a NAS. I’ve been trying to catch up with all that is being done so a little patience with me as I catch up.
I have a 4 bay Probox with eSATA. I found nothing mentioning that the onboard SATA ports supported port multiplayer so I picked up a PCIe card that does. I did find that the onboard only supports SATA II. The PCIe card supports SATAIII and port multiplier.
Just for info for all the PCIe slot with the SATAIII card is functioning great. It took me a bit to figure out that the 4th bay in the Probox was faulty and now I have a new enclosure on order. Have to see how that goes.
Still testing the software RAID. I’m not sure that it should be built into the kernel as a builtin module as I’m having some ‘mdadm: unexpected failure opening /dev/md0’ and all that I read up on assumes the module is the loadable version. But that is a different topic and I will try to stay on thread.
Again I can’t thank you and all who have done so much for this board. I’m finding it very cool.
For evbug you can try this:
#disable kernel-messages
echo 4 > /proc/sys/kernel/printk
#disable printing messages to console
dmesg -D
For mdadm…maybe something is missing. I have not tried raid yet.but let we discuss this in your md-thread
Thank you! That was driving me crazy. That is exactly it. Odd if I issue 7 it doesn’t turn back on unless I use 8. A least what I found on the dmesg log level is only 1-7.
I have uploaded new 4.14.53-main with raid-options and event-debug as module
frank-w I can do this not earlier than 18.07. How will I write the result.
hi all, yesterday i’ve uploaded new versions of LTS (4.4,4.9,4.14) to my gdrive
https://drive.google.com/open?id=17MoFc3vIuGHDEV5SsCmGegJDr009IXls
frank-w esterday I tested your precompiled kernel 4.14.55 : wi-fi is working. there are two interfaces eth0 and eth1 with different mac addresses. The monitor connected through the xdmi-vga adapter works with full HD resolution. Other resolution I not tried.
the problem is with usb keyboard, pressing each key causes the output to display:
` [ 503.349823] evbug: Event. Dev: input7, Type: 4, Code: 4, Value: 458792`
`[ 503.363941] evbug: Event. Dev: input7, Type: 1, Code: 28, Value: 1`
`[ 503.377628] evbug: Event. Dev: input7, Type: 0, Code: 0, Value: 0`
`[ 503.525803] evbug: Event. Dev: input7, Type: 4, Code: 4, Value: 458792`
accordingly, it is impossible to work with usb keyboard
poweroff command works correctly, but pressing the power button causes only the following information to be displayed:
`[ 3725.425806] evbug: Event. Dev: input6, Type: 1, Code: 116, Value: 1`
`[ 3725.439576] evbug: Event. Dev: input6, Type: 0, Code: 0, Value: 0`
`[ 3725.594139] evbug: Event. Dev: input6, Type: 1, Code: 116, Value: 0`
`[ 3725.607859] evbug: Event. Dev: input6, Type: 0, Code: 0, Value: 0`in 4.14.53 i made this commit: https://github.com/frank-w/BPI-R2-4.14/commit/5c4dadae829ab29e8714d1069739b29f4226e4f0#diff-0c5a11b88d355c91234ec8abda6a7e38
As you use a newer version,try unloading evbug-module. If this is not enough you can try blacklist it
I blacklist evbug-module, now keyboard work correctly.
But pressing the power button does not cause a shutdown now. In the future it would be convenient to turn off the power by button
On my pi this is/was working which image do you use? Have you blacklisted pmic-module?
I use bpi-r2 4.14.55-bpi-r2-main kernel from https://drive.google.com/open?id=17MoFc3vIuGHDEV5SsCmGegJDr009IXls
and pmic-module is not blacklisted and there is no such module in the output lsmod
Then try to load it:
modprobe mtk_pmic_keysmodule mtk_pmic_keys is loaded, but power key not work
I have a board version 1.2 can it be important?
I don’t know…i have only v1.1…will check it again…
Which image do you use?