Register Guidelines E-Books Today's Posts Search

Go Back   MobileRead Forums > E-Book Readers > Amazon Kindle > Kindle Developer's Corner

Notices

Reply
 
Thread Tools Search this Thread
Old 09-19-2019, 07:24 PM   #16
pazos
cosiñeiro
pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.
 
Posts: 1,406
Karma: 2451781
Join Date: Apr 2014
Device: BQ Cervantes 4
Quote:
Originally Posted by WaseemAlkurdi View Post
When targeting the vexpress board for a mainline U-Boot compile, the compiled U-Boot works flawlessly.
But when targeting any i.MX6 board that has a corresponding QEMU "machine" on mainline, it won't boot. I'm stumped.
Did you try using https://github.com/qemu/qemu/blob/ma.../fsl-imx6ul.c?

Also you didn't specify the calls you're using to build u-boot and to run qemu. A good guide (a bit old): https://elinux.org/Virtual_Development_Board
pazos is offline   Reply With Quote
Old 09-20-2019, 07:58 AM   #17
WaseemAlkurdi
Zealot
WaseemAlkurdi began at the beginning.
 
Posts: 147
Karma: 20
Join Date: Jul 2019
Device: Kindle Touch (K5) Wi-Fi x 2, Kindle (7th Gen, KT2), Paperwhite 3rd Gen
Quote:
Originally Posted by pazos View Post
Did you try using https://github.com/qemu/qemu/blob/ma.../fsl-imx6ul.c?

Also you didn't specify the calls you're using to build u-boot and to run qemu. A good guide (a bit old): https://elinux.org/Virtual_Development_Board
I'm currently building QEMU 4.1.0 again using the file you linked me to above, though it only has one extra line compared to the one I'm using. Who knows? It might just work.
Edit: Didn't work.

For the U-Boot build, I did like a million builds using mainline U-Boot (U-Boot 2019.10-rc3 as of the time of writing). Each time, I would do this:
Code:
CROSS_COMPILE=~/arm-2014.05/bin/arm-none-linux-gnueabi- make ARCH=arm <name_of_defconfig>
CROSS_COMPILE=~/OLDarm-2014.05/bin/arm-none-linux-gnueabi- make ARCH=arm -j8
The list of defconfigs is obtained using this command:
Code:
$ ls ~/Downloads/u-boot-2019.10-rc3/configs/ | grep mx
With mainline, I would get an error about my GCC (the toolchain's) being older than 6.0 and thus unsupported, but after removing the assertion, the build would continue beautifully.
Building mainline for the Versatile and Versatile Express boards works, even when using the older GCC, and U-Boot actually boots, as illustrated in the link you attached.
But not the i.MX6 configs. Every config I tried failed to boot (but compiled successfully)
The only i.MX board which works is the i.MX25 board. But that's still too far from the Kindle, and the Kindle kernels won't boot on this board.
Nor would the Kindle kernels boot on QEMU's i.MX6 boards when I tried booting them without U-Boot.

As for booting in QEMU: I'm using a lot of different variations on this call: (please scroll right to view the whole line)
Code:
$ qemu-system-arm -M {mcimx6ul-evk|sabrelite|mcimx7d-sabre}* -m 512M {-kernel} ~/Downloads/u-boot-2019.10-rc3/{u-boot.bin|u-boot|u-boot.imx|u-boot.img} -monitor stdio {-dtb ~/Downloads/u-boot-2019.10-rc3/u-boot.dtb**} {-append "console=ttymxc0"}
* The bracelets indicate the possible variations I tried. For example, I would try the call with mcimx6ul-evk, and when that didn't work, I would try sabrelite, and so on.
** If generated by the build.

Last edited by WaseemAlkurdi; 09-20-2019 at 08:05 AM.
WaseemAlkurdi is offline   Reply With Quote
Advert
Old 09-20-2019, 10:01 AM   #18
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
Quote:
Originally Posted by WaseemAlkurdi View Post
. . . . .

For the U-Boot build, I did like a million builds using mainline U-Boot (U-Boot 2019.10-rc3 as of the time of writing).

. . . . .
Say what???
Why are you not using the Amazon/Lab126 provided source of U-Boot?

You can't (and shouldn't) assume that a vendor provided, modified, source package will build or work the same as the mainline source.
knc1 is offline   Reply With Quote
Old 09-20-2019, 10:13 AM   #19
WaseemAlkurdi
Zealot
WaseemAlkurdi began at the beginning.
 
Posts: 147
Karma: 20
Join Date: Jul 2019
Device: Kindle Touch (K5) Wi-Fi x 2, Kindle (7th Gen, KT2), Paperwhite 3rd Gen
Quote:
Originally Posted by knc1 View Post
Say what???
Why are you not using the Amazon/Lab126 provided source of U-Boot?

You can't (and shouldn't) assume that a vendor provided, modified, source package will build or work the same as the mainline source.
I'm only using mainline U-Boot temporarily, as a second resort and something to compare Lab126 U-Boot with, until I can get any U-Boot at all for i.MX6 to work in QEMU, since the Amazon/Lab126 U-Boot won't build for any target except imx60_wario.
When I can get any U-Boot at all to boot in QEMU as i.MX6, I'm sticking permanently to Lab126 sources because they have the Kindle-specific modifications. (like idme variables and the like, which is, after all, why I'm sticking to their sh*tty ten-year-old tree).

Note that I have both trees side-by-side, and I'm ready to modify and build whichever tree you want me to.

