View Single Post
Old 01-14-2016, 01:10 PM   #2
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
Any chance you dd 'ed something to /dev/mmcblk0 rather than /dev/mmcblk0p1 ?
Any such typo in a dd command would have over-written the board ID.

= = = = =

Now this one:
Code:
modprobe: FATAL: Could not load /lib/modules/3.0.35-lab126/modules.dep: No such file or directory
You need to check on.

= = = = =

I assume you have a Linux system (larger than a Kindle) available -
That the system image file you are trying to boot is named: rootfs.img -
Change that name to whatever you are using.

Do:
Code:
sudo mkdir -p /mnt/tmp-p1
sudo mount rootfs.img /mnt/tmp-p1
cd /mnt/tmp-p1/lib/modules/3.0.35-lab126/

Check what files are in there:
ls -la

The .dep file is plain text, see what is in it:
less modules.dep
If it isn't there, or is empty, create one.

There is a way to do a 'make dep' on a tree of modules not in the standard location (handy for not trashing your host system).
You'll have to look the directions for that one up ('man mkdep' would be a good start).

= = = = =

OR, better yet, use a known good rootfs.img file (like from one of your working Kindles).
knc1 is offline   Reply With Quote