/17 20:25, Mauro Mozzarelli wrote:
From r4940-00e9a7a release, just built, BT Home Hub 5 router fails to
connect to dsl at boot.
After issuing:
# /etc/init.d/dsl_control stop
and then
# /etc/init.d/dsl_control start
It will reconnect eventually, but it won't automatically after a reboo
Home Hub 5 router fails to
connect to dsl at boot.
After issuing:
# /etc/init.d/dsl_control stop
and then
# /etc/init.d/dsl_control start
It will reconnect eventually, but it won't automatically after a reboot.
I have seen a lantiq patch coming through git, so this issue might be
re
From r4940-00e9a7a release, just built, BT Home Hub 5 router fails to
connect to dsl at boot.
After issuing:
# /etc/init.d/dsl_control stop
and then
# /etc/init.d/dsl_control start
It will reconnect eventually, but it won't automatically after a reboot.
I have seen a lantiq patch c
On 2017-01-17 19:41, K.Mani wrote:
> When we create a file on the booted board and reboot the file
> doesn't persist.
> Environment:
> OpenWRT branch "Barrier Breaker" on Annapurna board, with
> ALpine-v1(soc) is having NOR flash(MX25U25635F) 32MB
The vers
When we create a file on the booted board and reboot the file
doesn't persist.
Environment:
OpenWRT branch "Barrier Breaker" on Annapurna board, with
ALpine-v1(soc) is having NOR flash(MX25U25635F) 32MB
I think mounting of rootfs_data type jffs2 is not happe
2017-01-11 14:25 GMT+01:00 L. D. Pinney :
> This patch resets the spi to 3 byte mode needed for devices with more than
> 16M Flash.
> Tested on the Onion Omega2+ (MT7688)
>
> Signed-off-by: L. D. Pinney
> Tested-by: Nita Vesa
>
> ---
>
> diff --git
> a/target/linux/ramips/patches-4.4/101-spi-re
This patch resets the spi to 3 byte mode needed for devices with more than 16M
Flash.
Tested on the Onion Omega2+ (MT7688)
Signed-off-by: L. D. Pinney
Tested-by: Nita Vesa
---
diff --git a/target/linux/ramips/patches-4.4/101-spi-reset-to-3-byte-mode.patch
b/target/linux/ramips/patches-4.4/10
this can be done by adding the following... itll ping for every X
seconds... and choice to reboot if lost
luci-app-watchcat
watchcat
On Tue, Nov 15, 2016 at 2:04 PM, Rafał Miłecki wrote:
> On 14 November 2016 at 12:20, Dennis Schneck wrote:
>> Have the issue that often the WAN
On 14 November 2016 at 12:20, Dennis Schneck wrote:
> Have the issue that often the WAN Interface
> lost connection / IP Address. (down and up of interface did not work)
> If i reboot the Device it runs.
What exact commands did you execute?
Have you tried restarting network or dnsmas
Hello,
sorry about my poor english.
Have the issue that often the WAN Interface
lost connection / IP Address. (down and up of interface did not work)
If i reboot the Device it runs.
Is there a tool in LEDE to detect fail
in interentconnectitity an reboot the device
if the interentconnectitity
on htmode 'VHT80'
option country 'US'
option channel 'auto'
option txpower '30'
config wifi-iface
option device 'radio1'
option network 'lan'
option mode 'ap'
option key 'password'
opt
On 10/20/2016 10:20 AM, Jiri Pirko wrote:
> Thu, Oct 20, 2016 at 09:48:48AM CEST, garet...@orcon.net.nz wrote:
>> Hi Jiri
>> This is a common problem on XM devices due to new uboot on AirOS >= 5.6.x,
>> although I haven't got any XW devices to test but its possibly the same?
>> Try downgrading back
s.infradead.org] On Behalf Of
>Jiri Pirko
>Sent: Thursday, 20 October 2016 8:29 p.m.
>To: openwrt-de...@lists.openwrt.org; lede-dev@lists.infradead.org
>Subject: [LEDE-DEV] Ubnt power beam board - back to defaults after reboot
>
>Hi.
>
>Trying Ubiquity power beam M5
dev-boun...@lists.infradead.org] On Behalf Of
Jiri Pirko
Sent: Thursday, 20 October 2016 8:29 p.m.
To: openwrt-de...@lists.openwrt.org; lede-dev@lists.infradead.org
Subject: [LEDE-DEV] Ubnt power beam board - back to defaults after reboot
Hi.
Trying Ubiquity power beam M5. According to the instructions on
Hi.
Trying Ubiquity power beam M5. According to the instructions on openwrt
wiki, I'm using loco m5 firmware. All looks fine, only configuration is
lost after every reboot.
Tried:
openwrt-15.05.1-ar71xx-generic-ubnt-loco-m-xw-squashfs-sysupgrade.bin
openwrt-15.05-ar71xx-generic-ubnt-loco
Hi,
i tried to upgrade my TP-Link Archer C7 v2 from 145 to 257 and router
seems to be in constant reboot cycle. When I reset the config via
recovery, the router boots fine, currently I'm back on v145.
Unfortunately I don't have serial (and AP is under warranty), so I gues
243,6 +243,7 @@ do_upgrade() {
[ -n "$DELAY" ] && sleep "$DELAY"
ask_bool 1 "Reboot" && {
v "Rebooting system..."
+ umount -a
reboot -f
sleep 5
echo b
Sometimes, for various reasons, user may want to reboot a device. This
is a common task and it makes sense to support it with something common
like a procd.
Right now both: LuCI and LuCI2 implement this feature on their own with
luci-rpc-luci2-system reboot and luci-rpc-sys reboot. This leads to
On 05/07/2016 17:12, Rafał Miłecki wrote:
> Sometimes, for various reasons, user may want to reboot a device. This
> is a common task and it makes sense to support it with something common
> like a procd.
>
> Right now both: LuCI and LuCI2 implement this feature on their own
Sometimes, for various reasons, user may want to reboot a device. This
is a common task and it makes sense to support it with something common
like a procd.
Right now both: LuCI and LuCI2 implement this feature on their own with
luci-rpc-luci2-system reboot and luci-rpc-sys reboot. This leads to
hi,
the webserver will see an update to F24 tonight and get more disk space.
there will be several reboots over the next few hours. if all goes well
we will be back to normal operational mode in a few hours.
John
___
Lede-dev mailing list
Lede-
On Wed, 25 May 2016, Martin Tippmann wrote:
On Wed, May 25, 2016 at 3:15 AM, Rosen Penev wrote:
One other problem is that on the Openwrt wiki, there is a lot of old
information. Maybe a mechanism can be introduced where one can look up
the last edited date of a specific page. Maybe on the bott
> do you mean as such -->
>
> https://www.lede-project.org/docs/index.html
> https://github.com/lede-project/web/tree/master/docs
>
> you can even send a PR via github or use the ML
Totally missed that! Sorry!
regards
Martin
___
Lede-dev mailing list
L
On 25/05/2016 15:04, Martin Tippmann wrote:
> On Wed, May 25, 2016 at 3:15 AM, Rosen Penev wrote:
>> One other problem is that on the Openwrt wiki, there is a lot of old
>> information. Maybe a mechanism can be introduced where one can look up
>> the last edited date of a specific page. Maybe on
On Wed, May 25, 2016 at 3:15 AM, Rosen Penev wrote:
> One other problem is that on the Openwrt wiki, there is a lot of old
> information. Maybe a mechanism can be introduced where one can look up
> the last edited date of a specific page. Maybe on the bottom.
Yes - the supported models could/shou
Hi,
I'm not affiliated with OpenWRT nor LEDE (just a member of a small
Freifunk group) but the Wiki was (and still is) always my first choice
when looking for documentation.
Is there a plan to provide a LEDE wiki? The licence is CC
Attribution-Noncommercial-Share Alike 3.0[1] so it should be fine
Hi
Would appreciate pointers as to what might be causing this (or how to
investigate further):
Issuing "reboot" works fine on a rev 1.0 TPLink Archer C2600, however it
doesn't seem to work on a rev 1.1.
They apparently are exactly the same apart from the flash chip.
Plea
the reboot was not meant to be hostile or disruptive to OpenWrt. we are
just code nerds and messed up the politics of the launch at some places,
which in itself shows one of the reasons that motivated the reboot. the
whole idea is to give up our control over parts of the politics and
attract a new
28 matches
Mail list logo
