Support for Easybox 904 LTE


#82

Not to mention that requiring a bootloader modification will pretty much immediately kill any chance of getting it accepted as an official target.


#83

I wouldn't go quite that far, as the bootloader must be replaced for many other lantiq devices anyways (e.g. o2 box 6431, BT Home Hub 5 type A, many more), but it's certainly nothing to be taken lightly (losing the old badblock list would be another reason trying to avoid this). It might make getting official support a lot easier though.


#84

The HH5a bootloader doesn't have to be replaced (just uploaded and run), but yes, I see your point for some special targets. However, I distinctly remember some head honcho on the mailing list stating something to the extent of "OpenWrt strives not to replace the bootloader, if we have to replace the bootloader, we won't accept the target", although I can't recall where it was anymore. My mind may be playing tricks on me.

At any rate, not replacing the bootloader seriously increases acceptance.


#85

O.k., you're right about the BT HH5a (it's been a while), but on the Arcadyan VGV7510KW22 (O² Box 6431) and several other ISP branded devices replacing the bootloader (brnboot in that case) with u-boot is necessary (at least for openwrt-lantiq-xrx200-arcadyan_vgv7510kw22-nor-squashfs-sysupgrade.bin). Obviously this is frowned upon, but it might still be an easier option.


#86

I have make a raw build and it works, but i use the old linked uboot.

When the router boot up, for a short time it looks likes if it hangs them it works, at this moment i can see that lcd4linux need 89% CPU usage.
But only for a short time

The only problem is no working f2fs


#87

A more sensible reworking of the lcd4linux configuration notwithstanding, I think there's a quick fix for that.

The lcd4linux.conf that comes with the images has several display widgets set to a refresh rate of "tack", which is further down defined as "150", meaning they are supposed to be refreshed at 150 millisecond intervals. This is not only quite unnecessary, it also leads to lcd4linux using up ~10% CPU on those widgets, and ~30% at peak times when other widgets refresh. Which may also be the reason why QAuge decides to shut down lcd4linux when the screen is off -- it just takes up too much CPU like that.

Increasing the "tack" value to 1000 or 2000 (1 or 2 seconds respectively) or straight up replacing "update tack" with "update 1000" immediately reduces CPU load to < 1% (and in the process removes the need to shut down lcd4linux since the CPU load is not an issue anymore). I haven't looked into it further, as I said I fell out of tinkering with the device a few months ago, but I think a slightly delayed initialization of lcd4linux may help with the initial CPU spike, too.


#88

Some clarification about the short freeze when starting up the box. This is the case, when the wifi driver uploads the wlan firmware to the wifi soc, which is connected to the network.The freeze occurs also at the stock rom.


#89

Hi, I have an old Tp-Link Archer MR200 (LTE modem) and I want to renew it.

I have a look to Vodafone EasyBox 904 LTE in ebay.de web pages. It is cheap (second hand), but I want to ensure that:

  1. is it unlock for all LTE SIM cards? Or is it only for Vodafone? In that case, is it easy to unlock it?
  2. Is openwrt working with the LTE SIM card? I dont mine to loose DSL as I want to use it only with SIM CARD
  3. What bout 5 Ghz wifi ?

Thanks a lot guys,


#90

@ortegafernando
The Easybox 904-lte variant is not supported now.
It exist only an opened image of original FW (the original FW based on openwrt (10.03 or so))
see the thread inside old forum (link in post 2).

The Easybox 904xDSL variant will supported with a fork or a patch.
On this device all hardware will support but without ISDN and Simcardreader,
but note it exist some restrictions like WLAN only AP mode are possible, not all ADSL annexe, etc.


#91

Ok, thanks a lot. I have just delete this idea from my head.. Thanks.


#92

--- Changes to release ---
I uploaded a new SMP build which is now based on the configuration of @slh (Thanks!).
I added LuCI because I think this is a good thing for end users.
eb904xDSL_minimal.in.

I also wanted to use a branch with 18.06 to comply with stable releases, but it is using kernel 4.9 for the lantiq target. So I defer this until the next round where 4.14 is used =)


#93

