[LEDE-DEV] ar7 (TI AR7): update to kernel 4.4, please test
On 09/18/2016 04:18 PM, Hauke Mehrtens wrote: > I updated the ar7 target to kernel 4.4 in this branch: > https://git.lede-project.org/?p=lede/hauke/staging.git;a=shortlog;h=refs/heads/kernel-4.4 > > If you have any device supported by this target please test it and > report back if the ar7 target is still working with kernel 4.4 like > with the old kernel or if you see new problems. Please report back if it > worked and if it does not work. I only compile tested this because I do > not have this hardware. > > Having the target at kennel 4.4 is a requirement to get it into the next > release. I have tested this on a Netgear DG834Gv2. Unfortunately I never got a ping back from it and I don't have serial access. An otherwise identical configuration against 3.18.43 works. I did subsequently try to build 4.1 but the config kept screwing up and I don't have time to figure it out right now. Regards, -- James Le Cuirot (chewi) Gentoo Linux Developer pgpvSmUyjv4T_.pgp Description: OpenPGP digital signature ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] ar7 (TI AR7): update to kernel 4.4, please test
On 09/21/2016 07:16 AM, Mohammed Berdai wrote: > On 09/20/2016 10:47 PM, Hauke Mehrtens wrote: >> On 09/20/2016 10:57 PM, Mohammed Berdai wrote: >>> On 09/18/2016 04:18 PM, Hauke Mehrtens wrote: Hi, I updated the ar7 target to kernel 4.4 in this branch: https://git.lede-project.org/?p=lede/hauke/staging.git;a=shortlog;h=refs/heads/kernel-4.4 If you have any device supported by this target please test it and report back if the ar7 target is still working with kernel 4.4 like with the old kernel or if you see new problems. Please report back if it worked and if it does not work. I only compile tested this because I do not have this hardware. Having the target at kennel 4.4 is a requirement to get it into the next release. Hauke ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev >>> >>> Hi, >>> >>> I tested your git rep before kernel 4.4 commit and after it. >>> >>> I have Dlink DSL-624 and DSL-524. They have identical hardware. The former >>> has a Wifi card. >>> >>> I have already tested John's (blogic)) repo when he tried to port AR7 to >>> 4.4 and reported back. >>> >>> These are the results: >>> >>> before 4.4 commit (kernel 3.18.29): >>> * Ethernet ports work (ping works) >>> * via UART, boot msgs appear almost normal except two/three lines >>> * also via UART, greeting msg and results of commands appear scrambled >>> however, >>>late msgs from boot like random: nonblocking pool is initialized >>> still appear normal >>> >>> >>> after 4.4 commit: >>> * no response from pinging at 192.168.1.1. In some rare cases I get only >>> one response during early boot. >>> * large portion of boot msgs get omitted after 10 seconds >>> * no results are shown when issuing commands via UART. >>> >>> >>> These issues happened exactly the same as John's attempt to port 4.4 two >>> months ago >> Hi Mohammed, >> >> Thank you for the information. Have you every tried kernel 4.1 in LEDE? >> To know if kernel 4.1 also has these problems would help to narrow the >> problems down. >> >> Hauke >> > > Hi, > > No, I didn't try 4.1. > > I tried different serial speeds with different terminals > (minicom/picocom/putty/cutecom). For 3.18.29 entering Fail-safe lines appear > scrambled the remaining output lines appear normal. > > Dlink DSL-524 and DSL-624 both have only 16MB of ram. The UART on this platform has always acted funky, was the serial_kludge patch properly forward ported? -- Florian ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] ar7 (TI AR7): update to kernel 4.4, please test
On 09/20/2016 10:47 PM, Hauke Mehrtens wrote: > On 09/20/2016 10:57 PM, Mohammed Berdai wrote: >> On 09/18/2016 04:18 PM, Hauke Mehrtens wrote: >>> Hi, >>> >>> I updated the ar7 target to kernel 4.4 in this branch: >>> https://git.lede-project.org/?p=lede/hauke/staging.git;a=shortlog;h=refs/heads/kernel-4.4 >>> >>> If you have any device supported by this target please test it and >>> report back if the ar7 target is still working with kernel 4.4 like >>> with the old kernel or if you see new problems. Please report back if it >>> worked and if it does not work. I only compile tested this because I do >>> not have this hardware. >>> >>> Having the target at kennel 4.4 is a requirement to get it into the next >>> release. >>> >>> Hauke >>> >>> ___ >>> Lede-dev mailing list >>> Lede-dev@lists.infradead.org >>> http://lists.infradead.org/mailman/listinfo/lede-dev >>> >> >> Hi, >> >> I tested your git rep before kernel 4.4 commit and after it. >> >> I have Dlink DSL-624 and DSL-524. They have identical hardware. The former >> has a Wifi card. >> >> I have already tested John's (blogic)) repo when he tried to port AR7 to 4.4 >> and reported back. >> >> These are the results: >> >> before 4.4 commit (kernel 3.18.29): >> * Ethernet ports work (ping works) >> * via UART, boot msgs appear almost normal except two/three lines >> * also via UART, greeting msg and results of commands appear scrambled >> however, >>late msgs from boot like random: nonblocking pool is initialized still >> appear normal >> >> >> after 4.4 commit: >> * no response from pinging at 192.168.1.1. In some rare cases I get only >> one response during early boot. >> * large portion of boot msgs get omitted after 10 seconds >> * no results are shown when issuing commands via UART. >> >> >> These issues happened exactly the same as John's attempt to port 4.4 two >> months ago > Hi Mohammed, > > Thank you for the information. Have you every tried kernel 4.1 in LEDE? > To know if kernel 4.1 also has these problems would help to narrow the > problems down. > > Hauke > Hi, No, I didn't try 4.1. I tried different serial speeds with different terminals (minicom/picocom/putty/cutecom). For 3.18.29 entering Fail-safe lines appear scrambled the remaining output lines appear normal. Dlink DSL-524 and DSL-624 both have only 16MB of ram. Mohammed, ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] ar7 (TI AR7): update to kernel 4.4, please test
On 09/20/2016 10:57 PM, Mohammed Berdai wrote: > On 09/18/2016 04:18 PM, Hauke Mehrtens wrote: >> Hi, >> >> I updated the ar7 target to kernel 4.4 in this branch: >> https://git.lede-project.org/?p=lede/hauke/staging.git;a=shortlog;h=refs/heads/kernel-4.4 >> >> If you have any device supported by this target please test it and >> report back if the ar7 target is still working with kernel 4.4 like >> with the old kernel or if you see new problems. Please report back if it >> worked and if it does not work. I only compile tested this because I do >> not have this hardware. >> >> Having the target at kennel 4.4 is a requirement to get it into the next >> release. >> >> Hauke >> >> ___ >> Lede-dev mailing list >> Lede-dev@lists.infradead.org >> http://lists.infradead.org/mailman/listinfo/lede-dev >> > > Hi, > > I tested your git rep before kernel 4.4 commit and after it. > > I have Dlink DSL-624 and DSL-524. They have identical hardware. The former > has a Wifi card. > > I have already tested John's (blogic)) repo when he tried to port AR7 to 4.4 > and reported back. > > These are the results: > > before 4.4 commit (kernel 3.18.29): > * Ethernet ports work (ping works) > * via UART, boot msgs appear almost normal except two/three lines > * also via UART, greeting msg and results of commands appear scrambled > however, >late msgs from boot like random: nonblocking pool is initialized still > appear normal > > > after 4.4 commit: > * no response from pinging at 192.168.1.1. In some rare cases I get only one > response during early boot. > * large portion of boot msgs get omitted after 10 seconds > * no results are shown when issuing commands via UART. > > > These issues happened exactly the same as John's attempt to port 4.4 two > months ago Hi Mohammed, Thank you for the information. Have you every tried kernel 4.1 in LEDE? To know if kernel 4.1 also has these problems would help to narrow the problems down. Hauke ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] ar7 (TI AR7): update to kernel 4.4, please test
On 09/18/2016 04:18 PM, Hauke Mehrtens wrote: > Hi, > > I updated the ar7 target to kernel 4.4 in this branch: > https://git.lede-project.org/?p=lede/hauke/staging.git;a=shortlog;h=refs/heads/kernel-4.4 > > If you have any device supported by this target please test it and > report back if the ar7 target is still working with kernel 4.4 like > with the old kernel or if you see new problems. Please report back if it > worked and if it does not work. I only compile tested this because I do > not have this hardware. > > Having the target at kennel 4.4 is a requirement to get it into the next > release. > > Hauke > > ___ > Lede-dev mailing list > Lede-dev@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/lede-dev > Hi, I tested your git rep before kernel 4.4 commit and after it. I have Dlink DSL-624 and DSL-524. They have identical hardware. The former has a Wifi card. I have already tested John's (blogic)) repo when he tried to port AR7 to 4.4 and reported back. These are the results: before 4.4 commit (kernel 3.18.29): * Ethernet ports work (ping works) * via UART, boot msgs appear almost normal except two/three lines * also via UART, greeting msg and results of commands appear scrambled however, late msgs from boot like random: nonblocking pool is initialized still appear normal after 4.4 commit: * no response from pinging at 192.168.1.1. In some rare cases I get only one response during early boot. * large portion of boot msgs get omitted after 10 seconds * no results are shown when issuing commands via UART. These issues happened exactly the same as John's attempt to port 4.4 two months ago Mohammed, here are bootlogs: Before 4.4 ADAM2 Revision 0.22.02_b04_Mar 9 2005 (C) Copyright 1996-2003 Texas Instruments Inc. All Rights Reserved. (C) Copyright 2003 Telogy Networks, Inc. Usage: setmfreq [-d] [-s sys_freq, in MHz] [cpu_freq, in MHz] Memory optimization Complete! Adam2_AR7RD > Press any key to abort OS load, or wait 7 seconds for OS to boot... [0.00] Linux version 3.18.29 (rave@ravebox) (gcc version 5.4.0 (LEDE GCC 5.4.0 r1619) ) #0 Sat Sep 17 19:43:29 2016 [0.00] ar7-gpio: registered 32 GPIOs [0.00] bootconsole [early0] enabled [0.00] CPU0 revision is: 00018448 (MIPS 4KEc) [0.00] TI AR7 (TNETD7300), ID: 0x0005, Revision: 0x27 [0.00] Determined physical RAM map: [0.00] memory: 0100 @ 1400 (usable) [0.00] Initrd not found or empty - disabling initrd [0.00] Zone ranges: [0.00] Normal [mem 0x1400-0x14ff] [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x1400-0x14ff] [0.00] Initmem setup node 0 [mem 0x1400-0x14ff] [0.00] Primary instruction cache 16kB, VIPT, 4-way, linesize 16 bytes. [0.00] Primary data cache 16kB, 4-way, VIPT, no aliases, linesize 16 bytes [0.00] Built 1 zonelists in Zone order, mobility grouping off. Total pages: 4064 [0.00] Kernel command line: console=ttyS0,38400n8 rootfstype=squashfs,jffs2 [0.00] PID hash table entries: 64 (order: -4, 256 bytes) [0.00] Dentry cache hash table entries: 2048 (order: 1, 8192 bytes) [0.00] Inode-cache hash table entries: 1024 (order: 0, 4096 bytes) [0.00] Memory: 11244K/16384K available (2867K kernel code, 114K rwdata, 564K rodata, 156K init, 196K bss, 5140K reserved) [0.00] NR_IRQS:256 [0.00] Calibrating delay loop... 148.88 BogoMIPS (lpj=78) [0.08] pid_max: default: 32768 minimum: 301 [0.09] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) [0.10] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) [0.12] NET: Registered protocol family 16 [0.16] Switched to clocksource MIPS [0.17] NET: Registered protocol family 2 [0.19] TCP established hash table entries: 1024 (order: 0, 4096 bytes) [0.21] TCP bind hash table entries: 1024 (order: 0, 4096 bytes) [0.23] TCP: Hash tables configured (established 1024 bind 1024) [0.25] TCP: reno registered [0.26] UDP hash table entries: 256 (order: 0, 4096 bytes) [0.28] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) [0.30] NET: Registered protocol family 1 [0.38] futex hash table entries: 256 (order: -1, 3072 bytes) [0.43] squashfs: version 4.0 (2009/01/31) Phillip Lougher [0.44] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc. [0.48] msgmni has been set to 21 [0.50] io scheduler noop registered [0.51] io scheduler deadline registered (default) [0.52] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled [0.54] serial8250: ttyS0 at MMIO 0x8610e00 (irq = 15, base_baud = 3906250) is a TI-AR7 [
[LEDE-DEV] ar7 (TI AR7): update to kernel 4.4, please test
Hi, I updated the ar7 target to kernel 4.4 in this branch: https://git.lede-project.org/?p=lede/hauke/staging.git;a=shortlog;h=refs/heads/kernel-4.4 If you have any device supported by this target please test it and report back if the ar7 target is still working with kernel 4.4 like with the old kernel or if you see new problems. Please report back if it worked and if it does not work. I only compile tested this because I do not have this hardware. Having the target at kennel 4.4 is a requirement to get it into the next release. Hauke ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