EDIT: This is what happens when I try to build Amazon's U-Boot for versatile as to test it in QEMU ...
Code:
# time CROSS_COMPILE=/root/arm-2014.05/bin/arm-linux-gnueabi- make    
for dir in tools examples/standalone examples/api ; do make -C $dir _depend ; done
make[1]: Entering directory '/root/uboot_2009.08/tools'
make[1]: Nothing to be done for '_depend'.
make[1]: Leaving directory '/root/uboot_2009.08/tools'
make[1]: Entering directory '/root/uboot_2009.08/examples/standalone'
make[1]: Nothing to be done for '_depend'.
make[1]: Leaving directory '/root/uboot_2009.08/examples/standalone'
make[1]: Entering directory '/root/uboot_2009.08/examples/api'
make[1]: Nothing to be done for '_depend'.
make[1]: Leaving directory '/root/uboot_2009.08/examples/api'
make -C tools all
make[1]: Entering directory '/root/uboot_2009.08/tools'
make[1]: *** No rule to make target '/root/uboot_2009.08/include/asm/arch/mx6.h', needed by 'env_embedded.o'.  Stop.
make[1]: Leaving directory '/root/uboot_2009.08/tools'
make: *** [Makefile:357: tools] Error 2
... and for sabrelite:
Code:
make[1]: Entering directory '/root/uboot_2009.08/drivers/mmc'
/root/arm-2014.05/bin/arm-linux-gnueabi-gcc  -g  -Os   -fno-strict-aliasing -fno-common -ffixed-r8 -msoft-float   -D__KERNEL__ -DTEXT_BASE=0x27800000 -I/root/uboot_2009.08/include  -fno-builtin -ffreestanding -nostdinc -isystem /root/arm-2014.05/bin/../lib/gcc/arm-linux-gnueabi/4.9.4/include -pipe  -DCONFIG_ARM -D__ARM__ -marm  -mabi=aapcs-linux -mno-thumb-interwork -march=armv7-a -Wall -Wstrict-prototypes -fno-stack-protector   -o imx_esdhc.o imx_esdhc.c -c
imx_esdhc.c:44:25: error: 'CONFIG_SYS_FSL_ESDHC_NUM' undeclared here (not in a function)
 static struct mmc g_mmc[CONFIG_SYS_FSL_ESDHC_NUM];
                         ^
imx_esdhc.c:44:19: warning: 'g_mmc' defined but not used [-Wunused-variable]
 static struct mmc g_mmc[CONFIG_SYS_FSL_ESDHC_NUM];
                   ^
make[1]: *** [/root/uboot_2009.08/config.mk:218: imx_esdhc.o] Error 1
make[1]: Leaving directory '/root/uboot_2009.08/drivers/mmc'
make: *** [Makefile:351: drivers/mmc/libmmc.a] Error 2
TL;DR : Lab126's tree is really useless until I get QEMU's sabrelite (or more likely, imx60ul-evk) boards to accept Kindle images. But testing using mainline U-Boot is a stepping stone.

Last edited by WaseemAlkurdi; 09-20-2019 at 10:21 AM.
WaseemAlkurdi is offline   Reply With Quote
Old 09-22-2019, 03:38 PM   #20
WaseemAlkurdi
Zealot
WaseemAlkurdi began at the beginning.
 
Posts: 147
Karma: 20
Join Date: Jul 2019
Device: Kindle Touch (K5) Wi-Fi x 2, Kindle (7th Gen, KT2), Paperwhite 3rd Gen
The poster in this StackExchange thread is trying to do exactly what we are doing here ... only they are doing it for the reMarkable Tablet instead. I'm following along.
It seems like a good idea to use a generic sabrelite kernel + Kindle rootfs kernel ... or is it? Has the Kindle's kernel tree deviated a lot from mainstream? In other words, do you think it's a good idea to try this?

Edit: Surprise surprise! The U-Boot image which the poster has booted successfully in their QEMU instance didn't boot in mine. But is it really an issue with my compilation? I don't think so because even Ubuntu's packaged QEMU didn't boot that image.

Last edited by WaseemAlkurdi; 09-22-2019 at 03:42 PM.
WaseemAlkurdi is offline   Reply With Quote
Advert
Old 10-01-2019, 10:43 AM   #21
smindux
Junior Member
smindux began at the beginning.
 
Posts: 4
Karma: 14
Join Date: Oct 2019
Device: none
I have been trying the same for a few weeks and figured that u-boot is dead-end.
The last example you provided booted though (Thanks)
Code:
% qemu-system-arm --version
QEMU emulator version 4.0.0
Copyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers

% qemu-system-arm -M sabrelite -bios "files/u-boot.imx" -kernel "zImage" -dtb "zero-gravitas.dtb" -serial mon:stdio -display none -append "console=ttymxc0 loglevel=8 bootmem-debug"
               

'[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.1.28-zero-gravitas-01866-ge0b823726ea4-dirty (sandsmark@neruval) (gcc version 5.3.0 (GCC) ) #82 Thu Apr 27 14:27:47 CEST 2017
[    0.000000] CPU: ARMv7 Processor [410fc090] revision 0 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
[    0.000000] Machine model: reMarkable Prototype 1
I managed to compile and boot the linux kernel from lab126 without u-boot.
Code:
% qemu-system-arm -M sabrelite -kernel "zImage" -dtb "imx6sll-rex.dtb"  -serial mon:stdio -display none -append "console=ttymxc0 loglevel=8 bootmem-debug"  
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.1.15-lab126 (root@drama) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-16) (GCC) ) #1 SMP PREEMPT Tue Oct 1 17:03:51 EEST 2019
[    0.000000] CPU: ARMv7 Processor [410fc090] revision 0 (ARMv7), cr=10c53c7d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
[    0.000000] Machine model: Lab126 i.MX6SLL Board
Here are my steps if you are willing to reproduce (Host is CentOS, Cross Compilation TC is what the host provided)
Code:
# wget https://kindledownloads.s3.amazonaws.com/Kindle_src_5.12.1_3552180044.tar.gz
tar xvf Kindle_src_5.12.1_3552180044.tar.gz 
# cd gplrelease/
# tar xzvf linux-4.1.15.tar.gz 
# export ARCH=arm
# export CROSS_COMPILE=arm-linux-gnu-
# make imx_rex_defconfig
# make -j2 all
# cp ./arch/arm/boot/zImage /root/drama/
# cp ./arch/arm/boot/dts/imx6sll-rex.dtb /root/drama/
Good luck, Man.
smindux is offline   Reply With Quote
Old 10-01-2019, 02:25 PM   #22
WaseemAlkurdi
Zealot
WaseemAlkurdi began at the beginning.
 
