(resent to the list because my client decided to use HTML for some reason)
That patch is a raw kernel patch, you need to integrate it in LEDE's
buildsystem and hope that he is working with LEDE patches already applied.
Copy the patch's text in a text file and place this file in the
/patches-* f
Thank you all for the suggestions. I've tried the following steps:
1) Add the patch in a file with a name so that it will be added last:
999-mtu.patch. This failed during the build.
2) Next, I wanted to write these changes manually to a patch with
quilt. However, the file /drivers/net/ethernet/med
Weird, I'm not seeing the whole "mediatek" folder if I try to follow
your steps from a fresh source download with LEDE master (trunk/HEAD,
whatever).
I've checked the LEDE 17.01 branch and yes, there the "mediatek" folder
is there and also that file. Kernel version is the same for both,
4.4.61
The mediatek folder is not there by default. It gets generated in the
during the "make" command when compiling the image by the patches. It
can be found at the following full path:
source/build_dir/target-mipsel_24kc_musl/linux-ramips_mt7621/linux-4.4.61/drivers/net/ethernet/mediatek
I will try i
Hello,
Many devices make use of "dual firmware" configurations, splitting the
available flash and allowing two complete and independent installations.
This works fine for devices like the Linksys WRT1900AC etc, where the
boot loader make sure the kernel command line "root=" parameter matches
the b
Hi everybody,
I noticed a serious problem with a Clearfog build that enables
CONFIG_KERNEL_EARLY_PRINTK=y.
In short: after Loading Kernel, the serial console stays completely
silent, and apparently the board does *not* boot.
This came as a serious surprise to me.
Turns out the reason for this is
On 04/23/2017 08:40 PM, Bjørn Mork wrote:
> Hello,
>
> Many devices make use of "dual firmware" configurations, splitting the
> available flash and allowing two complete and independent installations.
> This works fine for devices like the Linksys WRT1900AC etc, where the
> boot loader make sure
Alberto Bursi writes:
> Can this "bs" partition be manipulated on installation or later?
Yes. The only thing preventing that is the default "(ro)" in the LEDE
images. But by using mtd-rw it can be manipulated. That's how I fixed
my installation.
I believe there are tools to manipulate it in
Hi LEDE Devs,
If this is not the right place to report this please let me know.
When selecting package dnsmasq-full from make menuconfig I believe it
should deselect package dnsmasq.
Otherwise this happens when selecting dnsmasq-full from an otherwise
default config.
Configuring ppp-mod-p
This allows us to make use of upgraded in "snapshot convert" as well.
Signed-off-by: Matthias Schiffer
Note: obviously, this patch should go into the procd repo when it is
actually applied; it is provided like this for now to allow easier testing
of the whole series.
---
...d-support-for-passin
When talking about
https://bugs.lede-project.org/index.php?do=details&task_id=685 with jow
and lynxis, we came to the conclusion that the best way to fix sysupgrades
would be to generalize the staged sysupgrade used on NAND devices to work
on all targets. That is what this patchset does, with some
In preparation for switching all targets to the staged sysupgrade
mechanism, upgraded is always built, and the "nandupgrade" ubus method is
renamed to "sysupgrade".
To make the migration easier, support for the old name "nandupgrade" and
the "upgrade" method that will become unused with the staged
Use install_bin to copy upgraded with all dependencies. The old name
/tmp/upgraded is temporarily retained as a symlink to avoid breaking
things.
Signed-off-by: Matthias Schiffer
---
package/system/procd/files/nand.sh | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/p
The chroot ensures we don't reference anything on the rootfs and is
reverted after the upgraded exec. While we're at it, also improve error
handling and logging at bit.
This change also required changes to sysupgrade, as the dynamically linked
version is expected at a different location, and libra
All targets with NAND support should gradually move their nand_do_upgrade
calls from platform_pre_upgrade to platform_do_upgrade.
Signed-off-by: Matthias Schiffer
---
target/linux/ramips/base-files/lib/upgrade/platform.sh | 9 +
1 file changed, 1 insertion(+), 8 deletions(-)
diff --git
We can reuse the kill_remaining and run_ramfs facilities of the stage2 run
by upgraded.
Signed-off-by: Matthias Schiffer
---
package/system/fstools/Makefile | 2 +-
package/system/fstools/files/snapshot | 16 +---
2 files changed, 10 insertions(+), 8 deletions(-)
diff --git a
Signed-off-by: Matthias Schiffer
---
.../base-files/files/lib/preinit/40_run_failsafe_hook | 6 +-
.../base-files/files/lib/preinit/99_10_failsafe_login | 11 +++
package/base-files/files/sbin/sysupgrade | 18 +-
3 files changed, 25 insertions(+), 10 d
Signed-off-by: Matthias Schiffer
Note: obviously, this patch should go into the procd repo when it is
actually applied; it is provided like this for now to allow easier testing
of the whole series.
---
...-that-has-become-unnecessary-after-sysupg.patch | 120 +
1 file changed
This will allow to add sysupgrade support via upgraded for failsafe mode.
Signed-off-by: Matthias Schiffer
Note: obviously, this patch should go into the procd repo when it is
actually applied; it is provided like this for now to allow easier testing
of the whole series.
---
...pport-for-sysupg
We always want to support staged upgrades now, so it's better to include
upgraded into the main package. /lib/upgrade/nand.sh is moved to
base-files.
The procd-nand-firstboot package is removed for now, it may return later
as a separate package.
Signed-off-by: Matthias Schiffer
---
package/base
This should ensure that the kernel partition can be mounted in
platform_copy_config when its size has changed. The following "sleep"
becomes unnecessary and is removed (it was skipped anyways when a change of
the partition table was detected).
While we're at it, also remove the ask_bool that can't
Support for the -d and -p options is dropped; it may be added again at some
point by adding these flags to the ubus sysupgrade call.
A downside of this is that we get a lot less information about the progress
of the upgrade: as soon as the actual upgrade starts, all shell sessions
are killed to al
Some functions only used by stage2 are moved there from common.sh.
One piece that could still use more cleanup is platform_pre_upgrade: many
targets reference files from there are aren't available in the ramfs, so
we need to evaluate it before the switch; conversely, flash writes happen
in that fu
You may want to enable CONFIG_DEBUG_MVEBU_UART0_ALTERNATE or
CONFIG_DEBUG_MVEBU_UART1_ALTERNATE if early printk is being enabled.
Best Regards,
Syrone Wong
On Mon, Apr 24, 2017 at 3:39 AM, Josua Mayer wrote:
> Hi everybody,
>
> I noticed a serious problem with a Clearfog build that enables
> C
This reverts commit a03216660797173fbe67866f75564e3fec9c1e8d. The previous
change causes IFUP events to occur from 30 seconds to 30 minutes depending
on various conditions at the WAN6 (typ.) interface. If a DHCPv6 lease is
24 hours and the connection is stable, then in other linux distro we would
e
On 04/23/2017 10:23 PM, Eric Luehrsen wrote:
> This reverts commit a03216660797173fbe67866f75564e3fec9c1e8d. The previous
> change causes IFUP events to occur from 30 seconds to 30 minutes depending
> on various conditions at the WAN6 (typ.) interface. If a DHCPv6 lease is
> 24 hours and the connec
Hi John and Jo-Philipp,
Have you ever got similar problem, or known any possible reason about this,
or known anyone who probably know this?
I just found much memory would be consumed if I configured board as bridge mode
in /etc/config/network and did UDP throughput test.
But using brctl to config
Hi,
this is most certainly a bug in the kernel. either the ethernet driver
blows up under load or some other memory allocation related bug. it is
very common for ethernet to kill boards under load by triggering bugs.
John
On 24/04/17 05:49, Y.B. Lu wrote:
Hi John and Jo-Philipp,
Have y
On Mon, Apr 24, 2017 at 4:24 AM, Eric Luehrsen wrote:
> This reverts commit a03216660797173fbe67866f75564e3fec9c1e8d. The previous
> change causes IFUP events to occur from 30 seconds to 30 minutes depending
> on various conditions at the WAN6 (typ.) interface. If a DHCPv6 lease is
> 24 hours and
29 matches
Mail list logo
