peterm6881 has joined #Speedsaver
Speedsaver has joined #Speedsaver
Speedsaver` has quit [Ping timeout: 250 seconds]
<peterm6881> hey Xogium
<peterm6881> ok I have good news and less good news
<peterm6881> I was following this:
<peterm6881> this stage completes ok
<peterm6881> make widora_mangopi_r3_defconfig
<peterm6881> when completed, make finishes ok too
<peterm6881> it create 3 separate .img files, sdcard, nor and nand
<peterm6881> sd card gets part way through boot but crashes
<peterm6881> so progress of sorts
<peterm6881> I'm just running a make clean && make
<Xogium> hmm
<Xogium> crashes how ? Kernel panic ?
<peterm6881> yes! You were right about 20.04 working
<Xogium> I suspected as much
<peterm6881> what does kernel panic mean?
<peterm6881> ok its just completed, let me burn the sd card again
<Xogium> A kernel panic (sometimes abbreviated as KP[1]) is a safety measure taken by an operating system's kernel upon detecting an internal fatal error in which either it is unable to safely recover or continuing to run the system would have a higher risk of major data loss. The term is largely specific to Unix and Unix-like systems. For Microsoft Windows operating systems the equivalent term is "Stop error",
<Xogium> resulting in a bug check[2] screen that presents the bug check code on a blue background in Windows (colloquially known as a "Blue Screen of Death" or BSoD), or on a green background on the Xbox One platform and some Windows Insider builds.
peterm6881 has quit [Quit: Leaving]
peterm6881 has joined #Speedsaver
<peterm6881> 1.813240] [<c06eea9c>] (panic) from [<c090135c>]
<peterm6881> 1.820718] [<c090135c>] (mount_block_root) from [
<peterm6881> e+0x128/0x188)
<peterm6881> 1.829249] [<c0901568>] (prepare_namespace) from
<peterm6881> c)
<peterm6881> 1.837164] [<c06f68d4>] (kernel_init) from [<c010
<peterm6881> 34)
<peterm6881> 1.844711] Exception stack(0xc2839fb0 to 0xc2839f
<peterm6881> 1.849758] 9fa0:
<peterm6881> 0 00000000
<peterm6881> 1.857925] 9fc0: 00000000 00000000 00000000 00000
<peterm6881> yeah ignore all that crap
<peterm6881> so why are we getting it here, using their defconfig specifically for this device?
<Xogium> not sure
<Xogium> what's the last message ?
<Xogium> the end kernel panic one
<Xogium> it gives a reason
<peterm6881> 1.813240] [<c06eea9c>] (panic) from [<c090135c>]
<peterm6881> 1.820718] [<c090135c>] (mount_block_root) from [
<peterm6881> 1.829249] [<c0901568>] (prepare_namespace) from
<peterm6881> c)
<peterm6881> e+0x128/0x188)
<peterm6881> 1.837164] [<c06f68d4>] (kernel_init) from [<c010
<peterm6881> 34)
<peterm6881> 1.844711] Exception stack(0xc2839fb0 to 0xc2839f
<peterm6881> 1.849758] 9fa0:
<peterm6881> 0 00000000
<peterm6881> 1.857925] 9fc0: 00000000 00000000 00000000 00000
<peterm6881> this is too annoying
<peterm6881> i can only paste a small number of the post messages
<Xogium> there is one other message
<Xogium> it should say, end kernel panic (not syncing)
<Xogium> then a reason like, attempted to kill init ! Or unlnown block device, or etc
<peterm6881> is it possible to ssh into a ttyUSB device?
<Xogium> no
<peterm6881> i literally cant stand puTTY in linux
<Xogium> you already have a direct connection
<peterm6881> how do you connect to it in terminal?
<Xogium> maybe try something else ? Minicom, screen ?
<peterm6881> screen, of course
<peterm6881> wait
<peterm6881> i wanted to copy the whole post into a documents and email it to you, but I cant scroll up in screen
<peterm6881> document
<peterm6881> how do I scroll up in screen? is it possible?
<peterm6881> [ 1.779485] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2)
<peterm6881> anyway, its this
<peterm6881> [ 1.787823] CPU: 0 PID: 1 Comm: swapper Not tainted 5.4.99 #1
<peterm6881> [ 1.798330] [<c010e1c8>] (unwind_backtrace) from [<c010b964>] (show_stack+0x10/0x14)
<peterm6881> [ 1.806105] [<c010b964>] (show_stack) from [<c06eea9c>] (panic+0xe8/0x2e4)
<peterm6881> [ 1.793552] Hardware name: Allwinner suniv Family
<peterm6881> [ 1.812999] [<c06eea9c>] (panic) from [<c090135c>] (mount_block_root+0x2bc/0x31c)
<peterm6881> [ 1.820480] [<c090135c>] (mount_block_root) from [<c0901568>] (prepare_namespace+0x128/0x188)
<peterm6881> [ 1.829009] [<c0901568>] (prepare_namespace) from [<c06f68d4>] (kernel_init+0x8/0x108)
<peterm6881> [ 1.836923] [<c06f68d4>] (kernel_init) from [<c01010e0>] (ret_from_fork+0x14/0x34)
<peterm6881> [ 1.844470] Exception stack(0xc2839fb0 to 0xc2839ff8)
<peterm6881> [ 1.849519] 9fa0: 00000000 00000000 00000000 00000000
<peterm6881> [ 1.857685] 9fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
<peterm6881> [ 1.865847] 9fe0: 00000000 00000000 00000000 00000000 00000013 00000000
<peterm6881> [ 1.872459] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2) ]---
<peterm6881> Im about to paste the kernel panic from start to finish, hang on a sec
<peterm6881> [ 1.779485] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2)
<peterm6881> [ 1.798330] [<c010e1c8>] (unwind_backtrace) from [<c010b964>] (show_stack+0x10/0x14)
<peterm6881> [ 1.793552] Hardware name: Allwinner suniv Family
<peterm6881> [ 1.806105] [<c010b964>] (show_stack) from [<c06eea9c>] (panic+0xe8/0x2e4)
<peterm6881> [ 1.787823] CPU: 0 PID: 1 Comm: swapper Not tainted 5.4.99 #1
<peterm6881> [ 1.812999] [<c06eea9c>] (panic) from [<c090135c>] (mount_block_root+0x2bc/0x31c)
<peterm6881> [ 1.820480] [<c090135c>] (mount_block_root) from [<c0901568>] (prepare_namespace+0x128/0x188)
<peterm6881> [ 1.829009] [<c0901568>] (prepare_namespace) from [<c06f68d4>] (kernel_init+0x8/0x108)
<peterm6881> [ 1.836923] [<c06f68d4>] (kernel_init) from [<c01010e0>] (ret_from_fork+0x14/0x34)
<peterm6881> [ 1.844470] Exception stack(0xc2839fb0 to 0xc2839ff8)
<peterm6881> [ 1.849519] 9fa0: 00000000 00000000 00000000 00000000
<peterm6881> [ 1.857685] 9fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
<peterm6881> [ 1.865847] 9fe0: 00000000 00000000 00000000 00000000 00000013 00000000
<peterm6881> [ 1.872459] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2) ]---
<peterm6881> the last message is where it hangs
<Xogium> ok so I know why at least
<Xogium> it is unable to mount the rootfs
<peterm6881> how do you think it got broke?
<Xogium> reason might vary, either it doesn't wait long enough for it, either it lacks the filesystem driver to do so, either it doesn't recognize the partition table
<Xogium> things like that
<Xogium> I guess I'll investigate when I get my board
<peterm6881> different card. same result. So at least its consistent
<Xogium> yes yes you will always hit this
<Xogium> but at least we know it can boot from micro sd on its own and we don't have to tell it to do that
<Xogium> which is more than we did know yesterday
<peterm6881> yup, looks like it tries the others first. Im gonna see if I can get the nor or nand versions installed
<peterm6881> any preference?
<Xogium> nand, we don't have nor
<peterm6881> lol that would be a good choice then ;)
<Xogium> there we go, hooked up piezo buzzer to dev kit
<peterm6881> the procedure to get an image onto the nand flash as decribed here is not a thing:
<Speedsaver> Title: MongoPi-R3 Micro Controller/Development Board Linux Wiki - DFRobot (at wiki.dfrobot.com)
<peterm6881> becuase all that happens when you press rst and boot and run the bash script is you get this: ERROR: Allwinner USB FEL device not found!
<peterm6881> so yeah, I think this is all gonna be too hard. Lets not bother. SC6502 managed rto blow up both his Speedsavers. I've never once blown up one in about 4 or 5 years
<peterm6881> to
<peterm6881> so concept: good, software: good, hardware: not a thing
<peterm6881> there comes a point where you really have to take the fucking hint
<Xogium> to be fair you probably need to install the driver to get to detect the board
<Xogium> so get access to fel mode
<Xogium> or
<Xogium> I don't know just trying to help without hardware here
<peterm6881> ok the part the walkthrough didnt tell you is fel mode is accessed through the OTG port ONLY
<Speedsaver> Title: FEL - linux-sunxi.org (at linux-sunxi.org)
<peterm6881> read this
<Xogium> ah
<peterm6881> i know Allwinner dont play by the rules, but to be fair their sunxi documentation is not the worst ive seen
<Xogium> hm this isn't allwinner this is open source tools made by the community
<peterm6881> i suspect the 2 are closely related
<peterm6881> since we know Allwinner literally say NOTHING to anybody else they dont reach out to themselves
<Xogium> I don't think so, the sunxi-tools package is reverse engineered
<Xogium> woohoo
<Xogium> isn't that an awesome pic
<peterm6881> List of MTD devices: No MTD device found
<peterm6881> first one straight of of the box, fucked nand
<peterm6881> out, sigh
<Xogium> hmm from where do you see ?
<peterm6881> I can get it to boot into fel mode, boot messages should indicate presence and size of nand
<peterm6881> none found. the next step would normally be to format it
<peterm6881> awesome quality control
<Xogium> well… that's chinese shit for ya
<Xogium> the software is pure shit
<Xogium> the hardware is perfectly fine
<Xogium> in this case its the software being shit and not detecting the mtd devices because its… missing the driver, or the definition for it in the device tree
<peterm6881> theres no way on gods green earth we are going to get this to do anything
<peterm6881> if the suppliers own tools dont do anything
<Xogium> wait until I get my hands on them boards
<Xogium> I'mm make them dance to my tune, not the vendor's
<peterm6881> lol
<Xogium> also did you see my picture ?
<peterm6881> i would have like to have sent you them actually doing something. You'll need 2 good quality micro USB cables, one for OTG for fel programming, one for ttl
<peterm6881> yes I see an IR blaster and what looks like phone
<Xogium> hehe
<Xogium> the phone is actually the st dev kit
<peterm6881> goodness
<Xogium> big motherf… er, board ?
<Xogium> lol
<peterm6881> I hope you have better luck with hardware than I have! :)
<peterm6881> i tried the original repo that the MangoPi for F1C200s was forked from, needless to say the result was the same
<Xogium> well the dev kit sure runs good, it even came with an already preprogrammed micro sd
<Xogium> st sure isn't joking
<peterm6881> it would be nice if they made affordable chips
<Xogium> I think part of the cost has to do with the fact they lutterally run their own supply chain instead of outsourcing to china like everybody else
<Xogium> *litterally
<Xogium> not saying it accounts for all parts of that cost, but surely it mus have some influence
peterm6881 has quit [Quit: Leaving]
peterm6881 has joined #Speedsaver
<peterm6881> Xogium, have you tried this: https://github.com/unframework/licheepi-nano-buildroot
<peterm6881> I'm trying it now but I dont know what changes I should make to menuconfig, and I need to change something
<peterm6881> otherwise i get the legacy menuconfig error, obvs
<Xogium> that's the image I gave you yesterday
<Xogium> after fixing the legacy configs
<peterm6881> ah ok
<peterm6881> can you remember what you changed?
<Xogium> I just followed the instruction in the menuconfig prompt for legacy config options
<Xogium> this it was just one or two of them, I deselected them, then made board/licheepi_nano/post-image.sh script executable because the guy forgot this part
<Xogium> then it built just fine
<peterm6881> is it possible there is something else in that menuconfig that could fix our kernel panic issue?
<Xogium> this isn't the same buildroot
<Xogium> the kp comes with the official buildroot forthe board
<Xogium> this ones makes the image I gave you which doesn't talk over serial or anything
<peterm6881> can you tell me specifically which options you deselected. I want to try something
<Xogium> the ones that are selected in the legacy options menu in menuconfig
<Xogium> the ones with an * sign
<Xogium> I don't remember which ones those were
<Xogium> but there's only 2 or 3
<peterm6881> ok thanks Xogium
peterm6881 has quit [Quit: Leaving]