@Shrieram,
Try changing the mode to Wifi Access Point.
1 Like
There are a bunch of people who P.M.'d last night and want to be testers. I will be responding to your requests tonight.
Thank you for volunteering.
David
1 Like
shm0
2454
@ParanoidZoid
The commit you linked about the config change.
By default all namespaces are toggled on now?
Cause the network namespace throws an expection on my system.
procd-ujail doesn't rely on the network (and user) namespace anyway.
I assume those can be safely disabled?
Seems to work fine, i can see that dnsmasq is in ujail now.
And the 4.19 bump in master works fine so far expect that patch
407-sfp-display-SFP-module-information.patch
fails to apply.
How does that exception manifest? I have been running with namespaces enabled for a couple of years on wrtpac devices (including network) and have not seen any issues.
1 Like
@shm0
I would say this is due to the hardware limitation of the wrt series; none have sfp ports.
thoughts?
1 Like
shm0
2457
I will post the log that contains the information about the exception in a few minutes.
//edit
here it is:
Mon Jun 17 16:56:31 2019 kern.warn kernel: [ 21.843169] ------------[ cut here ]------------
Mon Jun 17 16:56:31 2019 kern.warn kernel: [ 21.847856] WARNING: CPU: 0 PID: 482 at net/netfilter/core.c:398 0xc05f5c64
Mon Jun 17 16:56:32 2019 kern.warn kernel: [ 21.854878] Modules linked in: pppoe ppp_async pppox ppp_generic nf_conntrack_netlink iptable_nat ipt_REJECT ipt_MASQUERADE xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_helper xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_connbytes xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_HL xt_DSCP xt_CT xt_CLASSIFY slhc nfnetlink nf_reject_ipv4 nf_nat_ipv4 nf_log_ipv4 nf_conntrack_rtcache nf_conncount iptable_raw iptable_mangle iptable_filter ipt_ECN ip_tables crc_ccitt act_connmark sch_tbf sch_ingress sch_hfsc em_u32 cls_u32 cls_tcindex cls_route cls_matchall cls_fw cls_flow cls_basic act_skbedit act_mirred mwlwifi mac80211 cfg80211 compat cryptodev ip6table_nat ip6t_NPT ip6t_MASQUERADE nf_nat_ipv6 nf_nat nf_conntrack nf_defrag_ipv6
Mon Jun 17 16:56:32 2019 kern.warn kernel: [ 21.926916] nf_defrag_ipv4 ip6t_rt ip6t_mh ip6t_ipv6header ip6t_hbh ip6t_frag ip6t_eui64 ip6t_ah nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 ifb authenc gpio_button_hotplug
Mon Jun 17 16:56:32 2019 kern.warn kernel: [ 21.947925] CPU: 0 PID: 482 Comm: kworker/u4:3 Not tainted 4.19.50 #0
Mon Jun 17 16:56:32 2019 kern.warn kernel: [ 21.954399] Hardware name: Marvell Armada 380/385 (Device Tree)
Mon Jun 17 16:56:32 2019 kern.warn kernel: [ 21.960351] Workqueue: netns 0xc059ba1c
Mon Jun 17 16:56:32 2019 kern.warn kernel: [ 21.964211] Function entered at [<c010f450>] from [<c010b134>]
Mon Jun 17 16:56:32 2019 kern.warn kernel: [ 21.970073] Function entered at [<c010b134>] from [<c06c100c>]
Mon Jun 17 16:56:32 2019 kern.warn kernel: [ 21.975936] Function entered at [<c06c100c>] from [<c012762c>]
Mon Jun 17 16:56:32 2019 kern.warn kernel: [ 21.981798] Function entered at [<c012762c>] from [<c0127760>]
Mon Jun 17 16:56:32 2019 kern.warn kernel: [ 21.987660] Function entered at [<c0127760>] from [<c05f5c64>]
Mon Jun 17 16:56:32 2019 kern.warn kernel: [ 21.993522] Function entered at [<c05f5c64>] from [<c05f5dcc>]
Mon Jun 17 16:56:32 2019 kern.warn kernel: [ 21.999384] Function entered at [<c05f5dcc>] from [<c059af90>]
Mon Jun 17 16:56:32 2019 kern.warn kernel: [ 22.005246] Function entered at [<c059af90>] from [<c059bbc0>]
Mon Jun 17 16:56:32 2019 kern.warn kernel: [ 22.011108] Function entered at [<c059bbc0>] from [<c013ee28>]
Mon Jun 17 16:56:32 2019 kern.warn kernel: [ 22.016970] Function entered at [<c013ee28>] from [<c013f2cc>]
Mon Jun 17 16:56:32 2019 kern.warn kernel: [ 22.022832] Function entered at [<c013f2cc>] from [<c0144cdc>]
Mon Jun 17 16:56:32 2019 kern.warn kernel: [ 22.028694] Function entered at [<c0144cdc>] from [<c01010e8>]
Mon Jun 17 16:56:32 2019 kern.warn kernel: [ 22.034556] Exception stack(0xdec8bfb0 to 0xdec8bff8)
Mon Jun 17 16:56:32 2019 kern.warn kernel: [ 22.039634] bfa0: 00000000 00000000 00000000 00000000
Mon Jun 17 16:56:32 2019 kern.warn kernel: [ 22.047854] bfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Mon Jun 17 16:56:32 2019 kern.warn kernel: [ 22.056074] bfe0: 00000000 00000000 00000000 00000000 00000013 00000000
Mon Jun 17 16:56:32 2019 kern.warn kernel: [ 22.062847] ---[ end trace c6aa12c803781f21 ]---
About the sfp patch.
Can someone else confirm that the patch fails to apply?
Turris Omnia has an sfp slot.
I just finished a new build here and that patch applies fine.
Yes, and also the clearfog devices have sfp.
Edit: the only thing that stands out to me is I do not have any of ppp stuff running.
shm0
2459
Damn.
While merging the changes into my branch, something screwed and the result was a the same patch twice in my patch directory. I also did a git diff --name-only between the branches...
I apologize x)
But for the network namespace exception, i don't know.
1 Like
Shouldn't the same patch twice have caused quilt to quit and the build process to stop?
And yes, all the namespaces are activated on !SMALL_FLASH devices. UTS, IPC, USER_NS, PID_NS, and NET_NS.
And yeah, I guess ujail doesn't rely on all of them (only UTS, IPC, & PID). The others are probably there for LXC support.
I also am not sure about the ppp stuff. I don't run it myself. However, just searching up "ppp reboots" shows that some users have experienced problems ever since the switch from 2.4.7 (in 18.06) to git commits (in 19.07 & Master).
EDIT: What processes were running above the "cut here" line? My bootup process only lasts around 15 seconds, with wlan0 enabling itself at 80 seconds due to DFS.
phinn
2461
Now that the kernel 4.19 commit as gone in for mvebu today, anyone know what features/benefits we can expect? Don't think there is anything specific just curious.
For one, there are a lot of mvneta fixes and improvements (and in particular with <256MB RAM). Even though mvebu still runs swconfig, changes in mvneta still somewhat affect the switch.
1 Like
I'm still needing more volunteers especially with the 1900ac Version 1/V1. Currently I have zero (0) folks signed up to try the new kernel for the V1.
I'm looking for 1900ac V1 owners.
Just message me and let me know you are interested, and I'll send you the link to the downloads.
Thanks,
David
1 Like
You looking for WRT32X users bud?
Yes Sir... The more the merrier. I'll put you on the list.
I should have something ready to test tonight.
1 Like
Ok thanks, trying to compile a test version myself but hitting the same old brick wall lol.
Whats the overall change on the kernel? is it supporting everthing better then 4.14 with the move to 4.19?
From what @ParanoidZoid stated below, mvneta fixes. Other than that I don't have a lot of info on it.
1 Like
Thanks for the reply. Now all i have to figure out is why on earth the compiler is erroring out on a clean install.
/home/openwrt/trunk/scripts/ipkg-build -c -o 0 -g 0 /home/openwrt/trunk/build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/fftw3-long-double/fftw-3.3.8/ipkg-arm_cortex-a9_vfpv3/fftw3l /home/openwrt/trunk/bin/packages/arm_cortex-a9_vfpv3/packages
Packaged contents of /home/openwrt/trunk/build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/fftw3-long-double/fftw-3.3.8/ipkg-arm_cortex-a9_vfpv3/fftw3l into /home/openwrt/trunk/bin/packages/arm_cortex-a9_vfpv3/packages/fftw3l_3.3.8-1_arm_cortex-a9_vfpv3.ipk
rm -rf /home/openwrt/trunk/build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/fftw3-long-double/fftw-3.3.8/.pkgdir/fftw3l.installed /home/openwrt/trunk/build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/fftw3-long-double/fftw-3.3.8/.pkgdir/fftw3l
mkdir -p /home/openwrt/trunk/build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/fftw3-long-double/fftw-3.3.8/.pkgdir/fftw3l
install -d -m0755 /home/openwrt/trunk/build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/fftw3-long-double/fftw-3.3.8/.pkgdir/fftw3l/usr/lib
cp -fpR /home/openwrt/trunk/build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/fftw3-long-double/fftw-3.3.8/ipkg-install/usr/lib/libfftw3l.so* /home/openwrt/trunk/build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/fftw3-long-double/fftw-3.3.8/.pkgdir/fftw3l/usr/lib/
touch /home/openwrt/trunk/build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/fftw3-long-double/fftw-3.3.8/.pkgdir/fftw3l.installed
mkdir -p /home/openwrt/trunk/staging_dir/target-arm_cortex-a9+vfpv3_musl_eabi/root-mvebu/stamp
SHELL= flock /home/openwrt/trunk/tmp/.root-copy.flock -c 'cp -fpR /home/openwrt/trunk/build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/fftw3-long-double/fftw-3.3.8/.pkgdir/fftw3l/. /home/openwrt/trunk/staging_dir/target-arm_cortex-a9+vfpv3_musl_eabi/root-mvebu/'
touch /home/openwrt/trunk/staging_dir/target-arm_cortex-a9+vfpv3_musl_eabi/root-mvebu/stamp/.fftw3l_installed
make[3]: Leaving directory '/home/openwrt/trunk/feeds/packages/libs/fftw3'
time: package/feeds/packages/fftw3/long-double/compile#89.19#16.33#115.47
make[2]: Leaving directory '/home/openwrt/trunk'
make[1]: *** [package/Makefile:103: /home/openwrt/trunk/staging_dir/target-arm_cortex-a9+vfpv3_musl_eabi/stamp/.package_compile] Error 2
make[1]: Leaving directory '/home/openwrt/trunk'
make: *** [/home/openwrt/trunk/include/toplevel.mk:218: world] Error 2
At least its keeping my brain in check. lol
All this so i can find whythe themes are doing what they are doing so it can be fixed.
After pulling down the the sources did you run the following commands?
./scripts/feeds update -a
./scripts/feeds install -a
Then copy over your .config
make menuconfig
do your changes, if any, then save to exit out
Then run
make download -j16 << Or whatever number of processors you have.
After it completes downloading packages run.
IGNORE_ERRORS=25 make -j16
There are going to be packages that fail, so I always put in the option IGNORE_ERRORS. It will still fail if there are major errors besides just packages, so don't worry that ignoring errors will just compile no matter what 
because it won't.
Right will DM you how i do it, as i have done scripting all way thorugh.
1 Like
I recommend starting small and working your way up to the point where this can be scripted.
