Hi Martin/John,
Can you give us an idea where to look. If I use an external modem in bridge
mode and run PPPoE on the router then it works fine.
However with PPPoA, TCP and UDP misbehaves, UDP packets over 1300 seems to be
dropped silently and the first tcp packet is dropped with no logs in IP
Hello everyone,
For unknown reason I have problem with access https://git.lede-project.org.
[user@v-arch-1 ~]$ git clone https://git.lede-project.org/source.git
Cloning into 'source'...
fatal: unable to access 'https://git.lede-project.org/source.git/':
Failed to connect to git.lede-project.org p
While at it, convert to new build method
Signed-off-by: Yousong Zhou
---
.../linux/ar71xx/files/arch/mips/ath79/mach-wrt400n.c | 12 ++--
target/linux/ar71xx/image/generic.mk | 19 +++
target/linux/ar71xx/image/legacy-devices.mk | 5 -
targ
Signed-off-by: Yousong Zhou
---
tools/firmware-utils/src/wrt400n.c | 449 +++--
1 file changed, 181 insertions(+), 268 deletions(-)
diff --git a/tools/firmware-utils/src/wrt400n.c
b/tools/firmware-utils/src/wrt400n.c
index 1cf1deb..de9f945 100644
--- a/tools/firm
I believe the situation at the moment for WRT400N is like this
- factory image is broken and will brick the device because the utility
wrt400n will truncate the kernel to 1MB.
- sysupgrade image is missing from snapshots because the kernel size is too
big exceeding the size limit imposed b
Thanks Mathias, will generate a build.
Last time I tried chaos chalmer, I couldn't get VDSL to work (I personally use
VDSL), it wouldn't get line sync, but I'll try again and use different
firmware if required.
Thanks
Daniel
-Original Message-
From: Mathias Kresin [mailto:d...@kresin
Hello everyone
I am trying to build LEDE for the TRENDnet TEW-827DRU and I'm stuck on a
problem where the kernel won't boot.
This device is based off the IPQ8064 and QCA9980+QCA9980 chips. Very
similar to the TP-Link Archer C2600, Linksys EA8500, and Netgear D7500.
I have the factory format
From: Ram Chandra Jangir
This change will enables eMMC (ext4 fs) boot support, when we try to boot
from eMMC card then it will read partition names from
/sys/block/mmcblkX/mmcblkXY/uevent
file and will mount the rootfs_data partition as ext4fs overlay.
Signed-off-by: Ram Chandra Jangir
---
CMa
From: Josua Mayer
When there is a) no rootfs_data overlay partition,
and b) /dev/root points to an ext4 partition
the partition would be mounted twice, once as / and then as /overlay.
The essence of this change is to return before mounting /overlay,
if /dev/root has been mounted as /.
Signed-off
From: Ram Chandra Jangir
This change will enables eMMC (ext4 fs) boot support, when we try to boot
from eMMC card then it will read partition names from
/sys/block/mmcblkX/mmcblkXY/uevent
file and will mount the rootfs_data partition as ext4fs overlay.
Signed-off-by: Ram Chandra Jangir
---
CMa
From: Josua Mayer
Signed-off-by: Josua Mayer
---
libfstools/ext4.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libfstools/ext4.c b/libfstools/ext4.c
index f648aa8..454b15e 100644
--- a/libfstools/ext4.c
+++ b/libfstools/ext4.c
@@ -129,8 +129,8 @@ static int check_for_mtd
Hi John,
I have finally found the time to look into this, and managed to
reproduce the segfault that Álvaro noticed.
It is caused by a call to fclose(0x0); This is very unexpected,
shouldn't the C library check for NULL and return quietly?
Either way, I submitted the new patchset for you to revie
12 matches
Mail list logo
