@bodhi many thanks for reply and advice. I see, i have no intention of rolling my u-boot bootloader.If it boots "new kernel" i won't touch it. I will flash u boot to a new NAND flash, solder it, test it and share my findings in here.by whitepawn - Debian
Hi all, In past i was a tester on debian for Netgear RN102 with @bodhi.Thanks to him. Now i need some advice/guidance for another device but this time it is not a Network Attached Storage. It is an old barcode reader/rugged pc from 2011-2012 era. My goal is to port an relatively updated kernel to it and boot linux.Since it is close enough SOC model to my RN102 i believe i can find suggestionsby whitepawn - Debian
@bodhi Long time no see, how are you? Nice to see some upgrade. I am using my RN120 as daily driver with your older kernel and openmediavault. Does this new kernel includes better network performance? @tme Did you made any iperf tests?by whitepawn - Debian
Hi bodhi again, Could we get 5.10.7 kernel if possible?If it will not increase network problem please don't bother. Regards.by whitepawn - Debian
Hi makczo, Are you trying to load stock firmware?If so which guide are you using?Is this one?by whitepawn - Debian
Bodhi, Here is summary results of between recent kernels: Kernel Version 5.8.5 tld-1 5.9.3 tld-3 5.9.3 tld-4 iperf 196 Mbits/sec 722 Mbits/sec 636 Mbits/sec Sysbench Memory 0.66ms 0.67ms 0.77ms Sysbench CPU 4.33ms 6.32ms 6.33ms /dev/zero Not tested 669 MB/s 1.3 GB/s /dev/urandom Not tested 29.2 MB/s 31.8 MB/s I posted RN102 post detailed reports.This iby whitepawn - Debian
bodhi, I have just tested your fresh tld-4 kernel for providing you more info.Here is my results.I have tested on same setup as before: Server side Xeon Desktop: jigsaw@whitepawnxeon:~$ iperf -s ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 128 KByte (default) ----------------------------------------------------------by whitepawn - Debian
Bodhi, Thanks for suggestions.I have tried below: QuoteBodhi - Your Xeon Desktop Linux set the flow control to disabled. I have disabled flow control both server and client side. QuoteBodhi - Your Mi 4A Gigabit router does not have any QoS (Quality of services) rules activated for the ports where the RN102 and the Xeon Dekstop connected to. To confirm this i have tried it with anotheby whitepawn - Debian
Hi Bodhi, I have tried with your tld3 version with fresh install on my RN102.Network speed is improved significantly thank you.Now i can get 669 Mbits/sec.But i cannot figured out why i am not getting 900Mbits/sec.Here is my logs: Client Side: jigsaw@whitepawnxeon:~$ ethtool -a enp2s0 Pause parameters for enp2s0: Autonegotiate: on RX: on TX: on jigsaw@whitepawnxeon:~$ ethtool enp2by whitepawn - Debian
Hi tme nice to see you again! I have tried factory reset as described.Didn't help but i have original backup for env partition i will try with nandwrite original envs partition. I have read all new kernel information and L2 cache thing, great work.Will try new kernel but it seems it have network issues as right now i believe. Regards.by whitepawn - Debian
Hi guys again, I was very busy with life, sorry didn't post anything useful. Today i quickly tried with another router and also direct connection with static ip.It didn't improve network speed. It seems many developments are made will read forum. BTW can i quickly return to stock firmware?Which envs i must use? Regards.by whitepawn - Debian
Bodhi and Tme, I will be away from box for 1 week.Thank you all for your tests and suggestions. I will try them and post results. Regards.by whitepawn - Debian
Bodhi, I gathered logs with dmesg: root@neutron:~# ethtool -a eth0 Pause parameters for eth0: Autonegotiate: on RX: off TX: off RX negotiated: off TX negotiated: off root@neutron:~# ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Fullby whitepawn - Debian
Bodhi, I have disabled both ethernet devices flow control on client(Linux Mint) and server(RN102).Still getting 200mbps on Netgear.I also unplugged and plugged ethernet cable after turning off flow control on both server and client sides. Turned off both client and RN102 flow controls, this is my client side log, same applied on Netgear but i forget to get log but outputs are the same:by whitepawn - Debian
Bodhi, I have tried some below: Sysbench memory and CPU test: root@neutron:~# sysbench --test=memory --memory-block-size=512K --memory-total-size=512M run sysbench 0.4.12: multi-threaded system evaluation benchmark Running the test with following options: Number of threads: 1 Doing memory operations speed test Memory block size: 512K Memory transfer size: 512M Memory opby whitepawn - Debian
@tme, Quotetme I have modified my eSATAp to SATA adapter cable so that 5 V power is provided from an external power supply. 3.3 V and 12 V pins are unconnected. In my case i soldered old SATA power connector 5v pins directly to front usb power lines.Since my HDD draws only 0.4 amps during load i think it will be fine.I also mounted disk inside case between CPU heatsink and box chasis I haby whitepawn - Debian
Bodhi I have tested with your envs it succeeded.Here is what i have done: BootROM 1.08 Booting from NAND flash General initialization - Version: 1.0.0 High speed PHY - Version: 2.1.4 (COM-PHY-V20) Update PEX Device ID 0x6710 High speed PHY - Ended Successfully 0001 DDR3 Training Sequence - Ver 5.7.1 DDR3 Training Sequence - Run without PBS. DDR3 Training Sequence - Ended Suby whitepawn - Debian
Bodhi, QuoteBodhi Was it with only the esATA port has this HDD attched to it? no other HDD in the slots? Yes only HDD attached to box is e-SATA disk.And USB flash disk to boot.Nothing else attached. QuoteBodhi Yes. The SATA drive has the partition with label rootfs. So the kernel sees that and ignore the USB rootfs. HDD always got detected and scanned first. Oh i see now. QuoteBodhi Ifby whitepawn - Debian
@bodhi and tme, I resoldered stock flash chip and tested it before doing below: Since i don't have any e-SATA cable in hand and i am impaitent guy i sacrificed one of my sata cable and soldered it directly to e-SATA daughter board and feeded my HDD with external power source.(I was wrong, e-SATA port doesn't have power pins btw i have checked it but not a big deal for me)It detected mby whitepawn - Debian
Tme, Yes it is no e-SATAp but neither standard 7 pin e-SATA.If you looked connector inside there are also some pins which i think power pins. If it not provides 5v supply i can make a voltage regulator with LM7805 no problem.Since RN102 draws 1 amp in idle with one usb and one 2.5 inch drive attached oem psu (5v 12A) will work i think. I have many HDD drives with USB 3.0 so i want to savby whitepawn - Debian
Bodhi, Out of luck with SDIO pins.Now i decided to boot debian from rear e-SATA port with e-SATA to 2.5 inch HDD cable like this. Is this possible to boot from e-SATA via changing bootenvs?If its possible which envs i must use? Regards.by whitepawn - Debian
Tme, Quotetme So the whole kwb-image was uploaded. It took 87 s. 'kwbimage' on 'u-boot.bin' said "Invalid image version 20". Important? I think it is not normal but i am not sure.I never get this error. It seems u-boot is not compatible with out box because i get exactly same behavior on seagate and synology bootloaders.It hangs on: @bodhi I see so iby whitepawn - Debian
Hi Trond I am back, Many thanks for building u-boot, i have tried your stock u-boot.kwb and i ddr patched your code both of them are loaded extremely slowly like synology or seagate bootloaders that i tried in past. In my case your u-boot.kwb loads slow (approx 35-40 mins), Loaded 100 percent unlike yours hangs at 22 percent but it cannot boot and hangs at "". I also ddr patched toby whitepawn - Debian
Trond, Quick post before i test: Maybe ddr code is not working?Could you please try this. Your stock u-boot image (mtd0) you will need and you may patch it with ddr code. I will try it and post results. Regards.by whitepawn - Debian
Bodhi, QuoteBodhi This is the reason I always want to see the complete serial console log! Right now samsung 4gb is soldered to box thats why i couldn't give full log for 8gb one.If it helps i can resolder 8gb one and get a full log no problem. Yes sir compiling u-boot is fine with both "LP_OPTIONS16" and "LP_OPTIONS". With 8gb flash and "LP_OPTIONS" aby whitepawn - Debian
Bodhi, QuoteBodhi Since you've edited your post, I did not notice there is new info in it (the new post indicator in red) (until now I happen to want to read it again). I didn't want to spam forum thats why i just edited post.In most forums i think it is forbidden, is it possible to post before someone replies in here? QuoteBodhi Not sure I can recall what you mean by "u-booby whitepawn - Debian
mantequilla, I was having same issue on my Netgear RN102.Please check /etc/rc.local maybe it is same for you: Quotebodhi > All leds are constantly on.Maybe some scripts or > drivers required. This should be controlled in /etc/rc.local. See the examples I have in this file. Regards.by whitepawn - Debian
Bodhi, I have tried with these: ./build_rn102-nand.pl -v 2.7 -d /home/jigsaw/u-boot-2011.12-armada370/armada-370-netgear-rn102.dtb -P 8192 -L 2048 -N MLC ./build_rn102-nand.pl -v 2.5 -d /home/jigsaw/u-boot-2011.12-armada370/armada-370-netgear-rn102.dtb -P 4096 -L 128 -N MLC ./build_rn102-nand.pl -v 2.4 -d /home/jigsaw/u-boot-2011.12-armada370/armada-370-netgear-rn102.dtb -N M But unby whitepawn - Debian
Bodhi, QuoteBodhi Remember the previous posts above? that "living dangerously" has come back and bitten you in the rear :) I laughed so hard, but you are right:)I am just having fun maybe i am a masochist:) But i must admit it is a big learning curve for me so thanks again. I have tried my original mtd0 backup with both, I think you suspected bit-flaps or something that broke crby whitepawn - Debian
Bodhi, Still no luck sir: Neutron login: root Password: Last login: Sat Sep 19 13:05:39 PDT 2020 on ttyS0 Linux Neutron 5.8.5-mvebu-370xp-tld-1 #1.0 SMP PREEMPT Mon Aug 31 00:00:32 PDT 2020 armv7l The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyrightby whitepawn - Debian