Hi,
I tested this patch on my WRT1200AC and it seems to work fine, with
one exception. For some reason, the WAN (eth0) always has L2 state
DOWN (confirmed by ip link), even though WAN is connected and working
fine (verified with USB dongle). Any tips on how to proceed to fix
this?
As a side not,
Hi,
On Fri, Sep 11, 2015 at 3:10 PM, Kristian Evensen
wrote:
> Hi,
>
> I tested this patch on my WRT1200AC and it seems to work fine, with
> one exception.
Turns out there was a second exception. The USB1 port (eSATA) does not
work either
Hi,
On Fri, Sep 11, 2015 at 3:31 PM, Daniel Golle wrote:
> I assume you did make sure that these two flaws are actually
> regressions, i.e. both worked on 3.18, right?
Yes, everything worked fine on 3.18. I am compiling a new image now
and will send dmesg output when that is done. Thanks for the
From: Kristian Evensen
After commit ebd3d8417c7a ("interface: fix moving interface address routes to
the table specified by ip[46]table"), it is no longer possible for clients on
LAN to reach machines on the WAN.
This patch restores support for clients on LAN reaching clients on WA
From: Kristian Evensen
Commit d0f5ab6d95a1 ("ramips: Added support for ZBT-826 / ZBT-1026")
incorrectly changed the mode of the ramips shell scripts from 755 to 644.
I.e., they are not excutable any more and for example devices will be left
with broken configs.
Signed-off-by: Kristi
From: Kristian Evensen
The WG3526 is the follow-up to the 2626 and is mostly the same, with the
excaption that the mt7602 has been replaced with the mt7603. The internal wifi
setup has also changed slightly. Based on my tests, everything that worked on
the 2626 works on the 3526 and with roughly
From: Kristian Evensen
The WG3526 is the follow-up to the 2626 and is mostly the same, with the
excaption that the mt7602 has been replaced with the mt7603. The internal wifi
setup has also changed slightly. Based on my tests, everything that worked on
the 2626 works on the 3526 and with roughly
Hi,
On Thu, Mar 31, 2016 at 12:47 AM, Daniel Engberg
wrote:
> Currently the maximum image size defaults to 8Mbyte even though this model
> has 16Mbyte of flash memory.
Something has gone wrong when merging this patch (look at the Makefile
in the upstream commit), causing building mt7621 to brea
From: Kristian Evensen
The WG3526 is the follow-up to the 2626 and is mostly the same, with the
excaption that the mt7602 has been replaced with the mt7603. The internal wifi
setup has also changed slightly. Based on my tests, everything that worked on
the 2626 works on the 3526 and with roughly
From: Kristian Evensen
Comparing valid_until will always return false as the value is updated for each
route update message. This causes IPv6 routes to jump more around than House of
Pain, which might have undesirable consequences for user-space and user-space
applications.
Removing the
Hi,
On Wed, Sep 9, 2015 at 3:45 PM, Hans Dedecker wrote:
> Specific IP address and network rules are now checked before the main table
> lookup as the main table
> often holds a default route. As a result the IP address and network rules
> pointing to s specific
> routing table will not be chec
Sorry about partial reply, clumsy fingers.
On Wed, Sep 23, 2015 at 11:31 AM, Hans Dedecker wrote:
> Can you share the uci network config and ifstatus of the different
> interfaces ?
UCI config is nothing more than ... proto dhcp ... ip4/ip6table X
>>
>>
>> I don't see any other fix than a parti
Hi,
On Wed, Sep 9, 2015 at 3:45 PM, Hans Dedecker wrote:
> Remove ip loop policy rules as workaround for the kernel using unspecified
> address
> to lookup locally originating traffic is fixed by
> http://lkml.iu.edu/hypermail/linux/kernel/1505.0/03094.html
>
> Signed-off-by: Hans Dedecker
Th
On Wed, Sep 23, 2015 at 1:07 PM, Hans Dedecker wrote:
> Indeed we're using source based routing in combination with a default route
> in the main routing table; even the specific routing table(s) can contain a
> default route
> Based on the addr rule the traffic is guided to a specific routing tab
On Wed, Sep 23, 2015 at 1:23 PM, Kristian Evensen
wrote:
> On Wed, Sep 23, 2015 at 1:07 PM, Hans Dedecker wrote:
>> Indeed we're using source based routing in combination with a default route
>> in the main routing table; even the specific routing table(s) can contain a
>&
Hello,
I tried to compile and test trunk on two Linksys-routers (1200AC and
1900ACv2). After manually enabling the Generic Thermal sysfs driver,
compilation went fine. However, none of the routers want to boot.
Hooking up a serial shows what seems to be a filsystem issue, the
following error is re
From: Kristian Evensen
interface_ip_set_enabled() is usually called two times right after one another,
once to handle config_ip and once to handle proto_ip. As long as
ip->iface->l3_dev.dev is set, the local/source policy rules are updated.
This value is in several cases set on both con
instance_stop(), as well as when a process that should not be restarted
has exited in instance_exit().
Signed-off-by: Kristian Evensen
---
service/instance.c | 23 +++
1 file changed, 15 insertions(+), 8 deletions(-)
diff --git a/service/instance.c b/service/instance.c
index a5742b7
Hi,
On Fri, Mar 15, 2019 at 1:29 PM Petr Štetiar wrote:
>
> While testing simple firmware image for x86/64 in QEMU I've discovered
> some weird behavior today. This image contains simple package with
> simple init script to bootstrap the device UCI configuration from
> network server. This init s
can check which SIM
slot is currently used by reading from the file mentioned in the first
sentence.
- Turn on the modem again by running the following command:
echo 1 > /sys/class/gpio/power_mpcie/value
Signed-off-by: Kristian Evensen
---
.../ramips/base-files/etc/board.d/01_leds
Hi,
On Thu, Mar 21, 2019 at 2:23 PM Bjørn Mork wrote:
>
> Kristian Evensen writes:
>
> > - 2x SIM card slots (full size)
>
> Really? Am I the only one who remember credit card sized SIMs? :-)
>
> They were the only kind we had when GSM was introduced around he
Hi Hans,
On Thu, Apr 4, 2019 at 10:59 PM Hans Dedecker wrote:
> instance_delete should only be called when halt is set to true similar
> as in instance_exit
Thanks for the feedback. Just so I make sure I understand correctly,
do you mean that the conditional should look something like this?
57
instance_stop(), as well as when a process that should not be restarted
has exited in instance_exit().
v1->v2:
- Only call instance_delete() in instance_stop() if halt is true (thanks
Hans Dedecker).
Signed-off-by: Kristian Evensen
---
service/instance.c | 24
1 file changed,
(write 0/1 to /sys/class/gpio/power_mpcie/value).
- RS485 is available on /dev/ttyS0.
- RS232 is available on /dev/ttyS1.
- The name of the ioX-gpios map to the labels on the casing.
Signed-off-by: Kristian Evensen
---
.../ramips/base-files/etc/board.d/01_leds | 3 +
.../ramips/base-files
Hi Rafał,
On Thu, May 2, 2019 at 9:31 AM Rafał Miłecki wrote:
> Please include SPDX line with .dts file license, see:
> https://openwrt.org/submitting-patches#dts_checklist
Thanks for your feedback. Will update and submit a V2 later today.
BR,
Kristian
_
(write 0/1 to /sys/class/gpio/power_mpcie/value).
- RS485 is available on /dev/ttyS0.
- RS232 is available on /dev/ttyS1.
- The name of the ioX-gpios map to the labels on the casing.
v1->v2:
* Add SPDX line to DTS (thanks Rafał Miłecki).
Signed-off-by: Kristian Evensen
---
.../ramips/base-fi
lists were missing, so I have
added the functions uci_add_list() and uci_del_list() to simplify
working with uci lists from scripts.
Signed-off-by; Kristian Evensen
---
package/system/uci/files/lib/config/uci.sh | 20 +++-
1 file changed, 19 insertions(+), 1 deletion(-)
diff
Hi Petr,
Thanks a lot for your feedback. I have implemented most of it and the
board seems to work fine, but I have some questions.
On Fri, May 3, 2019 at 6:32 PM Petr Štetiar wrote:
> > In order to install OpenWRT, you first need to compile an initramfs
> > (ramdisk)-image for the device.
>
> i
Hello again,
On Sat, May 4, 2019 at 12:07 PM Kristian Evensen
wrote:
> Also, I am having some issues getting a ramdisk image to be built by
> default. After adding ramdisk to FEATURES, I still need to manually
> choose to build a ramdisk image. I have spent some time looking into
> t
Hi,
On Sun, May 5, 2019 at 12:53 PM Tom Psyborg wrote:
> > - 1x 5GHz wifi (mt7621)
>
> mt7621 is not wifi chip, you should update the description or just
> leave mt76 if you intention is to specify supporting driver.
Thanks for spotting this typo. I know very well that mt7621 is not a
wifi chip,
Hi Petr,
On Sun, May 5, 2019 at 10:14 PM Petr Štetiar wrote:
> I find it quite weird to demand any kind of compilation by the end-users, but
> I also find it quite wasteful to build initramfs images for all devices under
> particular target (lantiq/xrx200 and ramips/mt7620), just because one (or
Hi Petr,
On Sun, May 5, 2019 at 10:26 PM Petr Štetiar wrote:
> Unfortunately no, but I've just proposed[1] some temporary workaround, so
> let's see how this pans out. Until it's accepted, I would simply go with that
> proposed `FEATURES += ramdisk` based solution.
>
> 1. http://lists.infradead.o
either use AT-commands (AT+CFUN) or power-cycle the
modem (write 0/1 to /sys/class/gpio/power_mpcie/value).
- RS485 is available on /dev/ttyS0.
- RS232 is available on /dev/ttyS1.
- The name of the ioX-gpios map to the labels on the casing.
Signed-off-by: Kristian Evensen
---
v2->v3:
* Build initra
Hi Petr,
Thanks for your feedback.
On Wed, May 15, 2019 at 12:17 PM Petr Štetiar wrote:
> > In order to install OpenWRT, you first need to compile an initramfs
> > (ramdisk)-image for the device.
>
> This is no longer valid, right?
Correct, will remove it for v4.
>
> > --- a/target/linux/ramip
On Wed, May 15, 2019 at 12:42 PM Petr Štetiar wrote:
> Yes, you're correct, I've missed this userspace GPIOs.
Thanks for confirming. I will submit a v4 during the afternoon.
BR,
Kristian
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
h
/power_mpcie/value).
- RS485 is available on /dev/ttyS0.
- RS232 is available on /dev/ttyS1.
- The name of the ioX-gpios map to the labels on the casing.
Signed-off-by: Kristian Evensen
---
v3->v4:
* Update commit. I had forgot to remove instructions to compile a
ramdisk. This now d
lists were missing, so I have
added the functions uci_add_list() and uci_remove_list() to simplify
working with uci lists from scripts.
Signed-off-by; Kristian Evensen
---
v1->v2:
* Rename uci_del_list() to uci_remove_list() in order to be consistent
with uci_remove() (thanks Petr Štet
Hi,
On Wed, May 15, 2019 at 9:21 PM Petr Štetiar wrote:
> Thanks, I've merged it into my staging tree[1], but I had to fix one merge
> conflict in target.mk so please check it if I did it properly.
Thanks and strange about the conflict + whitespace, as patch applies
cleanly to master and checkpa
.
How to swap SIMs:
You control which SIM slot to use by writing 0/1 to
/sys/class/gpio/gpio13/value. In order for the change to take effect,
you can either use AT-commands (AT+CFUN) or power-cycle the modem (write
0/1 to /sys/class/gpio/gpio14/value).
Signed-off-by: Kristian Evensen
---
v1->
Hi,
On Thu, May 16, 2019 at 3:17 PM Petr Štetiar wrote:
> it's not mandatory, so you're not obliged to do so, but it makes me wonder if
> it would be possible to generate factory image which could be flashed with the
> same recovery mechanism, thus avoiding the -F in the sysupgrade above
> (consi
writing 0/1 to
/sys/class/gpio/gpio13/value. In order for the change to take effect,
you can either use AT-commands (AT+CFUN) or power-cycle the modem (write
0/1 to /sys/class/gpio/gpio14/value).
Signed-off-by: Kristian Evensen
---
v2->v3:
* Remove the old description of the first t
.
Notes:
* RS232 is available on /dev/ttyUSB0 and RS485 on /dev/ttyUSB1
Signed-off-by: Kristian Evensen
---
.../ath79/base-files/etc/board.d/01_leds | 3 +
.../ath79/base-files/etc/board.d/02_network | 1 +
.../base-files/etc/board.d/03_gpio_switches | 6 +
.../ath79/dts/ar9344_zbtlink_zb
Hi Petr,
Thanks for your comments.
On Fri, May 31, 2019 at 9:57 AM Petr Štetiar wrote:
> > +zbtlink,zbt-wd323)
> > + ucidef_set_led_wlan "wlan" "WLAN" "$boardname:green:wifi" "phy0tpt"
> > + ;;
> > esac
>
> Please add this trigger to the DTS.
Will do.
> > +#include "ar9344.dtsi"
> > +
.
Notes:
* RS232 is available on /dev/ttyUSB0 and RS485 on /dev/ttyUSB1
Signed-off-by: Kristian Evensen
---
v1->v2:
* Added WLAN trigger to DTS (thanks Petr Štetiar).
* Fixed typo in compatible string (ar9334->ar9344, thanks Petr Štetiar).
* Removed a reundant alias (thanks Petr Štetiar).
* Changed
Hi Christian,
On Wed, Jun 5, 2019 at 10:23 PM Christian Lamparter wrote:
> @Kristian Evensen, can you please check if the following patch would also
> resolve the issues you have been experiencing?
>
> I had to attach the patch as a file since gmail's webmail interface now seem
01_leds has several redundant LED-cases. This commit cleans
up the file by merging these cases into shared cases.
Signed-off-by: Kristian Evensen
---
.../ramips/base-files/etc/board.d/01_leds | 100 ++
1 file changed, 32 insertions(+), 68 deletions(-)
diff --git a/target
Hi,
On Sun, Jun 9, 2019 at 10:06 AM Christian Lamparter wrote:
> @ynezz, @Kristian
>
> The APM821xx checks out with both as well. While there are spurious
> events on enabling the interrupt (one released event),
> the /etc/rc.button/ scripts are setup to handle that. So, which patch
> should we t
the WE1026-H. The
second patch adds support for the WE1026-H.
Signed-off-by: Kristian Evensen
Kristian Evensen (2):
ramips: Update ZBT WE1026 DTS-files
ramips: Add support for ZBT WE1026-H
.../ramips/base-files/etc/board.d/01_leds | 5 +
.../ramips/base-files/etc/board.d/02_network
"flash"-name for the spi-nor node.
All changes have been tested on the WE1026-5G-16M and work fine. I.e.,
the device works as before the DTS-changes.
Signed-off-by: Kristian Evensen
---
target/linux/ramips/dts/WE1026-5G-16M.dts | 77 ++---
target/linux/ramips/dts/WE10
his
device. However, the files are structured so that adding support for the
16MB version should be easy.
* Only the LAN port is accessible from the outside of the casing and LEDs
are not visible.
Signed-off-by: Kristian Evensen
---
.../ramips/base-files/etc/board.d/01_leds | 5 +++
.../ramips/
Hi,
On Wed, Jul 3, 2019 at 9:55 AM Rafał Miłecki wrote:
> Why you didn't cc Alex, so he can ack your relicensing? You also
> didn't care to let us know we need his ack!
While I don't appreciate your tone, I see now that I made a mistake.
When checking the history of the files that I relicense, t
ound.
* Fix building support for nftables sets. In 4.18 the configuration
symbol changed from CONFIG_NFT_SET_RBTREE and CONFIG_NFT_SET_HAS, to
CONFIG_NF_TABLES_SET.
Signed-off-by: Kristian Evensen
---
include/netfilter.mk | 17 ++-
package/network/utils/nftables
set in run_state so
that the elements are updated as the user expects.
Since we now always copy the value of reload_set from cfg_state, there
is no need to write reload_set to run_state.
Signed-off-by: Kristian Evensen
---
ipsets.c | 47 +--
ipsets.h
Hi,
On Fri, Aug 23, 2019 at 1:40 PM Birger Koblitz wrote:
>
> ramips: use gpio_hog instead of gpio-export
>
> The `gpio-export` functionality is a hack for
> missing kernel functionality, which was rejected in upstream kernel long
> time
> ago, for details see this email
> http://lists.infradead.
required patching the
mdio-driver, and the code added comes from the vendor driver. I do not know if
patching the driver is an acceptable approach or not.
Signed-off-by: Kristian Evensen
---
.../ipq40xx/base-files/etc/board.d/02_network | 5 +
.../etc/hotplug.d/firmware/11-ath10k-caldata | 6
are of and will fix before the final submission, is
to add support for printing ipsets. Right now "fw3 print" prints per-interface
rules.
Signed-off-by: Kristian Evensen
---
ipsets.c | 38 ++-
ipsets.h | 7 ++
main.c| 8 +-
options.
required patching the
mdio-driver, and the code added comes from the vendor driver. I do not know if
patching the driver is an acceptable approach or not.
v1->v2:
* Do not use wildcard as identifier in the board.d-scripts (thanks
Adrian Schmutzler).
Signed-off-by: Kristian Evensen
---
.../ipq4
commit message of the initial U7623 commit. It is the .bin-file, and
not the .gz file that shall be sent to the device via tftp.
Signed-off-by: Kristian Evensen
---
.../0227-arm-dts-Add-Unielec-U7623-DTS.patch | 37 +-
1 file changed, 22 insertions(+), 15 deletions(-)
diff
Hi Jonas,
On Tue, Aug 7, 2018 at 10:10 PM, Jonas Gorski wrote:
> You are adding a second memory node with the same register range as
> the one directly above here, that looks wrong.
Thanks for noticing. The first memory node is redundant and a
left-over from when mediatek was based on an older k
message of the initial U7623 commit. It is the .bin-file, and
not the .gz file that shall be sent to the device via tftp.
v1->v2:
* Remove redundant memory node (thanks Jonas Gorski)
Signed-off-by: Kristian Evensen
---
.../0227-arm-dts-Add-Unielec-U7623-DTS.patch |
Hello,
I have some routers running OpenWRT (latest nightly) and that I have
to access remotely (using reverse SSH). When I restart networking
(/etc/init.d/network restart), clients on the LAN can no longer obtain
an IP address using DHCP. If I restart networking locally, DHCP works
as expected aft
Hi Jo-Philipp,
On Tue, Sep 25, 2018 at 6:59 AM Jo-Philipp Wich wrote:
> whats the complete dnsmasq cmdline?
This is the command line:
/usr/sbin/dnsmasq -C /var/etc/dnsmasq.conf.cfg01411c -k -x
/var/run/dnsmasq/dnsmasq.cfg01411c.pid
The configuration looks as follows:
# auto-generated config fi
Hi,
On Wed, Sep 26, 2018 at 3:14 PM Kristian Evensen
wrote:
> On Tue, Sep 25, 2018 at 11:23 AM Jo-Philipp Wich wrote:
> > does the same happen without "bind-dynamic" ? My hunch is that dnsmasq
> > fails to "resubscribe" to the socket after the ifindex of br
Hi,
On Tue, Sep 25, 2018 at 11:23 AM Jo-Philipp Wich wrote:
> Maybe netlink congestion or something related to privilege dropping? Can
> you manage to capture an strace log of the running dnsmasq instance
> while the network is getting restarted?
After some discussion on the dnsmasq mailing list
ess to and where this property is set, EEPROM is
only available from mtd.
Signed-off-by: Kristian Evensen
---
...om-on-SoC-from-a-mtd-device-defines-.patch | 34 ---
1 file changed, 29 insertions(+), 5 deletions(-)
diff --git
a/package/kernel/mac80211/patches/rt2x00/604-rt2x00-l
irewall or resort to scripts.
* Add support for the counters and comment extensions. By setting
"counters" or "comment" to true, then counters or comments are added to
the set.
Signed-off-by: Kristian Evensen
---
ipsets.c | 35 +-
f the file was crated by request_firmware().
>
> Cc: Felix Fietkau ,
> Cc: Daniel Golle
> Signed-off-by: Stanislaw Gruszka
Thanks for the patch. I submitted a patch doing something similar some
days ago, but your fix is much nicer. FWIW:
Acked-by
There is a new APU-model available, APU3. The device is configured in
the same way as the APU1 and APU2, so the same LED/network setup can be
used.
I considered changing the case to pc-engines-apu*, but I chose to follow
the existing pattern and add the full board name.
Signed-off-by: Kristian
Hello,
I have recently updated some ramips mt7621-devices (ZBT WG3526) to the
latest nightly. Almost everything seems to work fine, but using either
wifi interface in client mode seems triggers an oops. I see two
different oops-messages:
Message 1:
[ 66.442802] CPU 1 Unable to handle kernel pag
Hi,
On Thu, Apr 12, 2018 at 1:02 PM, John Crispin wrote:
> try enabling KALLSYMS to get a verbose stack trace.
Thanks for the pointer. I compiled a new image KALLSYMS, but now I am
not able to reproduce the error. Perhaps there was something dirty in
my build directory. I will keep the image KAL
Hi,
On Thu, Apr 12, 2018 at 3:28 PM, Kristian Evensen
wrote:
> Thanks for the pointer. I compiled a new image KALLSYMS, but now I am
> not able to reproduce the error. Perhaps there was something dirty in
> my build directory. I will keep the image KALLSYMS on the routers and
> keep
On Tue, Apr 17, 2018 at 2:56 PM, Felix Fietkau wrote:
> On 2018-04-17 13:50, Kristian Evensen wrote:
>> This is with the same image as last time (commit
>> f6e6eadc99c6274207f8f2ebc739063549959a1f) and configuration (radios
>> used as clients). I see that mt76 has been updat
Hi,
On Tue, Apr 17, 2018 at 3:34 PM, Kristian Evensen
wrote:
> Thanks, great. I just started building a new image for my router, will
> test and let you know if I still see the issue.
I think I have finished my testing, at least for now, and it seems the
problem is fixed. I compiled an
On Thu, Mar 15, 2018 at 1:30 PM, Kristian Evensen
wrote:
> There is a new APU-model available, APU3. The device is configured in
> the same way as the APU1 and APU2, so the same LED/network setup can be
> used.
>
> I considered changing the case to pc-engines-apu*, but I chose
Hi,
On Sat, Apr 21, 2018 at 2:58 AM, Philip Prindeville
wrote:
> Looks okay to me.
Great!
> Are the cases stenciled with the port #’s?
No, there are no markings on the case.
-Kristian
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
ht
Hello,
On Wed, Apr 18, 2018 at 11:34 AM, Kristian Evensen
wrote:
> I will keep an eye on this router, just in case, but it seems the
> problem is gone. Thanks for fixing it so fast!
The router (WG3526) has been running fine for a while now, but after
changing configuration from client to
Hello,
When building and testing nightly on an MT7620-device I have (the
Sanlinking D240), I noticed that changing the state of the two
exported pins (45 and 46) had no effect. The pins are used to control
the power to the two mini-PCIe slots on the board, and the devices
connected to the slots we
On Sun, May 20, 2018 at 10:26 PM, Rosen Penev wrote:
>> Bisecting further is hard, since the
>> commit is a combination of (a lot of) clean-up and some functional
>> changes.
> Changes can be viewed on the linux-next tree. It should be as simple
> as dropping in the relevant files to the files-4.1
Hi,
On Tue, May 22, 2018 at 4:33 PM, John Crispin wrote:
> what exactly is the issue ? breaking compat means that rosen either needs to
> fix the regression or we need to revert the patch.
The issue I saw is that writing to GPIO has no effect. On my device
(mt7620-based), I can control the power
Hi,
On Tue, May 22, 2018 at 1:33 PM, Rosen Penev wrote:
> Looks like it's this commit:
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/staging/mt7621-mmc?h=next-20180517&id=b734735fcaca60e8f07b040cd8a700f6fabe5b39
>
> Please try reverting. Unfortunately I don'
On Wed, May 23, 2018 at 4:09 AM, Andrey Jr. Melnikov
wrote:
> In gmane.comp.embedded.lede.devel Rosen Penev wrote:
>> On Tue, May 22, 2018 at 7:45 AM, Kristian Evensen
>> wrote:
>> > Hi,
>> >
>> > On Tue, May 22, 2018 at 4:33 PM, John Crispin wrote:
Hi,
On Tue, May 22, 2018 at 10:33 PM, Rosen Penev wrote:
> Looks like it's this commit:
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/staging/mt7621-mmc?h=next-20180517&id=b734735fcaca60e8f07b040cd8a700f6fabe5b39
>
> Please try reverting. Unfortunately I don
Hi,
> I know how to fix the issue by recovery, however, from the responses
> in the topic on the Lede forum it seems more people are running into
> this issue. This definitely needs to be fixed before a 18.06 release.
> Is there someone with a mt7621 device that can reproduce the problem,
> and th
Hi,
On Fri, May 25, 2018 at 7:06 PM, Kristian Evensen
wrote:
>> I know how to fix the issue by recovery, however, from the responses
>> in the topic on the Lede forum it seems more people are running into
>> this issue. This definitely needs to be fixed before a 18.06 re
Hi,
(Accidentally hit send)
On Fri, May 25, 2018 at 7:06 PM, Kristian Evensen
wrote:
>> I know how to fix the issue by recovery, however, from the responses
>> in the topic on the Lede forum it seems more people are running into
>> this issue. This definitely needs to be fi
Hi,
Some days ago I pulled master, built an image and installed it on my
ZBT-WE1326 router. After installing the image, I noticed that wifi is
broken. When looking at dmesg, mt76 reports:
[ 14.479853] mt76x2e :01:00.0: MCU message 1 (seq 1) timed out
I initially suspected mt76, but wifi tu
Hello,
On Tue, May 29, 2018 at 5:24 PM, Kristian Evensen
wrote:
> Carrying a local revert of the commit in question is always a
> possibility (and does not seem to have any unintentional
> side-effects), but I would rather try to fix the problem properly.
> Does anyone have any su
oring wifi.
Signed-off-by: Kristian Evensen
---
target/linux/ramips/dts/ZBT-WE1326.dts | 3 +++
1 file changed, 3 insertions(+)
diff --git a/target/linux/ramips/dts/ZBT-WE1326.dts
b/target/linux/ramips/dts/ZBT-WE1326.dts
index 6cbab66307..72707192a2 100644
--- a/target/linux/ramips/dts/ZBT-
Hi,
On Tue, May 29, 2018 at 10:49 PM, Karl Palsson wrote:
> There were a few people on this today it seems :)
Great!
> There's a patch at the bottom of that from mangix/neheb that
> removes from overrides that just set 0s, and that fixed it for my
> we1326
Yes, I saw the patch and made the cha
Hi,
On Tue, May 29, 2018 at 9:21 PM, Kristian Evensen
wrote:
> + interrupt-map = <0x1 0 0 1 &gic GIC_SHARED 24
> IRQ_TYPE_LEVEL_HIGH>,
> + <0x2 0 0 1 &gic GIC_SHARED 25
> IRQ_TYPE_LEVEL_HIGH>;
> +
Now that the offending c
AT32-paritions. While the command (fatload) is there, it just throws an
error when I try to use it.
* I will submit and hope to get the DTS for the device accepted
upstream. If and when that happens, I will update the patches
accordingly.
Signed-off-by: Kristian Evensen
---
.../mediatek/base-fil
Hi Pavel,
On Tue, Jul 3, 2018 at 8:20 PM, Pavel Ivanov wrote:
> Hi, Kristian !
> In your instructions for the firmware U7623-02, you write about
> repartitioning emmc (tftpboot $ {loadaddr} ).
> Sorry, i do not understand where I should take the mbr file?
You need to create the mbr yourself. I
Hi,
I have created a small tool which uses the MAC address to identify an
interface, and then collects some statistics about the interface. This
tool has worked fine for a long time, but lately I have noticed
strange values when running on some mt7620-boards. The problem turns
out to be the MAC ge
The changed applied to BananaPi R2 in upstream commit c0b0d540db1a,
which was backported to 4.14 in 4.14.53, is also required for the U7623.
Without updating the memory node, the board refuses to boot.
Fixes: d0839e020d0a ("kernel: bump 4.14 to 4.14.53")
Signed-off-by: Kristi
Hi Felix,
On Sun, Jun 29, 2014 at 8:36 PM, Felix Fietkau wrote:
> Please test the latest version and check if that hack is still necessary.
Thanks for your reply. I tested with latest netifd and latest libubus,
to make sure that I got the reload-fixes. The issue is unfortunately
still present. I
On Sun, Jun 29, 2014 at 11:19 PM, Felix Fietkau wrote:
> Thanks for the info about the commit that broke it, now this issue
> makes more sense to me. Please try this patch:
With this patch everything works fine, I do not see the crash any
more. Thanks for the help!
-Kristian
Hello,
I am currently working on a small project and I have come across a
problem I have not been able to solve myself. My setup is as
following, I have a TP-LINK WDR4300 (so ar71xx) router that will be
used as an access point to share a WAN connection. The WAN connection
is a different wifi. My i
Hi all,
On Sat, Aug 9, 2014 at 12:03 PM, Kristian Evensen
wrote:
> 2) When disconnecting any WIFI dongle, I always get a kernel oops.
> This happens irrespective of if the dongle is active (for example
> connected to network) or if I have just connected it to the router.
> The kerne
andling NEWROUTE nor DELROUTE. Store the
source address in RTA_PREFSRC, so that option works as specified in
documentation.
Signed-off-by: Kristian Evensen
---
system-linux.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/system-linux.c b/system-linux.c
index 83827d5..428302f
On Tue, Nov 25, 2014 at 8:47 PM, Steven Barth wrote:
> Maybe we should use RTA_PREFSRC for IPv4 and RTA_SRC for IPv6?
Sounds good to me. I am not to familiar with configuring IPv6, so I
was not aware that RTA_SRC is used differently there.
If no-one else jumps in before me, I will submit an upda
1 - 100 of 149 matches
Mail list logo