Posts: 147
Karma: 20
Join Date: Jul 2019
Device: Kindle Touch (K5) Wi-Fi x 2, Kindle (7th Gen, KT2), Paperwhite 3rd Gen
Quote:
Originally Posted by smindux View Post
I have been trying the same for a few weeks and figured that u-boot is dead-end.
The last example you provided booted though (Thanks)
Code:
% qemu-system-arm --version
QEMU emulator version 4.0.0
Copyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers

% qemu-system-arm -M sabrelite -bios "files/u-boot.imx" -kernel "zImage" -dtb "zero-gravitas.dtb" -serial mon:stdio -display none -append "console=ttymxc0 loglevel=8 bootmem-debug"
               

'[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.1.28-zero-gravitas-01866-ge0b823726ea4-dirty (sandsmark@neruval) (gcc version 5.3.0 (GCC) ) #82 Thu Apr 27 14:27:47 CEST 2017
[    0.000000] CPU: ARMv7 Processor [410fc090] revision 0 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
[    0.000000] Machine model: reMarkable Prototype 1
I managed to compile and boot the linux kernel from lab126 without u-boot.
Code:
% qemu-system-arm -M sabrelite -kernel "zImage" -dtb "imx6sll-rex.dtb"  -serial mon:stdio -display none -append "console=ttymxc0 loglevel=8 bootmem-debug"  
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.1.15-lab126 (root@drama) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-16) (GCC) ) #1 SMP PREEMPT Tue Oct 1 17:03:51 EEST 2019
[    0.000000] CPU: ARMv7 Processor [410fc090] revision 0 (ARMv7), cr=10c53c7d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
[    0.000000] Machine model: Lab126 i.MX6SLL Board
Here are my steps if you are willing to reproduce (Host is CentOS, Cross Compilation TC is what the host provided)
Code:
# wget https://kindledownloads.s3.amazonaws.com/Kindle_src_5.12.1_3552180044.tar.gz
tar xvf Kindle_src_5.12.1_3552180044.tar.gz 
# cd gplrelease/
# tar xzvf linux-4.1.15.tar.gz 
# export ARCH=arm
# export CROSS_COMPILE=arm-linux-gnu-
# make imx_rex_defconfig
# make -j2 all
# cp ./arch/arm/boot/zImage /root/drama/
# cp ./arch/arm/boot/dts/imx6sll-rex.dtb /root/drama/
Good luck, Man.
Thanks for the reply! It's a great breakthrough!

I'm going to reproduce your steps. You seem to have used the rex board instead of wario, which I'm currently using. Perhaps that might explain something?

As for U-Boot being a dead end, why have you come to that conclusion? In your example, didn't U-Boot boot at all? As far as I know, if there is a problem in the file you supplied with -bios, then the boot sequence should have stopped, instead of continuing. It doesn't really "skip" U-Boot just like that.

Have you tried compiling mainline U-Boot (instead of Lab126 U-Boot) to see whether it boots under your setup of (host, QEMU version, cross-compiler toolchain)? Under my setup, the only i.MX board that boots in U-Boot is the imx25-pdk, and that happened with both mainline and Lab126 U-Boot.

Edit: Have some karma! :-)

Edit 2: If we bring up the Kindle OS without relying on U-Boot, then it would be good, but I feel that the presence of U-Boot is very important, because of the implementation of idme variables, which is necessary to boot without modifying the userland to skip the missing variables, and to provide a more complete emulation package overall.

Edit 3 - Breaking news: I have booted the prebuilt kernel from the StackExchange thread above! The magic is in the kernel commandline.
This explains why U-Boot didn't work ... it's because using -append with the magical option that fixes the kernel requires passing -kernel as well ...

Edit 4: The magical option is console=ttymxc0!

Last edited by WaseemAlkurdi; 10-01-2019 at 05:53 PM.
WaseemAlkurdi is offline   Reply With Quote
Old 10-02-2019, 03:30 AM   #23
smindux
Junior Member
smindux began at the beginning.
 
