**** BEGIN LOGGING AT Sat Jan 12 02:59:57 2019 Jan 12 05:30:25 Does OpenWRT support multiple versions of a package allowing the user to select the version from within menuconfig? Jan 12 05:48:34 directly, no Jan 12 07:11:44 dansan: ... but you can, of course, customize the package metadata to build the version of your choice Jan 12 09:54:37 Hi Jan 12 09:54:54 Who can i ask about lantiq cway kernels? Jan 12 09:54:59 xway Jan 12 10:19:33 https://forum.openwrt.org/t/2nd-lan-port-lan2-on-avm-7330-7320-does-not-work/28895/8 Jan 12 10:20:01 The 2 people in the forum think that i'm too stupid to configure openwrt but that's not the problem. Jan 12 10:20:24 the missing interface does not even appear to exist to the Operating System Jan 12 10:31:11 rubberduck: the OpenWrt Ethernet driver only supports one of the ports on the ARX100 ("AR9") SoC Jan 12 10:31:37 is there a chance to support the second one? Jan 12 10:32:38 i have another question about this hardware: can i use Tagged-VLAN on this one Port? Jan 12 10:32:48 in theory yes - it comes down to whether someone has time and motivation to do it Jan 12 10:34:02 i did document the second lan port not working already on the toh site. i hope this is ok for you? i cannot test if ADSL is working as i have a VDSL100/40 at home and the 7330 only supports ADSL2+ Jan 12 10:35:11 imho it's fine to have it documented in the toh just to make others aware of that fact if they're planning to use that device Jan 12 10:36:59 other question to the same hardware: there is only one usb port working. is there a chance to get the second one on the side online? Jan 12 10:39:16 https://sky.webnmail.de/privatebin/?6c03a10ea1e3a638#RvYAzbCUUc1qJR/hpePBOytmowSdzIwJS7UFPcMOsqQ= Jan 12 10:39:25 only one port is recognized at boot Jan 12 10:39:36 https://github.com/openwrt/openwrt/blob/master/target/linux/lantiq/files-4.14/arch/mips/boot/dts/FRITZ7320.dts#L158 Jan 12 10:39:52 the .dts file only enables one USB controller and PHY, but not the second Jan 12 10:43:24 for reference: 7360SL enables both USB port: https://github.com/openwrt/openwrt/blob/master/target/linux/lantiq/files-4.14/arch/mips/boot/dts/FRITZ7360SL.dts#L226 (I'm aware that it's using a different SoC, but the USB implementation on ARX100 and VRX200 is similar enough) Jan 12 10:45:46 there is a eth section for the 7360 but none for the 7320? Jan 12 10:46:05 or is ethernet the &gsw section at line 101? Jan 12 10:46:21 yes, GSW is the Ethernet controller Jan 12 10:47:10 so maybe a patch at this section can activate lan2? or is the driver not capable of doing multiple phy? Jan 12 10:47:20 (please note: VRX200 uses a different Ethernet controller than ARX100, different drivers are also used for both SoCs) Jan 12 10:48:02 yes, it's the ARX100 Ethernet controller driver which is missing the bits for the second port Jan 12 10:48:30 so only adding the second port to the .dts won't help Jan 12 10:48:41 so i can hope on a fix? Jan 12 10:52:12 There is no hurry at my side - the 7330 was 'very expensive' for me: €9,- Jan 12 10:52:30 maybe i can deal with the only one lan port when VLAN is working. Jan 12 10:54:37 so that this device will be a very exotic Wireless LAN Accesspoint. Jan 12 10:57:43 I'm not sure if anyone will work on adding support for the second Ethernet port given how long this SoC is out and support is still missing Jan 12 10:57:51 but never say never, so... ;) Jan 12 11:02:00 maybe there is a chance if i send my 7330 to you via DHL? Jan 12 11:26:31 xdarklight: i compared the flash-layout in the 7360 dts file with the information from https://boxmatrix.info/wiki/FRITZ!Box_Fon_WLAN_7360_v1 Jan 12 11:26:35 this matches Jan 12 11:26:46 but for the https://boxmatrix.info/wiki/FRITZ!Box_Fon_WLAN_7360_v2 not Jan 12 11:27:15 is it possible to add a new dts file with the updated flash layout? i would buy a 7360v2 for testing then. Jan 12 12:25:10 rubberduck: re sending me a 7330: my main problem is "time". I have various other pieces of hardware lying on my desk, so adding another one to the stack would just mean that it's collecting dust :/ Jan 12 12:28:41 rubberduck: re 7360 v2 flash layout: adding support for a different flash layout should be simple (assuming the only changed the flash but kept everything else). see for example support for the 3370 in OpenWrt, which also comes in two variants (with different flash chips) Jan 12 12:29:19 (the 3370 uses NAND flash instead of NOR flash on the 7360, but you get the idea) Jan 12 13:21:56 xdarklight: what can i do to get the second flash layout into git? i don't like to learn git just for this... Jan 12 13:26:38 i found a possible problem in the 7360sl dts: the line 9 tells lantiq, xway but in the download-section it is in lantiq/xrx200 Jan 12 13:27:38 xdarklight: here the patched file: https://sky.webnmail.de/privatebin/?dfc05726719eed0b#xPnh31PWkKPXVz78/3gWXUmfHHcqaftT/vsq1ig47Q8= Jan 12 13:49:50 i bought a 3370 now - schould arrive next week - i'll come back if i have questions Jan 12 14:03:19 greearb_: i'm here fyi Jan 12 14:09:06 movi I'm here for a bit as well Jan 12 14:09:26 damn, i thought a packet dump meant a dump from the driver itself :/ Jan 12 14:09:29 you happen to go by a different nic in github bug reports? Jan 12 14:09:32 yes Jan 12 14:09:33 ahh Jan 12 14:09:36 can never be too paranoid Jan 12 14:10:16 anyway this complicates things, as i have a second c2600, but currently it's the main router of the house and it's running stock ath10k which i'm willing to bet doesn't have a monitor mode? Jan 12 14:10:24 you can sniff from local as well, but you miss a lot of traffic and may capture something that isn't really on the air Jan 12 14:10:54 yeah, stock can capture...it misses a few frames, but that should not matter for this case. Jan 12 14:11:12 ah great. i'm betting it needs to be exclusive? Jan 12 14:11:21 ? Jan 12 14:11:31 as in it can't run an ap at the same time? Jan 12 14:11:52 it could probably work, I'm not sure. ct FW can do it at least Jan 12 14:12:25 you would want to use tcpdump with a filter to only show your ps4 traffic though otherwise you will fill up disk/ram way too fast Jan 12 14:12:27 meh, alright i'll give it a shot in the evening Jan 12 14:12:31 nod Jan 12 14:12:51 how much of data should i be expecting? Jan 12 14:14:43 probably not much since your device cannot communicate Jan 12 17:54:15 hm Jan 12 17:54:22 * check_data_file_clashes: Package bridge wants to install file /home/jwh/erpoe/build_dir/target-mips64_octeon_64_musl/root-octeon/usr/sbin/brctl Jan 12 17:54:30 But that file is already provided by package * busybox Jan 12 17:54:38 but its unchecked, soooo Jan 12 18:37:36 The upgarde image is corrupt. Jan 12 18:37:37 rude Jan 12 18:38:44 gg Jan 12 19:53:10 <\x> how good is mt7615 on openwrt now? Jan 12 19:57:20 not yet supported Jan 12 20:00:45 hm, is there any provision for target specific kmods, or should I just guard it with depends? Jan 12 20:04:30 <\x> DonkeyHotei: will it work if i use those "mtk-openwrt-feeds" ? Jan 12 20:04:47 <\x> i mean this Jan 12 20:04:48 <\x> https://github.com/Nossiac/mtk-openwrt-feeds Jan 12 20:04:50 <\x> ?? Jan 12 20:05:33 ask the author? Jan 12 20:05:49 or check the readme Jan 12 20:05:51 <\x> oh okay Jan 12 20:05:54 <\x> sorry. Jan 12 20:07:39 jwh: there are target-specific kmods Jan 12 20:07:50 several targets have them Jan 12 20:08:14 oh hm Jan 12 20:08:43 target/linux/*/modules.mk Jan 12 20:09:06 <\x> still nice updates for 7612e on current snapshots tho Jan 12 20:09:08 <\x> really good Jan 12 20:09:24 ah thats what I was looking for, I was checking includes though :D Jan 12 20:13:54 getting closer to what I want... just need to figure out the defconfig stuff and see if I can override some envs per-target Jan 12 20:23:05 jwh: note that this is just the standard location for putting them there, you still need to have those depends, else they'll show up for everyone Jan 12 20:23:22 oh Jan 12 20:23:49 well thats ok, it's really jut to keep target specific stuff together Jan 12 20:24:47 so I'm not touch other parts of the tree for just a single kmod on one device Jan 12 21:37:37 hrm, just updated my mt7621 to latest, 2.4gig seems much improved right out of the box Jan 12 21:39:32 mt76 has seen a lot of love lately Jan 12 21:44:11 yeah, it was reading some of that commentary here that reminded to updated Jan 12 21:44:37 previosully was august 2018 timeframe or so Jan 12 21:44:49 will know more when the wife comes home :) Jan 12 21:49:37 so close! Jan 12 21:50:06 need to figure out why vendor Jan 12 21:50:18 modules don't probe and create interfaces Jan 12 21:50:28 maybe I'm using the wrong board type Jan 12 21:51:24 * jwh refers to notes Jan 12 23:21:20 <\x> based mt76 Jan 12 23:21:33 <\x> cheap and abundant. Jan 12 23:21:46 <\x> whats the best mt7621 device out there tho? Jan 12 23:24:44 hm Jan 12 23:25:25 ok so what about setting config symbols (for kernel) based on device, that is... common symbols for the target, but then more specific ones for device/subtarget? Jan 12 23:30:53 \x: don't know about best, but I've got a ZBT-WE1326 that I've been happy with, it's cheap and available Jan 12 23:37:39 <\x> i have the youhua Jan 12 23:37:42 <\x> wr1200js Jan 12 23:38:38 <\x> tho im kinda regretting that i bought this Jan 12 23:38:40 <\x> i mean Jan 12 23:38:57 <\x> newifi d3 is about the same price Jan 12 23:38:58 <\x> https://www.ebay.com/itm/reeeeeeeee/371944168049 Jan 12 23:39:32 <\x> larger spi flash, and 512MB ram. Jan 12 23:55:46 yeah, I actuallly tried to buy the youhua, but couldn't find it from any vendor I trusted Jan 12 23:56:04 that newwifi d3 I'd never even seen before Jan 12 23:56:08 when did it come out? Jan 12 23:57:00 thhe we1326 has 512meg ram Jan 13 00:54:14 hm am I missing something with modules.mk... it's showing up as a symbol but not enabled, do I specify a default state for it? Jan 13 00:55:55 better add it to device packages Jan 13 00:56:57 what Jan 13 00:57:26 as in the device profile? Jan 13 00:57:26 hm Jan 13 00:57:34 yess Jan 13 00:58:03 its target wide, guess I could add it to DEFAULT_PACKAGES there instead? Jan 13 00:58:20 DEVICE_PACKAGES+=+kmod-something Jan 13 00:58:37 yeah Jan 13 00:58:39 hm Jan 13 00:58:49 guess that will do, as long as I don't forget Jan 13 01:01:16 ain't having that Jan 13 01:03:58 ah, its just broken if switching from another target Jan 13 01:04:20 fine if I dump target in and do defconfig Jan 13 01:04:44 does that with a whole bunch of stuff, potential for broken builds heh **** ENDING LOGGING AT Sun Jan 13 02:59:57 2019