gleam2003
-
Posts
28 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Community Map
Posts posted by gleam2003
-
-
On 7/4/2022 at 7:30 AM, Werner said:
Would you mind providing a PR with these changes?
PR make
-
I'm working on it, sorry for delay.
The patch work ok on 5.15.
The uboot patch isn't needed.
Today I will submit the patch
-
3 hours ago, Werner said:
Would you mind providing a PR with these changes?
Yes, i would first test if it work ok with 5.15.
5.10 work fine without change
-
I patch the kernel 5.18 with the attached patch and it boot fine.
The kernel patch switch to i2c like orangepi 3 lts.
Probably it can work with 5.15 but not tested
-
I build legacy kernel 5.10.121 and system boot fine. Kernel 5.10.121 use i2c.
I try to edit dtb and replace rsb wit i2c but system doesn't boot at all (on current kernel)
I don't understand why orangepi 3 lts use i2c and we can't use the same with this board
-
I compile linux in buildroot with all armbian patch (5.10, 5.15) and try with different uboot and atf and I have the same problem.
Also I use the libreelec/lakka patch with buildroot and the board boot always without issue with linux kernel 5.10.109. (uboot+atf+crust)
-
I can't test with other sd, I a have only 3 sdhc memory and all have same issue.
I compile linux in buildroot with all armbian patch (5.10, 5.15) and try with different uboot and atf and I have the same problem.
Also I use the libreelec/lakka patch with buildroot and the board boot always without issue with linux kernel 5.10.109. (uboot+atf+crust)
-
I have similar problem with OrangePi One Plus and Armbian 22.02
First boot work ok, after resize and configure if reboot the image dosen't boot because can't mount root fs.
If I use 21.05 all work fine.
I can suppose it's like this:
I have other board with H3 and H5 and the problem dosen't affect this models
-
I use the patch and compile the image with the armbian.
Compilation is ok.
There isn't tve overlay to use, i don't know if it's necessary.
I power on the board with the image builded and Image work and I can connect via SSH but no image output.
I also test to add tve overlay to image, add tve to dts overlay Make file. I now have the dtbo tve file but adding it to overlay don't give me the solution, no image output.
If I use old kernel (with fex) image output via CVBS works.
UPDATE: add the patch for enable tve overlays kernel-sunxi-current.patch
-
I can't make it working with orangepi zero and kernel 5.10.92, can anyone help me
-
-
Finaly build with no error with this deb:
http://ftp.br.debian.org/debian/pool/main/q/qemu/qemu-user-static_5.1+dfsg-3_amd64.deb
-
2 hours ago, Werner said:
Does this happen as well when building on Ubuntu Focal native or in a virtual environment (Virtualbox or similar)?
The error with qemu old version happen on both, native or virtual.
The error after update qemu to 5.0 happen on vagrant, for now I don't test on native.
-
Now I have this error on end of build process:
Quote[ o.k. ] Unmounting [ /home/vagrant/armbian/.tmp/rootfs-legacy-beelinkx2-buster-no-no ]
qemu-arm-static: /build/qemu-aGGHr4/qemu-5.0/linux-user/elfload.c:2327: pgb_reserved_va: Assertion `addr == test' failed.
/home/vagrant/armbian/lib/distributions.sh: line 597: 3795 Aborted (core dumped) chroot "${SDCARD}" /bin/bash -c "dpkg-divert --quiet --local --rename --remove /sbin/initctl"
qemu-arm-static: /build/qemu-aGGHr4/qemu-5.0/linux-user/elfload.c:2327: pgb_reserved_va: Assertion `addr == test' failed.
/home/vagrant/armbian/lib/distributions.sh: line 597: 3798 Aborted (core dumped) chroot "${SDCARD}" /bin/bash -c "dpkg-divert --quiet --local --rename --remove /sbin/start-stop-daemon" -
http://security.ubuntu.com/ubuntu/pool/main/q/qemu/qemu_5.0-5ubuntu6_amd64.deb
Installed this on focal and now work -
where find compiled quemu 5.1.0 for focal? I test to build but have error when link with "--static"
-
Can I add that in past with old version of armbian on Ubuntu 16.04 the problem dosen't exist. Qemu version in this case, if I'm not wrong, is 2.5
-
I tried with Bionic and have the same issue.
Yes, is probably Qemu problem, I have the same problem if I chroot manually and try to do the same thing.In Focal qemu version is 3, in Bionic qemu version is 4 and I have the same problem.
I compile the version 5 on Focal but I can't successefull build the static version with softemmu.I will test the 5 from unstable branch on Bionic
-
In my customize-image.sh I need to dowload source via git and make it like user and not like root.
Example of customize-image.sh:
git clone https://github.com/xxx/xxx /home/pi/xxx
su -c "sudo -S /home/pi/xxx/xxx.sh" - pi
This work when I build image for OrangePi4 (and all other rk3399 board)
It dosen't work when build image for sun8i board like OrangePi Lite. Both git and su command return error and compilation fail.
This happen with legacy and mainline kernel, with ubuntu or debian.
-
Anyone can help me to find what I need to modify in u-boot for reach 1.2ghz cpu clock. I know that I can have some troubles with this clock but I use only 1 or 2 CPU core and already test this clock with old legacy kenrel without thermal or power issues.
-
There's a way to change the framebuffer display resolution / refreshrate?
Via HDMI my display work at 1920x1080 at 25Hz, i need to set it to 60Hz
-
1 hour ago, gleam2003 said:
You think is sufficent to make this change to drivers/mmc/core/mmc.c in kernel?
if (card->ext_csd.rev > 7) {
if (card->ext_csd.rev > 8) {
I can confirm that with this mod eMMC now work and I can use the nand-sata-install
-
1 hour ago, gleam2003 said:
I have already one R69 and no problem to access to eMMC and use NAND install script with an Legacy kernel Image.
Now I bought 2 new box and from the same image I can't access to eMMC in any way
If I use mainline kenrnel no problem, but my work for now only work on Legacy kernel.
[ 1.543692] mmc0: new high speed SDHC card at address 59b4
[ 1.544181] mmcblk0: mmc0:59b4 USD00 14.9 GiB
[ 1.545566] mmcblk0: p1
[ 1.546152] mmcblk mmc0:59b4: Card claimed for testing.
[ 1.546167] mmc0:59b4: USD00 14.9 GiB
[ 1.547746] [mmc]: sdc2 power_supply is null
[ 1.622884] mmc2: unrecognised EXT_CSD revision 8
[ 1.622900] mmc2: error -22 whilst initialising MMC card
[ 1.623020] [mmc]: sdc2 power_supply is null
[ 1.626080] [wifi_pm]: get wifi_sdc_id failed
[ 1.627121] [mmc]: sdc2 power_supply is null
[ 1.660056] usb 6-1: new low-speed USB device number 2 using sunxi-ohci
[ 1.717076] mmc2: unrecognised EXT_CSD revision 8
[ 1.717089] mmc2: error -22 whilst initialising MMC card
[ 1.717203] [mmc]: sdc2 power_supply is null
[ 1.721302] [mmc]: sdc2 power_supply is nullYou think is sufficent to make this change to drivers/mmc/core/mmc.c in kernel?
if (card->ext_csd.rev > 7) {
if (card->ext_csd.rev > 8) {
-
I have already one R69 and no problem to access to eMMC and use NAND install script with an Legacy kernel Image.
Now I bought 2 new box and from the same image I can't access to eMMC in any way
If I use mainline kenrnel no problem, but my work for now only work on Legacy kernel.
[ 1.543692] mmc0: new high speed SDHC card at address 59b4
[ 1.544181] mmcblk0: mmc0:59b4 USD00 14.9 GiB
[ 1.545566] mmcblk0: p1
[ 1.546152] mmcblk mmc0:59b4: Card claimed for testing.
[ 1.546167] mmc0:59b4: USD00 14.9 GiB
[ 1.547746] [mmc]: sdc2 power_supply is null
[ 1.622884] mmc2: unrecognised EXT_CSD revision 8
[ 1.622900] mmc2: error -22 whilst initialising MMC card
[ 1.623020] [mmc]: sdc2 power_supply is null
[ 1.626080] [wifi_pm]: get wifi_sdc_id failed
[ 1.627121] [mmc]: sdc2 power_supply is null
[ 1.660056] usb 6-1: new low-speed USB device number 2 using sunxi-ohci
[ 1.717076] mmc2: unrecognised EXT_CSD revision 8
[ 1.717089] mmc2: error -22 whilst initialising MMC card
[ 1.717203] [mmc]: sdc2 power_supply is null
[ 1.721302] [mmc]: sdc2 power_supply is null
First boot with only red LED
in Orange Pi Zero 2
Posted
I find that rsb is used in place if i2c.
I have an old board and like old orengepi one plus and the new orangepi 3 lts they dosen't boot with rsb.
I modify the DTS for use i2c and the board boot.
I think that this rsb bus is buggy