Posts: 4
Karma: 14
Join Date: Oct 2019
Device: none
Quote:
I'm going to reproduce your steps. You seem to have used the rex board instead of wario, which I'm currently using. Perhaps that might explain something?
This is why I chose this config (this is in kernel extraction directory)
Code:
[root@drama gplrelease]# grep -Ri lab126 arch/arm/configs/
arch/arm/configs/imx_rex_defconfig:CONFIG_LOCALVERSION="-lab126"
arch/arm/configs/imx_rex_defconfig:CONFIG_LAB126=y
arch/arm/configs/imx_rex_defconfig:CONFIG_CPU_FREQ_OVERRIDE_LAB126=y
arch/arm/configs/imx_rex_android_defconfig:CONFIG_LOCALVERSION="-lab126"
arch/arm/configs/imx_rex_android_defconfig:CONFIG_LAB126=y
[root@drama gplrelease]#
Probably it is good idea to do the same with u-boot that comes with kindle source package. Haven't tried this one though.
Code:
[root@drama uboot]# grep -Ri lab126 configs/
configs/mx6sll_rex_defconfig:CONFIG_SYS_EXTRA_OPTIONS="IMX_CONFIG=board/lab126/mx6sll_rex/imximage.cfg,ANDROID_SUPPORT,CMD_COREMARK"
[root@drama uboot]#
Quote:
As for U-Boot being a dead end, why have you come to that conclusion? In your example, didn't U-Boot boot at all? As far as I know, if there is a problem in the file you supplied with -bios, then the boot sequence should have stopped, instead of continuing. It doesn't really "skip" U-Boot just like that.

Have you tried compiling mainline U-Boot (instead of Lab126 U-Boot) to see whether it boots under your setup of (host, QEMU version, cross-compiler toolchain)? Under my setup, the only i.MX board that boots in U-Boot is the imx25-pdk, and that happened with both mainline and Lab126 U-Boot.
Everything I tried with u-boot didn't ... you know boot. Except the binaries provided by the StackExchange thread. So I figured I am done compiling it. I think DTB file should suffice for helping the kernel find all devices which actually might be a problem, because QEMU probably can't emulate them all.

So I am kissing u-boot goodbye and trying to attach the rootfs.img if you don't beat me to it.

Quote:
Edit 2: If we bring up the Kindle OS without relying on U-Boot, then it would be good, but I feel that the presence of U-Boot is very important, because of the implementation of idme variables, which is necessary to boot without modifying the userland to skip the missing variables, and to provide a more complete emulation package overall.
I had no idea about this idme thing ... looked it up and it makes sense what are you saying.
smindux is offline   Reply With Quote
Old 10-07-2019, 06:58 AM   #24
WaseemAlkurdi
Zealot
WaseemAlkurdi began at the beginning.
 
Posts: 147
Karma: 20
Join Date: Jul 2019
Device: Kindle Touch (K5) Wi-Fi x 2, Kindle (7th Gen, KT2), Paperwhite 3rd Gen
Quote:
Originally Posted by smindux View Post
This is why I chose this config (this is in kernel extraction directory)

Code:
[root@drama gplrelease]# grep -Ri lab126 arch/arm/configs/

arch/arm/configs/imx_rex_defconfig:CONFIG_LOCALVERSION="-lab126"

arch/arm/configs/imx_rex_defconfig:CONFIG_LAB126=y

arch/arm/configs/imx_rex_defconfig:CONFIG_CPU_FREQ_OVERRIDE_LAB126=y

arch/arm/configs/imx_rex_android_defconfig:CONFIG_LOCALVERSION="-lab126"

arch/arm/configs/imx_rex_android_defconfig:CONFIG_LAB126=y

[root@drama gplrelease]#
Probably it is good idea to do the same with u-boot that comes with kindle source package. Haven't tried this one though.

Code:
[root@drama uboot]# grep -Ri lab126 configs/

configs/mx6sll_rex_defconfig:CONFIG_SYS_EXTRA_OPTIONS="IMX_CONFIG=board/lab126/mx6sll_rex/imximage.cfg,ANDROID_SUPPORT,CMD_COREMARK"

[root@drama uboot]#




Everything I tried with u-boot didn't ... you know boot. Except the binaries provided by the StackExchange thread. So I figured I am done compiling it. I think DTB file should suffice for helping the kernel find all devices which actually might be a problem, because QEMU probably can't emulate them all.



So I am kissing u-boot goodbye and trying to attach the rootfs.img if you don't beat me to it.





I had no idea about this idme thing ... looked it up and it makes sense what are you saying.
Sorry for the late reply ... I've been busy, and not a lot of free time is available.
I managed to run the i.MX kernel in QEMU ARM too. But still no word on U-Boot.
I've contacted the QEMU mailing list, and they provided me with a possible patch, but how to apply it is a mystery (it's got ARM assembler code).
And the booted kernel seems to be panicking very early on for some reason.
Anyhow, U-Boot seems to be very far away unless QEMU is fixed up. I might post it up here if somebody's interested.

Last edited by WaseemAlkurdi; 10-07-2019 at 09:06 AM.
WaseemAlkurdi is offline   Reply With Quote
Old 10-07-2019, 07:05 AM   #25
WaseemAlkurdi
Zealot
WaseemAlkurdi began at the beginning.
 
Posts: 147
Karma: 20
Join Date: Jul 2019
Device: Kindle Touch (K5) Wi-Fi x 2, Kindle (7th Gen, KT2), Paperwhite 3rd Gen
@smindux
https://lists.nongnu.org/archive/htm.../msg00837.html
https://lists.nongnu.org/archive/htm.../msg00923.html
These are the replies I got. I did the patches, but it seems I need to know ARM assembler to continue.

Last edited by WaseemAlkurdi; 10-07-2019 at 09:06 AM.
WaseemAlkurdi is offline   Reply With Quote
Old 10-09-2019, 05:12 AM   #26
smindux
Junior Member
smindux began at the beginning.
 
Posts: 4
Karma: 14
Join Date: Oct 2019
Device: none
Meanwhile I managed to build u-boot that is provided by lab126 as per instructions in this previous post.
However as you might expect I could not boot it.

The debugging example Philippe provided is great and very enlightening, yet I get very different output.
Quote:
IN:
0x80404938: 00000000 andeq r0, r0, r0

