Open numericOverflow opened 2 years ago
Who knows. I'll apply a fix and something more to my repo, give me few days to finish other stuff first
The repo has no XTERM environment variable in the profile, so it must be added by busybox on its own I guess?
@dewi-ny-je - I fixed it by adding a line to the bottom of the generic user profile.
Would that work?
@numericOverflow Tested, it works. I fixed it in my fork https://github.com/dewi-ny-je/Xiaomi-Dafang-Hacks
However, it could be a mistake by whoever compiled it. https://github.com/EliasKotlyar/Xiaomi-Dafang-Hacks/pull/1693
exact camera hardware: Wyze v2
Click to show startup log & CPU details
``` Contents of dmesg after startup: 0.000000 Initializing cgroup subsys cpu 0.000000 Initializing cgroup subsys cpuacct 0.000000 Linux version 3.10.14 (root@ubuntu) (gcc version 4.7.2 (Ingenic r2.3.3 2016.12) ) #21 PREEMPT Thu Oct 19 11:38:16 CST 2017 0.000000 bootconsole [early0] enabled 0.000000 CPU0 RESET ERROR PC:801CB660 0.000000 [<801cb660>] __delay+0x0/0x10 0.000000 CPU0 revision is: 00d00101 (Ingenic Xburst) 0.000000 FPU revision is: 00b70000 0.000000 cgu_get_rate, parent = 860160000, rate = 0, m = 0, n = 0, reg val = 0x000020ff 0.000000 CCLK:860MHz L2CLK:430Mhz H0CLK:200MHz H2CLK:200Mhz PCLK:100Mhz 0.000000 Determined physical RAM map: 0.000000 memory: 00535000 @ 00010000 (usable) 0.000000 memory: 0003b000 @ 00545000 (usable after init) 0.000000 User-defined physical RAM map: 0.000000 memory: 06800000 @ 00000000 (usable) 0.000000 Zone ranges: 0.000000 Normal [mem 0x00000000-0x067fffff] 0.000000 Movable zone start for each node 0.000000 Early memory node ranges 0.000000 node 0: [mem 0x00000000-0x067fffff] 0.000000 On node 0 totalpages: 26624 0.000000 free_area_init_node: node 0, pgdat 80541cb0, node_mem_map 81000000 0.000000 Normal zone: 208 pages used for memmap 0.000000 Normal zone: 0 pages reserved 0.000000 Normal zone: 26624 pages, LIFO batch:7 0.000000 Primary instruction cache 32kB, 8-way, VIPT, linesize 32 bytes. 0.000000 Primary data cache 32kB, 8-way, VIPT, no aliases, linesize 32 bytes 0.000000 pls check processor_id[0x00d00101],sc_jz not support! 0.000000 MIPS secondary cache 128kB, 8-way, linesize 32 bytes. 0.000000 pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 0.000000 pcpu-alloc: [0] 0 0.000000 Built 1 zonelists in Zone order, mobility grouping off. Total pages: 26416 0.000000 Kernel command line: console=ttyS1,115200n8 mem=104M@0x0 ispmem=8M@0x6800000 rmem=16M@0x7000000 init=/linuxrc rootfstype=squashfs root=/dev/mtdblock2 rw mtdparts=jz_sfc:256k(boot),2048k(kernel),3392k(root),640k(driver),4736k(appfs),2048k(backupk),640k(backupd),2048k(backupa),256k(config),256k(para),-(flag) 0.000000 PID hash table entries: 512 (order: -1, 2048 bytes) 0.000000 Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) 0.000000 Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) 0.000000 Memory: 99300k/106496k available (4024k kernel code, 7196k reserved, 1304k data, 236k init, 0k highmem) 0.000000 SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 0.000000 Preemptible hierarchical RCU implementation. 0.000000 NR_IRQS:418 0.000000 clockevents_config_and_register success. 0.000024 Calibrating delay loop... 858.52 BogoMIPS (lpj=4292608) 0.087754 pid_max: default: 32768 minimum: 301 0.092738 Mount-cache hash table entries: 512 0.097841 Initializing cgroup subsys debug 0.102102 Initializing cgroup subsys freezer 0.109178 regulator-dummy: no parameters 0.113467 NET: Registered protocol family 16 0.135474 bio: create slabthe Xiaomi-Dafang-Hacks commitid (from
git log
) you are experiencing the issue with:I just pulled the main branch as of 2022-05-09 (last commit listed as 0cde105 on Dec 5, 2021)
Description
nano will not work/start, exits immediately after calling the exe:
The nano editor does not start, exits with the above message. FWIW, the
nano --help
command does display the help info correctly (I only pasted partial output here for reference)What did you do to debug the issue
Evidence
See debug section above
After switching the
$TERM
environmental var toxterm-256color
nano opens just fineIs there a reason that
$TERM=xterm
and not$TERM=xterm-256color
? Will this have other repercussions that are undesired?