Closed bsvdoom closed 7 years ago
@bsvdoom I don't have the very latest set of patches but with the version that I have (which is actually from the official OPI PC2 repository and which should be very similar) I noticed that if you shutdown even once without issuing sync, your card is very likely to get corrupted. This can manifest in various ways including not being able to get to the kernel or the kernel failing to mount its / or even sudo no longer working.
I would recommend to try to fully reflash the image you built to a new card (one that has not been in use).
@tkggithub I have always inited e2fsck on the mmc card/pendrive (on a remote pc) after each unsuccesful boot. Also tried with two different SD cards, and even pendrives, with the same results. I have reflashed the cards as well before a clean image burn. Also the cards and the pendrives works like charm in other devices. So I almost tried out every possibility to exclude this behaviour, but im out of ideas...
Also as I saw the official OPI PC2 repo is way behind this repo.
@bsvdoom Hi, friends: I have use this SDK to build Debian Sid Image 3 mintues ago, and Image can work on my OrangePi PC2. So, pls git pull this repo and build Image again.
Good Luck
@BuddyZhang1 Thank you buddy, I've pulled and the build is running now, i can test it in the evening, i will report the results.
Still no luck, the same hapened. I will try another card reader, but I dont think thats the issue here. Btw I wonder why Xunlong wrote 5V@2A when this board requires 5V@3A am I right?
@bsvdoom Hi, firends: I have confirm with our hardware engineer, OrangePi PC2 is compatible with 5V@2A and 5V@3A. Now, Pls download a Test Version Image of Debian Sid that build from this SDK.(https://drive.google.com/open?id=0BzAcx3iAhraoMEV5bW1YY0NhY1U) After u got this image, u can run on your board. If it doesn't work, we can check problem on hardware.
Good Luck
@BuddyZhang1 Thak you for the image, i just cant believe it boots. I wonder what the trick is, nobody else reported similar issue.. (why is it specific to my board?) Still testing..
@BuddyZhang1 So... the debug image is working so far. Any tips how can I get to the bottom of this? I need to find out whether is it hardware of software related.
Also no output from HDMI ever yet.
console=tty0 console=ttyS0,115200n8 no_console_suspend disp.screen0_output_mode=EDID:1920x1080p60 hdmi
Still nothing..any ideas, or should I post another issue?
Thanks!
Can anybody point me to any forum where somebody can help me with this? I hope I did not bought a corrupted board...
The problem is now known and solved.
If anyone cares: As I found out, it was a simple contact error with the SD slot. Despite this, the uboot is starting fine, just not recognizing the mmc slot afterwards until I move the card around in the slot a little.
@bsvdoom Hi, firends: I have confirm with our hardware engineer, OrangePi PC2 is compatible with 5V@2A and 5V@3A. Now, Pls download a Test Version Image of Debian Sid that build from this SDK.(https://drive.google.com/open?id=0BzAcx3iAhraoMEV5bW1YY0NhY1U)
Hi, @BuddyZhang1, does this image is compatible with OrangePi PC2? When I upload it on my board with dd
, I got following errors during boot:
Rootfs: /dev/mmcblk0p2
[ 34.051715] EXT2-fs (mmcblk0p2): error: couldn't mount because of unsupported optional features (240)
[ 34.062697] EXT4-fs (mmcblk0p2): couldn't mount as ext3 due to feature incompatibilities
[ 34.081421] JBD2: no valid journal superblock found
[ 34.086774] EXT4-fs (mmcblk0p2): error loading journal
[ 34.126314] UDF-fs: warning (device mmcblk0p2): udf_fill_super: No partition found (2)
mount: mounting /dev/mmcblk0p2 on /mnt/root failed: Invalid argument
umount: can't unmount /mnt/root: Invalid argument
After some research I reproduce this error with my own image (builded with this SDK) and found way to fix it. This issue related to ext4 journaling, that can be disabled with following patch: https://github.com/jubnzv/OrangePiH5_scripts/blob/0410101d8eae7f227bf2678b0edd25e7b7f759f7/build_image.sh#L74
But, anyway, I have some problems with my builded image: after load I got switch_root: can't execute '/sbin/init': Exec format error
after loading kernel. For now I have no idea what causes this error and working on this.
I just need some linux system on this board with ability to upload custom kernel. But no one of official images can be succesfully booted with same "journaling errors"...
May be there are some problems with my SD Card? I use recommended SanDisk 16GB Class 10 (100 Mb/s) card.
Could you please explain what i'm doing wrong?
```
U-Boot 2014.07 (Nov 09 2016 - 15:49:10) Allwinner Technology
uboot commit : 8
secure enable bit: 0
i2c: secure monitor exist
[ 0.728]pmbus: ready
u0:48105000
[ 0.731][ARISC] :arisc initialize
[ 0.762][ARISC] :arisc para ok
[SCP] :sunxi-arisc driver begin startup 2
[SCP] :arisc version: [sun8iw5_v0.03.00-244-gb750b8e]
[SCP] :sunxi-arisc driver v1.20 is starting
[ 0.777][ARISC] :sunxi-arisc driver startup succeeded
axp: get node[charger0] error
[SCP ERROR] :message process error
[SCP ERROR] :message addr : 48105080
[SCP ERROR] :message state : 5
[SCP ERROR] :message attr : 2
[SCP ERROR] :message type : 80
[SCP ERROR] :message result : f3
[SCP WARING] :callback not install
[SCP ERROR] :arisc twi read pmu reg 0x3 err
probe axp806 failed
axp_probe error
[ 0.959]PMU: cpux 1008 Mhz,AXI=336 Mhz
PLL6=600 Mhz,AHB1=200 Mhz, APB1=100Mhz MBus=400Mhz
run key detect
no key found
no uart input
DRAM: 1 GiB
fdt addr: 0x76e9f0e0
Relocation Offset is: 35ef2000
axp: get node[charger0] error
In: serial
Out: serial
Err: serial
gic: sec monitor mode
[box standby] read rtc = 0x0
[box standby] start_type = 0x1
[box standby] to kernel
boot_init_gpio used
ir boot recovery not used
workmode = 0,storage type = 1
[ 1.163]MMC: 0
[mmc]: mmc driver ver 2016-05-20 17:18:00-test0
[mmc]: get card2_boot_para:sdc_ex_dly_used 0
[mmc]: no mmc-hs400-1_8v!
[mmc]: no mmc-hs200-1_8v!
[mmc]: no mmc-ddr-1_8v!
[mmc]: delete max-frequency from dtb
SUNXI SD/MMC: 0
[mmc]: 50 MHz...
[mmc]: sample: 61 - 163(ps)
[mmc]: 100 MHz...
[mmc]: sample: 31 - 161(ps)
[mmc]: 200 MHz...
[mmc]: sample: 16 - 156(ps)
[mmc]: media type 0x0
[mmc]: Wrong media type 0x0
[mmc]: ************Try SD card 0************
[mmc]: host caps: 0x27
[mmc]: MID 00 PSN 00000add
[mmc]: PNM APPSD -- 0x41-50-50-53-44
[mmc]: PRV 0.0
[mmc]: MDT m-10 y-2018
[mmc]: speed mode : HSSDR52/SDR25
[mmc]: clock : 50000000 Hz
[mmc]: bus_width : 4 bit
[mmc]: user capacity : 15441 MB
[mmc]: ************SD/MMC 0 init OK!!!************
[mmc]: erase_grp_size : 0x1WrBlk*0x200=0x200 Byte
[mmc]: secure_feature : 0x0
[mmc]: secure_removal_type : 0x0
[ 1.363]sunxi flash init ok
[ 1.378]start
drv_disp_init
tv_init:
tv_probe:000
no report hpd work,you need support the switch class!
screen 0 don't support TV!
tv_init:
fetch tv1 err.
drv_disp_init finish
hdcp is closed by sys config.
no the part:Reserve0
hpd_dev_num=2, id of def_output_dev is 0
hdmi hpd out, force open?
fdt_setprop_u32 disp.init_disp(0x20b0404) code:
Hey there!
switch_root: can't execute '/sbin/init': Exec format error This error refers that your /sbin/init is not the same arhitecture as your kernel.
Hoe this helps.
I really do not want to spam, but I dont know where else to post this issue, please tell me if you do, and I will correct it.
So in a nutshell I've ordered an Orange PI PC 2, it arrived last week, tied out with this SDK. My first try was building a debian sid image, I've burnt it on a TF card, witch suceeded, but:
Yesterday after I saw the new commits I've tried rebuilding a Xenial release from the scrath SDK, but I got the same results. Can anyone confirm this SDK is working? Could it be a hardware faluire, or just a bugous kernel?
I've put in many-many hours, got more knowledge about software and hardware than I wanted..but still no use..
Here is a log when sda dies randomly. (Using any FS device for more than 10-15 secs reproduces the same.) Here is a log when it succeeded booting and tries to mount the ext4 mmcblk0p2.
Thanks in advance.