R00=00000000 R01=00000000 R02=00000000 R03=00000000
R04=00000000 R05=00000000 R06=00000000 R07=00000000
R08=00000000 R09=00000000 R10=00000000 R11=00000000
R12=00000000 R13=00000000 R14=00000000 R15=80404938
PSR=400001d3 -Z-- A S svc32
Which leads me to the conclusion that I am making some dumb mistake/decision somewhere along the way.
In addition to what Philippe suggested for enabling debugging on QEMU I enabled debugging in u-boot as well
Code:
CFLAGS+= -DCONFIG_LOG -DDEBUG -DCONFIG_LOGLEVEL=8 -DCONFIG_LOG_CONSOLE -DCONFIG_MAX_LOG_LEVEL=8
And I get utter silence ...

Next step is either someone points out my stupidity or I attach gdb to QEMU and try my chances ... not very optimistic about this last one.

As far as I understood the topic about idme - it is fluid enough to be able to set/modify it after kernel boot.

Introductory ARM Assembly if you want to dive.
smindux is offline   Reply With Quote
Old 10-09-2019, 08:17 AM   #27
WaseemAlkurdi
Zealot
WaseemAlkurdi began at the beginning.
 
Posts: 147
Karma: 20
Join Date: Jul 2019
Device: Kindle Touch (K5) Wi-Fi x 2, Kindle (7th Gen, KT2), Paperwhite 3rd Gen
Quote:
And I get utter silence ...

Next step is either someone points out my stupidity or I attach gdb to QEMU and try my chances ... not very optimistic about this last one.
Are you sure you enabled debugging properly?
Phillippes's post said nothing about CFLAGS, instead using patches to imx_cc6.c among others.

Sent from my Pixel XL using Tapatalk
WaseemAlkurdi is offline   Reply With Quote
Old 10-09-2019, 10:37 AM   #28
smindux
Junior Member
smindux began at the beginning.
 
Posts: 4
Karma: 14
Join Date: Oct 2019
Device: none
Quote:
Originally Posted by WaseemAlkurdi View Post
Are you sure you enabled debugging properly?
Phillippes's post said nothing about CFLAGS, instead using patches to imx_cc6.c among others.
Quite. He explains enabling debugging for QEMU and it is giving me some output ... not very helpful though.
CFLAGS is for enabling u-boot debugging and LOGLEVEL=8 should be quite verbose as per documentation.

Maybe trying this setup for i386 just for verification is sound idea, but this is an exercise for another day.
smindux is offline   Reply With Quote
Old 10-13-2019, 08:30 AM   #29
WaseemAlkurdi
Zealot
WaseemAlkurdi began at the beginning.
 
Posts: 147
Karma: 20
Join Date: Jul 2019
Device: Kindle Touch (K5) Wi-Fi x 2, Kindle (7th Gen, KT2), Paperwhite 3rd Gen
Quote:
Originally Posted by smindux View Post
Quite. He explains enabling debugging for QEMU and it is giving me some output ... not very helpful though.

CFLAGS is for enabling u-boot debugging and LOGLEVEL=8 should be quite verbose as per documentation.



Maybe trying this setup for i386 just for verification is sound idea, but this is an exercise for another day.
On the Kernel side, it's booting, but giving an immediate kernel panic, so I can't attach that rootfs.
I'll post the panic text and debugging attempt later today.
WaseemAlkurdi is offline   Reply With Quote
Old 10-19-2019, 04:42 AM   #30
WaseemAlkurdi
Zealot
WaseemAlkurdi began at the beginning.
 
Posts: 147
Karma: 20
Join Date: Jul 2019
Device: Kindle Touch (K5) Wi-Fi x 2, Kindle (7th Gen, KT2), Paperwhite 3rd Gen
Quote:
Originally Posted by smindux View Post
Quite. He explains enabling debugging for QEMU and it is giving me some output ... not very helpful though.
CFLAGS is for enabling u-boot debugging and LOGLEVEL=8 should be quite verbose as per documentation.

