Linux Distributions for Orange PI H3 boards

loboris

jacer replied at 2015-8-30 01:35
Which one should OPI-PC users download? OrangePI_Lubuntu_Vivid.img.xz? Does lib_mali_r4p0_DDK impl ...

OPI-PC users can download any of the available images.
After writing the image to the SD Card copy uImage_OPI-2 to uImage and script.bin.OPI-PC_resolution to script.bin.
<distro_rel>_mini.img                         are base images without desktop
OrangePI_Ubuntu_Vivid_Mate.img    Ubuntu 15.04 with Mate Desktop
OrangePI_Lubuntu_Vivid.img             Lubuntu 15.04 with LXDE/Lubuntu Desktop
OrangePI_Debian_Jessie.img            Debian 8.1 with XFCE Desktop (will be uploaded later today)

Mali drivers are not yet implemented, but this does not affect desktop performance anyway.
They are needed only for accelerated video playback in Kodi, and eventually for some gpu acceleration in Chromium.
They be added later, after testing.

loboris

ismu replied at 2015-8-30 08:54
Thanks @laboris for your hard work  I have question, what about XFCE? Do you create dedicated imag ...

The uploaded desktop images are base image (mini) + desktop (installed with install_xxx_desktop script) + some manual tweaking.
You can easily create any combination of base image + desktop.
About XFCE, I'll upload Debian Jessie XFCE image later.

Linux root fs can be created on external USB HD.
You can use create_image script to create Linux root fs in local directory (image_name="") and then copy (with rsync) to USB HD partition.
Or you can copy Linux partition from SD Card to external USB HD.

1. sudo rsync -r -t -p -o -g -x --delete -l -H -D --numeric-ids -s --stats <linux_root_directory>/ <mounted_usbhd_partition>/

Copy code

You must have botable sd card inserted (possibly the small one, with only fat partition), and uImage prepared to boot from USB HD.

I'm working on uImage version which will be able to detect the presence of Linux root fs on any partition on external USB HD (or flash drive) and boot from it automatically.
That way you'll be able to have two different Linux installation, one on SD Card and one on USB HD, and boot to USB one if inserted.

ismu

