lanefu changed the topic of #armbian-rockchip to: Armbian - Linux for ARM development boards | Rockchip SoC | www.armbian.com | This channel is relayed to the equivalent Discord channel | this channel is logged
<DC-IRC> <amazingfate> @krachlatte take a look at this two commits on legacy kernel. Maybe something is similar on mainline driver.
<DC-IRC> <krachlatte> i will have a look
<DC-IRC> <krachlatte> it looks like this patch mprove HS400ES compatibility for some eMMC is there but not the queue support in 6.3 kernel
<DC-IRC> <krachlatte> it looks like this patch mprove HS400ES compatibility for some eMMC is there but not the queue support in 6.3 kernel, so you would recommend to remove this ?
<DC-IRC> <amazingfate> A user revert this two commits and then he can boot from emmc on rock5b.
<DC-IRC> <krachlatte> i am tring to lrun from sd card, eemc is working with vendor uboot and vendor kernelfrom emmc
<DC-IRC> <krachlatte> i booted this image Armbian_23.02.0-trunk_Radxa-e25_jammy_legacy_4.19.193.img and did e emmc install
<DC-IRC> <krachlatte> [ 3.394110] mmc1: tuning execution failed: -5
<DC-IRC> <krachlatte> [ 3.394516] mmc1: error -5 whilst initialising SD card
<DC-IRC> <krachlatte> its the SD card not the EMMC
<DC-IRC> <krachlatte> 25
<DC-IRC> <krachlatte> it boots
<DC-IRC> <krachlatte> it was with the SD carad on the e25 expansion board
<DC-IRC> <krachlatte> sd-uhs-sdr104; and sd-uhs-sdr50 are the major differenzes
<DC-IRC> <krachlatte> changed from 104 to 50 that is the problem
<DC-IRC> <krachlatte> so i need someone to help me getting this patch into the build system
RecursiveG has quit [Quit: ZNC 1.8.2 - https://znc.in]
RecursiveG has joined #armbian-rockchip
<DC-IRC> <krachlatte> pull is there
<DC-IRC> <IgorPec> so this is the only missing problem to get this booting?
<DC-IRC> <krachlatte> yes
<DC-IRC> <krachlatte> i just created a pull request
<DC-IRC> <IgorPec> ok
<DC-IRC> <IgorPec> legacy kernel images works?
<DC-IRC> <krachlatte> not tested i tested only edge
<DC-IRC> <IgorPec> aha, ok. this would be nice to determine by the end of the month
<DC-IRC> <IgorPec> i don't have this hw around
<DC-IRC> <krachlatte> i can run legacy compile and check if it still boots
<DC-IRC> <IgorPec> ok, thank you
<DC-IRC> <krachlatte> but legacy is 5.10, i do not think so, i will chek if same patch is needed
<DC-IRC> <IgorPec> 5.10 stock from rockchip
<DC-IRC> <IgorPec> imo it should work, but as we have our own tree we might not have everything that radxa has . for this board
<DC-IRC> <krachlatte> i never had a working 5.10 for e25
<DC-IRC> <krachlatte> sorry
<DC-IRC> <IgorPec> aha, ok
<DC-IRC> <krachlatte> but i did not have this patch or found this fix 🙂
<DC-IRC> <krachlatte> so lets see
<DC-IRC> <IgorPec> yeah, otherwise is better to disable legacy until its not working well
<DC-IRC> <krachlatte> yep
<DC-IRC> <krachlatte> it looks like it has the same problem
<DC-IRC> <krachlatte> -> 2/9: board-add-radxa-rock3-makefile(:1) (+3/-0)[1M] {Makefile}
<DC-IRC> <krachlatte> [🐳|🔨] Problem with ->board-add-radxa-rock3-makefile(:1) (+3/-0)[1M] {Makefile}<-: Failed to apply patch /armbian/patch/kernel/archive/rk35xx-5.10/board-add-radxa-rock3-makefile.patch:
<DC-IRC> <krachlatte> there is a problem with this patch too
<DC-IRC> <IgorPec> if you can determine the reason ... i can check little later
<DC-IRC> <krachlatte> its not adding the boards rock3 and e25 to the makefile, fixed that and also the sdr50 thing
<DC-IRC> <krachlatte> build is running lets see
<DC-IRC> <amazingfate> This patch has to get fixed because there have been many boards merged into the legacy kernel.
<DC-IRC> <amazingfate> I haven't build rk35xx legacy for a long time. Maybe we can merge it with rockchip-rk3588.
<DC-IRC> <krachlatte> were can i find the option to revert back to eth0 interface naming ?
<DC-IRC> <krachlatte> enp1s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
<DC-IRC> <c0rnelius> add `net.ifnames=0` to the boot command line for. i don't own the E25 but there is someone I know who is running the tests and the problem we currently have is the second eth interface doesn't come up. this is the patching we are currently using, including the bit to make the SD function more properly: https://raw.githubusercontent.com/pyavitz/debian-image-builder/feature/patches/rockchip/rk356x/6.3/003-arm64-dts-rockchip-rk3568-ra
<DC-IRC> <c0rnelius> add `net.ifnames=0` to the boot command line for eth0, wlan0, etc. i don't own the E25 but there is someone I know who is running the tests and the problem we currently have is the second eth interface doesn't come up. this is the patching we are currently using, including the bit to make the SD function more properly: https://raw.githubusercontent.com/pyavitz/debian-image-builder/feature/patches/rockchip/rk356x/6.3/003-arm64-dts-r
<DC-IRC> <c0rnelius> Line 51 in the patch where I changed `gpios` to `gpio` was a suggestion from the BSD fellas, but it didn't help. As a kernel dev said a week or so ago both should work regardless so that's a dead end.
<DC-IRC> <krachlatte> updatesd my pull request also for the legacy kernel boots also fine best regards
<DC-IRC> <krachlatte> i have 2 interfaces showing up eth0 and eth1
<DC-IRC> <c0rnelius> @krachlatte what u-boot are you using?
<DC-IRC> <krachlatte> vendor u-boot
<DC-IRC> <c0rnelius> mainline linux or vendor?
<DC-IRC> <krachlatte> mainline
<DC-IRC> <c0rnelius> hmm. must be the u-boot then. i'm using mainline.
<DC-IRC> <c0rnelius> thanx
<DC-IRC> <Tenkawa> @c0rnelius that E25 is a yet weird mystery.... seems that every unit we've worked on acts differently
<DC-IRC> <Tenkawa> Then again I wonder how differently the 3568's in general behave
<DC-IRC> <c0rnelius> I don't have it, so I'm at the point of not caring. Be one thing if I can just debug it myself, but I don't feel like sitting there making guesses to get it working any further. I was thinking it was something missing in the u-boot preventing the interface from coming up... But yeah, its just a guess. Both the NanoPi R5S/C both come up fine, so that's a bit odd.
<DC-IRC> <Tenkawa> unfortunately my Odroid only has one gigE port so I cant recreate the network
<DC-IRC> <Tenkawa> Yeah... I hear ya..
<DC-IRC> <c0rnelius> Or that guys unit is buggy? It is Radxa so that is possible. No offense to them.
<DC-IRC> <krachlatte> i used the legacy image and isntalled it to the internal emmc
<DC-IRC> <krachlatte> works good
<DC-IRC> <krachlatte> all containers up and running from the old image on the internal memory
<DC-IRC> <c0rnelius> @krachlatte do you have the two u-boot bins handy? loader and itb?
<DC-IRC> <krachlatte> Were should i upload them to?
<DC-IRC> <c0rnelius> you archive them and pm or drop them where ever. its up to you.
<DC-IRC> <c0rnelius> you can archive them and pm or drop them where ever. its up to you.
<DC-IRC> <krachlatte> i will try a current compliation as well lets see
<DC-IRC> <krachlatte> current is not working