Boot hangs
I have my OPI-PC and downloaded OrangePI-PC_Ubuntu_Vivid_Mate.img via Loboris's 342 thread.Did the dd
Mounted BOOT and copied script.bin.OPI-PC_720p60 script.bin- left uImage alone and at other attempts copied uImage_OPI-2 to uImage
I've download Fedora22, Ubuntu, anotherone, from Google (unxz'ed) - a dozen tmes.....
Using HTMI
I've tried various extracts from scriptbin_kernel.tar, nothing, just uImage, uImage and 720p60, includeing "lib" into /linux
Boot starts, screams along starting, setting, staring etc
...
Started Setup Virtual Console
(red)LED Failed to start Kernel Modules.
...
Started vdev kernel dev man
started load/save random seed
starting coyp rules generated while the root was ro...
and that's it - an hour later there is sits ... "was ro..." .If I power off and restart ... nothing.
Suggestions please
Thanks
bug
Remember to umount the sdcard after copying the latest script.bin and Uimage.
Umountwill flush the file buffer so that the latest changes get written to the sdcard.
Use a serial usb cableso that you can catch the output and post it.Then it might tell us if the problem is before or after the linux kernel starts to boot.
When I got my Orangepi PC to boot I didn't copy anything into the lib dir. I just copied 2 files as per the instructions.
Just some ideas... Edited by liderbug at 2015-10-28 21:19
When I dd:plug SD in, umount, dd, unplug, plug, cd to BOOT, cp, cd, umount BOOT & linux.
I've used a 16gb & a 32gb sd.
"Use a serial usb cable "Need a bit of help there.OPI-PC to ??? assume my laptop running FC22.
Search returned 0
Thanks
Hi liderbug,
I'm glad (well, kind of, it sucks not being able to boot your OrangePi) that I'm not the only one encountering this problem. Hopefully it will be easier to fix if there are two of us.
This is the full log from the serial monitor:
http://pastebin.com/BQh9Puwx
I also attach image, because not all info is visible in this log.
http://i.imgur.com/CL8JbRx.jpg
I hope someone will help to come up with a solution. liderbug replied at 2015-10-28 14:14
When I dd:plug SD in, umount, dd, unplug, plug, cd to BOOT, cp, cd, umount BOOT & linux.
I've used ...
Have you run dd with oflag=direct ? If not, you must run sync before unpluging the card reader.
mattizz replied at 2015-10-29 00:34
Hi liderbug,
I'm glad (well, kind of, it sucks not being able to boot your OrangePi) that I'm not th ...
That's my screen exactly. Edited by liderbug at 2015-10-29 06:46
loboris replied at 2015-10-29 00:38
Have you run dd with oflag=direct ? If not, you must run sync before unpluging the card reader.
...
I have ... in the past ... as part of the dd line the last couple of tries??? ... Who's on first...
will do both and report back.
tks
simply as hell,burn img,no copied nothing on BOOT!!!!! Just rename script.binopipc720 to script.bin and uimageopi2 to uimage.Boot and post serial debug. loboris replied at 2015-10-29 00:38
Have you run dd with oflag=direct ? If not, you must run sync before unpluging the card reader.
...
Please edit your thread with img and replace copy wit rename ;)
@liddrbug
What I did.
1)Purchase the serial to usb cable from aliexpress
http://www.aliexpress.com/item/1-pcs-USB-To-RS232-TTL-UART-PL2303HX-Auto-Converter-USB-to-COM-Module-Cable-Newest/1948305958.html
2) install the driver from the manufacturers website. Look up pl2303hx on google to find who made it.
3) find the connection in /dev.
ls -l /dev/*usb*
On my mac its /dev/tty.usbserial
4) connect the usb serial cable.
There are three prongs next to the power inlet.
From left to right, looking at the orangepi from side.
Power supply inlet then
1) black wire
2) green wire
3 white wire
Red wire contains a power supply, i think so just ignore it.
5) run screen. From a terminal window
screen /dev/tty.usbserial 115200
6) plug in power supply to orange pi so that you can collect the log output.
I am probably going to do some tests on my dd procedure as I have encountered some strange problems on my fedora images
Such as
A) bad exec formal on fs_resize on my fedora minimal img
B) yum falls over on my fedora mate img and have not found a similar error message from other users from my searches on google.
I will probably do a md5 sum on the img before I write it and then dd the image back from the sdcard onto my mac and make sure the md5sums match as a verification.
Apple macs do an automatic verify on cds when they are written and given the number of people complaining about their faulty sdcards I think it is reasonable to also do this check.