loboris replied at 2015-8-30 16:49
The uploaded desktop images are base image (mini) + desktop (installed with install_xxx_desktop scr ...

Thanks for anserws. I wait for modified uImage When can we expect it (approximately, it is important for you)? But I need only boot from /dev/sdb1, it is possible make it fast? I know you are a lot of work

loboris

ismu replied at 2015-8-30 10:01
Thanks for anserws. I wait for modified uImage  When can we expect it (approximately, it is impo ...

Maybe today, if testing goes well.
I'll include also the script to install Linux to USB HD (similar to install_to_emmc).

Sitheek

@loboris : I have tested your's new mini images - jessie and vivid - There are some problems with kernel, first I am getting gmac error and ethernet does not work, second if reboot or poweroff command is issued you will get kernel panic message.

We have succesfully compiled kernel on Debian Jessie X86_64 and Ubuntu Vivid x86_64. It is necessary to add i386 architecture support to compile it from SDK with loboris scripts and install toolchain acording to H3 manual build documentation.

@loboris : Why have you deleted lechee.tar.gz from mega? Is it still neccesary or not?

I do not understand some of menuconfig options, what is soc camera support. I built these modules but i can not load it neither with modprobe nor insmod. It says no such file or directory. What is the difference between these modules and modules from vfe_sunxi subdirectory?

I will try to play with script.fex acording to instructions from orangepi v1, but I am still not sure what drivers should be loaded to get CSI Camera working.

For now i am not able to use OV5640 CSI Camera

john0815

What can be the reason when opi+ STOPS after 30,07 sec.
I replaced the Lib, the uImage and the script.bin

thank you

phelum

Hi loboris,

Thanks for uploading to Google Drive.  Much appreciated.

Cheers,
Steven

loboris

New kernel version uploaded.
Fixed problems with booting on trusty & wheezy images and with old images.

Please download scriptbin_kernel.tar.gz from Mega or Google drive, unpack and replace the kernel (uImage) on your SD Card (FAT partition), according with board used.

@john0815 I think the problem should be solved with new kernel.
@Sitheek
  have you copied the right script.bin and uImage ? Please use the new kernels.
  lechee.tar.gz was removed because there were some changes. I'll upload it again soon. It was needed only if you wanted to build your own kernel.
  I've ordered the camera module, when I receive it I'll try to fix the camera issues. For now I can't help you with anything related to camera. Sorry.

Sitheek

loboris replied at 2015-8-30 21:19
New kernel version uploaded.
Fixed problems with booting on trusty & wheezy images and with old i ...

I think the trick is related with proper settings of CSI sections in script.bin

I have changed only name of the camera form gc2035 to ov5640 and dmesg says somthing different than before :

[  277.578918] [VFE]cci probe start cci_sel = 0!
[  277.579014] [VFE]cci probe end cci_sel = 0!
[  277.579312] [VFE]cci_init end

[  299.283949] [VFE]Welcome to Video Front End driver
[  299.284292] [VFE]pdev->id = 0
[  299.284304] [VFE]dev->mipi_sel = 0
[  299.284311] [VFE]dev->vip_sel = 0
[  299.284318] [VFE]dev->isp_sel = 0
[  299.290142] [VFE_WARN]vfe vpu clock is null
[  299.298183] [VFE]..........................vfe clk open!.......................
[  299.298217] [ISP] isp platform_id = 5!
[  299.298378] [VFE]vfe_init end
[  299.300075] [VFE]probe_work_handle start!
[  299.300098] [VFE]v4l2 subdev register input_num = 0
[  299.300109] [VFE]vfe sensor detect start! input_num = 0
[  299.300123] [VFE]Find sensor name is "ov5640", i2c address is 78, type is "YUV" !
[  299.300135] [VFE]Sub device register "ov5640" i2c_addr = 0x78 start!
[  299.300149] [VFE]v4l2_device_register_subdev return 0
[  299.300158] [VFE]registered sensor subdev is OK!
[  299.300165] [VFE]Check sensor!
[  299.313469] [VFE]mclk on
[  299.380417] [VFE CCI_0 ERR] Status error at addr_8bit = 78, wr_flag = 1
[  299.380699] [VFE CCI_0 ERR] Status error at addr_8bit = 78, wr_flag = 1
[  299.380968] [VFE CCI_0 ERR] Status error at addr_8bit = 78, wr_flag = 1
[  299.380983] [OV5640]error at sensor_detect
[  299.380991] [OV5640]chip found is not an target chip.
[  299.381002] [VFE]mclk off
[  299.417317] [VFE]vfe sensor subdev unregister!
[  299.417341] [VFE]Sub device register "ov5640" failed!
[  299.417351] [VFE_ERR]vfe sensor register check error at input_num = 0
[  299.424816] [VFE]V4L2 device registered as video0
[  299.424847] [VFE]..........................vfe clk close!.......................
[  299.424871] [VFE]probe_work_handle end!
[  299.430795] [VFE]vfe_open
[  299.430815] [VFE]..........................vfe clk open!.......................
[  299.430850] [VFE]vfe_open ok
[  299.431044] [VFE]vfe_close
[  299.431056] [VFE]vfe select input flag = 0, s_input have not be used .
[  299.431075] [VFE]..........................vfe clk close!.......................
[  299.431110] [VFE]vfe_close end

Me and my friend will try to figure it out what to change in script.fex.
Superb, when you get the sensor we can work together to fix all issues

loboris

  install_xfce_desktop script updated.
  Fixed installing xfce desktop on Debian Jessie.

Download desktop_scripts.tar.gz from Mega or Google drive, extract to /usr/local/bin.