Maybe trying this setup for i386 just for verification is sound idea, but this is an exercise for another day.
Hi again! I've been really busy, and finding time to crunch keys is getting quite difficult.
This is dmesg from sabrelite with kernel version 4.1.15 (Kindle tree):
Code:
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.1.15-lab126 (waseem@my-awesome-slabtop) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-29) ) #1 SMP PREEMPT Fri Oct 11 02:01:27 EEST 2019
[    0.000000] CPU: ARMv7 Processor [410fc090] revision 0 (ARMv7), cr=10c53c7d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
[    0.000000] Machine model: Lab126 i.MX6SLL Board
[    0.000000] #### Error!! BIOS area is not in a memory region!!
[    0.000000] log_goal_location: 0x9be00000
[    0.000000] Unable to change over to statically positioned printk buffer!
[    0.000000] Printk log placed at 0x00000000
[    0.000000] Memory policy: Data cache writeback
[    0.000000] CPU: All CPU(s) started in SVC mode.
[    0.000000] PERCPU: Embedded 12 pages/cpu @9fbd6000 s17472 r8192 d23488 u49152
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048
[    0.000000] Kernel command line: console=ttymxc0 root=/dev/mmcblk0p1
[    0.000000] log_buf_len: 262144 bytes
[    0.000000] early log buf free: 260364(99%)
[    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Memory: 506520K/524288K available (8196K kernel code, 550K rwdata, 3064K rodata, 368K init, 574K bss, 17768K reserved, 0K cma-reserved)
[    0.000000] Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    vmalloc : 0xa0800000 - 0xff000000   (1512 MB)
    lowmem  : 0x80000000 - 0xa0000000   ( 512 MB)
    modules : 0x7f000000 - 0x80000000   (  16 MB)
      .text : 0x80008000 - 0x80b0739c   (11261 kB)
      .init : 0x80b08000 - 0x80b64000   ( 368 kB)
      .data : 0x80b64000 - 0x80bedac8   ( 551 kB)
       .bss : 0x80bf0000 - 0x80c7facc   ( 575 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] 	Additional per-CPU info printed with stalls.
[    0.000000] 	RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=1.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] L2C-310 erratum 769419 enabled
[    0.000000] L2C-310 full line of zeros enabled for Cortex-A9
[    0.000000] L2C-310 cache controller enabled, 8 ways, 64 kB
[    0.000000] L2C-310: CACHE_ID 0x00000000, AUX_CTRL 0x00000000
[    0.000000] Division by zero in kernel.
[    0.000000] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.1.15-lab126 #1
[    0.000000] Hardware name: Freescale i.MX6 SoloLite (Device Tree)
[    0.000000] [<80016f64>] (unwind_backtrace) from [<80013730>] (show_stack+0x10/0x14)
[    0.000000] [<80013730>] (show_stack) from [<807c3ac8>] (dump_stack+0x9c/0xdc)
[    0.000000] [<807c3ac8>] (dump_stack) from [<802b60e0>] (Ldiv0_64+0x8/0x18)
[    0.000000] [<802b60e0>] (Ldiv0_64) from [<800233bc>] (clk_pllv3_generic_recalc_rate+0x50/0x58)
[    0.000000] [<800233bc>] (clk_pllv3_generic_recalc_rate) from [<8059ca48>] (clk_register+0x350/0x73c)
[    0.000000] [<8059ca48>] (clk_register) from [<8002376c>] (imx_clk_pllv3+0xf0/0x270)
[    0.000000] [<8002376c>] (imx_clk_pllv3) from [<80b15a38>] (imx6sll_clocks_init+0x330/0x2b14)
[    0.000000] [<80b15a38>] (imx6sll_clocks_init) from [<80b3ab18>] (of_clk_init+0x100/0x190)
[    0.000000] [<80b3ab18>] (of_clk_init) from [<80b0c550>] (time_init+0x28/0x30)
[    0.000000] [<80b0c550>] (time_init) from [<80b08b50>] (start_kernel+0x284/0x3c8)
[    0.000000] [<80b08b50>] (start_kernel) from [<1000807c>] (0x1000807c)
[    0.000000] mxc_clocksource_init 3000000
[    0.000000] Switching to timer-based delay loop, resolution 333ns
[    0.000244] sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 715827882841ns
[    0.000507] clocksource mxc_timer1: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 637086815595 ns
[    0.011742] Console: colour dummy device 80x30
[    0.016149] Calibrating delay loop (skipped), value calculated using timer frequency.. 6.00 BogoMIPS (lpj=30000)
[    0.016304] pid_max: default: 32768 minimum: 301
[    0.017530] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.017580] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.029661] CPU: Testing write buffer coherency: ok
[    0.038498] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.039247] Setting up static identity map for 0x10008280 - 0x100082d8
[    0.098013] Brought up 1 CPUs
[    0.098186] SMP: Total of 1 processors activated (6.00 BogoMIPS).
[    0.098304] CPU: All CPU(s) started in SVC mode.
[    0.117198] devtmpfs: initialized
[    0.141477] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 0
[    0.162446] clocksource jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.170117] pinctrl core: initialized pinctrl subsystem
[    0.192318] NET: Registered protocol family 16
[    0.195938] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.226214] cpuidle: using governor ladder
[    0.246219] cpuidle: using governor menu
[    0.309822] imx_mmdc_probe: failed to enable automatic power saving
[    0.309984] imx-mmdc: probe of 21b0000.mmdc failed with error -16
[    0.318230] failed to find fsl,imx6sl-iomux-gpr regmap
[    0.320124] hw-breakpoint: debug architecture 0x4 unsupported.
[    0.331189] imx6sll-pinctrl 20e0000.iomuxc: initialized IMX pinctrl driver
[    0.416624] SCSI subsystem initialized
[    0.419901] usbcore: registered new interface driver usbfs
[    0.421636] usbcore: registered new interface driver hub
[    0.423149] usbcore: registered new device driver usb
[    0.533186] bd71827 0-004b: bd71827_i2c_probe(): Read BD71827_REG_DEVICE failed!
[    0.538582] bd71827: probe of 0-004b failed with error -110
[    0.540583] i2c i2c-0: IMX I2C adapter registered
[    0.541007] i2c i2c-0: can't use DMA
[    0.544978] i2c i2c-1: IMX I2C adapter registered
[    0.545119] i2c i2c-1: can't use DMA
[    0.548952] i2c i2c-2: IMX I2C adapter registered
[    0.549017] i2c i2c-2: can't use DMA
[    0.549316] Linux video capture interface: v2.00
[    0.549875] pps_core: LinuxPPS API ver. 1 registered
[    0.549916] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.550081] PTP clock support registered
[    0.553110] MIPI CSI2 driver module loaded
[    0.555032] Advanced Linux Sound Architecture Driver Initialized.
[    0.565011] Bluetooth: Core ver 2.20
[    0.565242] NET: Registered protocol family 31
[    0.565277] Bluetooth: HCI device and connection manager initialized
[    0.565467] Bluetooth: HCI socket layer initialized
[    0.565567] Bluetooth: L2CAP socket layer initialized
[    0.565868] Bluetooth: SCO socket layer initialized
[    0.571715] Switched to clocksource mxc_timer1
[    0.582220] cfg80211: World regulatory domain updated:
[    0.582285] cfg80211:  DFS Master region: unset
[    0.582331] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[    0.582494] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[    0.582651] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[    0.582678] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
[    0.582704] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[    0.582751] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[    0.582775] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[    0.582798] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[    0.582820] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
[    0.610284] idme_init:can't find idme node in DT
[    0.613811] NET: Registered protocol family 2
[    0.618543] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[    0.618732] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
[    0.618951] TCP: Hash tables configured (established 4096 bind 4096)
[    0.619412] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    0.619554] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    0.620795] NET: Registered protocol family 1
[    0.623848] RPC: Registered named UNIX socket transport module.
[    0.623915] RPC: Registered udp transport module.
[    0.623945] RPC: Registered tcp transport module.
[    0.623966] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.635223] Bus freq driver module loaded
[    0.638759] futex hash table entries: 256 (order: 2, 16384 bytes)
[    0.658748] VFS: Disk quotas dquot_6.6.0
[    0.659346] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.666427] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.669396] NFS: Registering the id_resolver key type
[    0.670232] Key type id_resolver registered
[    0.670285] Key type id_legacy registered
[    0.671010] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[    0.673661] fuse init (API version 7.23)
[    0.691330] io scheduler noop registered
[    0.691424] io scheduler deadline registered
[    0.691914] io scheduler cfq registered (default)
[    0.697417] MIPI DSI driver module loaded
[    0.697825] MIPI DSI driver module loaded
[    0.704383] imx-sdma 20ec000.sdma: no event needs to be remapped
[    0.705843] imx-sdma 20ec000.sdma: Timeout waiting for CH0 ready
[    0.706187] imx-sdma 20ec000.sdma: loaded firmware 3.3
[    0.715348] imx-sdma 20ec000.sdma: initialized
[    0.716675] regulator-virtuals:virt-buck1 supply buck1 not found, using dummy regulator
[    0.717265] reg-virt-consumer regulator-virtuals:virt-buck1: attached: buck1
[    0.717414] regulator-virtuals:virt-buck2 supply buck2 not found, using dummy regulator
[    0.717603] reg-virt-consumer regulator-virtuals:virt-buck2: attached: buck2
[    0.717725] regulator-virtuals:virt-buck3 supply buck3 not found, using dummy regulator
[    0.717881] reg-virt-consumer regulator-virtuals:virt-buck3: attached: buck3
[    0.717998] regulator-virtuals:virt-buck4 supply buck4 not found, using dummy regulator
[    0.718149] reg-virt-consumer regulator-virtuals:virt-buck4: attached: buck4
[    0.718266] regulator-virtuals:virt-buck5 supply buck5 not found, using dummy regulator
[    0.718497] reg-virt-consumer regulator-virtuals:virt-buck5: attached: buck5
[    0.718619] regulator-virtuals:virt-ldo1 supply ldo1 not found, using dummy regulator
[    0.718773] reg-virt-consumer regulator-virtuals:virt-ldo1: attached: ldo1
[    0.718891] regulator-virtuals:virt-ldo2 supply ldo2 not found, using dummy regulator
[    0.719058] reg-virt-consumer regulator-virtuals:virt-ldo2: attached: ldo2
[    0.719178] regulator-virtuals:virt-ldo3 supply ldo3 not found, using dummy regulator
[    0.719360] reg-virt-consumer regulator-virtuals:virt-ldo3: attached: ldo3
[    0.719483] regulator-virtuals:virt-ldo4 supply ldo4 not found, using dummy regulator
[    0.719638] reg-virt-consumer regulator-virtuals:virt-ldo4: attached: ldo4
[    0.719759] regulator-virtuals:virt-ldo5 supply ldo5 not found, using dummy regulator
[    0.719910] reg-virt-consumer regulator-virtuals:virt-ldo5: attached: ldo5
[    0.720030] regulator-virtuals:virt-ldo6 supply ldo6 not found, using dummy regulator
[    0.720208] reg-virt-consumer regulator-virtuals:virt-ldo6: attached: ldo6
[    0.720344] regulator-virtuals:virt-ldosnvs supply ldosnvs not found, using dummy regulator
[    0.720546] reg-virt-consumer regulator-virtuals:virt-ldosnvs: attached: ldosnvs
[    0.724830] 2020000.serial: ttymxc0 at MMIO 0x2020000 (irq = 18, base_baud = 5000000) is a IMX
[    0.786689] console [ttymxc0] enabled
[    0.792631] 2034000.serial: ttymxc2 at MMIO 0x2034000 (irq = 19, base_baud = 5000000) is a IMX
The kernel panics, because of a division by zero before it can mount the rootfs.
While this is the dmesg from the board versatile from that same kernel tree:
Code:
Booting Linux on physical CPU 0x0
Linux version 4.1.15 (waseem@my-awesome-slabtop) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-29) ) #1 Fri Oct 11 12:43:20 EEST 2019
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00093177
CPU: VIVT data cache, VIVT instruction cache
Machine: ARM-Versatile PB
log_goal_location: 0x9be00000
Unable to change over to statically positioned printk buffer!
Printk log placed at 0x00000000
Memory policy: Data cache writeback
sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
Kernel command line: console=ttyAMA0
log_buf_len: 16384 bytes
early log buf free: 15064(91%)
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 255644K/262144K available (2978K kernel code, 140K rwdata, 796K rodata, 120K init, 120K bss, 6500K reserved, 0K cma-reserved)
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    vmalloc : 0xd0800000 - 0xff000000   ( 744 MB)
    lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .text : 0xc0008000 - 0xc03b7eb4   (3776 kB)
      .init : 0xc03b8000 - 0xc03d6000   ( 120 kB)
      .data : 0xc03d6000 - 0xc03f9020   ( 141 kB)
       .bss : 0xc03f9020 - 0xc04172c0   ( 121 kB)
