View Single Post
Old 09-12-2016, 09:31 AM   #19
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
The 5.7.4 version of the firmware was released **before** we started re-using search bar commands. So it isn't likely to be an Amazon reaction to what we where doing.

The two that are reported not working are i.MX6 devices.
The one that is reported as working is an i.MX50 series device.

It might be some change made, either accidentally or on purpose with the change to the newer SoC device.

Try this:
Code:
ssh into the Kindle
dmesg -c
try the new search bar command
dmesg >/mnt/us/dmesg.txt
Then see if the kernel complained about anything.

Note: these i.MX6 models are most likely running a newer version of Busybox ash.
It could be that the newer version is stumbling over something in the script.
knc1 is offline   Reply With Quote