im understand reason of your sad and think we can change this situation for EDGE line
we will start porting krescue for edge - very very soon
and will inform about progress
Thanks @hyphop. Do you have the edge? If not I’m going to buy one for you so maybe next idea you have will start with the edge
bit tnx ! i have enough EDGE boards
Hi,
I have a problem with ethernet on VIM3 Pro with Krescue and other images on kernels 5.x – link down
But with debian 9.11 eth0 is UP.
With kernel 4.x.x seems to working ok like below :
Coreelec 9.2.2 OK
Linux CoreELEC 4.9.113 #1 SMP PREEMPT Mon Apr 13 20:13:06 BST 2020 aarch64 GNU/Linux
[ 0.564225@2] meson6-dwmac ff3f0000.ethernet: no reset control found
[ 0.564229@2] stmmac - user ID: 0x11, Synopsys ID: 0x37
[ 0.567210@4] libphy: stmmac: probed
[ 0.567215@4] eth%d: PHY ID 001cc916 at 0 IRQ POLL (stmmac-0:00) active
[ 0.567218@4] eth%d: PHY ID 001cc916 at 1 IRQ POLL (stmmac-0:01)
[ 0.683354@4] efusekeyname: mac offset: 0 size: 6
[ 13.461554@0] meson6-dwmac ff3f0000.ethernet eth0: fail to init PTP.
[ 14.474768@0] meson6-dwmac ff3f0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
Ubuntu 18.04.4 LTS OK
Linux Khadas 4.9.206 #13 SMP PREEMPT Tue Dec 31 00:37:47 CST 2019 aarch64 aarch64 aarch64 GNU/Linux
[ 25.422105] meson6-dwmac ff3f0000.ethernet eth0: fail to init PTP.
[ 28.501201] meson6-dwmac ff3f0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
debian 9.11 OK
Linux Khadas 5.5.0-rc2 #0.8.3 SMP PREEMPT Sun Jan 19 14:10:00 +09 2020 aarch64 GNU/Linux
[ 5.262364] meson8b-dwmac ff3f0000.ethernet eth0: PHY [0.0:00] driver [RTL8211F Gigabit Ethernet]
[ 5.396752] meson8b-dwmac ff3f0000.ethernet: Failed to reset the dma
[ 5.400517] meson8b-dwmac ff3f0000.ethernet eth0: stmmac_hw_setup: DMA engine initialization failed
[ 5.412752] meson8b-dwmac ff3f0000.ethernet eth0: stmmac_open: Hw setup failed
[ 6.028058] meson8b-dwmac ff3f0000.ethernet eth0: PHY [0.0:00] driver [RTL8211F Gigabit Ethernet]
[ 6.044681] meson8b-dwmac ff3f0000.ethernet eth0: No Safety Features support found
[ 6.047920] meson8b-dwmac ff3f0000.ethernet eth0: PTP not supported by HW
[ 6.054680] meson8b-dwmac ff3f0000.ethernet eth0: configuring for phy/rgmii link mode
[ 8.913389] meson8b-dwmac ff3f0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[ 6.054680] meson8b-dwmac ff3f0000.ethernet eth0: configuring for phy/rgmii link mode
[ 8.913389] meson8b-dwmac ff3f0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
Could you give me some advice ?
Please add ethtool to krescue if it’s possible
Regards
YES ! i know about this problem and still try to solve it
ABOUT PROBLEM: legacy kernel NO problem its only mainline linux kernel problem for VIM3 + VIM3L (if mainline kernel start after legacy without poweroff )
SOLUTION: poweroff ( unplug power cable and plug again ) ethernet must works again
Maybe then not enough
I have found no need to unplug / replug power lead. Poweroff and on again with remote works for me most times
It will be better if / when a simple reset is enough.
yes its have same effect !
It will be better if / when a simple reset is enough.
sure but this bug still not fixed in mainline Linux kernel
Hmm. Stopped working.
Every bootup from the SD containing Krescue now has NOT enabled the eth0 connection so no communication with the device!
try overwriting the latest Krescue on sd specifically for your vim
Yes, after re-writing the SD card several times and re-flashing the Android rom it seems to have started working again (maybe it got a little hot? )
I do not think that this is the reason
it looks like a malfunction sd
Yeah, possibly . . .
i will make tomorrow special separate thread about EDGE Krescue progress
hello
finally we think of edge and edge v. it also has a lot of possibilities, other than vim, but it’s a khadas, so it’s good material
[image]
Why is remote.conf ignored in the VIM3 Android setup? Is it not used at all, or just not in the usual /system/etc folder?
Hi, I think the android is clearly not this branch
krescue provide just android image and make warranty only for correct installation (we can get same android system via aml-burn-tool without any diff ==> all problem with android ask in android thread ! )
Oh! So it’s probably a change in the later versions of Android then?
Oh! So it’s probably a change in the later versions of Android then?
sure last build was
...code/khadas-rescue-tools/projects/Android_Pie$ grep VER= make.conf.VIM*
make.conf.VIM1:VER=V200317
make.conf.VIM3:VER=V200319
make.conf.VIM3L:VER=V200320
i dont have any other new sources
PS: when new version will be ready i can update krescue images