NR_IRQS:224
VIC @f1140000: id 0x00041190, vendor 0x41
FPGA IRQ chip 0 "SIC" @ f1003000, 13 irqs, parent IRQ: 63
clocksource timer3: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275 ns
Console: colour dummy device 80x30
Calibrating delay loop... 552.96 BogoMIPS (lpj=2764800)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
Setting up static identity map for 0x8400 - 0x8458
VFP support v0.3: implementor 41 architecture 1 part 10 variant 9 rev 0
clocksource jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
Serial: AMBA PL011 UART driver
dev:f1: ttyAMA0 at MMIO 0x101f1000 (irq = 44, base_baud = 0) is a PL011 rev1
console [ttyAMA0] enabled
dev:f2: ttyAMA1 at MMIO 0x101f2000 (irq = 45, base_baud = 0) is a PL011 rev1
dev:f3: ttyAMA2 at MMIO 0x101f3000 (irq = 46, base_baud = 0) is a PL011 rev1
fpga:09: ttyAMA3 at MMIO 0x10009000 (irq = 70, base_baud = 0) is a PL011 rev1
Switched to clocksource timer3
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
NetWinder Floating Point Emulator V0.97 (double precision)
futex hash table entries: 256 (order: -1, 3072 bytes)
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
romfs: ROMFS MTD (C) 2007 Red Hat, Inc.
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
pl061_gpio dev:e4: PL061 GPIO chip @0x101e4000 registered
pl061_gpio dev:e5: PL061 GPIO chip @0x101e5000 registered
pl061_gpio dev:e6: PL061 GPIO chip @0x101e6000 registered
pl061_gpio dev:e7: PL061 GPIO chip @0x101e7000 registered
clcd-pl11x dev:20: PL110 rev0 at 0x10120000
clcd-pl11x dev:20: Versatile hardware, VGA display
Console: switching to colour frame buffer device 80x60
brd: module loaded
physmap platform flash device: 04000000 at 34000000
physmap-flash.0: Found 1 x32 devices at 0x0 in 32-bit bank. Manufacturer ID 0x000000 Chip ID 0x000000
Intel/Sharp Extended Query Table at 0x0031
Using buffer write method
smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre <nico@fluxnic.net>
smc91x smc91x.0 eth0: SMC91C11xFD (rev 1) at d0a58000 IRQ 57
 [nowait]