The system looks great in its new "clean" default. Minor issues aside (we should look into getting LuCI to properly recognize the wifi settings, and adjust LCD4linux to settings that don't bother the CPU), it is a great starting point now.

However, I sysupgraded to your latest build yesterday evening, and then decided to "soak test" it. In its absolute default configuration and without anything connected and just wifi on, had the box sitting overnight. In this time, it randomly rebooted several times and in the morning I found it with an "unable to boot" screen, refusing to boot again.

I will flash it on my other box (I have two) and "soak test" it in a similar manner to rule out a hardware fault.


#94

After some tests, my box is also rebooting in a unpredictable manner.... The sad thing is, that no reason is printed in the serial messages. I suspect some wifi issues. Can you try out by disabling the rt38.. driver and report back? ( '/etc/init.d/rt38... disable')


#95

Quite possible. Last night, after installing, while I had LuCI's "wireless" interface page open in the browser, ssh connections would drop and not allow new connections until I closed the LuCI page (which was, at the time, polling the wifi interface on a regular basis). I couldn't reproduce it though, so I wrote it off as an unrelated coincidence.

Test unit is "soaking" now with disabled wifi driver. So far no reboots, but it has to run quite a bit longer than two hours to make an assessment.


#96

Yup. It seems to be the wifi driver alright. 20 hours in, 20 hours uptime, not a single random reboot.

For comparison: with active wifi, it had a first random reboot within an hour, and completely died after less than 12. (What I'm especially worried is that it actually damaged the installation, I had to go through a complete reflash to remedy that. And at this point was I lucky it didn't damage the bootloader?)

Edit: It managed an uptime of around 30 hours with nothing connected but the power supply, then out of the blue, it rebooted randomly. :frowning:

Edit 2: The Home Hub 5A -- another Lantiq device -- would reboot if the DSL port is unused. Apparantly a patch was submitted for 17.01.something, but I am still looking for that patch and whether it made it into the generic target or was specific to the HH5A.

The "OpenWrt/LEDE Installation Guide for BT Home Hub 5A" states that "a watchdog bug was also discovered which causes the hub to reboot between 24-48 hours if the hub is not connected to an active xDSL line. No patch is currently available."

So for the next round of soak testing, I disabled /etc/init.d/dsl_control ... let's see.


#97

It's a generic change for all lantiq devices.


#98

Hi I build an image with a patch from the master-lede branch of Easybox-904x git (19.01.2019), createt by the script from post # in this thread
and the files from how can we make xrx200 faster thread Post #1 how can we make xrx200 faster thread
and the script from Post 7#

General it works and it looks like a better irq balance but it does not speed up.
The wifi works to

other problems are:

  • The VDSL2 modem connects but it locks like not right work:
    It shows me Annex A but my Provider have Annexe B and i have choice an Annex B firmware
    "option ds_snr_offset" Have no effect
    And i have to less speed. (95Mb/s instead off 100Mb/s)

  • The other problem it fear that i have playing the NAND-flash to dead i get strange errors like:
    and sometimes the flash lost data, no idea if an pattern exist.

...
[    6.260608] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[    6.277030] init: - preinit -
Press the [f] key and hit [enter] to enter failsafe mode
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
[   10.748159] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" started, PID 671
[   10.786459] UBIFS (ubi0:1): recovery needed
[   10.837881] random: procd: uninitialized urandom read (4 bytes read)
[   10.919848] __nand_correct_data: uncorrectable ECC error
[   10.923707] __nand_correct_data: uncorrectable ECC error
[   10.929014] __nand_correct_data: uncorrectable ECC error
[   10.934323] __nand_correct_data: uncorrectable ECC error
...
[   11.208229] __nand_correct_data: uncorrectable ECC error
[   11.213538] __nand_correct_data: uncorrectable ECC error
[   11.218848] __nand_correct_data: uncorrectable ECC error
[   11.224157] __nand_correct_data: uncorrectable ECC error
[   11.229467] __nand_correct_data: uncorrectable ECC error
[   11.234776] __nand_correct_data: uncorrectable ECC error
[   11.256546] ubi0 warning: ubi_io_read: error -77 (ECC error) while reading 126976 bytes from PEB 521:4096, read only 126976 bytes, retry
[   11.274920] __nand_correct_data: uncorrectable ECC error
[   11.278787] __nand_correct_data: uncorrectable ECC error
[   11.284093] __nand_correct_data: uncorrectable ECC error
[   11.289403] __nand_correct_data: uncorrectable ECC error
[   11.294712] __nand_correct_data: uncorrectable ECC error
[   11.300021] __nand_correct_data: uncorrectable ECC error
[   11.305331] __nand_correct_data: uncorrectable ECC error
[   11.310640] __nand_correct_data: uncorrectable ECC error
[   11.316341] __nand_correct_data: uncorrectable ECC error
[   11.321260] __nand_correct_data: uncorrectable ECC error
[   11.326569] __nand_correct_data: uncorrectable ECC error
[   11.331878] __nand_correct_data: uncorrectable ECC error
[   11.337187] __nand_correct_data: uncorrectable ECC error
[   11.342497] __nand_correct_data: uncorrectable ECC error
[   11.347807] __nand_correct_data: uncorrectable ECC error
[   11.353116] __nand_correct_data: uncorrectable ECC error
[   11.374904] ubi0 error: ubi_io_read: error -77 (ECC error) while reading 126976 bytes from PEB 521:4096, read 126976 bytes
[   11.384591] CPU: 0 PID: 669 Comm: mount_root Not tainted 4.14.97 #0
[   11.390770] Stack : 00000000 00000209 c01c3000 8007c8d8 807c0000 8075d5ac 00000000 00000000
[   11.399120]         80712c04 87087b14 87d86b8c 8079c7c7 8070db10 00000001 87087ab8 74ab3c7c
[   11.407476]         00000000 00000000 80910000 00005878 00000000 00000000 00000007 00000000
[   11.415832]         00000146 01000000 00000145 00000000 80000000 807c0000 00000000 00000000
[   11.424187]         00000000 04121000 00001000 00000209 00000002 00000000 00000000 80900000
[   11.432543]         ...
[   11.434983] Call Trace:
[   11.437439] [<80011584>] show_stack+0x58/0x100
[   11.441890] [<805e8df4>] dump_stack+0xe4/0x120
[   11.446317] [<80411298>] ubi_io_read+0x248/0x330
[   11.450927] [<8040eda4>] ubi_eba_read_leb+0x2f0/0x450
[   11.455975] [<8040d708>] ubi_leb_read+0x88/0x100
[   11.460591] [<80255024>] ubifs_leb_read+0x3c/0xa4
[   11.465297] [<8025ddfc>] ubifs_start_scan+0x80/0xec
[   11.470163] [<8025e188>] ubifs_scan+0x4c/0x2d4
[   11.474603] [<8025ef2c>] ubifs_replay_journal+0x800/0x1494
[   11.480085] [<80252cd0>] ubifs_mount+0x10dc/0x187c
[   11.484875] [<80132c88>] mount_fs+0x20/0xb8
[   11.489058] [<80157f78>] vfs_kern_mount.part.7+0x60/0x170
[   11.494451] [<8015b9dc>] do_mount+0xa40/0xe40
[   11.498799] [<8015c180>] SyS_mount+0xb4/0xf4
[   11.503066] [<8001c378>] syscall_common+0x34/0x58
[   11.509182] UBIFS error (ubi0:1 pid 669): ubifs_check_node: bad CRC: calculated 0xf7dd00a5, read 0xc1dd8e65
[   11.517575] UBIFS error (ubi0:1 pid 669): ubifs_check_node: bad node at LEB 19:33656
[   11.525350] 	magic          0x6101831
[   11.528898] 	crc            0xc1dd8e65
[   11.532685] 	node_type      1 (data node)
[   11.536696] 	group_type     0 (no node group)
[   11.541046] 	sqnum          707
[   11.544180] 	len            3607
[   11.547420] 	key            (141, data, 60)
[   11.551580] 	size           4096
[   11.554799] 	compr_typ      1
[   11.557758] 	data size      3559
[   11.560927] 	data:
[   11.562991] 	00000000: 00 20 ca 22 81 0f 00 00 15 06 60 01 21 b5 ca 21 21 00 ff e1 0f f4 0a d9 cf 70 01 00 04 1e 20 b0
[   11.573692] 	00000020: cf 71 04 00 98 e8 cf 70 04 00 dc 0d e0 7f 20 a0 e0 7e f1 c0 74 01 00 04 a4 05 00 80 8e e8 cf 72
[   11.584398] 	00000040: 00 00 18 01 cf 71 01 00 1c 1c 58 a1 01 da 74 05 00 0a f6 06 40 a9 80 20 02 00 42 28 41 02 36 b9
[   11.595105] 	00000060: 38 60 c9 b8 22 78 2f 20 06 80 ca 20 a1 0a ae 0d cf 3c 7c 0c 01 11 f2 c0 e0 28 4e 00 15 06 6c 02
[   11.605812] 	00000080: 00 14 07 f2 8c 20 02 80 07 f4 2a d8 00 d9 28 72 d2 08 0f b5 17 00 4f f5 e0 78 f1 c0 e1 c5 cf 75
[   11.616516] 	000000a0: 04 00 a4 05 00 85 80 e0 94 06 08 21 21 00 b0 08 21 b5 ca 22 41 00 7c 11 06 c0 05 00 98 19 08 d1
...
[   12.697828] 	00000d40: 0f 7c 00 99 23 ae 26 00 02 09 24 fc 00 28 03 1a 09 00 00 88 39 e8 00 64 10 09 4a 00 09 00 da 00
[   12.708520] 	00000d60: 04 f0 10 d8 00 00 b1 01 e2 00 7c 05 07 f0 00 1c 61 98 31 00 0a e3 00 00 00 99 74 01 03 00 cc 22
[   12.719226] 	00000d80: 09 98 00 10 e8 64 01 00 05 d4 20 00 17 90 db 08 00 9e 81 8c 01 00 0c 04 05 98 00 cf 08 13 81 00
[   12.729932] 	00000da0: 20 d8 e6 f1 00 30 d8 e4 f1 00 74 6b 01 00 44 1e 20 99 00 7c 17 05 46 00 09 38 60 20 00 b2 61 b8
[   12.740638] 	00000dc0: 6c 00 0b 02 48 09 00 00 b1 01 9d 00 0e 44 7c 0e 00 04 76 04 00 00 e4 22 10 00 9e 64 03 03 00 01
[   12.751341] 	00000de0: 09 ec b8 00 00 d8 75
[   12.755529] CPU: 0 PID: 669 Comm: mount_root Not tainted 4.14.97 #0
[   12.761738] Stack : 00000000 ffffffff fffffffe 8007c8d8 807c0000 8075d5ac 00000000 00000000
[   12.770087]         80712c04 87087c14 87d86b8c 8079c7c7 8070db10 00000001 87087bb8 74ab3c7c
[   12.778443]         00000000 00000000 80910000 00009880 00000000 00000000 00000007 00000000
[   12.786799]         000001da 7f800000 000001d9 00000000 80000000 807c0000 00000000 00000013
[   12.795154]         ffffff79 00000000 8710c080 ffffffff 00000002 00000000 00000000 80900000
[   12.803510]         ...
[   12.805950] Call Trace:
[   12.808401] [<80011584>] show_stack+0x58/0x100
[   12.812855] [<805e8df4>] dump_stack+0xe4/0x120
[   12.817283] [<802557e4>] ubifs_check_node+0x25c/0x280
[   12.822336] [<8025dc8c>] ubifs_scan_a_node+0xbc/0x1ac
[   12.827378] [<8025e1c4>] ubifs_scan+0x88/0x2d4
[   12.831817] [<8025ef2c>] ubifs_replay_journal+0x800/0x1494
[   12.837304] [<80252cd0>] ubifs_mount+0x10dc/0x187c
[   12.842090] [<80132c88>] mount_fs+0x20/0xb8
[   12.846272] [<80157f78>] vfs_kern_mount.part.7+0x60/0x170
[   12.851666] [<8015b9dc>] do_mount+0xa40/0xe40
[   12.856014] [<8015c180>] SyS_mount+0xb4/0xf4
[   12.860280] [<8001c378>] syscall_common+0x34/0x58
[   12.865042] UBIFS error (ubi0:1 pid 669): ubifs_scan: bad node
[   12.870871] UBIFS error (ubi0:1 pid 669): ubifs_scanned_corruption: corruption at LEB 19:33656
[   12.879478] UBIFS error (ubi0:1 pid 669): ubifs_scanned_corruption: first 8192 bytes from LEB 19:33656
[   12.895453] UBIFS error (ubi0:1 pid 669): ubifs_scan: LEB 19 scanning failed
[   12.901474] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" stops
[   12.908968] mount_root: failed to mount -t ubifs /dev/ubi0_1 /tmp/overlay: No error information
[   12.916863] mount_root: overlay filesystem has not been fully initialized yet
[   12.924292] mount_root: switching to ubifs overlay
[   12.928546] mount_root: switching to ubifs failed - fallback to ramoverlay
[   12.974287] urandom-seed: Seed file not found (/etc/urandom.seed)
fw_config exists already
/etc/preinit: line 1: /usr/sbin/fw_printenv: not found
Bootnum: 
...

And loop of this:

...
[  163.826623] __nand_correct_data: uncorrectable ECC error
[  163.831549] __nand_correct_data: uncorrectable ECC error
[  163.836858] __nand_correct_data: uncorrectable ECC error
[  163.842167] __nand_correct_data: uncorrectable ECC error
[  163.847477] __nand_correct_data: uncorrectable ECC error
[  163.852786] __nand_correct_data: uncorrectable ECC error
[  163.858096] __nand_correct_data: uncorrectable ECC error
[  163.863405] __nand_correct_data: uncorrectable ECC error
[  163.872688] ubi0 error: ubi_io_read: error -77 (ECC error) while reading 28672 bytes from PEB 1333:4096, read 28672 bytes
[  163.882276] CPU: 0 PID: 67 Comm: kworker/0:1 Not tainted 4.14.97 #0
[  163.888485] Workqueue: ubiblock0_0 ubiblock_do_work
[  163.893338] Stack : 8070da7c 87233c5c 807a0000 87228000 8070db10 00000000 00000000 0a6a1000
[  163.901692]         00001000 8007caac 8721ae4c 8079c7c7 807a0000 00000001 87233c20 5603b70d
[  163.910048]         00000000 00000000 80799ca0 00010000 00000000 00000000 00000007 00000000
[  163.918403]         0000325e 807a0000 0000325d 00000000 00000000 807c0000 00000000 00000000
[  163.926759]         00000000 0a6a1000 00001000 00000535 00000002 00000000 00000000 80900000
[  163.935115]         ...
[  163.937554] Call Trace:
[  163.940004] [<80011584>] show_stack+0x58/0x100
[  163.944457] [<805e8df4>] dump_stack+0xe4/0x120
[  163.948878] [<80411298>] ubi_io_read+0x248/0x330
[  163.953491] [<8040eda4>] ubi_eba_read_leb+0x2f0/0x450
[  163.958540] [<8040f010>] ubi_eba_read_leb_sg+0x10c/0x18c
[  163.963849] [<8040d808>] ubi_leb_read_sg+0x88/0x100
[  163.968725] [<8041a314>] ubiblock_do_work+0xcc/0x130
[  163.973696] [<8004d290>] process_one_work+0x2f0/0x4e0
[  163.978733] [<8004d8a4>] worker_thread+0x424/0x704
[  163.983536] [<80053c68>] kthread+0x168/0x17c
[  163.987799] [<8000b598>] ret_from_kernel_thread+0x14/0x1c
[  163.993588] print_req_error: I/O error, dev ubiblock0_0, sector 980
[  164.008430] SQUASHFS error: squashfs_read_data failed to read block 0x6a672
[  164.014147] net wl000: loading /lib/firmware/iNIC/RT3883/iNIC_ap.bin failed with error -5
[  164.022241] net wl000: Direct firmware load for iNIC/RT3883/iNIC_ap.bin failed with error -5
[  164.030648] net wl000: Falling back to user helper
[  164.235082] net wl000: Fail request file iNIC/RT3883/iNIC_ap.bin
[  164.239806] --> Error opening iNIC/RT3883/iNIC_ap.bin
[  164.244767] Firmware path iNIC/RT3883/iNIC_ap.bin
[  164.249443] Profile[0] path iNIC/RT3883/iNIC_ap.dat, read path iNIC/RT3883/iNIC_ap.dat
[  164.257372] EEPROM[0] path iNIC/RT3883/iNIC_e2p.bin, read path iNIC/RT3883/iNIC_e2p.bin
[  164.265374] Profile[1] path iNIC/RT3883/iNIC_ap1.dat, read path iNIC/RT3883/iNIC_ap1.dat
[  164.273474] EEPROM[1] path iNIC/RT3883/iNIC_e2p1.bin, read path iNIC/RT3883/iNIC_e2p1.bin
[  164.281644] Request file: iNIC/RT3883/iNIC_ap.bin
[  164.379920] __nand_correct_data: uncorrectable ECC error
[  164.383779] __nand_correct_data: uncorrectable ECC error
[  164.389084] __nand_correct_data: uncorrectable ECC error
[  164.394393] __nand_correct_data: uncorrectable ECC error
[  164.399702] __nand_correct_data: uncorrectable ECC error
[  164.405012] __nand_correct_data: uncorrectable ECC error
...
[  164.729036] __nand_correct_data: uncorrectable ECC error
[  164.734345] __nand_correct_data: uncorrectable ECC error
[  164.739654] __nand_correct_data: uncorrectable ECC error
[  164.744964] __nand_correct_data: uncorrectable ECC error
[  164.750273] __nand_correct_data: uncorrectable ECC error
[  164.755583] __nand_correct_data: uncorrectable ECC error
[  164.760892] __nand_correct_data: uncorrectable ECC error
[  164.770179] ubi0 error: ubi_io_read: error -77 (ECC error) while reading 28672 bytes from PEB 1333:4096, read 28672 bytes
[  164.779755] CPU: 0 PID: 67 Comm: kworker/0:1 Not tainted 4.14.97 #0
[  164.785971] Workqueue: ubiblock0_0 ubiblock_do_work
[  164.790825] Stack : 8070da7c 87233c5c 807a0000 87228000 8070db10 00000000 00000000 0a6a1000
[  164.799179]         00001000 8007caac 8721ae4c 8079c7c7 807a0000 00000001 87233c20 5603b70d
[  164.807534]         00000000 00000000 80799ca0 00010000 00000000 00000000 00000007 00000000
[  164.815890]         000032c4 807a0000 000032c3 00000000 00000000 807c0000 00000000 00000000
[  164.824246]         00000000 0a6a1000 00001000 00000535 00000002 00000000 00000000 80900000
[  164.832602]         ...
[  164.835041] Call Trace:
[  164.837491] [<80011584>] show_stack+0x58/0x100
[  164.841943] [<805e8df4>] dump_stack+0xe4/0x120
[  164.846365] [<80411298>] ubi_io_read+0x248/0x330
[  164.850978] [<8040eda4>] ubi_eba_read_leb+0x2f0/0x450
[  164.856026] [<8040f010>] ubi_eba_read_leb_sg+0x10c/0x18c
[  164.861336] [<8040d808>] ubi_leb_read_sg+0x88/0x100
[  164.866211] [<8041a314>] ubiblock_do_work+0xcc/0x130
[  164.871182] [<8004d290>] process_one_work+0x2f0/0x4e0
[  164.876219] [<8004d8a4>] worker_thread+0x424/0x704
[  164.881022] [<80053c68>] kthread+0x168/0x17c
[  164.885286] [<8000b598>] ret_from_kernel_thread+0x14/0x1c
[  164.890791] print_req_error: I/O error, dev ubiblock0_0, sector 980
[  164.909000] SQUASHFS error: squashfs_read_data failed to read block 0x6a672
[  164.925910] __nand_correct_data: uncorrectable ECC error
[  164.929772] __nand_correct_data: uncorrectable ECC error
[  164.935077] __nand_correct_data: uncorrectable ECC error
[  164.940386] __nand_correct_data: uncorrectable ECC error
[  164.945696] __nand_correct_data: uncorrectable ECC error
[  164.951005] __nand_correct_data: uncorrectable ECC error
[  164.956314] __nand_correct_data: uncorrectable ECC error
[  164.961624] __nand_correct_data: uncorrectable ECC error
[  164.967320] __nand_correct_data: uncorrectable ECC error
...

#99

Update on the soak testing: With /etc/init.d/rt3883 and /etc/init.d/dsl_control disabled, the box has been sitting idle for ~70 hours now without any reboots. I would say that the box is stable in this setup.

Preliminary conclusions, as far as I'm qualified to draw them:

  • It seems very obvious that the RT3883 wifi driver is very much broken, to the point where it not only reboots the system but actually breaks the installation. This happens without the wifi driver loaded, too. See below.
  • The unsolicited reboot after 30 hours quite neatly fits the "24 to 48 hours" timeframe that is mentioned with the HH5A's "DSL watchdog". But that's hard to prove or disprove from a single occurrence. More testing is required.
  • lcd4linux is spamming dmesg and the logfile quite a bit. Amongst the errors that are related to not being able to ping google (which are of course due to no net connectivity), it is constantly complaining:
    fb_ili9341_eb904 13000000.display: fbtft_update_display: start_line=239 is larger than end_line=0. Shouldn't happen, will do full display update

I'm starting a new test round now, again with dsl enabled, to prove or disprove the watchdog timer. (I manually switch off the LED on the shell, so the red LED is a quick indicator that the box has rebooted.)

Edit: Less than 8 hours later I arrived home to find the Easybox sitting on the "Your Easybox couldn't be started" red screen of death. So something effectively killed the system again, and this time it wasn't the wifi driver. :frowning:


#100

Hi there i create a patch on 09.02.2019 with this script create-eb904x-patches.sh
based on the latest commit at this time 674668605210442b5347d3e7ae8771cd5eedb368

I add these extra parameter to kernel config before compiling:

# add this to the kernel config or the buildprocess stops, because you must enter thees parameter manuelle
# need by fbtft display
cat << EOF >> ./target/linux/lantiq/xrx200/config-4.14
CONFIG_VGA_CONSOLE=y 
CONFIG_VGACON_SOFT_SCROLLBACK=n 
CONFIG_DUMMY_CONSOLE_COLUMNS=80
CONFIG_DUMMY_CONSOLE_ROWS=25
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
EOF
	
# adding theese kernel config for starting the image from usbstick
# not nessasary
cat << EOF >> ./target/linux/lantiq/xrx200/config-4.14
CONFIG_SCSI_MOD=y
CONFIG_SCSI=y
CONFIG_BLK_DEV_SD=y
CONFIG_USB_STORAGE=y
CONFIG_USB_DWC2=y
CONFIG_EXT2_FS=y
CONFIG_EXT3_FS=y
CONFIG_EXT4_FS=y
CONFIG_JBD2=y
CONFIG_FS_MBCACHE=y
CONFIG_F2FS_FS=y
CONFIG_CRYPTO_CRC32C=y
CONFIG_CRYPTO_CRC32=y
CONFIG_EXT2_FS_XATTR=n
CONFIG_EXT3_FS_POSIX_ACL=n
CONFIG_EXT3_FS_SECURITY=n
CONFIG_EXT4_FS_POSIX_ACL=n
CONFIG_EXT4_FS_SECURITY=n
CONFIG_EXT4_ENCRYPTION=n
CONFIG_EXT4_DEBUG=n
CONFIG_JBD2_DEBUG=n
CONFIG_F2FS_STAT_FS=y
CONFIG_F2FS_FS_XATTR=y
CONFIG_F2FS_FS_POSIX_ACL=n
CONFIG_F2FS_FS_SECURITY=n
CONFIG_F2FS_CHECK_FS=n
CONFIG_F2FS_FS_ENCRYPTION=n
CONFIG_F2FS_FAULT_INJECTION=n
EOF

and i use this git https://github.com/Plonkbong/eb904x-feedfix.git for the display driver because i build the image via several steps:

  1. downloading all packages
  2. compile an minimal openwrt (using only the base) with this eb904x-config.seed
  3. build additional packages LCD, Keypad and Wifi via SDK using all feeds.
  4. create an image via imagebuilder

It runs stable since some hours the only problems are:
Keypad are not working:

root@OpenWrt:/# dmesg | grep -i key
[   13.366678] eb904_keypad 0-0014: Error while parsing <eb904,ctrl-rst-gpio> <-517>!
[   13.463182] eb904_keypad 0-0014: Error while parsing <eb904,ctrl-rst-gpio> <-517>!

root@OpenWrt:/# rmmod eb904_keypad
root@OpenWrt:/# rmmod matrix_keymap
root@OpenWrt:/# insmod eb904_keypad
[ 2005.381173] eb904_keypad: Unknown symbol matrix_keypad_build_keymap (err 0)
[ 2005.387090] eb904_keypad: Unknown symbol matrix_keypad_parse_properties (err 0)
failed to insert /lib/modules/4.14.98/eb904_keypad.ko
root@OpenWrt:/# insmod matrix_keymap
Failed to find matrix_keymap. Maybe it is a built in module ?

LCD working but Backlight do not turn off automatic.

Telefon-POTS-FXS Working, but only on one Port (U) i guess missconfigured or mechanical defect.

DSL: not tested

My Router run stable at the moment can it happen tha your router are unstable because NAND (to often overide ?) or elekrical mechanical problems ?
(see my post before) i solved this with reinstallation of the same image


#101

This particular device has been flashed less than a dozen times. It has been sitting doing nothing and still rebooted into a broken state after a few hours. I'm not quite sure what you mean by "electrical mechanical problems", but it didn't have a lightning strike or a car accident.