smc91x smc91x.0 eth0: Ethernet addr: 52:54:00:12:34:56
mousedev: PS/2 mouse device common for all mice
ledtrig-cpu: registered to indicate activity on CPUs
NET: Registered protocol family 17
input: ImExPS/2 Generic Explorer Mouse as /devices/fpga:07/serio1/input/input1
VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
Please append a correct "root=" boot option; here are the available partitions:
0100            4096 ram0  (driver?)
0101            4096 ram1  (driver?)
0102            4096 ram2  (driver?)
0103            4096 ram3  (driver?)
0104            4096 ram4  (driver?)
0105            4096 ram5  (driver?)
0106            4096 ram6  (driver?)
0107            4096 ram7  (driver?)
0108            4096 ram8  (driver?)
0109            4096 ram9  (driver?)
010a            4096 ram10  (driver?)
010b            4096 ram11  (driver?)
010c            4096 ram12  (driver?)
010d            4096 ram13  (driver?)
010e            4096 ram14  (driver?)
010f            4096 ram15  (driver?)
1f00           65536 mtdblock0  (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
CPU: 0 PID: 1 Comm: swapper Not tainted 4.1.15 #1
Hardware name: ARM-Versatile PB
[<c001a8d4>] (unwind_backtrace) from [<c0017eac>] (show_stack+0x10/0x14)
[<c0017eac>] (show_stack) from [<c02d08f0>] (panic+0x84/0x1e0)
[<c02d08f0>] (panic) from [<c03b9120>] (mount_block_root+0x1a4/0x25c)
[<c03b9120>] (mount_block_root) from [<c03b93b8>] (mount_root+0xe4/0x10c)
[<c03b93b8>] (mount_root) from [<c03b9540>] (prepare_namespace+0x160/0x1b4)
[<c03b9540>] (prepare_namespace) from [<c03b8da4>] (kernel_init_freeable+0x170/0x1b4)
[<c03b8da4>] (kernel_init_freeable) from [<c02cffdc>] (kernel_init+0x8/0xec)
[<c02cffdc>] (kernel_init) from [<c0014880>] (ret_from_fork+0x14/0x34)
---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
It doesn't panic (or more accurately, it panics, but justifiably, because of no root filesystem).

Last edited by WaseemAlkurdi; 10-19-2019 at 04:57 AM.
WaseemAlkurdi is offline   Reply With Quote
Reply


Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Please help with these compilation errors darkbreath Sigil 24 07-22-2016 11:47 AM
How to show kernel boot information instead Amazon boot picture? madtrapper Kindle Developer's Corner 8 01-04-2013 08:51 AM
Can I make a compilation within a compilation? Villordsutch Amazon Kindle 5 01-04-2012 03:10 AM
Opus cannot boot, stuck on boot screen baloma Bookeen 35 11-13-2010 04:20 AM
Compilation of Q&A FGFuzaxx iRex 14 07-17-2006 07:51 AM


All times are GMT -4. The time now is 06:52 PM.


MobileRead.com is a privately owned, operated and funded community.